Re: [drinks] [IANA #802710] Last Call: <draft-ietf-drinks-spp-framework-09.txt> (Session Peering Provisioning Framework (SPPF)) to Proposed Standard

Alexander Mayrhofer <alexander.mayrhofer@nic.at> Wed, 04 February 2015 08:06 UTC

Return-Path: <alexander.mayrhofer@nic.at>
X-Original-To: drinks@ietfa.amsl.com
Delivered-To: drinks@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEB3C1A6FF3 for <drinks@ietfa.amsl.com>; Wed, 4 Feb 2015 00:06:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.741
X-Spam-Level:
X-Spam-Status: No, score=-5.741 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 ghZlPlPyHgut for <drinks@ietfa.amsl.com>; Wed, 4 Feb 2015 00:06:27 -0800 (PST)
Received: from mail.sbg.nic.at (mail.sbg.nic.at [83.136.33.227]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49E911A6FE9 for <drinks@ietf.org>; Wed, 4 Feb 2015 00:06:26 -0800 (PST)
Received: from nics-exch2.sbg.nic.at ([10.17.175.6]) by mail.sbg.nic.at over TLS secured channel (TLSv1:AES128-SHA:128) with XWall v3.50 ; Wed, 4 Feb 2015 09:06:24 +0100
Received: from NICS-EXCH2.sbg.nic.at ([fe80::a5b2:6e42:e54d:9d57]) by NICS-EXCH2.sbg.nic.at ([fe80::a5b2:6e42:e54d:9d57%12]) with mapi id 14.03.0224.002; Wed, 4 Feb 2015 09:06:21 +0100
From: Alexander Mayrhofer <alexander.mayrhofer@nic.at>
To: "drafts-lastcall@iana.org" <drafts-lastcall@iana.org>
Thread-Topic: [IANA #802710] Last Call: <draft-ietf-drinks-spp-framework-09.txt> (Session Peering Provisioning Framework (SPPF)) to Proposed Standard
Thread-Index: AQHQNQWBiwd3WazDOEm7yLQsJLPmG5zgNy+Q
Date: Wed, 04 Feb 2015 08:06:19 +0000
Message-ID: <19F54F2956911544A32543B8A9BDE075467434CB@NICS-EXCH2.sbg.nic.at>
References: <RT-Ticket-802710@icann.org> <20150108140910.22746.6448.idtracker@ietfa.amsl.com> <rt-4.2.9-18109-1421795067-252.802710-7-0@icann.org>
In-Reply-To: <rt-4.2.9-18109-1421795067-252.802710-7-0@icann.org>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.10.0.163]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-XWALL-BCKS: auto
Archived-At: <http://mailarchive.ietf.org/arch/msg/drinks/2yu0Wb2OlUxkknQbHZSz3YWXdM8>
Cc: "drinks@ietf.org" <drinks@ietf.org>, "drinks-chairs@tools.ietf.org" <drinks-chairs@tools.ietf.org>, "draft-ietf-drinks-spp-framework.all@tools.ietf.org" <draft-ietf-drinks-spp-framework.all@tools.ietf.org>
Subject: Re: [drinks] [IANA #802710] Last Call: <draft-ietf-drinks-spp-framework-09.txt> (Session Peering Provisioning Framework (SPPF)) to Proposed Standard
X-BeenThere: drinks@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DRINKS WG <drinks.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/drinks>, <mailto:drinks-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/drinks/>
List-Post: <mailto:drinks@ietf.org>
List-Help: <mailto:drinks-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/drinks>, <mailto:drinks-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2015 08:06:33 -0000


Dear IANA-Team,

> On approval of this document, IANA understands that there are three
> actions which IANA must complete.

This is correct.
 
> First, in the ns registry of the IETF XML registry located at:
> 
> http://www.iana.org/assignments/xml-registry/
> 
> a new namespace will be registered as follows:
> 
> ID: sppf:base:1
> URI: urn:ietf:params:xml:ns:sppf:base:1
> Filename: [ TBD-at-registration ]
> Reference: [ RFC-to-be ]

Correct.

> As this document requests registration in a Specification Required registry,
> we will initiate the required Expert Review via a separate request. Expert
> review will need to be completed before your document can be approved
> for publication as an RFC.

I do understand that Expert approval was granted for this namespace, according to IANA Ticket #804800 (http://www.ietf.org/mail-archive/web/drinks/current/msg01310.html)
 
> Second, in the schema registry of the IETF XML registry located at:
> 
> http://www.iana.org/assignments/xml-registry/
> 
> a new schema will be registered as follows:
> 
> ID: sppf:1
> URI: urn:ietf:params:xml:ns:sppf:1
> Filename: [ TBD-at-registration ]
> Reference: [ RFC-to-be ]

Correct.

> As this document requests registration in a Specification Required registry,
> we will initiate the required Expert Review via a separate request. Expert
> review will need to be completed before your document can be approved
> for publication as an RFC.

I do understand the expert approval referred above does also cover that registration.
 
> Third, a new registry is to be created called the SPPF OrgIdType Namespaces"
> registry. Assignments consist of the OrgIdType namespace string and a
> reference for that string. The new registry is to be maintained via "RFC
> Required" as defined in RFC 5226.

This is correct.
 
> There are initial registrations in the new registry as follows:
> 
> OrgIdType namespace string Namespace Reference
> -------------------------- --------- -------------- IANA Enterprise Numbers iana-en [
> RFC-to-be ]
> 
> IANA QUESTION -> Where should this new registry be located? Is it a néw
> registry on the IANA Matrix (http://www.iana.org/protocols) or is it a
> subregistry of an existing registry, listed at http://www.iana.org/protocols? If
> it is a subregistry of an existing registry, in which registry will it be contained?

Clarification: This is a new registry on the IANA Matrix.

> IANA understands that these three actions are the only ones required to be
> completed upon approval of this document.

This is correct. 

thanks,
Alex Mayrhofer