IETF Logo Mail Archive

Re: [lamps] CAA Semantics for S/MIME

Ryan Sleevi <ryan-ietf@sleevi.com> Sat, 19 May 2018 04:03 UTC

Return-Path: <ryan-ietf@sleevi.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 45B2912E8C8 for <spasm@ietfa.amsl.com>; Fri, 18 May 2018 21:03:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.599, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sleevi.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 gLauE2Yd96At for <spasm@ietfa.amsl.com>; Fri, 18 May 2018 21:03:42 -0700 (PDT)
Received: from homiemail-a25.g.dreamhost.com (homie-sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3387812E8CB for <spasm@ietf.org>; Fri, 18 May 2018 21:03:42 -0700 (PDT)
Received: from homiemail-a25.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a25.g.dreamhost.com (Postfix) with ESMTP id C8F4A6001306 for <spasm@ietf.org>; Fri, 18 May 2018 21:03:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sleevi.com; h=mime-version :references:in-reply-to:from:date:message-id:subject:to:cc :content-type; s=sleevi.com; bh=MFFBYESomMvEAXxo1FzR/CdjnoM=; b= s8WPXwDasOGbSJGegTk0aS0489CII9pojgcORKYqIxvwbOZ5JsTA1+lL4K9HjCZI AB52InrYnC5Ftu+KTOGymyCTUNU1viIW2hqQyIOn7CIP5emlHpb2OVdai6wyK5FL 210Qj5fP+g4PDLZXlc0Tsxw9izFvacSsPmUBoDlf1aE=
Received: from mail-io0-f181.google.com (mail-io0-f181.google.com [209.85.223.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: ryan@sleevi.com) by homiemail-a25.g.dreamhost.com (Postfix) with ESMTPSA id 93C786000129 for <spasm@ietf.org>; Fri, 18 May 2018 21:03:39 -0700 (PDT)
Received: by mail-io0-f181.google.com with SMTP id g1-v6so8538482iob.2 for <spasm@ietf.org>; Fri, 18 May 2018 21:03:39 -0700 (PDT)
X-Gm-Message-State: ALKqPwfb5Rhk/RFL8qPru4v6GF/O1tC66vXwz/bdSPMWtZrnkXBIT4ZK qnqvjbp0YCzi7e9xJwiIBD+vmSohCIy37CDtigc=
X-Google-Smtp-Source: AB8JxZqN954gIcV02T+Q3MKeFFMVk2tGQgoHdAsGfwZYlM/lXUrOZpo0whIbiwd7yUE2PF5ZxnNXsAPA75mCXlpnqmI=
X-Received: by 2002:a6b:d312:: with SMTP id s18-v6mr12783137iob.284.1526702618869; Fri, 18 May 2018 21:03:38 -0700 (PDT)
MIME-Version: 1.0
References: <CAPh8bk-dtfqcf35m=Jwyv7Mm2mrFXe8xgiEKfvj7_W8PB-=+_A@mail.gmail.com> <CABcZeBPY__PZ=jeS6xjzhPZLhn3bf6Nkh=2oLTiNpSxTL5kEQQ@mail.gmail.com> <CAMm+Lwgxm5AsjGUDGoanwSrKvBCabEqs6rDEiBA7UFbmiA4w5w@mail.gmail.com>
In-Reply-To: <CAMm+Lwgxm5AsjGUDGoanwSrKvBCabEqs6rDEiBA7UFbmiA4w5w@mail.gmail.com>
From: Ryan Sleevi <ryan-ietf@sleevi.com>
Date: Sat, 19 May 2018 00:03:28 -0400
X-Gmail-Original-Message-ID: <CAErg=HEGomBCEaqEtqmc6E0XBiBR29DNwkhADJY+FcneFLjP9g@mail.gmail.com>
Message-ID: <CAErg=HEGomBCEaqEtqmc6E0XBiBR29DNwkhADJY+FcneFLjP9g@mail.gmail.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: Eric Rescorla <ekr@rtfm.com>, SPASM <spasm@ietf.org>, Wayne Thayer <wthayer@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000469d4e056c872758"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/13VHHMn9mRgxeiAJT4LJKOLjKn0>
Subject: Re: [lamps] CAA Semantics for S/MIME
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: Sat, 19 May 2018 04:03:44 -0000

Seems like it would be better discussed in a place with open access and
participation? To avoid capture by CAs by having a diverse set of views
represented?

On Fri, May 18, 2018 at 11:24 PM Phillip Hallam-Baker <phill@hallambaker.com>
wrote:

> Perhaps we could have a side discussion about this at the London CABForum
> meeting if folk are there.
>
>
>
> On Fri, May 18, 2018 at 1:45 PM, Eric Rescorla <ekr@rtfm.com> wrote:
>
>> I agree that this is out of the proposed charter. If the WG wants to add
>> it as a charter item now, that seems fine.
>>
>> -Ekr
>>
>>
>> On Tue, May 15, 2018 at 6:00 PM, Wayne Thayer <wthayer@gmail.com> wrote:
>>
>>> There is a vigorous discussion about CAA and S/MIME certificates
>>> happening over on the mozilla.dev.security.policy list [1]. It has been
>>> proposed that this issue could be addressed as part of rfc6844bis, but I'm
>>> reading the LAMPS recharter as being too narrow in scope to permit this.
>>> Does this work need to be deferred to a future LAMPS recharter?
>>>
>>> - Wayne
>>>
>>> [1]
>>> https://groups.google.com/d/msg/mozilla.dev.security.policy/NIc2Nwa9Msg/RGx4A5HBBAAJ
>>>
>>> _______________________________________________
>>> Spasm mailing list
>>> Spasm@ietf.org
>>> https://www.ietf.org/mailman/listinfo/spasm
>>>
>>>
>>
>> _______________________________________________
>> Spasm mailing list
>> Spasm@ietf.org
>> https://www.ietf.org/mailman/listinfo/spasm
>>
>>
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm
>

v2.23.0 | Report a Bug | By Email