[drinks] FW: I-D Action: draft-ietf-drinks-spp-framework-01.txt

"Bhatia, Vikas" <vbhatia@tnsi.com> Mon, 12 March 2012 18:43 UTC

Return-Path: <vbhatia@tnsi.com>
X-Original-To: drinks@ietfa.amsl.com
Delivered-To: drinks@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C21621F8976 for <drinks@ietfa.amsl.com>; Mon, 12 Mar 2012 11:43:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[AWL=0.503, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QDbkawNvN-kZ for <drinks@ietfa.amsl.com>; Mon, 12 Mar 2012 11:43:56 -0700 (PDT)
Received: from relayus.tnsi.com (relayus.tnsi.com [208.224.248.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0246B21F8945 for <drinks@ietf.org>; Mon, 12 Mar 2012 11:43:55 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap4EAJFDXk+sEQfn/2dsb2JhbAA5CrZdggkBAQEEAQEBaAMXBgEIEQQBASguCxQHAQEFBAEEEwgBBYgHvAuKLAmFaWMEpW+Cf4FA
X-IronPort-AV: E=Sophos;i="4.73,572,1325462400"; d="scan'208";a="983550"
Received: from mail-hub-na.win2k.corp.tnsi.com ([172.17.7.231]) by relayus.tnsi.com with ESMTP/TLS/RC4-MD5; 12 Mar 2012 18:43:54 +0000
Received: from TNS-MAIL-NA.win2k.corp.tnsi.com ([172.17.7.214]) by MAIL-HUB-NA.win2k.corp.tnsi.com ([172.17.7.231]) with mapi; Mon, 12 Mar 2012 14:43:54 -0400
From: "Bhatia, Vikas" <vbhatia@tnsi.com>
To: "drinks@ietf.org" <drinks@ietf.org>
Date: Mon, 12 Mar 2012 14:43:52 -0400
Thread-Topic: [drinks] I-D Action: draft-ietf-drinks-spp-framework-01.txt
Thread-Index: Ac0AfK7ViWWYCL49QS2wkInJxZDSXwAALqVg
Message-ID: <B4254E341B54864B92D28BC2138A9DC303145DBA10@TNS-MAIL-NA.win2k.corp.tnsi.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/mixed; boundary="_002_B4254E341B54864B92D28BC2138A9DC303145DBA10TNSMAILNAwin2_"
MIME-Version: 1.0
Subject: [drinks] FW: I-D Action: draft-ietf-drinks-spp-framework-01.txt
X-BeenThere: drinks@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 12 Mar 2012 18:43:57 -0000

Hi All,

New versions of the draft documents for the SPP Framework and SPP Protocol over SOAP have been submitted today.

Following are the set of changes to the documents. Action Item (AI) numbers are listed (wherever applicable). These AIs were identified in the last Interim and subsequent weekly design meetings.

===Start - List of Changes===

SPP Framework document
----------------------
AI-1/ Addressed data model diagram inconsistencies - Diagram has been significantly revamped per the discussions and comments
        David's comments:
        * remove extensions
        * add missing arrows (TN and RR)
        * add [0..n] on relevant arrows

        Other changes:
        * Added the new URI type of Public Identifier (refer AI-3 below)
        * Added Egress Route into the diagram

AI-3/ Non-numeric PI (URIPubIdType) and related text has been added.
AI-5/ Removed priority from RteRec base type
AI-6/ Also added "isInSvc" flag on RteRec base type
AI-7/ Move up "ttl" field to base RteRec type

SPP Protocol over SOAP document
--------------------------------
AI-13a In the response, returned an error with the maximum (Response code 2001).
AI-13c/ Removed definition of transaction id type as it is already listed in framework document.
AI-14/ Expanded element name "dtlResult" to "detailResult" to make it consistent with element "overallResult".
AI-15/ Defined a type "MsgType" to add max length to result message text.
AI-19/ Clarifed attributes of ObjKeyType on how they identify uniqueness and added an example as well.

-Corrected the numbering of Result Codes (like some result codes were starting with 2103 instead of 2100 etc).
-Introduced an enumeration "ResultCodeValType" to define all the result codes. This ensures that server can only send one of the result codes defined in the schema. In previous version(s), it was loosely defined to take in any integer.


General
-------
-Corrected some editorial nits (spell checks, consistent use of terminology etc.).
-Moved "ObjKeyTypeEnum" from framework to protocol document (thought protocol document was an appropriate places for it since it is only used in the SPP Protocol over SOAP schema).
-A-11/ Review Security Cons section (All) - The change I did was to add the text proposed by Scott in the SPP Protocol over SOAP document (and added Scott's name to acknowledgements).

===End - List of Changes===

Thanks,
Vikas

-----Original Message-----
From: drinks-bounces@ietf.org [mailto:drinks-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
Sent: Monday, March 12, 2012 2:19 PM
To: i-d-announce@ietf.org
Cc: drinks@ietf.org
Subject: [drinks] I-D Action: draft-ietf-drinks-spp-framework-01.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Data for Reachability of Inter/tra-NetworK SIP Working Group of the IETF.

        Title           : Session Peering Provisioning Framework (SPPF)
        Author(s)       : Kenneth Cartwright
                          Syed Wasim Ali
                          Alexander Mayrhofer
                          Vikas Bhatia
        Filename        : draft-ietf-drinks-spp-framework-01.txt
        Pages           : 59
        Date            : 2012-03-12

   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
   peering.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-drinks-spp-framework-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-drinks-spp-framework-01.txt

_______________________________________________
drinks mailing list
drinks@ietf.org
https://www.ietf.org/mailman/listinfo/drinks

This e-mail message is for the sole use of the intended recipient(s)and may
contain confidential and privileged information of Transaction Network Services.
Any unauthorised review, use, disclosure or distribution is prohibited. If you
are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.

--- Begin Message ---
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Data for Reachability of Inter/tra-NetworK SIP Working Group of the IETF.

	Title           : Session Peering Provisioning (SPP) Protocol over SOAP
	Author(s)       : Kenneth Cartwright
                          Vikas Bhatia
	Filename        : draft-ietf-drinks-spp-protocol-over-soap-01.txt
	Pages           : 91
	Date            : 2012-03-12

   The Session Peering Provisioning Framework (SPPF) is an XML framework
   that exists to enable the provisioning of session establishment data
   into Session Data Registries or SIP Service Provider data stores.
   Sending XML data structures over Simple Object Access Protocol (SOAP)
   and HTTP(s) is a widely used, de-facto standard for messaging between
   elements of provisioning systems.  Therefore the combination of SOAP
   and HTTP(s) as a transport protocol for SPPF is a natural fit.  The
   obvious benefits include leveraging existing industry expertise,
   leveraging existing standards, and a higher probability that existing
   provisioning systems can be more easily integrated with this
   protocol.  This document describes the specification for transporting
   SPPF XML structures over SOAP and HTTP(s).


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-drinks-spp-protocol-over-soap-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-drinks-spp-protocol-over-soap-01.txt

_______________________________________________
drinks mailing list
drinks@ietf.org
https://www.ietf.org/mailman/listinfo/drinks
--- End Message ---