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

"Pearl Liang via RT" <drafts-expert-review@iana.org> Mon, 09 February 2015 17:44 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 D86711A1B60; Mon, 9 Feb 2015 09:44:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.49
X-Spam-Level:
X-Spam-Status: No, score=-0.49 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 p2Jb30hxPNjo; Mon, 9 Feb 2015 09:44:38 -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 019D81A1B29; Mon, 9 Feb 2015 09:44:37 -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 t19HibM1028643; Mon, 9 Feb 2015 17:44:37 GMT
Received: by request3.lax.icann.org (Postfix, from userid 48) id 8A70CC20480; Mon, 9 Feb 2015 17:44:37 +0000 (UTC)
RT-Owner: pearl.liang
From: "Pearl Liang via RT" <drafts-expert-review@iana.org>
In-Reply-To: <19F54F2956911544A32543B8A9BDE07546743592@NICS-EXCH2.sbg.nic.at>
References: <RT-Ticket-807172@icann.org> <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> <19F54F2956911544A32543B8A9BDE07546743592@NICS-EXCH2.sbg.nic.at>
Message-ID: <rt-4.2.9-14398-1423503877-557.807172-7-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #807172
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: Mon, 09 Feb 2015 17:44:37 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/drinks/dofmQOnTq-bitpbnujBho6bv0Sg>
X-Mailman-Approved-At: Thu, 19 Feb 2015 00:22:32 -0800
Cc: drinks-chairs@tools.ietf.org, iesg@ietf.org, drinks@ietf.org, draft-ietf-drinks-spp-protocol-over-soap.all@tools.ietf.org
Subject: [drinks] [IANA #807172] AW: 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@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: Mon, 09 Feb 2015 17:44:40 -0000

Hi all,

Graham has reviewed the below comments and has no further question.

Thanks,
~pl


On Wed Feb 04 08:31:51 2015, alexander.mayrhofer@nic.at wrote:
> (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