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

"Pearl Liang via RT" <drafts-expert-review-comment@iana.org> Fri, 16 January 2015 17:12 UTC

Return-Path: <iana-shared@icann.org>
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 279C11ACE8A; Fri, 16 Jan 2015 09:12:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.19
X-Spam-Level:
X-Spam-Status: No, score=-3.19 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 Oza9AasxugXt; Fri, 16 Jan 2015 09:12:19 -0800 (PST)
Received: from smtp1.lax.icann.org (smtp01.icann.org [192.0.33.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A31F21ACD7D; Fri, 16 Jan 2015 09:12:19 -0800 (PST)
Received: from request3.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp1.lax.icann.org (8.13.8/8.13.8) with ESMTP id t0GHCJFv031971; Fri, 16 Jan 2015 17:12:19 GMT
Received: by request3.lax.icann.org (Postfix, from userid 48) id 72D48C21427; Fri, 16 Jan 2015 17:12:19 +0000 (UTC)
RT-Owner: pearl.liang
From: Pearl Liang via RT <drafts-expert-review-comment@iana.org>
In-Reply-To: <rt-4.0.8-27994-1421263974-1150.803729-9-0@icann.org>
References: <RT-Ticket-803729@icann.org> <rt-4.0.8-27994-1421263974-1150.803729-9-0@icann.org>
Message-ID: <rt-4.2.9-8251-1421428339-1577.803729-9-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #803729
X-Managed-BY: RT 4.2.9 (http://www.bestpractical.com/rt/)
X-RT-Originator: pearl.liang@icann.org
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Fri, 16 Jan 2015 17:12:19 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/drinks/IDaxqNerl0uCg-dNINJCj2Oxl08>
X-Mailman-Approved-At: Mon, 19 Jan 2015 08:03:04 -0800
Cc: drinks@ietf.org, drinks-chairs@tools.ietf.org, iesg@ietf.org, draft-ietf-drinks-spp-protocol-over-soap.all@tools.ietf.org
Subject: [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
Reply-To: drafts-expert-review-comment@iana.org
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: Fri, 16 Jan 2015 17:12:21 -0000

Hello,

The requested IANA actions from this draft has been reviewed by the experts.
Please see below question and comment from Graham Klyne:

> This document is requesting a new URN assignment in ns registry in the XML
> registry http://www.iana.org/assignments/xml-registry/xml-registry.xhtml.
>
> Can this be approved?

[...]
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).

(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).

...

I can't respond to the technical detail of the registration, but beyond the 
nit-questions above the request seems OK and I know of no reason to not go ahead 
with the registrations.

#g
--


Thanks,
~pl