draft-ietf-drinks-spprov-06.txt		draft-ietf-drinks-spprov-07.txt
	DRINKS J-F. Mule		DRINKS J-F. Mule
	Internet-Draft CableLabs		Internet-Draft CableLabs
	Intended status: Standards Track K. Cartwright		Intended status: Standards Track K. Cartwright
	Expires: September 12, 2011 TNS		Expires: October 21, 2011 TNS
	S. Ali		S. Ali
	NeuStar		NeuStar
	A. Mayrhofer		A. Mayrhofer
	enum.at GmbH		enum.at GmbH
	March 11, 2011		April 19, 2011
	Session Peering Provisioning Protocol		Session Peering Provisioning Protocol
	draft-ietf-drinks-spprov-06		draft-ietf-drinks-spprov-07
	Abstract		Abstract
	This document defines a protocol for provisioning session		This document defines a protocol for provisioning session
	establishment data into Session Data Registries and SIP Service		establishment data into Session Data Registries and SIP Service
	Provider data stores. The provisioned data is typically used by		Provider data stores. The provisioned data is typically used by
	various network elements for session peering.		various network elements for session peering.
	This document describes the Session Peering Provisioning Protocol		This document describes the Session Peering Provisioning Protocol
	used by clients to provision registries. The document provides a set		used by clients to provision registries. The document provides a set
	skipping to change at page 1, line 44		skipping to change at page 1, line 44
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on September 12, 2011.		This Internet-Draft will expire on October 21, 2011.
	Copyright Notice		Copyright Notice
	Copyright (c) 2011 IETF Trust and the persons identified as the		Copyright (c) 2011 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 49		skipping to change at page 2, line 49
	6. Protocol Commands . . . . . . . . . . . . . . . . . . . . . . 26		6. Protocol Commands . . . . . . . . . . . . . . . . . . . . . . 26
	6.1. Add Destination Group Operation . . . . . . . . . . . . . 26		6.1. Add Destination Group Operation . . . . . . . . . . . . . 26
	6.2. Get Destination Groups Operation . . . . . . . . . . . . . 27		6.2. Get Destination Groups Operation . . . . . . . . . . . . . 27
	6.3. Add Public Identifier Operation . . . . . . . . . . . . . 28		6.3. Add Public Identifier Operation . . . . . . . . . . . . . 28
	6.4. Get Public Identifiers Operation . . . . . . . . . . . . . 33		6.4. Get Public Identifiers Operation . . . . . . . . . . . . . 33
	6.5. Add Route Group Operation . . . . . . . . . . . . . . . . 33		6.5. Add Route Group Operation . . . . . . . . . . . . . . . . 33
	6.6. Get Route Groups Operation . . . . . . . . . . . . . . . . 38		6.6. Get Route Groups Operation . . . . . . . . . . . . . . . . 38
	6.7. Add Route Record Operation . . . . . . . . . . . . . . . . 39		6.7. Add Route Record Operation . . . . . . . . . . . . . . . . 39
	6.8. Get Route Records Operation . . . . . . . . . . . . . . . 43		6.8. Get Route Records Operation . . . . . . . . . . . . . . . 43
	6.9. Add Route Group Offer Operation . . . . . . . . . . . . . 44		6.9. Add Route Group Offer Operation . . . . . . . . . . . . . 44
	6.10. Accept Route Group Offer Operation . . . . . . . . . . . . 47		6.10. Accept Route Group Offer Operation . . . . . . . . . . . . 46
	6.11. Reject Route Group Offer Operation . . . . . . . . . . . . 48		6.11. Reject Route Group Offer Operation . . . . . . . . . . . . 47
	6.12. Get Route Group Offers Operation . . . . . . . . . . . . . 49		6.12. Get Route Group Offers Operation . . . . . . . . . . . . . 48
	6.13. Egress Route Operations . . . . . . . . . . . . . . . . . 50		6.13. Egress Route Operations . . . . . . . . . . . . . . . . . 50
	6.14. Delete Operation . . . . . . . . . . . . . . . . . . . . . 52		6.14. Delete Operation . . . . . . . . . . . . . . . . . . . . . 52
	7. SPPP Examples . . . . . . . . . . . . . . . . . . . . . . . . 55		7. SPPP Examples . . . . . . . . . . . . . . . . . . . . . . . . 54
	7.1. Add Destination Group . . . . . . . . . . . . . . . . . . 55		7.1. Add Destination Group . . . . . . . . . . . . . . . . . . 54
	7.2. Add Route Records . . . . . . . . . . . . . . . . . . . . 56		7.2. Add Route Records . . . . . . . . . . . . . . . . . . . . 55
	7.3. Add Route Records -- URIType . . . . . . . . . . . . . . . 57		7.3. Add Route Records -- URIType . . . . . . . . . . . . . . . 56
	7.4. Add Route Group . . . . . . . . . . . . . . . . . . . . . 58		7.4. Add Route Group . . . . . . . . . . . . . . . . . . . . . 57
	7.5. Add Public Identity -- Successful COR claim . . . . . . . 60		7.5. Add Public Identity -- Successful COR claim . . . . . . . 58
	7.6. Add LRN . . . . . . . . . . . . . . . . . . . . . . . . . 61		7.6. Add LRN . . . . . . . . . . . . . . . . . . . . . . . . . 60
	7.7. Add TN Range . . . . . . . . . . . . . . . . . . . . . . . 62		7.7. Add TN Range . . . . . . . . . . . . . . . . . . . . . . . 61
	7.8. Add TN Prefix . . . . . . . . . . . . . . . . . . . . . . 63		7.8. Add TN Prefix . . . . . . . . . . . . . . . . . . . . . . 62
	7.9. Enable Peering -- Route Group Offer . . . . . . . . . . . 64		7.9. Enable Peering -- Route Group Offer . . . . . . . . . . . 63
	7.10. Enable Peering -- Route Group Offer Accept . . . . . . . . 66		7.10. Enable Peering -- Route Group Offer Accept . . . . . . . . 64
	7.11. Add Egress Route . . . . . . . . . . . . . . . . . . . . . 67		7.11. Add Egress Route . . . . . . . . . . . . . . . . . . . . . 65
	7.12. Get Destination Group . . . . . . . . . . . . . . . . . . 68		7.12. Get Destination Group . . . . . . . . . . . . . . . . . . 66
	7.13. Get Public Identity . . . . . . . . . . . . . . . . . . . 69		7.13. Get Public Identity . . . . . . . . . . . . . . . . . . . 67
	7.14. Get Route Group Request . . . . . . . . . . . . . . . . . 70		7.14. Get Route Group Request . . . . . . . . . . . . . . . . . 68
	7.15. Get Route Group Offers Request . . . . . . . . . . . . . . 71		7.15. Get Route Group Offers Request . . . . . . . . . . . . . . 70
	7.16. Get Egress Route . . . . . . . . . . . . . . . . . . . . . 72		7.16. Get Egress Route . . . . . . . . . . . . . . . . . . . . . 71
	7.17. Delete Destination Group . . . . . . . . . . . . . . . . . 74		7.17. Delete Destination Group . . . . . . . . . . . . . . . . . 72
	7.18. Delete Public Identity . . . . . . . . . . . . . . . . . . 74		7.18. Delete Public Identity . . . . . . . . . . . . . . . . . . 73
	7.19. Delete Route Group Request . . . . . . . . . . . . . . . . 75		7.19. Delete Route Group Request . . . . . . . . . . . . . . . . 74
	7.20. Delete Route Group Offers Request . . . . . . . . . . . . 76		7.20. Delete Route Group Offers Request . . . . . . . . . . . . 75
	7.21. Delete Egress Route . . . . . . . . . . . . . . . . . . . 77		7.21. Delete Egress Route . . . . . . . . . . . . . . . . . . . 75
	8. XML Considerations . . . . . . . . . . . . . . . . . . . . . . 79		8. XML Considerations . . . . . . . . . . . . . . . . . . . . . . 77
	8.1. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 79		8.1. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 77
	8.2. Versioning and Character Encoding . . . . . . . . . . . . 79		8.2. Versioning and Character Encoding . . . . . . . . . . . . 77
	9. Security Considerations . . . . . . . . . . . . . . . . . . . 80		9. Security Considerations . . . . . . . . . . . . . . . . . . . 78
	10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 81		10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 79
	11. Formal Specification . . . . . . . . . . . . . . . . . . . . . 82		11. Formal Specification . . . . . . . . . . . . . . . . . . . . . 80
	12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 94		12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 93
	13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 95		13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 94
	13.1. Normative References . . . . . . . . . . . . . . . . . . . 95		13.1. Normative References . . . . . . . . . . . . . . . . . . . 94
	13.2. Informative References . . . . . . . . . . . . . . . . . . 95		13.2. Informative References . . . . . . . . . . . . . . . . . . 94
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 97		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 96
	1. Introduction		1. Introduction
	Service providers and enterprises use registries to make call or		Service providers and enterprises use registries to make call or
	session routing decisions for Voice over IP, SMS and MMS traffic		session routing decisions for Voice over IP, SMS and MMS traffic
	exchanges. This document is narrowly focused on the provisioning		exchanges. This document is narrowly focused on the provisioning
	protocol for these registries. This protocol prescribes a way for an		protocol for these registries. This protocol prescribes a way for an
	entity to provision session-related data into a registry. The data		entity to provision session-related data into a registry. The data
	being provisioned can be optionally shared with other participating		being provisioned can be optionally shared with other participating
	peering entities. The requirements and use cases driving this		peering entities. The requirements and use cases driving this
	skipping to change at page 8, line 6		skipping to change at page 9, line 5
	is pictured as a SIP Service Provider in Figure 2.		is pictured as a SIP Service Provider in Figure 2.
	A Registrant is uniquely identified by its ID.		A Registrant is uniquely identified by its ID.
	Registrar: In this document, we also extend the definition of a		Registrar: In this document, we also extend the definition of a
	Registrar from [RFC4725]. A Registrar performs provisioning		Registrar from [RFC4725]. A Registrar performs provisioning
	operations on behalf of a Registrant by interacting with the		operations on behalf of a Registrant by interacting with the
	Registry, in our case via the SPPP protocol defined in this		Registry, in our case via the SPPP protocol defined in this
	document.		document.
	A Registrar is identified by its ID.
	3. Protocol High Level Design		3. Protocol High Level Design
	This section introduces the structure of the data model and provides		This section introduces the structure of the data model and provides
	the information framework for the SPPP protocol. An overview of the		the information framework for the SPPP protocol. An overview of the
	protocol operations is first provided with a typical deployment		protocol operations is first provided with a typical deployment
	scenario. The data model is then defined along with all the objects		scenario. The data model is then defined along with all the objects
	manipulated by the protocol and their relationships.		manipulated by the protocol and their relationships.
	3.1. Protocol Layering		3.1. Protocol Layering
	skipping to change at page 11, line 4		skipping to change at page 11, line 4
	The logical structure presented below is consistent with the		The logical structure presented below is consistent with the
	terminology and requirements defined in		terminology and requirements defined in
	[I-D.ietf-drinks-usecases-requirements].		[I-D.ietf-drinks-usecases-requirements].
	+-------------+ +------------------+		+-------------+ +------------------+
	| all object | |Organization: |		| all object | |Organization: |
	| types | |orgId |		| types | |orgId |
	+------+------+ | |		+------+------+ | |
	+------------>| |		+------------>| |
	All objects are +------------------+		All objects are +------------------+
	associated with 2 ^		associated with an ^
	Organizations to |A Route Group is		organization to |A Route Group is
	identify the |associated with		identify the |associated with
	registrant and |zero or more Peering		object's registrant |zero or more Peering
	the registrar |Organizations		|Organizations
	|		|
	+--------+--------------+		+--------+--------------+
	|Route Group: | +-----[abstract]-+		|Route Group: | +-----[abstract]-+
	| rant, | | Route Record: |		| rant, | | Route Record: |
	| rar, | | |
	| rgName, | | rrName, |		| rgName, | | rrName, |
	| destGrpRef, +------->| priority, |		| destGrpRef, +------->| priority, |
	| isInSvc, | | extension |		| isInSvc, | | extension |
	| rrRef, | | |		| rrRef, | | |
	| peeringOrg, | +----------------+		| peeringOrg, | +----------------+
	| sourceIdent, | ^		| sourceIdent, | ^
	| priority, | |		| priority, | |
	| extension | |Various types		| extension | |Various types
	+-----------------------+ |of Route		+-----------------------+ |of Route
	| |Records...		| |Records...
	| +------+------------...		| +------+------------...
	| | | |		| | | |
	| +----+ +-------+ +----+		| +----+ +-------+ +----+
	v | URI| | NAPTR | | NS |		v | URI| | NAPTR | | NS |
	+----------------+-----+ +----+ +-------+ +----+		+----------------+-----+ +----+ +-------+ +----+
	|Destination |		|Destination |
	|Group: | +----------[abstract]-+		|Group: | +----------[abstract]-+
	| rant, | |Public Identifier: |		| rant, | |Public Identifier: |
	| rar, | | |		| dgName, | | |
	| dgName, | | rant, |		| extension, | | rant, |
	| extension |<----+ rar, |
	+----------------------+ | publicIdentifier, |		+----------------------+ | publicIdentifier, |
	| destGrpRef, |		| destGrpRef, |
	| rrRef, |		| rrRef, |
	| extension |		| extension |
	+---------------------+		+---------------------+
	^		^
	|Various types		|Various types
	|of Public		|of Public
	|Identifiers...		|Identifiers...
	+---------+-------+------------...		+---------+-------+------------...
	skipping to change at page 13, line 17		skipping to change at page 13, line 16
	[I-D.ietf-drinks-usecases-requirements], SPPP protocol defines		[I-D.ietf-drinks-usecases-requirements], SPPP protocol defines
	three type of Route Records: URIType, NAPTRType, and NSType.		three type of Route Records: URIType, NAPTRType, and NSType.
	These Route Records extend the abstract type RteRecType and		These Route Records extend the abstract type RteRecType and
	inherit the common attribute 'priority' that is meant for setting		inherit the common attribute 'priority' that is meant for setting
	precedence across the route records defined within a Route Group		precedence across the route records defined within a Route Group
	in a protocol agnostic fashion.		in a protocol agnostic fashion.
	o Organization:		o Organization:
	An Organization is an entity that may fulfill any combination of		An Organization is an entity that may fulfill any combination of
	three roles: Registrant, Registrar, and Peering Organization. All		three roles: Registrant, Registrar, and Peering Organization. All
	SPPP objects are associated with two organization identifiers to		SPPP objects are associated with an organization identifier to
	identify each object's registrant and registrar. A Route Group		identify each object's registrant, while tracking the identity of
	object is also associated with a set of zero or more organization		the registrar that provisioned each SPPP object is left as a
	identifiers that identify the peering organizations whose query		matter of policy for an SPPP implementation. A Route Group object
	responses may include the routing information (SED) defined in the		is also associated with a set of zero or more organization
	Route Records within that Route Group.		identifiers that identify the peering organization(s) whose
			resolution query responses may include the routing information
			(SED) defined in the Route Records within that Route Group.
	4. Transport Protocol Requirements		4. Transport Protocol Requirements
	This section provides requirements for transport protocols suitable		This section provides requirements for transport protocols suitable
	for SPPP. More specifically, this section specifies the services,		for SPPP. More specifically, this section specifies the services,
	features, and assumptions that SPPP delegates to the chosen transport		features, and assumptions that SPPP delegates to the chosen transport
	and envelope technologies.		and envelope technologies.
	Two different groups of use cases are specified in		Two different groups of use cases are specified in
	[I-D.ietf-drinks-usecases-requirements]. One group of use cases		[I-D.ietf-drinks-usecases-requirements]. One group of use cases
	skipping to change at page 17, line 40		skipping to change at page 17, line 40
	An SPPP update request object is contained within the generic		An SPPP update request object is contained within the generic
	<spppUpdateRequest> element.		<spppUpdateRequest> element.
	<element name="spppUpdateRequest">		<element name="spppUpdateRequest">
	<complexType>		<complexType>
	<sequence>		<sequence>
	<element name="clientTransId" type="spppb:TransIdType"		<element name="clientTransId" type="spppb:TransIdType"
	minOccurs="0"/>		minOccurs="0"/>
	<element name="minorVer" type="spppb:MinorVerType"		<element name="minorVer" type="spppb:MinorVerType"
	minOccurs="0"/>		minOccurs="0"/>
	<element name="rqstObj" type="spppb:BasicUpdateRqstType"		<element name="rqst" type="spppb:BasicUpdateRqstType"
	maxOccurs="unbounded"/>		maxOccurs="unbounded"/>
	</sequence>		</sequence>
	</complexType>		</complexType>
	</element>		</element>
	<simpleType name="TransIdType">		<simpleType name="TransIdType">
	<restriction base="string"/>		<restriction base="string"/>
	</simpleType>		</simpleType>
	<simpleType name="MinorVerType">		<simpleType name="MinorVerType">
	<restriction base="unsignedLong"/>		<restriction base="unsignedLong"/>
	skipping to change at page 18, line 30		skipping to change at page 18, line 30
	minor version of the SPPP API that the client is attempting to		minor version of the SPPP 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 SPPP		identifier in the XML namespace to identify the version of SPPP
	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 SPPP server for the given major version. The		supported by the SPPP server for the given major version. The
	versions supported by a given SPPP server can be retrieved by		versions supported by a given SPPP server can be retrieved by
	the client using the SPPP server menu operation described later		the client using the SPPP server menu operation described later
	in the document.		in the document.
	o rqstObj: One or more BasicUpdateRqstType objects. These are the		o rqst: One or more BasicUpdateRqstType objects. These are the
	actions that the client is requesting the SPPP server perform.		actions that the client is requesting the SPPP server perform.
	They are processed by the SPPP server in the order in which they		They are processed by the SPPP server in the order in which they
	are included in the request. And with respect to handling error		are included in the request. And with respect to handling error
	conditions, it is a matter of policy whether the objects are		conditions, it is a matter of policy whether the objects are
	processed in a "stop and rollback" fashion or in a "stop and		processed in a "stop and rollback" fashion or in a "stop and
	commit" fashion. In the "stop and rollback" scenario, the SPPP		commit" fashion. In the "stop and rollback" scenario, the SPPP
	server would stop processing BasicUpdateRqstType object		server would stop processing BasicUpdateRqstType object
	instances in the request at the first error and roll back any		instances in the request at the first error and roll back any
	BasicUpdateRqstType object instances that had already been		BasicUpdateRqstType object instances that had already been
	processed for that update request. In the "stop and commit"		processed for that update request. In the "stop and commit"
	skipping to change at page 21, line 15		skipping to change at page 21, line 15
	5.1.2.1. Query Request		5.1.2.1. Query Request
	An SPPP query request object is contained within the generic		An SPPP query request object is contained within the generic
	<spppQueryRequest> element.		<spppQueryRequest> element.
	<element name="spppQueryRequest">		<element name="spppQueryRequest">
	<complexType>		<complexType>
	<sequence>		<sequence>
	<element name="minorVer" type="spppb:MinorVerType"		<element name="minorVer" type="spppb:MinorVerType"
	minOccurs="0"/>		minOccurs="0"/>
	<element name="rqstObj" type="spppb:BasicQueryRqstType"/>		<element name="rqst" type="spppb:BasicQueryRqstType"/>
	</sequence>		</sequence>
	</complexType>		</complexType>
	</element>		</element>
	The data elements within the <spppQueryRequest> element are described		The data elements within the <spppQueryRequest> element are described
	as follows:		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 SPPP API that the client is attempting to		minor version of the SPPP 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 SPPP		identifier in the XML namespace to identify the version of SPPP
	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 SPPP server for the given major version. The		supported by the SPPP server for the given major version. The
	versions supported by a given SPPP server can be retrieved by		versions supported by a given SPPP server can be retrieved by
	the client using the SPPP server menu operation described later		the client using the SPPP server menu operation described later
	in the document.		in the document.
	o rqstObj: One BasicQueryRqstType objects. This is the query that		o rqst: One BasicQueryRqstType objects. This is the query that
	the client is requesting the SPPP server perform.		the client is requesting the SPPP server perform.
	All query request objects extend the base type BasicQueryRqstType.		All query request objects extend the base type BasicQueryRqstType.
	This base type is defined as follows:		This base type is defined as follows:
	<complexType name="BasicQueryRqstType" abstract="true">		<complexType name="BasicQueryRqstType" abstract="true">
	<sequence>		<sequence>
	<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>		<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
	</sequence>		</sequence>
	</complexType>		</complexType>
	skipping to change at page 24, line 46		skipping to change at page 24, line 46
	uniquely identify an object are malformed, then response code		uniquely identify an object are malformed, then response code
	2104 SHOULD be returned.		2104 SHOULD be returned.
	5.3. Basic Object Type and Organization Identifiers		5.3. Basic Object Type and Organization Identifiers
	This section introduces the basic object type that most first class		This section introduces the basic object type that most first class
	objects derive from.		objects derive from.
	All first class objects extend the basic object type BasicObjType		All first class objects extend the basic object type BasicObjType
	which contains the identifier of the registrant organization that		which contains the identifier of the registrant organization that
	owns this object, the identifier of the registrar organization that		owns this object, the date and time that the object was created by
	provisioned this object, the date and time that the object was		the server, and the date and time that the object was last modified.
	created by the server, and the date and time that the object was last
	modified.
	<complexType name="BasicObjType" abstract="true">		<complexType name="BasicObjType" abstract="true">
	<sequence>		<sequence>
	<element name="rant" type="spppb:OrgIdType"/>		<element name="rant" type="spppb:OrgIdType"/>
	<element name="rar" type="spppb:OrgIdType"/>
	<element name="cDate" type="dateTime" minOccurs="0"/>		<element name="cDate" type="dateTime" minOccurs="0"/>
	<element name="mDate" type="dateTime" minOccurs="0"/>		<element name="mDate" type="dateTime" minOccurs="0"/>
	<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>		<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
	</sequence>		</sequence>
	</complexType>		</complexType>
	The identifiers used for registrants (rant), registrars (rar) and		The identifiers used for registrants (rant) and peering organizations
	peering organizations (peeringOrg) are instances of OrgIdType. The		(peeringOrg) are instances of OrgIdType. The OrgIdType is defined as
	OrgIdType is defined as a string and all OrgIdType instances SHOULD		a string and all OrgIdType instances SHOULD follow the textual
	follow the textual convention: "namespace:value" (for example "iana-		convention: "namespace:value" (for example "iana-en:32473"). See the
	en:32473"). See the IANA Consideration section for more details.		IANA Consideration section for more details.
	6. Protocol Commands		6. Protocol Commands
	This section provides a description of each supported protocol		This section provides a description of each supported protocol
	command.		command.
	6.1. Add Destination Group Operation		6.1. Add Destination Group Operation
	As described in the introductory sections, a Destination Group		As described in the introductory sections, a Destination Group
	represents a set of Public Identifiers with common routing		represents a set of Public Identifiers with common routing
	skipping to change at page 27, line 12		skipping to change at page 27, line 12
	</sequence>		</sequence>
	</extension>		</extension>
	</complexContent>		</complexContent>
	</complexType>		</complexType>
	The DestGrpType object is composed of the following elements:		The DestGrpType object is composed of the following elements:
	o base: All first class objects extend BasicObjType which contains		o base: All first class objects extend BasicObjType which contains
	the ID of the registrant organization that owns this object, the		the ID of the registrant organization that owns this object, the
	ID of the registrar organization that provisioned this object,		date and time that the object was created by the server, and the
	the date and time that the object was created by the server, and		date and time that the object was last modified. If the client
	the date and time that the object was last modified. If the		passed in either the created date or the modification date, the
	client passed in either the created date or the modification		server will ignore them. The server sets these two date/time
	date, the server will ignore them. The server sets these two		values.
	date/time values.
	o dgName: The character string that contains the name of the		o dgName: The character string that contains the name of the
	Destination Group. This uniquely identifies this object within		Destination Group. This uniquely identifies this object within
	the context of the registrant ID (a child element of the base		the context of the registrant ID (a child element of the base
	element as described above).		element as described above).
	o ext: Point of extensibility described in a previous section of		o ext: Point of extensibility described in a previous section of
	this document.		this document.
	As with the responses to all update operations, the result of the		As with the responses to all update operations, the result of the
	skipping to change at page 35, line 38		skipping to change at page 35, line 38
	<element name="rrKey" type="spppb:ObjKeyType"/>		<element name="rrKey" type="spppb:ObjKeyType"/>
	<element name="priority" type="unsignedShort"/>		<element name="priority" type="unsignedShort"/>
	<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>		<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
	</sequence>		</sequence>
	</complexType>		</complexType>
	The RteGrpType object is composed of the following elements:		The RteGrpType object is composed of the following elements:
	o base: All first class objects extend BasicObjType which contains		o base: All first class objects extend BasicObjType which contains
	the ID of the registrant organization that owns this object, the		the ID of the registrant organization that owns this object, the
	ID of the registrar organization that provisioned this object,		date and time that the object was created by the server, and the
	the date and time that the object was created by the server, and		date and time that the object was last modified. If the client
	the date and time that the object was last modified. If the		passes in either the created date or the modification date, the
	client passes in either the created date or the modification		server will ignore them. The server sets these two date/time
	date, the server will ignore them. The server sets these two		values.
	date/time values.
	o rgName: The character string that contains the name of the Route		o rgName: The character string that contains the name of the Route
	Group. It uniquely identifies this object within the context of		Group. It uniquely identifies this object within the context of
	the registrant ID (a child element of the base element as		the registrant ID (a child element of the base element as
	described above).		described above).
	o rrRef: Set of zero or more objects of type RteRecRefType that		o rrRef: Set of zero or more objects of type RteRecRefType that
	house the unique keys of the Route Records that the RteGrpType		house the unique keys of the Route Records that the RteGrpType
	object refers to and their relative priority within the context		object refers to and their relative priority within the context
	of a given route group. The associated Route Records contain		of a given route group. The associated Route Records contain
	skipping to change at page 40, line 20		skipping to change at page 40, line 20
	<element name="priority" type="unsignedShort" minOccurs="0"/>		<element name="priority" type="unsignedShort" minOccurs="0"/>
	</sequence>		</sequence>
	</extension>		</extension>
	</complexContent>		</complexContent>
	</complexType>		</complexType>
	The RteRecType object is composed of the following elements:		The RteRecType object is composed of the following elements:
	o base: All first class objects extend BasicObjType which contains		o base: All first class objects extend BasicObjType which contains
	the ID of the registrant organization that owns this object, the		the ID of the registrant organization that owns this object, the
	ID of the registrar organization that provisioned this object,		date and time that the object was created by the server, and the
	the date and time that the object was created by the server, and		date and time that the object was last modified. If the client
	the date and time that the object was last modified. If the		passes in either the created date or the modification date, the
	client passes in either the created date or the modification		server will ignore them. The server sets these two date/time
	date, the server will ignore them. The server sets these two		values.
	date/time values.
	o rrName: The character string that contains the name of the Route		o rrName: The character string that contains the name of the Route
	Record. It uniquely identifies this object within the context		Record. It uniquely identifies this object within the context
	of the registrant ID (a child element of the base element as		of the registrant ID (a child element of the base element as
	described above).		described above).
	o priority: Zero or one priority value that can be used to provide		o priority: Zero or one priority value that can be used to provide
	a relative value weighting of one Route Record over another.		a relative value weighting of one Route Record over another.
	The manner in which this value is used, perhaps in conjunction		The manner in which this value is used, perhaps in conjunction
	with other factors, is a matter of policy.		with other factors, is a matter of policy.
	skipping to change at page 42, line 5		skipping to change at page 41, line 13
	SIP and ENUM protocols. When a given URIType is associated to a		SIP and ENUM protocols. When a given URIType is associated to a
	destination group, the user part of the replacement string <uri> that		destination group, the user part of the replacement string <uri> that
	may require the Public Identifier cannot be preset. As a SIP		may require the Public Identifier cannot be preset. As a SIP
	Redirect, the resolution server will apply <ere> pattern on the input		Redirect, the resolution server will apply <ere> pattern on the input
	Public Identifier in the query and process the replacement string by		Public Identifier in the query and process the replacement string by
	substituting any back reference(s) in the <uri> to arrive at the		substituting any back reference(s) in the <uri> to arrive at the
	final URI that is returned in the SIP Contact header. For an ENUM		final URI that is returned in the SIP Contact header. For an ENUM
	query, the resolution server will simply return the value of the		query, the resolution server will simply return the value of the
	<ere> and <uri> members of the URIType in the NAPTR REGEX parameter.		<ere> and <uri> members of the URIType in the NAPTR REGEX parameter.
	<complexType name="NAPTRType">		<complexType name="NAPTRType">
	<complexContent>		<complexContent>
	<extension base="spppb:RteRecType">		<extension base="spppb:RteRecType">
	<sequence>		<sequence>
	<element name="order" type="unsignedShort"/>		<element name="order" type="unsignedShort"/>
	<element name="flags" type="string" minOccurs="0"/>		<element name="flags" type="string" minOccurs="0"/>
	<element name="svcs" type="string"/>		<element name="svcs" type="string"/>
	<element name="regx" type="spppb:RegexParamType"		<element name="regx" type="spppb:RegexParamType"
	minOccurs="0"/>		minOccurs="0"/>
	<element name="repl" type="string" minOccurs="0"/>		<element name="repl" type="string" minOccurs="0"/>
	<element name="ttl" type="positiveInteger" minOccurs="0"/>		<element name="ttl" type="positiveInteger" minOccurs="0"/>
	<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>		<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
	</sequence>		</sequence>
	</extension>		</extension>
	</complexContent>		</complexContent>
	</complexType>		</complexType>
	<complexType name="NSType">		<complexType name="NSType">
	<complexContent>		<complexContent>
	<extension base="spppb:RteRecType">		<extension base="spppb:RteRecType">
	<sequence>		<sequence>
	<element name="hostName" type="string"/>		<element name="hostName" type="string"/>
	<element name="ttl" type="positiveInteger" minOccurs="0"/>		<element name="ipAddr" type="spppb:IPAddrType" minOccurs="0"
	<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>		maxOccurs="unbounded"/>
	</sequence>		<element name="ttl" type="positiveInteger" minOccurs="0"/>
	</extension>		<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
	</complexContent>		</sequence>
	</complexType>		</extension>
			</complexContent>
			</complexType>
	<complexType name="URIType">		<complexType name="IPAddrType">
	<complexContent>		<sequence>
	<extension base="spppb:RteRecType">		<element name="addr" type="string"/>
	<sequence>		<element name="type" type="spppb:IPType"/>
	<element name="ere" type="string" default="^(.*)$"/>		<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
	<element name="uri" type="string"/>		</sequence>
	<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
	</sequence>		</complexType>
	</extension>
	</complexContent>		<simpleType name="IPType">
	</complexType>		<restriction base="token">
			<enumeration value="IPv4"/>
			<enumeration value="IPv6"/>
			</restriction>
			</simpleType>
			<complexType name="URIType">
			<complexContent>
			<extension base="spppb:RteRecType">
			<sequence>
			<element name="ere" type="string" default="^(.*)$"/>
			<element name="uri" type="string"/>
			<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
			</sequence>
			</extension>
			</complexContent>
			</complexType>
	The NAPTRType object is composed of the following elements:		The NAPTRType object is composed of the following elements:
	o order: Order value in an ENUM NAPTR, relative to other NAPTRType		o order: Order value in an ENUM NAPTR, relative to other NAPTRType
	objects in the same Route Group.		objects in the same Route Group.
	o svcs: ENUM service(s) that are served by the SBE. This field's		o svcs: ENUM service(s) that are served by the SBE. This field's
	value must be of the form specified in [RFC3761] (e.g., E2U+		value must be of the form specified in [RFC3761] (e.g., E2U+
	pstn:sip+sip). The allowable values are a matter of policy and		pstn:sip+sip). The allowable values are a matter of policy and
	not limited by this protocol.		not limited by this protocol.
	skipping to change at page 43, line 27		skipping to change at page 43, line 7
	o ttl: Number of seconds that an addressing server may cache this		o ttl: Number of seconds that an addressing server may cache this
	NAPTR.		NAPTR.
	o ext: Point of extensibility described in a previous section of		o ext: Point of extensibility described in a previous section of
	this document.		this document.
	The NSType object is composed of the following elements:		The NSType object is composed of the following elements:
	o hostName: Fully qualified host name of the name server.		o hostName: Fully qualified host name of the name server.
			o ipAddr: Zero or more objects of type IpAddrType. Each object
			holds an IP Address and the IP Address type, IPv4 or IP v6.
	o ttl: Number of seconds that an addressing server may cache this		o ttl: Number of seconds that an addressing server may cache this
	Name Server.		Name Server.
	o ext: Point of extensibility described in a previous section of		o ext: Point of extensibility described in a previous section of
	this document.		this document.
	The URIType object is composed of the following elements:		The URIType object is composed of the following elements:
	o ere: The POSIX Extended Regular Expression (ere) as defined in		o ere: The POSIX Extended Regular Expression (ere) as defined in
	[RFC3986].		[RFC3986].
	skipping to change at page 46, line 33		skipping to change at page 46, line 4
	<element name="offeredTo" type="spppb:OrgIdType"/>		<element name="offeredTo" type="spppb:OrgIdType"/>
	</sequence>		</sequence>
	</complexType>		</complexType>
	<simpleType name="RteGrpOfferStatusType">		<simpleType name="RteGrpOfferStatusType">
	<restriction base="token">		<restriction base="token">
	<enumeration value="offered"/>		<enumeration value="offered"/>
	<enumeration value="accepted"/>		<enumeration value="accepted"/>
	</restriction>		</restriction>
	</simpleType>		</simpleType>
	The RteGrpOfferType object is composed of the following elements:		The RteGrpOfferType object is composed of the following elements:
	o base: All first class objects extend BasicObjType which contains		o base: All first class objects extend BasicObjType which contains
	the ID of the registrant organization that owns this object, the		the ID of the registrant organization that owns this object, the
	ID of the registrar organization that provisioned this object,		date and time that the object was created by the server, and the
	the date and time that the object was created by the server, and		date and time that the object was last modified. If the client
	the date and time that the object was last modified. If the		passed in either the created date or the modification date, the
	client passed in either the created date or the modification		will ignore them. The server sets these two date/time values.
	date, the will ignore them. The server sets these two date/time
	values.
	o rteGrpOfferKey: The object that identifies the route that is or		o rteGrpOfferKey: The object that identifies the route that is or
	has been offered and the organization that it is or has been		has been offered and the organization that it is or has been
	offered to. The combination of these three data elements		offered to. The combination of these three data elements
	uniquely identify a Route Group Offer.		uniquely identify a Route Group Offer.
	o status: The status of the offer, offered or accepted. This		o status: The status of the offer, offered or accepted. This
	status is controlled by the server. It is automatically set to		status is controlled by the server. It is automatically set to
	"offered" when ever a new Route Group Offer is added, and is		"offered" when ever a new Route Group Offer is added, and is
	automatically set to "accepted" if and when that offer is		automatically set to "accepted" if and when that offer is
	skipping to change at page 51, line 24		skipping to change at page 50, line 46
	<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>		<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
	</sequence>		</sequence>
	</extension>		</extension>
	</complexContent>		</complexContent>
	</complexType>		</complexType>
	The EgrRteType object is composed of the following elements:		The EgrRteType object is composed of the following elements:
	o base: All first class objects extend BasicObjType which contains		o base: All first class objects extend BasicObjType which contains
	the ID of the registrant organization that owns this object, the		the ID of the registrant organization that owns this object, the
	ID of the registrar organization that provisioned this object,		date and time that the object was created by the server, and the
	the date and time that the object was created by the server, and		date and time that the object was last modified. If the client
	the date and time that the object was last modified. If the		passes in either the created date or the modification date, the
	client passes in either the created date or the modification		server will ignore them. The server sets these two date/time
	date, the server will ignore them. The server sets these two		values.
	date/time values.
	o egrRteName: The name of the egress route.		o egrRteName: The name of the egress route.
	o pref: The preference of this egress route relative to other		o pref: The preference of this egress route relative to other
	egress routes that may get selected when responding to a		egress routes that may get selected when responding to a
	resolution request.		resolution request.
	o regxRewriteRule: The regular expression re-write rule that		o regxRewriteRule: The regular expression re-write rule that
	should be applied to the regular expression of the ingress		should be applied to the regular expression of the ingress
	NAPTR(s) that belong to the ingress route.		NAPTR(s) that belong to the ingress route.
	skipping to change at page 56, line 10		skipping to change at page 55, line 10
	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 SPPP client sets a unique transaction identifier 'tx_7777' for		SSP2 SPPP client sets a unique transaction identifier 'tx_7777' 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"?>
	<spppUpdateRequest		<spppUpdateRequest
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
	xmlns="urn:ietf:params:xml:ns:sppp:base:1">		xmlns="urn:ietf:params:xml:ns:sppp:base:1">
	<clientTransId>txid-5555</clientTransId>		<clientTransId>txid-5555</clientTransId>
	<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:AddDestGrpRqstType">		xsi:type="ns1:AddDestGrpRqstType">
	<destGrp>		<destGrp>
	<ns1:rant>iana-en:222</ns1:rant>		<ns1:rant>iana-en:222</ns1:rant>
	<ns1:rar>iana-en:222</ns1:rar>
	<dgName>DEST_GRP_SSP2_1</dgName>		<dgName>DEST_GRP_SSP2_1</dgName>
	</destGrp>		</destGrp>
	</rqstObj>		</rqst>
	</spppUpdateRequest>		</spppUpdateRequest>
	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 transaction identifier, Registry also		besides returning a unique transaction identifier, Registry also
	returns the matching client transaction identifier from the request		returns the matching client transaction identifier from the request
	message back to the SPPP client.		message back to the SPPP client.
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<spppUpdateResponse		<spppUpdateResponse
	skipping to change at page 57, line 10		skipping to change at page 56, line 10
	7.2. Add Route Records		7.2. Add Route Records
	SSP2 adds an ingress routes in the Registry.		SSP2 adds an ingress routes in the Registry.
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<spppUpdateRequest		<spppUpdateRequest
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
	xmlns="urn:ietf:params:xml:ns:sppp:base:1">		xmlns="urn:ietf:params:xml:ns:sppp:base:1">
	<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:AddRteRecRqstType">		xsi:type="ns1:AddRteRecRqstType">
	<rteRec xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rteRec xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:NAPTRType">		xsi:type="ns1:NAPTRType">
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<rar>iana-en:222</rar>
	<ns1:rrName>RTE_SSP2_SBE2</ns1:rrName>		<ns1:rrName>RTE_SSP2_SBE2</ns1:rrName>
	<order>10</order>		<order>10</order>
	<flags>u</flags>		<flags>u</flags>
	<svcs>E2U+sip</svcs>		<svcs>E2U+sip</svcs>
	<regx>		<regx>
	<ere>^(.*)$</ere>		<ere>^(.*)$</ere>
	<repl>sip:\1@sbe2.ssp2.example.com</repl>		<repl>sip:\1@sbe2.ssp2.example.com</repl>
	</regx>		</regx>
	</rteRec>		</rteRec>
	</rqstObj>		</rqst>
	</spppUpdateRequest>		</spppUpdateRequest>
	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"?>
	<spppUpdateResponse		<spppUpdateResponse
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
	xmlns="urn:ietf:params:xml:ns:sppp:base:1">		xmlns="urn:ietf:params:xml:ns:sppp:base:1">
	<serverTransId>tx_id_11145</serverTransId>		<serverTransId>tx_id_11145</serverTransId>
	skipping to change at page 58, line 9		skipping to change at page 57, line 9
	7.3. Add Route Records -- URIType		7.3. Add Route Records -- URIType
	SSP2 adds another ingress routes in the Registry and makes use of		SSP2 adds another ingress routes in the Registry and makes use of
	URIType		URIType
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<spppUpdateRequest>		<spppUpdateRequest>
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
	xmlns="urn:ietf:params:xml:ns:sppp:base:1">		xmlns="urn:ietf:params:xml:ns:sppp:base:1">
	<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:AddRteRecRqstType">		xsi:type="ns1:AddRteRecRqstType">
	<rteRec xsi:type="ns1:URIType">		<rteRec xsi:type="ns1:URIType">
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<rar>iana-en:222</rar>
	<rrName>RTE_SSP2_SBE4</rrName>		<rrName>RTE_SSP2_SBE4</rrName>
	<ere>^(.*)$</ere>		<ere>^(.*)$</ere>
	<uri>sip:\1;npdi@sbe4.ssp2.example.com</uri>		<uri>sip:\1;npdi@sbe4.ssp2.example.com</uri>
	</rteRec>		</rteRec>
	</rqstObj>		</rqst>
	</spppUpdateRequest>		</spppUpdateRequest>
	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"?>
	<spppUpdateResponse		<spppUpdateResponse
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
	xmlns="urn:ietf:params:xml:ns:sppp:base:1">		xmlns="urn:ietf:params:xml:ns:sppp:base:1">
	<serverTransId>tx_id_11145</serverTransId>		<serverTransId>tx_id_11145</serverTransId>
	skipping to change at page 59, line 10		skipping to change at page 58, line 10
	SSP2 creates the grouping of the ingress routes and choses higher		SSP2 creates the grouping of the ingress routes and choses higher
	precedence for RTE_SSP2_SBE2 by setting a lower number for the		precedence for RTE_SSP2_SBE2 by setting a lower number for the
	"priority" attribute, a protocol agnostic precedence indicator.		"priority" attribute, a protocol agnostic precedence indicator.
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<spppUpdateRequest		<spppUpdateRequest
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
	xmlns="urn:ietf:params:xml:ns:sppp:base:1">		xmlns="urn:ietf:params:xml:ns:sppp:base:1">
	<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:AddRteGrpRqstType">		xsi:type="ns1:AddRteGrpRqstType">
	<rteGrp>		<rteGrp>
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<rar>iana-en:222</rar>
	<rgName>RTE_GRP_SSP2_1</rgName>		<rgName>RTE_GRP_SSP2_1</rgName>
	<rrRef>		<rrRef>
	<rrKey>		<rrKey>
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<name>RTE_SSP2_SBE2</name>		<name>RTE_SSP2_SBE2</name>
	</rrKey>		</rrKey>
	<priority>100</priority>		<priority>100</priority>
	</rrRef>		</rrRef>
	<dgName>DEST_GRP_SSP2_1</dgName>		<dgName>DEST_GRP_SSP2_1</dgName>
	<isInSvc>true</isInSvc>		<isInSvc>true</isInSvc>
	<ns1:priority>10</ns1:priority>		<ns1:priority>10</ns1:priority>
	</rteGrp>		</rteGrp>
	</rqstObj>		</rqst>
	</spppUpdateRequest>		</spppUpdateRequest>
	To confirm successful processing of this request, Registry returns a		To confirm successful processing of this request, Registry returns a
	well-known resolution code '1000' to the SSP2 client.		well-known resolution code '1000' to the SSP2 client.
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<spppUpdateResponse		<spppUpdateResponse
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
	xmlns="urn:ietf:params:xml:ns:sppp:base:1">		xmlns="urn:ietf:params:xml:ns:sppp:base:1">
	skipping to change at page 60, line 16		skipping to change at page 59, line 10
	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.
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<clientTransId>txid-5577</clientTransId>		<clientTransId>txid-5577</clientTransId>
	<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:AddPubIdRqstType">		xsi:type="ns1:AddPubIdRqstType">
	<pi xsi:type="ns1:TNType">		<pi xsi:type="ns1:TNType">
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<rar>iana-en:222</rar>
	<cDate>2010-05-30T09:30:10Z</cDate>		<cDate>2010-05-30T09:30:10Z</cDate>
	<dgName>DEST_GRP_SSP2_1</dgName>		<dgName>DEST_GRP_SSP2_1</dgName>
	<tn>+12025556666</tn>		<tn>+12025556666</tn>
	<corInfo>		<corInfo>
	<corClaim>true</corClaim>		<corClaim>true</corClaim>
	</corInfo>		</corInfo>
	</pi>		</pi>
	</rqstObj>		</rqst>
	</spppUpdateRequest>		</spppUpdateRequest>
	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.
	skipping to change at page 61, line 23		skipping to change at page 60, line 23
	<code>1000</code>		<code>1000</code>
	<msg>success</msg>		<msg>success</msg>
	</overallResult>		</overallResult>
	<rqstObjResult>		<rqstObjResult>
	<code>1000</code>		<code>1000</code>
	<msg>success</msg>		<msg>success</msg>
	<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:AddPubIdRqstType">		xsi:type="ns1:AddPubIdRqstType">
	<pi xsi:type="ns1:TNType">		<pi xsi:type="ns1:TNType">
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<rar>iana-en:222</rar>
	<cDate>2010-05-30T09:30:10Z</cDate>		<cDate>2010-05-30T09:30:10Z</cDate>
	<dgName>DEST_GRP_SSP2_1</dgName>		<dgName>DEST_GRP_SSP2_1</dgName>
	<tn>+12025556666</tn>		<tn>+12025556666</tn>
	<corInfo>		<corInfo>
	<corClaim>true</corClaim>		<corClaim>true</corClaim>
	<cor>true</cor>		<cor>true</cor>
	<corDate>2010-05-30T09:30:11Z</corDate>		<corDate>2010-05-30T09:30:11Z</corDate>
	</corInfo>		</corInfo>
	</pi>		</pi>
	</rqstObj>		</rqstObj>
	skipping to change at page 62, line 9		skipping to change at page 61, line 9
	If another entity that SSP2 shares the routes with has access to		If another entity that SSP2 shares the routes with has access to
	Number Portability data, it may choose to perform route lookups by		Number Portability data, it may choose to perform route lookups by
	routing number. Therefore, SSP2 associates a routing number to a		routing number. Therefore, SSP2 associates a routing number to a
	destination group in order to facilitate ingress route discovery.		destination group in order to facilitate ingress route discovery.
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:AddPubIdRqstType">		xsi:type="ns1:AddPubIdRqstType">
	<pi xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<pi xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:RNType">		xsi:type="ns1:RNType">
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<rar>iana-en:222</rar>
	<ns1:dgName>DEST_GRP_SSP2_1</ns1:dgName>		<ns1:dgName>DEST_GRP_SSP2_1</ns1:dgName>
	<rn>2025550000</rn>		<rn>2025550000</rn>
	</pi>		</pi>
	</rqstObj>		</rqst>
	</spppUpdateRequest>		</spppUpdateRequest>
	Registry completes the request successfully and returns a favorable		Registry completes the request successfully and returns a favorable
	response to the SPPP client.		response to the SPPP client.
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<spppUpdateResponse		<spppUpdateResponse
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
	xmlns="urn:ietf:params:xml:ns:sppp:base:1">		xmlns="urn:ietf:params:xml:ns:sppp:base:1">
	skipping to change at page 63, line 9		skipping to change at page 62, line 9
	7.7. Add TN Range		7.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"?>
	<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:AddPubIdRqstType">		xsi:type="ns1:AddPubIdRqstType">
	<pi xsi:type="ns1:TNRType">		<pi xsi:type="ns1:TNRType">
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<rar>iana-en:222</rar>
	<dgName>DEST_GRP_SSP2_1</dgName>		<dgName>DEST_GRP_SSP2_1</dgName>
	<startTn>+12026660000</startTn>		<startTn>+12026660000</startTn>
	<endTn>+12026669999</endTn>		<endTn>+12026669999</endTn>
	</pi>		</pi>
	</rqstObj>		</rqst>
	</spppUpdateRequest>		</spppUpdateRequest>
	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"?>
	<spppUpdateResponse		<spppUpdateResponse
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
	xmlns="urn:ietf:params:xml:ns:sppp:base:1">		xmlns="urn:ietf:params:xml:ns:sppp:base:1">
	skipping to change at page 64, line 9		skipping to change at page 63, line 9
	7.8. Add TN Prefix		7.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"?>
	<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:AddPubIdRqstType">		xsi:type="ns1:AddPubIdRqstType">
	<pi xsi:type="ns1:TNPType">		<pi xsi:type="ns1:TNPType">
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<rar>iana-en:222</rar>
	<ns1:dgName>DEST_GRP_SSP2_1</ns1:dgName>		<ns1:dgName>DEST_GRP_SSP2_1</ns1:dgName>
	<tnPrefix>+1202777</tnPrefix>		<tnPrefix>+1202777</tnPrefix>
	</pi>		</pi>
	</rqstObj>		</rqst>
	</spppUpdateRequest>		</spppUpdateRequest>
	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"?>
	<spppUpdateResponse		<spppUpdateResponse
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
	xmlns="urn:ietf:params:xml:ns:sppp:base:1">		xmlns="urn:ietf:params:xml:ns:sppp:base:1">
	skipping to change at page 65, line 9		skipping to change at page 64, line 9
	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 route group.
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:AddRteGrpOfferRqstType">		xsi:type="ns1:AddRteGrpOfferRqstType">
	<rteGrpOffer>		<rteGrpOffer>
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<rar>iana-en:222</rar>
	<rteGrpOfferKey>		<rteGrpOfferKey>
	<rteGrpKey>		<rteGrpKey>
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<name>RTE_GRP_SSP2_1</name>		<name>RTE_GRP_SSP2_1</name>
	</rteGrpKey>		</rteGrpKey>
	<offeredTo>iana-en:111</offeredTo>		<offeredTo>iana-en:111</offeredTo>
	</rteGrpOfferKey>		</rteGrpOfferKey>
	<status>offered</status>		<status>offered</status>
	<offerDateTime>2006-05-04T18:13:51.0Z</offerDateTime>		<offerDateTime>2006-05-04T18:13:51.0Z</offerDateTime>
	</rteGrpOffer>		</rteGrpOffer>
	</rqstObj>		</rqst>
	</spppUpdateRequest>		</spppUpdateRequest>
	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"?>
	<spppUpdateResponse		<spppUpdateResponse
	skipping to change at page 66, line 14		skipping to change at page 65, line 9
	7.10. Enable Peering -- Route Group Offer Accept		7.10. Enable Peering -- Route 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 ingress routes.
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:AcceptRteGrpOfferRqstType">		xsi:type="ns1:AcceptRteGrpOfferRqstType">
	<rteGrpOfferKey>		<rteGrpOfferKey>
	<rteGrpKey>		<rteGrpKey>
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<name>RTE_GRP_SSP2_1</name>		<name>RTE_GRP_SSP2_1</name>
	</rteGrpKey>		</rteGrpKey>
	<offeredTo>iana-en:111</offeredTo>		<offeredTo>iana-en:111</offeredTo>
	</rteGrpOfferKey>		</rteGrpOfferKey>
	</rqstObj>		</rqst>
	</spppUpdateRequest>		</spppUpdateRequest>
	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 "RTE_GRP_SSP2_1" route association, SSP2
	ingress SBE information will be shared with SSP1.		ingress SBE information will be shared with SSP1.
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<spppUpdateResponse		<spppUpdateResponse
	skipping to change at page 67, line 15		skipping to change at page 66, line 10
	7.11. Add Egress Route		7.11. Add Egress Route
	SSP1 wants to prioritize all outbound traffic to routes associated		SSP1 wants to prioritize all outbound traffic to routes associated
	with "RTE_GRP_SSP2_1" route group through "sbe1.ssp1.example.com".		with "RTE_GRP_SSP2_1" route group through "sbe1.ssp1.example.com".
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<clientTransId>tx_9000</clientTransId>		<clientTransId>tx_9000</clientTransId>
	<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:AddEgrRteRqstType">		xsi:type="ns1:AddEgrRteRqstType">
	<egrRte>		<egrRte>
	<rant>iana-en:111</rant>		<rant>iana-en:111</rant>
	<rar/>
	<egrRteName>EGR_RTE_01</egrRteName>		<egrRteName>EGR_RTE_01</egrRteName>
	<pref>50</pref>		<pref>50</pref>
	<regxRewriteRule>		<regxRewriteRule>
	<ere>^(.*@)(.*)$</ere>		<ere>^(.*@)(.*)$</ere>
	<repl>\1\2?route=sbe1.ssp1.example.com</repl>		<repl>\1\2?route=sbe1.ssp1.example.com</repl>
	</regxRewriteRule>		</regxRewriteRule>
	<ingrRteRec>		<ingrRteRec>
	<rant>iana-en:222</ns1:rant>		<rant>iana-en:222</rant>
	<name>SSP2_RTE_REC_3</ns1:name>		<name>SSP2_RTE_REC_3</name>
	</ingrRteRec>		</ingrRteRec>
	</egrRte>		</egrRte>
	</rqstObj>		</rqst>
	</spppUpdateRequest>		</spppUpdateRequest>
	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"?>
	<spppUpdateResponse		<spppUpdateResponse
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
	xmlns="urn:ietf:params:xml:ns:sppp:base:1">		xmlns="urn:ietf:params:xml:ns:sppp:base:1">
	skipping to change at page 68, line 16		skipping to change at page 67, line 9
	7.12. Get Destination Group		7.12. Get Destination Group
	SSP2 uses the 'GetDestGrpsRqstType' operation to tally the last		SSP2 uses the 'GetDestGrpsRqstType' 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"?>
	<spppQueryRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppQueryRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:GetDestGrpsRqstType">		xsi:type="ns1:GetDestGrpsRqstType">
	<objKey>		<objKey>
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<name>DEST_GRP_SSP2_1</name>		<name>DEST_GRP_SSP2_1</name>
	</objKey>		</objKey>
	</rqstObj>		</rqst>
	</spppQueryRequest>		</spppQueryRequest>
	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"?>
	<spppQueryResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppQueryResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<overallResult>		<overallResult>
	<code>1000</code>		<code>1000</code>
	<msg>success</msg>		<msg>success</msg>
	</overallResult>		</overallResult>
	<resultSet xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<resultSet xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:DestGrpType">		xsi:type="ns1:DestGrpType">
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<rar>iana-en:222</rar>
	<dgName>DEST_GRP_SSP2_1</dgName>		<dgName>DEST_GRP_SSP2_1</dgName>
	</resultSet>		</resultSet>
	</spppQueryResponse>		</spppQueryResponse>
	7.13. Get Public Identity		7.13. 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"?>
	<spppQueryRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppQueryRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:GetPubIdsRqstType">		xsi:type="ns1:GetPubIdsRqstType">
	<pi xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<pi xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:TNType">		xsi:type="ns1:TNType">
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<rar>iana-en:222</rar>
	<tn>+12025556666</tn>		<tn>+12025556666</tn>
	</pi>		</pi>
	</rqstObj>		</rqst>
	</spppQueryRequest>		</spppQueryRequest>
	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"?>
	<spppQueryResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppQueryResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<overallResult>		<overallResult>
	<code>1000</code>		<code>1000</code>
	<msg>success</msg>		<msg>success</msg>
	</overallResult>		</overallResult>
	<resultSet xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<resultSet xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:TNType">		xsi:type="ns1:TNType">
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<rar>iana-en:222</rar>
	<dgName>DEST_GRP_1</dgName>		<dgName>DEST_GRP_1</dgName>
	<tn>+12025556666</tn>		<tn>+12025556666</tn>
	<corInfo>		<corInfo>
	<corClaim>true</corClaim>		<corClaim>true</corClaim>
	<cor>true</cor>		<cor>true</cor>
	<corDate>2010-05-30T09:30:10Z</corDate>		<corDate>2010-05-30T09:30:10Z</corDate>
	</corInfo>		</corInfo>
	</resultSet>		</resultSet>
	</spppQueryResponse>		</spppQueryResponse>
	7.14. Get Route Group Request		7.14. Get Route Group Request
	SSP2 obtains the last provisioned record for the route group		SSP2 obtains the last provisioned record for the route group
	RTE_GRP_SSP2_1.		RTE_GRP_SSP2_1.
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<spppQueryRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppQueryRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:GetRteGrpsRqstType">		xsi:type="ns1:GetRteGrpsRqstType">
	<objKey>		<objKey>
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<name>RTE_GRP_SSP2_1</name>		<name>RTE_GRP_SSP2_1</name>
	</objKey>		</objKey>
	</rqstObj>		</rqst>
	</spppQueryRequest>		</spppQueryRequest>
	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"?>
	<spppQueryResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppQueryResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<overallResult>		<overallResult>
	<code>1000</code>		<code>1000</code>
	<msg>success</msg>		<msg>success</msg>
	</overallResult>		</overallResult>
	<resultSet xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<resultSet xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:RteGrpType">		xsi:type="ns1:RteGrpType">
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<rar>iana-en:222</rar>
	<rgName>RTE_GRP_SSP2_1</rgName>		<rgName>RTE_GRP_SSP2_1</rgName>
	<rrRef>		<rrRef>
	<rrKey>		<rrKey>
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<name>RTE_SSP2_SBE2</name>		<name>RTE_SSP2_SBE2</name>
	</rrKey>		</rrKey>
	<priority>100</priority>		<priority>100</priority>
	</rrRef>		</rrRef>
	<rrRef>		<rrRef>
	<rrKey>		<rrKey>
	skipping to change at page 71, line 47		skipping to change at page 70, line 17
	7.15. Get Route Group Offers Request		7.15. Get Route Group Offers Request
	SSP2 fetches the last provisioned route group offer to the		SSP2 fetches the last provisioned route group offer to the
	<peeringOrg> SSP1.		<peeringOrg> SSP1.
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<spppQueryRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppQueryRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:GetRteGrpOffersRqstType">		xsi:type="ns1:GetRteGrpOffersRqstType">
	<offeredTo>iana-en:111</offeredTo>		<offeredTo>iana-en:111</offeredTo>
			</rqst>
	</rqstObj>
	</spppQueryRequest>		</spppQueryRequest>
	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"?>
	<spppQueryResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppQueryResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<overallResult>		<overallResult>
	<code>1000</code>		<code>1000</code>
	<msg>success</msg>		<msg>success</msg>
	</overallResult>		</overallResult>
	<resultSet xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<resultSet xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:RteGrpOfferType">		xsi:type="ns1:RteGrpOfferType">
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<rar>iana-en:222</rar>
	<rteGrpOfferKey>		<rteGrpOfferKey>
	<rteGrpKey>		<rteGrpKey>
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<name>RTE_GRP_SSP2_1</name>		<name>RTE_GRP_SSP2_1</name>
	</rteGrpKey>		</rteGrpKey>
	<offeredTo>iana-en:111</offeredTo>		<offeredTo>iana-en:111</offeredTo>
	</rteGrpOfferKey>		</rteGrpOfferKey>
	<status>offered</status>		<status>offered</status>
	<offerDateTime>2006-05-04T18:13:51.0Z</offerDateTime>		<offerDateTime>2006-05-04T18:13:51.0Z</offerDateTime>
	</resultSet>		</resultSet>
	skipping to change at page 73, line 9		skipping to change at page 71, line 16
	7.16. Get Egress Route		7.16. 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"?>
	<spppQueryRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppQueryRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:GetEgrRtesRqstType">		xsi:type="ns1:GetEgrRtesRqstType">
	<objKey>		<objKey>
	<rant>iana-en:111</rant>		<rant>iana-en:111</rant>
	<name>EGR_RTE_01</name>		<name>EGR_RTE_01</name>
	</objKey>		</objKey>
	</rqstObj>		</rqst>
	</spppQueryRequest>		</spppQueryRequest>
	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"?>
	<spppQueryResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppQueryResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<overallResult>		<overallResult>
	<code>1000</code>		<code>1000</code>
	<msg>success</msg>		<msg>success</msg>
	</overallResult>		</overallResult>
	<resultSet xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<resultSet xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:EgrRteType">		xsi:type="ns1:EgrRteType">
	<rant>iana-en:111</rant>		<rant>iana-en:111</rant>
	<rar>iana-en:111</rar>
	<egrRteName>EGR_RTE_01</egrRteName>		<egrRteName>EGR_RTE_01</egrRteName>
	<pref>50</pref>		<pref>50</pref>
	<svcs>E2U+sip</svcs>		<svcs>E2U+sip</svcs>
	<regxRewriteRule>		<regxRewriteRule>
	<ere>^(.*)$</ere>		<ere>^(.*)$</ere>
	<repl>sip:\1@sbe1.ssp1.example.com</repl>		<repl>sip:\1@sbe1.ssp1.example.com</repl>
	</regxRewriteRule>		</regxRewriteRule>
	<ingressRte>		<ingressRte>
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<name>RTE_GRP_SSP2_1</name>		<name>RTE_GRP_SSP2_1</name>
	skipping to change at page 74, line 14		skipping to change at page 72, line 39
	7.17. Delete Destination Group		7.17. 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"?>
	<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:DelDestGrpRqstType">		xsi:type="ns1:DelDestGrpRqstType">
	<objKey>		<objKey>
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<name>DEST_GRP_SSP2_1</name>		<name>DEST_GRP_SSP2_1</name>
	</objKey>		</objKey>
	</rqstObj>		</rqst>
	</spppUpdateRequest>		</spppUpdateRequest>
	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"?>
	<spppUpdateResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppUpdateResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<serverTransId>txid-982543123</serverTransId>		<serverTransId>txid-982543123</serverTransId>
	skipping to change at page 75, line 9		skipping to change at page 73, line 25
	</spppUpdateResponse>		</spppUpdateResponse>
	7.18. Delete Public Identity		7.18. Delete Public Identity
	SSP2 choses to de-activate the TN and remove it from the Registry.		SSP2 choses 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"?>
	<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:DelPubIdRqstType">		xsi:type="ns1:DelPubIdRqstType">
	<pi xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<pi xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:TNType">		xsi:type="ns1:TNType">
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<rar>iana-en:222</rar>
	<tn>+12025556666</tn>		<tn>+12025556666</tn>
	</pi>		</pi>
	</rqstObj>		</rqst>
	</spppUpdateRequest>		</spppUpdateRequest>
	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"?>
	<spppUpdateResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppUpdateResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<serverTransId>txid-98298273123</serverTransId>		<serverTransId>txid-98298273123</serverTransId>
	skipping to change at page 76, line 9		skipping to change at page 74, line 24
	</spppUpdateResponse>		</spppUpdateResponse>
	7.19. Delete Route Group Request		7.19. Delete Route Group Request
	SSP2 removes the route group called RTE_GRP_SSP2_1.		SSP2 removes the route group called RTE_GRP_SSP2_1.
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:DelRteGrpRqstType">		xsi:type="ns1:DelRteGrpRqstType">
	<objKey>		<objKey>
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<name>RTE_GRP_SSP2_1</name>		<name>RTE_GRP_SSP2_1</name>
	</objKey>		</objKey>
	</rqstObj>		</rqst>
	</spppUpdateRequest>		</spppUpdateRequest>
	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"?>
	<spppUpdateResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppUpdateResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<serverTransId>txid-982543123</serverTransId>		<serverTransId>txid-982543123</serverTransId>
	skipping to change at page 77, line 9		skipping to change at page 75, line 13
	</spppUpdateResponse>		</spppUpdateResponse>
	7.20. Delete Route Group Offers Request		7.20. Delete Route Group Offers Request
	SSP2 no longer wants to share route group RTE_GRP_SSP2_1 with SSP1.		SSP2 no longer wants to share route group RTE_GRP_SSP2_1 with SSP1.
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:DelRteGrpOfferRqstType">		xsi:type="ns1:DelRteGrpOfferRqstType">
	<rteGrpOfferKey>		<rteGrpOfferKey>
	<rteGrpKey>		<rteGrpKey>
	<rant>iana-en:222</rant>		<rant>iana-en:222</rant>
	<name>RTE_GRP_SSP2_1</name>		<name>RTE_GRP_SSP2_1</name>
	</rteGrpKey>		</rteGrpKey>
	<offeredTo>iana-en:111</offeredTo>		<offeredTo>iana-en:111</offeredTo>
	</rteGrpOfferKey>		</rteGrpOfferKey>
	</rqstObj>		</rqst>
	</spppUpdateRequest>		</spppUpdateRequest>
	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 route
	group offer from SSP2 to SSP1 followed by a successful route group		group offer from SSP2 to SSP1 followed by a successful route group
	accept request from SSP1.		accept request from SSP1.
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<spppUpdateResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppUpdateResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	skipping to change at page 78, line 9		skipping to change at page 76, line 9
	</spppUpdateResponse>		</spppUpdateResponse>
	7.21. Delete Egress Route		7.21. 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"?>
	<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"		<rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
	xsi:type="ns1:DelEgrRteRqstType">		xsi:type="ns1:DelEgrRteRqstType">
	<objKey>		<objKey>
	<rant>iana-en:111</rant>		<rant>iana-en:111</rant>
	<name>EGR_RTE_01</name>		<name>EGR_RTE_01</name>
	</objKey>		</objKey>
	</rqstObj>		</rqst>
	</spppUpdateRequest>		</spppUpdateRequest>
	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"?>
	<spppUpdateResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"		<spppUpdateResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">		xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
	<serverTransId>txid-982543123</serverTransId>		<serverTransId>txid-982543123</serverTransId>
	skipping to change at page 84, line 41		skipping to change at page 82, line 41
	<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>		<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
	</sequence>		</sequence>
	</extension>		</extension>
	</complexContent>		</complexContent>
	</complexType>		</complexType>
	<complexType name="NSType">		<complexType name="NSType">
	<complexContent>		<complexContent>
	<extension base="spppb:RteRecType">		<extension base="spppb:RteRecType">
	<sequence>		<sequence>
	<element name="hostName" type="string"/>		<element name="hostName" type="string"/>
			<element name="ipAddr" type="spppb:IPAddrType" minOccurs="0"
			maxOccurs="unbounded"/>
	<element name="ttl" type="positiveInteger" minOccurs="0"/>		<element name="ttl" type="positiveInteger" minOccurs="0"/>
	<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>		<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
	</sequence>		</sequence>
	</extension>		</extension>
	</complexContent>		</complexContent>
	</complexType>		</complexType>
	<complexType name="URIType">		<complexType name="URIType">
	<complexContent>		<complexContent>
	<extension base="spppb:RteRecType">		<extension base="spppb:RteRecType">
	<sequence>		<sequence>
	skipping to change at page 85, line 45		skipping to change at page 83, line 47
	</extension>		</extension>
	</complexContent>		</complexContent>
	</complexType>		</complexType>
	<annotation>		<annotation>
	<documentation> ------------------ Abstract Object and Element		<documentation> ------------------ Abstract Object and Element
	Type Definitions -------------- </documentation>		Type Definitions -------------- </documentation>
	</annotation>		</annotation>
	<complexType name="BasicObjType" abstract="true">		<complexType name="BasicObjType" abstract="true">
	<sequence>		<sequence>
	<element name="rant" type="spppb:OrgIdType"/>		<element name="rant" type="spppb:OrgIdType"/>
	<element name="rar" type="spppb:OrgIdType"/>
	<element name="cDate" type="dateTime" minOccurs="0"/>		<element name="cDate" type="dateTime" minOccurs="0"/>
	<element name="mDate" type="dateTime" minOccurs="0"/>		<element name="mDate" type="dateTime" minOccurs="0"/>
	<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>		<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
	</sequence>		</sequence>
	</complexType>		</complexType>
	<complexType name="RegexParamType">		<complexType name="RegexParamType">
	<sequence>		<sequence>
	<element name="ere" type="string" default="^(.*)$"/>		<element name="ere" type="string" default="^(.*)$"/>
	<element name="repl" type="string"/>		<element name="repl" type="string"/>
	</sequence>		</sequence>
	skipping to change at page 86, line 27		skipping to change at page 84, line 28
	</simpleType>		</simpleType>
	<simpleType name="MinorVerType">		<simpleType name="MinorVerType">
	<restriction base="unsignedLong"/>		<restriction base="unsignedLong"/>
	</simpleType>		</simpleType>
	<complexType name="ObjKeyType">		<complexType name="ObjKeyType">
	<sequence>		<sequence>
	<element name="rant" type="spppb:OrgIdType"/>		<element name="rant" type="spppb:OrgIdType"/>
	<element name="name" type="spppb:ObjNameType"/>		<element name="name" type="spppb:ObjNameType"/>
	</sequence>		</sequence>
	</complexType>		</complexType>
			<complexType name="IPAddrType">
			<sequence>
			<element name="addr" type="string"/>
			<element name="type" type="spppb:IPType"/>
			<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
			</sequence>
			</complexType>
			<simpleType name="IPType">
			<restriction base="token">
			<enumeration value="IPv4"/>
			<enumeration value="IPv6"/>
			</restriction>
			</simpleType>
	<complexType name="RteRecRefType">		<complexType name="RteRecRefType">
	<sequence>		<sequence>
	<element name="rrKey" type="spppb:ObjKeyType"/>		<element name="rrKey" type="spppb:ObjKeyType"/>
	<element name="priority" type="unsignedShort"/>		<element name="priority" type="unsignedShort"/>
	<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>		<element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
	</sequence>		</sequence>
	</complexType>		</complexType>
	<complexType name="SourceIdentType">		<complexType name="SourceIdentType">
	<sequence>		<sequence>
	<element name="sourceIdentLabel" type="string"/>		<element name="sourceIdentLabel" type="string"/>
	skipping to change at page 95, line 34		skipping to change at page 94, line 34
	January 2004.		January 2004.
	[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform		[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
	Resource Identifier (URI): Generic Syntax", STD 66,		Resource Identifier (URI): Generic Syntax", STD 66,
	RFC 3986, January 2005.		RFC 3986, January 2005.
	13.2. Informative References		13.2. Informative References
	[I-D.ietf-drinks-usecases-requirements]		[I-D.ietf-drinks-usecases-requirements]
	Channabasappa, S., "DRINKS Use cases and Protocol		Channabasappa, S., "DRINKS Use cases and Protocol
	Requirements", draft-ietf-drinks-usecases-requirements-04		Requirements", draft-ietf-drinks-usecases-requirements-05
	(work in progress), October 2010.		(work in progress), March 2011.
	[RFC2781] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO		[RFC2781] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO
	10646", RFC 2781, February 2000.		10646", RFC 2781, February 2000.
	[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,		[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
	A., Peterson, J., Sparks, R., Handley, M., and E.		A., Peterson, J., Sparks, R., Handley, M., and E.
	Schooler, "SIP: Session Initiation Protocol", RFC 3261,		Schooler, "SIP: Session Initiation Protocol", RFC 3261,
	June 2002.		June 2002.
	[RFC3761] Faltstrom, P. and M. Mealling, "The E.164 to Uniform		[RFC3761] Faltstrom, P. and M. Mealling, "The E.164 to Uniform
End of changes. 93 change blocks.
	207 lines changed or deleted		211 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/