draft-ietf-drinks-spp-protocol-over-soap-01.txt   draft-ietf-drinks-spp-protocol-over-soap-02.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: September 13, 2012 March 12, 2012 Expires: January 17, 2013 J-F. Mule
CableLabs
A. Mayrhofer
enum.at GmbH
July 16, 2012
Session Peering Provisioning (SPP) Protocol over SOAP Session Peering Provisioning (SPP) Protocol over SOAP
draft-ietf-drinks-spp-protocol-over-soap-01 draft-ietf-drinks-spp-protocol-over-soap-02
Abstract Abstract
The Session Peering Provisioning Framework (SPPF) is an XML framework The Session Peering Provisioning Framework (SPPF) is an XML framework
that exists to enable the provisioning of session establishment data that exists to enable the provisioning of session establishment data
into Session Data Registries or SIP Service Provider data stores. into Session Data Registries or SIP Service Provider data stores.
Sending XML data structures over Simple Object Access Protocol (SOAP) Sending XML data structures over Simple Object Access Protocol (SOAP)
and HTTP(s) is a widely used, de-facto standard for messaging between and HTTP(s) is a widely used, de-facto standard for messaging between
elements of provisioning systems. Therefore the combination of SOAP elements of provisioning systems. Therefore the combination of SOAP
and HTTP(s) as a transport protocol for SPPF is a natural fit. The and HTTP(s) as a transport protocol for SPPF is a natural fit. The
skipping to change at page 1, line 41 skipping to change at page 1, line 45
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 September 13, 2012. This Internet-Draft will expire on January 17, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 19 skipping to change at page 2, line 23
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 . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. SOAP Features and Protocol Layering . . . . . . . . . . . . . 6 3. SOAP Features and Protocol Layering . . . . . . . . . . . . . 6
4. HTTP(s) Features and SPP Protocol over SOAP . . . . . . . . . 9 4. HTTP(s) Features and SPP Protocol over SOAP . . . . . . . . . 9
5. Authentication and Session Management . . . . . . . . . . . . 10 5. Authentication and Session Management . . . . . . . . . . . . 10
6. SPP Protocol SOAP Data Structures . . . . . . . . . . . . . . 11 6. Language Identification . . . . . . . . . . . . . . . . . . . 11
6.1. Concrete Object Key Types . . . . . . . . . . . . . . . . 11 7. SPP Protocol SOAP Data Structures . . . . . . . . . . . . . . 12
6.1.1. Generic Object Key . . . . . . . . . . . . . . . . . . 11 7.1. Concrete Object Key Types . . . . . . . . . . . . . . . . 12
6.1.2. Public Identity Object Key . . . . . . . . . . . . . . 12 7.1.1. Generic Object Key . . . . . . . . . . . . . . . . . . 12
6.1.3. Route Group Offer Key . . . . . . . . . . . . . . . . 13 7.1.2. Public Identity Object Key . . . . . . . . . . . . . . 13
6.2. Operation Request and Response Structures . . . . . . . . 14 7.1.3. SED Group Offer Key . . . . . . . . . . . . . . . . . 14
6.2.1. Add Operation Structure . . . . . . . . . . . . . . . 14 7.2. Operation Request and Response Structures . . . . . . . . 15
6.2.2. Delete Operation Structure . . . . . . . . . . . . . . 17 7.2.1. Add Operation Structure . . . . . . . . . . . . . . . 15
6.2.3. Accept Operation Structure . . . . . . . . . . . . . . 20 7.2.2. Delete Operation Structure . . . . . . . . . . . . . . 18
6.2.4. Reject Operation Structure . . . . . . . . . . . . . . 24 7.2.3. Accept Operation Structure . . . . . . . . . . . . . . 21
6.2.5. Batch Operation Structure . . . . . . . . . . . . . . 27 7.2.4. Reject Operation Structure . . . . . . . . . . . . . . 24
6.2.6. Get Operation Structure . . . . . . . . . . . . . . . 30 7.2.5. Batch Operation Structure . . . . . . . . . . . . . . 27
6.2.7. Get Route Group Offers Operation Structure . . . . . . 32 7.2.6. Get Operation Structure . . . . . . . . . . . . . . . 30
6.2.8. Generic Query Response . . . . . . . . . . . . . . . . 33 7.2.7. Get SED Group Offers Operation Structure . . . . . . . 32
6.2.9. Get Server Details Operation Structure . . . . . . . . 34 7.2.8. Generic Query Response . . . . . . . . . . . . . . . . 33
6.3. Response Codes and Messages . . . . . . . . . . . . . . . 36 7.2.9. Get Server Details Operation Structure . . . . . . . . 34
7. Protocol Operations . . . . . . . . . . . . . . . . . . . . . 39 7.3. Response Codes and Messages . . . . . . . . . . . . . . . 35
8. SPP Protocol over SOAP WSDL Definition . . . . . . . . . . . . 40 8. Protocol Operations . . . . . . . . . . . . . . . . . . . . . 38
9. SPP Protocol over SOAP Examples . . . . . . . . . . . . . . . 52 9. SPP Protocol over SOAP WSDL Definition . . . . . . . . . . . . 39
9.1. Add Destination Group . . . . . . . . . . . . . . . . . . 52 10. SPP Protocol over SOAP Examples . . . . . . . . . . . . . . . 51
9.2. Add Route Records . . . . . . . . . . . . . . . . . . . . 54 10.1. Add Destination Group . . . . . . . . . . . . . . . . . . 51
9.3. Add Route Records -- URIRteRecType . . . . . . . . . . . . 55 10.2. Add SED Records . . . . . . . . . . . . . . . . . . . . . 53
9.4. Add Route Group . . . . . . . . . . . . . . . . . . . . . 56 10.3. Add SED Records -- URIType . . . . . . . . . . . . . . . 54
9.5. Add Public Identity -- Successful COR claim . . . . . . . 58 10.4. Add SED Group . . . . . . . . . . . . . . . . . . . . . . 55
9.6. Add LRN . . . . . . . . . . . . . . . . . . . . . . . . . 60 10.5. Add Public Identity -- Successful COR claim . . . . . . . 57
9.7. Add TN Range . . . . . . . . . . . . . . . . . . . . . . . 61 10.6. Add LRN . . . . . . . . . . . . . . . . . . . . . . . . . 59
9.8. Add TN Prefix . . . . . . . . . . . . . . . . . . . . . . 62 10.7. Add TN Range . . . . . . . . . . . . . . . . . . . . . . 60
9.9. Enable Peering -- Route Group Offer . . . . . . . . . . . 63 10.8. Add TN Prefix . . . . . . . . . . . . . . . . . . . . . . 61
9.10. Enable Peering -- Route Group Offer Accept . . . . . . . . 65 10.9. Enable Peering -- SED Group Offer . . . . . . . . . . . . 62
9.11. Add Egress Route . . . . . . . . . . . . . . . . . . . . . 66 10.10. Enable Peering -- SED Group Offer Accept . . . . . . . . 64
9.12. Remove Peering -- Route Group Offer Reject . . . . . . . . 68 10.11. Add Egress Route . . . . . . . . . . . . . . . . . . . . 65
9.13. Get Destination Group . . . . . . . . . . . . . . . . . . 69 10.12. Remove Peering -- SED Group Offer Reject . . . . . . . . 67
9.14. Get Public Identity . . . . . . . . . . . . . . . . . . . 71 10.13. Get Destination Group . . . . . . . . . . . . . . . . . . 68
9.15. Get Route Group Request . . . . . . . . . . . . . . . . . 72 10.14. Get Public Identity . . . . . . . . . . . . . . . . . . . 70
9.16. Get Route Group Offers Request . . . . . . . . . . . . . . 74 10.15. Get SED Group Request . . . . . . . . . . . . . . . . . . 71
9.17. Get Egress Route . . . . . . . . . . . . . . . . . . . . . 76 10.16. Get SED Group Offers Request . . . . . . . . . . . . . . 73
9.18. Delete Destination Group . . . . . . . . . . . . . . . . . 77 10.17. Get Egress Route . . . . . . . . . . . . . . . . . . . . 75
9.19. Delete Public Identity . . . . . . . . . . . . . . . . . . 78 10.18. Delete Destination Group . . . . . . . . . . . . . . . . 76
9.20. Delete Route Group Request . . . . . . . . . . . . . . . . 80 10.19. Delete Public Identity . . . . . . . . . . . . . . . . . 77
9.21. Delete Route Group Offers Request . . . . . . . . . . . . 81 10.20. Delete SED Group Request . . . . . . . . . . . . . . . . 79
9.22. Delete Egress Route . . . . . . . . . . . . . . . . . . . 82 10.21. Delete SED Group Offers Request . . . . . . . . . . . . . 80
9.23. Batch Request . . . . . . . . . . . . . . . . . . . . . . 83 10.22. Delete Egress Route . . . . . . . . . . . . . . . . . . . 81
10. Security Considerations . . . . . . . . . . . . . . . . . . . 86 10.23. Batch Request . . . . . . . . . . . . . . . . . . . . . . 82
10.1. Integrity, Privacy, and Authentication . . . . . . . . . . 86 11. Security Considerations . . . . . . . . . . . . . . . . . . . 85
10.2. Vulnerabilities . . . . . . . . . . . . . . . . . . . . . 86 11.1. Integrity, Privacy, and Authentication . . . . . . . . . 85
10.3. Deployment Environment Specifics . . . . . . . . . . . . . 87 11.2. Vulnerabilities . . . . . . . . . . . . . . . . . . . . . 85
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 88 11.3. Deployment Environment Specifics . . . . . . . . . . . . 86
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 89 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 87
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 90 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 88
13.1. Normative References . . . . . . . . . . . . . . . . . . . 90 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 89
13.2. Informative References . . . . . . . . . . . . . . . . . . 90 14.1. Normative References . . . . . . . . . . . . . . . . . . 89
14.2. Informative References . . . . . . . . . . . . . . . . . 89
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 91 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 91
1. Introduction 1. Introduction
SPPF, defined in [I-D.draft-ietf-drinks-spp-framework], is best SPPF, defined in [I-D.draft-ietf-drinks-spp-framework], is best
supported by a transport and messaging infrastructure that is supported by a transport and messaging infrastructure that is
connection oriented, request-response oriented, easily secured, connection oriented, request-response oriented, easily secured,
supports propagation through firewalls in a standard fashion, and supports propagation through firewalls in a standard fashion, and
that is easily integrated into back-office systems. This is due to that is easily integrated into back-office systems. This is due to
the fact that the client side of SPPF is likely to be integrated with the fact that the client side of SPPF is likely to be integrated with
skipping to change at page 7, line 18 skipping to change at page 7, line 18
+-------------+ +-------------+
| |
V V
+-------------+ +-------------+
(2) | Message |Example: (2) | Message |Example:
| Envelope | HTTP, SOAP, None, etc. | Envelope | HTTP, SOAP, None, etc.
+-------------+ +-------------+
| |
V V
+--------------+ +--------------+
+------| SOAP |-----+ +----| SOAP |---+
| (3) | Operation | | |(3) | Operation | |
Contains | +--------------+ | Contains Contains | +--------------+ | Contains
| Example: | | Example: |
V submitAddRqst V V submitAddRqst V
+--------------+ +-------------+ +--------------+ +-------------+
|SOAP Request | |SOAP Response| |SOAP Request | |SOAP Response|
Example:| Message | (4) | Message | Example: Example: | Message | (4) | Message | Example:
spppAdd | (Operation | | (Operation | spppAdd spppAdd | (Operation | | (Operation | spppAdd
RequestMsg | Input) | | Output) | ResponseMsg RequestMsg | Input) | | Output) | ResponseMsg
+--------------+ +-------------+ +--------------+ +-------------+
| | | |
Contains | | Contains Contains | | Contains
| | | |
V V V V
+---------------+ +---------------+ +---------------+ +---------------+
Example:| Wrapped | (5) | Wrapped | Example: Example: | Wrapped | (5) | Wrapped | Example:
spppAdd |Request Object | |Response Object| spppAdd spppAdd |Request Object | |Response Object| spppAdd
Request +---------------+ +---------------+ Response Request +---------------+ +---------------+ Response
| | | |
Contains | | Contains Contains | | Contains
| | | |
V V V V
+-------------+ +---------------+ +-------------+ +---------------+
| SPPF | | SPPF | | SPPF | | SPPF |
|XML Types | (6) | XML Types | |XML Types | (6) | XML Types |
+-------------+ +---------------+ +-------------+ +---------------+
Figure 1: Layering and Technical Structure of the SPP Protocol over Figure 1: Layering and Technical Structure of the SPP Protocol over
SOAP Messages SOAP Messages
The operations supported by SPP Protocol over SOAP are normatively The operations supported by SPP Protocol over SOAP are normatively
defined later in this document. Each SOAP operation defines a defined later in this document. Each SOAP operation defines a
request/input message and a response/output message. Each such request/input message and a response/output message. Each such
request and response message then contains a single object that wraps request and response message then contains a single object that wraps
the SPPF XML data types that comprise the inputs and the outputs, the SPPF XML data types that comprise the inputs and the outputs,
respectively, of the SOAP operation. respectively, of the SOAP operation.
skipping to change at page 11, line 5 skipping to change at page 11, line 5
To achieve integrity and privacy, conforming SPP Protocol SOAP To achieve integrity and privacy, conforming SPP Protocol SOAP
Clients and Servers MUST support SOAP over HTTP over TLS [RFC5246] as Clients and Servers MUST support SOAP over HTTP over TLS [RFC5246] as
the secure transport mechanism. This combination of HTTP and TLS is the secure transport mechanism. This combination of HTTP and TLS is
referred to as HTTPS. And to accomplish authentication, conforming referred to as HTTPS. And to accomplish authentication, conforming
SOAP SPPF Clients and Servers MUST use HTTP Digest Authentication as SOAP SPPF Clients and Servers MUST use HTTP Digest Authentication as
defined in [RFC2617]. As a result, the communication session is defined in [RFC2617]. As a result, the communication session is
established through the initial HTTP connection setup, the digest established through the initial HTTP connection setup, the digest
authentication, and the TLS handshake. When the HTTP connection is authentication, and the TLS handshake. When the HTTP connection is
broken down, the communication session ends. broken down, the communication session ends.
6. SPP Protocol SOAP Data Structures 6. Language Identification
Section 9 of [I-D.draft-ietf-drinks-spp-framework] requires transport
protocols to provide a mechanism to transmit language tags together
with human-readable messages. When conforming SPP Protocol SOAP
servers use such tagging, the XML "lang" attribute (see Section 2.12
of [W3C.REC-xml-20081126]) MUST be used for that purpose. Clients
MAY use the HTTP "Accept-Language" header field (see Section 14.4 of
[RFC2616]) in order to indicate their language preference.
7. SPP Protocol SOAP Data Structures
SPP Protocol over SOAP uses a set of XML based data structures for SPP Protocol over SOAP uses a set of XML based data structures for
all the supported operations and any parameters that those operations all the supported operations and any parameters that those operations
are applied to. As also mentioned earlier in this document, these are applied to. As also mentioned earlier in this document, these
XML structures are envelope-independent and transport-independent. XML structures are envelope-independent and transport-independent.
Refer the "Protocol Operations" section of this document for a Refer the "Protocol Operations" section of this document for a
description of all the operations that MUST be supported. description of all the operations that MUST be supported.
The following sections describe the definition all the XML data The following sections describe the definition all the XML data
structures. structures.
6.1. Concrete Object Key Types 7.1. Concrete Object Key Types
Certain operations in SPPF require an object key that uniquely Certain operations in SPPF require an object key that uniquely
identifies the object(s) on which a given operation needs to be identifies the object(s) on which a given operation needs to be
performed. SPPF defines the XML structure of the any such object key performed. SPPF defines the XML structure of the any such object key
in an abstact manner and delegates the concrete representation to any in an abstract manner and delegates the concrete representation to
conforming transport protocol. The following sub-sections define the any conforming transport protocol. The following sub-sections define
various types of concrete object key types used in various operations the various types of concrete object key types used in various
in SPP Protocol over SOAP: operations in SPP Protocol over SOAP:
6.1.1. Generic Object Key 7.1.1. Generic Object Key
Most objects in SPP Protocol over SOAP are uniquely identified by the Most objects in SPP Protocol over SOAP are uniquely identified by the
attributes in the generic object key (Refer "Generic Object Key Type" attributes in the generic object key (Refer "Generic Object Key Type"
section of the framework document for details). The concrete XML section of the framework document for details). The concrete XML
representation of ObjKeyType is as below: representation of ObjKeyType is as below:
<complexType name="ObjKeyType"> <complexType name="ObjKeyType">
<complexContent> <complexContent>
<extension base="sppfb:ObjKeyType"> <extension base="sppfb:ObjKeyType">
<sequence> <sequence>
skipping to change at page 12, line 11 skipping to change at page 13, line 11
</complexType> </complexType>
The ObjKeyType has the data elements as described below: The ObjKeyType has the data elements as described below:
o rant: The identifier of the registrant organization that owns o rant: The identifier of the registrant organization that owns
the object. the object.
o name: The character string that contains the name of the object. o name: The character string that contains the name of the object.
o type: The enumeration value that represents the type of SPPF o type: The enumeration value that represents the type of SPPF
object. For example, both a Destination Group and a Route Group object. For example, both a Destination Group and a SED Group
can have the same name "TestObj" and be associated with same can have the same name "TestObj" and be associated with same
Registrant Id "iana-en:222". Hence, to uniquely identify the Registrant Id "iana-en:222". Hence, to uniquely identify the
object that represents a Destination Group with the name object that represents a Destination Group with the name
"TestObj", the type "DestGrp" must be specified when using this "TestObj", the type "DestGrp" must be specified when using this
concrete ObjKeyType structure to identify the Destination Group concrete ObjKeyType structure to identify the Destination Group
"TestObj". "TestObj".
The object types in SPP Protocol over SOAP that MUST adhere to the The object types in SPP Protocol over SOAP that MUST adhere to the
above definition of generic object key are defined as an enumeration above definition of generic object key are defined as an enumeration
in the XML data structure. The structure of the the enumeration is in the XML data structure. The structure of the the enumeration is
as follows: as follows:
<simpleType name="ObjKeyTypeEnum"> <simpleType name="ObjKeyTypeEnum">
<restriction base="token"> <restriction base="token">
<enumeration value="RteGrp"/> <enumeration value="SedGrp"/>
<enumeration value="DestGrp"/> <enumeration value="DestGrp"/>
<enumeration value="RteRec"/> <enumeration value="SedRec"/>
<enumeration value="EgrRte"/> <enumeration value="EgrRte"/>
</restriction> </restriction>
</simpleType> </simpleType>
6.1.2. Public Identity Object Key 7.1.2. Public Identity Object Key
Public Identity type objects can further be of various sub-types like Public Identity type objects can further be of various sub-types like
a TN, RN, TN Prefix, URI, or a TN Range and cannot be cleanly a TN, RN, TN Prefix, URI, or a TN Range and cannot be cleanly
identified with the attributes in the generic ObjKeyType. The identified with the attributes in the generic ObjKeyType. The
definition of PubIdKeyType is as below: definition of PubIdKeyType is as below:
<complexType name="PubIdKeyType"> <complexType name="PubIdKeyType">
<complexContent> <complexContent>
<extension base="sppfb:PubIdKeyType"> <extension base="sppfb:PubIdKeyType">
<sequence> <sequence>
<element name="rant" type="sppfb:OrgIdType"/> <element name="rant" type="sppfb:OrgIdType"/>
<element name="dgName" type="sppfb:ObjNameType" minOccurs="0"/> <element name="dgName" type="sppfb:ObjNameType"
<choice> minOccurs="0"/>
<element name="number" <choice>
type="sppfb:NumberType"/> <element name="number"
<element name="range" type="sppfb:NumberType"/>
type="sppfb:NumberRangeType"/> <element name="range"
<element name="uri" type="sppfb:NumberRangeType"/>
type="anyURI"/> <element name="uri"
</choice> type="anyURI"/>
</sequence> </choice>
</extension> </sequence>
</complexContent> </extension>
</complexType> </complexContent>
</complexType>
The PubIdKeyType has the data elements as described below: The PubIdKeyType has the data elements as described below:
o rant: The identifier of the registrant organization that owns o rant: The identifier of the registrant organization that owns
the object. the object.
o dgName: The name of the Destination Group that a Public o dgName: The name of the Destination Group that a Public
Identifier is member of. Note that this is an optional Identifier is member of. Note that this is an optional
attribute of the key as Public Identifiers may or may not be attribute of the key as Public Identifiers may or may not be
provisioned as members of a Destination Group. provisioned as members of a Destination Group.
skipping to change at page 13, line 45 skipping to change at page 14, line 46
that contains the value and type of a number . that contains the value and type of a number .
o range: An element of type NumberRangeType (refer framework o range: An element of type NumberRangeType (refer framework
document) that contains a range of numbers. document) that contains a range of numbers.
o uri: A value that represents a Public Identifier. o uri: A value that represents a Public Identifier.
It is MUST that only one of the "number", "range", and "uri" elements It is MUST that only one of the "number", "range", and "uri" elements
appears in a PubIdKeyType instance. appears in a PubIdKeyType instance.
6.1.3. Route Group Offer Key 7.1.3. SED Group Offer Key
In addition to the attributes in the generic ObjKeyType, a Route In addition to the attributes in the generic ObjKeyType, a SED Group
Group Offer object is uniquely identified by the organization ID of Offer object is uniquely identified by the organization ID of the
the organization to whom an Route Group has been offered. The organization to whom an SED Group has been offered. The definition
definition of RteGrpOfferKeyType is as below: of SedGrpOfferKeyType is as below:
<complexType name="RteGrpOfferKeyType"> <complexType name="SedGrpOfferKeyType">
<complexContent> <complexContent>
<extension base="sppfb:RteGrpOfferKeyType"> <extension base="sppfb:SedGrpOfferKeyType">
<sequence> <sequence>
<element name="rteGrpKey" type="sppfs:ObjKeyType"/> <element name="sedGrpKey" type="sppfs:ObjKeyType"/>
<element name="offeredTo" type="sppfb:OrgIdType"/> <element name="offeredTo" type="sppfb:OrgIdType"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
The RteGrpOfferKeyType has the data elements as described below: The SedGrpOfferKeyType has the data elements as described below:
o rteGrpKey: Identifies the Route Group that was offered. o sedGrpKey: Identifies the SED Group that was offered.
o offeredTo: The organization ID of the organization that was o offeredTo: The organization ID of the organization that was
offered the Route Group object identified by the rteGrpKey. offered the SED Group object identified by the sedGrpKey.
6.2. Operation Request and Response Structures 7.2. Operation Request and Response Structures
An SPPF client interacts with an SPPF server by using one of the An SPPF client interacts with an SPPF server by using one of the
supported transport mechanisms to send one or more requests to the supported transport mechanisms to send one or more requests to the
server and receive corresponding replies from the server. The basic server and receive corresponding replies from the server. The basic
set of operations that an SPPF client can submit to an SPPF server set of operations that an SPPF client can submit to an SPPF server
and the semantics of those operations are defined in the "Framework and the semantics of those operations are defined in the "Framework
Operations" section of the framework document. The following sub- Operations" section of the framework document. The following sub-
sections describe the XML data structures that are used for each of sections describe the XML data structures that are used for each of
those types of operations for a SPP Protocol over SOAP those types of operations for a SPP Protocol over SOAP
implementation. implementation.
6.2.1. Add Operation Structure 7.2.1. Add Operation Structure
In order to add (or modify) an object in the registry, an authorized In order to add (or modify) an object in the registry, an authorized
entity can send the spppAddRequest to the registry. entity can send the spppAddRequest to the registry.
An SPP Protocol over SOAP Add request is wrapped within the An SPP Protocol over SOAP Add request is wrapped within the
<spppAddRequest> element while an SPP Protocol over SOAP Add response <spppAddRequest> element while an SPP Protocol over SOAP Add response
is wrapped within an <spppAddResponse> element. The following sub- is wrapped within an <spppAddResponse> element. The following sub-
sections describe the spppAddRequest and spppAddResponse elements. sections describe the spppAddRequest and spppAddResponse elements.
Refer the "SPP Protocol over SOAP Examples" section of this document Refer the "SPP Protocol over SOAP Examples" section of this document
for an example of Add operation on each type of SPPF object. for an example of Add operation on each type of SPPF object.
6.2.1.1. Add Request 7.2.1.1. Add Request
An SPP Protocol over SOAP Add request definition is contained within An SPP Protocol over SOAP Add request definition is contained within
the generic <spppAddRequest> element. the generic <spppAddRequest> element.
<element name="spppAddRequest"> <element name="spppAddRequest">
<complexType> <complexType>
<sequence> <sequence>
<element name="clientTransId" <element name="clientTransId"
type="sppfb:TransIdType" minOccurs="0"/> type="sppfb:TransIdType" minOccurs="0"/>
<element name="minorVer" <element name="minorVer"
skipping to change at page 15, line 49 skipping to change at page 17, line 9
o obj: One or more elements of abstract type BasicObjType (defined o obj: One or more elements of abstract type BasicObjType (defined
in the framework document). Each element contains all the in the framework document). Each element contains all the
attributes of an SPPF object that that the client is requesting attributes of an SPPF object that that the client is requesting
the SPPF server to add. Refer the "Framework Data Model the SPPF server to add. Refer the "Framework Data Model
Objects" section of the framework document for the XML structure Objects" section of the framework document for the XML structure
of all concrete types, for various SPPF objects, that extend of all concrete types, for various SPPF objects, that extend
from abstract BasicObjType and hence are eligible to be passed from abstract BasicObjType and hence are eligible to be passed
into this element. The elements are processed by the SPPF into this element. The elements are processed by the SPPF
server in the order in which they are included in the request. server in the order in which they are included in the request.
With respect to handling of error conditions, it is a matter of With respect to handling of error conditions, conforming SPPP
policy whether the objects are processed in a "stop and SOAP servers MUST stop processing BasicObjType elements in the
rollback" fashion or in a "stop and commit" fashion. In the request at the first error, and roll back any BasicObjType
"stop and rollback" scenario, the SPPF server would stop elements that had already been processed for that add request
processing BasicObjType elements in the request at the first ("stop and rollback").
error and roll back any BasicObjType elements that had already
been processed for that add request. In the "stop and commit"
scenario the SPPF server would stop processing BasicObjType
elements in the request at the first error but commit any
BasicObjType elements that had already been processed for that
add request.
6.2.1.2. Add Response 7.2.1.2. Add Response
An SPP Protocol over SOAP add response object is contained within the An SPP Protocol over SOAP add response object is contained within the
generic <spppAddResponse> element. This response structure is used generic <spppAddResponse> element. This response structure is used
for all types of SPPF objects that are provisioned by the SPPF for all types of SPPF objects that are provisioned by the SPPF
client. client.
<element name="spppAddResponse"> <element name="spppAddResponse">
<complexType> <complexType>
<sequence> <sequence>
<element name="clientTransId" type="sppfb:TransIdType" <element name="clientTransId" type="sppfb:TransIdType"
skipping to change at page 17, line 35 skipping to change at page 18, line 37
Response Code section for further details. Response Code section for further details.
o detailResult: An optional response code, response message, and o detailResult: An optional response code, response message, and
BasicObjType (as defined in the framework document) triplet. BasicObjType (as defined in the framework document) triplet.
This element will be present only if an object level error has This element will be present only if an object level error has
occurred. It indicates the error condition and the exact occurred. It indicates the error condition and the exact
request object that contributed to the error. The response code request object that contributed to the error. The response code
will reflect the exact error. See the Response Code section for will reflect the exact error. See the Response Code section for
further details. further details.
6.2.2. Delete Operation Structure 7.2.2. Delete Operation Structure
In order to remove an object from the registry, an authorized entity In order to remove an object from the registry, an authorized entity
can send the spppDelRequest into the registry. An SPP Protocol over can send the spppDelRequest into the registry. An SPP Protocol over
SOAP Delete request is wrapped within the <spppDelRequest> element SOAP Delete request is wrapped within the <spppDelRequest> element
while a SPP Protocol over SOAP Delete response is wrapped within the while a SPP Protocol over SOAP Delete response is wrapped within the
generic <spppDelResponse> element. The following sub-sections generic <spppDelResponse> element. The following sub-sections
describe the spppDelRequest and spppDelResponse elements. Refer the describe the spppDelRequest and spppDelResponse elements. Refer the
"SPP Protocol over SOAP Examples" section of this document for an "SPP Protocol over SOAP Examples" section of this document for an
example of Delete operation on each type of SPPF object. example of Delete operation on each type of SPPF object.
6.2.2.1. Delete Request 7.2.2.1. Delete Request
An SPP Protocol over SOAP Delete request definition is contained An SPP Protocol over SOAP Delete request definition is contained
within the generic <spppDelRequest> element. within the generic <spppDelRequest> element.
<element name="spppDelRequest"> <element name="spppDelRequest">
<complexType> <complexType>
<sequence> <sequence>
<element name="clientTransId" <element name="clientTransId"
type="sppfb:TransIdType" minOccurs="0"/> type="sppfb:TransIdType" minOccurs="0"/>
<element name="minorVer" <element name="minorVer"
skipping to change at page 18, line 48 skipping to change at page 20, line 9
in the document. in the document.
o objKey: One or more elements of abstract type ObjKeyType (as o objKey: One or more elements of abstract type ObjKeyType (as
defined in the framework document). Each element contains defined in the framework document). Each element contains
attributes that uniquely identify the object that the client is attributes that uniquely identify the object that the client is
requesting the server to delete. Refer the "Concrete Object requesting the server to delete. Refer the "Concrete Object
Keys" section of this document for a description of all concrete Keys" section of this document for a description of all concrete
object key types, for various SPPF objects, which are eligible object key types, for various SPPF objects, which are eligible
to be passed into this element. The elements are processed by to be passed into this element. The elements are processed by
the SPPF server in the order in which they are included in the the SPPF server in the order in which they are included in the
request. With respect to handling of error conditions, it is a request. With respect to handling of error conditions,
matter of policy whether the objects are processed in a "stop conforming SPPP SOAP servers MUST stop processing ObjKeyType
and rollback" fashion or in a "stop and commit" fashion. In the elements in the request at the first error, and roll back any
"stop and rollback" scenario, the SPPF server would stop ObjKeyType elements that had already been processed for that
processing ObjKeyType elements in the request at the first error delete request ("stop and rollback").
and roll back any ObjKeyType elements that had already been
processed for that delete request. In the "stop and commit"
scenario the SPPF server would stop processing ObjKeyType
elements in the request at the first error but commit any
KeyParamType elements that had already been processed for that
delete request.
6.2.2.2. Delete Response 7.2.2.2. Delete Response
An SPP Protocol over SOAP delete response object is contained within An SPP Protocol over SOAP delete response object is contained within
the generic <sppDeleteResponse> element. This response structure is the generic <sppDeleteResponse> element. This response structure is
used for a delete request on all types of SPPF objects that are used for a delete request on all types of SPPF objects that are
provisioned by the SPPF client. provisioned by the SPPF client.
<element name="spppDelResponse"> <element name="spppDelResponse">
<complexType> <complexType>
<sequence> <sequence>
<element name="clientTransId" type="sppfb:TransIdType" <element name="clientTransId" type="sppfb:TransIdType"
minOccurs="0"/> minOccurs="0"/>
<element name="serverTransId" type="sppfb:TransIdType"/> <element name="serverTransId" type="sppfb:TransIdType"/>
<element name="overallResult" type="sppfb:ResultCodeType"/> <element name="overallResult" type="sppfb:ResultCodeType"/>
<element name="detailResult" type="sppfs:ObjKeyResultCodeType" <element name="detailResult" type="sppfs:ObjKeyResultCodeType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
</element> </element>
<complexType name="ResultCodeType"> <complexType name="ResultCodeType">
<sequence>
<element name="code" type="int"/>
<element name="msg" type="string"/>
</sequence>
</complexType>
<complexType name="ObjKeyResultCodeType">
<complexContent>
<extension base="sppfs:ResultCodeType">
<sequence> <sequence>
<element name="code" type="int"/> <element name="objKey" type="sppfb:ObjKeyType"/>
<element name="msg" type="string"/>
</sequence> </sequence>
</complexType> </extension>
</complexContent>
<complexType name="ObjKeyResultCodeType"> </complexType>
<complexContent>
<extension base="sppfs:ResultCodeType">
<sequence>
<element name="objKey" type="sppfb:ObjKeyType"/>
</sequence>
</extension>
</complexContent>
</complexType>
An <spppDelResponse> contains the elements necessary for the SPPF An <spppDelResponse> contains the elements necessary for the SPPF
client to precisely determine the overall result of the request, and client to precisely determine the overall result of the request, and
if an error occurred, it provides information about the specific if an error occurred, it provides information about the specific
object key(s) that caused the error. object key(s) that caused the error.
The data elements within the SPP Protocol over SOAP Delete response The data elements within the SPP Protocol over SOAP Delete response
are described as follows: are described as follows:
o clientTransId: Zero or one client transaction ID. This value is o clientTransId: Zero or one client transaction ID. This value is
skipping to change at page 20, line 35 skipping to change at page 21, line 37
Response Code section for further details. Response Code section for further details.
o detailResult: An optional response code, response message, and o detailResult: An optional response code, response message, and
ObjKeyType (as defined in the framework document) triplet. This ObjKeyType (as defined in the framework document) triplet. This
element will be present only if an specific object key level element will be present only if an specific object key level
error has occurred. It indicates the error condition and the error has occurred. It indicates the error condition and the
exact request object key that contributed to the error. The exact request object key that contributed to the error. The
response code will reflect the exact error. See the Response response code will reflect the exact error. See the Response
Code section for further details. Code section for further details.
6.2.3. Accept Operation Structure 7.2.3. Accept Operation Structure
In SPPF, a Route Group Offer can be accepted or rejected by, or on In SPPF, a SED Group Offer can be accepted or rejected by, or on
behalf of, the registrant to whom the Route Group has been offered behalf of, the registrant to whom the SED Group has been offered
(refer "Framework Data Model Objects" section of the framework (refer "Framework Data Model Objects" section of the framework
document for a description of the Route Group Offer object). The document for a description of the SED Group Offer object). The
Accept operation is used to accept such Route Group Offers by, or on Accept operation is used to accept such SED Group Offers by, or on
behalf of, the Registrant. The request structure for an SPP Protocol behalf of, the Registrant. The request structure for an SPP Protocol
over SOAP Accept operation is wrapped within the <spppAcceptRequest> over SOAP Accept operation is wrapped within the <spppAcceptRequest>
element while an SPP Protocol over SOAP Accept response is wrapped element while an SPP Protocol over SOAP Accept response is wrapped
within the generic <spppAcceptResponse> element. The following sub- within the generic <spppAcceptResponse> element. The following sub-
sections describe the spppAcceptRequest and spppAcceptResponse sections describe the spppAcceptRequest and spppAcceptResponse
elements. Refer the "SPP Protocol over SOAP Examples" section of elements. Refer the "SPP Protocol over SOAP Examples" section of
this document for an example of Accept operation on a Route Group this document for an example of Accept operation on a SED Group
Offer. Offer.
6.2.3.1. Accept Request Structure 7.2.3.1. Accept Request Structure
An SPP Protocol over SOAP Accept request definition is contained An SPP Protocol over SOAP Accept request definition is contained
within the generic <sppAcceptRequest> element. within the generic <sppAcceptRequest> element.
<element name="spppAcceptRequest"> <element name="spppAcceptRequest">
<complexType> <complexType>
<sequence> <sequence>
<element name="clientTransId" <element name="clientTransId"
type="sppfb:TransIdType" minOccurs="0"/> type="sppfb:TransIdType" minOccurs="0"/>
<element name="minorVer" <element name="minorVer"
type="sppfb:MinorVerType" minOccurs="0"/> type="sppfb:MinorVerType" minOccurs="0"/>
<element name="rteGrpOfferKey" <element name="sedGrpOfferKey"
type="sppfs:RteGrpOfferKeyType" type="sppfs:SedGrpOfferKeyType"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
</element> </element>
The data elements within the <spppAcceptRequest> element are The data elements within the <spppAcceptRequest> element are
described as follows: described as follows:
o clientTransId: Zero or one client-generated transaction ID that, o clientTransId: Zero or one client-generated transaction ID that,
within the context of the SPPF client, identifies this request. within the context of the SPPF client, identifies this request.
skipping to change at page 21, line 46 skipping to change at page 23, line 5
minor version of the SPPF API that the client is attempting to minor version of the SPPF API that the client is attempting to
use. This is used in conjunction with the major version use. This is used in conjunction with the major version
identifier in the XML namespace to identify the version of SPPF identifier in the XML namespace to identify the version of SPPF
that the client is using. If the element is not present, the that the client is using. If the element is not present, the
server assumes that the client is using the latest minor version server assumes that the client is using the latest minor version
supported by the SPPF server for the given major version. The supported by the SPPF server for the given major version. The
versions supported by a given SPPF server can be retrieved by versions supported by a given SPPF server can be retrieved by
the client using the SPPF server menu operation described later the client using the SPPF server menu operation described later
in the document. in the document.
o rteGrpOfferKey: One or more elements of type RteGrpOfferKeyType o sedGrpOfferKey: One or more elements of type SedGrpOfferKeyType
(as defined in this document). Each element contains attributes (as defined in this document). Each element contains attributes
that uniquely identify a Route Group Offer that the client is that uniquely identify a SED Group Offer that the client is
requesting the server to accept. The elements are processed by requesting the server to accept. The elements are processed by
the SPPF server in the order in which they are included in the the SPPF server in the order in which they are included in the
request. With respect to handling of error conditions, it is a request. With respect to handling of error conditions,
matter of policy whether the objects are processed in a "stop conforming SPPP SOAP servers MUST stop processing
and rollback" fashion or in a "stop and commit" fashion. In the SedGrpOfferKeyType elements in the request at the first error,
"stop and rollback" scenario, the SPPF server would stop and roll back any SedGrpOfferKeyType elements that had already
processing RteGrpOfferKeyType elements in the request at the been processed for that accept request ("stop and rollback").
first error and roll back any RteGrpOfferKeyType elements that
had already been processed for that accept request. In the
"stop and commit" scenario the SPPF server would stop processing
RteGrpOfferKeyType elements in the request at the first error
but commit any RteGrpOfferKeyType elements that had already been
processed for that accept request.
6.2.3.2. Accept Response 7.2.3.2. Accept Response
An SPP Protocol over SOAP accept response structure is contained An SPP Protocol over SOAP accept response structure is contained
within the generic <sppAcceptResponse> element. This response within the generic <sppAcceptResponse> element. This response
structure is used for an Accept request on a Route Group Offer. structure is used for an Accept request on a SED Group Offer.
<element name="spppAcceptResponse"> <element name="spppAcceptResponse">
<complexType> <complexType>
<sequence> <sequence>
<element name="clientTransId" type="sppfb:TransIdType" <element name="clientTransId" type="sppfb:TransIdType"
minOccurs="0"/> minOccurs="0"/>
<element name="serverTransId" type="sppfb:TransIdType"/> <element name="serverTransId" type="sppfb:TransIdType"/>
<element name="overallResult" type="sppfb:ResultCodeType"/> <element name="overallResult" type="sppfb:ResultCodeType"/>
<element name="detailResult" <element name="detailResult"
type="sppfs:RteGrpOfferKeyResultCodeType" type="sppfs:SedGrpOfferKeyResultCodeType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
</element> </element>
<complexType name="ResultCodeType"> <complexType name="ResultCodeType">
<sequence> <sequence>
<element name="code" type="int"/> <element name="code" type="int"/>
<element name="msg" type="string"/> <element name="msg" type="string"/>
</sequence> </sequence>
</complexType> </complexType>
<complexType name="RteGrpOfferKeyResultCodeType"> <complexType name="SedGrpOfferKeyResultCodeType">
<complexContent> <complexContent>
<extension base="sppfs:ResultCodeType"> <extension base="sppfs:ResultCodeType">
<sequence> <sequence>
<element name="rteGrpOfferKey" type="sppfs:RteGrpOfferKeyType"/> <element name="sedGrpOfferKey" type="sppfs:SedGrpOfferKeyType"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
An <spppAcceptResponse> contains the elements necessary for the SPPF An <spppAcceptResponse> contains the elements necessary for the SPPF
client to precisely determine the overall result of the request, and client to precisely determine the overall result of the request, and
if an error occurred, it provides information about the specific if an error occurred, it provides information about the specific SED
Route Group Offer key(s) that caused the error. Group Offer key(s) that caused the error.
The data elements within the SPP Protocol over SOAP Accept response The data elements within the SPP Protocol over SOAP Accept response
are described as follows: are described as follows:
o clientTransId: Zero or one client transaction ID. This value is o clientTransId: Zero or one client transaction ID. This value is
simply an echo of the client transaction ID that SPPF client simply an echo of the client transaction ID that SPPF client
passed into the SPPF update request. When included in the passed into the SPPF update request. When included in the
request, the SPPF server MUST return it in the corresponding request, the SPPF server MUST return it in the corresponding
response message. response message.
o serverTransId: Exactly one server transaction ID that identifies o serverTransId: Exactly one server transaction ID that identifies
this request for tracking purposes. This value MUST be unique this request for tracking purposes. This value MUST be unique
for a given SPPF server. for a given SPPF server.
o overallResult: Exactly one response code and message pair that o overallResult: Exactly one response code and message pair that
explicitly identifies the result of the request. See the explicitly identifies the result of the request. See the
Response Code section for further details. Response Code section for further details.
o detailResult: An optional response code, response message, and o detailResult: An optional response code, response message, and
RteGrpOfferKeyType (as defined in this document) triplet. This SedGrpOfferKeyType (as defined in this document) triplet. This
element will be present only if any specific Route Group Offer element will be present only if any specific SED Group Offer key
key level error has occurred. It indicates the error condition level error has occurred. It indicates the error condition and
and the exact request Route Group Offer key that contributed to the exact request SED Group Offer key that contributed to the
the error. The response code will reflect the exact error. See error. The response code will reflect the exact error. See the
the Response Code section for further details. Response Code section for further details.
6.2.4. Reject Operation Structure 7.2.4. Reject Operation Structure
In SPPF, Route Group Offer can be accepted or rejected by, or on In SPPF, SED Group Offer can be accepted or rejected by, or on behalf
behalf of, the registrant to whom the Route Group has been offered of, the registrant to whom the SED Group has been offered (refer
(refer "Framework Data Model Objects" section of the framerwork "Framework Data Model Objects" section of the framework document for
document for a description of the Route Group Offer object). The a description of the SED Group Offer object). The Reject operation
Reject operation is used to reject such Route Group Offers by, or on is used to reject such SED Group Offers by, or on behalf of, the
behalf of, the Registrant. The request structure for an SPP Protocol Registrant. The request structure for an SPP Protocol over SOAP
over SOAP Reject operation is wrapped within the <spppRejectRequest> Reject operation is wrapped within the <spppRejectRequest> element
element while an SPP Protocol over SOAP Reject response is wrapped while an SPP Protocol over SOAP Reject response is wrapped within the
within the generic <spppRejecResponse> element. The following sub- generic <spppRejecResponse> element. The following sub-sections
sections describe the spppRejectRequest and spppRejecResponse describe the spppRejectRequest and spppRejecResponse elements. Refer
elements. Refer the "SPP Protocol over SOAP Examples" section of the "SPP Protocol over SOAP Examples" section of this document for an
this document for an example of Reject operation on a Route Group example of Reject operation on a SED Group Offer.
Offer.
6.2.4.1. Reject Request 7.2.4.1. Reject Request
An SPP Protocol over SOAP Reject request definition is contained An SPP Protocol over SOAP Reject request definition is contained
within the generic <spppRejectRequest> element. within the generic <spppRejectRequest> element.
<element name="spppRejectRequest"> <element name="spppRejectRequest">
<complexType> <complexType>
<sequence> <sequence>
<element name="clientTransId" <element name="clientTransId"
type="sppfb:TransIdType" minOccurs="0"/> type="sppfb:TransIdType" minOccurs="0"/>
<element name="minorVer" <element name="minorVer"
type="sppfb:MinorVerType" minOccurs="0"/> type="sppfb:MinorVerType" minOccurs="0"/>
<element name="rteGrpOfferKey" <element name="sedGrpOfferKey"
type="sppfs:RteGrpOfferKeyType" type="sppfs:SedGrpOfferKeyType"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</complexType> </complexType>
</element> </element>
The data elements within the <spppRejectRequest> element are The data elements within the <spppRejectRequest> element are
described as follows: described as follows:
o clientTransId: Zero or one client-generated transaction ID that, o clientTransId: Zero or one client-generated transaction ID that,
within the context of the SPPF client, identifies this request. within the context of the SPPF client, identifies this request.
This value can be used at the discretion of the SPPF client to This value can be used at the discretion of the SPPF client to
skipping to change at page 25, line 40 skipping to change at page 25, line 45
minor version of the SPPF API that the client is attempting to minor version of the SPPF API that the client is attempting to
use. This is used in conjunction with the major version use. This is used in conjunction with the major version
identifier in the XML namespace to identify the version of SPPF identifier in the XML namespace to identify the version of SPPF
that the client is using. If the element is not present, the that the client is using. If the element is not present, the
server assumes that the client is using the latest minor version server assumes that the client is using the latest minor version
supported by the SPPF server for the given major version. The supported by the SPPF server for the given major version. The
versions supported by a given SPPF server can be retrieved by versions supported by a given SPPF server can be retrieved by
the client using the SPPF server menu operation described later the client using the SPPF server menu operation described later
in the document. in the document.
o rteGrpOfferKey: One or more elements of type RteGrpOfferKeyType o sedGrpOfferKey: One or more elements of type SedGrpOfferKeyType
(as defined in this document). Each element contains attributes (as defined in this document). Each element contains attributes
that uniquely identify a Route Group Offer that the client is that uniquely identify a SED Group Offer that the client is
requesting the server to reject. The elements are processed by requesting the server to reject. The elements are processed by
the SPPF server in the order in which they are included in the the SPPF server in the order in which they are included in the
request. With respect to handling of error conditions, it is a request. With respect to handling of error conditions,
matter of policy whether the objects are processed in a "stop conforming SPPP SOAP servers MUST stop processing
and rollback" fashion or in a "stop and commit" fashion. In the SedGrpOfferKeyType elements in the request at the first error,
"stop and rollback" scenario, the SPPF server would stop and roll back any SedGrpOfferKeyType elements that had already
processing RteGrpOfferKeyType elements in the request at the been processed for that reject request ("stop and rollback").
first error and roll back any RteGrpOfferKeyType elements that
had already been processed for that reject request. In the
"stop and commit" scenario the SPPF server would stop processing
RteGrpOfferKeyType elements in the request at the first error
but commit any RteGrpOfferKeyType elements that had already been
processed for that reject request.
6.2.4.2. Reject Response 7.2.4.2. Reject Response
An SPP Protocol over SOAP reject response structure is contained An SPP Protocol over SOAP reject response structure is contained
within the generic <sppRejectResponse> element. This response within the generic <sppRejectResponse> element. This response
structure is used for an Reject request on a Route Group Offer. structure is used for an Reject request on a SED Group Offer.
<element name="spppRejectResponse"> <element name="spppRejectResponse">
<complexType> <complexType>
<sequence> <sequence>
<element name="clientTransId" type="sppfb:TransIdType" <element name="clientTransId" type="sppfb:TransIdType"
minOccurs="0"/> minOccurs="0"/>
<element name="serverTransId" type="sppfb:TransIdType"/> <element name="serverTransId" type="sppfb:TransIdType"/>
<element name="overallResult" type="sppfb:ResultCodeType"/> <element name="overallResult" type="sppfb:ResultCodeType"/>
<element name="detailResult" <element name="detailResult"
type="sppfs:RteGrpOfferKeyResultCodeType" type="sppfs:SedGrpOfferKeyResultCodeType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
</element> </element>
<complexType name="ResultCodeType"> <complexType name="ResultCodeType">
<sequence> <sequence>
<element name="code" type="int"/> <element name="code" type="int"/>
<element name="msg" type="string"/> <element name="msg" type="string"/>
</sequence> </sequence>
</complexType> </complexType>
<complexType name="RteGrpOfferKeyResultCodeType"> <complexType name="SedGrpOfferKeyResultCodeType">
<complexContent> <complexContent>
<extension base="sppfs:ResultCodeType"> <extension base="sppfs:ResultCodeType">
<sequence> <sequence>
<element name="rteGrpOfferKey" type="sppfs:RteGrpOfferKeyType"/> <element name="sedGrpOfferKey" type="sppfs:SedGrpOfferKeyType"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
An <spppRejectResponse> contains the elements necessary for the SPPF An <spppRejectResponse> contains the elements necessary for the SPPF
client to precisely determine the overall result of the request, and client to precisely determine the overall result of the request, and
if an error occurred, it provides information about the specific if an error occurred, it provides information about the specific SED
Route Group Offer key(s) that caused the error. Group Offer key(s) that caused the error.
The data elements within the SPP Protocol over SOAP Reject response The data elements within the SPP Protocol over SOAP Reject response
are described as follows: are described as follows:
o clientTransId: Zero or one client transaction ID. This value is o clientTransId: Zero or one client transaction ID. This value is
simply an echo of the client transaction ID that SPPF client simply an echo of the client transaction ID that SPPF client
passed into the SPPF update request. When included in the passed into the SPPF update request. When included in the
request, the SPPF server MUST return it in the corresponding request, the SPPF server MUST return it in the corresponding
response message. response message.
o serverTransId: Exactly one server transaction ID that identifies o serverTransId: Exactly one server transaction ID that identifies
this request for tracking purposes. This value MUST be unique this request for tracking purposes. This value MUST be unique
for a given SPPF server. for a given SPPF server.
o overallResult: Exactly one response code and message pair that o overallResult: Exactly one response code and message pair that
explicitly identifies the result of the request. See the explicitly identifies the result of the request. See the
Response Code section for further details. Response Code section for further details.
o detailResult: An optional response code, response message, and o detailResult: An optional response code, response message, and
RteGrpOfferKeyType (as defined in this document) triplet. This SedGrpOfferKeyType (as defined in this document) triplet. This
element will be present only if any specific Route Group Offer element will be present only if any specific SED Group Offer key
key level error has occurred. It indicates the error condition level error has occurred. It indicates the error condition and
and the exact request Route Group Offer key that contributed to the exact request SED Group Offer key that contributed to the
the error. The response code will reflect the exact error. See error. The response code will reflect the exact error. See the
the Response Code section for further details. Response Code section for further details.
6.2.5. Batch Operation Structure 7.2.5. Batch Operation Structure
An SPP Protocol over SOAP Batch request XML structure allows the SPPF An SPP Protocol over SOAP Batch request XML structure allows the SPPF
client to send any of of Add, Del, Accept or Reject operations client to send any of of Add, Del, Accept or Reject operations
together in one single request. This gives an SPPF Client the together in one single request. This gives an SPPF Client the
flexibility to use one single request structure to perform more than flexibility to use one single request structure to perform more than
operations (verbs). The batch request structure is wrapped within operations (verbs). The batch request structure is wrapped within
the <spppBatchRequest> element while a SPPF Batch response is wrapped the <spppBatchRequest> element while a SPPF Batch response is wrapped
within the <spppBatchResponse> element. This following sub-sections within the <spppBatchResponse> element. This following sub-sections
describe the spppBatchRequest and spppBatchResponse elements. Refer describe the spppBatchRequest and spppBatchResponse elements. Refer
the "SPP Protocol over SOAP Examples" section of this document for an the "SPP Protocol over SOAP Examples" section of this document for an
example of a batch operation. example of a batch operation.
6.2.5.1. Batch Request Structure 7.2.5.1. Batch Request Structure
An SPP Protocol over SOAP Batch request definition is contained An SPP Protocol over SOAP Batch request definition is contained
within the generic <spppBatchRequest> element. within the generic <spppBatchRequest> element.
<element name="spppBatchRequest"> <element name="spppBatchRequest">
<complexType> <complexType>
<sequence> <sequence>
<element name="clientTransId" <element name="clientTransId"
type="sppfb:TransIdType" minOccurs="0"/> type="sppfb:TransIdType" minOccurs="0"/>
<element name="minorVer" <element name="minorVer"
type="sppfb:MinorVerType" minOccurs="0"/> type="sppfb:MinorVerType" minOccurs="0"/>
<choice minOccurs="1" maxOccurs="unbounded"> <choice minOccurs="1" maxOccurs="unbounded">
<element name="addObj" type="sppfb:BasicObjType"/> <element name="addObj" type="sppfb:BasicObjType"/>
<element name="delObj" type="sppfb:ObjKeyType"/> <element name="delObj" type="sppfb:ObjKeyType"/>
<element name="acceptRteGrpOffer" <element name="acceptSedGrpOffer"
type="sppfs:RteGrpOfferKeyType"/> type="sppfs:SedGrpOfferKeyType"/>
<element name="rejectRteGrpOffer" <element name="rejectSedGrpOffer"
type="sppfs:RteGrpOfferKeyType"/> type="sppfs:SedGrpOfferKeyType"/>
</choice> </choice>
</sequence> </sequence>
</complexType> </complexType>
</element> </element>
The data elements within the <sppBatchRequest> element are described The data elements within the <sppBatchRequest> element are described
as follows: as follows:
o clientTransId: Zero or one client-generated transaction ID that, o clientTransId: Zero or one client-generated transaction ID that,
within the context of the SPPF client, identifies this request. within the context of the SPPF client, identifies this request.
skipping to change at page 29, line 5 skipping to change at page 29, line 5
the client using the SPPF server menu operation described later the client using the SPPF server menu operation described later
in the document. in the document.
o addObj: One or more elements of abstract type BasicObjType where o addObj: One or more elements of abstract type BasicObjType where
each element identifies an object that needs to be added. each element identifies an object that needs to be added.
o delObj: One or more elements of abstract type ObjKeyType where o delObj: One or more elements of abstract type ObjKeyType where
each element identifies a key for the object that needs to be each element identifies a key for the object that needs to be
deleted . deleted .
o acceptRteGrpOffer: One or more elements of type o acceptSedGrpOffer: One or more elements of type
RteGrpOfferKeyType where each element identifies a Route Group SedGrpOfferKeyType where each element identifies a SED Group
Offer that needs to be accepted. Offer that needs to be accepted.
o rejectRteGrpOffer: One or more elements of type o rejectSedGrpOffer: One or more elements of type
RteGrpOfferKeyType where each element identifies a Route Group SedGrpOfferKeyType where each element identifies a SED Group
Offer that needs to be rejected. Offer that needs to be rejected.
With respect to handling of error conditions, it is a matter of With respect to handling of error conditions, conforming SPPP SOAP
policy whether the batch operation processed in a "stop and rollback" servers MUST stop processing elements in the request at the first
fashion or in a "stop and commit" fashion. In the "stop and error, and roll back any elements that had already been processed for
rollback" scenario, the SPPF server would stop processing elements in that batch request ("stop and rollback").
the request at the first error and roll back any elements that had
already been processed for that batch request. In the "stop and
commit" scenario the SPPF server would stop processing elements in
the request at the first error but commit any elements that had
already been processed for that batch request.
6.2.5.2. Batch Response 7.2.5.2. Batch Response
An SPP Protocol over SOAP batch response structure is contained An SPP Protocol over SOAP batch response structure is contained
within the generic <sppBatchResponse> element. This response within the generic <sppBatchResponse> element. This response
structure is used for an Batch request that contains many different structure is used for an Batch request that contains many different
types of SPPF operations. types of SPPF operations.
<element name="spppBatchResponse"> <element name="spppBatchResponse">
<complexType> <complexType>
<sequence> <sequence>
<element name="clientTransId" type="sppfb:TransIdType" <element name="clientTransId" type="sppfb:TransIdType"
minOccurs="0"/> minOccurs="0"/>
<element name="serverTransId" type="sppfb:TransIdType"/> <element name="serverTransId" type="sppfb:TransIdType"/>
<element name="overallResult" type="sppfb:ResultCodeType"/> <element name="overallResult" type="sppfb:ResultCodeType"/>
<choice minOccurs="0" maxOccurs="unbounded"> <choice minOccurs="0" maxOccurs="unbounded">
<element name="addResult" <element name="addResult"
type="sppfs:ObjResultCodeType"/> type="sppfs:ObjResultCodeType"/>
<element name="delResult" <element name="delResult"
type="sppfs:ObjKeyResultCodeType"/> type="sppfs:ObjKeyResultCodeType"/>
<element name="acceptResult" <element name="acceptResult"
type="sppfs:RteGrpOfferKeyResultCodeType"/> type="sppfs:SedGrpOfferKeyResultCodeType"/>
<element name="rejectResult" <element name="rejectResult"
type="sppfs:RteGrpOfferKeyResultCodeType"/> type="sppfs:SedGrpOfferKeyResultCodeType"/>
</choice> </choice>
</sequence> </sequence>
</complexType> </complexType>
</element> </element>
An <spppBatchResponse> contains the elements necessary for an SPPF An <spppBatchResponse> contains the elements necessary for an SPPF
client to precisely determine the overall result of various client to precisely determine the overall result of various
operations in the request, and if an error occurred, it provides operations in the request, and if an error occurred, it provides
information about the specific objects or keys in the request that information about the specific objects or keys in the request that
caused the error. caused the error.
skipping to change at page 30, line 37 skipping to change at page 30, line 33
o addResult: One or more elements of type ObjResultCodeType where o addResult: One or more elements of type ObjResultCodeType where
each element identifies the result code, result message and the each element identifies the result code, result message and the
specific object that the result relates to. specific object that the result relates to.
o delResult: One or more elements of type ObjKeyResultCodeType o delResult: One or more elements of type ObjKeyResultCodeType
where each element identifies the result code, result message where each element identifies the result code, result message
and the specific object key that the result relates to. and the specific object key that the result relates to.
o acceptResult: One or more elements of type o acceptResult: One or more elements of type
RteGrpOfferKeyResultCodeType where each element identifies the SedGrpOfferKeyResultCodeType where each element identifies the
result code, result message and the specific Route Group Offer result code, result message and the specific SED Group Offer key
key that the result relates to. that the result relates to.
o rejectResult: One or more elements of type o rejectResult: One or more elements of type
RteGrpOfferKeyResultCodeType where each element identifies the SedGrpOfferKeyResultCodeType where each element identifies the
result code, result message and the specific Route Group Offer result code, result message and the specific SED Group Offer key
key that the result relates to. that the result relates to.
6.2.6. Get Operation Structure 7.2.6. Get Operation Structure
In order to query the details of an object from the Registry, an In order to query the details of an object from the Registry, an
authorized entity can send the spppGetRequest to the registry with a authorized entity can send the spppGetRequest to the registry with a
GetRqstType XML data structure containing one or more object keys GetRqstType XML data structure containing one or more object keys
that uniquely identify the object whose details are being queried. that uniquely identify the object whose details are being queried.
The request strcuture for an SPP Protocol over SOAP Get operation is The request structure for an SPP Protocol over SOAP Get operation is
contained within the generic <spppGetRequest> element while an SPP contained within the generic <spppGetRequest> element while an SPP
Protocol over SOAP Get response is wrapped within the generic Protocol over SOAP Get response is wrapped within the generic
<spppGetResponse> element. The following sub-sections describe the <spppGetResponse> element. The following sub-sections describe the
spppGetRequest and spppGetResponse element. Refer the examples spppGetRequest and spppGetResponse element. Refer the examples
section for an example of SPP Protocol over SOAP Get operation on section for an example of SPP Protocol over SOAP Get operation on
each type of SPPF object each type of SPPF object
6.2.6.1. Get Request 7.2.6.1. Get Request
<element name="spppGetRequest"> <element name="spppGetRequest">
<complexType> <complexType>
<sequence> <sequence>
<element name="minorVer" <element name="minorVer"
type="sppfb:MinorVerType" minOccurs="0"/> type="sppfb:MinorVerType" minOccurs="0"/>
<element name="objKey" <element name="objKey"
type="sppfb:ObjKeyType" type="sppfb:ObjKeyType"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</sequence> </sequence>
skipping to change at page 32, line 5 skipping to change at page 31, line 44
in the document. in the document.
o objKey: One or more elements of abstract type ObjKeyType (as o objKey: One or more elements of abstract type ObjKeyType (as
defined in the framework document). Each element contains defined in the framework document). Each element contains
attributes that uniquely identify the object that the client is attributes that uniquely identify the object that the client is
requesting the server to query. Refer the "Concrete Object requesting the server to query. Refer the "Concrete Object
Keys" section of this document for a description of all concrete Keys" section of this document for a description of all concrete
object key types, for various SPPF objects, which are eligible object key types, for various SPPF objects, which are eligible
to be passed into this element. to be passed into this element.
6.2.6.2. Get Response 7.2.6.2. Get Response
The spppGetResponse element is described later in section titled The spppGetResponse element is described later in section titled
"Generic Query Response". "Generic Query Response".
6.2.7. Get Route Group Offers Operation Structure 7.2.7. Get SED Group Offers Operation Structure
In addition to the ability to query the details of one or more Route In addition to the ability to query the details of one or more SED
Group offers using an a Route Group Offer key in the spppGetRequest, Group offers using an a SED Group Offer key in the spppGetRequest,
this operation also provides an additional, more flexible, structure this operation also provides an additional, more flexible, structure
to query for Route Group Offer objects. This additional structure is to query for SED Group Offer objects. This additional structure is
contained within the <getRteGrpOffersRequest> element while the contained within the <getSedGrpOffersRequest> element while the
response is wrapped within the generic <spppGetResponse> element. response is wrapped within the generic <spppGetResponse> element.
The following sub-sections describe the getRteGrpOffersRequest and The following sub-sections describe the getSedGrpOffersRequest and
spppGetResponse elements. spppGetResponse elements.
6.2.7.1. Get Route Group Offers Request 7.2.7.1. Get SED Group Offers Request
Using the details passed into this structure, the server will attempt Using the details passed into this structure, the server will attempt
to find Route Group Offer objects that satisfy all the criteria to find SED Group Offer objects that satisfy all the criteria passed
passed into the request. If no criteria is passed in then the server into the request. If no criteria is passed in then the server will
will return the list of Route Group Offer objects that belongs to the return the list of SED Group Offer objects that belongs to the
registrant. If there are no matching Route Group Offers found then registrant. If there are no matching SED Group Offers found then an
an empty result set will be returned. empty result set will be returned.
<element name="getRteGrpOffersRequest"> <element name="getSedGrpOffersRequest">
<complexType> <complexType>
<sequence> <sequence>
<element name="minorVer" type="sppfb:MinorVerType" <element name="minorVer" type="sppfb:MinorVerType"
minOccurs="0"/> minOccurs="0"/>
<element name="offeredBy" type="sppfb:OrgIdType" <element name="offeredBy" type="sppfb:OrgIdType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<element name="offeredTo" type="sppfb:OrgIdType" <element name="offeredTo" type="sppfb:OrgIdType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<element name="status" type="sppfb:RteGrpOfferStatusType" <element name="status" type="sppfb:SedGrpOfferStatusType"
minOccurs="0"/> minOccurs="0"/>
<element name="rteGrpOfferKey" type="sppfs:RteGrpOfferKeyType" <element name="sedGrpOfferKey" type="sppfs:SedGrpOfferKeyType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
</element> </element>
The data elements within the <getRteGrpOffersRequest> element are The data elements within the <getSedGrpOffersRequest> element are
described as follows: described as follows:
o minorVer: Zero or one minor version identifier, indicating the o minorVer: Zero or one minor version identifier, indicating the
minor version of the SPPF API that the client is attempting to minor version of the SPPF API that the client is attempting to
use. This is used in conjunction with the major version use. This is used in conjunction with the major version
identifier in the XML namespace to identify the version of SPPF identifier in the XML namespace to identify the version of SPPF
that the client is using. If the element is not present, the that the client is using. If the element is not present, the
server assumes that the client is using the latest minor version server assumes that the client is using the latest minor version
supported by the SPPF server for the given major version. The supported by the SPPF server for the given major version. The
versions supported by a given SPPF server can be retrieved by versions supported by a given SPPF server can be retrieved by
skipping to change at page 33, line 32 skipping to change at page 33, line 26
offered by the organization IDs in this list should be included offered by the organization IDs in this list should be included
in the result set. The result set is also subject to other in the result set. The result set is also subject to other
query criteria in the request. query criteria in the request.
o status: The status of the offer, offered or accepted. Only o status: The status of the offer, offered or accepted. Only
offers in the specified status should be included in the result offers in the specified status should be included in the result
set. If this element is not present then the status of the set. If this element is not present then the status of the
offer should not be considered in the query. The result set is offer should not be considered in the query. The result set is
also subject to other query criteria in the request. also subject to other query criteria in the request.
o rteGrpOfferKey: Zero or more Route Group Offer Keys. Only o sedGrpOfferKey: Zero or more SED Group Offer Keys. Only offers
offers having one of these keys should be included in the result having one of these keys should be included in the result set.
set. The result set is also subject to other query criteria in The result set is also subject to other query criteria in the
the request. request.
6.2.7.2. Get Route Group Offers Response 7.2.7.2. Get SED Group Offers Response
The spppGetResponse element is described later in section titled The spppGetResponse element is described later in section titled
"Generic Query Response". "Generic Query Response".
6.2.8. Generic Query Response 7.2.8. Generic Query Response
An SPP Protocol over SOAP query response object is contained within An SPP Protocol over SOAP query response object is contained within
the generic <spppGetResponse> element. the generic <spppGetResponse> element.
<element name="spppGetResponse"> <element name="spppGetResponse">
<complexType> <complexType>
<sequence> <sequence>
<element name="overallResult" <element name="overallResult"
type="sppfs:ResultCodeType"/> type="sppfs:ResultCodeType"/>
<element name="resultObj" <element name="resultObj"
skipping to change at page 34, line 34 skipping to change at page 34, line 25
o overallResult: Exactly one response code and message pair that o overallResult: Exactly one response code and message pair that
explicitly identifies the result of the request. See the explicitly identifies the result of the request. See the
Response Code section for further details. Response Code section for further details.
o resultObj: The set of zero or more objects that matched the o resultObj: The set of zero or more objects that matched the
query criteria. If no objects matched the query criteria then query criteria. If no objects matched the query criteria then
the result object(s) MUST be empty and the overallResult value the result object(s) MUST be empty and the overallResult value
MUST indicate success (if no matches are found for the query MUST indicate success (if no matches are found for the query
criteria, the response is considered a success). criteria, the response is considered a success).
6.2.9. Get Server Details Operation Structure 7.2.9. Get Server Details Operation Structure
In order to query certain details of the SPPF server, like the SPPF In order to query certain details of the SPPF server, like the SPPF
server's status and the major/minor version supported by the server, server's status and the major/minor version supported by the server,
the Server Details operation structure SHOULD be used. This the Server Details operation structure SHOULD be used. This
structure is contained within the <spppServerStatusRequest> element structure is contained within the <spppServerStatusRequest> element
while a SPPF server status response is wrapped within the while a SPPF server status response is wrapped within the
<spppServerStatusResponse> element. This following sub-sections <spppServerStatusResponse> element. This following sub-sections
describe the spppServerStatusRequest and spppServerStatusResponse describe the spppServerStatusRequest and spppServerStatusResponse
elements. elements.
6.2.9.1. Get Server Details Request 7.2.9.1. Get Server Details Request
<element name="spppServerStatusRequest"> <element name="spppServerStatusRequest">
<complexType> <complexType>
<sequence> <sequence>
<element name="minorVer" <element name="minorVer"
type="sppfb:MinorVerType" minOccurs="0"/> type="sppfb:MinorVerType" minOccurs="0"/>
</sequence> </sequence>
</complexType> </complexType>
</element> </element>
The data elements within the <spppServerStatusRequest> element are The data elements within the <spppServerStatusRequest> element are
skipping to change at page 35, line 28 skipping to change at page 35, line 17
is attempting to use. This is used in conjunction with the is attempting to use. This is used in conjunction with the
major version identifier in the XML namespace to identify the major version identifier in the XML namespace to identify the
version of SPP Protocol over SOAP that the client is using. If version of SPP Protocol over SOAP that the client is using. If
the element is not present, the server assumes that the client the element is not present, the server assumes that the client
is using the latest minor version of SPP Protocol over SOAP is using the latest minor version of SPP Protocol over SOAP
supported by the SPPF server for the given major version. The supported by the SPPF server for the given major version. The
versions of SPP Protocol over SOAP supported by a given SPPF versions of SPP Protocol over SOAP supported by a given SPPF
server can be retrieved by the client using this same server can be retrieved by the client using this same
spppServerStatusRequest without passing in the minorVer element. spppServerStatusRequest without passing in the minorVer element.
6.2.9.2. Get Server Details Response 7.2.9.2. Get Server Details Response
An SPP Protocol over SOAP server details response structure is An SPP Protocol over SOAP server details response structure is
contained within the generic <spppServerStatusResponse> element. contained within the generic <spppServerStatusResponse> element.
<element name="spppServerStatusResponse"> <element name="spppServerStatusResponse">
<complexType> <complexType>
<sequence> <sequence>
<element name="overallResult" type="sppfs:ResultCodeType"/> <element name="overallResult" type="sppfs:ResultCodeType"/>
<element name="svcMenu" type="sppfb:SvcMenuType"/> <element name="svcMenu" type="sppfb:SvcMenuType"/>
</sequence> </sequence>
skipping to change at page 36, line 11 skipping to change at page 35, line 44
o overallResult: Exactly one response code and message pair that o overallResult: Exactly one response code and message pair that
explicitly identifies the result of the request. See the explicitly identifies the result of the request. See the
Response Code section for further details. Response Code section for further details.
o svcMenu: Exactly one element of type SvcMenuType which in turn o svcMenu: Exactly one element of type SvcMenuType which in turn
contains the elements to return the server status and major/ contains the elements to return the server status and major/
minor version of the SPP Protocol over SOAP supported by the minor version of the SPP Protocol over SOAP supported by the
SPPF server (refer framework document for definition of SPPF server (refer framework document for definition of
SvcMenuType) . SvcMenuType) .
6.3. Response Codes and Messages 7.3. Response Codes and Messages
This section contains the listing of response codes and their This section contains the listing of response codes and their
corresponding human-readable text. These response codes are in corresponding human-readable text. These response codes are in
conformance with the response types defined in the section "Response conformance with the response types defined in the section "Response
Message Types" of the framework document. Message Types" of the framework document.
The response code numbering scheme generally adheres to the theory The response code numbering scheme generally adheres to the theory
formalized in section 4.2.1 of [RFC5321]: formalized in section 4.2.1 of [RFC5321]:
o The first digit of the response code can only be 1 or 2: 1 = a o The first digit of the response code can only be 1 or 2: 1 = a
skipping to change at page 39, line 5 skipping to change at page 38, line 5
the following parameters: "AttributeName" and "AttributeValue". the following parameters: "AttributeName" and "AttributeValue".
For example, if an SPPF client sends a request to delete a For example, if an SPPF client sends a request to delete a
Destination Group with a name "TestDG", and it does not already Destination Group with a name "TestDG", and it does not already
exist, then the error message returned should be: "Attribute value exist, then the error message returned should be: "Attribute value
invalid. AttrName:dgName AttrVal:TestDG". invalid. AttrName:dgName AttrVal:TestDG".
The use of these parameters MUST adhere to the rules defined in The use of these parameters MUST adhere to the rules defined in
"Response Message Types" section of the framework document. "Response Message Types" section of the framework document.
7. Protocol Operations 8. Protocol Operations
Refer the "Framework Operations" section of the framework document Refer the "Framework Operations" section of the framework document
for a description of all SPPF operations, and any necessary semantics for a description of all SPPF operations, and any necessary semantics
that MUST be adhered to in order to conform with the SPPF that MUST be adhered to in order to conform with the SPPF
specification. specification.
8. SPP Protocol over SOAP WSDL Definition 9. SPP Protocol over SOAP WSDL Definition
The SPP Protocol over SOAP WSDL and data types are defined below. The SPP Protocol over SOAP WSDL and data types are defined below.
The WSDL design approach is commonly referred to as _Generic WSDL_. The WSDL design approach is commonly referred to as _Generic WSDL_.
It is generic in the sense that there is not a specific WSDL It is generic in the sense that there is not a specific WSDL
operation defined for each object type that is supported by the SPPF operation defined for each object type that is supported by the SPPF
protocol. There is a single WSDL structure for each type of SPPF protocol. There is a single WSDL structure for each type of SPPF
operation. Each such WSDL structure contains exactly one input operation. Each such WSDL structure contains exactly one input
structure and one output structure that wraps any data elements that structure and one output structure that wraps any data elements that
are part of the incoming request and the outgoing response are part of the incoming request and the outgoing response
respectively. The spppSOAPBinding in the WSDL defines the binding respectively. The spppSOAPBinding in the WSDL defines the binding
skipping to change at page 41, line 14 skipping to change at page 40, line 14
<sequence> <sequence>
<element name="rant" type="sppfb:OrgIdType"/> <element name="rant" type="sppfb:OrgIdType"/>
<element name="name" type="sppfb:ObjNameType"/> <element name="name" type="sppfb:ObjNameType"/>
<element name="type" type="sppfs:ObjKeyTypeEnum"/> <element name="type" type="sppfs:ObjKeyTypeEnum"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<simpleType name="ObjKeyTypeEnum"> <simpleType name="ObjKeyTypeEnum">
<restriction base="token"> <restriction base="token">
<enumeration value="RteGrp"/> <enumeration value="SedGrp"/>
<enumeration value="DestGrp"/> <enumeration value="DestGrp"/>
<enumeration value="RteRec"/> <enumeration value="SedRec"/>
<enumeration value="EgrRte"/> <enumeration value="EgrRte"/>
</restriction> </restriction>
</simpleType> </simpleType>
<complexType name="RteGrpOfferKeyType"> <complexType name="SedGrpOfferKeyType">
<complexContent> <complexContent>
<extension base="sppfb:RteGrpOfferKeyType"> <extension base="sppfb:SedGrpOfferKeyType">
<sequence> <sequence>
<element name="rteGrpKey" <element name="sedGrpKey"
type="sppfs:ObjKeyType"/> type="sppfs:ObjKeyType"/>
<element name="offeredTo" <element name="offeredTo"
type="sppfb:OrgIdType"/> type="sppfb:OrgIdType"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<complexType name="PubIdKeyType"> <complexType name="PubIdKeyType">
<complexContent> <complexContent>
skipping to change at page 42, line 41 skipping to change at page 41, line 41
</sequence> </sequence>
</complexType> </complexType>
</element> </element>
<element name="spppAcceptRequest"> <element name="spppAcceptRequest">
<complexType> <complexType>
<sequence> <sequence>
<element name="clientTransId" <element name="clientTransId"
type="sppfb:TransIdType" minOccurs="0"/> type="sppfb:TransIdType" minOccurs="0"/>
<element name="minorVer" <element name="minorVer"
type="sppfb:MinorVerType" minOccurs="0"/> type="sppfb:MinorVerType" minOccurs="0"/>
<element name="rteGrpOfferKey" <element name="sedGrpOfferKey"
type="sppfs:RteGrpOfferKeyType" type="sppfs:SedGrpOfferKeyType"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
</element> </element>
<element name="spppRejectRequest"> <element name="spppRejectRequest">
<complexType> <complexType>
<sequence> <sequence>
<element name="clientTransId" <element name="clientTransId"
type="sppfb:TransIdType" minOccurs="0"/> type="sppfb:TransIdType" minOccurs="0"/>
<element name="minorVer" <element name="minorVer"
type="sppfb:MinorVerType" minOccurs="0"/> type="sppfb:MinorVerType" minOccurs="0"/>
<element name="rteGrpOfferKey" <element name="sedGrpOfferKey"
type="sppfs:RteGrpOfferKeyType" type="sppfs:SedGrpOfferKeyType"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
</element> </element>
<element name="spppGetRequest"> <element name="spppGetRequest">
<complexType> <complexType>
<sequence> <sequence>
<element name="minorVer" <element name="minorVer"
type="sppfb:MinorVerType" minOccurs="0"/> type="sppfb:MinorVerType" minOccurs="0"/>
<element name="objKey" <element name="objKey"
skipping to change at page 43, line 33 skipping to change at page 42, line 33
<element name="spppBatchRequest"> <element name="spppBatchRequest">
<complexType> <complexType>
<sequence> <sequence>
<element name="clientTransId" <element name="clientTransId"
type="sppfb:TransIdType" minOccurs="0"/> type="sppfb:TransIdType" minOccurs="0"/>
<element name="minorVer" <element name="minorVer"
type="sppfb:MinorVerType" minOccurs="0"/> type="sppfb:MinorVerType" minOccurs="0"/>
<choice minOccurs="1" maxOccurs="unbounded"> <choice minOccurs="1" maxOccurs="unbounded">
<element name="addObj" type="sppfb:BasicObjType"/> <element name="addObj" type="sppfb:BasicObjType"/>
<element name="delObj" type="sppfb:ObjKeyType"/> <element name="delObj" type="sppfb:ObjKeyType"/>
<element name="acceptRteGrpOffer" <element name="acceptSedGrpOffer"
type="sppfs:RteGrpOfferKeyType"/> type="sppfs:SedGrpOfferKeyType"/>
<element name="rejectRteGrpOffer" <element name="rejectSedGrpOffer"
type="sppfs:RteGrpOfferKeyType"/> type="sppfs:SedGrpOfferKeyType"/>
</choice> </choice>
</sequence> </sequence>
</complexType> </complexType>
</element> </element>
<element name="spppServerStatusRequest"> <element name="spppServerStatusRequest">
<complexType> <complexType>
<sequence> <sequence>
<element name="minorVer" <element name="minorVer"
type="sppfb:MinorVerType" minOccurs="0"/> type="sppfb:MinorVerType" minOccurs="0"/>
</sequence> </sequence>
</complexType> </complexType>
</element> </element>
<element name="getRteGrpOffersRequest"> <element name="getSedGrpOffersRequest">
<complexType> <complexType>
<sequence> <sequence>
<element name="minorVer" <element name="minorVer"
type="sppfb:MinorVerType" minOccurs="0"/> type="sppfb:MinorVerType" minOccurs="0"/>
<element name="offeredBy" <element name="offeredBy"
type="sppfb:OrgIdType" minOccurs="0" type="sppfb:OrgIdType" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
<element name="offeredTo" type="sppfb:OrgIdType" <element name="offeredTo" type="sppfb:OrgIdType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<element name="status" <element name="status"
type="sppfb:RteGrpOfferStatusType" minOccurs="0"/> type="sppfb:SedGrpOfferStatusType" minOccurs="0"/>
<element name="rteGrpOfferKey" <element name="sedGrpOfferKey"
type="sppfs:RteGrpOfferKeyType" type="sppfs:SedGrpOfferKeyType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
</element> </element>
<element name="spppAddResponse"> <element name="spppAddResponse">
<complexType> <complexType>
<sequence> <sequence>
<element name="clientTransId" <element name="clientTransId"
type="sppfb:TransIdType" minOccurs="0"/> type="sppfb:TransIdType" minOccurs="0"/>
<element name="serverTransId" <element name="serverTransId"
skipping to change at page 45, line 11 skipping to change at page 44, line 11
<element name="spppAcceptResponse"> <element name="spppAcceptResponse">
<complexType> <complexType>
<sequence> <sequence>
<element name="clientTransId" <element name="clientTransId"
type="sppfb:TransIdType" minOccurs="0"/> type="sppfb:TransIdType" minOccurs="0"/>
<element name="serverTransId" <element name="serverTransId"
type="sppfb:TransIdType"/> type="sppfb:TransIdType"/>
<element name="overallResult" <element name="overallResult"
type="sppfs:ResultCodeType"/> type="sppfs:ResultCodeType"/>
<element name="detailResult" <element name="detailResult"
type="sppfs:RteGrpOfferKeyResultCodeType" type="sppfs:SedGrpOfferKeyResultCodeType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
</element> </element>
<element name="spppRejectResponse"> <element name="spppRejectResponse">
<complexType> <complexType>
<sequence> <sequence>
<element name="clientTransId" <element name="clientTransId"
type="sppfb:TransIdType" minOccurs="0"/> type="sppfb:TransIdType" minOccurs="0"/>
<element name="serverTransId" <element name="serverTransId"
type="sppfb:TransIdType"/> type="sppfb:TransIdType"/>
<element name="overallResult" <element name="overallResult"
type="sppfs:ResultCodeType"/> type="sppfs:ResultCodeType"/>
<element name="detailResult" <element name="detailResult"
type="sppfs:RteGrpOfferKeyResultCodeType" type="sppfs:SedGrpOfferKeyResultCodeType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
</element> </element>
<element name="spppBatchResponse"> <element name="spppBatchResponse">
<complexType> <complexType>
<sequence> <sequence>
<element name="clientTransId" <element name="clientTransId"
type="sppfb:TransIdType" minOccurs="0"/> type="sppfb:TransIdType" minOccurs="0"/>
<element name="serverTransId" <element name="serverTransId"
type="sppfb:TransIdType"/> type="sppfb:TransIdType"/>
<element name="overallResult" <element name="overallResult"
type="sppfs:ResultCodeType"/> type="sppfs:ResultCodeType"/>
<choice minOccurs="0" maxOccurs="unbounded"> <choice minOccurs="0" maxOccurs="unbounded">
<element name="addResult" <element name="addResult"
type="sppfs:ObjResultCodeType"/> type="sppfs:ObjResultCodeType"/>
<element name="delResult" <element name="delResult"
type="sppfs:ObjKeyResultCodeType"/> type="sppfs:ObjKeyResultCodeType"/>
<element name="acceptResult" <element name="acceptResult"
type="sppfs:RteGrpOfferKeyResultCodeType"/> type="sppfs:SedGrpOfferKeyResultCodeType"/>
<element name="rejectResult" <element name="rejectResult"
type="sppfs:RteGrpOfferKeyResultCodeType"/> type="sppfs:SedGrpOfferKeyResultCodeType"/>
</choice> </choice>
</sequence> </sequence>
</complexType> </complexType>
</element> </element>
<element name="spppGetResponse"> <element name="spppGetResponse">
<complexType> <complexType>
<sequence> <sequence>
<element name="overallResult" <element name="overallResult"
type="sppfs:ResultCodeType"/> type="sppfs:ResultCodeType"/>
skipping to change at page 47, line 32 skipping to change at page 46, line 32
</complexType> </complexType>
<complexType name="ObjKeyResultCodeType"> <complexType name="ObjKeyResultCodeType">
<complexContent> <complexContent>
<extension base="sppfs:ResultCodeType"> <extension base="sppfs:ResultCodeType">
<sequence> <sequence>
<element name="objKey" type="sppfb:ObjKeyType"/> <element name="objKey" type="sppfb:ObjKeyType"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<complexType name="RteGrpOfferKeyResultCodeType"> <complexType name="SedGrpOfferKeyResultCodeType">
<complexContent> <complexContent>
<extension base="sppfs:ResultCodeType"> <extension base="sppfs:ResultCodeType">
<sequence> <sequence>
<element name="rteGrpOfferKey" <element name="sedGrpOfferKey"
type="sppfs:RteGrpOfferKeyType"/> type="sppfs:SedGrpOfferKeyType"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
</xsd:schema> </xsd:schema>
</wsdl:types> </wsdl:types>
<wsdl:message name="spppAddRequestMsg"> <wsdl:message name="spppAddRequestMsg">
<wsdl:part name="rqst" element="sppfs:spppAddRequest"/> <wsdl:part name="rqst" element="sppfs:spppAddRequest"/>
</wsdl:message> </wsdl:message>
<wsdl:message name="spppDelRequestMsg"> <wsdl:message name="spppDelRequestMsg">
skipping to change at page 48, line 13 skipping to change at page 47, line 13
</wsdl:message> </wsdl:message>
<wsdl:message name="spppRejectRequestMsg"> <wsdl:message name="spppRejectRequestMsg">
<wsdl:part name="rqst" element="sppfs:spppRejectRequest"/> <wsdl:part name="rqst" element="sppfs:spppRejectRequest"/>
</wsdl:message> </wsdl:message>
<wsdl:message name="spppBatchRequestMsg"> <wsdl:message name="spppBatchRequestMsg">
<wsdl:part name="rqst" element="sppfs:spppBatchRequest"/> <wsdl:part name="rqst" element="sppfs:spppBatchRequest"/>
</wsdl:message> </wsdl:message>
<wsdl:message name="spppGetRequestMsg"> <wsdl:message name="spppGetRequestMsg">
<wsdl:part name="rqst" element="sppfs:spppGetRequest"/> <wsdl:part name="rqst" element="sppfs:spppGetRequest"/>
</wsdl:message> </wsdl:message>
<wsdl:message name="spppGetRteGrpOffersRequestMsg"> <wsdl:message name="spppGetSedGrpOffersRequestMsg">
<wsdl:part name="rqst" element="sppfs:getRteGrpOffersRequest"/> <wsdl:part name="rqst" element="sppfs:getSedGrpOffersRequest"/>
</wsdl:message> </wsdl:message>
<wsdl:message name="spppAddResponseMsg"> <wsdl:message name="spppAddResponseMsg">
<wsdl:part name="rspns" element="sppfs:spppAddResponse"/> <wsdl:part name="rspns" element="sppfs:spppAddResponse"/>
</wsdl:message> </wsdl:message>
<wsdl:message name="spppDelResponseMsg"> <wsdl:message name="spppDelResponseMsg">
<wsdl:part name="rspns" element="sppfs:spppDelResponse"/> <wsdl:part name="rspns" element="sppfs:spppDelResponse"/>
</wsdl:message> </wsdl:message>
<wsdl:message name="spppAcceptResponseMsg"> <wsdl:message name="spppAcceptResponseMsg">
<wsdl:part name="rspns" element="sppfs:spppAcceptResponse"/> <wsdl:part name="rspns" element="sppfs:spppAcceptResponse"/>
</wsdl:message> </wsdl:message>
skipping to change at page 49, line 18 skipping to change at page 48, line 18
<wsdl:output message="sppfs:spppRejectResponseMsg"/> <wsdl:output message="sppfs:spppRejectResponseMsg"/>
</wsdl:operation> </wsdl:operation>
<wsdl:operation name="submitBatchRqst"> <wsdl:operation name="submitBatchRqst">
<wsdl:input message="sppfs:spppBatchRequestMsg"/> <wsdl:input message="sppfs:spppBatchRequestMsg"/>
<wsdl:output message="sppfs:spppBatchResponseMsg"/> <wsdl:output message="sppfs:spppBatchResponseMsg"/>
</wsdl:operation> </wsdl:operation>
<wsdl:operation name="submitGetRqst"> <wsdl:operation name="submitGetRqst">
<wsdl:input message="sppfs:spppGetRequestMsg"/> <wsdl:input message="sppfs:spppGetRequestMsg"/>
<wsdl:output message="sppfs:spppGetResponseMsg"/> <wsdl:output message="sppfs:spppGetResponseMsg"/>
</wsdl:operation> </wsdl:operation>
<wsdl:operation name="submitGetRteGrpOffersRqst"> <wsdl:operation name="submitGetSedGrpOffersRqst">
<wsdl:input message="sppfs:spppGetRteGrpOffersRequestMsg"/> <wsdl:input message="sppfs:spppGetSedGrpOffersRequestMsg"/>
<wsdl:output message="sppfs:spppGetResponseMsg"/> <wsdl:output message="sppfs:spppGetResponseMsg"/>
</wsdl:operation> </wsdl:operation>
<wsdl:operation name="submitServerStatusRqst"> <wsdl:operation name="submitServerStatusRqst">
<wsdl:input message="sppfs:spppServerStatusRequestMsg"/> <wsdl:input message="sppfs:spppServerStatusRequestMsg"/>
<wsdl:output message="sppfs:spppServerStatusResponseMsg"/> <wsdl:output message="sppfs:spppServerStatusResponseMsg"/>
</wsdl:operation> </wsdl:operation>
</wsdl:portType> </wsdl:portType>
<wsdl:binding name="spppSoapBinding" type="sppfs:spppPortType"> <wsdl:binding name="spppSoapBinding" type="sppfs:spppPortType">
<soap:binding style="document" <soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/> transport="http://schemas.xmlsoap.org/soap/http"/>
skipping to change at page 50, line 35 skipping to change at page 49, line 35
</wsdl:operation> </wsdl:operation>
<wsdl:operation name="submitGetRqst"> <wsdl:operation name="submitGetRqst">
<soap:operation soapAction="submitGetRqst" style="document"/> <soap:operation soapAction="submitGetRqst" style="document"/>
<wsdl:input> <wsdl:input>
<soap:body use="literal"/> <soap:body use="literal"/>
</wsdl:input> </wsdl:input>
<wsdl:output> <wsdl:output>
<soap:body use="literal"/> <soap:body use="literal"/>
</wsdl:output> </wsdl:output>
</wsdl:operation> </wsdl:operation>
<wsdl:operation name="submitGetRteGrpOffersRqst"> <wsdl:operation name="submitGetSedGrpOffersRqst">
<soap:operation soapAction="submitGetRteGrpOffersRqst" <soap:operation soapAction="submitGetSedGrpOffersRqst"
style="document"/> style="document"/>
<wsdl:input> <wsdl:input>
<soap:body use="literal"/> <soap:body use="literal"/>
</wsdl:input> </wsdl:input>
<wsdl:output> <wsdl:output>
<soap:body use="literal"/> <soap:body use="literal"/>
</wsdl:output> </wsdl:output>
</wsdl:operation> </wsdl:operation>
<wsdl:operation name="submitServerStatusRqst"> <wsdl:operation name="submitServerStatusRqst">
<soap:operation soapAction="submitServerStatusRqst" <soap:operation soapAction="submitServerStatusRqst"
skipping to change at page 52, line 5 skipping to change at page 51, line 5
</wsdl:binding> </wsdl:binding>
<wsdl:service name="spppService"> <wsdl:service name="spppService">
<wsdl:port name="spppPort" binding="sppfs:spppSoapBinding"> <wsdl:port name="spppPort" binding="sppfs:spppSoapBinding">
<soap:address location="REPLACE_WITH_ACTUAL_URL"/> <soap:address location="REPLACE_WITH_ACTUAL_URL"/>
</wsdl:port> </wsdl:port>
</wsdl:service> </wsdl:service>
</wsdl:definitions> </wsdl:definitions>
Figure 2: WSDL Figure 2: WSDL
9. SPP Protocol over SOAP Examples 10. SPP Protocol over SOAP Examples
This section shows XML message exchange between two SIP Service This section shows XML message exchange between two SIP Service
Providers (SSP) and a registry. The messages in this section are Providers (SSP) and a registry. The messages in this section are
valid XML instances that conform to the SPP Protocol over SOAP schema valid XML instances that conform to the SPP Protocol over SOAP schema
version within this document. This section relies on the XML data version within this document. This section relies on the XML data
structures defined in the base SPPF specification structures defined in the base SPPF specification
[I-D.draft-ietf-drinks-spp-framework]. So refer to that document to [I-D.draft-ietf-drinks-spp-framework]. So refer to that document to
understand XML object types embedded in these example messages. understand XML object types embedded in these example messages.
In this sample use case scenario, SSP1 and SSP2 provision resource In this sample use case scenario, SSP1 and SSP2 provision resource
data in the registry and use SPPF constructs to selectively share the data in the registry and use SPPF constructs to selectively share the
route groups. In the figure below, SSP2 has two ingress SBE SED groups. In the figure below, SSP2 has two ingress SBE instances
instances that are associated with the public identities that SSP2 that are associated with the public identities that SSP2 has the
has the retail relationship with. Also, the two SBE instances for retail relationship with. Also, the two SBE instances for SSP1 are
SSP1 are used to show how to use SPPF to associate route preferences used to show how to use SPPF to associate route preferences for the
for the destination ingress routes and exercise greater control on destination ingress routes and exercise greater control on outbound
outbound traffic to the peer's ingress SBEs. traffic to the peer's ingress SBEs.
---------------+ +------------------ ---------------+ +------------------
| | | |
+------+ +------+ +------+ +------+
| sbe1 | | sbe2 | | sbe1 | | sbe2 |
+------+ +------+ +------+ +------+
SSP1 | | SSP2 SSP1 | | SSP2
+------+ +------+ +------+ +------+
| sbe3 | | sbe4 | | sbe3 | | sbe4 |
+------+ +------+ +------+ +------+
iana-en:111 | | iana-en:222 iana-en:111 | | iana-en:222
---------------+ +------------------ ---------------+ +------------------
| | | |
| | | |
| SPPF +------------------+ SPPF | | SPPF +------------------+ SPPF |
+------->| Registry |<--------+ +------->| Registry |<--------+
+------------------+ +------------------+
9.1. Add Destination Group 10.1. Add Destination Group
SSP2 adds a destination group to the registry for use later. The SSP2 adds a destination group to the registry for use later. The
SSP2 SPPF client sets a unique transaction identifier 'txn_1479' for SSP2 SPPF client sets a unique transaction identifier 'txn_1479' for
tracking purposes. The name of the destination group is set to tracking purposes. The name of the destination group is set to
DEST_GRP_SSP2_1 DEST_GRP_SSP2_1
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"
xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1" xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:spppAddRequest> <urn:spppAddRequest>
<!--Optional:--> <!--Optional:-->
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<!--1 or more repetitions:--> <!--1 or more repetitions:-->
<obj xsi:type="urn1:DestGrpType"> <obj xsi:type="urn1:DestGrpType">
<urn1:rant>iana-en:222</urn1:rant> <urn1:rant>iana-en:222</urn1:rant>
<urn1:rar>iana-en:223</urn1:rar> <urn1:rar>iana-en:223</urn1:rar>
<urn1:dgName>DEST_GRP_SSP2_1</urn1:dgName> <urn1:dgName>DEST_GRP_SSP2_1</urn1:dgName>
</obj> </obj>
</urn:spppAddRequest> </urn:spppAddRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
The registry processes the request and return a favorable response The registry processes the request and return a favorable response
confirming successful creation of the named destination group. Also, confirming successful creation of the named destination group. Also,
besides returning a unique server transaction identifier, Registry besides returning a unique server transaction identifier, Registry
also returns the matching client transaction identifier from the also returns the matching client transaction identifier from the
request message back to the SPPF client. request message back to the SPPF client.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<S:Envelope <S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body> <S:Body>
<ns3:spppAddResponse <ns3:spppAddResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<serverTransId>tx_12345</serverTransId> <serverTransId>tx_12345</serverTransId>
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>Request Succeeded.</msg> <msg>Request Succeeded.</msg>
</overallResult> </overallResult>
</ns3:spppAddResponse> </ns3:spppAddResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
9.2. Add Route Records 10.2. Add SED Records
SSP2 adds an ingress routes in the registry. SSP2 adds SED records in the form of ingress routes to the registry.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"
xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1" xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:spppAddRequest> <urn:spppAddRequest>
<!--Optional:--> <!--Optional:-->
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<!--1 or more repetitions:--> <!--1 or more repetitions:-->
<obj xsi:type="urn1:NAPTRType"> <obj xsi:type="urn1:NAPTRType">
<urn1:rant>iana-en:222</urn1:rant> <urn1:rant>iana-en:222</urn1:rant>
<urn1:rar>iana-en:223</urn1:rar> <urn1:rar>iana-en:223</urn1:rar>
<urn1:rrName>RTE_SSP2_SBE2</urn1:rrName> <urn1:sedName>SED_SSP2_SBE2</urn1:sedName>
<urn1:isInSvc>true</urn1:isInSvc> <urn1:isInSvc>true</urn1:isInSvc>
<urn1:order>10</urn1:order> <urn1:order>10</urn1:order>
<urn1:flags>u</urn1:flags> <urn1:flags>u</urn1:flags>
<urn1:svcs>E2U+sip</urn1:svcs> <urn1:svcs>E2U+sip</urn1:svcs>
<urn1:regx> <urn1:regx>
<urn1:ere>^(.*)$</urn1:ere> <urn1:ere>^(.*)$</urn1:ere>
<urn1:repl>sip:\1@sbe2.ssp2.example.com</urn1:repl> <urn1:repl>sip:\1@sbe2.ssp2.example.com</urn1:repl>
</urn1:regx> </urn1:regx>
</obj> </obj>
</urn:spppAddRequest> </urn:spppAddRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
The registry returns a success response. The registry returns a success response.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<S:Envelope <S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body> <S:Body>
<ns3:spppAddResponse <ns3:spppAddResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<serverTransId>tx_12345</serverTransId> <serverTransId>tx_12345</serverTransId>
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>Request Succeeded.</msg> <msg>Request Succeeded.</msg>
</overallResult> </overallResult>
</ns3:spppAddResponse> </ns3:spppAddResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
9.3. Add Route Records -- URIRteRecType 10.3. Add SED Records -- URIType
SSP2 adds another ingress routes in the registry and makes use of SSP2 adds another SED record to the registry and makes use of URIType
URIRteRecType
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"
xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1" xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:spppAddRequest> <urn:spppAddRequest>
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<!--1 or more repetitions:--> <!--1 or more repetitions:-->
<obj xsi:type="urn1:URIRteRecType"> <obj xsi:type="urn1:URIType">
<urn1:rant>iana-en:222</urn1:rant> <urn1:rant>iana-en:222</urn1:rant>
<urn1:rar>iana-en:223</urn1:rar> <urn1:rar>iana-en:223</urn1:rar>
<urn1:rrName>RTE_SSP2_SBE4</urn1:rrName> <urn1:sedName>SED_SSP2_SBE4</urn1:sedName>
<urn1:isInSvc>true</urn1:isInSvc> <urn1:isInSvc>true</urn1:isInSvc>
<urn1:ere>^(.*)$</urn1:ere> <urn1:ere>^(.*)$</urn1:ere>
<urn1:uri>sip:\1;npdi@sbe4.ssp2.example.com</urn1:uri> <urn1:uri>sip:\1;npdi@sbe4.ssp2.example.com</urn1:uri>
</obj> </obj>
</urn:spppAddRequest> </urn:spppAddRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
The registry returns a success response. The registry returns a success response.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body> <S:Body>
<ns3:spppAddResponse <ns3:spppAddResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<serverTransId>tx_12345</serverTransId> <serverTransId>tx_12345</serverTransId>
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>Request Succeeded.</msg> <msg>Request Succeeded.</msg>
</overallResult> </overallResult>
</ns3:spppAddResponse> </ns3:spppAddResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
9.4. Add Route Group 10.4. Add SED Group
SSP2 creates the grouping of the ingress routes and chooses higher SSP2 creates the grouping of SED records (e.g. ingress routes) and
precedence for RTE_SSP2_SBE2 by setting a lower number for the chooses higher precedence for SED_SSP2_SBE2 by setting a lower number
"priority" attribute, a protocol agnostic precedence indicator. for the "priority" attribute, a protocol agnostic precedence
indicator.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"
xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1" xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:spppAddRequest> <urn:spppAddRequest>
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<!--1 or more repetitions:--> <!--1 or more repetitions:-->
<obj xsi:type="urn1:RteGrpType"> <obj xsi:type="urn1:SedGrpType">
<urn1:rant>iana-en:222</urn1:rant> <urn1:rant>iana-en:222</urn1:rant>
<urn1:rar>iana-en:223</urn1:rar> <urn1:rar>iana-en:223</urn1:rar>
<urn1:rgName>RTE_GRP_SSP2_1</urn1:rgName> <urn1:sedGrpName>SED_GRP_SSP2_1</urn1:sedGrpName>
<urn1:rrRef> <urn1:sedRecRef>
<urn1:rrKey xsi:type="urn:ObjKeyType"> <urn1:sedKey xsi:type="urn:ObjKeyType">
<rant>iana-en:222</rant> <rant>iana-en:222</rant>
<name>RTE_SSP2_SBE2</name> <name>SED_SSP2_SBE2</name>
<type>RteRec</type> <type>SedRec</type>
</urn1:rrKey> </urn1:sedKey>
<urn1:priority>100</urn1:priority> <urn1:priority>100</urn1:priority>
</urn1:rrRef> </urn1:sedRecRef>
<urn1:dgName>DEST_GRP_SSP2_1</urn1:dgName> <urn1:dgName>DEST_GRP_SSP2_1</urn1:dgName>
<urn1:isInSvc>true</urn1:isInSvc> <urn1:isInSvc>true</urn1:isInSvc>
<urn1:priority>10</urn1:priority> <urn1:priority>10</urn1:priority>
</obj> </obj>
</urn:spppAddRequest> </urn:spppAddRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
To confirm successful processing of this request, registry returns a To confirm successful processing of this request, registry returns a
well-known result code '1000' to the SSP2 client. well-known result code '1000' to the SSP2 client.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body> <S:Body>
<ns3:spppAddResponse <ns3:spppAddResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<serverTransId>tx_12345</serverTransId> <serverTransId>tx_12345</serverTransId>
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>Request Succeeded.</msg> <msg>Request Succeeded.</msg>
</overallResult> </overallResult>
</ns3:spppAddResponse> </ns3:spppAddResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
9.5. Add Public Identity -- Successful COR claim 10.5. Add Public Identity -- Successful COR claim
SSP2 activates a TN public identity by associating it with a valid SSP2 activates a TN public identity by associating it with a valid
destination group. Further, SSP2 puts forth a claim that it is the destination group. Further, SSP2 puts forth a claim that it is the
carrier-of-record for the TN. carrier-of-record for the TN.
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"
xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1" xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:spppAddRequest> <urn:spppAddRequest>
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<!--1 or more repetitions:--> <!--1 or more repetitions:-->
<obj xsi:type="urn1:TNType"> <obj xsi:type="urn1:TNType">
<urn1:rant>iana-en:222</urn1:rant> <urn1:rant>iana-en:222</urn1:rant>
<urn1:rar>iana-en:223</urn1:rar> <urn1:rar>iana-en:223</urn1:rar>
<urn1:dgName>DEST_GRP_SSP2_1</urn1:dgName> <urn1:dgName>DEST_GRP_SSP2_1</urn1:dgName>
<urn1:tn>+12025556666</urn1:tn> <urn1:tn>+12025556666</urn1:tn>
<urn1:corInfo> <urn1:corInfo>
<urn1:corClaim>true</urn1:corClaim> <urn1:corClaim>true</urn1:corClaim>
</urn1:corInfo> </urn1:corInfo>
</obj> </obj>
</urn:spppAddRequest> </urn:spppAddRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
Assuming that the registry has access to TN authority data and it Assuming that the registry has access to TN authority data and it
performs the required checks to verify that SSP2 is in fact the performs the required checks to verify that SSP2 is in fact the
service provider of record for the given TN, the request is processed service provider of record for the given TN, the request is processed
successfully. In the response message, the registry sets the value successfully. In the response message, the registry sets the value
of <cor> to "true" in order to confirm SSP2 claim as the carrier of of <cor> to "true" in order to confirm SSP2 claim as the carrier of
record and the <corDate> reflects the time when the carrier of record record and the <corDate> reflects the time when the carrier of record
claim is processed. claim is processed.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<S:Envelope <S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<S:Body> <S:Body>
<ns3:spppAddResponse <ns3:spppAddResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<serverTransId>tx_12345</serverTransId> <serverTransId>tx_12345</serverTransId>
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>Request Succeeded.</msg> <msg>Request Succeeded.</msg>
</overallResult> </overallResult>
<detailResult> <detailResult>
<code>1000</code> <code>1000</code>
<msg>Request Succeeded.</msg> <msg>Request Succeeded.</msg>
<obj xsi:type="ns2:TNType"> <obj xsi:type="ns2:TNType">
<ns2:rant>iana-en:222</ns2:rant> <ns2:rant>iana-en:222</ns2:rant>
<ns2:rar>iana-en:223</ns2:rar> <ns2:rar>iana-en:223</ns2:rar>
<ns2:cDate>2010-05-30T09:30:10Z</ns2:cDate> <ns2:cDate>2010-05-30T09:30:10Z</ns2:cDate>
<ns2:dgName>DEST_GRP_SSP2_1</ns2:dgName> <ns2:dgName>DEST_GRP_SSP2_1</ns2:dgName>
<ns2:tn>+12025556666</ns2:tn> <ns2:tn>+12025556666</ns2:tn>
<ns2:corInfo> <ns2:corInfo>
<ns2:corClaim>true</ns2:corClaim> <ns2:corClaim>true</ns2:corClaim>
<ns2:cor>true</ns2:cor> <ns2:cor>true</ns2:cor>
<ns2:corDate>2010-05-30T09:30:11Z</ns2:corDate> <ns2:corDate>2010-05-30T09:30:11Z</ns2:corDate>
</ns2:corInfo> </ns2:corInfo>
</obj> </obj>
</detailResult> </detailResult>
</ns3:spppAddResponse> </ns3:spppAddResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
9.6. Add LRN 10.6. Add LRN
If another entity that SSP2 shares the routes with has access to If another entity that SSP2 shares session establishment information
Number Portability data, it may choose to perform route lookups by (e.g. routes) with has access to Number Portability data, it may
routing number. Therefore, SSP2 associates a routing number to a choose to perform route lookups by routing number. Therefore, SSP2
destination group in order to facilitate ingress route discovery. associates a routing number to a destination group in order to
facilitate ingress route discovery.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"
xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1" xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:spppAddRequest> <urn:spppAddRequest>
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<!--1 or more repetitions:--> <!--1 or more repetitions:-->
<obj xsi:type="urn1:RNType"> <obj xsi:type="urn1:RNType">
<urn1:rant>iana-en:222</urn1:rant> <urn1:rant>iana-en:222</urn1:rant>
<urn1:rar>iana-en:223</urn1:rar> <urn1:rar>iana-en:223</urn1:rar>
<urn1:dgName>DEST_GRP_SSP2_1</urn1:dgName> <urn1:dgName>DEST_GRP_SSP2_1</urn1:dgName>
<urn1:rn>2025550000</urn1:rn> <urn1:rn>2025550000</urn1:rn>
</obj> </obj>
</urn:spppAddRequest> </urn:spppAddRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
Registry completes the request successfully and returns a favorable Registry completes the request successfully and returns a favorable
response to the SPPF client. response to the SPPF client.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<S:Envelope <S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body> <S:Body>
<ns3:spppAddResponse <ns3:spppAddResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<serverTransId>tx_12345</serverTransId> <serverTransId>tx_12345</serverTransId>
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>Request Succeeded.</msg> <msg>Request Succeeded.</msg>
</overallResult> </overallResult>
</ns3:spppAddResponse> </ns3:spppAddResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
9.7. Add TN Range 10.7. Add TN Range
Next, SSP2 activates a block of ten thousand TNs and associate it to Next, SSP2 activates a block of ten thousand TNs and associate it to
a destination group. a destination group.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"
xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1" xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:spppAddRequest> <urn:spppAddRequest>
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<!--1 or more repetitions:--> <!--1 or more repetitions:-->
<obj xsi:type="urn1:TNRType"> <obj xsi:type="urn1:TNRType">
<urn1:rant>iana-en:222</urn1:rant> <urn1:rant>iana-en:222</urn1:rant>
<urn1:rar>iana-en:223</urn1:rar> <urn1:rar>iana-en:223</urn1:rar>
<urn1:dgName>DEST_GRP_SSP2_1</urn1:dgName> <urn1:dgName>DEST_GRP_SSP2_1</urn1:dgName>
<urn1:range> <urn1:range>
<urn1:startTn>+12026660000</urn1:startTn> <urn1:startTn>+12026660000</urn1:startTn>
<urn1:endTn>+12026669999</urn1:endTn> <urn1:endTn>+12026669999</urn1:endTn>
</urn1:range> </urn1:range>
</obj> </obj>
</urn:spppAddRequest> </urn:spppAddRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
Registry completes the request successfully and returns a favorable Registry completes the request successfully and returns a favorable
response. response.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<S:Envelope <S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body> <S:Body>
<ns3:spppAddResponse <ns3:spppAddResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<serverTransId>tx_12345</serverTransId> <serverTransId>tx_12345</serverTransId>
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>Request Succeeded.</msg> <msg>Request Succeeded.</msg>
</overallResult> </overallResult>
</ns3:spppAddResponse> </ns3:spppAddResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
9.8. Add TN Prefix 10.8. Add TN Prefix
Next, SSP2 activates a block of ten thousand TNs using the TNPType Next, SSP2 activates a block of ten thousand TNs using the TNPType
structure and identifying a TN prefix. structure and identifying a TN prefix.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"
xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1" xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:spppAddRequest> <urn:spppAddRequest>
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<!--1 or more repetitions:--> <!--1 or more repetitions:-->
<obj xsi:type="urn1:TNPType"> <obj xsi:type="urn1:TNPType">
<urn1:rant>iana-en:222</urn1:rant> <urn1:rant>iana-en:222</urn1:rant>
<urn1:rar>iana-en:223</urn1:rar> <urn1:rar>iana-en:223</urn1:rar>
<urn1:dgName>DEST_GRP_SSP2_1</urn1:dgName> <urn1:dgName>DEST_GRP_SSP2_1</urn1:dgName>
<urn1:tnPrefix>+1202777</urn1:tnPrefix> <urn1:tnPrefix>+1202777</urn1:tnPrefix>
</obj> </obj>
</urn:spppAddRequest> </urn:spppAddRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
Registry completes the request successfully and returns a favorable Registry completes the request successfully and returns a favorable
response. response.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<S:Envelope <S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body> <S:Body>
<ns3:spppAddResponse <ns3:spppAddResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<serverTransId>tx_12345</serverTransId> <serverTransId>tx_12345</serverTransId>
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>Request Succeeded.</msg> <msg>Request Succeeded.</msg>
</overallResult> </overallResult>
</ns3:spppAddResponse> </ns3:spppAddResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
9.9. Enable Peering -- Route Group Offer 10.9. Enable Peering -- SED Group Offer
In order for SSP1 to complete session establishment for a destination In order for SSP1 to complete session establishment for a destination
TN where the target subscriber has a retail relationship with SSP2, TN where the target subscriber has a retail relationship with SSP2,
it first requires an asynchronous bi-directional handshake to show it first requires an asynchronous bi-directional handshake to show
mutual consent. To start the process, SSP2 initiates the peering mutual consent. To start the process, SSP2 initiates the peering
handshake by offering SSP1 access to its route group. handshake by offering SSP1 access to its SED group.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"
xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1" xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:spppAddRequest> <urn:spppAddRequest>
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<!--1 or more repetitions:--> <!--1 or more repetitions:-->
<obj xsi:type="urn1:RteGrpOfferType"> <obj xsi:type="urn1:SedGrpOfferType">
<urn1:rant>iana-en:222</urn1:rant> <urn1:rant>iana-en:222</urn1:rant>
<urn1:rar>iana-en:223</urn1:rar> <urn1:rar>iana-en:223</urn1:rar>
<urn1:rteGrpOfferKey xsi:type="urn:RteGrpOfferKeyType"> <urn1:sedGrpOfferKey xsi:type="urn:SedGrpOfferKeyType">
<rteGrpKey xsi:type="urn:ObjKeyType"> <sedGrpKey xsi:type="urn:ObjKeyType">
<rant>iana-en:222</rant> <rant>iana-en:222</rant>
<name>RTE_GRP_SSP2_1</name> <name>SED_GRP_SSP2_1</name>
<type>RteGrp</type> <type>SedGrp</type>
</rteGrpKey> </sedGrpKey>
<offeredTo>iana-en:111</offeredTo> <offeredTo>iana-en:111</offeredTo>
</urn1:rteGrpOfferKey> </urn1:sedGrpOfferKey>
<urn1:status>offered</urn1:status> <urn1:status>offered</urn1:status>
<urn1:offerDateTime> <urn1:offerDateTime>
2006-05-04T18:13:51.0Z 2006-05-04T18:13:51.0Z
</urn1:offerDateTime> </urn1:offerDateTime>
</obj> </obj>
</urn:spppAddRequest> </urn:spppAddRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
Registry completes the request successfully and confirms that the Registry completes the request successfully and confirms that the
SSP1 will now have the opportunity to weigh in on the offer and SSP1 will now have the opportunity to weigh in on the offer and
either accept or reject it. The registry may employ out-of-band either accept or reject it. The registry may employ out-of-band
notification mechanisms for quicker updates to SSP1 so they can act notification mechanisms for quicker updates to SSP1 so they can act
faster, though this topic is beyond the scope of this document. faster, though this topic is beyond the scope of this document.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<S:Envelope <S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body> <S:Body>
<ns3:spppAddResponse <ns3:spppAddResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<serverTransId>tx_12345</serverTransId> <serverTransId>tx_12345</serverTransId>
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>Request Succeeded.</msg> <msg>Request Succeeded.</msg>
</overallResult> </overallResult>
</ns3:spppAddResponse> </ns3:spppAddResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
9.10. Enable Peering -- Route Group Offer Accept 10.10. Enable Peering -- SED Group Offer Accept
SSP1 responds to the offer from SSP2 and agrees to have visibility to SSP1 responds to the offer from SSP2 and agrees to have visibility to
SSP2 ingress routes. SSP2 session establishment information (e.g. ingress routes).
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:spppAcceptRequest> <urn:spppAcceptRequest>
<!--Optional:--> <!--Optional:-->
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<!--1 or more repetitions:--> <!--1 or more repetitions:-->
<rteGrpOfferKey> <sedGrpOfferKey>
<rteGrpKey> <sedGrpKey>
<rant>iana-en:222</rant> <rant>iana-en:222</rant>
<name>RTE_GRP_SSP2_1</name> <name>SED_GRP_SSP2_1</name>
<type>RteGrp</type> <type>SedGrp</type>
</rteGrpKey> </sedGrpKey>
<offeredTo>iana-en:111</offeredTo> <offeredTo>iana-en:111</offeredTo>
</rteGrpOfferKey> </sedGrpOfferKey>
</urn:spppAcceptRequest> </urn:spppAcceptRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
Registry confirms that the request has been processed successfully. Registry confirms that the request has been processed successfully.
From this point forward, if SSP1 looks up a public identity through From this point forward, if SSP1 looks up a public identity through
the query resolution server, where the public identity is part of the the query resolution server, where the public identity is part of the
destination group by way of "RTE_GRP_SSP2_1" route association, SSP2 destination group by way of "SED_GRP_SSP2_1" session establishment
ingress SBE information will be shared with SSP1. data association, SSP2 ingress SBE information will be shared with
SSP1.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<S:Envelope <S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body> <S:Body>
<ns3:spppAcceptResponse <ns3:spppAcceptResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<serverTransId>tx_12350</serverTransId> <serverTransId>tx_12350</serverTransId>
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>Request Succeeded.</msg> <msg>Request Succeeded.</msg>
</overallResult> </overallResult>
</ns3:spppAcceptResponse> </ns3:spppAcceptResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
9.11. Add Egress Route 10.11. Add Egress Route
SSP1 wants to prioritize all outbound traffic to routes associated SSP1 wants to prioritize all outbound traffic to the ingress route
with "RTE_GRP_SSP2_1" route group through "sbe1.ssp1.example.com". associated with the "SED_GRP_SSP2_1" SED Group record, through
"sbe1.ssp1.example.com".
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"
xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1" xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:spppAddRequest> <urn:spppAddRequest>
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<!--1 or more repetitions:--> <!--1 or more repetitions:-->
<obj xsi:type="urn1:EgrRteType"> <obj xsi:type="urn1:EgrRteType">
<urn1:rant>iana-en:222</urn1:rant> <urn1:rant>iana-en:222</urn1:rant>
<urn1:rar>iana-en:223</urn1:rar> <urn1:rar>iana-en:223</urn1:rar>
<urn1:egrRteName>EGR_RTE_01</urn1:egrRteName> <urn1:egrRteName>EGR_RTE_01</urn1:egrRteName>
<urn1:pref>50</urn1:pref> <urn1:pref>50</urn1:pref>
<urn1:regxRewriteRule> <urn1:regxRewriteRule>
<urn1:ere>^(.*@)(.*)$</urn1:ere> <urn1:ere>^(.*@)(.*)$</urn1:ere>
<urn1:repl>\1\2?route=sbe1.ssp1.example.com</urn1:repl> <urn1:repl>\1\2?route=sbe1.ssp1.example.com</urn1:repl>
</urn1:regxRewriteRule> </urn1:regxRewriteRule>
<urn1:ingrRteRec xsi:type="urn:ObjKeyType"> <urn1:ingrSedGrp xsi:type="urn:ObjKeyType">
<rant>iana-en:222</rant> <rant>iana-en:222</rant>
<name>SSP2_RTE_REC_3</name> <name>SED_GRP_SSP2_1</name>
<type>RteRec</type> <type>SedGrp</type>
</urn1:ingrRteRec> </urn1:ingrSedGrp>
</obj> </obj>
</urn:spppAddRequest> </urn:spppAddRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
Since peering has already been established, the request to add the Since peering has already been established, the request to add the
egress route has been successfully completed. egress route has been successfully completed.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<S:Envelope <S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body> <S:Body>
<ns3:spppAddResponse <ns3:spppAddResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<serverTransId>tx_12345</serverTransId> <serverTransId>tx_12345</serverTransId>
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>Request Succeeded.</msg> <msg>Request Succeeded.</msg>
</overallResult> </overallResult>
</ns3:spppAddResponse> </ns3:spppAddResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
9.12. Remove Peering -- Route Group Offer Reject 10.12. Remove Peering -- SED Group Offer Reject
SSP1 had earlier accepted to have visibility to SSP2 ingress routes. SSP1 had earlier accepted to have visibility to SSP2 session
SSP1 now decides to no more maintain this visiblity and hence rejects establishment data. SSP1 now decides to no longer maintain this
the Route Group Offer. visibility and hence rejects the SED Group Offer.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:spppRejectRequest> <urn:spppRejectRequest>
<!--Optional:--> <!--Optional:-->
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<!--1 or more repetitions:--> <!--1 or more repetitions:-->
<rteGrpOfferKey> <sedGrpOfferKey>
<rteGrpKey> <sedGrpKey>
<rant>iana-en:222</rant> <rant>iana-en:222</rant>
<name>RTE_GRP_SSP2_1</name> <name>SED_GRP_SSP2_1</name>
<type>RteGrp</type> <type>SedGrp</type>
</rteGrpKey> </sedGrpKey>
<offeredTo>iana-en:111</offeredTo> <offeredTo>iana-en:111</offeredTo>
</rteGrpOfferKey> </sedGrpOfferKey>
</urn:spppRejectRequest> </urn:spppRejectRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
Registry confirms that the request has been processed successfully. Registry confirms that the request has been processed successfully.
From this point forward, if SSP1 looks up a public identity through From this point forward, if SSP1 looks up a public identity through
the query resolution server, where the public identity is part of the the query resolution server, where the public identity is part of the
destination group by way of "RTE_GRP_SSP2_1" route association, SSP2 destination group by way of "SED_GRP_SSP2_1" session establishment
ingress SBE information will NOT be shared with SSP1 and hence SSP2 data association, SSP2 ingress SBE information will NOT be shared
ingress SBE will NOT be returned in the query response. with SSP1 and hence SSP2 ingress SBE will NOT be returned in the
query response.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<S:Envelope <S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body> <S:Body>
<ns3:spppRejectResponse <ns3:spppRejectResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<clientTransId>txn_1479</clientTransId> <clientTransId>txn_1479</clientTransId>
<serverTransId>tx_12350</serverTransId> <serverTransId>tx_12350</serverTransId>
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>Request Succeeded.</msg> <msg>Request Succeeded.</msg>
</overallResult> </overallResult>
</ns3:spppRejectResponse> </ns3:spppRejectResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
9.13. Get Destination Group 10.13. Get Destination Group
SSP2 uses the 'spppGetRequest' operation to tally the last SSP2 uses the 'spppGetRequest' operation to tally the last
provisioned record for destination group DEST_GRP_SSP2_1. provisioned record for destination group DEST_GRP_SSP2_1.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:spppGetRequest> <urn:spppGetRequest>
<!--1 or more repetitions:--> <!--1 or more repetitions:-->
<objKey xsi:type="urn:ObjKeyType"> <objKey xsi:type="urn:ObjKeyType">
<rant>iana-en:222</rant> <rant>iana-en:222</rant>
<name>DEST_GRP_SSP2_1</name> <name>DEST_GRP_SSP2_1</name>
<type>DestGrp</type> <type>DestGrp</type>
</objKey> </objKey>
</urn:spppGetRequest> </urn:spppGetRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
Registry completes the request successfully and returns a favorable Registry completes the request successfully and returns a favorable
response. response.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<S:Envelope <S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<S:Body> <S:Body>
<ns3:spppGetResponse <ns3:spppGetResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>success</msg> <msg>success</msg>
</overallResult> </overallResult>
<resultObj xsi:type="ns2:DestGrpType"> <resultObj xsi:type="ns2:DestGrpType">
<ns2:rant>iana-en:222</ns2:rant> <ns2:rant>iana-en:222</ns2:rant>
<ns2:rar>iana-en:223</ns2:rar> <ns2:rar>iana-en:223</ns2:rar>
<ns2:dgName>DEST_GRP_SSP2_1</ns2:dgName> <ns2:dgName>DEST_GRP_SSP2_1</ns2:dgName>
</resultObj> </resultObj>
</ns3:spppGetResponse> </ns3:spppGetResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
9.14. Get Public Identity 10.14. Get Public Identity
SSP2 obtains the last provisioned record associated with a given TN. SSP2 obtains the last provisioned record associated with a given TN.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"
xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1" xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:spppGetRequest> <urn:spppGetRequest>
<!--1 or more repetitions:--> <!--1 or more repetitions:-->
<objKey xsi:type="urn:PubIdKeyType"> <objKey xsi:type="urn:PubIdKeyType">
<rant>iana-en:222</rant> <rant>iana-en:222</rant>
<number> <number>
<urn1:value>+12025556666</urn1:value> <urn1:value>+12025556666</urn1:value>
<urn1:type>TN</urn1:type> <urn1:type>TN</urn1:type>
</number> </number>
</objKey> </objKey>
</urn:spppGetRequest> </urn:spppGetRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
Registry completes the request successfully and returns a favorable Registry completes the request successfully and returns a favorable
response. response.
<S:Envelope <S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<S:Body> <S:Body>
<ns3:spppGetResponse <ns3:spppGetResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>success</msg> <msg>success</msg>
</overallResult> </overallResult>
<resultObj xsi:type="ns2:TNType"> <resultObj xsi:type="ns2:TNType">
<ns2:rant>iana-en:222</ns2:rant> <ns2:rant>iana-en:222</ns2:rant>
<ns2:rar>iana-en:223</ns2:rar> <ns2:rar>iana-en:223</ns2:rar>
<ns2:dgName>DEST_GRP_SSP2_1</ns2:dgName> <ns2:dgName>DEST_GRP_SSP2_1</ns2:dgName>
<ns2:tn>+12025556666</ns2:tn> <ns2:tn>+12025556666</ns2:tn>
<ns2:corInfo> <ns2:corInfo>
<ns2:corClaim>true</ns2:corClaim> <ns2:corClaim>true</ns2:corClaim>
<ns2:cor>true</ns2:cor> <ns2:cor>true</ns2:cor>
<ns2:corDate>2010-05-30T09:30:10Z</ns2:corDate> <ns2:corDate>2010-05-30T09:30:10Z</ns2:corDate>
</ns2:corInfo> </ns2:corInfo>
</resultObj> </resultObj>
</ns3:spppGetResponse> </ns3:spppGetResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
9.15. Get Route Group Request 10.15. Get SED Group Request
SSP2 obtains the last provisioned record for the route group SSP2 obtains the last provisioned record for the SED group
RTE_GRP_SSP2_1. SED_GRP_SSP2_1.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:spppGetRequest> <urn:spppGetRequest>
<!--1 or more repetitions:--> <!--1 or more repetitions:-->
<objKey xsi:type="urn:ObjKeyType"> <objKey xsi:type="urn:ObjKeyType">
<rant>iana-en:222</rant> <rant>iana-en:222</rant>
<name>RTE_GRP_SSP2_1</name> <name>SED_GRP_SSP2_1</name>
<type>RteGrp</type> <type>SedGrp</type>
</objKey> </objKey>
</urn:spppGetRequest> </urn:spppGetRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
Registry completes the request successfully and returns a favorable Registry completes the request successfully and returns a favorable
response. response.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<S:Envelope <S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<S:Body> <S:Body>
<ns3:spppGetResponse <ns3:spppGetResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>success</msg> <msg>success</msg>
</overallResult> </overallResult>
<resultObj xsi:type="ns2:RteGrpType"> <resultObj xsi:type="ns2:SedGrpType">
<ns2:rant>iana-en:222</ns2:rant> <ns2:rant>iana-en:222</ns2:rant>
<ns2:rar>iana-en:223</ns2:rar> <ns2:rar>iana-en:223</ns2:rar>
<ns2:rgName>RTE_GRP_SSP2_1</ns2:rgName> <ns2:sedGrpName>SED_GRP_SSP2_1</ns2:sedGrpName>
<ns2:rrRef> <ns2:sedRecRef>
<ns2:rrKey xsi:type="ns3:ObjKeyType"> <ns2:sedKey xsi:type="ns3:ObjKeyType">
<rant>iana-en:222</rant> <rant>iana-en:222</rant>
<name>RTE_SSP2_SBE2</name> <name>SED_SSP2_SBE2</name>
<type>RteRec</type> <type>SedRec</type>
</ns2:rrKey> </ns2:sedKey>
<ns2:priority>100</ns2:priority> <ns2:priority>100</ns2:priority>
</ns2:rrRef> </ns2:sedRecRef>
<ns2:rrRef> <ns2:sedRecRef>
<ns2:rrKey xsi:type="ns3:ObjKeyType"> <ns2:sedKey xsi:type="ns3:ObjKeyType">
<rant>iana-en:222</rant> <rant>iana-en:222</rant>
<name>RTE_SSP2_SBE4</name> <name>SED_SSP2_SBE4</name>
<type>RteRec</type> <type>SedRec</type>
</ns2:rrKey> </ns2:sedKey>
<ns2:priority>101</ns2:priority> <ns2:priority>101</ns2:priority>
</ns2:rrRef> </ns2:sedRecRef>
<ns2:dgName>DEST_GRP_SSP2_1</ns2:dgName> <ns2:dgName>DEST_GRP_SSP2_1</ns2:dgName>
<ns2:isInSvc>true</ns2:isInSvc> <ns2:isInSvc>true</ns2:isInSvc>
<ns2:priority>10</ns2:priority> <ns2:priority>10</ns2:priority>
</resultObj> </resultObj>
</ns3:spppGetResponse> </ns3:spppGetResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
9.16. Get Route Group Offers Request 10.16. Get SED Group Offers Request
SSP2 fetches the last provisioned route group offer to the SSP2 fetches the last provisioned SED group offer to the <peeringOrg>
<peeringOrg> SSP1. SSP1.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:getRteGrpOffersRequest> <urn:getSedGrpOffersRequest>
<offeredTo>iana-en:111</offeredTo> <offeredTo>iana-en:111</offeredTo>
</urn:getRteGrpOffersRequest> </urn:getSedGrpOffersRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
Registry processes the request successfully and returns a favorable Registry processes the request successfully and returns a favorable
response. response.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<S:Envelope <S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<S:Body> <S:Body>
<ns3:spppGetResponse <ns3:spppGetResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>success</msg> <msg>success</msg>
</overallResult> </overallResult>
<resultObj xsi:type="ns2:RteGrpOfferType"> <resultObj xsi:type="ns2:SedGrpOfferType">
<ns2:rant>iana-en:222</ns2:rant> <ns2:rant>iana-en:222</ns2:rant>
<ns2:rar>iana-en:223</ns2:rar> <ns2:rar>iana-en:223</ns2:rar>
<ns2:rteGrpOfferKey <ns2:sedGrpOfferKey
xsi:type="ns3:RteGrpOfferKeyType"> xsi:type="ns3:SedGrpOfferKeyType">
<rteGrpKey> <sedGrpKey>
<rant>iana-en:222</rant> <rant>iana-en:222</rant>
<name>RTE_GRP_SSP2_1</name> <name>SED_GRP_SSP2_1</name>
<type>RteGrp</type> <type>SedGrp</type>
</rteGrpKey> </sedGrpKey>
<offeredTo>iana-en:111</offeredTo> <offeredTo>iana-en:111</offeredTo>
</ns2:rteGrpOfferKey> </ns2:sedGrpOfferKey>
<ns2:status>offered</ns2:status> <ns2:status>offered</ns2:status>
<ns2:offerDateTime> <ns2:offerDateTime>
2006-05-04T18:13:51.0Z 2006-05-04T18:13:51.0Z
</ns2:offerDateTime> </ns2:offerDateTime>
</resultObj> </resultObj>
</ns3:spppGetResponse> </ns3:spppGetResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
9.17. Get Egress Route 10.17. Get Egress Route
SSP1 wants to verify the last provisioned record for the egress route SSP1 wants to verify the last provisioned record for the egress route
called EGR_RTE_01. called EGR_RTE_01.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:spppGetRequest> <urn:spppGetRequest>
<!--1 or more repetitions:--> <!--1 or more repetitions:-->
<objKey xsi:type="urn:ObjKeyType"> <objKey xsi:type="urn:ObjKeyType">
<rant>iana-en:111</rant> <rant>iana-en:111</rant>
<name>EGR_RTE_01</name> <name>EGR_RTE_01</name>
<type>EgrRte</type> <type>EgrRte</type>
</objKey> </objKey>
</urn:spppGetRequest> </urn:spppGetRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
Registry completes the request successfully and returns a favorable Registry completes the request successfully and returns a favorable
response. response.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<S:Envelope <S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<S:Body> <S:Body>
<ns3:spppGetResponse <ns3:spppGetResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>success</msg> <msg>success</msg>
</overallResult> </overallResult>
<resultObj xsi:type="ns2:EgrRteType"> <resultObj xsi:type="ns2:EgrRteType">
<ns2:rant>iana-en:222</ns2:rant> <ns2:rant>iana-en:222</ns2:rant>
<ns2:rar>iana-en:223</ns2:rar> <ns2:rar>iana-en:223</ns2:rar>
<ns2:egrRteName>EGR_RTE_01</ns2:egrRteName> <ns2:egrRteName>EGR_RTE_01</ns2:egrRteName>
<ns2:pref>50</ns2:pref> <ns2:pref>50</ns2:pref>
<ns2:regxRewriteRule> <ns2:regxRewriteRule>
<ns2:ere>^(.*)$</ns2:ere> <ns2:ere>^(.*)$</ns2:ere>
<ns2:repl>sip:\1@sbe1.ssp1.example.com</ns2:repl> <ns2:repl>sip:\1@sbe1.ssp1.example.com</ns2:repl>
</ns2:regxRewriteRule> </ns2:regxRewriteRule>
<ns2:ingrRteRec xsi:type="ns3:ObjKeyType"> <ns2:ingrSedGrp xsi:type="ns3:ObjKeyType">
<rant>iana-en:222</rant> <rant>iana-en:222</rant>
<name>RTE_GRP_SSP2_1</name> <name>SED_GRP_SSP2_1</name>
<type>RteRec</type> <type>SedRec</type>
</ns2:ingrRteRec> </ns2:ingrSedGrp>
</resultObj> </resultObj>
</ns3:spppGetResponse> </ns3:spppGetResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
9.18. Delete Destination Group 10.18. Delete Destination Group
SSP2 initiates a request to delete the destination group SSP2 initiates a request to delete the destination group
DEST_GRP_SSP2_1. DEST_GRP_SSP2_1.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:spppDelRequest> <urn:spppDelRequest>
<!--1 or more repetitions:--> <!--1 or more repetitions:-->
<objKey xsi:type="urn:ObjKeyType"> <objKey xsi:type="urn:ObjKeyType">
<rant>iana-en:222</rant> <rant>iana-en:222</rant>
<name>DEST_GRP_SSP2_1</name> <name>DEST_GRP_SSP2_1</name>
<type>DestGrp</type> <type>DestGrp</type>
</objKey> </objKey>
</urn:spppDelRequest> </urn:spppDelRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
Registry completes the request successfully and returns a favorable Registry completes the request successfully and returns a favorable
response. response.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<S:Envelope <S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body> <S:Body>
<ns3:spppDelResponse <ns3:spppDelResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<serverTransId>tx_12354</serverTransId> <serverTransId>tx_12354</serverTransId>
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>Request Succeeded.</msg> <msg>Request Succeeded.</msg>
</overallResult> </overallResult>
</ns3:spppDelResponse> </ns3:spppDelResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
9.19. Delete Public Identity 10.19. Delete Public Identity
SSP2 chooses to de-activate the TN and remove it from the registry. SSP2 chooses to de-activate the TN and remove it from the registry.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"
xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1" xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:spppDelRequest> <urn:spppDelRequest>
<!--1 or more repetitions:--> <!--1 or more repetitions:-->
<objKey xsi:type="urn:PubIdKeyType"> <objKey xsi:type="urn:PubIdKeyType">
<rant>iana-en:222</rant> <rant>iana-en:222</rant>
<dgName>DEST_GRP_SSP2_1</dgName> <dgName>DEST_GRP_SSP2_1</dgName>
<number> <number>
<urn1:value>+12025556666</urn1:value> <urn1:value>+12025556666</urn1:value>
<urn1:type>TN</urn1:type> <urn1:type>TN</urn1:type>
</number> </number>
</objKey> </objKey>
</urn:spppDelRequest> </urn:spppDelRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
Registry completes the request successfully and returns a favorable Registry completes the request successfully and returns a favorable
response. response.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<S:Envelope <S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body> <S:Body>
<ns3:spppDelResponse <ns3:spppDelResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<serverTransId>tx_12354</serverTransId> <serverTransId>tx_12354</serverTransId>
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>Request Succeeded.</msg> <msg>Request Succeeded.</msg>
</overallResult> </overallResult>
</ns3:spppDelResponse> </ns3:spppDelResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
9.20. Delete Route Group Request 10.20. Delete SED Group Request
SSP2 removes the route group called RTE_GRP_SSP2_1. SSP2 removes the SED group called SED_GRP_SSP2_1.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:spppDelRequest> <urn:spppDelRequest>
<!--1 or more repetitions:--> <!--1 or more repetitions:-->
<objKey xsi:type="urn:ObjKeyType"> <objKey xsi:type="urn:ObjKeyType">
<rant>iana-en:222</rant> <rant>iana-en:222</rant>
<name>RTE_GRP_SSP2_1</name> <name>SED_GRP_SSP2_1</name>
<type>RteGrp</type> <type>SedGrp</type>
</objKey> </objKey>
</urn:spppDelRequest> </urn:spppDelRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
Registry completes the request successfully and returns a favorable Registry completes the request successfully and returns a favorable
response. response.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<S:Envelope <S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body> <S:Body>
<ns3:spppDelResponse <ns3:spppDelResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<serverTransId>tx_12354</serverTransId> <serverTransId>tx_12354</serverTransId>
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>Request Succeeded.</msg> <msg>Request Succeeded.</msg>
</overallResult> </overallResult>
</ns3:spppDelResponse> </ns3:spppDelResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
9.21. Delete Route Group Offers Request 10.21. Delete SED Group Offers Request
SSP2 no longer wants to share route group RTE_GRP_SSP2_1 with SSP1. SSP2 no longer wants to share SED group SED_GRP_SSP2_1 with SSP1.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:spppDelRequest> <urn:spppDelRequest>
<!--1 or more repetitions:--> <!--1 or more repetitions:-->
<objKey xsi:type="urn:RteGrpOfferKeyType"> <objKey xsi:type="urn:SedGrpOfferKeyType">
<rteGrpKey> <sedGrpKey>
<rant>iana-en:222</rant> <rant>iana-en:222</rant>
<name>RTE_GRP_SSP2_1</name> <name>SED_GRP_SSP2_1</name>
<type>RteGrp</type> <type>SedGrp</type>
</rteGrpKey> </sedGrpKey>
<offeredTo>iana-en:111</offeredTo> <offeredTo>iana-en:111</offeredTo>
</objKey> </objKey>
</urn:spppDelRequest> </urn:spppDelRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
Registry completes the request successfully and returns a favorable Registry completes the request successfully and returns a favorable
response. Restoring this resource sharing will require a new route response. Restoring this resource sharing will require a new SED
group offer from SSP2 to SSP1 followed by a successful route group group offer from SSP2 to SSP1 followed by a successful SED group
accept request from SSP1. accept request from SSP1.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<S:Envelope <S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body> <S:Body>
<ns3:spppDelResponse <ns3:spppDelResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<serverTransId>tx_12354</serverTransId> <serverTransId>tx_12354</serverTransId>
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>Request Succeeded.</msg> <msg>Request Succeeded.</msg>
</overallResult> </overallResult>
</ns3:spppDelResponse> </ns3:spppDelResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
9.22. Delete Egress Route 10.22. Delete Egress Route
SSP1 decides to remove the egress route with the label EGR_RTE_01. SSP1 decides to remove the egress route with the label EGR_RTE_01.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:spppDelRequest> <urn:spppDelRequest>
<!--1 or more repetitions:--> <!--1 or more repetitions:-->
<objKey xsi:type="urn:ObjKeyType"> <objKey xsi:type="urn:ObjKeyType">
<rant>iana-en:111</rant> <rant>iana-en:111</rant>
<name>EGR_RTE_01</name> <name>EGR_RTE_01</name>
<type>EgrRte</type> <type>EgrRte</type>
</objKey> </objKey>
</urn:spppDelRequest> </urn:spppDelRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
Registry completes the request successfully and returns a favorable Registry completes the request successfully and returns a favorable
response. response.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<S:Envelope <S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body> <S:Body>
<ns3:spppDelResponse <ns3:spppDelResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<serverTransId>tx_12354</serverTransId> <serverTransId>tx_12354</serverTransId>
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>Request Succeeded.</msg> <msg>Request Succeeded.</msg>
</overallResult> </overallResult>
</ns3:spppDelResponse> </ns3:spppDelResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
9.23. Batch Request 10.23. Batch Request
Following is an example of how some of the operations mentioned in Following is an example of how some of the operations mentioned in
previous sections MAY be performed by an SPPF client as a batch in previous sections MAY be performed by an SPPF client as a batch in
one single SPP Protocol over SOAP request. one single SPP Protocol over SOAP request.
In the sample request below SSP1 wants to accept a Route Group Offer In the sample request below SSP1 wants to accept a SED Group Offer
from SSP3, add a Destination Group, add a NAPTR Route Rec, add a from SSP3, add a Destination Group, add a NAPTR SED Record, add a SED
Route Group, add a Route Group Offer, delete a previously provisioned Group, add a SED Group Offer, delete a previously provisioned TN type
TN type Public Identifier, delete a previously provisioned Route Public Identifier, delete a previously provisioned SED Group, and
Group, and reject a Route Group Offer from SSP4. reject a SED Group Offer from SSP4.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"
xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1" xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/> <soapenv:Header/>
<soapenv:Body> <soapenv:Body>
<urn:spppBatchRequest> <urn:spppBatchRequest>
<clientTransId>txn_1467</clientTransId> <clientTransId>txn_1467</clientTransId>
<minorVer>1</minorVer> <minorVer>1</minorVer>
<acceptRteGrpOffer> <acceptSedGrpOffer>
<rteGrpKey> <sedGrpKey>
<rant>iana-en:225</rant> <rant>iana-en:225</rant>
<name>RTE_SSP3_SBE1_Offered</name> <name>SED_SSP3_SBE1_Offered</name>
<type>RteGrp</type> <type>SedGrp</type>
</rteGrpKey> </sedGrpKey>
<offeredTo>iana-en:222</offeredTo> <offeredTo>iana-en:222</offeredTo>
</acceptRteGrpOffer> </acceptSedGrpOffer>
<addObj xsi:type="urn1:DestGrpType"> <addObj xsi:type="urn1:DestGrpType">
<urn1:rant>iana-en:222</urn1:rant> <urn1:rant>iana-en:222</urn1:rant>
<urn1:rar>iana-en:223</urn1:rar> <urn1:rar>iana-en:223</urn1:rar>
<urn1:dgName>DEST_GRP_SSP2_1</urn1:dgName> <urn1:dgName>DEST_GRP_SSP2_1</urn1:dgName>
</addObj> </addObj>
<addObj xsi:type="urn1:NAPTRType"> <addObj xsi:type="urn1:NAPTRType">
<urn1:rant>iana-en:222</urn1:rant> <urn1:rant>iana-en:222</urn1:rant>
<urn1:rar>iana-en:223</urn1:rar> <urn1:rar>iana-en:223</urn1:rar>
<urn1:rrName>RTE_SSP2_SBE2</urn1:rrName> <urn1:sedName>SED_SSP2_SBE2</urn1:sedName>
<urn1:order>10</urn1:order> <urn1:order>10</urn1:order>
<urn1:flags>u</urn1:flags> <urn1:flags>u</urn1:flags>
<urn1:svcs>E2U+sip</urn1:svcs> <urn1:svcs>E2U+sip</urn1:svcs>
<urn1:regx> <urn1:regx>
<urn1:ere>^(.*)$</urn1:ere> <urn1:ere>^(.*)$</urn1:ere>
<urn1:repl>sip:\1@sbe2.ssp2.example.com</urn1:repl> <urn1:repl>sip:\1@sbe2.ssp2.example.com</urn1:repl>
</urn1:regx> </urn1:regx>
</addObj> </addObj>
<addObj xsi:type="urn1:RteGrpType"> <addObj xsi:type="urn1:SedGrpType">
<urn1:rant>iana-en:222</urn1:rant> <urn1:rant>iana-en:222</urn1:rant>
<urn1:rar>iana-en:223</urn1:rar> <urn1:rar>iana-en:223</urn1:rar>
<urn1:rgName>RTE_GRP_SSP2_1</urn1:rgName> <urn1:sedGrpName>SED_GRP_SSP2_1</urn1:sedGrpName>
<urn1:rrRef> <urn1:sedRecRef>
<urn1:rrKey xsi:type="urn:ObjKeyType"> <urn1:sedKey xsi:type="urn:ObjKeyType">
<rant>iana-en:222</rant> <rant>iana-en:222</rant>
<name>RTE_SSP2_SBE2</name> <name>SED_SSP2_SBE2</name>
<type>RteRec</type> <type>SedRec</type>
</urn1:rrKey> </urn1:sedKey>
<urn1:priority>100</urn1:priority> <urn1:priority>100</urn1:priority>
</urn1:rrRef> </urn1:sedRecRef>
<urn1:dgName>DEST_GRP_SSP2_1</urn1:dgName> <urn1:dgName>DEST_GRP_SSP2_1</urn1:dgName>
<urn1:isInSvc>true</urn1:isInSvc> <urn1:isInSvc>true</urn1:isInSvc>
<urn1:priority>10</urn1:priority> <urn1:priority>10</urn1:priority>
</addObj> </addObj>
<addObj xsi:type="urn1:RteGrpOfferType"> <addObj xsi:type="urn1:SedGrpOfferType">
<urn1:rant>iana-en:222</urn1:rant> <urn1:rant>iana-en:222</urn1:rant>
<urn1:rar>iana-en:223</urn1:rar> <urn1:rar>iana-en:223</urn1:rar>
<urn1:rteGrpOfferKey xsi:type="urn:RteGrpOfferKeyType"> <urn1:sedGrpOfferKey xsi:type="urn:SedGrpOfferKeyType">
<rteGrpKey xsi:type="urn:ObjKeyType"> <sedGrpKey xsi:type="urn:ObjKeyType">
<rant>iana-en:222</rant> <rant>iana-en:222</rant>
<name>RTE_GRP_SSP2_1</name> <name>SED_GRP_SSP2_1</name>
<type>RteGrp</type> <type>SedGrp</type>
</rteGrpKey> </sedGrpKey>
<offeredTo>iana-en:111</offeredTo> <offeredTo>iana-en:111</offeredTo>
</urn1:rteGrpOfferKey> </urn1:sedGrpOfferKey>
<urn1:status>offered</urn1:status> <urn1:status>offered</urn1:status>
<urn1:offerDateTime> <urn1:offerDateTime>
2006-05-04T18:13:51.0Z 2006-05-04T18:13:51.0Z
</urn1:offerDateTime> </urn1:offerDateTime>
</addObj> </addObj>
<delObj xsi:type="urn:PubIdKeyType"> <delObj xsi:type="urn:PubIdKeyType">
<rant>iana-en:222</rant> <rant>iana-en:222</rant>
<dgName>DEST_GRP_SSP2_Previous</dgName> <dgxDEST_GRP_SSP2_Previous</dgName>
<number> <number>
<urn1:value>+12025556666</urn1:value> <urn1:value>+12025556666</urn1:value>
<urn1:type>TN</urn1:type> <urn1:type>TN</urn1:type>
</number> </number>
</delObj> </delObj>
<delObj xsi:type="urn:ObjKeyType"> <delObj xsi:type="urn:ObjKeyType">
<rant>iana-en:222</rant> <rant>iana-en:222</rant>
<name>RTE_GRP_SSP2_Previous</name> <name>SED_GRP_SSP2_Previous</name>
<type>RteGrp</type> <type>SedGrp</type>
</delObj> </delObj>
<rejectRteGrpOffer> <rejectSedGrpOffer>
<rteGrpKey> <sedGrpKey>
<rant>iana-en:226</rant> <rant>iana-en:226</rant>
<name>RTE_SSP4_SBE1_Offered</name> <name>SED_SSP4_SBE1_Offered</name>
<type>RteGrp</type> <type>SedGrp</type>
</rteGrpKey> </sedGrpKey>
<offeredTo>iana-en:222</offeredTo> <offeredTo>iana-en:222</offeredTo>
</rejectRteGrpOffer> </rejectSedGrpOffer>
</urn:spppBatchRequest> </urn:spppBatchRequest>
</soapenv:Body> </soapenv:Body>
</soapenv:Envelope> </soapenv:Envelope>
Registry completes the request successfully and returns a favorable Registry completes the request successfully and returns a favorable
response. response.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<S:Envelope <S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body> <S:Body>
<ns3:spppBatchResponse <ns3:spppBatchResponse
xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
<serverTransId>tx_12354</serverTransId> <serverTransId>tx_12354</serverTransId>
<overallResult> <overallResult>
<code>1000</code> <code>1000</code>
<msg>Request Succeeded.</msg> <msg>Request Succeeded.</msg>
</overallResult> </overallResult>
</ns3:spppBatchResponse> </ns3:spppBatchResponse>
</S:Body> </S:Body>
</S:Envelope> </S:Envelope>
10. Security Considerations 11. Security Considerations
SPP Protocol over SOAP is used to query and update session peering SPP Protocol over SOAP is used to query and update session peering
data and addresses, so the ability to access this protocol should be data and addresses, so the ability to access this protocol should be
limited to users and systems that are authorized to query and update limited to users and systems that are authorized to query and update
this data. Because this data is sent in both directions, it may not this data. Because this data is sent in both directions, it may not
be sufficient for just the client or user to be authenticated with be sufficient for just the client or user to be authenticated with
the server. The identity of the server should also be authenticated the server. The identity of the server should also be authenticated
by the client, which is often accomplished using the TLS certificate by the client, which is often accomplished using the TLS certificate
exchange and validation described in [RFC2818]. SPP Protocol over exchange and validation described in [RFC2818]. SPP Protocol over
SOAP messages may include sensitive information, routing data, lists SOAP messages may include sensitive information, routing data, lists
of resolvable addresses, etc. So when used in a production setting of resolvable addresses, etc. So when used in a production setting
and across non-secure networks, SPP Protocol over SOAP should only be and across non-secure networks, SPP Protocol over SOAP should only be
used over communications channels that provide strong encryption for used over communications channels that provide strong encryption for
data privacy. data privacy.
10.1. Integrity, Privacy, and Authentication 11.1. Integrity, Privacy, and Authentication
The SPP Protocol over SOAP binding relies on an underlying secure The SPP Protocol over SOAP binding relies on an underlying secure
transport for integrity and privacy. Such transports are expected to transport for integrity and privacy. Such transports are expected to
include TLS/HTTPS. In addition to the application level include TLS/HTTPS. In addition to the application level
authentication imposed by an SPPF server, there are a number of authentication imposed by an SPPF server, there are a number of
options for authentication within the transport layer and the options for authentication within the transport layer and the
messaging envelope. These include TLS client certificates, HTTP messaging envelope. These include TLS client certificates, HTTP
Digest Access Authentication, and digital signatures within SOAP Digest Access Authentication, and digital signatures within SOAP
headers. headers.
At a minimum, all conforming SPP Protocol over SOAP implementations At a minimum, all conforming SPP Protocol over SOAP implementations
MUST support HTTPS. MUST support HTTPS.
10.2. Vulnerabilities 11.2. Vulnerabilities
The above protocols may have various vulnerabilities, and these may The above protocols may have various vulnerabilities, and these may
be inherited by SPP Protocol over SOAP. SPP Protocol over SOAP be inherited by SPP Protocol over SOAP. SPP Protocol over SOAP
itself may have vulnerabilities because an authorization model is not itself may have vulnerabilities because an authorization model is not
explicitly specified in the current specification. explicitly specified in the current specification.
Sections 5 and 10.1 describe requirements for HTTPS support using Sections 5 and 10.1 describe requirements for HTTPS support using
TLS. Non-anonymous TLS servers can optionally request a certificate TLS. Non-anonymous TLS servers can optionally request a certificate
from a TLS client; that option is not a requirement for this from a TLS client; that option is not a requirement for this
protocol. This presents a denial of service risk in which protocol. This presents a denial of service risk in which
skipping to change at page 87, line 11 skipping to change at page 86, line 11
client-initiated renegotiation on the server and by ensuring that client-initiated renegotiation on the server and by ensuring that
other means (such as firewall access control lists) are used to other means (such as firewall access control lists) are used to
restrict unauthenticated client access to servers. restrict unauthenticated client access to servers.
In conjunction with the above, it is important that SPP Protocol over In conjunction with the above, it is important that SPP Protocol over
SOAP implementations implement an authorization model that considers SOAP implementations implement an authorization model that considers
the source of each query or update request and determines whether it the source of each query or update request and determines whether it
is reasonable to authorize that source to perform that specific query is reasonable to authorize that source to perform that specific query
or update. or update.
10.3. Deployment Environment Specifics 11.3. Deployment Environment Specifics
Some deployments of SPP Protocol over SOAP could choose to use Some deployments of SPP Protocol over SOAP could choose to use
transports without encryption. This presents vulnerabilities but transports without encryption. This presents vulnerabilities but
could be selected for deployments involving closed networks or could be selected for deployments involving closed networks or
debugging scenarios. However, the vulnerabilities of such a debugging scenarios. However, the vulnerabilities of such a
deployment could be a lack of integrity and privacy of the data deployment could be a lack of integrity and privacy of the data
transported in this type of deployment. transported in this type of deployment.
11. IANA Considerations 12. IANA Considerations
This document uses URNs to describe XML namespaces and XML schemas This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in [RFC3688]. conforming to a registry mechanism described in [RFC3688].
URN assignments requested are: urn:ietf:params:xml:ns:sppf:soap:1 URN assignments requested are: urn:ietf:params:xml:ns:sppf:soap:1
12. Acknowledgements 13. Acknowledgements
This document is a result of various discussions held by the DRINKS This document is a result of various discussions held by the DRINKS
design team, which is comprised of the following individuals, in design team, with contributions from the following individuals, in
alphabetical order: Alexander Mayrhofer, David Schwartz, Deborah A alphabetical order: Alexander Mayrhofer, David Schwartz, Deborah A
Guyton, Jean-Francois Mule Kenneth Cartwright, Lisa Dusseault, Manjul Guyton, Jean-Francois Mule Kenneth Cartwright, Lisa Dusseault, Manjul
Maharishi, Mickael Marrache, Otmar Lendl, Peter Saint-Andre, Richard Maharishi, Mickael Marrache, Otmar Lendl, Peter Saint-Andre, Richard
Shockey, Samuel Melloul, Scott Hollenbeck, Sumanth Channabasappa, Shockey, Samuel Melloul, Scott Hollenbeck, Sumanth Channabasappa,
Syed Ali, and Vikas Bhatia . Syed Ali, and Vikas Bhatia .
13. References 14. References
13.1. Normative References 14.1. Normative References
[I-D.draft-ietf-drinks-spp-framework] [I-D.draft-ietf-drinks-spp-framework]
Mule, J-F., Cartwright, K., Ali, S., Mayrhofer, A., and V. Cartwright, K., Bhatia, V., Ali, S., and D. Schwartz,
Bhatia, "Session Peering Provisioning Framework", "Session Peering Provisioning Framework",
draft-ietf-drinks-spp-framework-01 (work in progress), draft-ietf-drinks-spp-framework-02 (work in progress),
March 2012. July 2012.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[RFC2617] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., [RFC2617] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S.,
Leach, P., Luotonen, A., and L. Stewart, "HTTP Leach, P., Luotonen, A., and L. Stewart, "HTTP
skipping to change at page 90, line 37 skipping to change at page 89, line 37
[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.
[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.
[SOAPREF] Gudgin, M., Hadley, M., Moreau, J., and H. Nielsen, "SOAP [SOAPREF] Gudgin, M., Hadley, M., Moreau, J., and H. Nielsen, "SOAP
Version 1.2 Part 1: Messaging Framework", W3C Version 1.2 Part 1: Messaging Framework", W3C
Recommendation REC-SOAP12-part1-20030624, June 2002. Recommendation REC-SOAP12-part1-20030624, June 2002.
13.2. Informative References 14.2. Informative References
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000. [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000.
[RFC5321] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321, [RFC5321] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321,
October 2008. October 2008.
[W3C.REC-xml-20081126]
Sperberg-McQueen, C., Yergeau, F., Bray, T., Maler, E.,
and J. Paoli, "Extensible Markup Language (XML) 1.0 (Fifth
Edition)", World Wide Web Consortium Recommendation REC-
xml-20081126, November 2008,
<http://www.w3.org/TR/2008/REC-xml-20081126>.
[WSDLREF] Christensen, E., Curbera, F., Meredith, G., and S. [WSDLREF] Christensen, E., Curbera, F., Meredith, G., and S.
Weerawarana, "Web Services Description Language (WSDL) Weerawarana, "Web Services Description Language (WSDL)
1.1", W3C Note NOTE-wsdl-20010315, March 2001. 1.1", W3C Note NOTE-wsdl-20010315, March 2001.
Authors' Addresses Authors' Addresses
Kenneth Cartwright Kenneth Cartwright
TNS TNS
1939 Roland Clarke Place 1939 Roland Clarke Place
Reston, VA 20191 Reston, VA 20191
skipping to change at line 3471 skipping to change at page 91, line 22
Email: kcartwright@tnsi.com Email: kcartwright@tnsi.com
Vikas Bhatia Vikas Bhatia
TNS TNS
1939 Roland Clarke Place 1939 Roland Clarke Place
Reston, VA 20191 Reston, VA 20191
USA USA
Email: vbhatia@tnsi.com Email: vbhatia@tnsi.com
Jean-Francois Mule
CableLabs
858 Coal Creek Circle
Louisville, CO 80027
USA
Email: jfm@cablelabs.com
Alexander Mayrhofer
enum.at GmbH
Karlsplatz 1/9
Wien, A-1010
Austria
Email: alexander.mayrhofer@enum.at
 End of changes. 234 change blocks. 
1301 lines changed or deleted 1300 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/