draft-ietf-drinks-spp-framework-05.txt   draft-ietf-drinks-spp-framework-06.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 16, 2014 S. Ali Expires: April 24, 2014 S. Ali
NeuStar NeuStar
D. Schwartz D. Schwartz
XConnect XConnect
July 15, 2013 October 21, 2013
Session Peering Provisioning Framework (SPPF) Session Peering Provisioning Framework (SPPF)
draft-ietf-drinks-spp-framework-05 draft-ietf-drinks-spp-framework-06
Abstract Abstract
This document specifies the data model and the overall structure for This document specifies the data model and the overall structure for
a framework to provision session establishment data into Session Data a framework to provision session establishment data into Session Data
Registries and SIP Service Provider data stores. The framework is Registries and SIP Service Provider data stores. The framework is
called the Session Peering Provisioning Framework (SPPF). The called the Session Peering Provisioning Framework (SPPF). The
provisioned data is typically used by network elements for session provisioned data is typically used by network elements for session
establishment. establishment.
skipping to change at page 1, line 38 skipping to change at page 1, line 39
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 16, 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 3, line 17 skipping to change at page 3, line 17
9.2. Authorization . . . . . . . . . . . . . . . . . . . . . . 39 9.2. Authorization . . . . . . . . . . . . . . . . . . . . . . 39
9.3. Denial of Service . . . . . . . . . . . . . . . . . . . . 40 9.3. Denial of Service . . . . . . . . . . . . . . . . . . . . 40
9.3.1. DoS Issues Inherited from Transport Mechanism . . . . 40 9.3.1. DoS Issues Inherited from Transport Mechanism . . . . 40
9.3.2. DoS Issues Specific to SPPF . . . . . . . . . . . . . 41 9.3.2. DoS Issues Specific to SPPF . . . . . . . . . . . . . 41
9.4. Information Disclosure . . . . . . . . . . . . . . . . . 41 9.4. Information Disclosure . . . . . . . . . . . . . . . . . 41
9.5. Non Repudiation . . . . . . . . . . . . . . . . . . . . . 42 9.5. Non Repudiation . . . . . . . . . . . . . . . . . . . . . 42
9.6. Replay Attacks . . . . . . . . . . . . . . . . . . . . . 42 9.6. Replay Attacks . . . . . . . . . . . . . . . . . . . . . 42
9.7. Man in the Middle . . . . . . . . . . . . . . . . . . . . 42 9.7. Man in the Middle . . . . . . . . . . . . . . . . . . . . 42
10. Internationalization Considerations . . . . . . . . . . . . . 42 10. Internationalization Considerations . . . . . . . . . . . . . 42
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 43 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 43
11.1. URN Assignments . . . . . . . . . . . . . . . . . . . . 43
11.2. Organization Identifier Namespace Registry . . . . . . . 43
12. Formal Specification . . . . . . . . . . . . . . . . . . . . 43 12. Formal Specification . . . . . . . . . . . . . . . . . . . . 43
13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 51 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 52
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 52 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 52
14.1. Normative References . . . . . . . . . . . . . . . . . . 52 14.1. Normative References . . . . . . . . . . . . . . . . . . 52
14.2. Informative References . . . . . . . . . . . . . . . . . 52 14.2. Informative References . . . . . . . . . . . . . . . . . 53
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 54 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 54
1. Introduction 1. Introduction
Service providers and enterprises use routing databases known as Service providers and enterprises use routing databases known as
registries to make session routing decisions for Voice over IP, SMS registries to make session routing decisions for Voice over IP, SMS
and MMS traffic exchanges. This document is narrowly focused on the and MMS traffic exchanges. This document is narrowly focused on the
provisioning framework for these registries. This framework provisioning framework for these registries. This framework
prescribes a way for an entity to provision session-related data into prescribes a way for an entity to provision session-related data into
a Registry. The data being provisioned can be optionally shared with a Registry. The data being provisioned can be optionally shared with
skipping to change at page 43, line 7 skipping to change at page 43, line 7
Section 8.2. The use of time elements in the protocol is specified Section 8.2. The use of time elements in the protocol is specified
in Section 3.2. Where human-readable languages are used in the in Section 3.2. Where human-readable languages are used in the
protocol, those messages SHOULD be tagged according to [RFC5646], and protocol, those messages SHOULD be tagged according to [RFC5646], and
the transport protocol MUST support a respective mechanism to the transport protocol MUST support a respective mechanism to
transmit such tags together with those human-readable messages. If transmit such tags together with those human-readable messages. If
tags are absent, the language of the message defaults to "en" tags are absent, the language of the message defaults to "en"
(English). (English).
11. IANA Considerations 11. IANA Considerations
11.1. URN Assignments
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]. conforming to a Registry mechanism described in [RFC3688].
Two URI assignments are requested. Two URI assignments are requested.
Registration request for the SPPF XML namespace: Registration request for the SPPF XML namespace:
urn:ietf:params:xml:ns:sppf:base:1 urn:ietf:params:xml:ns:sppf:base:1
Registrant Contact: IESG Registrant Contact: IESG
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the XML schema: Registration request for the XML schema:
URI: urn:ietf:params:xml:schema:sppf:1 URI: urn:ietf:params:xml:schema:sppf:1
Registrant Contact: IESG Registrant Contact: IESG
XML: See the "Formal Specification" section of this document XML: See the "Formal Specification" section of this document
(Section 12). (Section 12).
IANA is requested to create a new SPPF Registry for Organization 11.2. Organization Identifier Namespace Registry
Identifiers that will indicate valid strings to be used for well-
known enterprise namespaces.
This document makes the following assignments for the OrgIdType
namespaces:
Namespace OrgIdType namespace string IANA is requested to create and maintain a Registry entitled "SPPF
---- ---------------------------- OrgIdType Namespaces". Strings used as OrgIdType Namespace
IANA Enterprise Numbers iana-en identifiers MUST conform to the following syntax in the Augmented
Backus-Naur Form (ABNF) [RFC5234]
namespace = ALPHA * (ALPHA/DIGIT/"-")
Assignments consist of the OrgIdType namespace string, and the
definition of the associated namespace. This document makes the
following initial assignment for the OrgIdType Namespaces:
OrgIdType namespace string Namespace
-------------------------- ---------
IANA Enterprise Numbers iana-en
Future assignments are to be made through the well known IANA Policy
"RFC Required" (see section 4.1 of [RFC5226])
12. Formal Specification 12. Formal Specification
This section provides the draft XML Schema Definition for SPPF This section provides the draft XML Schema Definition for SPPF
Protocol. Protocol.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema xmlns:sppfb="urn:ietf:params:xml:ns:sppf:base:1" <schema xmlns:sppfb="urn:ietf:params:xml:ns:sppf:base:1"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:ietf:params:xml:ns:sppf:base:1" targetNamespace="urn:ietf:params:xml:ns:sppf:base:1"
skipping to change at page 52, line 38 skipping to change at page 52, line 48
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, RFC Resource Identifier (URI): Generic Syntax", STD 66, RFC
3986, January 2005. 3986, January 2005.
[RFC4949] Shirey, R., "Internet Security Glossary, Version 2", RFC [RFC4949] Shirey, R., "Internet Security Glossary, Version 2", RFC
4949, August 2007. 4949, August 2007.
[RFC5067] Lind, S. and P. Pfautz, "Infrastructure ENUM [RFC5067] Lind, S. and P. Pfautz, "Infrastructure ENUM
Requirements", RFC 5067, November 2007. Requirements", RFC 5067, November 2007.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008.
14.2. Informative References 14.2. Informative References
[RFC2609] Guttman, E., Perkins, C., and J. Kempf, "Service Templates [RFC2609] Guttman, E., Perkins, C., and J. Kempf, "Service Templates
and Service: Schemes", RFC 2609, June 1999. and Service: Schemes", RFC 2609, June 1999.
[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.
[RFC2781] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO [RFC2781] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO
 End of changes. 12 change blocks. 
14 lines changed or deleted 36 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/