Re: [lamps] rfc7030-est clarifications and LAMPS charter

Russ Housley <housley@vigilsec.com> Mon, 05 August 2019 14:02 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 D5E99120222 for <spasm@ietfa.amsl.com>; Mon, 5 Aug 2019 07:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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 H9gKtvZLh0tn for <spasm@ietfa.amsl.com>; Mon, 5 Aug 2019 07:02:02 -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 A3E9912018A for <spasm@ietf.org>; Mon, 5 Aug 2019 07:02:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id A8C03300AAF for <spasm@ietf.org>; Mon, 5 Aug 2019 09:42:44 -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 ByBiFZ_xfr12 for <spasm@ietf.org>; Mon, 5 Aug 2019 09:42:42 -0400 (EDT)
Received: from [172.26.55.168] (unknown [104.129.196.116]) by mail.smeinc.net (Postfix) with ESMTPSA id 4001B3004D8; Mon, 5 Aug 2019 09:42:41 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <0455CEB5-65EF-498C-A5E9-133C6D4226CE@sn3rd.com>
Date: Mon, 05 Aug 2019 10:01:59 -0400
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, LAMPS WG <spasm@ietf.org>, Ben Kaduk <kaduk@mit.edu>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3DF77ED0-C4EC-479E-84E9-C882CAFE076D@vigilsec.com>
References: <21504.1564174053@dooku.sandelman.ca> <9CE09410-5F6B-407F-B239-888E3136F24A@vigilsec.com> <547B521B-A93B-4E33-96A9-8B2DEE216748@vigilsec.com> <20190731194117.GG1006@kduck.mit.edu> <14050.1564606087@localhost> <0455CEB5-65EF-498C-A5E9-133C6D4226CE@sn3rd.com>
To: Sean Turner <sean@sn3rd.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/jhXXe927YPGxAboav4ADh-xSbg0>
Subject: Re: [lamps] rfc7030-est clarifications and LAMPS charter
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 05 Aug 2019 14:02:05 -0000

Sure.  That name change works for me.  I think adding the module can only improve interoperability.

Russ


> On Aug 5, 2019, at 7:58 AM, Sean Turner <sean@sn3rd.com> wrote:
> 
> I think you have two choices:
> 
> 1) Fix the  text
> 2) Fix the text and include a module
> 
> In either case fixing the text is* :
> 
> * This is basically what Russ suggested, but I do not think the name of the set should imply that the only attributes that can be used are defined in 7030.  Any attribute can be included so I changed “AttributesDefinedInRFC7030” to “CsrAttrSet”.
> 
> OLD:
> 
> CsrAttrs ::= SEQUENCE SIZE (0..MAX) OF AttrOrOID
> 
>   AttrOrOID ::= CHOICE (oid OBJECT IDENTIFIER, attribute Attribute }
> 
>   Attribute { ATTRIBUTE:IOSet } ::= SEQUENCE {
>        type   ATTRIBUTE.&id({IOSet}),
>        values SET SIZE(1..MAX) OF ATTRIBUTE.&Type({IOSet}{@type}) }
> 
> NEW:
> 
> CsrAttrs ::= SEQUENCE SIZE (0..MAX) OF AttrOrOID
> 
>   AttrOrOID ::= CHOICE {
>       oid OBJECT IDENTIFIER,
>       attribute Attribute {{AttrSet}}  }
> 
>   Attribute { ATTRIBUTE:IOSet } ::= SEQUENCE {
>        type   ATTRIBUTE.&id({IOSet}),
>        values SET SIZE(1..MAX) OF ATTRIBUTE.&Type({IOSet}{@type}) }
> 
>  AttrSet ATTRIBUTE ::= { CsrAttrSet }
> 
>  CsrAttrSet ATTRIBUTE ::= {
>       aa-asymmDecryptKeyID,     -- see Section 4.4.1.2.
>       … }
> 
> spt
> 
> 
>> On Jul 31, 2019, at 16:48, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
>> 
>> Signed PGP part
>> 
>> Benjamin Kaduk <kaduk@mit.edu> wrote:
>>>> Thinking about this some more, I think that the best way to resolve
>>>> this errata is to provide an appendix with an ASN.1 module.  Here is
>>>> my suggestion:
>> 
>>> That feels somewhat heavyweight for an erratum.  What are the pros/cons
>>> of errata vs. small updating RFC?
>> 
>> The intention is to have a small updating RFC.
>> 
>> -- 
>> ]               Never tell me the odds!                 | ipv6 mesh networks [
>> ]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
>> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [
>> 
>> 
>> 
> 
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm