Subject: [drinks] FW: New Version Notification for draft-ietf-drinks-sppp-over-soap-06.txt

From: "Cartwright, Ken" <[email-masked]>
Date: Mon, 31 Oct 2011 17:25:21 -0400

Vikas and I have just completed the initial cut at the version of this draft that specifically makes it amenable to REST.  We will continue to work on it in the coming weeks.

Ken

-----Original Message-----
From: [email-masked] [mailto:[email-masked]]
Sent: Monday, October 31, 2011 5:22 PM
To: Cartwright, Ken
Cc: Cartwright, Ken
Subject: New Version Notification for draft-ietf-drinks-sppp-over-soap-06.txt

A new version of I-D, draft-ietf-drinks-sppp-over-soap-06.txt has been successfully submitted by Kenneth Cartwright and posted to the IETF repository.

Filename:        draft-ietf-drinks-sppp-over-soap
Revision:        06
Title:           SPPP Over SOAP and HTTP
Creation date:   2011-10-31
WG ID:           drinks
Number of pages: 50

Abstract:
   The Session Peering Provisioning Protocol (SPPP) is an XML protocol
   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 for SPPP 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
   SPPP XML structures over SOAP and HTTP(s).

The IETF Secretariat

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.