draft-ietf-drinks-spp-framework-04.txt   draft-ietf-drinks-spp-framework-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: August 29, 2013 S. Ali Expires: January 16, 2014 S. Ali
NeuStar NeuStar
D. Schwartz D. Schwartz
XConnect XConnect
February 25, 2013 July 15, 2013
Session Peering Provisioning Framework (SPPF) Session Peering Provisioning Framework (SPPF)
draft-ietf-drinks-spp-framework-04 draft-ietf-drinks-spp-framework-05
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.
Status of this Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 August 29, 2013. This Internet-Draft will expire on January 16, 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 8 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Framework High Level Design . . . . . . . . . . . . . . . . . 10 3. Framework High Level Design . . . . . . . . . . . . . . . . . 7
3.1. Framework Data Model . . . . . . . . . . . . . . . . . . . 10 3.1. Framework Data Model . . . . . . . . . . . . . . . . . . 7
3.2. Time Value . . . . . . . . . . . . . . . . . . . . . . . . 13 3.2. Time Value . . . . . . . . . . . . . . . . . . . . . . . 10
3.3. Extensibility . . . . . . . . . . . . . . . . . . . . . . 13 3.3. Extensibility . . . . . . . . . . . . . . . . . . . . . . 10
4. Transport Protocol Requirements . . . . . . . . . . . . . . . 14 4. Transport Protocol Requirements . . . . . . . . . . . . . . . 11
4.1. Connection Oriented . . . . . . . . . . . . . . . . . . . 14 4.1. Connection Oriented . . . . . . . . . . . . . . . . . . . 11
4.2. Request and Response Model . . . . . . . . . . . . . . . . 14 4.2. Request and Response Model . . . . . . . . . . . . . . . 11
4.3. Connection Lifetime . . . . . . . . . . . . . . . . . . . 14 4.3. Connection Lifetime . . . . . . . . . . . . . . . . . . . 11
4.4. Authentication . . . . . . . . . . . . . . . . . . . . . . 14 4.4. Authentication . . . . . . . . . . . . . . . . . . . . . 11
4.5. Authorization . . . . . . . . . . . . . . . . . . . . . . 15 4.5. Authorization . . . . . . . . . . . . . . . . . . . . . . 11
4.6. Confidentiality and Integrity . . . . . . . . . . . . . . 15 4.6. Confidentiality and Integrity . . . . . . . . . . . . . . 12
4.7. Near Real Time . . . . . . . . . . . . . . . . . . . . . . 15 4.7. Near Real Time . . . . . . . . . . . . . . . . . . . . . 12
4.8. Request and Response Sizes . . . . . . . . . . . . . . . . 15 4.8. Request and Response Sizes . . . . . . . . . . . . . . . 12
4.9. Request and Response Correlation . . . . . . . . . . . . . 15 4.9. Request and Response Correlation . . . . . . . . . . . . 12
4.10. Request Acknowledgement . . . . . . . . . . . . . . . . . 15 4.10. Request Acknowledgement . . . . . . . . . . . . . . . . . 12
4.11. Mandatory Transport . . . . . . . . . . . . . . . . . . . 16 4.11. Mandatory Transport . . . . . . . . . . . . . . . . . . . 13
5. Base Framework Data Structures and Response Codes . . . . . . 17 5. Base Framework Data Structures and Response Codes . . . . . . 13
5.1. Basic Object Type and Organization Identifiers . . . . . . 17 5.1. Basic Object Type and Organization Identifiers . . . . . 13
5.2. Various Object Key Types . . . . . . . . . . . . . . . . . 17 5.2. Various Object Key Types . . . . . . . . . . . . . . . . 13
5.2.1. Generic Object Key Type . . . . . . . . . . . . . . . 18 5.2.1. Generic Object Key Type . . . . . . . . . . . . . . . 14
5.2.2. Derived Object Key Types . . . . . . . . . . . . . . . 18 5.2.2. Derived Object Key Types . . . . . . . . . . . . . . 15
5.3. Response Message Types . . . . . . . . . . . . . . . . . . 20 5.3. Response Message Types . . . . . . . . . . . . . . . . . 16
6. Framework Data Model Objects . . . . . . . . . . . . . . . . . 23 6. Framework Data Model Objects . . . . . . . . . . . . . . . . 18
6.1. Destination Group . . . . . . . . . . . . . . . . . . . . 23 6.1. Destination Group . . . . . . . . . . . . . . . . . . . . 19
6.2. Public Identifier . . . . . . . . . . . . . . . . . . . . 24 6.2. Public Identifier . . . . . . . . . . . . . . . . . . . . 19
6.3. SED Group . . . . . . . . . . . . . . . . . . . . . . . . 29 6.3. SED Group . . . . . . . . . . . . . . . . . . . . . . . . 24
6.4. SED Record . . . . . . . . . . . . . . . . . . . . . . . . 33 6.4. SED Record . . . . . . . . . . . . . . . . . . . . . . . 28
6.5. SED Group Offer . . . . . . . . . . . . . . . . . . . . . 37 6.5. SED Group Offer . . . . . . . . . . . . . . . . . . . . . 32
6.6. Egress Route . . . . . . . . . . . . . . . . . . . . . . . 39 6.6. Egress Route . . . . . . . . . . . . . . . . . . . . . . 33
7. Framework Operations . . . . . . . . . . . . . . . . . . . . . 41 7. Framework Operations . . . . . . . . . . . . . . . . . . . . 35
7.1. Add Operation . . . . . . . . . . . . . . . . . . . . . . 41 7.1. Add Operation . . . . . . . . . . . . . . . . . . . . . . 35
7.2. Delete Operation . . . . . . . . . . . . . . . . . . . . . 41 7.2. Delete Operation . . . . . . . . . . . . . . . . . . . . 35
7.3. Get Operations . . . . . . . . . . . . . . . . . . . . . . 42 7.3. Get Operations . . . . . . . . . . . . . . . . . . . . . 36
7.4. Accept Operations . . . . . . . . . . . . . . . . . . . . 42 7.4. Accept Operations . . . . . . . . . . . . . . . . . . . . 37
7.5. Reject Operations . . . . . . . . . . . . . . . . . . . . 43 7.5. Reject Operations . . . . . . . . . . . . . . . . . . . . 37
7.6. Get Server Details Operation . . . . . . . . . . . . . . . 43 7.6. Get Server Details Operation . . . . . . . . . . . . . . 38
8. XML Considerations . . . . . . . . . . . . . . . . . . . . . . 45 8. XML Considerations . . . . . . . . . . . . . . . . . . . . . 38
8.1. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 45 8.1. Namespaces . . . . . . . . . . . . . . . . . . . . . . . 38
8.2. Versioning and Character Encoding . . . . . . . . . . . . 45 8.2. Versioning and Character Encoding . . . . . . . . . . . . 39
9. Security Considerations . . . . . . . . . . . . . . . . . . . 46 9. Security Considerations . . . . . . . . . . . . . . . . . . . 39
9.1. Confidentiality and Authentication . . . . . . . . . . . . 46 9.1. Confidentiality and Authentication . . . . . . . . . . . 39
9.2. Authorization . . . . . . . . . . . . . . . . . . . . . . 46 9.2. Authorization . . . . . . . . . . . . . . . . . . . . . . 39
9.3. Denial of Service . . . . . . . . . . . . . . . . . . . . 46 9.3. Denial of Service . . . . . . . . . . . . . . . . . . . . 40
9.3.1. DoS Issues Inherited from Transport Mechanism . . . . 46 9.3.1. DoS Issues Inherited from Transport Mechanism . . . . 40
9.3.2. DoS Issues Specific to SPPF . . . . . . . . . . . . . 47 9.3.2. DoS Issues Specific to SPPF . . . . . . . . . . . . . 41
9.4. Information Disclosure . . . . . . . . . . . . . . . . . . 48 9.4. Information Disclosure . . . . . . . . . . . . . . . . . 41
9.5. Non Repudiation . . . . . . . . . . . . . . . . . . . . . 48 9.5. Non Repudiation . . . . . . . . . . . . . . . . . . . . . 42
9.6. Replay Attacks . . . . . . . . . . . . . . . . . . . . . . 48 9.6. Replay Attacks . . . . . . . . . . . . . . . . . . . . . 42
9.7. Man in the Middle . . . . . . . . . . . . . . . . . . . . 48 9.7. Man in the Middle . . . . . . . . . . . . . . . . . . . . 42
10. Internationalization Considerations . . . . . . . . . . . . . 50 10. Internationalization Considerations . . . . . . . . . . . . . 42
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 51 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 43
12. Formal Specification . . . . . . . . . . . . . . . . . . . . . 52 12. Formal Specification . . . . . . . . . . . . . . . . . . . . 43
13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 61 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 51
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 62 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 52
14.1. Normative References . . . . . . . . . . . . . . . . . . . 62 14.1. Normative References . . . . . . . . . . . . . . . . . . 52
14.2. Informative References . . . . . . . . . . . . . . . . . . 62 14.2. Informative References . . . . . . . . . . . . . . . . . 52
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 64 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
other participating peering entities. The requirements and use cases other participating peering entities. The requirements and use cases
skipping to change at page 5, line 5 skipping to change at page 4, line 5
The framework that supports flow of messages to facilitate client to The framework that supports flow of messages to facilitate client to
Registry provisioning is referred to as Session Peering Provisioning Registry provisioning is referred to as Session Peering Provisioning
Framework (SPPF). Framework (SPPF).
The role of the "client" and the "server" only applies to the The role of the "client" and the "server" only applies to the
connection, and those roles are not related in any way to the type of connection, and those roles are not related in any way to the type of
entity that participates in a protocol exchange. For example, a entity that participates in a protocol exchange. For example, a
Registry might also include a "client" when such a Registry initiates Registry might also include a "client" when such a Registry initiates
a connection (for example, for data distribution to SSP). a connection (for example, for data distribution to SSP).
*--------* *------------* *------------* *--------* *------------* *------------*
| | (1). Client | | (3).Registry | | | | (1). Client | | (3).Registry | |
| Client | ------------> | Registry |<------------->| Registry | | Client | ------------> | Registry |<------------->| Registry |
| | to Registry | | to Registry | | | | to Registry | | to Registry | |
*--------* *------------* *------------* *--------* *------------* *------------*
/ \ \ / \ \
/ \ \ / \ \
/ \ \ / \ \
/ \ v / \ v
/ \ ... / \ ...
/ \ / \
/ (2). Distrib \ / (2). Distrib \
/ Registry data \ / Registry data \
/ to local data \ / to local data \
V store V V store V
+----------+ +----------+ +----------+ +----------+
|Local Data| |Local Data| |Local Data| |Local Data|
|Repository| |Repository| |Repository| |Repository|
+----------+ +----------+ +----------+ +----------+
Three Registry Provisioning Flows Three Registry Provisioning Flows
Figure 1 Figure 1
A "terminating" SIP Service Provider (SSP) provisions Session A "terminating" SIP Service Provider (SSP) provisions Session
Establishment Data or SED into the Registry to be selectively shared Establishment Data or SED into the Registry to be selectively shared
with other peer SSPs. with other peer SSPs.
SED is typically used by various downstream SIP signaling systems to SED is typically used by various downstream SIP signaling systems to
skipping to change at page 6, line 29 skipping to change at page 5, line 35
of the SPPF and to express the data types, the semantic relationships of the SPPF and to express the data types, the semantic relationships
between the various data types, and the various constraints as a between the various data types, and the various constraints as a
binding construct. However, the "protocol" specification is free to binding construct. However, the "protocol" specification is free to
choose any data representation format as long as it meets the choose any data representation format as long as it meets the
requirements laid out in the SPPF XML schema definition. As an requirements laid out in the SPPF XML schema definition. As an
example, XML and JSON are two widely used data representation example, XML and JSON are two widely used data representation
formats. formats.
This document is organized as follows: This document is organized as follows:
o Section 2 provides the terminology o Section 2 provides the terminology
o Section 3 provides an overview of SPPF, including functional
entities and data model
o Section 4 specifies requirements for SPPF transport protocols o Section 3 provides an overview of SPPF, including functional
entities and data model
o Section 5 describes the base framework data structures, the o Section 4 specifies requirements for SPPF transport protocols
generic response types that MUST be supported by a conforming
transport "protocol" specification, and the basic object type
most first class objects extend from
o Section 6 provides a detailed description of the data model o Section 5 describes the base framework data structures, the
object specifications generic response types that MUST be supported by a conforming
transport "protocol" specification, and the basic object type most
first class objects extend from
o Section 8 defines XML considerations XML parsers must meet to o Section 6 provides a detailed description of the data model object
conform to this specification specifications
o Section 7 describes the operations that are supported by the o Section 7 describes the operations that are supported by the data
data model model
o Section 7 describes the operations that are supported by the o Section 8 defines XML considerations XML parsers must meet to
data model conform to this specification
o Sections 9 - 11 discuss security, internationalization and IANA o Sections 9 - 11 discuss security, internationalization and IANA
considerations considerations
o Section 12 normatively defines the SPPF using its XML Schema o Section 12 normatively defines the SPPF using its XML Schema
Definition. Definition.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
This document reuses terms from [RFC3261], [RFC5486], use cases and This document reuses terms from [RFC3261], [RFC5486], use cases and
requirements documented in [RFC6461] and the ENUM Validation requirements documented in [RFC6461] and the ENUM Validation
Architecture [RFC4725]. Architecture [RFC4725].
skipping to change at page 11, line 28 skipping to change at page 8, line 28
|A SED Group is / |A SED Group is /
|associated with / |associated with /
|zero or more / +---[abstract]----+ |zero or more / +---[abstract]----+
|Peering / | SED Record: | |Peering / | SED Record: |
|Organizations / | rant, | |Organizations / | rant, |
| / | sedName, |0..n | / | sedName, |0..n
|0..n / | sedFunction, |------| |0..n / | sedFunction, |------|
+--------+--------------+0..n 0..n| isInSvc, | | +--------+--------------+0..n 0..n| isInSvc, | |
|SED Group: |------------------| ttl | | |SED Group: |------------------| ttl | |
| rant, | +-----------------+ | | rant, | +-----------------+ |
| sedGrpName, | ^ | | sedGrpName, | ^ Various types |
| isInSvc, | |Various types | | isInSvc, | | of SED Records |
| sedRecRef, | |of SED | | sedRecRef, | | |
| peeringOrg, | |Records | | peeringOrg, | +-----+------------+ |
| sourceIdent, | +-----+------------+ | | sourceIdent, | | | | |
| priority, | | | | | | priority, | +----+ +-------+ +----+ |
| dgName | +----+ +-------+ +----+ | | dgName | | URI| | NAPTR | | NS | |
+-----------------------+ | URI| | NAPTR | | NS | | +-----------------------+ +----+ +-------+ +----+ |
|0..n +----+ +-------+ +----+ | |0..n |
| |
| +-----[abstract]------+ | | +-----[abstract]------+ |
| |Public Identifier: | | |0..n |Public Identifier: | |
|0..n | rant, | | +----------------------+0..n 0..n| rant, | |
+----------------------+0..n 0..n| publicIdentifier, | | | Dest Group: |--------------| publicIdentifier, | |
| Dest Group: |--------------| destGrpRef | | | rant, | | dgName | |
| rant, | | | | | dgName | | | |
| dgName | +---------------------+ | +----------------------+ +---------------------+ |
+----------------------+ ^Various types | ^ Various types |
|of Public | +---------+-------+------+----------+ of Public |
|Identifiers | | | | | | Identifiers |
+---------+-------+------+----------+ | +------+ +-----+ +-----+ +-----+ +------+ |
| | | | | | | URI | | TNP | | TNR | | RN | | TN |-------------|
+------+ +-----+ +-----+ +-----+ +------+ | +------+ +-----+ +-----+ +-----+ +------+ 0..n
| URI | | TNP | | TNR | | RN | |TN |----------|
+------+ +-----+ +-----+ +-----+ +------+ 0..n
Figure 2 Figure 2
The objects and attributes that comprise the data model can be The objects and attributes that comprise the data model can be
described as follows (objects listed from the bottom up): described as follows (objects listed from the bottom up):
o Public Identifier: o Public Identifier:
From a broad perspective a public identifier is a well-known From a broad perspective a public identifier is a well-known
attribute that is used as the key to perform resolution lookups. attribute that is used as the key to perform resolution lookups.
Within the context of SPPF, a public identifier object can be a Within the context of SPPF, a public identifier object can be a
Telephone Number (TN), a range of Telephone Numbers, a PSTN Telephone Number (TN), a range of Telephone Numbers, a PSTN
Routing Number (RN), a TN prefix, or a URI. Routing Number (RN), a TN prefix, or a URI.
An SPPF Public Identifier is associated with a Destination Group An SPPF Public Identifier may be a member of zero or more
to create a logical grouping of Public Identifiers that share a Destination Groups to create logical groupings of Public
common set of Session Establishment Data (e.g. routes). Identifiers that share a common set of Session Establishment Data
(e.g. routes).
A TN Public Identifier may optionally be associated with zero or A TN Public Identifier may optionally be associated with zero or
more individual SED Records. This ability for a Public Identifier more individual SED Records. This ability for a Public Identifier
to be directly associated with a SED Record, as opposed to being to be directly associated with a SED Record, as opposed to forcing
associated with a Destination Group, supports the use cases where membership in one or more Destination Groups, supports use cases
the SED Record contains data specifically tailored to an where the SED Record contains data specifically tailored to an
individual TN Public Identifier. individual TN Public Identifier.
o Destination Group: o Destination Group:
A named collection of zero or more Public Identifiers that can be A named logical grouping of zero or more Public Identifiers that
associated with one or more SED Groups for the purpose of can be associated with one or more SED Groups for the purpose of
facilitating the management of their common session establishment facilitating the management of their common session establishment
information. information.
o SED Group: o SED Group:
A SED Group contains a set of SED Record references, a set of A SED Group contains a set of SED Record references, a set of
Destination Group references, and a set of peering organization Destination Group references, and a set of peering organization
identifiers. This is used to establish a three part relationships identifiers. This is used to establish a three part relationships
between a set of Public Identifiers, the session establishment between a set of Public Identifiers, the session establishment
information (SED) shared across these Public Identifiers, and the information (SED) shared across these Public Identifiers, and the
list of peering organizations whose query responses from the list of peering organizations whose query responses from the
skipping to change at page 13, line 17 skipping to change at page 10, line 17
These SED Records extend the abstract type SedRecType and inherit These SED Records extend the abstract type SedRecType and inherit
the common attribute 'priority' that is meant for setting the common attribute 'priority' that is meant for setting
precedence across the SED records defined within a SED Group in a precedence across the SED records defined within a SED Group in a
protocol agnostic fashion. protocol agnostic fashion.
o Egress Route: o Egress Route:
In a high-availability environment, the originating SSP likely has In a high-availability environment, the originating SSP likely has
more than one egress paths to the ingress SBE of the target SSP. more than one egress paths to the ingress SBE of the target SSP.
The Egress Route allows the originating SSP to choose a specific The Egress Route allows the originating SSP to choose a specific
egress SBE to be associated with the target ingress SBE. the egress SBE to be associated with the target ingress SBE. the
'svcs' element identifies the SED records associated with the SED 'svcs' element specifies ENUM services ((e.g.,E2U+pstn:sip+sip)
that are used to identify the SED records associated with the SED
Group that will be modified by the originating SSP. Group that will be modified by the originating SSP.
o Organization: o Organization:
An Organization is an entity that may fulfill any combination of An Organization is an entity that may fulfill any combination of
three roles: Registrant, Registrar, and Peering Organization. All three roles: Registrant, Registrar, and Peering Organization. All
objects in SPPF are associated with two organization identifiers objects in SPPF are associated with two organization identifiers
to identify each object's Registrant and Registrar. A SED Group to identify each object's Registrant and Registrar. A SED Group
object is also associated with a set of zero or more organization object is also associated with a set of zero or more organization
identifiers that identify the peering organization(s) whose identifiers that identify the peering organization(s) whose
resolution query responses may include the session establishment resolution query responses may include the session establishment
skipping to change at page 13, line 42 skipping to change at page 10, line 43
3.2. Time Value 3.2. Time Value
Some request and response messages in SPPF include time value(s) Some request and response messages in SPPF include time value(s)
defined as type xs:dateTime, a built-in W3C XML Schema Datatype. Use defined as type xs:dateTime, a built-in W3C XML Schema Datatype. Use
of unqualified local time value is disallowed as it can lead to of unqualified local time value is disallowed as it can lead to
interoperability issues. The value of time attribute MUST be interoperability issues. The value of time attribute MUST be
expressed in Coordinated Universal Time (UTC) format without the expressed in Coordinated Universal Time (UTC) format without the
timezone digits. timezone digits.
"2010-05-30T09:30:10Z" is an example of an acceptable time value for "2010-05-30T09:30:10Z" is an example of an acceptable time value for
use in SPPF messages. "2010-05-30T06:30:10+3:00" is a valid UTC time, use in SPPF messages. "2010-05-30T06:30:10+3:00" is a valid UTC
but it is not approved for use in SPPF messages. time, but it is not approved for use in SPPF messages.
3.3. Extensibility 3.3. Extensibility
The framework contains various points of extensiblity in form of the The framework contains various points of extensibility in form of the
"ext" elements. Extensions used beyond the scope of privat e SPPF "ext" elements. Extensions used beyond the scope of private SPPF
installations MUST be documented in an RFC level document, and the installations MUST be documented in an RFC level document, and the
first such extension SHOULD define an IANA registry, holding a list first such extension SHOULD define an IANA registry, holding a list
of documented extensions. of documented extensions.
4. Transport Protocol Requirements 4. Transport Protocol Requirements
This section provides requirements for transport protocols suitable This section provides requirements for transport protocols suitable
for SPPF. More specifically, this section specifies the services, for SPPF. More specifically, this section specifies the services,
features, and assumptions that SPPF framework delegates to the chosen features, and assumptions that SPPF framework delegates to the chosen
transport and envelope technologies. transport and envelope technologies.
skipping to change at page 14, line 45 skipping to change at page 11, line 45
short-lived, and may be established only on demand. Other use cases short-lived, and may be established only on demand. Other use cases
involve either provisioning a large dataset, or a constant stream of involve either provisioning a large dataset, or a constant stream of
small updates, either of which would likely require long-lived small updates, either of which would likely require long-lived
connections. connections.
Therefore, a protocol suitable for SPPF SHOULD be able to support Therefore, a protocol suitable for SPPF SHOULD be able to support
both short-lived as well as long-lived connections. both short-lived as well as long-lived connections.
4.4. Authentication 4.4. Authentication
All SPPF objects are associated with a Registrant identifier. SPPF All SPPF objects are associated with a Registrant identifier. An
Clients provisions SPPF objects on behalf of Registrants. An SPPF Client provisions SPPF objects on behalf of Registrants. An
authenticated SPP Client is a Registrar. Therefore, the SPPF authenticated SPP Client is a Registrar. Therefore, the SPPF
transport protocol MUST provide means for an SPPF server to transport protocol MUST provide means for an SPPF server to
authenticate an SPPF Client. authenticate an SPPF Client.
4.5. Authorization 4.5. Authorization
After successful authentication of the SPPF client as a Registrar the After successful authentication of the SPPF client as a Registrar the
Registry performs authorization checks to determine if the Registrar Registry performs authorization checks to determine if the Registrar
is authorized to act on behalf of the Registrant whose identifier is is authorized to act on behalf of the Registrant whose identifier is
included in the SPPF request. Refer to the Security Considerations included in the SPPF request. Refer to the Security Considerations
section for further guidance. section for further guidance.
4.6. Confidentiality and Integrity 4.6. Confidentiality and Integrity
SPPF objects that the Registry manages can be private in nature. SPPF objects that the Registry manages can be private in nature.
Therefore, the transport protocol MUST provide means for end-to-end Therefore, the transport protocol MUST provide means for end-to-end
skipping to change at page 17, line 15 skipping to change at page 13, line 28
5. Base Framework Data Structures and Response Codes 5. Base Framework Data Structures and Response Codes
SPPF contains some common data structures for most of the supported SPPF contains some common data structures for most of the supported
object types. This section describes these common data structures. object types. This section describes these common data structures.
5.1. Basic Object Type and Organization Identifiers 5.1. Basic Object Type and Organization Identifiers
All first class objects extend the type BasicObjType. It consists of All first class objects extend the type BasicObjType. It consists of
the Registrant organization, the Registrar organization, the date and the Registrant organization, the Registrar organization, the date and
time of object creation, and the last date and time the object was time of object creation, and the last date and time the object was
updated. The Registry MUST date and time of the object creation and updated. The Registry MUST store the date and time of the object
update, if applicable, for all Get operations (see Section 7). If creation and update, if applicable, for all Get operations (see
the client passed in either date and time values, the Registry MUST Section 7). If the client passed in either date and time values, the
ignore it. The Registrar performs the SPPF operations on behalf of Registry MUST ignore it. The Registrar performs the SPPF operations
the Registrant, the organization that owns the object. on behalf of the Registrant, the organization that owns the object.
<complexType name="BasicObjType" abstract="true"> <complexType name="BasicObjType" abstract="true">
<sequence> <sequence>
<element name="rant" type="sppfb:OrgIdType"/> <element name="rant" type="sppfb:OrgIdType"/>
<element name="rar" type="sppfb:OrgIdType"/> <element name="rar" type="sppfb:OrgIdType"/>
<element name="cDate" type="dateTime" minOccurs="0"/> <element name="cDate" type="dateTime" minOccurs="0"/>
<element name="mDate" type="dateTime" minOccurs="0"/> <element name="mDate" type="dateTime" minOccurs="0"/>
<element name="ext" type="sppfb:ExtAnyType" minOccurs="0"/> <element name="ext" type="sppfb:ExtAnyType" minOccurs="0"/>
</sequence> </sequence>
</complexType> </complexType>
The identifiers used for Registrants (rant) and Registrars (rar) are The identifiers used for Registrants (rant) and Registrars (rar) are
instances of OrgIdType. The OrgIdType is defined as a string and all instances of OrgIdType. The OrgIdType is defined as a string and all
OrgIdType instances MUST follow the textual convention: "namespace: OrgIdType instances MUST follow the textual convention:
value" (for example "iana-en:32473"). See the IANA Consideration "namespace:value" (for example "iana-en:32473"). See the IANA
section for more details. Consideration section for more details.
5.2. Various Object Key Types 5.2. Various Object Key Types
The SPPF data model contains various object relationships. In some The SPPF data model contains various object relationships. In some
cases, these object relationships are established by embedding the cases, these object relationships are established by embedding the
unique identity of the related object inside the relating object. unique identity of the related object inside the relating object.
Note that an object's unique identity is required to Delete or Get Note that an object's unique identity is required to Delete or Get
the details of an object. The following sub-sections normatively the details of an object. The following sub-sections normatively
define the various object keys in SPPF and the attributes of those define the various object keys in SPPF and the attributes of those
keys . keys.
"Name" attributes that are used as components of object key types "Name" attributes that are used as components of object key types
MUST be treated case insensitive, more specifically, comparison MUST be treated case insensitive, more specifically, comparison
operations MUST use the toCasefold() function, as specified in operations MUST use the toCasefold() function, as specified in
Section 3.13 of [Unicode6.1]. Section 3.13 of [Unicode6.1].
5.2.1. Generic Object Key Type 5.2.1. Generic Object Key Type
Most objects in SPPF are uniquely identified by an object key that Most objects in SPPF are uniquely identified by an object key that
has the object's name, object's type and its Registrant's has the object's name, object's type and its Registrant's
skipping to change at page 18, line 39 skipping to change at page 15, line 11
</documentation> </documentation>
</annotation> </annotation>
</complexType> </complexType>
5.2.2. Derived Object Key Types 5.2.2. Derived Object Key Types
The SPPF data model contains certain objects that are uniquely The SPPF data model contains certain objects that are uniquely
identified by attributes, different from or in addition to, the identified by attributes, different from or in addition to, the
attributes in the generic object key described in previous section. attributes in the generic object key described in previous section.
These kind of object keys are derived from the abstract ObjKeyType These kind of object keys are derived from the abstract ObjKeyType
and defined in there own abstract key types. Because these object and defined in their own abstract key types. Because these object
key types are abstract, these MUST be specified in a concrete form in key types are abstract, they MUST be specified in a concrete form in
any SPPF conforming transport protocol specification. These are used any SPPF conforming transport protocol specification. These are used
in Delete and Get operations, and may also be used in Accept and in Delete and Get operations, and may also be used in Accept and
Reject operations. Reject operations.
Following are the derived object keys in SPPF data model: Following are the derived object keys in SPPF data model:
o SedGrpOfferKeyType: This uniquely identifies a SED Group object o SedGrpOfferKeyType: This uniquely identifies a SED Group object
offer. This key type extends from ObjKeyType and MUST also have offer. This key type extends from ObjKeyType and MUST also have
the organization ID of the Registrant to whom the object is the organization ID of the Registrant to whom the object is being
being offered, as one of its attributes. In addition to the offered, as one of its attributes. In addition to the Delete and
Delete and Get operations, these key types are used in Accept Get operations, these key types are used in Accept and Reject
and Reject operations on a SED Group Offer object. The operations on a SED Group Offer object. The structure of abstract
structure of abstract SedGrpOfferKeyType is as follows: SedGrpOfferKeyType is as follows:
<complexType name="SedGrpOfferKeyType" <complexType name="SedGrpOfferKeyType"
abstract="true"> abstract="true">
<complexContent> <complexContent>
<extension base="sppfb:ObjKeyType"> <extension base="sppfb:ObjKeyType">
<annotation> <annotation>
<documentation> <documentation>
---- Generic type that represents ---- Generic type that represents
the key for a object offer. ---- the key for a object offer. ----
</documentation> </documentation>
</annotation> </annotation>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
A SED Group Offer object MUST use SedGrpOfferKeyType. Refer the A SED Group Offer object MUST use SedGrpOfferKeyType. Refer the
"Framework Data Model Objects" section of this document for "Framework Data Model Objects" section of this document for
description of SED Group Offer object. description of SED Group Offer object.
o PubIdKeyType: This uniquely identifies a Public Identity object.
This key type extends from abstract ObjKeyType. Any concrete
definition of PubIdKeyType MUST contain the elements that
identify the value and type of Public Identity and also contain
the organization ID of the Registrant that is the owner of the
Public Identity object. A Public Identity object key in SPPF is
uniquely identified by the the Registrant's organization ID, the
value of the public identity, and, optionally, the Destination
Group name the public identity belongs to. Consequently, any
concrete representation of the PubIdKeyType MUST contain the
following attributes:
* Registrant Id: The unique organization ID that identifies o PubIdKeyType: This uniquely identifies a Public Identity object.
the Registrant. This key type extends from abstract ObjKeyType. Any concrete
definition of PubIdKeyType MUST contain the elements that identify
the value and type of Public Identity and also contain the
organization ID of the Registrant that is the owner of the Public
Identity object. A Public Identity object in SPPF is uniquely
identified by the Registrant's organization ID, the value of the
public identity, and the type of the public identity object.
Consequently, any concrete representation of the PubIdKeyType MUST
contain the following attributes:
* Destination Group name: The name of the Destination Group Registrant Id: The unique organization ID that identifies the
the Public Identity is associated with. This is an Registrant.
optional attribute.
* Type: The type of Public Identity. Value: The value of the Public Identity.
* Value: The value of the Public Identity. Type: The type of the Public Identity Object.
The PubIdKeyType is used in Delete and Get operations on a The PubIdKeyType is used in Delete and Get operations on a Public
Public Identifier object. Identifier object.
o The structure of abstract PubIdKeyType is as follows: o The structure of abstract PubIdKeyType is as follows:
<complexType name="PubIdKeyType" abstract="true"> <complexType name="PubIdKeyType" abstract="true">
<complexContent> <complexContent>
<extension base="sppfb:ObjKeyType"> <extension base="sppfb:ObjKeyType">
<annotation> <annotation>
<documentation> <documentation>
---- Generic type that represents the key for a Pub Id. ---- ---- Generic type that represents the key for a Pub Id. ----
</documentation> </documentation>
</annotation> </annotation>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
A Public Identity object MUST use attributes of PubIdKeyType for its A Public Identity object MUST use attributes of PubIdKeyType for its
unique identification . Refer to Section 6 for a description of unique identification . Refer to Section 6 for a description of
Public Identity object. Public Identity object.
5.3. Response Message Types 5.3. Response Message Types
This section contains the listing of response types that MUST be This section contains the listing of response types that MUST be
defined by the SPPF conforming transport protocol specification and defined by the SPPF conforming transport protocol specification and
implemented by a conforming SPPF server. implemented by a conforming SPPF server.
+---------------------+---------------------------------------------+ +-----------------+-------------------------------------------------+
| Response Type | Description | | Response Type | Description |
+---------------------+---------------------------------------------+ +-----------------+-------------------------------------------------+
| Request Succeeded | Any conforming specification MUST define a | | Request | Any conforming specification MUST define a |
| | response to indicate that a given request | | Succeeded | response to indicate that a given request |
| | succeeded. | | | succeeded. |
| | | | | |
| Request syntax | Any conforming specification MUST define a | | Request syntax | Any conforming specification MUST define a |
| invalid | response to indicate that a syntax of a | | invalid | response to indicate that a syntax of a given |
| | given request was found invalid. | | | request was found invalid. |
| | | | | |
| Request too large | Any conforming specification MUST define a | | Request too | Any conforming specification MUST define a |
| | response to indicate that the count of | | large | response to indicate that the count of entities |
| | entities in the request is larger than the | | | in the request is larger than the server is |
| | server is willing or able to process. | | | willing or able to process. |
| | | | | |
| Version not | Any conforming specification MUST define a | | Version not | Any conforming specification MUST define a |
| supported | response to indicate that the server does | | supported | response to indicate that the server does not |
| | not support the version of the SPPF | | | support the version of the SPPF protocol |
| | protocol specified in the request. | | | specified in the request. |
| | | | | |
| Command invalid | Any conforming specification MUST define a | | Command invalid | Any conforming specification MUST define a |
| | response to indicate that the operation | | | response to indicate that the operation and/or |
| | and/or command being requested by the | | | command being requested by the client is |
| | client is invalid and/or not supported by | | | invalid and/or not supported by the server. |
| | the server. | | | |
| | | | System | Any conforming specification MUST define a |
| System temporarily | Any conforming specification MUST define a | | temporarily | response to indicate that the SPPF server is |
| unavailable | response to indicate that the SPPF server | | unavailable | temporarily not available to serve client |
| | is temporarily not available to serve | | | request. |
| | client request. | | | |
| | | | Unexpected | Any conforming specification MUST define a |
| Unexpected internal | Any conforming specification MUST define a | | internal system | response to indicate that the SPPF server |
| system or server | response to indicate that the SPPF server | | or server | encountered an unexpected error that prevented |
| error. | encountered an unexpected error that | | error. | the server from fulfilling the request. |
| | prevented the server from fulfilling the | | | |
| | request. | | Attribute value | Any conforming specification MUST define a |
| | | | invalid | response to indicate that the SPPF server |
| Attribute value | Any conforming specification MUST define a | | | encountered an attribute or property in the |
| invalid | response to indicate that the SPPF server | | | request that had an invalid/bad value. |
| | encountered an attribute or property in the | | | Optionally, the specification MAY provide a way |
| | request that had an invalid/bad value. | | | to indicate the Attribute Name and the |
| | Optionally, the specification MAY provide a | | | Attribute Value to identify the object that was |
| | way to indicate the Attribute Name and the | | | found to be invalid. |
| | Attribute Value to identify the object that | | | |
| | was found to be invalid. | | Object does not | Any conforming specification MUST define a |
| | | | exist | response to indicate that an object present in |
| Object does not | Any conforming specification MUST define a | | | the request does not exist on the SPPF server. |
| exist | response to indicate that an object present | | | Optionally, the specification MAY provide a way |
| | in the request does not exist on the SPPF | | | to indicate the Attribute Name and the |
| | server. Optionally, the specification MAY | | | Attribute Value that identifies the non- |
| | provide a way to indicate the Attribute | | | existent object. |
| | Name and the Attribute Value that | | | |
| | identifies the non-existent object. | | Object status | Any conforming specification MUST define a |
| | | | or ownership | response to indicate that the operation |
| Object status or | Any conforming specification MUST define a | | does not allow | requested on an object present in the request |
| ownership does not | response to indicate that the operation | | for operation. | cannot be performed because the object is in a |
| allow for | requested on an object present in the | | | status that does not allow the said operation |
| operation. | request cannot be performed because the | | | or the user requesting the operation is not |
| | object is in a status that does not allow | | | authorized to perform the said operation on the |
| | the said operation or the user requesting | | | object. Optionally, the specification MAY |
| | the operation is not authorized to perform | | | provide a way to indicate the Attribute Name |
| | the said operation on the object. | | | and the Attribute Value that identifies the |
| | Optionally, the specification MAY provide a | | | object. |
| | way to indicate the Attribute Name and the | +-----------------+-------------------------------------------------+
| | Attribute Value that identifies the object. |
+---------------------+---------------------------------------------+
Table 1: Response Types Table 1: Response Types
When the response messages are "parameterized" with the Attribute When the response messages are "parameterized" with the Attribute
Name and Attribute Value, then the use of these parameters MUST Name and Attribute Value, then the use of these parameters MUST
adhere to the following rules: adhere to the following rules:
o Any value provided for the Attribute Name parameter MUST be an o Any value provided for the Attribute Name parameter MUST be an
exact XSD element name of the protocol data element that the exact XSD element name of the protocol data element that the
response message is referring to. For example, valid values for response message is referring to. For example, valid values for
"attribute name" are "dgName", "sedGrpName", "sedRec", etc. "attribute name" are "dgName", "sedGrpName", "sedRec", etc.
o The value for Attribute Value MUST be the value of the data o The value for Attribute Value MUST be the value of the data
element to which the preceding Attribute Name refers. element to which the preceding Attribute Name refers.
o Response type "Attribute value invalid" MUST be used whenever an o Response type "Attribute value invalid" MUST be used whenever an
element value does not adhere to data validation rules. element value does not adhere to data validation rules.
o Response types "Attribute value invalid" and "Object does not o Response types "Attribute value invalid" and "Object does not
exist" MUST not be used interchangeably. Response type "Object exist" MUST not be used interchangeably. Response type "Object
does not exist" MUST be returned by an Update/Del/Accept/Reject does not exist" MUST be returned by an Update/Del/Accept/Reject
operation when the data element(s) used to uniquely identify a operation when the data element(s) used to uniquely identify a
pre-existing object do not exist. If the data elements used to pre-existing object do not exist. If the data elements used to
uniquely identify an object are malformed, then response type uniquely identify an object are malformed, then response type
"Attribute value invalid" MUST be returned. "Attribute value invalid" MUST be returned.
6. Framework Data Model Objects 6. Framework Data Model Objects
This section provides a description of the specification of each This section provides a description of the specification of each
supported data model object (the nouns) and identifies the commands supported data model object (the nouns) and identifies the commands
(the verbs) that MUST be supported for each data model object. (the verbs) that MUST be supported for each data model object.
However, the specification of the data structures necessary to However, the specification of the data structures necessary to
support each command is delegated to an SPPF conforming transport support each command is delegated to an SPPF conforming transport
protocol specification. protocol specification.
6.1. Destination Group 6.1. Destination Group
Destination Group represents a set of Public Identifiers with common Destination Group represents a logical grouping of Public Identifiers
session establishment information. The transport protocol MUST with common session establishment information. The transport
support the ability to Create, Modify, Get, and Delete Destination protocol MUST support the ability to Create, Modify, Get, and Delete
Groups (refer the "Framework Operations" section of this document for Destination Groups (refer the "Framework Operations" section of this
a generic description of various operations). document for a generic description of various operations).
A Destination Group object MUST be uniquely identified by attributes A Destination Group object MUST be uniquely identified by attributes
as defined in the description of "ObjKeyType" in the section "Generic as defined in the description of "ObjKeyType" in the section "Generic
Object Key Type" of this document. Object Key Type" of this document.
The DestGrpType object structure is defined as follows: The DestGrpType object structure is defined as follows:
<complexType name="DestGrpType"> <complexType name="DestGrpType">
<complexContent> <complexContent>
<extension base="sppfb:BasicObjType"> <extension base="sppfb:BasicObjType">
<sequence> <sequence>
<element name="dgName" type="sppfb:ObjNameType"/> <element name="dgName" type="sppfb:ObjNameType"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
The DestGrpType object is composed of the following elements: The DestGrpType object is composed of the following elements:
o base: All first class objects extend BasicObjType (see o base: All first class objects extend BasicObjType (see
Section 5.1). Section 5.1).
o dgName: The character string that contains the name of the o dgName: The character string that contains the name of the
Destination Group. Destination Group.
o ext: Point of extensibility described in Section 3.3. o ext: Point of extensibility described in Section 3.3.
6.2. Public Identifier 6.2. Public Identifier
A Public Identifier is the search key used for locating the session A Public Identifier is the search key used for locating the session
establishment data (SED). In many cases, a Public Identifier is establishment data (SED). In many cases, a Public Identifier is
attributed to the end user who has a retail relationship with the attributed to the end user who has a retail relationship with the
service provider or Registrant organization. SPPF supports the service provider or Registrant organization. SPPF supports the
notion of the carrier-of-record as defined in [RFC5067]. Therefore, notion of the carrier-of-record as defined in [RFC5067]. Therefore,
the Registrant under whom the Public Identity is being created can the Registrant under whom the Public Identity is being created can
optionally claim to be a carrier-of-record. optionally claim to be a carrier-of-record.
SPPF identifies three types of Public Identifiers: telephone numbers SPPF identifies three types of Public Identifiers: telephone numbers
(TN), routing numbers (RN), and URI type of Public Identifiers. SPPF (TN), routing numbers (RN), and URI. SPPF provides structures to
provides structures to manage a single TN, a contiguous range of TNs, manage a single TN, a contiguous range of TNs, and a TN prefix. The
and a TN prefix. The transport protocol MUST support the ability to transport protocol MUST support the ability to Create, Modify, Get,
Create, Modify, Get, and Delete Public Identifiers (refer the and Delete Public Identifiers (refer the "Framework Operations"
"Framework Operations" section of this document for a generic section of this document for a generic description of various
description of various operations). operations).
A Public Identity object MUST be uniquely identified by attributes as A Public Identity object MUST be uniquely identified by attributes as
defined in the description of "PubIdKeyType" in the section defined in the description of "PubIdKeyType" in the section
Section 5.2.2. Section 5.2.2.
The abstract XML schema type definition PubIDType is a generalization The abstract XML schema type definition PubIdType is a generalization
for the concrete Public Identifier schema types. PubIDType element for the concrete Public Identifier schema types. PubIdType element
'dgName' represents the name of the destination group that a given 'dgName' represents the name of a destination group that a given
Public Identifier may be a member of. The PubIDType object structure Public Identifier may be a member of. Note that this element may be
is defined as follows: present multiple times so that a given Public Identifier may be a
member of multiple destination groups. The PubIdType object
structure is defined as follows:
<complexType name="PubIdType" abstract="true"> <complexType name="PubIdType" abstract="true">
<complexContent> <complexContent>
<extension base="sppfb:BasicObjType"> <extension base="sppfb:BasicObjType">
<sequence> <sequence>
<element name="dgName" type="sppfb:ObjNameType" minOccurs="0"/> <element name="dgName" type="sppfb:ObjNameType"
minOccurs="0" maxOccurs="unbounded"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
A Public Identifier may be provisioned as a member of a Destination A Public Identifier may be a member of zero or more Destination
Group or provisioned outside of a Destination Group. A Public Groups. When a Public Identifier is member of a Destination Group,
Identifier that is provisioned as a member of a Destination Group is it is intended to be associated with SED(s) through the SED Group(s)
intended to be associated with its SED through the SED Group(s) that that are associated with the Destination Group. When a Public
are associated with its containing Destination Group. A Public Identifier is not member of any Destination Group, it is intended to
Identifier that is not provisioned as a member of a Destination Group be associated with SED through the SED Records that are directly
is intended to be associated with its SED through the SED Records associated with the Public Identifier.
that are directly associated with the Public Identifier.
A telephone number is provisioned using the TNType, an extension of A telephone number is provisioned using the TNType, an extension of
PubIDType. When a Public Identifier is provisioned as a member of a PubIdType. Each TNType object is uniquely identified by the
Destination Group, each TNType object is uniquely identified by the combination of its value contained within <tn> element, and its
combination of its value contained within <tn> element, and the Registrant ID. TNType is defined as follows:
unique key of its parent Destination Group (dgName and rantId). In
other words a given telephone number string may exist within one or
more Destination Groups, but must not exist more than once within a
Destination Group. A Public Identifier that is not provisioned as a
member of a Destination Group is uniquely identified by the
combination of its value, and its Registrant ID. TNType is defined
as follows:
<complexType name="TNType"> <complexType name="TNType">
<complexContent> <complexContent>
<extension base="sppfb:PubIdType"> <extension base="sppfb:PubIdType">
<sequence> <sequence>
<element name="tn" type="sppfb:NumberValType"/> <element name="tn" type="sppfb:NumberValType"/>
<element name="corInfo" type="sppfb:CORInfoType" minOccurs="0"/> <element name="corInfo" type="sppfb:CORInfoType" minOccurs="0"/>
<element name="sedRecRef" type="sppfb:SedRecRefType" <element name="sedRecRef" type="sppfb:SedRecRefType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</sequence> </sequence>
skipping to change at page 25, line 47 skipping to change at page 21, line 28
<simpleType name="NumberValType"> <simpleType name="NumberValType">
<restriction base="token"> <restriction base="token">
<maxLength value="20"/> <maxLength value="20"/>
<pattern value="\+?\d\d*"/> <pattern value="\+?\d\d*"/>
</restriction> </restriction>
</simpleType> </simpleType>
TNType consists of the following attributes: TNType consists of the following attributes:
o tn: Telephone number to be added to the Registry. o tn: Telephone number to be added to the Registry.
o sedRecRef: Optional reference to SED records that are directly o sedRecRef: Optional reference to SED records that are directly
associated with the TN Public Identifier. Following the SPPF associated with the TN Public Identifier. Following the SPPF data
data model, the SED record could be a protocol agnostic URIType model, the SED record could be a protocol agnostic URIType or
or another type. another type.
o corInfo: corInfo is an optional parameter of type CORInfoType o corInfo: corInfo is an optional parameter of type CORInfoType that
that allows the Registrant organization to set forth a claim to allows the Registrant organization to set forth a claim to be the
be the carrier-of-record (see [RFC5067]). This is done by carrier-of-record (see [RFC5067]). This is done by setting the
setting the value of <corClaim> element of the CORInfoType value of <corClaim> element of the CORInfoType object structure to
object structure to "true". The other two parameters of the "true". The other two parameters of the CORInfoType, <cor> and
CORInfoType, <cor> and <corDate> are set by the Registry to <corDate> are set by the Registry to describe the outcome of the
describe the outcome of the carrier-of-record claim by the carrier-of-record claim by the Registrant. In general, inclusion
Registrant. In general, inclusion of <corInfo> parameter is of <corInfo> parameter is useful if the Registry has the authority
useful if the Registry has the authority information, such as, information, such as, the number portability data, etc., in order
the number portability data, etc., in order to qualify whether to qualify whether the Registrant claim can be satisfied. If the
the Registrant claim can be satisfied. If the carrier-of-record carrier-of-record claim disagrees with the authority data in the
claim disagrees with the authority data in the Registry, whether Registry, whether the TN add operation fails or not is a matter of
the TN add operation fails or not is a matter of policy and it policy and it is beyond the scope of this document.
is beyond the scope of this document.
A routing number is provisioned using the RNType, an extension of A routing number is provisioned using the RNType, an extension of
PubIDType. The Registrant organization can add the RN and associate PubIDType. The Registrant organization can add the RN and associate
it with the appropriate destination group to share the route it with the appropriate destination group(s) to share the route
information. This allows SSPs to use the RN search key to derive the information. This allows SSPs to use the RN search key to derive the
ingress routes for session establishment at the runtime resolution ingress routes for session establishment at the runtime resolution
process (see [RFC3761]. Each RNType object is uniquely identified by process (see [RFC3761]. Each RNType object is uniquely identified by
the combination of its value inside the <rn> element, and the unique the combination of its value inside the <rn> element, and its
key of its parent Destination Group (dgName and rantId). In other Registrant ID. RNType is defined as follows:
words a given routing number string may exist within one or more
Destination Groups, but must not exist more than once within a
Destination Group. RNType is defined as follows:
<complexType name="RNType"> <complexType name="RNType">
<complexContent> <complexContent>
<extension base="sppfb:PubIdType"> <extension base="sppfb:PubIdType">
<sequence> <sequence>
<element name="rn" type="sppfb:NumberValType"/> <element name="rn" type="sppfb:NumberValType"/>
<element name="corInfo" type="sppfb:CORInfoType" minOccurs="0"/> <element name="corInfo" type="sppfb:CORInfoType" minOccurs="0"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
RNType has the following attributes: RNType has the following attributes:
o rn: Routing Number used as the search key. o rn: Routing Number used as the search key.
o corInfo: corInfo is an optional parameter of type CORInfoType o corInfo: corInfo is an optional parameter of type CORInfoType that
that allows the Registrant organization to set forth a claim to allows the Registrant organization to set forth a claim to be the
be the carrier-of-record (see [RFC5067]) carrier-of-record (see [RFC5067])
TNRType structure is used to provision a contiguous range of TNRType structure is used to provision a contiguous range of
telephone numbers. The object definition requires a starting TN and telephone numbers. The object definition requires a starting TN and
an ending TN that together define the span of the TN range. Use of an ending TN that together define the span of the TN range. Use of
TNRType is particularly useful when expressing a TN range that does TNRType is particularly useful when expressing a TN range that does
not include all the TNs within a TN block or prefix. The TNRType not include all the TNs within a TN block or prefix. The TNRType
definition accommodates the open number plan as well such that the definition accommodates the open number plan as well such that the
TNs that fall between the start and end TN range may include TNs with TNs that fall between the start and end TN range may include TNs with
different length variance. Whether the Registry can accommodate the different length variance. Whether the Registry can accommodate the
open number plan semantics is a matter of policy and is beyond the open number plan semantics is a matter of policy and is beyond the
scope of this document. Each TNRType object is uniquely identified scope of this document. Each TNRType object is uniquely identified
by the combination of its value that in turn is a combination of the by the combination of its value that in turn is a combination of the
<startTn> and <endTn> elements, and the unique key of its parent <startTn> and <endTn> elements, and its Registrant ID. TNRType
Destination Group (dgName and rantId). In other words a given TN object structure definition is as follows:
Range may exist within one or more Destination Groups, but must not
exist more than once within a Destination Group. TNRType object
structure definition is as follows:
<complexType name="TNRType"> <complexType name="TNRType">
<complexContent> <complexContent>
<extension base="sppfb:PubIdType"> <extension base="sppfb:PubIdType">
<sequence> <sequence>
<element name="range" type="sppfb:NumberRangeType"/> <element name="range" type="sppfb:NumberRangeType"/>
<element name="corInfo" type="sppfb:CORInfoType" minOccurs="0"/> <element name="corInfo" type="sppfb:CORInfoType" minOccurs="0"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
skipping to change at page 27, line 43 skipping to change at page 23, line 19
<complexType name="NumberRangeType"> <complexType name="NumberRangeType">
<sequence> <sequence>
<element name="startTn" type="sppfb:NumberValType"/> <element name="startTn" type="sppfb:NumberValType"/>
<element name="endTn" type="sppfb:NumberValType"/> <element name="endTn" type="sppfb:NumberValType"/>
</sequence> </sequence>
</complexType> </complexType>
TNRType has the following attributes: TNRType has the following attributes:
o startTn: Starting TN in the TN range o startTn: Starting TN in the TN range
o endTn: The last TN in the TN range o endTn: The last TN in the TN range
o corInfo: corInfo is an optional parameter of type CORInfoType o corInfo: corInfo is an optional parameter of type CORInfoType that
that allows the Registrant organization to set forth a claim to allows the Registrant organization to set forth a claim to be the
be the carrier-of-record (see [RFC5067]) carrier-of-record (see [RFC5067])
In some cases, it is useful to describe a set of TNs with the help of In some cases, it is useful to describe a set of TNs with the help of
the first few digits of the telephone number, also referred to as the the first few digits of the telephone number, also referred to as the
telephone number prefix or a block. A given TN prefix may include telephone number prefix or a block. A given TN prefix may include
TNs with different length variance in support of open number plan. TNs with different length variance in support of open number plan.
Once again, whether the Registry supports the open number plan Once again, whether the Registry supports the open number plan
semantics is a matter of policy and it is beyond the scope of this semantics is a matter of policy and it is beyond the scope of this
document. The TNPType data structure is used to provision a TN document. The TNPType data structure is used to provision a TN
prefix. Each TNPType object is uniquely identified by the prefix. Each TNPType object is uniquely identified by the
combination of its value in the <tnPrefix> element, and the unique combination of its value in the <tnPrefix> element, and its
key of its parent Destination Group (dgName and rantId). TNPType is Registrant ID. TNPType is defined as follows:
defined as follows:
<complexType name="TNPType"> <complexType name="TNPType">
<complexContent> <complexContent>
<extension base="sppfb:PubIdType"> <extension base="sppfb:PubIdType">
<sequence> <sequence>
<element name="tnPrefix" type="sppfb:NumberValType"/> <element name="tnPrefix" type="sppfb:NumberValType"/>
<element name="corInfo" type="sppfb:CORInfoType" minOccurs="0"/> <element name="corInfo" type="sppfb:CORInfoType" minOccurs="0"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
TNPType consists of the following attributes: TNPType consists of the following attributes:
o tnPrefix: The telephone number prefix o tnPrefix: The telephone number prefix
o corInfo: corInfo is an optional parameter of type CORInfoType o corInfo: corInfo is an optional parameter of type CORInfoType that
that allows the Registrant organization to set forth a claim to allows the Registrant organization to set forth a claim to be the
be the carrier-of-record (see [RFC5067]) carrier-of-record (see [RFC5067])
In some cases, a Public Identifier may be a URI, such as an email In some cases, a Public Identifier may be a URI, such as an email
address. The URIPubIdType object is comprised of the data element address. The URIPubIdType object is comprised of the data element
necessary to house such Public Identifiers. Each URIPubIdType object necessary to house such Public Identifiers. Each URIPubIdType object
is uniquely identified by the combination of its value in the <uri> is uniquely identified by the combination of its value in the <uri>
element, and the unique key of its parent Destination Group (dgName element, and its Registrant ID. URIPubIdType is defined as follows:
and rantId). URIPubIdType is defined as follows:
<complexType name="URIPubIdType"> <complexType name="URIPubIdType">
<complexContent> <complexContent>
<extension base="sppfb:PubIdType"> <extension base="sppfb:PubIdType">
<sequence> <sequence>
<element name="uri" type="anyURI"/> <element name="uri" type="anyURI"/>
<element name="ext" type="sppfb:ExtAnyType" minOccurs="0"/> <element name="ext" type="sppfb:ExtAnyType" minOccurs="0"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
URIPubIdType consists of the following attributes: URIPubIdType consists of the following attributes:
o uri: The value that acts a Public Identifier. o uri: The value that acts a Public Identifier.
o ext: Point of extensibility described in Section 3.3. o ext: Point of extensibility described in Section 3.3.
6.3. SED Group 6.3. SED Group
SED Group is a grouping of one or more Destination Group, the common SED Group is a grouping of one or more Destination Group, the common
SED Records, and the list of peer organizations with access to the SED Records, and the list of peer organizations with access to the
SED Records associated with a given SED Group. It is this indirect SED Records associated with a given SED Group. It is this indirect
linking of public identifiers to their Session Establishment Data linking of public identifiers to their Session Establishment Data
that significantly improves the scalability and manageability of the that significantly improves the scalability and manageability of the
peering data. Additions and changes to SED information are reduced peering data. Additions and changes to SED information are reduced
to a single operation on a SED Group or SED Record , rather than to a single operation on a SED Group or SED Record , rather than
skipping to change at page 30, line 36 skipping to change at page 25, line 38
<complexType name="SedRecRefType"> <complexType name="SedRecRefType">
<sequence> <sequence>
<element name="sedKey" type="sppfb:ObjKeyType"/> <element name="sedKey" type="sppfb:ObjKeyType"/>
<element name="priority" type="unsignedShort"/> <element name="priority" type="unsignedShort"/>
<element name="ext" type="sppfb:ExtAnyType" minOccurs="0"/> <element name="ext" type="sppfb:ExtAnyType" minOccurs="0"/>
</sequence> </sequence>
</complexType> </complexType>
The SedGrpType object is composed of the following elements: The SedGrpType object is composed of the following elements:
o base: All first class objects extend BasicObjType (see o base: All first class objects extend BasicObjType (see
Section 5.1). Section 5.1).
o sedGrpName: The character string that contains the name of the o sedGrpName: The character string that contains the name of the SED
SED Group. It uniquely identifies this object within the Group. It uniquely identifies this object within the context of
context of the Registrant ID (a child element of the base the Registrant ID (a child element of the base element as
element as described above). described above).
o sedRecRef: Set of zero or more objects of type SedRecRefType o sedRecRef: Set of zero or more objects of type SedRecRefType that
that house the unique keys of the SED Records (containing the house the unique keys of the SED Records (containing the session
session establishment data) that the SedGrpType object refers to establishment data) that the SedGrpType object refers to and their
and their relative priority within the context of this SED relative priority within the context of this SED Group.
Group.
o dgName: Set of zero or more names of DestGrpType object o dgName: Set of zero or more names of DestGrpType object instances.
instances. Each dgName name, in association with this SED Each dgName name, in association with this SED Group's Registrant
Group's Registrant ID, uniquely identifies a DestGrpType object ID, uniquely identifies a DestGrpType object instance whose
instance whose public identifiers are reachable using the associated public identifiers are reachable using the session
session establishment information housed in this SED Group. An establishment information housed in this SED Group. An intended
intended side affect of this is that a SED Group cannot provide side affect of this is that a SED Group cannot provide session
session establishment information for a Destination Group establishment information for a Destination Group belonging to
belonging to another Registrant. another Registrant.
o peeringOrg: Set of zero or more peering organization IDs that o peeringOrg: Set of zero or more peering organization IDs that have
have accepted an offer to receive this SED Group's information. accepted an offer to receive this SED Group's information. Note
Note that this identifier "peeringOrg" is an instance of that this identifier "peeringOrg" is an instance of OrgIdType.
OrgIdType. The set of peering organizations in this list is not The set of peering organizations in this list is not directly
directly settable or modifiable using the addSedGrpsRqst settable or modifiable using the addSedGrpsRqst operation. This
operation. This set is instead controlled using the SED offer set is instead controlled using the SED offer and accept
and accept operations. operations.
o sourceIdent: Set of zero or more SourceIdentType object o sourceIdent: Set of zero or more SourceIdentType object instances.
instances. These objects, described further below, house the These objects, described further below, house the source
source identification schemes and identifiers that are applied identification schemes and identifiers that are applied at
at resolution time as part of source based routing algorithms resolution time as part of source based routing algorithms for the
for the SED Group. SED Group.
o isInSvc: A boolean element that defines whether this SED Group o isInSvc: A boolean element that defines whether this SED Group is
is in service. The session establishment information contained in service. The session establishment information contained in a
in a SED Group that is in service is a candidate for inclusion SED Group that is in service is a candidate for inclusion in
in resolution responses for public identities residing in the resolution responses for public identities residing in the
Destination Group associated with this SED Group. The session Destination Group associated with this SED Group. The session
establishment information contained in a SED Group that is not establishment information contained in a SED Group that is not in
in service is not a candidate for inclusion in resolution service is not a candidate for inclusion in resolution responses.
responses.
o priority: Zero or one priority value that can be used to provide o priority: Priority value that can be used to provide a relative
a relative value weighting of one SED Group over another. The value weighting of one SED Group over another. The manner in
manner in which this value is used, perhaps in conjunction with which this value is used, perhaps in conjunction with other
other factors, is a matter of policy. factors, is a matter of policy.
o ext: Point of extensibility described in Section 3.3. o ext: Point of extensibility described in Section 3.3.
As described above, the SED Group contains a set of references to SED As described above, the SED Group contains a set of references to SED
record objects. A SED record object is based on an abstract type: record objects. A SED record object is based on an abstract type:
SedRecType. The concrete types that use SedRecType as an extension SedRecType. The concrete types that use SedRecType as an extension
base are NAPTRType, NSType, and URIType. The definitions of these base are NAPTRType, NSType, and URIType. The definitions of these
types are included the SED Record section of this document. types are included the SED Record section of this document.
The SedGrpType object provides support for source-based routing via The SedGrpType object provides support for source-based routing via
the peeringOrg data element and more granular source base routing via the peeringOrg data element and more granular source base routing via
the source identity element. The source identity element provides the source identity element. The source identity element provides
skipping to change at page 32, line 39 skipping to change at page 27, line 41
<restriction base="token"> <restriction base="token">
<enumeration value="uri"/> <enumeration value="uri"/>
<enumeration value="ip"/> <enumeration value="ip"/>
<enumeration value="rootDomain"/> <enumeration value="rootDomain"/>
</restriction> </restriction>
</simpleType> </simpleType>
The SourceIdentType object is composed of the following data The SourceIdentType object is composed of the following data
elements: elements:
o sourceIdentScheme: The source identification scheme that this o sourceIdentScheme: The source identification scheme that this
source identification criteria applies to and that the source identification criteria applies to and that the associated
associated sourceIdentRegex should be matched against. sourceIdentRegex should be matched against.
o sourceIdentRegex: The regular expression that should be used to o sourceIdentRegex: The regular expression that should be used to
test for a match against the portion of the resolution request test for a match against the portion of the resolution request
that is dictated by the associated sourceIdentScheme. that is dictated by the associated sourceIdentScheme.
o ext: Point of extensibility described in Section 3.3. o ext: Point of extensibility described in Section 3.3.
6.4. SED Record 6.4. SED Record
SED Group represents a combined grouping of SED Records that define SED Group represents a combined grouping of SED Records that define
session establishment information. However, SED Records need not be session establishment information. However, SED Records need not be
created to just serve a single SED Group. SED Records can be created created to just serve a single SED Group. SED Records can be created
and managed to serve multiple SED Groups. As a result, a change for and managed to serve multiple SED Groups. As a result, a change for
example to the properties of a network node used for multiple routes, example to the properties of a network node used for multiple routes,
would necessitate just a single update operation to change the would necessitate just a single update operation to change the
properties of that node. The change would then be reflected in all properties of that node. The change would then be reflected in all
skipping to change at page 33, line 49 skipping to change at page 28, line 49
<simpleType name="SedFunctionType"> <simpleType name="SedFunctionType">
<restriction base="token"> <restriction base="token">
<enumeration value="routing"/> <enumeration value="routing"/>
<enumeration value="lookup"/> <enumeration value="lookup"/>
</restriction> </restriction>
</simpleType> </simpleType>
The SedRecType object is composed of the following elements: The SedRecType object is composed of the following elements:
o base: All first class objects extend BasicObjType (see o base: All first class objects extend BasicObjType (see
Section 5.1). Section 5.1).
o sedName: The character string that contains the name of the SED o sedName: The character string that contains the name of the SED
Record. It uniquely identifies this object within the context Record. It uniquely identifies this object within the context of
of the Registrant ID (a child element of the base element as the Registrant ID (a child element of the base element as
described above). described above).
o sedFunction: As described in [RFC6461], SED or Session o sedFunction: As described in [RFC6461], SED or Session
Establishment Data falls primarily into one of two categories or Establishment Data falls primarily into one of two categories or
functions, LUF and LRF. To remove any ambiguity as to the functions, LUF and LRF. To remove any ambiguity as to the
function a SED record is intended to provide, this optional function a SED record is intended to provide, this optional
element allows the provisioning party to make his or her element allows the provisioning party to make his or her
intentions explicit. intentions explicit.
o isInSvc: A boolean element that defines whether this SED Record o isInSvc: A boolean element that defines whether this SED Record is
is in service or not. The session establishment information in service or not. The session establishment information
contained in a SED Record which is in service is a candidate for contained in a SED Record which is in service is a candidate for
inclusion in resolution responses for Telephone Numbers that are inclusion in resolution responses for Telephone Numbers that are
either directly associated to this SED Record, or for Public either directly associated to this SED Record, or for Public
Identities residing in a Destination Group that is associated to Identities residing in a Destination Group that is associated to a
a SED Group which in turn has an association to this SED Record. SED Group which in turn has an association to this SED Record.
o ttl: Number of seconds that an addressing server may cache a o ttl: Number of seconds that an addressing server may cache a
particular SED Record. particular SED Record.
As described above, SED records are based on an abstract type: As described above, SED records are based on an abstract type:
SedRecType. The concrete types that use SedRecType as an extension SedRecType. The concrete types that use SedRecType as an extension
base are NAPTRType, NSType, and URIType. The definitions of these base are NAPTRType, NSType, and URIType. The definitions of these
types are included below. The NAPTRType object is comprised of the types are included below. The NAPTRType object is comprised of the
data elements necessary for a NAPTR (see [RFC3403]that contains data elements necessary for a NAPTR (see [RFC3403]that contains
routing information for a SED Group. The NSType object is comprised routing information for a SED Group. The NSType object is comprised
of the data elements necessary for a DNS name server that points to of the data elements necessary for a DNS name server that points to
another DNS server that contains the desired routing information. another DNS server that contains the desired routing information.
The NSType is relevant only when the resolution protocol is ENUM (see The NSType is relevant only when the resolution protocol is ENUM (see
[RFC3761]). The URIType object is comprised of the data elements [RFC3761]). The URIType object is comprised of the data elements
necessary to house a URI. necessary to house a URI.
The data provisioned in a Registry can be leveraged for many purposes The data provisioned in a Registry can be leveraged for many purposes
and queried using various protocols including SIP, ENUM and others. and queried using various protocols including SIP, ENUM and others.
As such, the resolution data represented by the Sed records must be As such, the resolution data represented by the SED records must be
in a form suitable for transport using one of these protocols. In in a form suitable for transport using one of these protocols. In
the NPATRType for example, if the URI is associated with a the NAPTRType for example, if the URI is associated with a
destination group, the user part of the replacement string <uri> that destination group, the user part of the replacement string <uri> that
may require the Public Identifier cannot be preset. As a SIP may require the Public Identifier cannot be preset. As a SIP
Redirect, the resolution server will apply <ere> pattern on the input Redirect, the resolution server will apply <ere> pattern on the input
Public Identifier in the query and process the replacement string by Public Identifier in the query and process the replacement string by
substituting any back reference(s) in the <uri> to arrive at the substituting any back reference(s) in the <uri> to arrive at the
final URI that is returned in the SIP Contact header. For an ENUM final URI that is returned in the SIP Contact header. For an ENUM
query, the resolution server will simply return the values of the query, the resolution server will simply return the values of the
<ere> and <uri> members of the URI. <ere> and <uri> members of the URI.
<complexType name="NAPTRType"> <complexType name="NAPTRType">
skipping to change at page 36, line 20 skipping to change at page 31, line 20
<simpleType name="flagsType"> <simpleType name="flagsType">
<restriction base="token"> <restriction base="token">
<length value="1"/> <length value="1"/>
<pattern value="[A-Z]|[a-z]|[0-9]"/> <pattern value="[A-Z]|[a-z]|[0-9]"/>
</restriction> </restriction>
</simpleType> </simpleType>
The NAPTRType object is composed of the following elements: The NAPTRType object is composed of the following elements:
o order: Order value in an ENUM NAPTR, relative to other NAPTRType o order: Order value in an ENUM NAPTR, relative to other NAPTRType
objects in the same SED Group. objects in the same SED Group.
o svcs: ENUM service(s) that are served by the SBE. This field's o svcs: ENUM service(s) that are served by the SBE. This field's
value must be of the form specified in [RFC6116] (e.g., E2U+ value must be of the form specified in [RFC6116] (e.g.,
pstn:sip+sip). The allowable values are a matter of policy and E2U+pstn:sip+sip). The allowable values are a matter of policy
not limited by this protocol. and not limited by this protocol.
o regx: NAPTR's regular expression field. If this is not included o regx: NAPTR's regular expression field. If this is not included
then the Repl field must be included. then the Repl field must be included.
o repl: NAPTR replacement field, should only be provided if the o repl: NAPTR replacement field, should only be provided if the
Regex field is not provided, otherwise the server will ignore it Regex field is not provided, otherwise the server will ignore it
o ext: Point of extensibility described in Section 3.3. o ext: Point of extensibility described in Section 3.3.
The NSType object is composed of the following elements: The NSType object is composed of the following elements:
o hostName: Root-relative host name of the name server. o hostName: Root-relative host name of the name server.
o ipAddr: Zero or more objects of type IpAddrType. Each object o ipAddr: Zero or more objects of type IpAddrType. Each object
holds an IP Address and the IP Address type, IPv4 or IP v6. holds an IP Address and the IP Address type, IPv4 or IP v6.
o ext: Point of extensibility described in Section 3.3. o ext: Point of extensibility described in Section 3.3.
The URIType object is composed of the following elements: The URIType object is composed of the following elements:
o ere: The POSIX Extended Regular Expression (ere) as defined in o ere: The POSIX Extended Regular Expression (ere) as defined in
[RFC3986]. [RFC3986].
o uri: the URI as defined in [RFC3986]. In some cases, this will o uri: the URI as defined in [RFC3986]. In some cases, this will
serve as the replacement string and it will be left to the serve as the replacement string and it will be left to the
resolution server to arrive at the final usable URI. resolution server to arrive at the final usable URI.
6.5. SED Group Offer 6.5. SED Group Offer
The list of peer organizations whose resolution responses can include The list of peer organizations whose resolution responses can include
the session establishment information contained in a given SED Group the session establishment information contained in a given SED Group
is controlled by the organization to which a SED Group object belongs is controlled by the organization to which a SED Group object belongs
(its Registrant), and the peer organization that submits resolution (its Registrant), and the peer organization that submits resolution
requests (a data recipient, also know as a peering organization). requests (a data recipient, also know as a peering organization).
The Registrant offers access to a SED Group by submitting a SED Group The Registrant offers access to a SED Group by submitting a SED Group
Offer. The data recipient can then accept or reject that offer. Not Offer. The data recipient can then accept or reject that offer. Not
skipping to change at page 38, line 23 skipping to change at page 32, line 51
<element name="ext" type="sppfb:ExtAnyType" minOccurs="0"/> <element name="ext" type="sppfb:ExtAnyType" minOccurs="0"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<complexType name="SedGrpOfferKeyType" abstract="true"> <complexType name="SedGrpOfferKeyType" abstract="true">
<annotation> <annotation>
<documentation> <documentation>
-- Generic type that represents the key for a SED group offer. Must -- Generic type that represents the key for a SED group offer. Must
be defined in concrete form in the transport specificaiton. -- be defined in concrete form in the transport specification. --
</documentation> </documentation>
</annotation> </annotation>
</complexType> </complexType>
<simpleType name="SedGrpOfferStatusType"> <simpleType name="SedGrpOfferStatusType">
<restriction base="token"> <restriction base="token">
<enumeration value="offered"/> <enumeration value="offered"/>
<enumeration value="accepted"/> <enumeration value="accepted"/>
</restriction> </restriction>
</simpleType> </simpleType>
skipping to change at page 38, line 37 skipping to change at page 33, line 17
<simpleType name="SedGrpOfferStatusType"> <simpleType name="SedGrpOfferStatusType">
<restriction base="token"> <restriction base="token">
<enumeration value="offered"/> <enumeration value="offered"/>
<enumeration value="accepted"/> <enumeration value="accepted"/>
</restriction> </restriction>
</simpleType> </simpleType>
The SedGrpOfferType object is composed of the following elements: The SedGrpOfferType object is composed of the following elements:
o base: All first class objects extend BasicObjType (see o base: All first class objects extend BasicObjType (see
Section 5.1). Section 5.1).
o sedGrpOfferKey: The object that identifies the SED that is or o sedGrpOfferKey: The object that identifies the SED that is or has
has been offered and the organization that it is or has been been offered and the organization that it is or has been offered
offered to. to.
o status: The status of the offer, offered or accepted. The o status: The status of the offer, offered or accepted. The server
server controls the status. It is automatically set to controls the status. It is automatically set to "offered" when
"offered" when ever a new SED Group Offer is added, and is ever a new SED Group Offer is added, and is automatically set to
automatically set to "accepted" if and when that offer is "accepted" if and when that offer is accepted. The value of the
accepted. The value of the element is ignored when passed in by element is ignored when passed in by the client.
the client.
o offerDateTime: Date and time in UTC when the SED Group Offer was o offerDateTime: Date and time in UTC when the SED Group Offer was
added. added.
o acceptDateTime: Date and time in UTC when the SED Group Offer o acceptDateTime: Date and time in UTC when the SED Group Offer was
was accepted. accepted.
6.6. Egress Route 6.6. Egress Route
In a high-availability environment, the originating SSP likely has In a high-availability environment, the originating SSP likely has
more than one egress path to the ingress SBE of the target SSP. If more than one egress path to the ingress SBE of the target SSP. If
the originating SSP wants to exercise greater control and choose a the originating SSP wants to exercise greater control and choose a
specific egress SBE to be associated to the target ingress SBE, it specific egress SBE to be associated to the target ingress SBE, it
can do so using the EgrRteType object. can do so using the EgrRteType object.
An Egress Route object MUST be uniquely identified by attributes as An Egress Route object MUST be uniquely identified by attributes as
skipping to change at page 40, line 4 skipping to change at page 34, line 31
<element name="pref" type="unsignedShort"/> <element name="pref" type="unsignedShort"/>
<element name="regxRewriteRule" type="sppfb:RegexParamType"/> <element name="regxRewriteRule" type="sppfb:RegexParamType"/>
<element name="ingrSedGrp" type="sppfb:ObjKeyType" <element name="ingrSedGrp" type="sppfb:ObjKeyType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<element name="svcs" type="sppfb:SvcType" minOccurs="0"/> <element name="svcs" type="sppfb:SvcType" minOccurs="0"/>
<element name="ext" type="sppfb:ExtAnyType" minOccurs="0"/> <element name="ext" type="sppfb:ExtAnyType" minOccurs="0"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
The EgrRteType object is composed of the following elements: The EgrRteType object is composed of the following elements:
o base: All first class objects extend BasicObjType (see o base: All first class objects extend BasicObjType (see
Section 5.1). Section 5.1).
o egrRteName: The name of the egress route. o egrRteName: The name of the egress route.
o pref: The preference of this egress route relative to other o pref: The preference of this egress route relative to other egress
egress routes that may get selected when responding to a routes that may get selected when responding to a resolution
resolution request. request.
o regxRewriteRule: The regular expression re-write rule that o regxRewriteRule: The regular expression re-write rule that should
should be applied to the regular expression of the ingress be applied to the regular expression of the ingress NAPTR(s) that
NAPTR(s) that belong to the ingress route. belong to the ingress route.
o ingrSedGrp: The ingress SED group that the egress route should o ingrSedGrp: The ingress SED group that the egress route should be
be used for. used for.
o svcs: ENUM service(s) that are served by an Egress Route. This o svcs: ENUM service(s) that are served by an Egress Route. This
element is used to identify the ingress NAPTRs associated with element is used to identify the ingress NAPTRs associated with the
the SED Group to which an Egress Route's regxRewriteRule should SED Group to which an Egress Route's regxRewriteRule should be
be applied. If no ENUM service(s) are associated with an Egress applied. If no ENUM service(s) are associated with an Egress
Route, then the Egress Route's regxRewriteRule should be applied Route, then the Egress Route's regxRewriteRule should be applied
to all the NAPTRs associated with the SED Group. This field's to all the NAPTRs associated with the SED Group. This field's
value must be of the form specified in [RFC6116] (e.g., E2U+ value must be of the form specified in [RFC6116] (e.g.,
pstn:sip+sip). The allowable values are a matter of policy and E2U+pstn:sip+sip). The allowable values are a matter of policy
not limited by this protocol. and not limited by this protocol.
o ext: Point of extensibility described in Section 3.3. o ext: Point of extensibility described in Section 3.3.
7. Framework Operations 7. Framework Operations
In addition to the operation specific object types, all operations
MAY specify the minor version of the protocol that when used in
conjunction with the major version (that can be for instance
specified in the protocol namespace) can serve to identify the
version of the SPPF protocol that the client is using. If the minor
version is not specified, the latest minor version supported by the
SPPF server for the given major version will be used. Additionally,
operations that may potentially modify persistent protocol objects
SHOULD include a transaction ID as well.
7.1. Add Operation 7.1. Add Operation
Any conforming transport protocol specification MUST provide a Any conforming transport protocol specification MUST provide a
definition for the operation that adds one or more SPPF objects into definition for the operation that adds one or more SPPF objects into
the Registry. If the object, as identified by the request attributes the Registry. If the object, as identified by the request attributes
that form part of the object's key, does not exist, then the Registry that form part of the object's key, does not exist, then the Registry
MUST create the object. If the object does exist, then the Registry MUST create the object. If the object does exist, then the Registry
MUST replace the current properties of the object with the properties MUST replace the current properties of the object with the properties
passed in as part of the Add operation. passed in as part of the Add operation.
skipping to change at page 41, line 40 skipping to change at page 36, line 17
amongst the response messages defined in "Response Message Types" amongst the response messages defined in "Response Message Types"
section of the document. section of the document.
When an object is deleted, any references to that object must of When an object is deleted, any references to that object must of
course also be removed as the SPPF server implementation fulfills the course also be removed as the SPPF server implementation fulfills the
deletion request. Furthermore, the deletion of a composite object deletion request. Furthermore, the deletion of a composite object
must also result in the deletion of the objects it contains. As a must also result in the deletion of the objects it contains. As a
result, the following rules apply to the deletion of SPPF object result, the following rules apply to the deletion of SPPF object
types: types:
o Destination Groups: When a destination group is deleted all o Destination Groups: When a destination group is deleted any
public identifiers within that destination group must also be references between that destination group and any SED group must
automatically deleted by the SPPF implementation as part of be automatically removed by the SPPF implementation as part of
fulfilling the deletion request. And any references between fulfilling the deletion request. Similarly, any references
that destination group and any SED group must be automatically between that destination group and any Public Identifier must be
removed by the SPPF implementation as part of fulfilling the removed by the SPPF implementation as part of fulfilling the
deletion request. deletion request.
o SED Groups: When a SED group is deleted any references between o SED Groups: When a SED group is deleted any references between
that SED group and any destination group must be automatically that SED group and any destination group must be automatically
removed by the SPPF implementation as part of fulfilling the removed by the SPPF implementation as part of fulfilling the
deletion request. Similarly any references between that SED deletion request. Similarly any references between that SED group
group and any SED records must be removed by the SPPF and any SED records must be removed by the SPPF implementation as
implementation as part of fulfilling the deletion request. part of fulfilling the deletion request. Furthermore, SED group
Furthermore, SED group offers relating that SED group must also offers relating that SED group must also be deleted as part of
be deleted as part of fulfilling the deletion request. fulfilling the deletion request.
o SED Records: When a SED record is deleted any references between o SED Records: When a SED record is deleted any references between
that SED record and any SED group must be removed by the SPPF that SED record and any SED group must be removed by the SPPF
implementation as part of fulfilling the deletion request. implementation as part of fulfilling the deletion request.
Similarly, any reference between that SED record and any Public
Identifier must be removed by the SPPF implementation as part of
fulfilling the deletion request.
o Public Identifiers: When a public identifier is deleted any o Public Identifiers: When a public identifier is deleted any
references between that public identifier and its containing references between that public identifier and any referenced
destination group must be removed by the SPPF implementation as destination group must be removed by the SPPF implementation as
part of fulfilling the deletion request. Any SED records part of fulfilling the deletion request. Any references to SED
contained directly within that Public Identifier must be deleted records associated directly to that Public Identifier must also be
by the SPPF implementation as part of fulfilling the deletion deleted by the SPPF implementation as part of fulfilling the
request. deletion request.
7.3. Get Operations 7.3. Get Operations
At times, on behalf of the Registrant, the Registrar may need to get At times, on behalf of the Registrant, the Registrar may need to get
information about SPPF objects that were previously provisioned in information about SPPF objects that were previously provisioned in
the Registry. A few examples include logging, auditing, and pre- the Registry. A few examples include logging, auditing, and pre-
provisioning dependency checking. This query mechanism is limited to provisioning dependency checking. This query mechanism is limited to
aid provisioning scenarios and should not be confused with query aid provisioning scenarios and should not be confused with query
protocols provided as part of the resolution system (e.g. ENUM and protocols provided as part of the resolution system (e.g. ENUM and
SIP). SIP).
skipping to change at page 47, line 5 skipping to change at page 40, line 33
issues inherent to the specific lower-level mechanism used for any issues inherent to the specific lower-level mechanism used for any
implementation of SPPF. SPPF also has its own set of higher-level implementation of SPPF. SPPF also has its own set of higher-level
exposures that are likely to be independent of lower-layer mechanism exposures that are likely to be independent of lower-layer mechanism
choices. choices.
9.3.1. DoS Issues Inherited from Transport Mechanism 9.3.1. DoS Issues Inherited from Transport Mechanism
SPPF implementation is in general dependent on the selection and SPPF implementation is in general dependent on the selection and
implementation of a lower-level transport protocol and a binding implementation of a lower-level transport protocol and a binding
between that protocol and SPPF. The archetypal SPPF implementation between that protocol and SPPF. The archetypal SPPF implementation
uses XML (http://www.w3.org/TR/xml/) representation in a SOAP uses XML (http://www.w3.org/TR/xml/) representation in a SOAP (http:/
(http://www.w3.org/TR/soap/) request/response framework over HTTP /www.w3.org/TR/soap/) request/response framework over HTTP
([RFC2616]), and probably also uses TLS ([RFC5246]) for on-the wire ([RFC2616]), and probably also uses TLS ([RFC5246]) for on-the wire
data integrity and participant authentication, and might use HTTP data integrity and participant authentication, and might use HTTP
Digest authentication ([RFC2609]). Digest authentication ([RFC2609]).
The typical deployment scenario for SPPF is to have servers in a The typical deployment scenario for SPPF is to have servers in a
managed facility, and therefore techniques such as Network Ingress managed facility, and therefore techniques such as Network Ingress
Filtering ([RFC2609]) are generally applicable. In short, any DoS Filtering ([RFC2609]) are generally applicable. In short, any DoS
mechanism affecting a typical HTTP implementation would affect such mechanism affecting a typical HTTP implementation would affect such
an SPPF implementation, and the mitigation tools for HTTP in general an SPPF implementation, and the mitigation tools for HTTP in general
also therefore apply to SPPF. also therefore apply to SPPF.
skipping to change at page 51, line 29 skipping to change at page 43, line 29
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 IANA is requested to create a new SPPF Registry for Organization
Identifiers that will indicate valid strings to be used for well- Identifiers that will indicate valid strings to be used for well-
known enterprise namespaces. known enterprise namespaces.
This document makes the following assignments for the OrgIdType This document makes the following assignments for the OrgIdType
namespaces: namespaces:
Namespace OrgIdType namespace string Namespace OrgIdType namespace string
---- ---------------------------- ---- ----------------------------
IANA Enterprise Numbers iana-en IANA Enterprise Numbers iana-en
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 54, line 5 skipping to change at page 45, line 33
<element name="dgName" <element name="dgName"
type="sppfb:ObjNameType"/> type="sppfb:ObjNameType"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<complexType name="PubIdType" abstract="true"> <complexType name="PubIdType" abstract="true">
<complexContent> <complexContent>
<extension base="sppfb:BasicObjType"> <extension base="sppfb:BasicObjType">
<sequence> <sequence>
<element name="dgName" type="sppfb:ObjNameType" minOccurs="0"/> <element name="dgName" type="sppfb:ObjNameType"
minOccurs="0" maxOccurs="unbounded"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<complexType name="TNType"> <complexType name="TNType">
<complexContent> <complexContent>
<extension base="sppfb:PubIdType"> <extension base="sppfb:PubIdType">
<sequence> <sequence>
<element name="tn" type="sppfb:NumberValType"/> <element name="tn" type="sppfb:NumberValType"/>
<element name="corInfo" type="sppfb:CORInfoType" minOccurs="0"/> <element name="corInfo" type="sppfb:CORInfoType" minOccurs="0"/>
skipping to change at page 62, line 22 skipping to change at page 52, line 29
[RFC2277] Alvestrand, H., "IETF Policy on Character Sets and [RFC2277] Alvestrand, H., "IETF Policy on Character Sets and
Languages", BCP 18, RFC 2277, January 1998. Languages", BCP 18, RFC 2277, January 1998.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, November 2003. 10646", STD 63, RFC 3629, November 2003.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
[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, Resource Identifier (URI): Generic Syntax", STD 66, RFC
RFC 3986, January 2005. 3986, January 2005.
[RFC4949] Shirey, R., "Internet Security Glossary, Version 2", [RFC4949] Shirey, R., "Internet Security Glossary, Version 2", RFC
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.
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.,
skipping to change at page 62, line 45 skipping to change at page 53, line 4
[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
10646", RFC 2781, February 2000. 10646", RFC 2781, February 2000.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
June 2002. June 2002.
[RFC3403] Mealling, M., "Dynamic Delegation Discovery System (DDDS) [RFC3403] Mealling, M., "Dynamic Delegation Discovery System (DDDS)
Part Three: The Domain Name System (DNS) Database", Part Three: The Domain Name System (DNS) Database", RFC
RFC 3403, October 2002. 3403, October 2002.
[RFC3761] Faltstrom, P. and M. Mealling, "The E.164 to Uniform [RFC3761] Faltstrom, P. and M. Mealling, "The E.164 to Uniform
Resource Identifiers (URI) Dynamic Delegation Discovery Resource Identifiers (URI) Dynamic Delegation Discovery
System (DDDS) Application (ENUM)", RFC 3761, April 2004. System (DDDS) Application (ENUM)", RFC 3761, April 2004.
[RFC4725] Mayrhofer, A. and B. Hoeneisen, "ENUM Validation [RFC4725] Mayrhofer, A. and B. Hoeneisen, "ENUM Validation
Architecture", RFC 4725, November 2006. Architecture", RFC 4725, November 2006.
[RFC4732] Handley, M., Rescorla, E., and IAB, "Internet Denial-of- [RFC4732] Handley, M., Rescorla, E., IAB, "Internet Denial-of-
Service Considerations", RFC 4732, December 2006. Service Considerations", RFC 4732, December 2006.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, August 2008. (TLS) Protocol Version 1.2", RFC 5246, August 2008.
[RFC5321] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321, [RFC5321] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321,
October 2008. October 2008.
[RFC5486] Malas, D. and D. Meyer, "Session Peering for Multimedia [RFC5486] Malas, D. and D. Meyer, "Session Peering for Multimedia
Interconnect (SPEERMINT) Terminology", RFC 5486, Interconnect (SPEERMINT) Terminology", RFC 5486, March
March 2009. 2009.
[RFC5646] Phillips, A. and M. Davis, "Tags for Identifying [RFC5646] Phillips, A. and M. Davis, "Tags for Identifying
Languages", BCP 47, RFC 5646, September 2009. Languages", BCP 47, RFC 5646, September 2009.
[RFC6116] Bradner, S., Conroy, L., and K. Fujiwara, "The E.164 to [RFC6116] Bradner, S., Conroy, L., and K. Fujiwara, "The E.164 to
Uniform Resource Identifiers (URI) Dynamic Delegation Uniform Resource Identifiers (URI) Dynamic Delegation
Discovery System (DDDS) Application (ENUM)", RFC 6116, Discovery System (DDDS) Application (ENUM)", RFC 6116,
March 2011. March 2011.
[RFC6461] Channabasappa, S., "Data for Reachability of Inter-/ [RFC6461] Channabasappa, S., "Data for Reachability of Inter-/Intra-
Intra-NetworK SIP (DRINKS) Use Cases and Protocol NetworK SIP (DRINKS) Use Cases and Protocol Requirements",
Requirements", RFC 6461, January 2012. RFC 6461, January 2012.
[Unicode6.1] [Unicode6.1]
The Unicode Consortium, "The Unicode Standard - Version The Unicode Consortium, "The Unicode Standard - Version
6.1", Unicode 6.1, January 2012. 6.1", Unicode 6.1, January 2012.
Authors' Addresses Authors' Addresses
Kenneth Cartwright Kenneth Cartwright
TNS TNS
1939 Roland Clarke Place 1939 Roland Clarke Place
skipping to change at page 64, line 34 skipping to change at page 54, line 34
NeuStar NeuStar
46000 Center Oak Plaza 46000 Center Oak Plaza
Sterling, VA 20166 Sterling, VA 20166
USA USA
Email: syed.ali@neustar.biz Email: syed.ali@neustar.biz
David Schwartz David Schwartz
XConnect XConnect
316 Regents Park Road 316 Regents Park Road
London, N3 2XJ London N3 2XJ
United Kingdom United Kingdom
Email: dschwartz@xconnect.net Email: dschwartz@xconnect.net
 End of changes. 132 change blocks. 
537 lines changed or deleted 524 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/