Re: [mile] [IANA #911630] RE: Evaluation: <draft-ietf-mile-rfc5070-bis-22.txt> to Proposed Standard
"Roman D. Danyliw" <rdd@cert.org> Fri, 10 June 2016 20:15 UTC
Return-Path: <rdd@cert.org>
X-Original-To: expand-draft-ietf-mile-rfc5070-bis.all@virtual.ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 2C42412D123; Fri, 10 Jun 2016 13:15:16 -0700 (PDT)
X-Original-To: xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0878012D8FB for <xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com>; Fri, 10 Jun 2016 13:15:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org
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 dFrukHNeTmAN for <xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com>; Fri, 10 Jun 2016 13:15:14 -0700 (PDT)
Received: from plainfield.sei.cmu.edu (plainfield.sei.cmu.edu [192.58.107.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA52112D84D for <draft-ietf-mile-rfc5070-bis.all@ietf.org>; Fri, 10 Jun 2016 13:15:13 -0700 (PDT)
Received: from timber.sei.cmu.edu (timber.sei.cmu.edu [10.64.21.23]) by plainfield.sei.cmu.edu (8.14.4/8.14.4/1543) with ESMTP id u5AKDQdu030157; Fri, 10 Jun 2016 16:13:26 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cert.org; s=jthatj15xw2j; t=1465589606; bh=kJkD1SSAwiS1ajACKHW5cPFBiqC7b+fs9VaJ0ky9jFg=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version:Sender: Reply-To; b=lKpCuj/jMQFtJbdJghS3p6CE6hulqQRSIsfuwKyEasp2BTSjpbUnzF+B16jUWdON5 vuEckBony/2hHbpgllGaZqb0ZrXQGGJI8UI11hfM004Q9DoOWka2LnXbezlZTEME5W lFbeKK+lvV4p5GPZFW84StGRFIlUgLIPLpjl75ww=
Received: from CASSINA.ad.sei.cmu.edu (cassina.ad.sei.cmu.edu [10.64.28.249]) by timber.sei.cmu.edu (8.14.4/8.14.4/1543) with ESMTP id u5AKB9KR028627; Fri, 10 Jun 2016 16:11:09 -0400
Received: from MARATHON.ad.sei.cmu.edu ([10.64.28.250]) by CASSINA.ad.sei.cmu.edu ([10.64.28.249]) with mapi id 14.03.0279.002; Fri, 10 Jun 2016 16:13:22 -0400
From: "Roman D. Danyliw" <rdd@cert.org>
To: "drafts-eval-comment@iana.org" <drafts-eval-comment@iana.org>
Thread-Topic: [IANA #911630] RE: Evaluation: <draft-ietf-mile-rfc5070-bis-22.txt> to Proposed Standard
Thread-Index: AQHRwoLcMts0z7Efj0+h/RToguVUbp/jDB8A
Date: Fri, 10 Jun 2016 20:13:21 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFCD975E324@marathon>
References: <RT-Ticket-911630@icann.org> <RT-Ticket-910912@icann.org> <20160527200004.11174.11087.idtracker@ietfa.amsl.com> <rt-4.2.9-21084-1464848494-693.910912-7-0@icann.org> <359EC4B99E040048A7131E0F4E113AFCD9750185@marathon> <rt-4.2.9-8280-1465498593-1772.911630-9-0@icann.org>
In-Reply-To: <rt-4.2.9-8280-1465498593-1772.911630-9-0@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.64.22.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Resent-From: alias-bounces@ietf.org
Resent-To: rdd@cert.org, ncamwing@cisco.com, takeshi_takahashi@nict.go.jp, david.waltermire@nist.gov, Kathleen.Moriarty.ietf@gmail.com, stephen.farrell@cs.tcd.ie, mile-chairs@tools.ietf.org, mile@ietf.org
Resent-Message-Id: <20160610201516.2C42412D123@ietfa.amsl.com>
Resent-Date: Fri, 10 Jun 2016 13:15:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/l1Xax_KjaN2kxHlpcYop1tx1PEE>
Cc: "draft-ietf-mile-rfc5070-bis.all@ietf.org" <draft-ietf-mile-rfc5070-bis.all@ietf.org>
Subject: Re: [mile] [IANA #911630] RE: Evaluation: <draft-ietf-mile-rfc5070-bis-22.txt> to Proposed Standard
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2016 20:15:16 -0000
Good afternoon Amanda! Thanks for the example. Could you please make the column names: ** "Attribute Value" ** "Description" ** "Reference" Back to my earlier example: Sub-Registry name: Contact-role Attribute Value = creator Description = The entity that generate the document. Reference = RFC-num-of-this-document Roman > -----Original Message----- > From: Amanda Baber via RT [mailto:drafts-eval-comment@iana.org] > Sent: Thursday, June 09, 2016 2:57 PM > Cc: draft-ietf-mile-rfc5070-bis.all@ietf.org > Subject: [IANA #911630] RE: Evaluation: <draft-ietf-mile-rfc5070-bis-22.txt> > to Proposed Standard > > Hi Roman, > > One more question: should the contents of Section 10.2's "IV (Value)" > column appear anywhere in the registry? For example, should it be the label > for that registry's value column? For example, in the CDNI Payload Types > registry at http://www.iana.org/assignments/cdni-parameters, the label for > the value column is "Payload Type." > > thanks, > Amanda > > On Thu Jun 02 13:24:34 2016, rdd@cert.org wrote: > > Hello Amanda! > > > > Sorry for the confusion. Let me clarify below ... > > > > > -----Original Message----- > > > From: Amanda Baber via RT [mailto:drafts-eval@iana.org] > > > Sent: Thursday, June 02, 2016 2:22 AM > > > Cc: draft-ietf-mile-rfc5070-bis.all@ietf.org; iesg@ietf.org > > > Subject: [IANA #910912] Evaluation: <draft-ietf-mile-rfc5070-bis- > > > 22.txt> to Proposed Standard > > > > > > IESG: > > > > > > IANA NOT OK. Comments in tracker > > > IANA Actions - NOT OK > > > > > > How to populate these 33 registries is unclear. > > > > > > For example, Section 3.9 says, “These values are maintained in the > > > ‘Contact- > > > role’ IANA registry per Section 10.2” and then presents a list of 19 > > > items. Is the “Contact-role” registry made up of the single entry in > > > the IANA Considerations table, as the IANA Considerations section > > > seems to indicate, or does it consist of the 19 items in Section > > > 3.9? If the latter, where should the entries in 10.2 table's "IV > > > (Value)" column be placed? > > > > Taking "Contact-role" as an example, the desired outcome is the > > following: > > > > --[ snip ]-- > > Registry name: Contact-role > > > > Value, Description, Reference > > "creator", "The entity that generate the document.", RFC-num-of-this- > > document "reporter, "The entity that reported the information.", > > RFC-num-of- this-document "admin", "An administrative contact or > > business owner for an asset or organization.", > > RFC-num-of-this-document ... [ entry #4 - 18] ... > > "ext-value", "A value used to indicate that this attribute is extended > > and the actual value is provided using the corresponding ext-* > > attribute." , RFC-num-of-this-document --[ snip ]-- > > > > Yes, each enumerate value will be a distinct entry in a given > > registry. Contact-role would have 19 entries. > > > > I realized that there is no text saying that a reference to this > > document should be added to each registry entries in the Reference > > column. > > > > Roman > >
- [mile] [IANA #910912] Evaluation: <draft-ietf-mil… Amanda Baber via RT
- Re: [mile] [IANA #910912] Evaluation: <draft-ietf… Roman D. Danyliw
- [mile] [IANA #911630] RE: Evaluation: <draft-ietf… Amanda Baber via RT
- [mile] [IANA #911630] RE: Evaluation: <draft-ietf… Amanda Baber via RT
- Re: [mile] [IANA #911630] RE: Evaluation: <draft-… Roman D. Danyliw