Re: [mile] [IANA #910912] Evaluation: <draft-ietf-mile-rfc5070-bis-22.txt> to Proposed Standard

"Roman D. Danyliw" <rdd@cert.org> Thu, 02 June 2016 13:11 UTC

Return-Path: <rdd@cert.org>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91D4E12D6CD; Thu, 2 Jun 2016 06:11:28 -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 79t8fFqyPePe; Thu, 2 Jun 2016 06:11:26 -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 352C412D18F; Thu, 2 Jun 2016 06:11:25 -0700 (PDT)
Received: from pawpaw.sei.cmu.edu (pawpaw.sei.cmu.edu [10.64.21.22]) by plainfield.sei.cmu.edu (8.14.4/8.14.4/1543) with ESMTP id u52D9ZM9024278; Thu, 2 Jun 2016 09:09:35 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cert.org; s=jthatj15xw2j; t=1464872975; bh=i+rw1GiTPUs3vGLPYrWOy2kt8qTvyX2MjC0mSHAJQeI=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version:Sender: Reply-To; b=T3TWjGjEMJ+aVGjeSl0cG2SYPuBc2I0yDNCfnYosOJ81pkAPvQ6PQEqqv9NswJQhJ 89wPJidj63Cz0+Bn4pdZGUYDytqjwxRZgGV1GEkCfHENbt5xGYgWbaYpkFfULnHcWY N3j340LMNjxhzAdD0xW3V+0GGOCTVyUu8jfeV9GM=
Received: from CASSINA.ad.sei.cmu.edu (cassina.ad.sei.cmu.edu [10.64.28.249]) by pawpaw.sei.cmu.edu (8.14.4/8.14.4/1543) with ESMTP id u52D9WnZ011636; Thu, 2 Jun 2016 09:09:32 -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; Thu, 2 Jun 2016 09:09:31 -0400
From: "Roman D. Danyliw" <rdd@cert.org>
To: "drafts-eval@iana.org" <drafts-eval@iana.org>
Thread-Topic: [IANA #910912] Evaluation: <draft-ietf-mile-rfc5070-bis-22.txt> to Proposed Standard
Thread-Index: AQHRvJcKxLUfTwKRi06UvEaYjyCDAZ/WIZ1A
Date: Thu, 02 Jun 2016 13:09:30 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFCD9750185@marathon>
References: <RT-Ticket-910912@icann.org> <20160527200004.11174.11087.idtracker@ietfa.amsl.com> <rt-4.2.9-21084-1464848494-693.910912-7-0@icann.org>
In-Reply-To: <rt-4.2.9-21084-1464848494-693.910912-7-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
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/jBJyrh4YvsdIZ1qg3HPrNOrxNnA>
Cc: "mile@ietf.org" <mile@ietf.org>, "draft-ietf-mile-rfc5070-bis.all@ietf.org" <draft-ietf-mile-rfc5070-bis.all@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [mile] [IANA #910912] 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: Thu, 02 Jun 2016 13:11:28 -0000

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