Re: [drinks] [IANA #803729] Expert Review for draft-ietf-drinks-spp-protocol-over-soap-07

Alexander Mayrhofer <alexander.mayrhofer@nic.at> Wed, 04 February 2015 08:31 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 C72B51A6FF3; Wed, 4 Feb 2015 00:31:42 -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 YcATmQTNy1q5; Wed, 4 Feb 2015 00:31:39 -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 3FF5B1A0163; Wed, 4 Feb 2015 00:31:28 -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:31:26 +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:31:22 +0100
From: Alexander Mayrhofer <alexander.mayrhofer@nic.at>
To: "drafts-expert-review-comment@iana.org" <drafts-expert-review-comment@iana.org>
Thread-Topic: [IANA #803729] Expert Review for draft-ietf-drinks-spp-protocol-over-soap-07
Thread-Index: AQHQMa+iM/+W1K9UKk65vxqmNCtYD5zgQZzw
Date: Wed, 4 Feb 2015 08:31:22 +0000
Message-ID: <19F54F2956911544A32543B8A9BDE07546743592@NICS-EXCH2.sbg.nic.at>
References: <RT-Ticket-803729@icann.org> <rt-4.0.8-27994-1421263974-1150.803729-9-0@icann.org> <rt-4.2.9-8251-1421428339-1577.803729-9-0@icann.org>
In-Reply-To: <rt-4.2.9-8251-1421428339-1577.803729-9-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/Gx5rbbl-lZ7Jt6ecZYtXv1rAEsw>
Cc: "drinks@ietf.org" <drinks@ietf.org>, "drinks-chairs@tools.ietf.org" <drinks-chairs@tools.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "draft-ietf-drinks-spp-protocol-over-soap.all@tools.ietf.org" <draft-ietf-drinks-spp-protocol-over-soap.all@tools.ietf.org>
Subject: Re: [drinks] [IANA #803729] Expert Review for draft-ietf-drinks-spp-protocol-over-soap-07
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:31:43 -0000

(author hat on)

Pearl,

please find my responses to Graham's questions below:

> [...]
> I do have a couple of questions:
> 
> (a) the XML appears to use at least two new URNs:
> 
> xmlns:sppfb="urn:ietf:params:xml:ns:sppf:base:1"
> xmlns:sppfs="urn:ietf:params:xml:ns:sppf:soap:1"
>
> but only registers one:
> 
> urn:ietf:params:xml:ns:sppf:soap:1
> 
> It's probably fine - I think the other is registered in
> https://tools.ietf.org/html/draft-ietf-drinks-spp-framework-09#section-11.1.
> Will these documents be going forward together? A little more explanation
> and cross-reference might conceivably be helpful (e.g. that the WSDL
> definition uses these new URNs, and where the other one is defined).

This is correct - the registration of the other namespace is requested in the Framework document. And, yes, the intention is that both documents move forward together, since they are tightly coupled anyways. 

We will add explanation and cross-reference to the document together in either a new revision of the document or an RFC Editor Note - my proposal for such text would be to add a new paragraph in Section 12 (IANA Considerations), saying:

Note that the WSDL Specification also makes use of the "urn:ietf:params:xml:ns:sppf:base:1" XML Namespace URN, which is defined in [SPPF].

> (b) it's not clear from the registration what the URN is being registered *as*.
> From context, I think it is as an *XML namespace*, but I think it could be
> clearer (both XML Namespaces and XML Schemas are mentioned in the
> accompanying text).

Again, we will address this together with other changes to the document, my proposal is to change the first paragraph of Section 12 into:

This document uses URNs to describe XML Namespaces and XML Schemas.
 According to [RFC3688], IANA is requested to perform  registration of the following URN in the 
 IANA XML Namespace Registry:

(plus add the following Line to the front of the registration request)

Registration request for the SPPF SOAP XML namespace:

Hope that clarifies the questions?
thanks,
Alex