IETF Logo Mail Archive

Re: [Endymail] Improvements to S/MIME

Wei Chuang <weihaw@google.com> Mon, 15 September 2014 08:39 UTC

Return-Path: <weihaw@google.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 CADE71A01E1 for <endymail@ietfa.amsl.com>; Mon, 15 Sep 2014 01:39:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.03
X-Spam-Level:
X-Spam-Status: No, score=-3.03 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001] autolearn=ham
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 hLEz4XKcUCbU for <endymail@ietfa.amsl.com>; Mon, 15 Sep 2014 01:39:00 -0700 (PDT)
Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5D1C1A017A for <endymail@ietf.org>; Mon, 15 Sep 2014 01:39:00 -0700 (PDT)
Received: by mail-qg0-f43.google.com with SMTP id a108so3613057qge.30 for <endymail@ietf.org>; Mon, 15 Sep 2014 01:38:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=4u3ToQN7qE+pn+Rn6t88NC+Q9zjYwjFnrC5mBkT/Cms=; b=p3ZnMyDdnrSbOLeAKM5umaf33JFSUIDWjegfufpuw0TXTldUXNC9DqYeHCFb3/7c8m hX8jUNWXI4JLrTUqSB2VKQlM+y9SPLWN8ld4rCNgdk+hWYkCnNOMhalIRgTaWIpk+hme xZ6PDBMfLELCCw4eusztNFMSqDM+G/zTzqKBHW/7fr+oDPIzTLZENtPdyBo4Kr6OuGWV eUdMi6XRZt8dmDUxJHYYG53UtqyAX44z+gJLm4vQFd36qi4gbDdq2JXAHr2b40xbhxR3 ykJA2/o9GLj90/xqE2+G9Ze+YcvP72xWh4Q2srPxwzKVUzHfrsRsRnjc0RG41+aHz03g Dy8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=4u3ToQN7qE+pn+Rn6t88NC+Q9zjYwjFnrC5mBkT/Cms=; b=jpREu265hPCMesohy2oBwfXepz4wF56ewpVFhZFcbKowGk2pYfxy9GZSH/WnCkdppy fceCF9cEK/JUeP3rRNIFqzQ2lF1kHM8bvxBcJi8leAfrch7PuUKWM1mgO1nBE/cmRSxV 58BVSoXOohwTpHI6sYpuzB/iPkUvTD9l00ZadVBponvDYaentgfYfRLecYpFEEO4J8zP IFLIeNyC7QBcnRejR3iaPavRIJ7LlxUeoT8bGUSZWPhPXuZPgx9AfBRbnohwqPG1RsZS S24a+OVn6njmND6uOs5r/SVAHrtWj/IfmKJNI8EGrGmVE0THA+aQQgvm3DUcXwTSBXFM hTMA==
X-Gm-Message-State: ALoCoQkWdCAOtP/jE0bw8JCrm8QexIEDCCCug0bO4jLNxseE2/nwdSDytJlNZjhkFLcTeZMfxPrC
X-Received: by 10.224.162.196 with SMTP id w4mr33318051qax.60.1410770339845; Mon, 15 Sep 2014 01:38:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.116.71 with HTTP; Mon, 15 Sep 2014 01:38:38 -0700 (PDT)
In-Reply-To: <CAMm+LwikXRV8ZWibbcS=3wW96ogsbhJSd=KAuUc=pAMPhSgp+w@mail.gmail.com>
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> <CAMm+LwikXRV8ZWibbcS=3wW96ogsbhJSd=KAuUc=pAMPhSgp+w@mail.gmail.com>
From: Wei Chuang <weihaw@google.com>
Date: Mon, 15 Sep 2014 01:38:38 -0700
Message-ID: <CAAFsWK0g-QQFgphg4Z+UoDLJxAKzS5pnCkO32d6kTKxg1vcZfw@mail.gmail.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Content-Type: multipart/alternative; boundary="089e012946b6f7a19305031690cf"
Archived-At: http://mailarchive.ietf.org/arch/msg/endymail/HJ5ReG-ZBwOViF5nK3fbEo6nmq8
Cc: Cyrus Daboo <cyrus@daboo.name>, 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: Mon, 15 Sep 2014 08:39:03 -0000

On Sun, Sep 14, 2014 at 7:26 AM, Phillip Hallam-Baker <phill@hallambaker.com
> wrote:

> 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?
>

Agreed another idea to examine (as all have interesting trade offs).


>
> 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.
>

This is related to Certificate Transparency right?  Granted I'm not really
that familiar with CT which I had thought was for attestation of the
validity of a certificate.  Is there a pointer to some discussion /
description on how one might use the Trans Notary infrastructure to
broadcast the configuration information?

-Wei

v2.23.0 | Report a Bug | By Email