From nobody Thu Jan 8 03:53:01 2015 Return-Path: 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 9F66B1A89B5 for ; Thu, 8 Jan 2015 03:52:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.977 X-Spam-Level: X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 FluBdLBZ67sp for ; Thu, 8 Jan 2015 03:52:56 -0800 (PST) Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B309E1A3B9F for ; Thu, 8 Jan 2015 03:52:55 -0800 (PST) Received: by mail-la0-f44.google.com with SMTP id gd6so8752859lab.3 for ; Thu, 08 Jan 2015 03:52:54 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=a6Eao36M3YMKIkjQsWCOD8ABzzjYEvdhgc7bGaMqhYc=; b=N4KEWuz4hErw+l8Dgn650bDyM722TeCqCIUFtI9ad7BpkeH0loiedGjW1CbSQ1rdZE /59KmGeGIH7sHWtkVyASebW0plMFC7HuG1KUsOu4XlgnbMvCuRj/PkYbiggGmtkaSp8J SEMy+4Ba5L7HvTITlMgdsckuw6m3huzTsgmaaOIZVaD+lRIOT+zNuYdFgno3QsJsprGp emhNCOX9eFfVveqkWgCqa5xerwtudA7HKCQDikp8d+xPtnH49OhPySMUj6q2qJRQl+np SqUD5Hhkt/ARTfbN6v3bA7qo4Q9nzo/nlHD8NVD5+k4kXkjfjqeF5AY/DamCYFjhQn8G xIkg== X-Gm-Message-State: ALoCoQn0T0Ex3n6SPdqmlAwGwpRWA/Emw6G3jsXcY/zeFCaneCmI3ONVfy5IYDT19Y/odTkHySns MIME-Version: 1.0 X-Received: by 10.112.170.36 with SMTP id aj4mr12647645lbc.3.1420717636923; Thu, 08 Jan 2015 03:47:16 -0800 (PST) Received: by 10.25.12.215 with HTTP; Thu, 8 Jan 2015 03:47:16 -0800 (PST) Date: Thu, 8 Jan 2015 11:47:16 +0000 Message-ID: From: Richard Barnes To: "drinks@ietf.org" , draft-ietf-drinks-spp-framework@tools.ietf.org, draft-ietf-drinks-spp-protocol-over-soap@tools.ietf.org Content-Type: multipart/alternative; boundary=001a11c261fc134aa7050c229abe Archived-At: Subject: [drinks] AD review of draft-ietf-drinks-spp-framework and draft-ietf-drinks-spp-protocol-over-soap X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2015 11:52:59 -0000 --001a11c261fc134aa7050c229abe Content-Type: text/plain; charset=UTF-8 I have reviewed these documents in preparation for IETF LC. Overall, I think they hang together OK, even if the use of XML and SOAP does make me feel like I'm back in the 90s :) I've requested LC, but there are a few comments below that I would like you to consider along with other LC comments. Overall, these specifications would read better if they were not separated as they are, especially since there doesn't seem to be any demand for non-SOAP transports. But they are intelligible separately, so I won't object to processing them as-is. --Richard ===== draft-ietf-drinks-spp-framework-09 ===== ** TODO: See RFC 5486 for use cases Section 1, "for data distribution to SSP" - Expand "SSP" Section 1, "SED is typically used" - Expand "SED" Section 2 - It would be helpful to define "Session Establishment Data", at least by reference. Section 4 - Do we realistically expect there to be other transports for this protocol? If not, let's delete this section or move it to an appendix. Section 4.11, "provided in SPP Protocol over SOAP document" - Needs a normative reference. Section 5.1 - This section needs to define the semantis for the cDate/mDate elements, as is done in Section 6.1 et al. (I assume these are "created" and "modified", respectively.) Section 5.2 - It seems odd that these identifiers have defined contents, but not a data structure. Shouldn't these be moved from the SOAP document to this section? Section 5.3 - It seems like the "conforming specification MUST define" incantation could be moved to the top. Section 6.2, "When a Public Identifier is not member of any Destination Group, it is intended to be associated with SED through the SED Records that are directly associated with the Public Identifier." Since the "dgName" illustration above shows the association to a Destination Group, it would be helpful to note that these direct associations are provided using "sedRecRef" elements in individual identifiers. Section 6.2 - In a related vein, why is "sedRecRef" not defined at the level of PubIdType, along with "dgName"? As is, it's only defined for TNs. This seems to imply that other identifier types must be part of a Destination Group. Why is that? Section 6.2 - It seems like more needs to be said about NumberValType, especially as it is used for TN / RN / TNP. For TN/RN, MUST it be the full E.164 number? For TNP, is it a truncated E.164 number? Section 6.2 - "Whether the Registry can accommodate the open number plan semantics is a matter of policy and is beyond the scope of this document." No, it's not! The semantics of TNR need to be clear regardless of the number plan. Whether a given registry *accepts* TNR objects for open number plans is up to the registry. The semantics are not clear to me. Could you provide an example of how TNR works in an an open-plan environment? ===== draft-ietf-drinks-spp-protocol-over-soap-07 ===== I did not review the WSDL or examples in detail. Section 5, "Clients and Servers MUST use HTTP Digest Authentication" - Is there a reason that TLS-layer authentication (client certificates) is not acceptable? Or other, stronger techniques that might come out of HTTPAUTH. Section 7.1 - It seems like this section should move to -spp-framework. Section 7.2 - Given that you're using namespaces, prepending "sppp" to all the element names here seems wasteful. Instead of "", just use xmlns:sppp="..." and "". Section 7.2 - It would save some schema/writing if you pulled out a few common attributes of the request and response objects (clientTransId, minorVer; clientTransId, serverTransId, overallResult, detailResult). These would also be good candidates for things to put in the SOAP header. Even if you don't restructure this, you could remove the repeated definition of "ResultCodeType". Section 7.2.1.2, "clientTransId: Zero or one client transaction ID. This value is simply an echo of the client transaction ID" - It would be clearer to be make this a MUST. Section 7.2.5 - Given that you have these nice batch request/responses, why would you bother defining the individual request/response types? Instead of "", you would just have "" Given all the SOAP overhead, you can afford the extra characters, and it will save a lot of spec/code. This change is even backward-compatible with servers that implement batch requests. Section 11 - It would be nice to refer here to the authentication and authorization concerns discussed in Section 5 and Section 6. --001a11c261fc134aa7050c229abe Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I have reviewed these documents in preparation for IETF LC= .=C2=A0 Overall, I think they hang together OK, even if the use of XML and = SOAP does make me feel like I'm back in the 90s :)

I've requ= ested LC, but there are a few comments below that I would like you to consi= der along with other LC comments.

Overall, these specifications woul= d read better if they were not separated as they are, especially since ther= e doesn't seem to be any demand for non-SOAP transports.=C2=A0 But they= are intelligible separately, so I won't object to processing them as-i= s.

--Richard


=3D=3D=3D=3D=3D draft-ietf-drinks-spp-framew= ork-09 =3D=3D=3D=3D=3D

** TODO: See RFC 5486 for use cases

Se= ction 1, "for data distribution to SSP" - Expand "SSP"<= br>
Section 1, "SED is typically used" - Expand "SED"= ;

Section 2 - It would be helpful to define "Session Establishm= ent Data", at least by reference.

Section 4 - Do we realistical= ly expect there to be other transports for this protocol?=C2=A0 If not, let= 's delete this section or move it to an appendix.

Section 4.11, = "provided in SPP Protocol over SOAP document" - Needs a normative= reference.

Section 5.1 - This section needs to define the semantis = for the cDate/mDate elements, as is done in Section 6.1 et al.=C2=A0 (I ass= ume these are "created" and "modified", respectively.)<= br>
Section 5.2 - It seems odd that these identifiers have defined conte= nts, but not a data structure.=C2=A0 Shouldn't these be moved from the = SOAP document to this section?

Section 5.3 - It seems like the "= ;conforming specification MUST define" incantation could be moved to t= he top.

Section 6.2, "When a Public Identifier is not member of= any Destination Group, it is intended to be associated with SED through th= e SED Records that are directly associated with the Public Identifier."= ;
Since the "dgName" illustration above shows the association = to a Destination Group, it would be helpful to note that these direct assoc= iations are provided using "sedRecRef" elements in individual ide= ntifiers.

Section 6.2 - In a related vein, why is "sedRecRef&qu= ot; not defined at the level of PubIdType, along with "dgName"?= =C2=A0 As is, it's only defined for TNs.=C2=A0 This seems to imply that= other identifier types must be part of a Destination Group.=C2=A0 Why is t= hat?

Section 6.2 - It seems like more needs to be said about NumberV= alType, especially as it is used for TN / RN / TNP.=C2=A0 For TN/RN, MUST i= t be the full E.164 number?=C2=A0 For TNP, is it a truncated E.164 number?<= br>
Section 6.2 - "Whether the Registry can accommodate the open nu= mber plan semantics is a matter of policy and is beyond the scope of this d= ocument."
No, it's not!=C2=A0 The semantics of TNR need to be c= lear regardless of the number plan.=C2=A0 Whether a given registry *accepts= * TNR objects for open number plans is up to the registry.=C2=A0 The semant= ics are not clear to me.=C2=A0 Could you provide an example of how TNR work= s in an an open-plan environment?


=3D=3D=3D=3D=3D draft-ietf-dri= nks-spp-protocol-over-soap-07 =3D=3D=3D=3D=3D

I did not review the W= SDL or examples in detail.

Section 5, "Clients and Servers MUST= use HTTP Digest Authentication" - Is there a reason that TLS-layer au= thentication (client certificates) is not acceptable?=C2=A0 Or other, stron= ger techniques that might come out of HTTPAUTH.

Section 7.1 - It see= ms like this section should move to -spp-framework.

Section 7.2 - Gi= ven that you're using namespaces, prepending "sppp" to all th= e element names here seems wasteful.=C2=A0 Instead of "<urn:spppAdd= Request>", just use xmlns:sppp=3D"..." and "<sppp= :addRequest>".

Section 7.2 - It would save some schema/writi= ng if you pulled out a few common attributes of the request and response ob= jects (clientTransId, minorVer; clientTransId, serverTransId, overallResult= , detailResult).=C2=A0 These would also be good candidates for things to pu= t in the SOAP header.=C2=A0 Even if you don't restructure this, you cou= ld remove the repeated definition of "ResultCodeType".

Sec= tion 7.2.1.2, "clientTransId: Zero or one client transaction ID.=C2=A0= This value is simply an echo of the client transaction ID" - It would= be clearer to be make this a MUST.

Section 7.2.5 - Given that you h= ave these nice batch request/responses, why would you bother defining the i= ndividual request/response types?=C2=A0 Instead of "<spppAddRequest= >", you would just have "<spppBatchRequest><addObj>= ;</spppBatchRequest>"=C2=A0 Given all the SOAP overhead, you can= afford the extra characters, and it will save a lot of spec/code.=C2=A0 Th= is change is even backward-compatible with servers that implement batch req= uests.

Section 11 - It would be nice to refer here to the authentica= tion and authorization concerns discussed in Section 5 and Section 6.
--001a11c261fc134aa7050c229abe-- From nobody Mon Jan 19 08:03:06 2015 Return-Path: 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 6E7F91ACD18 for ; Thu, 8 Jan 2015 03:45:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=0.001] 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 IbxM_JmiTFN8; Thu, 8 Jan 2015 03:45:25 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0857F1A0368; Thu, 8 Jan 2015 03:45:25 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: drinks@ietf.org, drinks-chairs@tools.ietf.org, alexander.mayrhofer@enum.at, draft-ietf-drinks-spp-framework.all@tools.ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.10.0.p6 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150108114525.6009.7368.idtracker@ietfa.amsl.com> Date: Thu, 08 Jan 2015 03:45:25 -0800 From: IETF Secretariat Archived-At: X-Mailman-Approved-At: Mon, 19 Jan 2015 08:03:04 -0800 Subject: [drinks] ID Tracker State Update Notice: X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.15 List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2015 11:45:26 -0000 IESG state changed to Last Call Requested from Publication Requested ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-drinks-spp-framework/ From nobody Mon Jan 19 08:03:07 2015 Return-Path: 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 103B71A89D3 for ; Thu, 8 Jan 2015 03:45:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=0.001] 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 z4FSdXT24RLd; Thu, 8 Jan 2015 03:45:47 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C4EC81A0368; Thu, 8 Jan 2015 03:45:47 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: drinks@ietf.org, drinks-chairs@tools.ietf.org, syed.ali@neustar.biz, draft-ietf-drinks-spp-protocol-over-soap.all@tools.ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.10.0.p6 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150108114547.4523.95366.idtracker@ietfa.amsl.com> Date: Thu, 08 Jan 2015 03:45:47 -0800 From: IETF Secretariat Archived-At: X-Mailman-Approved-At: Mon, 19 Jan 2015 08:03:04 -0800 Subject: [drinks] ID Tracker State Update Notice: X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.15 List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2015 11:45:49 -0000 IESG state changed to Last Call Requested from Publication Requested ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-drinks-spp-protocol-over-soap/ From nobody Mon Jan 19 08:03:09 2015 Return-Path: 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 D677D1A3BA0; Thu, 8 Jan 2015 06:09:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 d1ixzvwhC8OZ; Thu, 8 Jan 2015 06:09:10 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A7951A0231; Thu, 8 Jan 2015 06:09:10 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 5.10.0.p6 Auto-Submitted: auto-generated Precedence: bulk Sender: Message-ID: <20150108140910.22746.71003.idtracker@ietfa.amsl.com> Date: Thu, 08 Jan 2015 06:09:10 -0800 Archived-At: X-Mailman-Approved-At: Mon, 19 Jan 2015 08:03:04 -0800 Cc: drinks@ietf.org Subject: [drinks] Last Call: (Session Peering Provisioning Framework (SPPF)) to Proposed Standard X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.15 Reply-To: ietf@ietf.org List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2015 14:09:13 -0000 The IESG has received a request from the Data for Reachability of Inter/tra-NetworK SIP WG (drinks) to consider the following document: - 'Session Peering Provisioning Framework (SPPF)' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2015-01-22. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document specifies the data model and the overall structure for a framework to provision session establishment data into Session Data Registries and SIP Service Provider data stores. The framework is called the Session Peering Provisioning Framework (SPPF). The provisioned data is typically used by network elements for session establishment. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-drinks-spp-framework/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-drinks-spp-framework/ballot/ No IPR declarations have been submitted directly on this I-D. From nobody Mon Jan 19 08:03:11 2015 Return-Path: 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 EB4B11A6F11 for ; Thu, 8 Jan 2015 06:09:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 xELYfTAqZvfS; Thu, 8 Jan 2015 06:09:16 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 29FC51A0231; Thu, 8 Jan 2015 06:09:13 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: drinks@ietf.org, drinks-chairs@tools.ietf.org, alexander.mayrhofer@enum.at, draft-ietf-drinks-spp-framework.all@tools.ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.10.0.p6 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150108140913.22746.64016.idtracker@ietfa.amsl.com> Date: Thu, 08 Jan 2015 06:09:13 -0800 From: IETF Secretariat Archived-At: X-Mailman-Approved-At: Mon, 19 Jan 2015 08:03:04 -0800 Subject: [drinks] ID Tracker State Update Notice: X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.15 List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2015 14:09:20 -0000 Last call has been made for draft-ietf-drinks-spp-framework and state has been changed to In Last Call ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-drinks-spp-framework/ From nobody Mon Jan 19 08:03:12 2015 Return-Path: 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 898EA1A6F33; Thu, 8 Jan 2015 06:10:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 boPItMn42tOV; Thu, 8 Jan 2015 06:10:43 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C1A531A870C; Thu, 8 Jan 2015 06:10:04 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 5.10.0.p6 Auto-Submitted: auto-generated Precedence: bulk Sender: Message-ID: <20150108141004.20013.11484.idtracker@ietfa.amsl.com> Date: Thu, 08 Jan 2015 06:10:04 -0800 Archived-At: X-Mailman-Approved-At: Mon, 19 Jan 2015 08:03:04 -0800 Cc: drinks@ietf.org Subject: [drinks] Last Call: (Session Peering Provisioning (SPP) Protocol over SOAP) to Proposed Standard X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.15 Reply-To: ietf@ietf.org List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2015 14:10:46 -0000 The IESG has received a request from the Data for Reachability of Inter/tra-NetworK SIP WG (drinks) to consider the following document: - 'Session Peering Provisioning (SPP) Protocol over SOAP' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2015-01-22. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract The Session Peering Provisioning Framework (SPPF) specifies the data model and the overall structure to provision session establishment data into Session Data Registries and SIP Service Provider data stores. To utilize this framework one needs a transport protocol. Given that Simple Object Access Protocol (SOAP) is currently widely used for messaging between elements of such provisioning systems, this document specifies the usage of SOAP (via HTTPS) as the transport protocol for SPPF. The benefits include leveraging prevalent expertise, and a higher probability that existing provisioning systems will be able to easily migrate to using an SPPF based protocol. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-drinks-spp-protocol-over-soap/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-drinks-spp-protocol-over-soap/ballot/ No IPR declarations have been submitted directly on this I-D. From nobody Mon Jan 19 08:03:15 2015 Return-Path: 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 509351A6F01 for ; Thu, 8 Jan 2015 06:11:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 b1abhRh1HLDy; Thu, 8 Jan 2015 06:10:55 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C7FB91A89B1; Thu, 8 Jan 2015 06:10:07 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: drinks@ietf.org, drinks-chairs@tools.ietf.org, syed.ali@neustar.biz, draft-ietf-drinks-spp-protocol-over-soap.all@tools.ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.10.0.p6 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150108141007.20013.28542.idtracker@ietfa.amsl.com> Date: Thu, 08 Jan 2015 06:10:07 -0800 From: IETF Secretariat Archived-At: X-Mailman-Approved-At: Mon, 19 Jan 2015 08:03:04 -0800 Subject: [drinks] ID Tracker State Update Notice: X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.15 List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2015 14:11:13 -0000 Last call has been made for draft-ietf-drinks-spp-protocol-over-soap and state has been changed to In Last Call ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-drinks-spp-protocol-over-soap/ From nobody Mon Jan 19 08:03:17 2015 Return-Path: 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 A7FC21AD36F for ; Wed, 14 Jan 2015 12:05:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=0.001] 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 ca3exzgzSvHt; Wed, 14 Jan 2015 12:05:33 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DBCCE1AD377; Wed, 14 Jan 2015 12:05:15 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: drinks@ietf.org, drinks-chairs@tools.ietf.org, syed.ali@neustar.biz, draft-ietf-drinks-spp-protocol-over-soap.all@tools.ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.10.0.p8 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150114200515.11568.75425.idtracker@ietfa.amsl.com> Date: Wed, 14 Jan 2015 12:05:15 -0800 From: IETF Secretariat Archived-At: X-Mailman-Approved-At: Mon, 19 Jan 2015 08:03:04 -0800 Subject: [drinks] ID Tracker State Update Notice: X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.15 List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2015 20:05:36 -0000 IANA review state changed to IANA - Not OK ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-drinks-spp-protocol-over-soap/ From nobody Mon Jan 19 08:03:19 2015 Return-Path: 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" In-Reply-To: References: Message-ID: 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 From nobody Mon Jan 19 08:12:41 2015 Return-Path: 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 E73521B2B41 for ; Mon, 19 Jan 2015 08:12:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.842 X-Spam-Level: X-Spam-Status: No, score=-3.842 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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 YGtrjSDZ3wNN for ; Mon, 19 Jan 2015 08:12:36 -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 EEAAA1B2ADB for ; Mon, 19 Jan 2015 08:09:24 -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 ; Mon, 19 Jan 2015 17:09:15 +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; Mon, 19 Jan 2015 17:09:12 +0100 From: Alexander Mayrhofer To: "drinks@ietf.org" Thread-Topic: FYI... drafts progressing Thread-Index: AdA0AbuI7VEjvK3eQ1ie/6SYoG8Jdw== Date: Mon, 19 Jan 2015 16:09:11 +0000 Message-ID: <19F54F2956911544A32543B8A9BDE07546723B38@NICS-EXCH2.sbg.nic.at> 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="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-XWALL-BCKS: auto Archived-At: Subject: [drinks] FYI... drafts progressing X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2015 16:12:38 -0000 All, you might have seen that our two remaining drafts have progressed further,= and are now in IETF-wide last call (which lasts until January 22). So far,= i'm not aware of any LC comments. There were some comments from the Expert reviewing the IANA XML namespace U= RN registrations, but those don't hold up the process (The registration pro= cess with IANA will proceed). Alex From nobody Mon Jan 26 03:35:17 2015 Return-Path: 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 952491A88AD for ; Mon, 26 Jan 2015 03:35:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.793 X-Spam-Level: X-Spam-Status: No, score=-0.793 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, LOCALPART_IN_SUBJECT=1.107, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=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 yzpY4bFRhFR6 for ; Mon, 26 Jan 2015 03:35:15 -0800 (PST) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43D761A026F for ; Mon, 26 Jan 2015 03:35:15 -0800 (PST) Received: from [192.168.1.26] ([217.91.35.233]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0LjaEi-1XirAR1oaG-00baiK; Mon, 26 Jan 2015 12:34:59 +0100 Message-ID: <54C6265F.9020800@gmx.de> Date: Mon, 26 Jan 2015 12:34:55 +0100 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: draft-ietf-drinks-spp-framework@tools.ietf.org, drinks@ietf.org Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:k0jruf81kWsvggbXbh9M56Uk7/jX96NO0u+uurOKgezSmIgugf5 ZkECPKe51Mcluu4VroGZre6LGJf2eB5jaiACRDQGoqGLHX3dbNu4rWskBzUzW8yq6FO1FC/ 8R2uMY3Lrcnly5sKtJp92pxXnGem8m/UwSN9Da+xHGXPqF2UGdR9REGBidztM6Qmo2nfbgV Tpzk12a5nAdDxLS2wb8og== X-UI-Out-Filterresults: notjunk:1; Archived-At: Subject: [drinks] draft-ietf-drinks-spp-framework: XML related feedback X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jan 2015 11:35:16 -0000 Hi there, below some XML related feedback, applying to : 1) I'm not sure it's a good idea to repeat some specific XML related information from the XML spec, such as about case-sensitivity; if people can understand XML schema, they don't need this. 2) "All SPPF elements are defined in the namespaces in the IANA Considerations section and in the Formal Framework Specification section of this document." - which makes the IANA considerations section a normative part of the spec. Bad idea. Please state the actual namespace name where it belongs (where the XML vocab is defined). Best regards, Julian From nobody Wed Jan 28 08:17:20 2015 Return-Path: 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 2CE071A0092 for ; Tue, 20 Jan 2015 15:06:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 yd0-xleKxLqp; Tue, 20 Jan 2015 15:06:15 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 92AFE1A0079; Tue, 20 Jan 2015 15:06:14 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: drinks@ietf.org, drinks-chairs@tools.ietf.org, alexander.mayrhofer@enum.at, draft-ietf-drinks-spp-framework.all@tools.ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.10.0.p8 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150120230614.12183.98705.idtracker@ietfa.amsl.com> Date: Tue, 20 Jan 2015 15:06:14 -0800 From: IETF Secretariat Archived-At: X-Mailman-Approved-At: Wed, 28 Jan 2015 08:17:15 -0800 Subject: [drinks] ID Tracker State Update Notice: X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.15 List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2015 23:06:17 -0000 IANA review state changed to IANA - Not OK ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-drinks-spp-framework/ From nobody Wed Jan 28 08:17:22 2015 Return-Path: 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 EAE791A007A; Tue, 20 Jan 2015 15:04:30 -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 Be2a7GQZitXK; Tue, 20 Jan 2015 15:04:28 -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 1C31C1A0067; Tue, 20 Jan 2015 15:04:28 -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 t0KN4RTI025894; Tue, 20 Jan 2015 23:04:27 GMT Received: by request3.lax.icann.org (Postfix, from userid 48) id AF434C21465; Tue, 20 Jan 2015 23:04:27 +0000 (UTC) RT-Owner: pearl.liang From: "Pearl Liang via RT" In-Reply-To: <20150108140910.22746.6448.idtracker@ietfa.amsl.com> References: <20150108140910.22746.6448.idtracker@ietfa.amsl.com> Message-ID: X-RT-Loop-Prevention: IANA X-RT-Ticket: IANA #802710 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: Tue, 20 Jan 2015 23:04:27 +0000 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Archived-At: X-Mailman-Approved-At: Wed, 28 Jan 2015 08:17:16 -0800 Cc: drinks@ietf.org, drinks-chairs@tools.ietf.org, draft-ietf-drinks-spp-framework.all@tools.ietf.org Subject: [drinks] [IANA #802710] Last Call: (Session Peering Provisioning Framework (SPPF)) to Proposed Standard X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.15 Reply-To: drafts-lastcall@iana.org List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2015 23:04:31 -0000 (BEGIN IANA LAST CALL COMMENTS) IESG/Authors/WG Chairs: IANA has reviewed draft-ietf-drinks-spp-framework-09. Authors should review the comments and/or questions below. Please report any inaccuracies and respond to any questions as soon as possible. We received the following comments/questions from the IANA's reviewer: IANA has questions about the requested IANA actions made by the authors in the IANA Considerations section of this document. On approval of this document, IANA understands that there are three actions which IANA must complete. 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 ] 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. 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 ] 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. 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. 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? IANA understands that these three actions are the only ones required to be completed upon approval of this document. Note: The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed. Thanks, Pearl Liang ICANN (END IANA LAST CALL COMMENTS) On Thu Jan 08 14:09:38 2015, iesg-secretary@ietf.org wrote: > > The IESG has received a request from the Data for Reachability of > Inter/tra-NetworK SIP WG (drinks) to consider the following document: > - 'Session Peering Provisioning Framework (SPPF)' > as Proposed Standard > > The IESG plans to make a decision in the next few weeks, and solicits > final comments on this action. Please send substantive comments to the > ietf@ietf.org mailing lists by 2015-01-22. Exceptionally, comments may be > sent to iesg@ietf.org instead. In either case, please retain the > beginning of the Subject line to allow automated sorting. > > Abstract > > > This document specifies the data model and the overall structure for > a framework to provision session establishment data into Session Data > Registries and SIP Service Provider data stores. The framework is > called the Session Peering Provisioning Framework (SPPF). The > provisioned data is typically used by network elements for session > establishment. > > > > > The file can be obtained via > http://datatracker.ietf.org/doc/draft-ietf-drinks-spp-framework/ > > IESG discussion can be tracked via > http://datatracker.ietf.org/doc/draft-ietf-drinks-spp-framework/ballot/ > > > No IPR declarations have been submitted directly on this I-D. > > From nobody Wed Jan 28 08:17:24 2015 Return-Path: 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 ECF031A8733; Thu, 22 Jan 2015 00:09:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 Ny26HbR_g__L; Thu, 22 Jan 2015 00:08:59 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A17E1A0271; Thu, 22 Jan 2015 00:08:59 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: DraftTracker Mail System To: iesg@ietf.org, drinks@ietf.org, drinks-chairs@tools.ietf.org, alexander.mayrhofer@enum.at, draft-ietf-drinks-spp-framework.all@tools.ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.10.0.p8 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150122080859.8378.30309.idtracker@ietfa.amsl.com> Date: Thu, 22 Jan 2015 00:08:59 -0800 Archived-At: X-Mailman-Approved-At: Wed, 28 Jan 2015 08:17:16 -0800 Cc: iesg-secretary@ietf.org Subject: [drinks] Last Call Expired: X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.15 List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2015 08:09:01 -0000 Please DO NOT reply to this email. I-D: ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-drinks-spp-framework/ IETF Last Call has ended, and the state has been changed to Waiting for AD Go-Ahead. From nobody Wed Jan 28 08:17:37 2015 Return-Path: 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 47C1D1A0278; Thu, 22 Jan 2015 00:09:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 Eo-VlnJHo2T7; Thu, 22 Jan 2015 00:09:01 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 46C211A0363; Thu, 22 Jan 2015 00:09:00 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: DraftTracker Mail System To: iesg@ietf.org, drinks@ietf.org, drinks-chairs@tools.ietf.org, syed.ali@neustar.biz, draft-ietf-drinks-spp-protocol-over-soap.all@tools.ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.10.0.p8 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150122080900.8378.32744.idtracker@ietfa.amsl.com> Date: Thu, 22 Jan 2015 00:09:00 -0800 Archived-At: X-Mailman-Approved-At: Wed, 28 Jan 2015 08:17:16 -0800 Cc: iesg-secretary@ietf.org Subject: [drinks] Last Call Expired: X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.15 List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2015 08:09:02 -0000 Please DO NOT reply to this email. I-D: ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-drinks-spp-protocol-over-soap/ IETF Last Call has ended, and the state has been changed to Waiting for AD Go-Ahead. From nobody Wed Jan 28 08:17:38 2015 Return-Path: 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 9FA901A1ACA for ; Mon, 26 Jan 2015 13:09:57 -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 nz1aN57qm1-u for ; Mon, 26 Jan 2015 13:09:49 -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 A6FEA1A6EF4 for ; Mon, 26 Jan 2015 13:09:49 -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 t0QL9nrU016761; Mon, 26 Jan 2015 21:09:49 GMT Received: by request3.lax.icann.org (Postfix, from userid 48) id 07C93C203EA; Mon, 26 Jan 2015 21:09:49 +0000 (UTC) RT-Owner: pearl.liang From: "Pearl Liang via RT" In-Reply-To: References: Message-ID: X-RT-Loop-Prevention: IANA X-RT-Ticket: IANA #804800 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, 26 Jan 2015 21:09:48 +0000 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Archived-At: X-Mailman-Approved-At: Wed, 28 Jan 2015 08:17:16 -0800 Cc: drinks@ietf.org, drinks-chairs@tools.ietf.org, draft-ietf-drinks-spp-framework.all@tools.ietf.org Subject: [drinks] [IANA #804800] Expert review for draft-ietf-drinks-spp-framework-09 X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.15 Reply-To: drafts-expert-review@iana.org List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jan 2015 21:09:57 -0000 Hello, Just FYI, this document requests two new URI assignments, ns and schema, be registered in the http://www.iana.org/assignments/xml-registry. Upon review, the experts have approved this one. Thanks, ~pl