IETF Logo Mail Archive

Re: [lamps] Logo carrying certificate profile for email` draft

Russ Housley <housley@vigilsec.com> Thu, 10 May 2018 16:55 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D344126DFB for <spasm@ietfa.amsl.com>; Thu, 10 May 2018 09:55:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 T1J3ePkx3u9L for <spasm@ietfa.amsl.com>; Thu, 10 May 2018 09:55:07 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5EAA12EBD9 for <spasm@ietf.org>; Thu, 10 May 2018 09:55:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id CD1A9300A26 for <spasm@ietf.org>; Thu, 10 May 2018 12:55:03 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id HZHkz5__sd4T for <spasm@ietf.org>; Thu, 10 May 2018 12:55:02 -0400 (EDT)
Received: from [5.5.33.83] (vpn.snozzages.com [204.42.252.17]) by mail.smeinc.net (Postfix) with ESMTPSA id 2D6153004D6; Thu, 10 May 2018 12:55:00 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <DF9CC133-E092-42F3-965F-FD69C0C0B063@vigilsec.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_BC37F12C-0662-42B5-88DA-D0A05D5D1100"; protocol="application/pkcs7-signature"; micalg="sha1"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Thu, 10 May 2018 12:54:59 -0400
In-Reply-To: <CAAFsWK2YCAQGPomunWv3CELDmKUYGN7phZN3=3+xr9cVQe7JwQ@mail.gmail.com>
Cc: LAMPS <spasm@ietf.org>
To: Wei Chuang <weihaw@google.com>
References: <CAAFsWK2YCAQGPomunWv3CELDmKUYGN7phZN3=3+xr9cVQe7JwQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/XXjETZkH4iRcmZosuCXTvsgj4ME>
Subject: Re: [lamps] Logo carrying certificate profile for email` draft
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 16:55:09 -0000

Wei:

I think that an Independent stream document is sufficient to get the code point assignments.

Russ


> On May 8, 2018, at 3:02 AM, Wei Chuang <weihaw@google.com> wrote:
> 
> Hi all,
> 
> I've posted a draft https://datatracker.ietf.org/doc/draft-chuang-bimi-certificate/ <https://datatracker.ietf.org/doc/draft-chuang-bimi-certificate/> regarding a logo carrying certificate for authenticated email using domain based methods (DKIM and SPF).  In particular this draft calls for a new Extended Key Usage for these certificates to help distinguish this usage from other profiles such as S/MIME.  Can this draft be considered for the LAMPS rechartering?  This work is being done by a Brand Indicator for Message Identification (BIMI) working group.  An early version of the overall protocol can be seen at https://authindicators.github.io/rfc-brand-indicators-for-message-identification/ <https://authindicators.github.io/rfc-brand-indicators-for-message-identification/> though that version doesn't include changes that include X.509 certificates.  
> 
> thanks,
> -Wei 
>

v2.23.0 | Report a Bug | By Email