--- 1/draft-ietf-drinks-spp-protocol-over-soap-04.txt 2013-10-21 13:15:21.014296929 -0700 +++ 2/draft-ietf-drinks-spp-protocol-over-soap-05.txt 2013-10-21 13:15:21.142300026 -0700 @@ -1,22 +1,22 @@ DRINKS K. Cartwright Internet-Draft V. Bhatia Intended status: Standards Track TNS -Expires: January 13, 2014 J-F. Mule +Expires: April 24, 2014 J-F. Mule CableLabs A. Mayrhofer enum.at GmbH - July 12, 2013 + October 21, 2013 Session Peering Provisioning (SPP) Protocol over SOAP - draft-ietf-drinks-spp-protocol-over-soap-04 + draft-ietf-drinks-spp-protocol-over-soap-05 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 @@ -33,21 +33,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on January 13, 2014. + This Internet-Draft will expire on April 24, 2014. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -3347,44 +3347,49 @@ restrict unauthenticated client access to servers. In conjunction with the above, it is important that SPP Protocol over SOAP implementations implement an authorization model that considers the source of each query or update request and determines whether it is reasonable to authorize that source to perform that specific query or update. 12. IANA Considerations - This document uses URNs to describe XML Namespaces and XML Schemas - conforming to a registry mechanism described in [RFC3688]. + This document uses URNs to describe XML Namespaces and XML Schemas. + According to [RFC3688], IANA is requested to perform the following + URN assignment: - URN assignment requested is: urn:ietf:params:xml:ns:sppf:soap:1 + URN: urn:ietf:params:xml:ns:sppf:soap:1 + + Registrant Contact: IESG + + XML: See Section 9 of [THISDOCUMENT] 13. Acknowledgements This document is a result of various discussions held with the IETF DRINKS working group, specifically the protocol design team, with contributions from the following individuals, in alphabetical order: Alexander Mayrhofer, David Schwartz, Deborah A Guyton, Jean-Francois Mule Kenneth Cartwright, Lisa Dusseault, Manjul Maharishi, Mickael Marrache, Otmar Lendl, Peter Saint-Andre, Richard Shockey, Samuel Melloul, Scott Hollenbeck, Sumanth Channabasappa, Syed Ali, and Vikas Bhatia . 14. References 14.1. Normative References [I-D.draft-ietf-drinks-spp-framework] Cartwright, K., Bhatia, V., Ali, S., and D. Schwartz, "Session Peering Provisioning Framework ", draft-ietf- - drinks-spp-framework-04 (work in progress), October 2012. + drinks-spp-framework-06 (work in progress), October 2013. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. [RFC2617] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., Leach, P., Luotonen, A., and L. Stewart, "HTTP