[mile] [IANA #909390] Last Call: <draft-ietf-mile-rfc5070-bis-21.txt> (The Incident Object Description Exchange Format v2) to Proposed Standard

"Sabrina Tanamal via RT" <drafts-lastcall-comment@iana.org> Wed, 01 June 2016 22:03 UTC

Return-Path: <iana-shared@icann.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 16E5412B071; Wed, 1 Jun 2016 15:03:00 -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 E3B4212D097; Wed, 1 Jun 2016 15:02:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.625
X-Spam-Level:
X-Spam-Status: No, score=-4.625 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-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 SgcAq0xjjXLV; Wed, 1 Jun 2016 15:02:58 -0700 (PDT)
Received: from smtp01.icann.org (smtp01.icann.org [192.0.46.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4510A12B071; Wed, 1 Jun 2016 15:02:58 -0700 (PDT)
Received: from request3.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp01.icann.org (8.13.8/8.13.8) with ESMTP id u51M2vB1005813; Wed, 1 Jun 2016 22:02:57 GMT
Received: by request3.lax.icann.org (Postfix, from userid 48) id 4CA49C202F4; Wed, 1 Jun 2016 22:02:57 +0000 (UTC)
RT-Owner: sabrina.tanamal
From: Sabrina Tanamal via RT <drafts-lastcall-comment@iana.org>
In-Reply-To: <20160518180522.14701.2797.idtracker@ietfa.amsl.com>
References: <RT-Ticket-909390@icann.org> <20160518180522.14701.2797.idtracker@ietfa.amsl.com>
Message-ID: <rt-4.2.9-23239-1464818577-194.909390-9-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #909390
X-Managed-BY: RT 4.2.9 (http://www.bestpractical.com/rt/)
X-RT-Originator: sabrina.tanamal@icann.org
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Wed, 01 Jun 2016 22:02:57 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
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: <20160601220300.16E5412B071@ietfa.amsl.com>
Resent-Date: Wed, 01 Jun 2016 15:03:00 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/K4tBW8F92DBpCU9tVJV_CiGeFrw>
Cc: draft-ietf-mile-rfc5070-bis.all@ietf.org, iesg@ietf.org
Subject: [mile] [IANA #909390] Last Call: <draft-ietf-mile-rfc5070-bis-21.txt> (The Incident Object Description Exchange Format v2) to Proposed Standard
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: drafts-lastcall-comment@iana.org
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: Wed, 01 Jun 2016 22:03:00 -0000

IESG/Authors/WG Chairs:

As this document is asking IANA to add and maintain a large number of registries, we suggest that the authors evaluate to make sure that all these registries are needed.

In addition, we need the authors to clarify the registries' contents. Is the document instructing IANA to create 33 registries, each of which has a single entry consisting of the corresponding contents of the table's "IV (Value)" column, the table's "IV (Description)" column, and a Reference column that will include a link to this document? Or will each of those registries have multiple values pulled from the sections named in the "IV (Description)" field? For example, would the "Restriction" registry consist of the 10 values listed in Section 3.3.1? 

Section 3.3.1 specifically states, "These [10] values are maintained in the 'Restriction' IANA registry per Section 10.2," but this appears to be contradicted by the paragraph preceding the table in Section 10.2, which seems to indicate that only the single value in that Section 10.2 table, "iodef-restriction-type," will be registered. 

If these registries should be made of the lists of values in Section 3.3.1, 3.2, 3.9, etc., the purpose of the "IV (Description)" field in the table in Section 10.2 is unclear. 

Thank you, 

Sabrina Tanamal
IANA Specialist
ICANN