IETF Logo Mail Archive

Re: [Endymail] Improvements to S/MIME

Phillip Hallam-Baker <phill@hallambaker.com> Sun, 14 September 2014 14:26 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: endymail@ietfa.amsl.com
Delivered-To: endymail@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 268B51A03C4 for <endymail@ietfa.amsl.com>; Sun, 14 Sep 2014 07:26:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IcxNpTuuy4Zy for <endymail@ietfa.amsl.com>; Sun, 14 Sep 2014 07:26:08 -0700 (PDT)
Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8E8B1A03C3 for <endymail@ietf.org>; Sun, 14 Sep 2014 07:26:07 -0700 (PDT)
Received: by mail-la0-f43.google.com with SMTP id gi9so3379984lab.30 for <endymail@ietf.org>; Sun, 14 Sep 2014 07:26:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=HA+Cwz+VWxS4ILkwgUUQvcBOA7xn51xIjfijAQmmPh8=; b=C8mNf7VTUPYHPpgEdZVd/kH+h6io9cHXNftg0ThC0LHNXCNNMGkRA2Q2IiaYtzLDtS ZPusEpc0hq7f/OwmFpeW8EygNoPbT7zDIh1SVANsUJOMzpXUJbhZmBLwdcw/JAGB9G00 qXnSreauOiVytgW99MM2vy/IzURRqTj00N0P2usr457h87mMt9C+Hk1tPsUHdHawplj7 sR8SRBhWxqJo24E6PkkYfkj42RWapOi0z4cAvAAVYrcl8JgnpA1r413qz4NOwVOio5Z4 V5zo++RcDWX9T09ajWX+eCbIPqsK55ULfneKsBW5EfrZVMtSQADXdyUSnZul+n/P25Xk ptdA==
MIME-Version: 1.0
X-Received: by 10.112.157.162 with SMTP id wn2mr20841918lbb.18.1410704766150; Sun, 14 Sep 2014 07:26:06 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.122.51 with HTTP; Sun, 14 Sep 2014 07:26:06 -0700 (PDT)
In-Reply-To: <777AF78C7D6D8A868249F5B5@cyrus-4.local>
References: <CAAFsWK0VtnVvKwvkC1kjK+yKORkADVW1cKDx7nQ1fxA=dpZeTQ@mail.gmail.com> <87sijvmmo5.fsf@vigenere.g10code.de> <CAMm+LwivBifWKYMDBDocr4LCH40iVgP4zE2xXgEfkrb4bpN+Nw@mail.gmail.com> <CAAFsWK1kZ6Hh9dEZiRrVJ1XaWWQmOMe2fp0174fPx3JzGsXTdg@mail.gmail.com> <777AF78C7D6D8A868249F5B5@cyrus-4.local>
Date: Sun, 14 Sep 2014 10:26:06 -0400
X-Google-Sender-Auth: BbYGc46qCvJ4cdRsyazQmBLTC9U
Message-ID: <CAMm+LwikXRV8ZWibbcS=3wW96ogsbhJSd=KAuUc=pAMPhSgp+w@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Cyrus Daboo <cyrus@daboo.name>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/endymail/eEba_dEvaMswDBCVcp-bb1hXWuk
Cc: Wei Chuang <weihaw@google.com>, Werner Koch <wk@gnupg.org>, endymail <endymail@ietf.org>
Subject: Re: [Endymail] Improvements to S/MIME
X-BeenThere: endymail@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <endymail.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/endymail>, <mailto:endymail-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/endymail/>
List-Post: <mailto:endymail@ietf.org>
List-Help: <mailto:endymail-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/endymail>, <mailto:endymail-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Sep 2014 14:26:09 -0000

On Sun, Sep 14, 2014 at 10:14 AM, Cyrus Daboo <cyrus@daboo.name> wrote:
> Hi Wei,
>
> --On September 14, 2014 at 1:21:19 AM -0700 Wei Chuang <weihaw@google.com>
> wrote:
>
>>> * Mechanism for discovering recipient encryption preference, format
>>> support (PGP/SMIME), algorithm support and encryption key
>>>
>>
>> Two ideas:
>> 1) DNS (either new TXT entry or new record type)
>> 2) EHLO SMTP extension
>
> What about Webfinger - RFC7033?

Well design of a JSON Web Service is hardly difficult.

Webfinger infrastructure might be one of the places we look for
information, so is the DNS, so is the emergent Trans notary
infrastructure.

First we should decide on what the information flows between the
client and service need to be. Then we can decide what the realization
should be.

A Web Service is just an API after all, reuse of an API is sometimes
good and sometimes very bad. Trying to reuse a 2D API for 3D graphics
was a very bad plan for the company that tried it.

v2.23.0 | Report a Bug | By Email