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

Wei Chuang <weihaw@google.com> Thu, 10 May 2018 17:00 UTC

Return-Path: <weihaw@google.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 533FA124B17 for <spasm@ietfa.amsl.com>; Thu, 10 May 2018 10:00:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -18.209
X-Spam-Level:
X-Spam-Status: No, score=-18.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 dehnzkyiTy-b for <spasm@ietfa.amsl.com>; Thu, 10 May 2018 10:00:21 -0700 (PDT)
Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82F08126DFB for <spasm@ietf.org>; Thu, 10 May 2018 10:00:21 -0700 (PDT)
Received: by mail-io0-x22d.google.com with SMTP id e20-v6so3827111iof.4 for <spasm@ietf.org>; Thu, 10 May 2018 10:00:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+FXH+Tqm8IvGIZcSBUgK2Fu6D92lX9wuRMv39nhT61E=; b=C1Mkyoyr3feTSxznBEiLfdJ4FBusgD9XtQ+lFxnZmGW+6uopjQQPsQQ7p5y8NXqFUo qo3gnE7G4zmH0/bmxftKeyrvac/ZeS8x40rQJ95uYLgWnwP/78YwkaX9RdnBDMBdTLXs V1M9zSlvhZKpOcwBMkRgATLRyZwdZMNdqwjte1ZHsu2o54rcgrEf0lz3bhjo0MMqOFQe a/f+hFoiuChJQGvQd8xUJHa3b7SAWUY7r+1VnqcnEn0N+tkOqEzJJ33Pwg9ELlz5xBVB Wyx8wN54mO4i9tWl/ry50lucyAIr7+/IlSO9hSEOVaBYbsLg/vq6gPkZNPnR/GrAI25Y Hc3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+FXH+Tqm8IvGIZcSBUgK2Fu6D92lX9wuRMv39nhT61E=; b=sBRmKBWvyt//DS72SbSu/Lp4kMSUE3pDi+U2MK/0RT0IyUpDVfEf9eM0T60HEFw+TB 9b4jK9rmkZ1eV5f5jPfVVLsb2onzv/30O+OSwVXTO53kD6+7dOqWGZx+HUcLcSSs11Me tjkfWlA+NTwX5a4Yknr5tSU3qBE94YJejPiRWLglrpAVEoFP+qlO8Hh9Ln9hAKr0P7uK ZtSF4Xm3ANHoKYntXEWcnxNn0ZW9+AQtXT0glLiWjRjaxxTmCIyo9ObrciC6Duh+2AH5 J1I/cQ/c7AlgXp83NWy6ZxiJh7kcwoQxsDmvy0Lt5gcbmZ21bu1hZaPOaegmebPiHdCw SydA==
X-Gm-Message-State: ALKqPwfBGjFP1RqzdRBtHCJlaOo4+Kodm1EWp1Lc2RtaLdBBegywcFJC JjYm/UcCuBbNZCoaoQjCMYFRr6q1JpETLYBNwVoezu+6
X-Google-Smtp-Source: AB8JxZoziCyLzoZ/J4n5XVbigETgDZEVozczLv/lIuUrXHtjuSUN357bJnejSrnCEhmoZbbdrXuo5IUJyx1Q2wYGaGQ=
X-Received: by 2002:a6b:6b16:: with SMTP id g22-v6mr2334949ioc.20.1525971620402; Thu, 10 May 2018 10:00:20 -0700 (PDT)
MIME-Version: 1.0
References: <CAAFsWK2YCAQGPomunWv3CELDmKUYGN7phZN3=3+xr9cVQe7JwQ@mail.gmail.com> <DF9CC133-E092-42F3-965F-FD69C0C0B063@vigilsec.com>
In-Reply-To: <DF9CC133-E092-42F3-965F-FD69C0C0B063@vigilsec.com>
From: Wei Chuang <weihaw@google.com>
Date: Thu, 10 May 2018 10:00:05 -0700
Message-ID: <CAAFsWK1j0X1wnbdHtQxLM4J7j+8bZS1dPJm+zitirkN7XzEuLw@mail.gmail.com>
To: Russ Housley <housley@vigilsec.com>
Cc: SPASM <spasm@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="000000000000697f6d056bdcf4c7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/EloMdJBiDfdSYwYhI3EpEgLa9G0>
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 17:00:23 -0000

I'm fine with that.  I was checking with the author of the other likely
IETF document (BIMI assertion records) whether he intended his document to
be standards track to make sure that's aligned (likely it should be).

-Wei

On Thu, May 10, 2018 at 9:55 AM Russ Housley <housley@vigilsec.com> wrote:

> 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/ 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/
> though that version doesn't include changes that include X.509
> certificates.
>
> thanks,
> -Wei
>
>
>