draft-ietf-drinks-spp-protocol-over-soap-04.txt   draft-ietf-drinks-spp-protocol-over-soap-05.txt 
DRINKS K. Cartwright DRINKS K. Cartwright
Internet-Draft V. Bhatia Internet-Draft V. Bhatia
Intended status: Standards Track TNS Intended status: Standards Track TNS
Expires: January 13, 2014 J-F. Mule Expires: April 24, 2014 J-F. Mule
CableLabs CableLabs
A. Mayrhofer A. Mayrhofer
enum.at GmbH enum.at GmbH
July 12, 2013 October 21, 2013
Session Peering Provisioning (SPP) Protocol over SOAP Session Peering Provisioning (SPP) Protocol over SOAP
draft-ietf-drinks-spp-protocol-over-soap-04 draft-ietf-drinks-spp-protocol-over-soap-05
Abstract Abstract
The Session Peering Provisioning Framework (SPPF) specifies the data The Session Peering Provisioning Framework (SPPF) specifies the data
model and the overall structure to provision session establishment model and the overall structure to provision session establishment
data into Session Data Registries and SIP Service Provider data data into Session Data Registries and SIP Service Provider data
stores. To utilize this framework one needs a transport protocol. stores. To utilize this framework one needs a transport protocol.
Given that Simple Object Access Protocol (SOAP) is currently widely Given that Simple Object Access Protocol (SOAP) is currently widely
used for messaging between elements of such provisioning systems, used for messaging between elements of such provisioning systems,
this document specifies the usage of SOAP (via HTTPS) as the this document specifies the usage of SOAP (via HTTPS) as the
skipping to change at page 1, line 44 skipping to change at page 1, line 44
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." 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 Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 75, line 36 skipping to change at page 75, line 36
restrict unauthenticated client access to servers. restrict unauthenticated client access to servers.
In conjunction with the above, it is important that SPP Protocol over In conjunction with the above, it is important that SPP Protocol over
SOAP implementations implement an authorization model that considers SOAP implementations implement an authorization model that considers
the source of each query or update request and determines whether it the source of each query or update request and determines whether it
is reasonable to authorize that source to perform that specific query is reasonable to authorize that source to perform that specific query
or update. or update.
12. IANA Considerations 12. IANA Considerations
This document uses URNs to describe XML Namespaces and XML Schemas This document uses URNs to describe XML Namespaces and XML Schemas.
conforming to a registry mechanism described in [RFC3688]. 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 13. Acknowledgements
This document is a result of various discussions held with the IETF This document is a result of various discussions held with the IETF
DRINKS working group, specifically the protocol design team, with DRINKS working group, specifically the protocol design team, with
contributions from the following individuals, in alphabetical order: contributions from the following individuals, in alphabetical order:
Alexander Mayrhofer, David Schwartz, Deborah A Guyton, Jean-Francois Alexander Mayrhofer, David Schwartz, Deborah A Guyton, Jean-Francois
Mule Kenneth Cartwright, Lisa Dusseault, Manjul Maharishi, Mickael Mule Kenneth Cartwright, Lisa Dusseault, Manjul Maharishi, Mickael
Marrache, Otmar Lendl, Peter Saint-Andre, Richard Shockey, Samuel Marrache, Otmar Lendl, Peter Saint-Andre, Richard Shockey, Samuel
Melloul, Scott Hollenbeck, Sumanth Channabasappa, Syed Ali, and Vikas Melloul, Scott Hollenbeck, Sumanth Channabasappa, Syed Ali, and Vikas
Bhatia . Bhatia .
14. References 14. References
14.1. Normative References 14.1. Normative References
[I-D.draft-ietf-drinks-spp-framework] [I-D.draft-ietf-drinks-spp-framework]
Cartwright, K., Bhatia, V., Ali, S., and D. Schwartz, Cartwright, K., Bhatia, V., Ali, S., and D. Schwartz,
"Session Peering Provisioning Framework ", draft-ietf- "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 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[RFC2617] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., [RFC2617] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S.,
Leach, P., Luotonen, A., and L. Stewart, "HTTP Leach, P., Luotonen, A., and L. Stewart, "HTTP
 End of changes. 7 change blocks. 
8 lines changed or deleted 13 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/