DRINKS                                                         J-F. Mule
Internet-Draft                                                 CableLabs
Intended status: Standards Track                           K. Cartwright
Expires: January 13, April 15, 2011                                              TNS
                                                                  S. Ali
                                                                 NeuStar
                                                            A. Mayrhofer
                                                            enum.at GmbH
                                                           July
                                                        October 12, 2010

                 Session Peering Provisioning Protocol
                      draft-ietf-drinks-spprov-01
                      draft-ietf-drinks-spprov-02

Abstract

   This document defines a protocol for provisioning session
   establishment data into Session Data Registries and SIP Service
   Provider data stores.  The provisioned data is typically used by
   various network elements for session peering.

   This document describes the Session Peering Provisioning Protocol
   used by clients to provision registries.  The document provides a set
   of guiding principles for the design of this protocol including
   extensibility and independent transport definitions, a basic data
   model and an XML Schema Document.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 13, April 15, 2011.

Copyright Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  7
   3.  Protocol Definition  . . . High Level Design . . . . . . . . . . . . . . . . . .  9
     3.1.  Protocol Overview and Layering  . . . . . . . . . . . . . .  9
     3.2.  Data Model . . . . . . . . . . . . . . . . . . . . . . . . 10
       3.2.1.  Structure of the SPPP Data Model . . . . . . . . . . . 10
       3.2.2.  9
     3.2.  Protocol Data Model Objects and Attributes  . . . . . . . . . . 12
       3.2.3.  Applicability for LUF-only Data Provisioning . . . . . 13
       3.2.4.  Applicability for LUF+LRF data Provisioning  . . . . . 15
     3.3.  Common Attributes  . . .  . . . . . . . . . . . . . . . . . 17
     3.4.  Known Issues and Current Limitations of the Data Model . . 17 10
   4.  Transport Protocol Requirements  . . . . . . . . . . . . . . . 18 14
     4.1.  Connection Oriented  . . . . . . . . . . . . . . . . . . . 19 15
     4.2.  Request & and Response Model . . . . . . . . . . . . . . . . . 19 15
     4.3.  Connection Lifetime  . . . . . . . . . . . . . . . . . . . 19 15
     4.4.  Authentication . . . . . . . . . . . . . . . . . . . . . . 19 15
     4.5.  Confidentiality & and Integrity  . . . . . . . . . . . . . . . 20 16
     4.6.  Near Real Time . . . . . . . . . . . . . . . . . . . . . . 20 16
     4.7.  Request & and Response Sizes . . . . . . . . . . . . . . . . . 20 16
     4.8.  Request and Response Correlation . . . . . . . . . . . . . 20 16
     4.9.  Request Acknowledgement  . . . . . . . . . . . . . . . . . 20 16
     4.10. Mandatory Transport  . . . . . . . . . . . . . . . . . . . 21 17
   5.  XML Considerations .  Base Protocol Data Structures  . . . . . . . . . . . . . . . . 18
     5.1.  Request and Response Structures  . . . . . 22
     5.1.  Namespaces . . . . . . . . 18
       5.1.1.  Update Request and Response Structures . . . . . . . . 18
       5.1.2.  Query Request and Response Structures  . . . . . . . . 22 21
     5.2.  Versioning  Response Codes and Messages  . . . . . . . . . . . . . . . 23
     5.3.  Basic Object Type and Organization Identifiers . . . . . . 25
   6.  Protocol Commands  . . . 22
   6.  Request and Reply Model . . . . . . . . . . . . . . . . . . . 23 27
     6.1.  Request  .  Add Route Group Operation  . . . . . . . . . . . . . . . . 27
     6.2.  Get Route Groups Operation . . . . . . . . 23
     6.2.  Reply . . . . . . . . 31
     6.3.  Add Destination Group Operation  . . . . . . . . . . . . . 32
     6.4.  Get Destination Groups Operation . . . . . 25
   7.  Response Codes and Messages . . . . . . . . 33
     6.5.  Add Route Group Offer Operation  . . . . . . . . . 27
   8.  Protocol Commands . . . . 34
     6.6.  Accept Route Group Offer Operation . . . . . . . . . . . . 36
     6.7.  Reject Route Group Offer Operation . . . . . . 29
     8.1.  Add Route Group Operation . . . . . . 37
     6.8.  Get Route Group Offers Operation . . . . . . . . . . 29
     8.2.  Get Route Groups Operation . . . 38
     6.9.  Public Identifier Operations . . . . . . . . . . . . . 36
     8.3.  Add Route Group Offers Operation . . 40
     6.10. Egress Route Operations  . . . . . . . . . . . 38
     8.4.  Accept Route Group Offers Operation . . . . . . 44
     6.11. Add Route Record Operation . . . . . 41
     8.5.  Reject Route Group Offers Operation . . . . . . . . . . . 42
     8.6. 46
     6.12. Get Route Group Offers Records Operation  . . . . . . . . . . . . . 44
     8.7.  Public Identifier Operations . . 51
     6.13. Delete Operation . . . . . . . . . . . . . 47
       8.7.1.  Add Public Identifier . . . . . . . . 52
   7.  SPPP Examples  . . . . . . . . 47
       8.7.2.  Get Public Identifier . . . . . . . . . . . . . . . . 50
       8.7.3.  Delete Public Identifier 53
     7.1.  Add Destination Group  . . . . . . . . . . . . . . . 51
     8.8.  Egress . . . 53
     7.2.  Add Route Operations Records  . . . . . . . . . . . . . . . . . 52
       8.8.1. . . . 54
     7.3.  Add Egress Route Records -- URIType . . . . . . . . . . . . . . . 55
     7.4.  Add Route Group  . . . . . . 53
       8.8.2.  Get Egress . . . . . . . . . . . . . . . 56
     7.5.  Add Public Identity -- Successful COR claim  . . . . . . . 58
     7.6.  Add LRN  . . . . . . . . . . . . . . . . . . . . . . . . . 59
     7.7.  Add TN Range . . . . . . . . . . . . . . . . . . . . . . . 60
     7.8.  Add TN Range with Open Number Plan support . . . . . . . . 61
     7.9.  Enable Peering -- Route Group Offer  . . . . . . . . . . . 62
     7.10. Enable Peering -- Route Group Offer Accept . . . . . . . . 54
       8.8.3.  Delete 64
     7.11. Add Egress Route . . . . . . . . . . . . . . . . . 55
   9.  Security Considerations . . . . 65
     7.12. Get Destination Group  . . . . . . . . . . . . . . . . . 56
   10. IANA Considerations . 66
     7.13. Get Public Identity  . . . . . . . . . . . . . . . . . . . 67
     7.14. Get Route Group Request  . 57
   11. Formal Specification . . . . . . . . . . . . . . . . 68
     7.15. Get Route Group Offers Request . . . . . 58
   12. Specification Extensibility . . . . . . . . . 69
     7.16. Get Egree Route  . . . . . . . . . . . 71
   13. Acknowledgments . . . . . . . . . . 70
     7.17. Delete Destination Group . . . . . . . . . . . . . . . . . 72
   14. References
     7.18. Delete Public Identity . . . . . . . . . . . . . . . . . . 72
     7.19. Delete Route Group Request . . . . . . . . . . . . . . . . 73
     14.1. Normative References
     7.20. Delete Route Group Offers Request  . . . . . . . . . . . . 74
     7.21. Delete Egress Route  . . . . . . . 73
     14.2. Informative References . . . . . . . . . . . . 75
   8.  XML Considerations . . . . . . . 73
   Authors' Addresses . . . . . . . . . . . . . . . 77
     8.1.  Namespaces . . . . . . . . . 75

1.  Introduction

   Service providers . . . . . . . . . . . . . . . 77
     8.2.  Versioning and enterprises use registries to make call or
   session Character Encoding  . . . . . . . . . . . . 77
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 78
   10. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 79
   11. Formal Specification . . . . . . . . . . . . . . . . . . . . . 80
   12. Specification Extensibility  . . . . . . . . . . . . . . . . . 93
   13. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 94
   14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 95
     14.1. Normative References . . . . . . . . . . . . . . . . . . . 95
     14.2. Informative References . . . . . . . . . . . . . . . . . . 95
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 97

1.  Introduction

   Service providers and enterprises use registries to make call or
   session routing decisions for Voice over IP, SMS and MMS traffic
   exchanges.  This document is narrowly focused on the provisioning
   protocol for these registries.  This protocol prescribes a way for an
   entity to provision session-related data into a registry.  The data
   being provisioned can be optionally shared with other participating
   peering entities.  The requirements and use cases driving this
   protocol have been documented in
   [I-D.ietf-drinks-usecases-requirements].  The reader is expected to
   be familiar with the terminology defined in the previously mentioned
   document.

   Three types of provisioning flows have been described in the use case
   document: client to registry provisioning, registry to local data
   repository and registry-to-registry.  This document addresses a
   subset (client-to-registry provisioning) by defining a Session
   Peering Provisioning Protocol (SPPP) for provisioning Session
   Establishment Data (SED) into a Registry (arrow numbered one "1" in the figure
   below).  While the other "provisioning flows" are shown below as
   separate message flows, no determination has been made for whether
   one common baseline protocol could be used for all three, or whether
   distinct protocols are required.

                             *------------*               *------------*
    (1). Provisioning SED    |            | (3).Registry  |            |
    -----------------------> |  Registry  |<------------->|  Registry  |
         data into Registries|            |  to Registry  |            |
                             *------------*  exchanges    *------------*
                                  /  \                          \
                                 /    \                          \
                                /      \                          \
                               /        \                          v
                              /          \                         ...
                             /            \
                            / (2).         \
                           / Distributing   \
                          /      SED         \
                         V                    V
                        +----------+       +----------+
                        |Local Data|       |Local Data|
                        |Repository|       |Repository|
                        +----------+       +----------+

                     Three Registry Provisioning Flows

                                 Figure 1

   The data provisioned for session establishment is typically used by
   various downstream SIP signaling systems to route a call to the next
   hop associated with the called domain.  These systems typically use a
   local data store ("Local Data Repository") as their source of session
   routing information.  More specifically, the SED data is the set of
   parameters that the outgoing signaling path border elements (SBEs)
   need to initiate the session.  See [RFC5486] for more details.

   A "terminating" SIP Service Provider (SSP) provisions SED into the
   registry to be selectively shared with other peer SSPs.
   Subsequently, a Registry may distribute the provisioned data into
   local Data Repositories used for look-up queries (identifier -> URI)
   or for lookup and location resolution (identifier -> URI -> ingress
   SBE of terminating SSP).  In some cases, the Registry may
   additionally offer a central query resolution service (not shown in
   the above figure).

   A key requirement for the SPPP protocol is to be able to accommodate
   two basic deployment scenarios:

   1.  A Local Data Repository serves a Look-Up Function (LUF) to
       determine the target domain to assist in call routing (as
       described in [RFC5486]).  In this case, the querying entity may
       use other means to perform the Location Routing Function (LRF)
       which in turn helps determine the actual location of the
       Signaling Function in that domain.

   2.  Both  A Local Data Repository serves both a Look-Up function (LUF) and
       Location Routing Function (LRF) to locate the SED data fully.

   In terms of protocol design, SPPP protocol is agnostic to the
   transport.  This document includes the description of the data model
   and the means to enable protocol operations within a request and
   response structure.  To encourage interoperability, the protocol
   supports extensibility aspects.

   Transport requirements are provided in this document to help with the
   selection of the optimum transport mechanism.
   ([I-D.ietf-drinks-sppp-over-soap]) identifies a SOAP transport
   mechanism for SPPP.

   This document is organized as follows:

   o    Section 3 2 provides an overview the terminology;

   o    Section 3 provides an overview of the SPPP protocol, including
        the layering approach, functional entities and data model;

   o    Section 4 defines specifies requirements for SPPP transport protocols;

   o    Section 5 describes the base protocol data structures including
        the request and response elements (Section 5.1), the response
        codes and messages (Section 5.2) and the basic object type most
        first class objects extend from;

   o    Section 6 and Section 7 describe the main protocol commands and
        examples;

   o    Section 8 defines XML considerations that XML parsers must meet
        to conform to this specification.

   o    Section 6 describes the protocol request-reply model; specification;

   o    Section 8 11 normatively defines the SPPP protocol commands for this version of
        SPPP, and how to extend them; using its XML
        Schema Definition.

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

   This document reuses terms from [RFC3261], [RFC5486], use cases and
   requirements documented in [I-D.ietf-drinks-usecases-requirements]
   and the ENUM Validation Architecture [RFC4725].

   In addition, this document specifies the following additional terms:

   SPPP:   Session Peering Provisioning Protocol, the protocol used to
      provision data into a Registry (see arrow labeled "1." in Figure 1
      of [I-D.ietf-drinks-usecases-requirements]).  It is the primary
      scope of this document.

   SPDP:   Session Peering Distribution Protocol, the protocol used to
      distribute data to Local Data Repository (see arrow labeled "2."
      in Figure 1 of [I-D.ietf-drinks-usecases-requirements]).

   Client:   An application that supports an SPPP Client; it is
      sometimes referred to as a "Registry Client".

   Registry:   The Registry operates a master database of Session
      Establishment Data for one or more Registrants.

      A Registry acts as an SPPP Server.

   Registrant:   In this document, we extend the definition of a
      Registrant based on [RFC4725].  The Registrant is the end-user,
      the person or organization who is the "holder" of the Session
      Establishment Data being provisioned into the Registry.  For
      example, in [I-D.ietf-drinks-usecases-requirements], a Registrant
      is pictured as a SIP Service Provider in Figure 2.

      A Registrant is identified by its name and an identifier in the
      data model.

   Registrar:   In this document, we also extend the definition of a
      Registrar from [RFC4725].  A Registrar performs provisioning
      operations on behalf of a Registrant by interacting with the
      Registry, in our case via the SPPP protocol defined in this
      document.

      A Registrar is identified by its name and an identifier in the
      data model.

3.  Protocol Definition High Level Design

   This section introduces the structure of the data model and provides
   the information framework for the SPPP protocol.  An overview of the
   protocol operations is first provided with a typical deployment
   scenario.  The data model is then defined along with all the objects
   manipulated by the protocol and their relationships.

3.1.  Protocol Overview and Layering

   SPPP is a simple request/reply protocol that allows a client
   application to submit provisioning data and query requests to a
   server.  The SPPP data structures are designed to be protocol
   agnostic.  Concerns regarding encryption, non-repudiation, and
   authentication are beyond the scope of this document.  For more
   details, please refer to the Transport Protocol Requirements section.

                   Layer                      Example
              +-------------+      +-----------------------------+
          (5) |Data Objects |      |      RteGrpType, etc.       |
              +-------------+      +-----------------------------+
                    |                           |
              +-------------+      +-----------------------------+
          (4) | Operations  |      |    addRteGrpsRqst,   AddRteGrpRqstType, etc.   |
              +-------------+      +-----------------------------+
                    |                           |
              +-------------+      +-----------------------------+
          (3) |   Message   |      | spppRequest, spppResponse    spppUpdateRequest,       |
              |             |      |    spppUpdateResponse,      |
              |             |      |    spppQueryRequest,        |
              |             |      |    spppQueryResponse        |
              +-------------+      +-----------------------------+
                    |                           |
              +-------------+      +-----------------------------+
          (2) |   Message   |      |   HTTP, SOAP, None, etc.    |
              |   Envelope  |      |                             |
              +-------------+      +-----------------------------+
                    |                           |
              +-------------+      +-----------------------------+
          (1) |  Transport  |      |    TCP, TLS, BEEP, etc.     |
              |   Protocol  |      |                             |
              +-------------+      +-----------------------------+

                               SPPP Layering

                                 Figure 2

   SPPP can be viewed as a set of layers that collectively define the
   structure of an SPPP request and response.  Layers 1 and 2, as
   detailed below, are left to separate specifications to allow for
   potentially multiple SPPP transport, envelope, and authentication
   technologies.  This document defines layers 3, 4, and 5 below.

   1.  The transport protocol layer provides a communication mechanism
       between the client and server.  SPPP can be layered over any
       transport protocol that provides a set of basic requirements
       defined in the Transport Protocol Requirements section.

   2.  The message envelope layer is optional, but can provide features
       that are above the transport technology layer but below the
       application messaging layer.  Technologies such as HTTP and SOAP
       are examples of messaging envelope technologies.

   3.  The message layer provides a simple, envelope-independent and
       transport-independent, SPPP wrapper for SPPP request and response
       messages.

   4.  The operation layer defines the set of base SPPP actions that can
       be invoked for a given object data type using an SPPP message.
       Operations are encoded using XML encoded actions and objects.

   5.  The data object layer defines the base set of SPPP data objects
       that can be included in update operations or returned in
       operation responses.

3.2.  Protocol Data Model

   The data model illustrated and described in Figure 3 defines the
   logical objects and the relationships between these objects that the
   SPPP protocol supports.  SPPP defines the protocol operations through
   which an SPPP Client populates a Registry with these logical objects.
   Various clients belonging to different Registrants and distinct Registrars may use the
   protocol for populating the Registry's data.

3.2.1.  Structure of the SPPP Data Model

   The logical structure presented below is consistent with the
   terminology and requirements defined in
   [I-D.ietf-drinks-usecases-requirements].  Note that the current
   version of this data model does not yet address the notion of Data
   Recipient Groups (left for a future revision of this document).

   +-------------+      +------------------+
   | all object  |      |Organization:     |
   | types       |      |orgId,            |
   +------+------+      |orgName,          |
          +------------>|
          +------------>|extension         |
                        |
                        |extension                  |

    All objects are     |                  |
    associated with 2   |                  |
    Organizations to    +------------------+
    identify the            ^
    registrant and          |A Route Group is
    the registrar           |associated with
                            |zero or more Peering
                            |Organizations
                            |
                   +--------+--------------+
                   |Route Group:           |        +-----[abstract]-+
                   |  rantId*,  rantId,              |        | Route Record:  |
                   |  rarId,               |        |                |
                   |  rteGrpName*,  rteGrpName,          |        | Route Record:  rrName,       |
                   |  dgName*,  destGrpRef,          +------->|  priority,     |
                   |  isInSvc,             |        |  extension     |
                   |  rteRec*,  rteRecRef,           |        |                |
                   |  peeringOrg,          |        +----------------+
                   |  sourceIdent,         |            ^
                   |  priority,            |            |
                   |  extension            |            |Various types
                   +-----------------------+            |of Route
                         ^                              |Records...
                         |                       +------+------------...
                         |                       |        |         |
                         |                     +----+  +-------+ +----+
                         |                     | URI|  | NAPTR | | NS |
        +----------------+-----+               +----+  +-------+ +----+
        |Destination           |
        |Group:                |     +----------[abstract]-+
        |  rantId*,  rantId,             |     |Public Identifier:   |
        |  rarId,              |     |Identifier:     |                     |  dgName*,
        |  dgName,             |     |  rantId*,  rantId,            |
        |  extension           |<----+  rarId,             |
        +----------------------+     |  publicIdentifier*,  publicIdentifier,  |
                                     |  destGrpRef,        |
                                     |  dgName*,  rteRec,            |
                                     |  extension          |
                                     +---------------------+
                                                ^
                                                |Various types
                                                |of Public
                                                |Identifiers...
                                     +------+------------...
                                     |        |      |
                                  +-----+  +----+ +-----+
                                  |Email|
                                  | TN  |  |TNR | | TNR RN  |
                                  +-----+  +----+ +-----+ ...

                              SPPP Data Model

                                 Figure 3

   Note that the attributes whose names end with the character * are
   mandatory attributes.

3.2.2.  Data Model Objects and Attributes

   The objects and attributes that comprise the data model can be
   described as follows (objects listed from the bottom up):

   o  Public Identifier (publicIdentifier): Identifier:
      A public identifier is a well known attribute that is often used as the
      key to perform lookup functions.  For the purposes of this
      document, a Public Identifier can be an email address, a telephone number, a range
      of telephone numbers or numbers, a PSTN Routing Number (RN). (RN), or perhaps
      another type of lookup key.

      A Destination Group Public Identifier may be associated with a Public Identifier Destination Group to
      create a logical grouping and of Public Identifiers that share a
      common set of Routes.

      A Public Identifier may optionally be associated with zero or more
      individual route records. Route Records.  This ability for a Public Identifier to
      be directly associated with a set of routes Route Records (e.g. target
      URI), as opposed to being associated with a Destination Group,
      supports the use cases where the target URI contains data
      specifically tailored to an individual Public Identifier.

   o  Telephone Number Range (TNRType, tn, endTn): Range:
      A public identifier may represent an inclusive range of telephone
      numbers.  The TN range is defined by the first and last telephone
      number of the inclusive range.  For example, a TN range of
      (tn=12125550000, endTn=12125560000) defined by
      tn=12125550000 and endTn=12125560000 means all the TNs from
      12125550000 to 12125560000 inclusive are included.

   o  Destination Group (dgName): Group:
      A name collection of zero or more Public Identifiers that are related
      to can be
      associated with one or more Route Group relationships. Groups for the purpose of
      facilitating the management of thier common routing information.

   o  Route Group (rteGrpName): Group:
      A Route Group contains a set of route records (RteRecs) that are
      associated with Public Identifiers.  To support the use cases
      defined in [I-D.ietf-drinks-usecases-requirements], this document
      defines the following types references to Route Records, a set
      of RteRecs: NAPTRType, NSType, Destination Group references, and
      URIType.  To support the Look-Up Function resolution, it is
      assumed that the administrative domain will be defined as a URI
      and it can be expressed as set of peering organization
      identifiers.  This is used to establishe a URIType or three part
      relationships between a NAPTRType.
      A Route Group can be either in or out set of service (as indicated by
      'isInService' attribute).  It also contains a Public Identifiers and their common
      routing information (SED), and the list of peering organizations
      whose query responses may include that can routing information in
      their query responses.  To support the object (peeringOrg) and have
      access to its content (sourceIdent).

   o  Source Identity (SourceIdentType, sourceIdentLabels,
      sourceIdentScheme):
      In some scenarios, it is important to identify use cases defined in
      [I-D.ietf-drinks-usecases-requirements], this document defines the source
      following types of a
      query. Route Records: NAPTRType, NSType, and URIType.
      The source identity label is sourceIdent element within a character string that
      identifies Route Group, in concert with the source
      set of a resolution lookup and can be used for
      source-based peering organization identifiers enables fine grained
      source based routing.  We define several ways of identifying the
      source: by IP address, by  Further details about the Route Group and
      source URI or a domain name. based routing refer to the definitions and descriptions of
      the Route Group operations found later in this document.

   o  Route Record (RteRecType): Record:
      A Route Record is contains the data that the a resolution systems return system returns
      in response to a successful query with the for a Public Identifier as the
      query string.  It is Identifier.  Route
      Recoords are associated with a Route Group for routes SED that
      are is not
      specific to a Public Identifier.
      To support the use cases defined in
      [I-D.ietf-drinks-usecases-requirements], SPPP protocol defines
      three type of Route Records: URIType, NAPTRType, and NSType.
      These Route Records extend the abstract type RteRecType and
      inherit the common attribute 'priority' that is meant for setting
      precedence across the route records defined within a Route Group
      in a protocol agnostic fashion.

   o  Organization (OrgIdType):  Organization:
      An Organization represents is an entity that is authorized to access
      given data elements. may fulfill any combination of
      three roles: Registrant, Registrar, and Peering Organization.  All
      SPPP objects are associated with two
      organizations organization identifiers to
      identify the each object's registrant and the registrar.  An
      entity authorized to view a  A Route
      Group (typically a SSP peering
      partner) object is identified also associated with a peering Organization (peeringOrg).

3.2.3.  Applicability for LUF-only Data Provisioning

   This section describes set of zero or more
      organization identifiers that identify the data model for SPPP clients peering organizations
      whose query responses may include the routing information (SED)
      defined in the Route Records within that only
   provision data Route Group.

4.  Transport Protocol Requirements

   This section provides requirements for LUF resolution.

   The purpose of LUF data provisioning is transport protocols suitable
   for SPPP.  More specifically, this section specifies the services,
   features, and assumptions that SPPP delegates to provide the administrative
   domain given a destination group.  As such, chosen transport
   and envelope technologies.

   Two different groups of use cases are specified in
   [I-D.ietf-drinks-usecases-requirements].  One group of use cases
   describes the provisioning of data by a client provisioning
   LUF-only into a Registry
   (Section 3.1 of the above referenced document), while the other group
   describes the distribution of data only needs into local data repositories
   (Section 3.2).  The current version of this document focuses on the
   first set of use cases (client to provide one registry provisioning).

   These use cases may involve the provisioning of very small data sets
   like the modification or more route groups that
   contain update of a route group name and single public identifier.  Other
   provisioning operations may deal with huge datasets like the
   "download" of a URI whole local number portability database to a
   Registry.

   As a result, a transport protocol for SPPP must be very flexible and
   accommodate various sizes of data set sizes.

   For the target domain.

   Note that source-based routing reasons outlined above, it is supported: depending conceivable that provisioning
   and distributing may use different transport protocols.  This
   document focuses on what entity
   requests the look-up resolution (sourceIdent), provisioning protocol.

   A few topics remain open for discussion:

   o  The ability to establish multiple connections between a different URI client and
      server may be
   returned by using different Route Groups.

   Certain desirable.  If so, we may want to specify the
      relation of transactions between the various connections.

   o  Pipelining of requests is required at the SPPP protocol operations could layer.  It
      may have impacts at the transport level that need to be added in future revisions outlined.

   o  Scope: the current scope of this document as "short-cuts" for LUF related data provisioning.

                        +-----------------------+
                        |Route Group:           |
                        |  rteGrpName*,         |
                        |  isInService,         |
                        |  URI    ,             |
                        |  extension            |
                        |                       |
                        +-----------------------+
                                   ^
                                   |
                         +---------+------------+
                         |Destination           |
                         |Group:                |
                         |  dgName*,            |<----+
                         |  extension           |     |
                         +----------------------+     |
                                                      |
                                        +-------------+---------+
                                        |Public                 |
                                        |Identifier:            |
                                        |  publicIdentifier*,   |
                                        |  dgName*,             |
                                        |  extension            |
                                        +-----------------------+

                   LUF-only Data Model Example for SPPP

                                 Figure 4

   As an example, effort is based upon having a request
      connection oriented transport.  Is there any need to add support a route group where public
   identifiers resolve into
      transport protocol with asynchronous operation?

   o  If it is required that responses arrive in the URI sip:ssp1.example.com during look-up
   resolution would be:

       <?xml version="1.0" encoding="UTF-8"?>
       <addRteGrpsRqst
              xmlns="urn:ietf:params:xml:ns:sppp:base:1"
              xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
               <clientTransId>id-12317123</clientTransId>
               <minorVer>20</minorVer>
               <rteGrp>
                   <base>
                       <rantId>registrantID123</rantId>
                       <rarId>registrarId0</rarId>
                   </base>
                   <rteGrpName>route_grp_1</rteGrpName>
                   <rteRec xsi:type="URIType">
                       <ere>^(.*)$</ere>
                       <uri>urn:ssp1.example.com</uri>
                   </rteRec>
                   <isInSvc>true</isInSvc>
               </rteGrp>
       </addRteGrpsRqst>

                                 Figure 5

3.2.4.  Applicability for LUF+LRF data Provisioning

   This section provides a read-out order of the data
      requests, this must be specified clearly.

4.1.  Connection Oriented

   The SPPP protocol follows a model where a Client establishes a
   connection to a Server in order to further exchange provisioning
   transactions over such point-to-point connection.  A transport
   protocol for SPPP clients MUST therefore be connection oriented.

   Note that provision data for both LUF and LRF resolution.

   The purpose the role of LUF+LRF data provisioning is the "Client" and the "Server" only applies to provide a URI given a
   destination group as well as
   the location routing for that target
   domain.  As such, a client provisioning LUF+LRF data provides one or
   more route groups connection, and those roles are not related in any way to the
   type of entity that contain participates in a route group name and protocol exchange.  For
   example, a URI Registry might also include a "Client" when such a
   Registry initiates a connection (for example, for the
   target domain data distribution
   to SSP).

4.2.  Request and each route group Response Model

   Provisioning operations in SPPP follow the request - response model,
   where a transaction is associated with initiated by a Route Record
   which can be in Client using a Request command,
   and the form Server responds to the Client by means of a URI, NAPTR or NS resource record.

                   +-----------------------+
                   |Route Group:           |        +-----[abstract]-+
                   |  rteGrpName*,         |        |                |
                   |  isInSvc,             |        | Route Record:  |
                   |  rteRec,              +------->|  NAPTR         |
                   |  extension            |        |  priority,     |
                   |                       |        |  extension     |
                   +-----------------------+        |                |
                              ^                     +----------------+
                              |
                    +---------+------------+
                    |Destination           |
                    |Group:                |
                    |  dgName*,            |<----+
                    |  extension           |     |
                    +----------------------+     |
                                                 |
                                   +-------------+-[abstract]-+
                                   |Public                    |
                                   |Identifier:               |
                                   |  publicIdentifier*,      |
                                   |  dgName*,                |
                                   |  extension               |
                                   +--------------------------+

                    LUF+LRF Data Model Example Response.

   Multiple subsequent request-response exchanges MAY be performed over
   a single connection.

   Therefore, a transport protocol for SPPP

                                 Figure 6

   As an example, MUST follow the request-
   response model by allowing a response to be sent to the request
   initiator.

4.3.  Connection Lifetime

   Some use cases involve provisioning a single request to add a route group where public
   identifiers resolve into the URI ssp1.example.com network
   element - connections supporting such provisioning requests might be
   short-lived, and NAPTR
   associated with that domain based only established on the source Organization would
   be:

         <?xml version="1.0" encoding="UTF-8"?>
         <addRteGrpsRqst xmlns="urn:ietf:params:xml:ns:sppp:base:1"
             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                 <clientTransId>id-12317123</clientTransId>
                 <minorVer>20</minorVer>
                 <rteGrp>
                     <base>
                         <rantId>registrantID123</rantId>
                         <rarId>registrarId0</rarId>
                     </base>
                     <rteGrpName>route_grp_1</rteGrpName>
                     <isInSvc>true</isInSvc>
                     <rteRec xsi:type="URIType">
                         <ere>^(.*)$</ere>
                         <uri>urn:ssp1.example.com</uri>
                     </rteRec>
                     <isInSvc>true</isInSvc>
                 </rteGrp>
         </addRteGrpsRqst>

                                 Figure 7

3.3.  Common Attributes

   This section defines common object attributes.  The demand.

   Other use cases involve either provisioning a huge set of data, or a
   constant stream of small updates, which would require long-lived
   connections.

   Therefore, a protocol
   exchanges and operations in suitable for SPPP take various parameters.  Some of
   these are common to several objects.

   Two organization roles have been identified in the SHOULD support short lived as
   well as long lived connections.

4.4.  Authentication

   Many use cases require the Server to authenticate the Client, and in
   this protocol.  A registrant is
   potentially also the organization or business entity
   that "owns" Client to authenticate the object while a registrar Server.  While
   authentication of the Server by the Client is an entity that can
   provision an object.

3.4.  Known Issues and Current Limitations expected to be used
   only to prevent impersonation of the Data Model

   The data model described in Figure 3 does not yet address all Server, authentication of the
   requirements
   Client by the Server is expected to be used to identify and use cases defined in
   [I-D.ietf-drinks-usecases-requirements].

   This section will list known further
   authorize the Client to certain resources on the Server.

   Therefore, an SPPP transport protocol issues MUST provide means for a Server
   to be addressed in
   future revisions.

4.  Transport Protocol Requirements

   This section provides requirements authenticate and authorize a Client, and MAY provide means for
   Clients to authenticate a Server.

   However, SPPP transport protocols suitable SHOULD also allow for SPPP.  More specifically, this section specifies the services,
   features, unauthenticated
   connections.

4.5.  Confidentiality and assumptions Integrity

   Data that SPPP delegates to is transported over the chosen protocol is deemed confidential.
   Therefore, a transport protocol suitable for SPPP MUST ensure
   confidentiality and envelope technologies.

   Two different groups of use cases are specified in
   [I-D.ietf-drinks-usecases-requirements].  One group of integrity protection by providing encryption
   capabilities.

   Additionally, a DRINKS protocol MUST NOT use an unreliable lower-
   layer transport protocol that does not provide confidentiality and
   integrity protection.

4.6.  Near Real Time

   Many use cases
   describes require near real-time responses from the provisioning of data by a client into Server.
   Therefore, a Registry
   (Section 3.1 of the above referenced document), while the other group
   describes the distribution of data into local data repositories
   (Section 3.2).  The current version of this document focuses on DRINKS transport protocol MUST support near-real-time
   response to requests submitted by the
   first set Client.

4.7.  Request and Response Sizes

   SPPP covers a range of use cases (client to registry provisioning).

   These use - from cases may involve the where provisioning of very small data sets
   like the modification or update of a
   single public identifier.  Other
   provisioning operations may deal with huge datasets like the
   "download" of a whole local number portability database identifier will create very small request and response
   sizes to a
   Registry.

   As a result, cases where millions of data records are submitted or
   retrieved in one transaction.  Therefore, a transport protocol
   suitable for SPPP must be very flexible MUST support a great variety of request and
   accommodate various sizes
   response sizes.

   A transport protocol MAY allow splitting large chunks of data set sizes.

   For the reasons outlined above, it is conceivable that provisioning into
   several smaller chunks.

4.8.  Request and distributing may use different transport protocols.  This
   document focuses on the provisioning protocol. Response Correlation

   A few topics remain open transport protocol suitable for discussion:

   o  The ability SPPP MUST allow responses to establish multiple connections between a client and
      server may be desirable.  If so, we may want to specify the
      relation of transactions between the various connections.

   o  Pipelining of requests is required at
   correlated with requests.

4.9.  Request Acknowledgement

   Data transported in the SPPP protocol layer.  It
      may have impacts at is likely crucial for the transport level
   operation of the communication network that need is being provisioned.

   Failed transactions can lead to situations where a subset of public
   identifiers (or even SSPs) might not be outlined.

   o  Scope: reachable, or situations
   where the current scope provisioning state of this effort the network is based upon having a
      connection oriented transport.  Is there any need to support inconsistent.

   Therefore, a transport protocol with asynchronous operation?

   o  If it is required that responses arrive in the order of the
      requests, this must be specified clearly.

4.1.  Connection Oriented

   The for SPPP protocol follows MUST provide a model where Response for
   each Request, so that a Client establishes a
   connection to can identify whether a Server Request
   succeeded or failed.

4.10.  Mandatory Transport

   As of this writing of this revision, one transport protocol proposal
   has been provided in order to further exchange provisioning
   transactions over such point-to-point connection.  A [I-D.ietf-drinks-sppp-over-soap].

   This section will define a mandatory transport protocol for SPPP MUST therefore to be connection oriented.

   Note that the role
   compliant with this RFC.

5.  Base Protocol Data Structures

   SPPP uses a common model and a common set of data structures for most
   of the "Client" supported operations and object types.  This section describes
   these common data structures.

5.1.  Request and Response Structures

   An SPPP client interacts with an SPPP server by using one of the "Server" only applies
   supported transport mechanisms to
   the connection, and those roles are not related in any way send one or more requests to the
   type
   server and receive corresponding replies from the server.  There are
   two generalized types of entity operations that participates in a protocol exchange.  For
   example, a Registry might also include a "Client" when such a
   Registry initiates a connection (for example, for data distribution an SPPP client can submit to SSP).

4.2.
   an SPPP server, updates and queries.  The following two sub-sections
   describe the generalized data structures that are used for each of
   these two types of operations.

5.1.1.  Update Request & and Response Model

   Provisioning operations in Structures

   An SPPP follow the update request - is wrapped within the <spppUpdateRequest>
   element while an SPPP update response model,
   where a transaction is initiated by a Client using a wrapped within an
   <spppUpdateResponse> element.  The following two sub-sections
   describe these two elements.

5.1.1.1.  Update Request command,
   and

   An SPPP update request object is contained within the Server responds to generic
   <spppUpdateRequest> element.

     <element name="spppUpdateRequest">
       <complexType>
         <sequence>
           <element name="clientTransId" type="spppb:TransIdType"
                    minOccurs="0"/>
           <element name="minorVer" type="spppb:MinorVerType"
                    minOccurs="0"/>
           <element name="rqst" type="spppb:BasicRqstType"
                    maxOccurs="unbounded"/>
         </sequence>
       </complexType>
     </element>

     <simpleType name="TransIdType">
       <restriction base="string"/>
     </simpleType>
     <simpleType name="MinorVerType">
       <restriction base="unsignedLong"/>
     </simpleType>

   The data elements within the Client by means <spppUpdateRequest> element are
   described as follows:

   o    clientTransId: Zero or one client generated transaction ID that,
        within the context of a Response.

   Multiple subsequent request-response exchanges MAY be performed over
   a single connection.

   Therefore, a transport protocol for SPPP MUST follow the request-
   response model by allowing a response to SPPP client, identifies this request.
        This value can be sent to used at the request
   initiator.

4.3.  Connection Lifetime

   Some use cases involve provisioning a single request discretion of the SPPP client to a network
   element - connections supporting such provisioning
        track, log or correlate requests might be
   short-lived, and only established on demand.

   Other use cases involve either provisioning a huge set of data, or a
   constant stream of small updates, which would require long-lived
   connections.

   Therefore, a protocol suitable for SPPP SHOULD support short lived as
   well as long lived connections.

4.4.  Authentication

   Many use cases require the Server their responses.  This
        value is also echoed back to authenticate the Client, and
   potentially also client in the Client to authenticate SPPP update
        response.  An SPPP server will not check this value for
        uniqueness.

   o    minorVer: Zero or one minor version identifier, indicating the Server.  While
   authentication
        minor version of the Server by SPPP API that the Client client is expected attempting to be
        use.  This is used
   only in conjunction with the major version
        identifier in the XML namespace to prevent impersonation of identify the Server, authentication version of SPPP
        that the
   Client by client is using.  If the Server element is expected to be used to identify and further
   authorize not present, the Client to certain resources on
        server assumes that the client is using the latest minor version
        supported by the Server.

   Therefore, an SPPP transport protocol MUST provide means for a Server
   to authenticate and authorize a Client, and MAY provide means server for
   Clients to authenticate the given major version.  The
        versions supported by a Server.

   However, given SPPP transport SHOULD also allow for unauthenticated
   connections.

4.5.  Confidentiality & Integrity

   Data server can be retrieved by
        the client using the SPPP server menu operation described later
        in the document.

   o    rqst: One or more BasicRqstType objects.  These are the actions
        that is transported over the protocol client is deemed confidential.
   Therefore, a transport protocol suitable for requesting the SPPP MUST ensure
   confidentiality and integrity protection by providing encryption
   capabilities.

   Additionally, a DRINKS protocol MUST NOT use an unreliable lower-
   layer transport protocol that does not provide confidentiality and
   integrity protection.

4.6.  Near Real Time

   Many use cases require near real-time responses from the Server.
   Therefore, a DRINKS transport protocol MUST support near-real-time
   response to requests submitted server perform.  They are
        processed by the Client.

4.7.  Request & Response Sizes SPPP covers server in the order in which they are
        included in the request.  And with respect to handling error
        conditions, it is a range matter of use cases - from cases where provisioning policy whether the objects are
        processed in a
   single public identifier will create very small request "stop and response
   sizes to cases where millions of data records are submitted rollback" fashion or
   retrieved in one transaction.  Therefore, a transport protocol
   suitable for SPPP MUST support a great variety of request "stop and
   response sizes.

   A transport protocol MAY allow splitting large chunks of data into
   several smaller chunks.

4.8.  Request
        commit" fashion.  In the "stop and Response Correlation

   A transport protocol suitable for rollback" scenario, the SPPP MUST allow responses to be
   correlated with requests.

4.9.  Request Acknowledgement

   Data transported
        server would stop processing BasicRqstType object instances in
        the SPPP protocol is likely crucial request at the first error and roll back any BasicRqstType
        object instances that had already been processed for that update
        request.  In the
   operation of "stop and commit" scenario the communication network that is being provisioned.

   Failed transactions can lead to situations where a subset of public
   identifiers (or even SSPs) might not be reachable, or situations
   where SPPP server
        would stop processing BasicRqstType object instances in the provisioning state of
        request at the network is inconsistent.

   Therefore, a transport protocol first error but commit any BasicRqstType object
        instances that had already been processed for SPPP MUST provide a Response for
   each Request, so that a Client can identify whether a Request
   succeeded or failed.

4.10.  Mandatory Transport

   As of this writing of this revision, one transport protocol proposal
   has been provided in [I-D.ietf-drinks-sppp-over-soap]. update
        request.

   All update request objects extend the base type BasicRqstType.  This section will define a mandatory transport protocol to be
   compliant with this RFC.

5.  XML Considerations

   XML serves
   base type is defined as the encoding format for SPPP, allowing complex
   hierarchical data to be expressed in a text format that can be read,
   saved, and manipulated with both traditional text tools follows:

     <complexType name="BasicRqstType" abstract="true">
       <sequence>
         <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
       </sequence>
     </complexType>

   The BasicRqstType object primarily acts as an abstract base type, and tools
   specific to XML.

   XML
   its only data element is described as follows:

   o    ext: This is case sensitive.  Unless stated otherwise, XML specifications
   and examples provided in this document MUST be interpreted in the
   character case presented standard extension element for this object.
        Refer to develop a conforming implementation.

   This the Extensibility section discusses a small number of XML-related considerations
   pertaining to SPPP.

5.1.  Namespaces

   All this document for more
        details.

5.1.1.2.  Update Response

   An SPPP protocol update response object is contained within the generic
   <spppUpdateResponse> element.

  <element name="spppUpdateResponse">
    <complexType>
      <sequence>
        <element name="overallResult" type="spppb:ResultCodeType"/>
        <element name="rqstObjResult" type="spppb:RqstObjResultCodeType"
            minOccurs="0" maxOccurs="unbounded"/>
        <element name="clientTransId" type="spppb:TransIdType"
            minOccurs="0"/>
        <element name="serverTransId" type="spppb:TransIdType"/>
      </sequence>
    </complexType>
  </element>

  <complexType name="ResultCodeType">
    <sequence>
       <element name="code" type="int"/>
       <element name="msg" type="string"/>
    </sequence>
  </complexType>

  <complexType name="RqstObjResultCodeType">
    <complexContent>
       <extension base="spppb:ResultCodeType">
          <sequence>
             <element name="rqstObj" type="spppb:BasicRqstType"/>
          </sequence>
       </extension>

    </complexContent>
  </complexType>

   An <spppUpdateResponse> contains the elements are defined in necessary for the following namespace:
   urn:ietf:params:xml:ns:sppp:base:1

   Namespace and schema definitions are used SPPP
   client to identify both precisely determine the base
   protocol schema and overal result of the schemas for managed objects.

5.2.  Versioning

   All XML instances SHOULD begin with request, and
   if an <?xml?> declaration to
   identify error occurred, it provides information about the version of XML that specific
   object, data element, or condition caused the error.

   The data elements within the SPPP update response are described as
   follows:

   o    clientTransId: Zero or one client transaction ID.  This value is being used, optionally identify
   use
        simply an echo of the character encoding used, and optionally provide a hint to
   an XML parser client transaction ID that an external schema file SPPP client
        passed into the SPPP update request.

   o    serverTransId: Exactly one server transaction ID that identifies
        this request for tracking purposes.  This value is needed guaranteed to validate the
   XML instance.

   Conformant XML parsers recognize both UTF-8 (defined in [RFC3629])
        be unique for a given SPPP server.

   o    overallResult: Exactly one response code and UTF-16 (defined in [RFC2781]); per [RFC2277] UTF-8 is message pair that
        explicitly identifies the
   RECOMMENDED character encoding result of the request.  See the
        Response Code section for use with SPPP.

   Character encodings other than UTF-8 further details.

   o    rqstObjResult: An optional response code, response message, and UTF-16 are allowed by XML.
   UTF-8 is the default encoding assumed by XML
        BasicRqstObject triplet.  This element will be present only if
        an object level error condition occurs, and indicates exactly
        which error condition occurred and exactly which request object
        that was passed in caused the absence of error condition.  The contained
        BasicRqstObject is simply an
   "encoding" attribute or a byte order mark (BOM); thus, echo of the "encoding"
   attribute in request object instance
        that caused the XML declaration is OPTIONAL if UTF-8 encoding is
   used.  SPPP clients error, while the response code and servers MUST accept a UTF-8 BOM if present,
   though emitting a UTF-8 BOM message
        indicate the error condition for this object.  See the Response
        Code section for further details.

   o    ext: This is NOT RECOMMENDED.

   Example XML declarations:

   <?xml?> version="1.0" encoding="UTF-8" standalone="no"?>

6.  Request and Reply Model

   An SPPP client interacts with an SPPP server by using one of the
   supported transport mechanisms to send one or more requests standard extension element for this object.
        Refer to the
   server Extensibility section for more details.

5.1.2.  Query Request and receive corresponding replies from the server. Response Structures

   An SPPP query request is wrapped within the <spppRequest> <spppQueryRequest>
   element while an SPPP
   reply query response is wrapped within an <spppReply>
   <spppQueryResponse> element.  Furthermore, fully
   formed SPPP requests and replies are comprised of constructs required
   by the chosen transport technology, and the chosen envelope
   technology.  The supported transport technology and envelope
   technology specifications will be defined in separate documents, and
   are not discussed here.

6.1. following two sub-sections describe
   these two element structures.

5.1.2.1.  Query Request

   An SPPP query request object, common to any transport and envelope
   technology, object is contained within the generic <spppRequest>
   <spppQueryRequest> element.

     <element name="spppRequest">
                    <complexType>
                             <sequence>
                                      <any/>
                             </sequence>
                    </complexType>
           </element>

   Within any <spppRequest> element is the request object specific to
   the type of object(s) being operated on and the action(s) being
   performed on that object.  For example, the addRteGroupRqst object,
   used to create Route Groups, that would be passed within an
   <spppRequest> is defined as follows:

           <element name="addRteGrpsRqst"> name="spppQueryRequest">
       <complexType>
         <sequence>
           <element name="basicRqst"
                   type="spppb:BasicRqstType"/>
                 <element name="rteGrp"
                   type="spppb:RteGrpType"
                   maxOccurs="unbounded"/>
               </sequence>
              </complexType>
           </element>

   All update requests contain a BasicRqstType object.  This object is
   defined as follows:

           <complexType name="BasicRqstType">
            <sequence>
             <element name="clientTransId "
                      type="spppb:TransIdType"/>
             <element name="minorVer"
                      type="spppb:MinorVerType"/>
             <element name="ext"
                      type="spppb:ExtAnyType" type="spppb:MinorVerType"
               minOccurs="0"/>
           <element name="rqst" type="spppb:BasicQueryRqstType"/>
         </sequence>
       </complexType>

           <simpleType name="TransIdType">
               <restriction base="string"/>
           </simpleType>

           <simpleType name="MinorVerType">
               <restriction base="unsignedLong"/>
           </simpleType>
     </element>

   The data elements within the BasicRqstType object are primarily
   "house keeping" data elements.  They <spppQueryRequest> element are described
   as follows:

   o    clientTransId: The client generated transaction ID that
        identifies this request for tracking purposes.  This value is
        also echoed back to the client in the response.  This value will
        not be checked for uniqueness.

   o    minorVer: This identifies    minorVer: Zero or one minor version identifier, indicating the
        minor version of the SPPP API that the client is attempting to
        use.  This is used in conjunction with the major version
        identifier in the XML namespace.  Refer namespace to identify the Versioning section version of this document SPPP
        that the client is using.  If the element is not present, the
        server assumes that the client is using the latest minor version
        supported by the SPPP server for more detail. the given major version.  The
        versions supported by a given SPPP server can be retrieved by
        the client using the SPPP server menu operation described later
        in the document.

   o    rqst: One BasicQueryRqstType objects.  This is the query that
        the client is requesting the SPPP server perform.

   All query request objects extend the base type BasicQueryRqstType.
   This base type is defined as follows:

     <complexType name="BasicQueryRqstType" abstract="true">
       <sequence>
         <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
       </sequence>
     </complexType>

   The BasicQueryRqstType object primarily acts as an abstract base
   type, and its only data element is described as follows:

   o    ext: This is the standard extension element for this object.
        Refer to the Extensibility section of this document for more
        details.

6.2.  Reply

5.1.2.2.  Query Response

   An SPPP reply object, common to any transport and envelope
   technology, query response object is contained within the generic <spppReply>
   <spppQueryResponse> element.

     <element name="spppReply"> name="spppQueryResponse">
       <complexType>
         <sequence>
                                      <any/>
           <element name="overallResult" type="spppb:ResultCodeType"/>
           <element name="resultSet" type="spppb:BasicObjType"
              minOccurs="0" maxOccurs=" unbounded"/>
         </sequence>
       </complexType>
     </element>

   Within any <spppReply> element is

   An <spppQueryResponse> contains the reply object containing elements necessary for the SPPP
   client to precisely determine the overal result of the request.  All create, update, query, and delete operations
   result in a common response object structure, defined as follows:

          <element name="cmnRspns">
             <complexType>
                <sequence>
                   <element name="rspns" type="spppb:BasicRspnsType"/>
                </sequence>
             </complexType>
          </element>

           <complexType name="BasicRspnsType">
             <sequence>
              <element name="clientTransId"
                           type="TransIdType"/>
              <element name="serverTransId"
                           type="TransIdType"/>
              <element name="resCode"
                           type="int"/>
              <element name="resMsg"
                           type="string"/>
              <element name="ext"
                           type="spppb:ExtAnyType"
                           minOccurs="0"/>
             </sequence>
                                   </complexType> if
   an error occurred, exactly what condition caused the error.

   The data elements within the BasicRspnseType object SPPP query response are described as
   follows:

   o    clientTransId: The echoed back client transaction ID that
        explicitly identifies this request for tracking purposes.  This
        value is not guaranteed to be unique.

   o    serverTransId: The server transaction ID that identifies this
        request for tracking purposes.  This value is guaranteed to be
        unique.

   o    resCode: The    overallResult: Exactly one response code and message pair that
        explicitly identifies the result of the request.  See the
        Response Code section for further details.

   o    resMsg:    resultSet: The human readable response message set of zero or more objects that accompanies the
        response code.  See matched the Response Code section for further
        details.

   o    ext: This is
        query criteria.  If no objects matched the standard extension element for query criteria then
        this object.
        Refer to result set MUST be empty and the Extensibility section overallResult value MUST
        indicate success (if no matches are found for more details.

7. the query
        criteria, the response is considered a success).

5.2.  Response Codes and Messages

   This section contains an initial the listing of response codes and their
   corresponding human readable human-readable text.

   The response code numbering scheme generally adheres to the theory
   formalized in section 4.2.1 of [RFC2821]:

   o    The first digit of the response code can only be 1 or 2: 1 = a
        positive result, 2 = a negative result.

   o    The second digit of the response code indicates the category: 0
        = Protocol Syntax, 1 = Implementation Specific Business Rule, 2
        = Security, 3 = Server System.

   o    The third and fourth digits of the response code indicate the
        individual message event within the category defines by the
        first two digits.

   +--------+----------------------------------------------------------+

   The response codes are also categorized as to whether they are
   overall response codes that may only be returned in the
   "overallResult" data element in SPPP responses, of object level
   response codes that may only be returned in the "rqstObjResult"
   element of the SPPP responses.

   +--------+--------------------------+-------------------------------+
   | Result | Text                     | Overall or Object Level       |
   | Code   |                          |
   +--------+----------------------------------------------------------+                               |
   +--------+--------------------------+-------------------------------+
   | 1000   | Request Succeeded.       | Overall Response Code         |
   |        |                          |                               |
   | 2001   | Request syntax invalid.  | Overall Response Code         |
   |        |                          |                               |
   | 2002   | Request too large.       | Overall Response Code         |
   |        |                          |                               |
   | 2003   | Version not supported.   | Overall Response Code         |
   |        |                          |                               |
   | 2103   | Command invalid.         | Overall Response Code         |
   |        |                          |                               |
   | 2301   | System temporarily       | Overall Response Code         |
   |        | unavailable.             |                               |
   |        |                          |                               |
   | 2302   | Unexpected internal      | Overall Response Code         |
   |        | system or server error.  |                               |
   |        |                          |                               |
   | 2104   | Attribute value invalid: [ObjecTypeName]:[Object's invalid. | Object Level Response Code    |
   |        |                          |                               | rantId]:[Object's name]:{[Embedded
   |        | AttrName:[AttributeName] |                               |
   |        | AttrVal:[AttributeValue] |                               | ObjecTypeName]}:[attribute name]:[attribute value].
   |        |                          |                               |
   | 2105   | Object does not exist: [ObjecTypeName]:[Object's exist.   | Object Level Response Code    |
   |        | AttrName:[AttributeName] |                               |
   |        | AttrVal:[AttributeValue] |                               | rantId]:[Object's name].
   |        |                          |                               |
   | 2106   | Object status or ownership does not allow for operation: |         | Object Level Response Code    | [OperationName]:[ObjecTypeName]:[Object's
   |        | ownership does not allow | rantId]:[Object's name].                               |
   |        | for operation.           |                               | 2301
   | System temporarily unavailable.        | AttrName:[AttributeName] |                               |
   |        | 2302 AttrVal:[AttributeValue] | Unexpected internal system or server error.                               |
   +--------+----------------------------------------------------------+
   +--------+--------------------------+-------------------------------+

           Table 1: Response Codes Numbering Scheme and Messages

   Some

   Each of the object level response messages are "parameterized" with one or more of
   the following parameters: "attribute name", "attribute value",
   "objectType-objectId", "AttributeName" and "operation name". "AttributeValue".

   The use of these parameters MUST adhere to the following rules:

   o    All parameters within a response message are mandatory and MUST
        be present.  Parameters within a response message MUST NOT be
        left empty.

   o    Any value provided for the "attribute name" parameter MUST be an
        exact element name of "AttributeName" parameter MUST be an
        exact XSD element name of the protocol data element that the
        response message is referring to.  For example, valid values for
        "attribute name" are "dgName", "rteGrpName", "rteRec", etc.

   o    The value for "AttributeValue" MUST be the value of the data
        element to which the preceding "AttributeName" refers.

   o    Result code 2104 SHOULD be used whenever an element value does
        not adhere to data validation rules.

   o    Result codes 2104 and 2105 MUST NOT be used interchangeably.
        Response code 2105 SHOULD be returned by an update operation
        when the data element(s) used to uniquely identify a pre-
        existing object do not exist.  If the data elements used to
        uniquely identify an object are malformed, then response code
        2104 SHOULD be returned.

5.3.  Basic Object Type and Organization Identifiers

   This section introduces the basic object type that most first class
   objects derive from.

   All first class objects extend the basic object type BasicObjType
   which contains the identifier of the registrant organization that
   owns this object, the identifier of the registrar organization that
   provisioned this object, the date and time that the object was
   created by the server, and the date and time that the object was last
   modified.

     <complexType name="BasicObjType" abstract="true">
       <sequence>
         <element name="rantId" type="spppb:OrgIdType"/>
         <element name="rarId" type="spppb:OrgIdType"/>
         <element name="crtDate" type="dateTime" minOccurs="0"/>
         <element name="modDate" type="dateTime" minOccurs="0"/>
         <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
       </sequence>
     </complexType>

   The identifiers used for registrants (rantId), registrars (rarId) and
   peering organizations (peeringOrg) are instances of OrgIdType.  The
   OrgIdType is defined as a string and all OrgIdType instances SHOULD
   follow the textual convention: "namespace:value" (for example "iana-
   en:32473").  See the IANA Consideration section for more details.

6.  Protocol Commands

   This section provides a description of each supported protocol
   command.

6.1.  Add Route Group Operation

   As described in the introductory sections, a Route Group represents a
   combined grouping of Route Records that define route information,
   Destination Groups that contain a set of Public Identifiers with
   common routing information, and the list of peer organizations that
   have access to these public identifiers using this route information.
   It is this indirect linking of public identifiers to their route
   information that significantly improves the scalability and
   manageability of the peering data.  Additions and changes to routing
   information are reduced to a single operation on a Route Group or
   Route Record , rather than millions of data updates to individual
   public identifier records that individually contain their peering
   data.

   The AddRteGrpRqstType operation creates or overwrites a Route Group
   object.  If a Route Group with the given name and registrant ID
   (which together comprise the unique key or a Route Group) does not
   exist, then the server MUST create the Route Group.  If a Route Group
   with the given name and registrant ID does exist, then the server
   MUST replace the current properties of the Route Group with the
   properties passed into the AddRteGrpRqstType operation.  The XSD
   declarations of the AddRteGrpRqstType operation request object are as
   follows:

     <complexType name="AddRteGrpRqstType">
       <complexContent>
         <extension base="spppb:BasicRqstType">
           <sequence>
             <element name="rteGrp" type="spppb:RteGrpType"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

   The element passed into the spppUpdateRequest element for this
   operation is an instance of AddRteGrpRqstType, which extends
   BasicRqstType and contains one RteGrpType object.  The RteGrpType
   object structure is defined as follows:

    <complexType name="RteGrpType">
      <complexContent>
       <extension base="spppb:BasicObjType">
         <sequence>
           <element name="rteGrpName" type="spppb:ObjNameType"/>
           <element name="rteRecRef" type="spppb:RteRecRefType"
             minOccurs="0" maxOccurs="unbounded"/>
           <element name="dgName" type="spppb:ObjNameType" minOccurs="0"
             maxOccurs="unbounded"/>
           <element name="peeringOrg" type="spppb:OrgIdType"
             minOccurs="0" maxOccurs="unbounded"/>
           <element name="sourceIdent" type="spppb:SourceIdentType"
             minOccurs="0" maxOccurs="unbounded"/>
           <element name="isInSvc" type="boolean"/>
           <element name="priority" type="unsignedShort"/>
           <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
         </sequence>
       </extension>
      </complexContent>
    </complexType>

    <complexType name="RteRecRefType">
      <sequence>
        <element name="rteRec" type="spppb:ObjKeyType"/>
        <element name="priority" type="unsignedShort"/>
        <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
      </sequence>
    </complexType>

   The RteGrpType object is composed of the following elements:

   o    base: All first class objects extend BasicObjType which contains
        the ID of the registrant organization that owns this object, the
        ID of the registrar organization that provisioned this object,
        the date and time that the object was created by the server, and
        the date and time that the object was last modified.  If the
        client passes in either the created date or the modification
        date, the server will ignore them.  The server sets these two
        date/time values.

   o    rteGrpName: The character string that contains the name of the
        Route Group.  It uniquely identifies this object within the
        context of the registrant ID (a child element of the base
        element as described above).

   o    rteRecRef: Set of zero or more objects of type RteRecRefType
        that house the unique keys of the Route Records that the the
        RteGrpType object refers to and their relative priority within
        the context of a given route group.  The associated Route
        Records contain the routing information, sometimes called SED,
        associated with this Roue Group.

   o    dgName: Set of zero or more names of DestGrpType object
        instances.  Each dgName name, in association with this Route
        Group's registrant ID, uniquely identifies a DestGrpType object
        instance whose public identifiers are reachable using the
        routing information housed in this Route Group.  An intended
        side affect of this is that a Route Group cannot provide routing
        information for a Destination Group belonging to another
        registrant.

   o    peeringOrg: Set of zero or more peering organization IDs that
        have accepted an offer to receive this Route Group's
        information.  The set of peering organizations in this list is
        not directly settable or modifiable using the addRteGrpsRqst
        operation.  This set is instead controlled using the route offer
        and accept operations.

   o    sourceIdent: Set of zero or more SourceIdentType object
        instances.  These objects, described further below, house the
        source identification schemes and identifiers that are applied
        at resolution time as part of source based routing algorithms
        for the Route Group.

   o    isInSvc: A boolean element that defines whether this Route Group
        is in service.  The routing information contained in a Route
        Group that is in service is a candidate for inclusion in
        resolution responses for public identities residing in the
        Destination Group associated with this Route Group.  The routing
        information contained in a Route Group that is not in service is
        not a candidate for inclusion in resolution responses.

   o    priority: Zero or one priority value that can be used to provide
        a relative value weighting of one Route Group over another.  The
        manner in which this value is used, perhaps in conjunction with
        other factors, is a matter of policy.

   o    ext: Point of extensibility described in a previous section of
        this document.

   As described above, the Route Group contains a set of references to
   route record objects.  A route record object is based on an abstract
   type: RteRecType.  The concrete types that use RteRecType as an
   extension base are NAPTRType, NSType, and URIType.  The definitions
   of these types are included the Route Record section of this
   document.

   The RteGrpType object provides support for source-based routing via
   the peeringOrg data element and more granular source base routing via
   the source identity element.  The source identity element provides
   the ability to specify zero or more of the following in association
   with a given Route Group: a regular expression that is matched
   against the resolution client IP address, a regular expression that
   is matched against the root domain name(s), and/or a regular
   expression that is matched against the calling party URI(s).  The
   result will be that, after identifying the visible Route Groups whose
   associated Destination Group(s) contain the lookup key being queried
   and whose peeringOrg list contains the querying organizations
   organization ID, the resolution server will evaluate the
   characteristics of the Source URI, and Source IP address, and root
   domain of the lookup key being queried.  The resolution server then
   compares these criteria against the source identity criteria
   associated with the Route Groups.  The routing information contained
   in Route Groups that have source based routing criteria will only be
   included in the resolution response if one or more of the criteria
   matches the source criteria from the resolution request.  The Source
   Identity data element is of type SourceIdentType, whose structure is
   defined as follows:

     <complexType name="SourceIdentType">
       <sequence>
         <element name="sourceIdentLabel" type="string"/>
         <element name="sourceIdentScheme"
           type="spppb:SourceIdentSchemeType"/>
         <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
       </sequence>
     </complexType>

     <simpleType name="SourceIdentSchemeType">
       <restriction base="token">
         <enumeration value="uri"/>
         <enumeration value="ip"/>
         <enumeration value="rootDomain"/>
       </restriction>
     </simpleType>

   The SourceIdentType object is composed of the following data
   elements:

   o    sourceIdentScheme: The source identification scheme that this
        source identification criteria applies to and that the
        associated sourceIdentRegex should be matched against.

   o    sourceIdentRegex: The regular expression that should be used to
        test for a match against the portion of the resolution request
        that is dictated by the associated sourceIdentScheme.

   o    ext: Point of extensibility described in a previous section of
        this document.

   As with the responses to all update operations, the result of the
   AddRteGrpRqstType operation is contained in the generic
   spppUpdateResponse data structure described in an earlier sections of
   this document.  For a detailed description of the spppUpdateResponse
   data structure refer to that section of the document.

6.2.  Get Route Groups Operation

   The getRteGrpsRqst operation allows a client to get the properties of
   Route Group objects that a registrar organization is authorized to
   view.  The server will attempt to find a Route Group object that has
   the registrant ID and route group name pair contained in each
   ObjKeyType object instance.  If the set of ObjKeyType objects is
   empty then the server will return the list of Route Group objects
   that the querying client has the authority to view.  If there are no
   matching Route Groups found then an empty result set will be
   returned.

   The element passed into the spppQueryRequest element for this
   operation is an instance of type GetRteGrpsRqstType, which extends
   BasicRqstType and contains zero or more ObjKeyType objects.  Any
   limitation on the maximum number of objects that may be passed into
   or returned by this operation is a policy decision and not limited by
   the protocol.  The XSD declaration of the operation is as follows:

     <complexType name="GetRteGrpsRqstType">
       <complexContent>
         <extension base="spppb:BasicQueryRqstType">
           <sequence>
             <element name="objKey" type="spppb:ObjKeyType"
               minOccurs="0" maxOccurs="unbounded"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

   As described in an earlier section of this document, the result of
   any spppQueryRequest operation is an spppQueryResponse element that
   contains the overall response code and the query result set, if any.
   Refer to that section of the document for a detailed description of
   the spppQueryResponse element.

6.3.  Add Destination Group Operation

   As described in the introductory sections, a Destination Group
   represents a set of Public Identifiers with common routing
   information.

   The AddDestGrpRqstType operation creates or overwrites a Destination
   Group object.  If a Destination Group with the given name and
   registrant ID (which together comprise the unique key for a
   Destination Group) does not exist, then the server MUST create the
   Destination Group.  If a Destination Group with the given name and
   registrant ID does exist, then the server MUST replace the current
   properties of the Destination Group with the properties passed into
   the AddDestGrpsRqstType operation.  The XSD declarations of the
   operation request object are as follows:

     <complexType name="AddDestGrpRqstType">
       <complexContent>
         <extension base="spppb:BasicRqstType">
           <sequence>
             <element name="destGrp" type="spppb:DestGrpType"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

   The element passed into the spppUpdateRequest element for this
   operation is an element of type AddDestGrpRqsttype, which extends
   BasicRqstType and contains a DestGrpType object.  The DestGrpType
   object structure is defined as follows:

     <complexType name="DestGrpType">
       <complexContent>
        <extension base="spppb:BasicObjType">
         <sequence>
            <element name="dgName" type="spppb:ObjNameType"/>
         </sequence>
        </extension>
       </complexContent>
     </complexType>

   The DestGrpType object is composed of the following elements:

   o    base: All first class objects extend BasicObjType which contains
        the ID of the registrant organization that owns this object, the
        ID of the registrar organization that provisioned this object,
        the date and time that the object was created by the server, and
        the date and time that the object was last modified.  If the
        client passed in either the created date or the modification
        date, the server will ignore them.  The server sets these two
        date/time values.

   o    dgName: The character string that contains the name of the
        Destination Group.  This uniquely identifies this object within
        the context of the registrant ID (a child element of the base
        element as described above).

   o    ext: Point of extensibility described in a previous section of
        this document.

   As with the responses to all update operations, the result of the
   AddDestGrpRqstType operation is contained in the generic
   spppUpdateResponse data structure described in an earlier sections of
   this document.  For a detailed description of the spppUpdateResponse
   data structure refer to that section of the document.

6.4.  Get Destination Groups Operation

   The getDestGrpsRqst operation allows a client to get the properties
   of Destination Group objects that a registrar organization is
   authorized to view.  The server will attempt to find a Destination
   Group object that has the registrant ID and destination group name
   pair contained in each ObjKeyType object instance.  If there are no
   matching Destination Groups found then an empty result set will be
   returned.  If the set of ObjKeyType objects passed in is empty then
   the server will return the list of Destination Group objects that the
   querying registrar has the authority to view.

   The element passed into the spppQueryRequest element for this
   operation is an instance of type GetDestGrpsRqstType, which extends
   BasicQueryRqstType and contains zero or more ObjKeyType objects.  Any
   limitation on the maximum number of objects that may be passed into
   or returned by this operation is a policy decision and not limited by
   the protocol.  The XSD declaration of the operation is as follows:

     <complexType name="GetDestGrpsRqstType">
       <complexContent>
         <extension base="spppb:BasicQueryRqstType">
           <sequence>
             <element name="objKey" type="spppb:ObjKeyType"
               minOccurs="0" maxOccurs="unbounded"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

   As described in an earlier section of this document, the result of
   any spppQueryRequest operation is an spppQueryResponse element that
   contains the overall response code and the query result set, if any.
   Refer to that section of the document for a detailed description of
   the spppQueryResponse element.

6.5.  Add Route Group Offer Operation

   The list of peer organizations whose resolution responses can include
   the routing information contained in a given Route Group is
   controlled by the organization to which a Route Group object belongs
   (its registrant), and the peer organization that submits resolution
   requests (a data recipient, also know as a peering organization).
   The registrant offers access to a Route Group by submitting a Route
   Group Offer.  The data recipient can then accept or reject that
   offer.  Not until access to a Route Group has been offered and
   accepted will the data recipient's organization ID be included in the
   peeringOrg list in a Route Group object, and that Route Group's
   peering information become a candidate for inclusion in the responses
   to the resolution requests submitted by that data recipient.  The
   AddRteGrpOffersRqstType operation creates or overwrites one or more
   Route Group Offer objects.  If a Route Group Offer for the given
   Route Group object key and the offeredToOrg ID does not exist, then
   the server creates the Route Group Offer object.  If a such a Route
   Group Offer does exist, then the server replaces the current object
   with the new object.  The XSD declarations of the operation request
   object are as follows:

     <complexType name="AddRteGrpOfferRqstType">
       <complexContent>
         <extension base="spppb:BasicRqstType">
           <sequence>
             <element name="rteGrpOffer" type="spppb:RteGrpOfferType"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

   The element passed into the spppUpdateRequest element for this
   operation is an instance of AddRteGrpOfferRqstType, which extends
   BasicRqstType and contains a RteGrpOfferType object.  The XSD
   declaration of the RteGrpOfferType is as follows:

   <complexType name="RteGrpOfferType">
    <complexContent>
      <extension base="spppb:BasicObjType">
        <sequence>
          <element name="rteGrpOfferKey"
                   type="spppb:RteGrpOfferKeyType"/>
          <element name="status" type="spppb:RteGrpOfferStatusType"/>
          <element name="offerDateTime" type="dateTime"/>
          <element name="acceptDateTime" type="dateTime" minOccurs="0"/>
          <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
        </sequence>
      </extension>
     </complexContent>
   </complexType>

   <complexType name="RteGrpOfferKeyType">
     <sequence>
       <element name="rteGrpKey" type="spppb:ObjKeyType"/>
       <element name="offeredTo" type="spppb:OrgIdType"/>
     </sequence>
   </complexType>

   <simpleType name="RteGrpOfferStatusType">
     <restriction base="token">
       <enumeration value="offered"/>
       <enumeration value="accepted"/>
     </restriction>
   </simpleType>
   The RteGrpOfferType object is composed of the following elements:

   o    base: All first class objects extend BasicObjType which contains
        the ID of the registrant organization that owns this object, the
        ID of the registrar organization that provisioned this object,
        the date and time that the object was created by the server, and
        the date and time that the object was last modified.  If the
        client passed in either the created date or the modification
        date, the protocol data element will ignore them.  The server sets these two date/time
        values.

   o    rteGrpOfferKey: The object that identifies the
        response message route that is referring to.  For example, valid values for
        "attribute name" are "destGrpName", "rteGrpName", etc.

   o    A value provided for or
        has been offered and the "command/request type" parameter MUST
        be an exact request object name organization that the response message it is
        referring or has been
        offered to.  For example,  The combination of these three data elements
        uniquely identify a valid value for "request object
        name" is "delRteGrpsRqst". Route Group Offer.

   o    status: The value for "attribute value" MUST be status of the offer, offered or accepted.  This
        status is controlled by the server.  It is automatically set to
        "offered" when ever a new Route Group Offer is added, and is
        automatically set to "accepted" if and when that offer is
        accepted.  The value of the data element to which is ignored when passed in by
        the preceding "attribute name" refers. client.

   o    Result code 2104 SHOULD be used whenever an element value does
        not adhere to data validation rules.    offerDateTime: Date and time in GMT when the Route Group Offer
        was added.

   o    Result codes 2104    acceptDateTime: Date and 2105 MUST NOT be used interchangeably.
        Response code 2105 SHOULD be returned time in GMT when the data element(s)
        used to uniquely identify a pre-existing object do not exist.
        If Route Group Offer
        was accepted.

   As with the data elements used responses to uniquely identify an object are
        malformed, then response code 2104 SHOULD be returned.

8.  Protocol Commands

   This section provides a preliminary list all update operations, the result of the
   AddRteGrpOfferRqstType operation is contained in the generic
   spppUpdateResponse data structure described in an earlier sections of SPPP protocol commands.
   At
   this early stage document.  For a detailed description of the protocol development, spppUpdateResponse
   data structure refer to that section of the commands are
   only listed with a brief description.

8.1.  Add document.

6.6.  Accept Route Group Offer Operation

   As described in the introductory sections,

   Not until access to a Route Group represents a
   combined grouping of Route Records that define route information,
   Destination Groups that contain a set of Public Identifiers with
   common routing information, has been offered and accepted will
   the data recipient's organization ID will it be included in the
   peeringOrg list of peer organizations that
   have access to these public identifiers using this route information.
   It is this indirect linking of public identities to route information in that significantly improves the scalability Route Group object, and manageability of the that Route Group's
   peering data.  Additions and changes to routing information are
   reduced to a single operation on become a Route Group, rather than millions
   of data updates candidate for inclusion in the responses
   to individual public identity records the resolution requests submitted by that
   individually contain their peering point data. data recipient.  The addRteGrpsRqst
   AcceptRteGrpOffersRqstType operation creates or overwrites one is called by, or more on behalf of,
   the data recipient to accept a Route Group objects. Offer that is pending in
   the "offered" status for the data recipient's organization ID.  If a
   Route Group with Offer for the given name and Route Group Offer key (route name,
   route registrant
   ID does not exist, ID, data recipient's organization ID) exists, then
   the server MUST create moves the Route Group.  If a
   Route Group with Offer to the given name "accepted" status and registrant
   adds that data recipient's organization ID into the list of
   peerOrgIds for that Route Group.  If a such a Route Group Offer does
   not exist, then the server MUST replace the current properties of the Route Group with
   the properties passed into returns the addRteGrpsRqst operation. appropriate error code, 2105.
   The XSD declarations of for the operation request object are as follows:

       <element name="addRteGrpsRqst" type="spppb:AddRteGrpsRqstType"/>

<complexType name="AddRteGrpsRqstType"> name="AcceptRteGrpOfferRqstType">
  <complexContent>
    <extension base="spppb:BasicRqstType">
      <sequence>
        <element name="rteGrp" type="spppb:RteGrpType"
                                               maxOccurs="unbounded"/> name="rteGrpOfferKey" type="spppb:RteGrpOfferKeyType"/>
      </sequence>
    </extension>
  </complexContent>
</complexType>

   The element passed into the spppRequest spppUpdateRequest element for this
   operation is
   the addRteGrpsRqst element.  This element is an instance of type
   AddRteGrpsRqstType, AcceptRteGrpOffersRqstType, which extends
   BasicRqstType and contains one or
   more RteGrpType objects.  Any limitation on a RteGrpOfferKeyType object.

   As with the maximum number responses to all update operations, the result of
   RteGrpType objects that may be passed into this the
   AcceptRteGrpOfferRqstType operation is a policy
   decision and is not limited by contained in the protocol.  The RteGrpType object generic
   spppUpdateResponse data structure is defined as follows:

       <complexType name="RteGrpType">
         <sequence>
           <element name="base" type="spppb:BasicObjType"/>
           <element name="rteGrpName" type="spppb:ObjNameType"/>
           <element name="rteRec" type="spppb:RteRecType"
                           minOccurs="0" maxOccurs="unbounded"/>
           <element name="dgName" type="spppb:ObjNameType"
                           minOccurs="0" maxOccurs="unbounded"/>
           <element name="peeringOrg" type="spppb:OrgIdType"
                           minOccurs="0" maxOccurs="unbounded"/>
           <element name="sourceIdent" type="spppb:SourceIdentType"
                           minOccurs="0" maxOccurs="unbounded"/>
           <element name="isInSvc" type="boolean"/>
                   <element name="ext" type="spppb:ExtAnyType"
   s="0"/>
         </sequence>
       </complexType>

   The RteGrpType object is composed of the following elements:

   o    base: As described in previous sections, most objects contain
        exactly one instance of BasicObjType which contains the ID an earlier sections of
        the registrant organization that owns
   this object and the ID document.  For a detailed description of the registrar organization that provisioned this object.

   o    rteGrpName: The character string spppUpdateResponse
   data structure refer to that contains the name section of the document.

6.7.  Reject Route Group.  It uniquely identifies this object within the
        context of Group Offer Operation

   The data recipient to which a Route Group has been offered has the registrant ID (a child element
   option of the base
        element as described above).

   o    rteRec: Set rejecting a Route Group Offer.  Furthermore, that offer may
   be rejected, regardless of zero whether or not it has been previously
   accepted.  The RejectRteGrpOffersRqstType operation is used for these
   purposes and is called by, or more objects of type RteRecType that
        house on behalf of, the routing information, sometimes referred data recipient to as SED,
   accept a Route Group Offer that is pending in the RteGrpType object contains.

   o    dgName: Set of zero "offered" status or more names of DestGrpType object
        instances.  Each dgName name,
   is in association with this Route
        Group's registrant ID, uniquely identifies the "accepted" status for the data recipient's organization ID.
   If a DestGrpType object
        instance whose public identities are reachable using Route Group Offer for the routing
        information housed in this given Route Group.

   o    peeringOrg: Set of zero or more peering Group Offer key (route
   name, route registrant ID, data recipient's organization IDs that
        have accepted an offer to receive this Route Group's
        information.  The set of peering organizations ID) exists
   in this list is
        not directly settable or modifiable using the addRteGrpsRqst
        operation.  This set is instead controlled using either the route offer
        and accept operations.

   o    sourceIdent: Set of zero offered or more SourceIdentType object
        instances.  These objects, described further below, house accepted status, then the
        source identification schemes and identifiers server deletes
   that are applied
        at resolution time as part Route Group Offer object, and, if appropriate, removes the data
   recipients organization ID from the list of source based routing algorithms peeringOrg IDs for the that
   Route Group.

   o    isInSvc: A boolean element that defines whether this  If the Route Group
        is in service. Offer does not exist, then the
   server returns the appropriate error code, 2105.  The routing information contained in a Route
        Group that is in service XSD
   declarations for the operation request object are as follows:

<complexType name="RejectRteGrpOfferRqstType">
  <complexContent>
    <extension base="spppb:BasicRqstType">
      <sequence>
        <element name="rteGrpOfferKey" type="spppb:RteGrpOfferKeyType"/>
      </sequence>
    </extension>
  </complexContent>
</complexType>

   The element passed into the spppUpdateRequest element for this
   operation is an instance of RejectRteGrpOffersRqstType, which extends
   BasicRqstType and contains a candidate for inclusion in
        resolution RteGrpOfferKeyType object.

   As with the responses for public identities residing in to all update operations, the
        Destination Group associated with this Route Group.  The routing
        information contained in a Route Group that result of the
   RejectRteGrpOfferRqstType operation is not contained in service is
        not a candidate for inclusion is resolution responses.

   o    ext: Point of extensibility the generic
   spppUpdateResponse data structure described in a previous section an earlier sections of
   this document.

   As described above,  For a detailed description of the spppUpdateResponse
   data structure refer to that section of the document.

6.8.  Get Route Group contains Offers Operation

   The getRteGrpOffersRqst operation allows a set client to get the
   properties of route record
   objects.  A route record object zero or more Route Group Offer objects that registrar
   is based on an abstract type:
   RteRecType. authorized to view.  The concrete types server will attempt to find Route Group
   Offer objects that use RteRecType as an extension
   base are NAPTRType, NSType, and URIType.  The definitions of these
   types are included below.  The NAPTRType object is comprised of have all the
   data elements necessary for a NAPTR that contains routing information properties specified in the Route Group.  The NSType object criteria
   passed into the operation.  If no criteria is comprised of passed in then the data elements
   necessary for a Name Server that points to another DNS
   server will return the list of Route Group Offer objects that
   contains the desired routing information.
   querying client has the authority to view.  If there are no matching
   Route Group Offers found then an empty result set will be returned.

   The URIType object element passed into the spppQueryRequest element for this
   operation is
   comprised an instance of GetRteGrpOffersRqstType, which extends
   BasicQueryRqstType and contains the data elements necessary to house a URI.

   The data provisioned in a Registry can criteria that the returned Route
   Group Offer objects must match.  Any limitation on the maximum number
   of objects that may be leveraged for many purposes
   and queried using various protocols including SIP, ENUM and others.
   It is for returned by this reason that a route record type offers operation is a choice of
   URI, policy
   decision and DNS resource record types.  The URIType is commonly used to
   provision data related to not limited by the SIP route in registries. protocol.  The use XSD declaration of
   DNS resource record types is also relevant to the scenario where the
   data provisioned in the registry
   operation is used to answer ENUM queries but
   the provisioning protocol should be agnostic to a particular
   resolution protocol.

       <complexType name="RteRecType" abstract="true">
         <sequence>
           <element name="priority" type="positiveInteger"
                                               default="100"/>
         </sequence>
       </complexType>

       <complexType name="NAPTRType">
         <complexContent>
           <extension base="spppb:RteRecType">
             <sequence>
               <element name="order" type="unsignedShort"/>
               <element name="pref" type="unsignedShort"/>
               <element name="flags" type="string" minOccurs="0"/>
               <element name="svcs" type="string"/>
               <element name="regx" type="spppb:RegexParamType"
                                               minOccurs="0"/>
               <element name="repl" type="string" minOccurs="0"/>
               <element name="ttl" type="positiveInteger"
                                               minOccurs="0"/>
               <element name="ext" type="spppb:ExtAnyType"
                                               minOccurs="0"/>
             </sequence>
           </extension>
         </complexContent>
       </complexType> as follows:

   <complexType name="NSType"> name="GetRteGrpOffersRqstType">
     <complexContent>
       <extension base="spppb:RteRecType">
             <sequence>
               <element name="hostName" type="string"/>
               <element name="ipAddr" type="spppb:IPAddrType"
                       minOccurs="0" maxOccurs="unbounded"/>
               <element name="ttl" type="positiveInteger"
                                               minOccurs="0"/>
               <element name="ext" type="spppb:ExtAnyType"
                                               minOccurs="0"/>
             </sequence>
           </extension>
         </complexContent>
       </complexType>

       <complexType name="IPAddrType"> base="spppb:BasicQueryRqstType">
         <sequence>
           <element name="addr" type="string"/>
           <element name="type" type="spppb:IPType"/>
           <element name="ext" type="spppb:ExtAnyType" name="offeredByPeers" type="boolean" minOccurs="0"/>
         </sequence>
       </complexType>
       <simpleType name="IPType">
         <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" name="offeredToPeers" type="boolean" minOccurs="0"/>
           <element name="status" type="spppb:RteGrpOfferStatusType"
             minOccurs="0"/>
           <element name="peeringOrg" type="spppb:OrgIdType"
             minOccurs="0" maxOccurs="unbounded"/>
           <element name="rteGrpOfferKey"
             type="spppb:RteGrpOfferKeyType" minOccurs="0"
             maxOccurs="unbounded"/>
         </sequence>
       </extension>
     </complexContent>
   </complexType>

   The NAPTRType GetRteGrpOffersRqstType object is composed of the following
   elements:

   o    order: Order    offeredByPeers: Zero or one boolean value that, if true,
        indicates that only offers that are offered by peering
        organizations to the querying registrant should be included in an ENUM NAPTR, relative
        the result set.  If this value is false, the offers by peering
        organizations to the querying registrant should not be included
        in the result set.  The result set is also subject to other NAPTRType
        objects
        query criteria in the same Route Group. request.

   o    pref: Preference    offeredToPeers: Zero or one boolean value in an ENUM NAPTR.

   o    svcs: ENUM service(s) that, if true,
        indicates that only offers that are served offered to peering
        organizations by the SBE.  This field's
        value must querying registrant should be of the form specified included in RFC 3761 (e.g., E2U+
        pstn:sip+sip).  The allowable values are a matter of policy and
        not limited by this protocol.

   o    regx: NAPTR's regular expression field.
        the result set.  If this value is false, the offers to peering
        organizations by the querying registrant should not be included
        then
        in the Repl field must be included. result set.  The result set is also subject to other
        query criteria in the request.

   o    repl: NAPTR replacement field,    status: The status of the offer, offered or accepted.  Only
        offers in the specified status should only be provided if included in the
        Regex field result
        set.  If this element is not provided, otherwise it will be ignored by present then the
        server.

   o    ttl: Number of seconds that an addressing server may cache this
        NAPTR.

   o    ext: Point status of extensibility described the
        offer should not be considered in a previous section of
        this document. the query.  The NSType object result set is composed of the following elements:

   o    hostName: Fully qualified host name of
        also subject to other query criteria in the name server. request.

   o    ipAddr:    peeringOrg: 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 organization IDs.  Only offers that an addressing server may cache this
        Name Server.

   o    ext: Point of extensibility described are
        offered to or offered by the organization IDs in a previous section of this document. list
        should be included in the result set.  The URIType object result set is composed of also
        subject to other query criteria in the following elements: request.

   o    ere:    rteGrpOfferKey: Zero or more Route Group Offer Keys.  Only
        offers having one of these keys should be included in the result
        set.  The POSIX Extended Regular Expression (ere) as defined result set is also subject to other query criteria in
        [RFC3986]

   o    uri:
        the URI as defined request.

   As described in [RFC3986]

   The RteGrpType object provides support for source-based routing via an earlier section of this document, the source identity element.  The source-based routing criteria
   provides result of
   any spppQueryRequest operation is an spppQueryResponse element that
   contains the ability overall response code and the query result set, if any.
   Refer to specify zero or more that section of the following in
   association with a given Route Group: document for a regular expression that detailed description of
   the spppQueryResponse element.

6.9.  Public Identifier Operations

   Public Identifier is
   matched against the resolution client IP address, a regular
   expression that search key used for locating the session
   establishment data (SED).  In many cases, a Public Identifier is matched against
   attributed to the root domain name(s), and/or end user who has a
   regular expression that is matched against retail relationship with the calling party URI(s).
   The result will
   service provider or registrant organization.  In SPPP, SED can be that, after identifying
   provisioned by the visible Route Groups
   whose associated Destination Group(s) contain registrant, or by the lookup key being
   queried, registrar on behalf of the resolution server will evaluate
   registrant.  Also, SPPP supports the characteristics notion of the Source URI, and Source IP address, and root domain of carrier-of-record
   as defined in RFC 5067.  Therefore, the lookup
   key being queried.  The resolution server compares these criteria
   against source based routing criteria associated with entity adding the Route
   Groups.  The routing information contained in Route Groups that have
   source based routing criteria will only be included Public
   Identity in the resolution
   response if one or more Registry can optionally claim to be a carrier-of-
   record.

   SPPP identifies three types of Public Identifiers: telephone number
   (TN), email address, and the criteria matches routing number (RN).  SPPP also supports
   the source criteria
   from requirement of adding a contiguous range of TNs including the resolution request.

      <complexType name="SourceIdentType">
        <sequence>
          <element name="sourceIdentRegex" type="string"/>
          <element name="sourceIdentScheme"
                                    type="spppb:SourceIdentSchemeType"/>
          <element name="ext" type="spppb:ExtAnyType"
                                              minOccurs="0"/>
        </sequence>
      </complexType>

      <simpleType name="SourceIdentSchemeType">
        <restriction base="token">
          <enumeration value="uri"/>
          <enumeration value="ip"/>
          <enumeration value="rootDomain"/>
        </restriction>
      </simpleType>
   length variance associated to the Open Number Plan.

   The SourceIdentType object XML schema type definition PubIDType is composed the generalization of the following data
   elements:

   o    sourceIdentScheme: The source identification scheme that this
        source identification criteria applies to and that
   Public Identifier.  PubIDType is an abstract type.  In agreement with
   the
        associated sourceIdentRegex should be matched against.

   o    sourceIdentRegex: The regular expression that should be used to
        test for a match against data model, PubIDType member 'dgName' represents the portion name of the resolution request
   destination group that a given Public Identifier is dictated by the associated sourceIdentScheme.

   o    ext: Point of extensibility described in a previous section of
        this document. to.
   The result of the addRteGrpsRqst operation PubIDType object structure is the addRteGrpsRspns
   element defined below.  As as follows:

  <complexType name="PubIdType" abstract="true">
    <complexContent>
     <extension base="spppb:BasicObjType">
       <sequence>
         <element name="dgName" type="spppb:ObjNameType" minOccurs="0"/>
       </sequence>
     </extension>
    </complexContent>
  </complexType>

   A registrant can add a Public Identifier with all SPPP requests, the result help of a
   BasicRqstType called AddPubIdRqstType.  To complete the add request,
   AddPubIdRqstType XML instance is all-
   or-nothing. added to <spppUpdateRequest> root
   element.  If more than one RteRecType there is passed into this request,
   then they will either all succeed or all fail.  In a conflict and a Public Identifier already
   exists in the case of
   failure, Registry, the failure response code(s) and message(s) old entry will indicate be replaced with the reason for newly
   provisioned entry.  For the failure and add or update operation, the object(s) that caused destination
   group name is a mandatory parameter.  Not including a valid
   destination group name in the failure.

   <element name="addRteGrpsRspns" type="spppb:BasicRspnsType"/>

   The response codes that update request will cause the addRteGrpsRqst operation can Registry
   to return are
   as follows:

   o    1000: Request Succeeded.

   o    2001: Request syntax invalid.

   o    2002: Request too large.

   o    2003: Version not supported.

   o    2103: Command invalid.

   o    2104: Attribute value invalid.

   o    2105: Object does not exist.

   o    2106: Object status or ownership does not allow for request. an appropriate error.

   Telephone number is identified by TNType, an extension of PubIDType.
   TNType is composed of the following attributes:

   o    2301: System temporarily unavailable.    tn: Telephone number to be added to the Registry.

   o    2302: Unexpected internal system or server error.

8.2.  Get Route Groups Operation

   The getRteGrpsRqst operation    rteRecRef: Optional reference to the route record that is
        directly associated with the TN Public Identifier.  Following
        the SPPP data model, the route record could be a protocol
        agnostic URIType or another type.

   o    corInfo: corInfo is an optional parameter of type CORInfoType
        that allows the registrant organization to set forth a client claim to get
        be the properties of
   Route Group objects that a registrar organization carrier-of-record [see RFC 5067].  This is authorized done by
        setting the <corClaim> element of the CORInfoType object
        structure to
   view. true.  The server will attempt to find a Route Group object that has other two parameters of the registrant ID CORInfoType,
        <cor> and route group name pair contained in each
   ObjKeyType object instance.  If the <corDateTime> are meant to be set by the Registry to
        relay the outcome of ObjKeyType objects is
   empty then the server will return carrier-of-record claim by the list
        registrant.  In general, inclusion of Route Group objects
   that <corInfo> parameter is
        useful if the querying client Registry has the authority information, such as,
        the number portability, etc., in order to view.  If there are no
   matching Route Groups found then an empty result set will qualify whether the
        registrant claim can be
   returned.

   The element passed into satisfied.  If the spppRequest element for this operation is carrier-of-record
        claim disagrees with the getRteGrpsRqst element.  This element is authority data of type
   GetRteGrpsRqstType, which extends BasicRqstType and contains zero or
   more ObjKeyType objects.  Any limitation on the maximum number of
   objects that may be passed into or returned by this Registry, whether
        the TN add operation fails or not is a matter of policy decision and not limited by it
        is beyond the protocol.  The XSD declaration scope of this document.  In the operation is as follows:

        <element name="getRteGrpsRqst" type="spppb:GetRteGrpsRqstType"/>

       <complexType name="GetRteGrpsRqstType">
         <complexContent>
           <extension base="spppb:BasicRqstType">
             <sequence>
               <element name="objectKey" type="spppb:ObjKeyType"
                               minOccurs="0" maxOccurs="unbounded"/>
             </sequence>
           </extension>
         </complexContent>
       </complexType>

   The result of response message
        <spppUpdateResponse>, the getRteGrpsRqst operation returned in SPPP Server must include the
   spppResponse element is <cor>
        parameter of the getRteGrpsRspns <corInfo> element defined below.
   This object contains to let the resulting set of RteGrpType objects, or an
   empty set if there were no matches.

       <element name="getRteGrpsRspns"
   type="spppb:GetRteGrpsRspnsType"/> registrant know
        the outcome of the claim.

   TNType object definition is as follows:

     <complexType name="GetRteGrpsRspnsType"> name="TNType">
       <complexContent>
         <extension base="spppb:BasicRspnsType"> base="spppb:PubIdType">
           <sequence>
             <element name="rteGrp" type="spppb:RteGrpType" name="tn" type="string"/>
             <element name="rteRecRef" type="spppb:RteRecRefType"
                minOccurs="0" maxOccurs="unbounded"/>
             <element name="corInfo" type="spppb:CORInfoType"
                minOccurs="0"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

   The response codes that the getRteGrpsRqst operation can return are
   as follows:

   o    1000: Request Succeeded.

   o    2001: Request syntax invalid.

   o    2002: Request too large.

   o    2003: Version not supported.

   o    2103: Command invalid.

   o    2104: Attribute value invalid.

   o    2301: System temporarily unavailable.

   o    2302: Unexpected internal system or server error.

8.3.  Add Route Group Offers Operation

   The list of peer organizations whose resolution responses can include
   the routing information contained in a given Route Group

   Routing number is
   controlled identified by the organization to which a Route Group object belongs,
   its registrant, and the peer organization RNType.  SSPs that submits resolution
   requests, a possess the number
   portability data recipient or peering organization.  The registrant
   offers access may be able to a Route Group by submitting a Route Group Offer and leverage the data recipient can then accept or reject that offer.  Not until
   access RN search key to a Route Group has been offered and accepted will
   discover the data
   recipient's ingress routes for session establishment.  Therefore,
   the registrant organization ID be included in can add the peeringOrg list in a
   Route Group object, RN and that Route Group's peering associate it with the
   appropriate destination group to share the route information.

   RNType is composed of the following attributes:

   o    rn: Routing Number used as the search key

   o    corInfo: Optional <corInfo> element of type CORInfoType.

   RNType object information become is as follows:

     <complexType name="RNType">
       <complexContent>
         <extension base="spppb:PubIdType">
           <sequence>
             <element name="rn" type="string" default="true"/>
             <element name="corInfo" type="spppb:CORInfoType"
                  minOccurs="0"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

   A contiguous range of TNs is added with the help of TNRType.  This
   object type includes an optional "prefix" attribute to indicate that
   a candidate given TN range qualifies for inclusion in the responses Open Number Plan (ONP).  In order
   to correctly expand the resolution requests
   submitted by number range that data recipient.  The addRteGrpOffersRqst operation
   creates or overwrites one or more Route Group Offer objects.  If a
   Route Group Offer qualifies for Open Number
   Plan, the given Route key (route name and registrant
   ID) and offeredToOrg ID does not exist, then Registry must have the server creates required data about the
   Route Group Offer national
   significant number length for the TN prefix included in the TN range
   object.  If the Registry encounters an error in adding even a such single
   TN that is part of the TN range, the whole request will be deemed a Route Group Offer does exist,
   then
   failure.  In other words, the server replaces TNRType add request is transactional in
   nature, and the current object with partial success case is not supported.

   TNRType is composed of the new object. following attributes:

   o    endTn: The
   XSD declarations last number in the TN range

   o    corInfo: Optional <corInfo> element of type CORInfoType.

   o    prefix: Optional attribute, when set to "true", indicates that
        the operation request included TN Range falls under the Open Number Plan.

   TNRange object are structure is as follows:

     <complexType name="TNRType">
       <complexContent>
         <extension base="spppb:TNType">
           <sequence>
             <element name="endTn" type="string"/>
             <element name="addRteGrpOffersRqst"
                                  type="spppb:AddRteGrpOffersRqstType"/> name="corInfo" type="spppb:CORInfoType"
                minOccurs="0"/>
           </sequence>
           <attribute name="prefix" type="boolean" default="false" />
         </extension>
       </complexContent>
     </complexType>

   The object structure of AddPubIdRqstType used to add Public
   Identifiers is as follows

     <complexType name="AddRteGrpOffersRqstType"> name="AddPubIdRqstType">
       <complexContent>
         <extension base="spppb:BasicRqstType">
           <sequence>
             <element name="rteGrpOffer" type="spppb:RteGrpOfferType"
                                                 maxOccurs="unbounded"/> name="pi" type="spppb:PubIdType"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

   The element passed into client can set the spppRequest element for this operation is GetPubIdsRqstType in the addRteGrpOffersRqst element.  This element is of type
   AddRteGrpOffersRqstType, which extends BasicRqstType and contains <spppQueryRequest>
   structure to obtain information about one or more RteGrpOfferType objects.  Any limitation on the maximum
   number of <pi> objects that may be passed into or returned by this
   operation is a policy decision
   were successfully provisioned earlier and that the calling entity is
   privileged to see.  If the GetPubIdsRqstType object does not limited include
   <pi> data, then all authorized Public Identity data will be returned
   by the protocol.  The
   XSD declaration of Registry in the operation response.  If no matching Public Identifiers
   are found, then an empty result set will be returned.

   GetPubIdsRqstType object structure is as follows:

     <complexType name="RteGrpOfferType">
      <sequence>
        <element name="base" type="spppb:BasicObjType"/>
        <element name="rteGrpOfferKey" type="spppb:RteGrpOfferKeyType"/>
        <element name="status" type="spppb:RteGrpOfferStatusType"/>
        <element name="offerDateTime" type="dateTime"/>
        <element name="acceptDateTime" type="dateTime" minOccurs="0"/>
        <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
      </sequence>
    </complexType>
       <complexType name="RteGrpOfferKeyType"> name="GetPubIdsRqstType">
       <complexContent>
         <extension base="spppb:BasicQueryRqstType">
           <sequence>
             <element name="rteGrpKey" type="spppb:ObjKeyType"/>
        <element name="offeredTo" type="spppb:OrgIdType"/> name="pi" type="spppb:PubIdType" minOccurs="0"
               maxOccurs="unbounded"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

    <simpleType name="RteGrpOfferStatusType">
      <restriction base="token">
        <enumeration value="offered"/>
        <enumeration value="accepted"/>
      </restriction>
    </simpleType>

   The RteGrpOfferType object is composed of the following elements:

   o    base:

   As described in previous sections, most objects contain
        exactly one instance of BasicObjType which contains the ID an earlier section of
        the registrant organization that owns this object and document, the ID result of
        the registrar organization that provisioned this object.

   o    rteGrpOfferKey: The object
   any spppQueryRequest operation is a spppQueryResponse that identifies contains
   the route that is or
        has been offered response code and the organization that it is or has been
        offered to.  The combination of these three data elements
        uniquely identify a query result set, if any.

6.10.  Egress Route Group Offer.

   o    status: Operations

   The status of the offer, offered or accepted.  This
        status is controlled by the server.  It is automatically set to
        "offered" when ever egress route add operation allows a new Route Group Offer is added, and is
        automatically set call originating SSP to "accepted" if and when that offer is
        accepted.  The value of the element is ignored when passed in by
        the client.

   o    offerDateTime: Date and time
   define a preferred egress route in GMT when an attempt to reach the Route Group Offer
        was added.

   o    acceptDateTime: Date and time in GMT when ingress
   SBE of the Route Group Offer
        was accepted. target SSP.  The result of addRteGrpOffersRqst need arises when there is a choice of
   egress SBE and an SSP wants to exercise greater control in deciding
   how to route the addRteGrpOffersRspns element
   defined below. outbound session establishment request.

   As with all SPPP requests, the result is all-or-
   nothing.  If more than one RteGrpOfferType a first step, it is passed into this
   request, then they will either all succeed or all fail.  In assumed that the case target SSP has offered to
   share the route group that consists of failure, the failure response code(s) ingress route information
   to the SBE(s) and message(s) will indicate the reason for originating SSP has accepted the offer.  Next,
   the originating SSP can add the egress route in the Registry, with
   appropriate regular expression, to rewrite ingress route information
   from the failure target SSP and include the object(s) that caused egress SBE information.  In high-
   availability configurations, the failure.

     <element name="addRteGrpOffersRspns" type="spppb:BasicRspnsType"/>

   The response codes that originating SSP will likely add a
   secondary egress route object re-writing the addRteGrpOffersRqst operation can return
   are same ingress route from
   the target SSP with a secondary choice of egress SBE as follows:

   o    1000: Request Succeeded.

   o    2001: Request syntax invalid.

   o    2002: Request too large.

   o    2003: Version not supported.

   o    2103: Command invalid.

   o    2104: Attribute a backup.  In
   this case, the backup egress route definition will carry the higher
   integer value invalid.

   o    2105: Object does not exist.

   o    2106: Object status or ownership does not allow for request.

   o    2301: System temporarily unavailable.

   o    2302: Unexpected internal system or server error.

8.4.  Accept Route Group Offers Operation

   Not until access the "pref" parameter to indicate a Route Group has been offered lower priority.

   An egress route is identified by type EgrRteType and accepted will its object
   structure is shown below:

    <complexType name="EgrRteType">
      <complexContent>
       <extension base="spppb:BasicObjType">
         <sequence>
           <element name="egrRteName" type="spppb:ObjNameType"/>
           <element name="pref" type="unsignedShort"/>
           <element name="regxRewriteRule" type="spppb:RegexParamType"/>
           <element name="ingrRteRec" type="spppb:ObjKeyType"
              minOccurs="0" maxOccurs="unbounded"/>
           <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
         </sequence>
       </extension>
      </complexContent>
    </complexType>

   The EgrRteType object is composed of the data recipient's following elements:

   o    base: All first class objects extend BasicObjType which contains
        the ID of the registrant organization that owns this object, the
        ID be included in of the peeringOrg
   list in registrar organization that Route Group provisioned this object,
        the date and time that Route Group's peering
   information become a candidate for inclusion in the responses to the
   resolution requests submitted object was created by that data recipient.The
   acceptRteGrpOffersRqst operation is called by, or on behalf of, the
   data recipient to accept one or more Route Group Offers that are
   pending in server, and
        the "offered" status for date and time that the data recipient's organization
   ID. object was last modified.  If a Route Group Offer for the given Route Group Offer key
   (route name, route registrant ID, data recipient's organization ID)
   exists, then
        client passes in either the server moves created date or the Route Group Offer to modification
        date, the "accepted"
   status and adds that data recipient's organization ID into server will ignore them.  The server sets these two
        date/time values.

   o    egrRteName: The name of the list egress route.

   o    pref: The preference of peerOrgIds for this egress route relative to other
        egress routes that Route Group.  If a such may get selected when responding to a Route Group Offer
   does not exist, then
        resolution request.

   o    regxRewriteRule: The regular expression re-write rule that
        should be applied to the server returns regular expression of the appropriate error code
   2105. ingress
        NAPTR(s) that belong to the ingress route.

   o    ingrRteRec: The XSD declarations for ingress route records that the operation egress route
        should be used for.

   o    ext: Point of extensibility described in a previous section of
        this document.

   The AddEgrRteRqstType request object are as
   follows:

      <element name="acceptRteGrpOffersRqst"
                               type="spppb:AcceptRteGrpOffersRqstType"/> is used to create or overwrite an
   egress route.

     <complexType name="AcceptRteGrpOffersRqstType"> name="AddEgrRteRqstType">
       <complexContent>
         <extension base="spppb:BasicRqstType">
           <sequence>
             <element name="rteGrpOfferKey"
                 type="spppb:RteGrpOfferKeyType" maxOccurs="unbounded"/> name="egrRte" type="spppb:EgrRteType"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

   The element passed into the spppRequest element for this operation

   An instance of AddEgrRtesRqstType is added in the acceptRteGrpOffersRqst element.  This spppUpdateRequest
   element is of type
   AcceptRteGrpOffersRqstType, which extends BasicRqstType and contains
   one or more RteGrpOfferKeyType objects. in order to send a valid request to the server.  Any
   limitation on the maximum number of objects that may be passed into or returned by this
   operation AddEgrRteRqstType instances is a
   matter of policy decision and is not limited by the protocol. specification.

   The result of acceptRteGrpOffersRqst response from the server is returned in addEgrRteRspns element,
   which is defined as the acceptRteGrpOffersRspns element defined below. of type BasicRspnsType.

   The GetEgrRtesRqstType is used by an authorized entity to fetch the
   well-known egress route data.

     <complexType name="GetEgrRtesRqstType">
       <complexContent>
         <extension base="spppb:BasicQueryRqstType">
           <sequence>
             <element name="objKey" type="spppb:ObjKeyType"
               minOccurs="0" maxOccurs="unbounded"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

6.11.  Add Route Record Operation

   As with all SPPP requests, described in the result is all-
   or-nothing.  If more than one RteGrpOfferKeyType introductory sections, a Route Group represents a
   combined grouping of Route Records that define route information.
   However, Route Records need not be created to just server a single
   Route Group.  Route Records can be created and managed to serve
   multiple Route Groups.  As a result, a change to the properties of a
   network node, for example, that is passed into this
   request, used for multiple routes, would
   necessitate just a single update operation to change the properties
   of that node.  The change would then they will either be reflected in all succeed the Route
   Groups whose route record set contains a reference to that node.

   The AddRteRecRqstType operation creates or all fail.  In overwrites a Route Record
   object.  If a Route Record with the given name and registrant ID
   (which together comprise the unique key or a Route Record) does not
   exist, then the case
   of failure, server MUST create the failure response code(s) Route Record.  If a Route
   Record with the given name and message(s) will indicate registrant ID does exist, then the reason for
   server MUST replace the failure and current properties of the object(s) that caused Route Record with
   the failure.

      <element name="acceptRteGrpOffersRspns"
                                           type="spppb:BasicRspnsType"/> properties passed into the AddRteRecRqstType operation.  The response codes that XSD
   declarations of the acceptRteGrpOffersRspns AddRteRecRqstType operation can
   return request object are as
   follows:

   o    1000: Request Succeeded.

   o    2001: Request syntax invalid.

   o    2002: Request too large.

   o    2003: Version not supported.

   o    2103: Command invalid.

   o    2104: Attribute value invalid.

   o    2105: Object does not exist.

   o    2106: Object status or ownership does not allow

     <complexType name="AddRteRecRqstType">
       <complexContent>
         <extension base="spppb:BasicRqstType">
           <sequence>
             <element name="rteRec" type="spppb:RteRecType"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

   The element passed into the spppUpdateRequest element for request.

   o    2301: System temporarily unavailable.

   o    2302: Unexpected internal system or server error.

8.5.  Reject Route Group Offers Operation

   Not until access to a Route Group has been offered this
   operation is an instance of AddRteRecRqstType, which extends
   BasicRqstType and accepted will contains one RteRecType object.  The RteRecType
   object structure is defined as follows:

  <complexType name="RteRecType" abstract="true">
    <complexContent>
      <extension base="spppb:BasicObjType">
         <sequence>
           <element name="rrName" type="spppb:ObjNameType"/>
           <element name="priority" type="unsignedShort" minOccurs="0"/>
         </sequence>
      </extension>
    </complexContent>
  </complexType>

   The RteRecType object is composed of the following elements:

   o    base: All first class objects extend BasicObjType which contains
        the data recipient's organization ID be included in of the peeringOrg
   list in registrant organization that Route Group owns this object, and that Route Group's peering
   information become a candidate for inclusion in the responses to the
   resolution requests submitted by that data recipient.  However, the
   data recipient that the Route Group has been offered to has the
   option
        ID of rejecting a Route Group Offer that has been offered but not
   accepted or the registrar organization that has been offered and accepted.  The
   rejectRteGrpOffersRqst operation is used for these purposes and is
   called by, or on behalf of, provisioned this object,
        the data recipient to accept one or more
   Route Group Offers date and time that are pending in the "offered" status or object was created by the
   "accepted" status for server, and
        the data recipient's organization ID. date and time that the object was last modified.  If a
   Route Group Offer for the given Route Group Offer key (route name,
   route registrant ID, data recipient's organization ID) exists
        client passes in either the offered created date or accepted status, then the modification
        date, the server deletes will ignore them.  The server sets these two
        date/time values.

   o    rrName: The character string that contains the name of the Route Group Offer
        Record.  It uniquely identifies this object , and, if appropriate, removes within the data
   recipients organization ID from context
        of the list registrant ID (a child element of peerOrgIds for that Route
   Group.  If the base element as
        described above).

   o    priority: Zero or one priority value that can be used to provide
        a relative value weighting of one Route Group Offer does not exist, then the server
   returns the appropriate error code 2105. Record over another.
        The XSD declarations for
   the operation request object manner in which this value is used, perhaps in conjunction
        with other factors, is a matter of policy.

   o    ext: Point of extensibility described in a previous section of
        this document.

   As described above, route records are based on an abstract type:
   RteRecType.  The concrete types that use RteRecType as follows:

      <element name="rejectRteGrpOffersRqst"
                               type="spppb:RejectRteGrpOffersRqstType"/>

      <complexType name="RejectRteGrpOffersRqstType">
        <complexContent>
          <extension base="spppb:BasicRqstType">
            <sequence>
              <element name="rteGrpOfferKey"
                 type="spppb:RteGrpOfferKeyType" maxOccurs="unbounded"/>
            </sequence>
          </extension>
        </complexContent>
      </complexType> an extension
   base are NAPTRType, NSType, and URIType.  The definitions of these
   types are included below.  The element passed into the spppRequest element for this operation is
   the rejectRteGrpOffersRqst element.  This element NAPTRType object is comprised of type
   RejectRteGrpOffersRqstType, which extends BasicRqstType and contains
   one or more RteGrpOfferKeyType objects.  Any limitation on the
   maximum number of objects
   data elements necessary for a NAPTR that may be passed into or returned by this
   operation is contains routing information
   for a policy decision and not limited by the protocol. Route Group.  The result of rejectRteGrpOffersRqst NSType object is comprised of the rejectRteGrpOffersRspns
   element defined below.  As with all SPPP requests, data
   elements necessary for a Name Server that points to another DNS
   server that contains the result is all-
   or-nothing.  If more than one RteGrpOfferKeyType desired routing information.  The URIType
   object is passed into this
   request, then they will either all succeed or all fail.  In the case comprised of failure, the failure response code(s) and message(s) will indicate the reason data elements necessary to house a URI.

   The data provisioned in a Registry can be leveraged for the failure many purposes
   and the object(s) that caused the failure.

       <element name="rejectRteGrpOffersRspns"
                                   type="spppb:BasicRspnsType"/>

   The response codes queried using various protocols including SIP, ENUM and others.
   It is for this reason that a route record type offers a choice of URI
   and DNS resource record types.  URIType fulfills the rejectRteGrpOffersRspns operation can
   return are as follows:

   o    1000: Request Succeeded.

   o    2001: Request syntax invalid.

   o    2002: Request too large.

   o    2003: Version not supported.

   o    2103: Command invalid.

   o    2104: Attribute value invalid.

   o    2105: Object does not exist.

   o    2106: Object status or ownership does not allow need for request.

   o    2301: System temporarily unavailable.

   o    2302: Unexpected internal system or server error.

8.6.  Get Route Group Offers Operation

   The getRteGrpOffersRqst operation allows both
   SIP and ENUM protocols.  When a client given URIType is associated to get a
   destination group, the
   properties user part of zero or more Route Group Offer objects the replacement string <uri> that
   may require the Public Identifier cannot be preset.  As a SIP
   Redirect, the resolution server will apply <ere> pattern on the input
   Public Identifier in the query and process the replacement string by
   substituting any back reference(s) in the <uri> to arrive at the
   final URI that
   registrar is authorized to view.  The returned in the SIP Contact header.  For an ENUM
   query, the resolution server will attempt simply return the value of the
   <ere> and <uri> members of the URIType in the NAPTR REGEX parameter.

    <complexType name="RteRecType" abstract="true">
      <sequence>
        <element name="rrName" type="spppb:ObjNameType"/>
        <element name="priority" type="unsignedShort"/>
      </sequence>
    </complexType>
    <complexType name="NAPTRType">
      <complexContent>
        <extension base="spppb:RteRecType">
          <sequence>
            <element name="order" type="unsignedShort"/>
            <element name="flags" type="string" minOccurs="0"/>
            <element name="svcs" type="string"/>
            <element name="regx" type="spppb:RegexParamType"
              minOccurs="0"/>
            <element name="repl" type="string" minOccurs="0"/>
            <element name="ttl" type="positiveInteger" minOccurs="0"/>
            <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
          </sequence>
        </extension>
      </complexContent>
    </complexType>

    <complexType name="NSType">
      <complexContent>
        <extension base="spppb:RteRecType">
          <sequence>
            <element name="hostName" type="string"/>
            <element name="ipAddr" type="spppb:IPAddrType" minOccurs="0"
              maxOccurs="unbounded"/>
            <element name="ttl" type="positiveInteger" minOccurs="0"/>
            <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
          </sequence>
        </extension>
      </complexContent>
    </complexType>

    <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>
    <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>

   The NAPTRType object is composed of the following elements:

   o    order: Order value in an ENUM NAPTR, relative to find
   Route Group Offer other NAPTRType
        objects in the same Route Group.

   o    svcs: ENUM service(s) that has all are served by the properties SBE.  This field's
        value must be of the form specified in
   the criteria passed into the operation. RFC 3761 (e.g., E2U+
        pstn:sip+sip).  The allowable values are a matter of policy and
        not limited by this protocol.

   o    regx: NAPTR's regular expression field.  If no criteria this is passed in not included
        then the server Repl field must be included.

   o    repl: NAPTR replacement field, should only be provided if the
        Regex field is not provided, otherwise it will return be ignored by the list
        server.

   o    ttl: Number of Route Group Offer objects seconds that the querying client has the authority to view.  If there are no
   matching Route Group Offers found then an empty result set will be
   returned.

   The element passed into the spppRequest element for addressing server may cache this operation is
   the getRteGrpOffersRqst element.  This element
        NAPTR.

   o    ext: Point of extensibility described in a previous section of
        this document.

   The NSType object is composed of type
   GetRteGrpOffersRqstType, which extends BasicRqstType and contains the
   criteria that following elements:

   o    hostName: Fully qualified host name of the returnedRoute Group Offer name server.

   o    ipAddr: Zero or more objects must match.  Any
   limitation on of type IpAddrType.  Each object
        holds an IP Address and the maximum number IP Address type, IPv4 or IP v6.

   o    ttl: Number of objects seconds that an addressing server may be passed into
   or returned by cache this operation is a policy decision and not limited by
   the protocol.  The XSD declaration
        Name Server.

   o    ext: Point of the operation is as follows:

      <element name="getRteGrpOffersRqst"
                                  type="spppb:GetRteGrpOffersRqstType"/>

      <complexType name="GetRteGrpOffersRqstType">
        <complexContent>
          <extension base="spppb:BasicRqstType">
            <sequence>
              <element name="offeredByPeers" type="boolean"
                                                         minOccurs="0"/>
              <element name="offeredToPeers" type="boolean"
                                                         minOccurs="0"/>
              <element name="status" type="spppb:RteGrpOfferStatusType"
                                                         minOccurs="0"/>
              <element name="peeringOrg" type="spppb:OrgIdType"
                                   minOccurs="0" maxOccurs="unbounded"/>
              <element name="rteGrpOfferKey"
  type="spppb:RteGrpOfferKeyType" minOccurs="0" maxOccurs="unbounded"/>
            </sequence>
          </extension>
        </complexContent>
      </complexType> extensibility described in a previous section of
        this document.

   The GetRteGrpOffersRqstType URIType object is composed of the following elements:

   o    offeredByPeers: Zero or one boolean value that, if true,
        indicates that only offers that are offered by peering
        organizations to the querying registrant should be included    ere: The POSIX Extended Regular Expression (ere) as defined in
        [RFC3986].

   o    uri: the result set.  If URI as defined in [RFC3986].  In some cases, this value is false, the offers by peering
        organizations to will
        serve as the querying registrant should not replacement string and it will be included
        in left to the result set.  The result set is also subject
        resolution server to other
        query criteria in arrive at the request.

   o    offeredToPeers: Zero or one boolean value that, if true,
        indicates that only offers that are offered final usable URI.

   As with the responses to peering
        organizations by all update operations, the querying registrant should be included result of the
   AddRteRecRqstType operation is contained in the result set.  If generic
   spppUpdateResponse data structure described in an earlier sections of
   this value is false, document.  For a detailed description of the offers spppUpdateResponse
   data structure refer to peering
        organizations by the querying registrant should not be included
        in that section of the result set. document.

6.12.  Get Route Records Operation

   The result set is also subject getRteRecsRqst operation allows a client to other
        query criteria in get the request.

   o    status: The status properties of
   Route Record objects that a registrar organization is authorized to
   view.  The server will attempt to find a Route Record object that has
   the offer, offered or accepted.  Only
        offers in the specified status should be included registrant ID and route record name pair contained in the result
        set. each
   ObjKeyType object instance.  If this element the set of ObjKeyType objects is not present
   empty then the status server will return the list of Route Record objects
   that the
        offer should not be considered in querying client has the query.  The authority to view.  If there are no
   matching Route Record found then an empty result set is
        also subject to other query criteria in will be
   returned.

   The element passed into the request.

   o    peeringOrg: Zero spppQueryRequest element for this
   operation is an instance of type GetRteRecsRqstType, which extends
   BasicRqstType and contains zero or more organization IDs.  Only offers ObjKeyType objects.  Any
   limitation on the maximum number of objects that are
        offered to may be passed into
   or offered returned by this operation is a policy decision and not limited by
   the organization IDs protocol.  The XSD declaration of the operation is as follows:

     <complexType name="GetRteRecsRqstType">
       <complexContent>
         <extension base="spppb:BasicQueryRqstType">
           <sequence>
             <element name="objKey" type="spppb:ObjKeyType"
               minOccurs="0" maxOccurs="unbounded"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

   As described in an earlier section of this list
        should be included in document, the result set.  The result set of
   any spppQueryRequest operation is also
        subject to other an spppQueryResponse element that
   contains the overall response code and the query criteria in result set, if any.
   Refer to that section of the request.

   o    rteGrpOfferKey: Zero or more Route Group Offer Keys.  Only
        offers having one document for a detailed description of these keys should be included in
   the result
        set.  The result set spppQueryResponse element.

6.13.  Delete Operation

   In order to remove an object from the Registry, an authorized entity
   can send the <spppUpdateRequest> to the Registry with a corresponding
   delete BasicRqstType object.  If the entity that issued the command
   is also subject not authorized to other query criteria perform this operation or if the public
   identifier doesn't exist, an appropriate error code will be returned
   in the request.

   The result of the getRteGrpOffersRqst operation returned <spppUpdateRespnonse> message.

   As an example, DelPubIdRqstType aids in identifying the
   spppResponse element Public
   Identifier that is used to delete a Public Identifier from the getRteGrpOffersRspns element defined
   below.  This
   Registry.  DelPubIdsRqstType object contains the resulting set of RteGrpOfferType
   objects, or an empty set if there were no matches.

      <element name="getRteGrpOffersRspns"
                                 type="spppb:GetRteGrpOffersRspnsType"/> definition is shown below:

     <complexType name="GetRteGrpOffersRspnsType"> name="DelPubIdRqstType">
       <complexContent>
         <extension base="spppb:BasicRspnsType"> base="spppb:BasicRqstType">
           <sequence>
             <element name="rteGrpOffer" type="spppb:RteGrpOfferType"
                                   minOccurs="0" maxOccurs="unbounded"/> name="pi" type="spppb:PubIdType"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

   The response codes that the getRteGrpOffersRqst

   Similarly, each 'Add' operation can return
   are as follows:

   o    1000: Request Succeeded.

   o    2001: Request syntax invalid.

   o    2002: Request too large.

   o    2003: Version not supported.

   o    2103: Command invalid.

   o    2104: Attribute value invalid.

   o    2301: System temporarily unavailable.

   o    2302: Unexpected internal system or server error.

8.7.  Public Identifier Operations

   Public Identifier is in the SP protocol has a well-known attribute that is
   corresponding 'Del' operation used as the
   search key to find delete the routes associated with it.  There are three
   types respective object
   type from the Registry.

7.  SPPP Examples

   This section shows XML message exchange between two SIP Service
   Providers (SSP) and a Registry.  For the sake of public identifiers defined in this document: TNType for simplicity, the
   telephone number, EmailType
   transport wrapper for the email address, and RNType for
   PSTN routing number.  Further, TNRangeType SPPP protocol is used left out.  The SPPP
   protocol messages in this section are valid XML instances that
   conform to add a range of
   telephone numbers.

8.7.1.  Add Public Identifier

   addPubIdsRqst operation is used the SPPP schema version within this document.

   In this sample use case scenario, SSP1 and SSP2 provision resource
   data in the registry and use SPPP constructs to create or overwrite one or more
   public identifier(s).  When activating a new public identifier that
   can be reached using a common set of routes, it is often selectively share the
   route groups.  In the figure below, SSP2 has two ingress SBE
   instances that are associated with a well-known destination group.  In some cases, such as the
   email public identifier, identities that SSP2
   has the routing information is unique, and
   therefore, addPubIdsRqst allows retail relationship with.  Also, the public identifier two SBE instances for
   SSP1 are used to be directly
   associated with a show how to use SPPP protocol to associate route record.

   PubIdType in the schema represents
   preferences for the public identifier and it is
   defined as an abstract type.  TNType, EmailType, destination ingress routes and RNType, exercise greater
   control on outbound traffic to the
   concrete types of PubIdType, are inputs peer's ingress SBEs.

      ---------------+                      +------------------
                     |                      |
               +---------------+     +---------------+
               | sbe1.ssp1.com |     | sbe2.ssp2.com |
               +---------------+     +---------------+
       SSP1          |                      |           SSP2
               +---------------+     +---------------+
               | sbe3.ssp1.com |     | sbe4.ssp2.com |
               +---------------+     +---------------+
        iana-en:111  |                      |     iana-en:222
      ---------------+                      +------------------
              |                                     |
              |                                     |
              | SPPP   +------------------+   SPPP  |
              +------->|     Registry     |<--------+
                       +------------------+

7.1.  Add Destination Group

   SSP2 adds a destination group to 'addPubIdRqst' operation. the Registry for use later.  The declaration
   SSP2 SPPP client sets a unique transaction identifier 'tx_7777' for
   tracking purposes.  The name of 'addPubIdsRqst' is as follows:

       <element name="addPubIdsRqst" type="spppb:AddPubIdsRqstType"/>
       <complexType name="AddPubIdsRqstType">
         <complexContent>
           <extension base="spppb:BasicRqstType">
             <sequence>
               <element name="pi" type="spppb:PubIdType"
                 maxOccurs="unbounded"/>
             </sequence>
           </extension>
         </complexContent>
       </complexType>

   For the 'addPubIdsRqst' operation to succeed, each public identifier
   should be associated with at least a valid destination group or is set to
   DEST_GRP_SSP2_1
      <?xml version="1.0" encoding="UTF-8"?>
      <spppUpdateRequest
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
       xmlns="urn:ietf:params:xml:ns:sppp:base:1">
        <clientTransId>txid-5555</clientTransId>
        <rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
          xsi:type="ns1:AddDestGrpRqstType">
          <destGrp>
            <ns1:rantId>iana-en:222</ns1:rantId>
            <ns1:rarId>iana-en:222</ns1:rarId>
            <dgName>DEST_GRP_SSP2_1</dgName>
          </destGrp>
        </rqst>
      </spppUpdateRequest>

   The Registry processes the request and return a
   valid route type as defined within favorable response
   confirming successful creation of the PubIdType definition.  If not, named destination group.  Also,
   besides returning a unique transaction identifier, Registry also
   returns the provisioning server will deem matching client transaction identifier from the request a failure and return
   message back to the SPPP client.

      <?xml version="1.0" encoding="UTF-8"?>
      <spppUpdateResponse
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
       xmlns="urn:ietf:params:xml:ns:sppp:base:1">
        <clientTransId>tx_7777</clientTransId>
        <serverTransId>tx_id_12346</serverTransId>
        <overallResult>
          <code>1000</code>
          <msg>success</msg>
        </overallResult>
      </spppUpdateResponse>

7.2.  Add Route Records

   SSP2 adds an
   appropriate failure code ingress routes in the response.

   TNType is Registry.

     <?xml version="1.0" encoding="UTF-8"?>
     <spppUpdateRequest
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
       xmlns="urn:ietf:params:xml:ns:sppp:base:1">
       <rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
         xsi:type="ns1:AddRteRecRqstType">
         <rteRec xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
           xsi:type="ns1:NAPTRType">
           <rantId>iana-en:222</rantId>
           <rarId>iana-en:222</rarId>
           <ns1:rrName>RTE_SSP2_SBE2</ns1:rrName>
           <order>10</order>
           <flags>u</flags>
           <svcs>E2U+sip</svcs>
           <regx>
             <ere>^(.*)$</ere>
             <repl>sip:\1@sbe2.ssp2.com</repl>
           </regx>
         </rteRec>
       </rqst>
     </spppUpdateRequest>

   The Registry returns a concrete public identifier that extends PubIdType
   definition.  If success response.

     <?xml version="1.0" encoding="UTF-8"?>
     <spppUpdateResponse
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
       xmlns="urn:ietf:params:xml:ns:sppp:base:1">
       <serverTransId>tx_id_11145</serverTransId>
       <overallResult>
         <code>1000</code>
         <msg>Request successful</msg>
       </overallResult>
     </spppUpdateResponse>

7.3.  Add Route Records -- URIType

   SSP2 adds another ingress routes in the Registry and makes use of
   URIType
   <?xml version="1.0" encoding="UTF-8"?>
   <spppUpdateRequest
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
     xmlns="urn:ietf:params:xml:ns:sppp:base:1">
     <rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
       xsi:type="ns1:AddRteRecRqstType">
       <rteRec xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
         xsi:type="ns1:URIType">
         <rantId>iana-en:222</rantId>
         <rarId>iana-en:222</rarId>
         <ns1:rrName>RTE_SSP2_SBE4</ns1:rrName>
         <ns1:ere>^(.*)$</ns1:ere>
         <ns1:uri>sip:\1;npdi@sbe4.ssp2.com</ns1:uri>
       </rteRec>
     </rqst>
   </spppUpdateRequest>

   The Registry returns a success response.

     <?xml version="1.0" encoding="UTF-8"?>
     <spppUpdateResponse
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
       xmlns="urn:ietf:params:xml:ns:sppp:base:1">
       <serverTransId>tx_id_11145</serverTransId>
       <overallResult>
         <code>1000</code>
         <msg>Request successful</msg>
       </overallResult>
     </spppUpdateResponse>

7.4.  Add Route Group

   SSP2 creates the entity provisioning grouping of the telephone ingress routes and choses higher
   precedence for RTE_SSP2_SBE2 by setting a lower number is for the
   carrier
   "priority" attribute, a protocol agnostic precedence indicator.

     <?xml version="1.0" encoding="UTF-8"?>
     <spppUpdateRequest
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
       xmlns="urn:ietf:params:xml:ns:sppp:base:1">
       <rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
         xsi:type="ns1:AddRteGrpRqstType">
         <rteGrp>
           <rantId>iana-en:222</rantId>
           <rarId>iana-en:222</rarId>
           <rteGrpName>RTE_GRP_SSP2_1</rteGrpName>
           <ns1:rteRecRef>
             <ns1:rteRec>
               <ns1:rantId>iana-en:222</ns1:rantId>
               <ns1:name>RTE_SSP2_SBE2</ns1:name>
             </ns1:rteRec>
             <ns1:priority>100</ns1:priority>
           </ns1:rteRecRef>
           <dgName>DEST_GRP_SSP2_1</dgName>
           <isInSvc>true</isInSvc>
           <ns1:priority>10</ns1:priority>
         </rteGrp>
       </rqst>
     </spppUpdateRequest>

   To confirm successful processing of record [see RFC 5067], then it SHOULD include the
   'corClaim' element with this request, Registry returns a value 'true'.  If the SPPP server records
   disagree with
   well-known resolution code '1000' to the SSP2 client.

     <?xml version="1.0" encoding="UTF-8"?>
     <spppUpdateResponse
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
       xmlns="urn:ietf:params:xml:ns:sppp:base:1">
       <serverTransId>tx_id_12345</serverTransId>
       <overallResult>
         <code>1000</code>
         <msg>Request successful</msg>
       </overallResult>
     </spppUpdateResponse>

7.5.  Add Public Identity -- Successful COR claim of the provisioning entity, an
   appropriate failure response MUST be returned.

     <complexType name="PubIdType" abstract="true">
       <sequence>
         <element name="base" type="spppb:BasicObjType"/>
         <element name="dgName" type="spppb:ObjNameType" minOccurs="0"/>
         <element name="rteRec" type="spppb:RteRecType" minOccurs="0"
           maxOccurs="unbounded"/>
       </sequence>
     </complexType>
     <complexType name="TNType">
       <complexContent>
         <extension base="spppb:PubIdType">
           <sequence>
             <element name="tn" type="string"/>
             <element name="corClaim" type="spppb:CORInfoType"
               minOccurs="0"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

   For added flexibility, there is support to add

   SSP2 activates a range of telephone
   numbers and associate them TN public identity by associating it with a valid
   destination group.  TNRType extends
   TNType and adds the 'endTn' attribute to mark  Further, SSP2 puts forth a claim that it is the end of
   carrier-of-record for the range.
   In TN.

     <?xml version="1.0" encoding="UTF-8"?>
     <spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
       <clientTransId>txid-5577</clientTransId>
       <rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
         xsi:type="ns1:AddPubIdRqstType">
         <pi xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
           xsi:type="ns1:TNType">
           <ns1:rantId>iana-en:222</ns1:rantId>
           <ns1:rarId>iana-en:222</ns1:rarId>
           <ns1:crtDate>2010-05-30T09:30:10Z</ns1:crtDate>
           <ns1:dgName>DEST_GRP_SSP2_1</ns1:dgName>
           <tn>+12025556666</tn>
           <ns1:corInfo>
             <ns1:corClaim>true</ns1:corClaim>
           </ns1:corInfo>
         </pi>
       </rqst>
     </spppUpdateRequest>

   Assuming that the TNRType context, Registry has access to TN authority data and it
   performs the extended 'tn' attribute required checks to verify that SSP2 is used for in fact the
   starting TN
   service provider of a given telephone number range.

       <complexType name="TNRType">
         <complexContent>
           <extension base="spppb:TNType">
             <sequence>
               <element name="endTn" type="string"/>
             </sequence>
           </extension>
         </complexContent>
       </complexType>

   The element passed into the spppRequest element record for this operation is the addPubIdsRqst element.  This element is of type
   AddPubIdsRqstType, which extends BasicRqstType and contians one or
   more PubIdType objects.  Any limitation on given TN, the maximum number of
   PubIdType objects that may request was
   processed successfully. <cor> element confirms SSP2 claim to be passed into this operatoin is a policy
   decision and is not limited by the protocol.

   The response from
   carrier of record has been accepted and the server processing time is returned in addPubIdsRspns
   reflected by <corDateTime> data element.

     <?xml version="1.0" encoding="UTF-8"?>
     <spppUpdateResponse
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
       xmlns="urn:ietf:params:xml:ns:sppp:base:1">
       <clientTransId>txid-5577</clientTransId>
       <serverTransId>tx_id_12345</serverTransId>
       <overallResult>
         <code>1000</code>
         <msg>success</msg>
       </overallResult>
       <rqstObjResult>
         <code>1000</code>
         <msg>success</msg>
         <rqstObj xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
           xsi:type="ns1:AddPubIdRqstType">
             <pi xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
               xsi:type="ns1:TNType">
               <ns1:rantId>iana-en:222</ns1:rantId>
               <ns1:rarId>iana-en:222</ns1:rarId>
               <ns1:crtDate>2010-05-30T09:30:10Z</ns1:crtDate>
               <ns1:dgName>DEST_GRP_SSP2_1</ns1:dgName>
               <tn>+12025556666</tn>
               <ns1:corInfo>
                 <ns1:corClaim>true</ns1:corClaim>
                 <ns1:cor>true</ns1:cor>
                 <ns1:corDateTime>2006-05-04T18:13:51.0Z
                                          </ns1:corDateTime>
               </ns1:corInfo>
             </pi>
         </rqstObj>
       </rqstObjResult>
     </spppUpdateResponse>

7.6.  Add LRN

   If more than one public identifiers are passed in another entity that SSP2 shares the addPubIdsRqst,
   then routes with has access to
   Number Portability data, it may choose to perform route lookups by
   routing number.  Therefore, SSP2 associates a failure routing number to add one will result a
   destination group in the failure of addPubIdsRqst
   operation.  If the 'transactional' attribute is set order to 'true' in facilitate ingress route discovery.

     <?xml version="1.0" encoding="UTF-8"?>
     <spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
       <rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
         xsi:type="ns1:AddPubIdRqstType">
         <pi xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
           xsi:type="ns1:RNType">
           <rantId>rantId0</rantId>
           <rarId>rarId0</rarId>
           <ns1:dgName>DEST_GRP_SSP2_1</ns1:dgName>
           <rn>2025550000</rn>
         </pi>
       </rqst>
     </spppUpdateRequest>

   Registry completes the
   root element spppRequest and more than one operation request elements
   are included, then a failure of any one operation will result in the
   overall failure of spppRequest.  In the case of successfully and returns a failure, the favorable
   response code(s) and message(s) will indicate to the reason SPPP client.

     <?xml version="1.0" encoding="UTF-8"?>
     <spppUpdateResponse
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
       xmlns="urn:ietf:params:xml:ns:sppp:base:1">
       <serverTransId>tx_id_12345</serverTransId>
       <overallResult>
         <code>1000</code>
         <msg>Request successful</msg>
       </overallResult>
     </spppUpdateResponse>

7.7.  Add TN Range

   Next, SSP2 activates a block of failure.

   <element name="addRteGrpsRspns" type="spppb:BasicRspnsType"/>

   The response codes that the addRteGrpsRqst operation can return are
   as follows:

   o    1000: Request Succeeded.

   o    2001: Request syntax invalid.

   o    2002: Request too large.

   o    2003: Version not supported.

   o    2103: Command invalid.

   o    2104: Attribute value invalid.

   o    2105: Object does not exist.

   o    2106: Object status or ownership does not allow for request.

   o    2301: System temporarily unavailable.

   o    2302: Unexpected internal system or server error.

8.7.2.  Get Public Identifier

   The getPubIdsRqst can be used by an authorized entity ten thousand TNs and associate it to obtain
   a destination group.  Since the
   properties of one or more public identifiers.  In case of an
   authorization failure or if no matching 'prefix' public identifiers are found,
   an appropriate failure code will be returned.

   To make a successful query, getPubIdsRqst element identity attribute is
   not set within to 'true', this means that the
   spppRequest root element. getPubIdsRqst is TNs belong to a closed number
   plan.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
       xsi:type="ns1:AddPubIdRqstType">
       <pi xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
         xsi:type="ns1:TNRType">
         <rantId>iana-en:222</rantId>
         <rarId>iana-en:222</rarId>
         <ns1:dgName>DEST_GRP_SSP2_1</ns1:dgName>
         <tn>+12026660000</tn>
         <endTn>+12026669999</endTn>
       </pi>
     </rqst>
   </spppUpdateRequest>

   Registry completes the request successfully and returns a favorable
   response.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppUpdateResponse
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
     xmlns="urn:ietf:params:xml:ns:sppp:base:1">
     <serverTransId>tx_id_12244498</serverTransId>
     <overallResult>
       <code>1000</code>
       <msg>Request successful</msg>
     </overallResult>
   </spppUpdateResponse>

7.8.  Add TN Range with Open Number Plan support

   In this case, open number plan refers to TN length variance.
   Inclusion of type GetPubIdsRqstType,
   which extends from the common BasicRqstType.

         <element name="getPubIdsRqst" type="spppb:GetPubIdsRqstType"/>
         <complexType name="AddPubIdsRqstType">
           <complexContent>
             <extension base="spppb:BasicRqstType">
               <sequence>
                 <element name="pi" type="spppb:PubIdType"
                   maxOccurs="unbounded"/>
               </sequence>
             </extension>
           </complexContent>
         </complexType>

   The result "prefix" attribute of TNRType with its value set to true
   indicates that the getPubIdsRqst operation returned in start TN range identified by the
   spppResponse <tn> element is
   not necessarily a subscriber number and the getPubIdsRspns element of type
   GetPubIdsRspnsType.  If the matching record is found, getPubIdsRspns
   element Registry will include one or more pi elements with destination group
   name and/or the route record associations.

       <element name="getPubIdsRspns" type="spppb:GetPubIdsRspnsType"/>
       <complexType name="GetPubIdsRspnsType">
         <complexContent>
           <extension base="spppb:BasicRspnsType">
             <sequence>
               <element name="pi" type="spppb:PubIdType" minOccurs="0"
                 maxOccurs="unbounded"/>
             </sequence>
           </extension>
         </complexContent>
       </complexType>

   The response codes that have to
   consult the addRteGrpsRqst operation can return are
   as follows:

   o    1000: Request Succeeded.

   o    2001: Request syntax invalid.

   o    2002: Request too large.

   o    2003: Version not supported.

   o    2103: Command invalid.

   o    2104: Attribute value invalid.

   o    2105: Object does not exist.

   o    2106: Object status or ownership does not allow number plan data for request.

   o    2301: System temporarily unavailable.

   o    2302: Unexpected internal system or server error.

8.7.3.  Delete Public Identifier

   In order the respective country to remove know how
   to expand the public identifier, an authorized entity can
   use number range. <endTn> attribute marks the delPubIdsRqst operation.  If end of the entity that issued TN
   range.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
       xsi:type="ns1:AddPubIdRqstType">
       <pi xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
         xsi:type="ns1:TNRType" prefix="true">
         <rantId>iana-en:222</rantId>
         <rarId>iana-en:222</rarId>
         <ns1:dgName>DEST_GRP_SSP2_1</ns1:dgName>
         <tn>+4312315566</tn>
         <endTn>+4312315567</endTn>
       </pi>
     </rqst>
   </spppUpdateRequest>

   Registry completes the
   command is not authorized request successfully and returns a favorable
   response.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppUpdateResponse
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
     xmlns="urn:ietf:params:xml:ns:sppp:base:1">
     <serverTransId>tx_id_12255598</serverTransId>
     <overallResult>
       <code>1000</code>
       <msg>Request successful</msg>
     </overallResult>
   </spppUpdateResponse>

7.9.  Enable Peering -- Route Group Offer

   In order for SSP1 to perform this operation or if complete session establishment for a destination
   TN where the public
   identifier doesn't exist, target subscriber has a retail relationship with SSP2,
   it first requires an appropriate error code will be returned
   in asynchronous bi-directional handshake to show
   mutual consent.  To start the response.

   delPubIdsRqst element is set in process, SSP2 initiates the peering
   handshake by offering SSP1 access to its route group.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
       xsi:type="ns1:AddRteGrpOfferRqstType">
       <rteGrpOffer>
         <rantId>iana-en:222</rantId>
         <rarId>iana-en:222</rarId>
         <rteGrpOfferKey>
           <rteGrpKey>
             <rantId>iana-en:222</rantId>
             <name>RTE_GRP_SSP2_1</name>
           </rteGrpKey>
           <offeredTo>iana-en:111</offeredTo>
         </rteGrpOfferKey>
         <status>offered</status>
         <offerDateTime>2006-05-04T18:13:51.0Z</offerDateTime>
       </rteGrpOffer>
     </rqst>
   </spppUpdateRequest>

   Registry completes the request successfully and confirms that the root spppRequest element.
   delPubIdsRqst element is of type DelPubIdsRqstType as shown below:

       <element name="getPubIdsRqst" type="spppb:GetPubIdsRqstType"/>
       <complexType name="DelPubIdsRqstType">
         <complexContent>
           <extension base="spppb:BasicRqstType">
             <sequence>
               <element name="pi" type="spppb:PubIdType"
                 maxOccurs="unbounded"/>
             </sequence>
           </extension>
         </complexContent>
       </complexType>

   The result of
   SSP1 will now have the delPubIdsRqst operation returned opportunity to weigh in on the
   spppResponse element offer and
   either accept or reject it.  The Registry may employ out-of-band
   notification mechanisms for quicker updates to SSP1 so they can act
   faster, though this topic is beyond the getPubIdsRspns element scope of type
   GetPubIdsRspnsType.

       <element name="delPubIdsRspns" type="spppb:BasicRspnsType"/>

8.8.  Egress this document.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppUpdateResponse
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
     xmlns="urn:ietf:params:xml:ns:sppp:base:1">
     <serverTransId>tx_id_12277798</serverTransId>
     <overallResult>
       <code>1000</code>
       <msg>Request successful</msg>
     </overallResult>
   </spppUpdateResponse>

7.10.  Enable Peering -- Route Operations

   This section describes Group Offer Accept

   SSP1 responds to the operations related offer from SSP2 and agrees to egress have visibility to
   SSP2 ingress routes.  In
   this version, egress routes are only defined for route records of
   NAPTR type (future versions may expand

   <?xml version="1.0" encoding="UTF-8"?>
   <spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
       xsi:type="ns1:AcceptRteGrpOfferRqstType">
       <rteGrpOfferKey>
         <rteGrpKey>
           <rantId>iana-en:222</rantId>
           <name>RTE_GRP_SSP2_1</name>
         </rteGrpKey>
         <offeredTo>iana-en:111</offeredTo>
       </rteGrpOfferKey>
     </rqst>
   </spppUpdateRequest>

   Registry confirms that the request has been processed successfully.
   From this notion to URI types).

   The egress route functionality allows point forward, if SSP1 looks up a call originating SSP to
   define its egress route in an attempt to reach public identity through
   the ingress SBE of query resolution server, where the
   target SSP.  In some cases, public identity is part of the call originating SSP has more than
   one choice
   destination group by way of egress SBEs and intends "RTE_GRP_SSP2_1" route association, SSP2
   ingress SBE information will be shared with SSP1.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppUpdateResponse
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
     xmlns="urn:ietf:params:xml:ns:sppp:base:1">
     <serverTransId>tx_id_12333798</serverTransId>
     <overallResult>
       <code>1000</code>
       <msg>success</msg>
     </overallResult>
   </spppUpdateResponse>

7.11.  Add Egress Route

   SSP1 wants to selectively use one of these prioritize all outbound traffic to routes associated
   with "RTE_GRP_SSP2_1" route elements for call termination group through "sbe1.ssp1.com".

   <?xml version="1.0" encoding="UTF-8"?>
   <spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <clientTransId>tx_9000</clientTransId>
     <rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
       xsi:type="ns1:AddEgrRteRqstType">
       <egrRte>
         <rantId>iana-en:111</rantId>
         <rarId/>
         <egrRteName>EGR_RTE_01</egrRteName>
         <pref>50</pref>
         <regxRewriteRule>
           <ere>^(.*@)(.*)$</ere>
           <repl>\1\2?route=sbe1.ssp1.com</repl>
         </regxRewriteRule>
         <ns1:ingrRteRec>
           <ns1:rantId>iana-en:222</ns1:rantId>
           <ns1:name>SSP2_RTE_REC_3</ns1:name>
         </ns1:ingrRteRec>
       </egrRte>
     </rqst>
   </spppUpdateRequest>

   Since peering has already been established, the request to add the target SSP.

   An
   egress route simply allows an organization has been successfully completed.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppUpdateResponse
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd"
     xmlns="urn:ietf:params:xml:ns:sppp:base:1">
     <clientTransId>tx_9000</clientTransId>
     <serverTransId>tx_id_12388898</serverTransId>
     <overallResult>
       <code>1000</code>
       <msg>Request successful</msg>
     </overallResult>

   </spppUpdateResponse>

7.12.  Get Destination Group

   SSP2 uses the 'GetDestGrpsRqstType' operation to re-write tally the route
   records provided by last
   provisioned record for destination group DEST_GRP_SSP2_1.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppQueryRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
       xsi:type="ns1:GetDestGrpsRqstType">
       <objKey>
         <rantId>iana-en:222</rantId>
         <name>DEST_GRP_SSP2_1</name>
       </objKey>
     </rqst>
   </spppQueryRequest>

   Registry completes the request successfully and returns a peer in favorable
   response.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppQueryResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <overallResult>
       <code>1000</code>
       <msg>success</msg>
     </overallResult>
     <resultSet xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
       xsi:type="ns1:DestGrpType">
       <rantId>iana-en:222</rantId>
       <rarId>iana-en:222</rarId>
       <dgName>DEST_GRP_SSP2_1</dgName>
     </resultSet>
   </spppQueryResponse>

7.13.  Get Public Identity

   SSP2 obtains the last provisioned record associated with a given Route Group.  If a terminating
   SSP has provided TN.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppQueryRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
       xsi:type="ns1:GetPubIdsRqstType">
       <pi xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
         xsi:type="ns1:TNType">
         <rantId>iana-en:222</rantId>
         <rarId>iana-en:222</rarId>
         <tn>+12025556666</tn>
       </pi>
     </rqst>
   </spppQueryRequest>

   Registry completes the request successfully and returns a route group with at least one route record in favorable
   response.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppQueryResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <overallResult>
       <code>1000</code>
       <msg>success</msg>
     </overallResult>
     <resultSet xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
       xsi:type="ns1:TNType">
       <rantId>iana-en:222</rantId>
       <rarId>iana-en:222</rarId>
       <ns1:dgName>DEST_GRP_1</ns1:dgName>
       <tn>+12025556666</tn>
       <ns1:corInfo>
         <ns1:corClaim>true</ns1:corClaim>
         <ns1:cor>true</ns1:cor>
         <ns1:corDateTime>2010-05-30T09:30:10Z</ns1:corDateTime>
       </ns1:corInfo>
     </resultSet>
   </spppQueryResponse>

7.14.  Get Route Group Request

   SSP2 obtains the
   form of an ingress DNS NAPTR record, then last provisioned record for the egress route allows the
   originating SSP to re-write the regular expression of group
   RTE_GRP_SSP2_1.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppQueryRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
       xsi:type="ns1:GetRteGrpsRqstType">
       <objKey>
         <rantId>iana-en:222</rantId>
         <name>RTE_GRP_SSP2_1</name>
       </objKey>
     </rqst>
   </spppQueryRequest>

   Registry completes the matching
   ingress NAPTR.  The SPPP protocol allows a client to add, get request successfully and
   delete egress route objects based on returns a given peer's ingress route
   group.

   An egress route is of type EgrRteType as shown below:

  <complexType name="EgrRteType">
    <sequence>
      <element name="base" type="spppb:BasicObjType"/>
      <element name="egrRteName" type="spppb:ObjNameType"/>
      <element name="pref" type="unsignedShort"/>
      <element name="svcs" type="string"/>
      <element name="regxRewriteRule" type="spppb:RegexParamType"/>
      <element name="ingressRte" type="spppb:ObjKeyType" minOccurs="0"/>
      <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
    </sequence>
  </complexType>

   The EgrRteType object is composed of favorable
   response.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppQueryResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <overallResult>
       <code>1000</code>
       <msg>success</msg>
     </overallResult>
     <resultSet xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
       xsi:type="ns1:RteGrpType">
       <rantId>iana-en:222</rantId>
       <rarId>iana-en:222</rarId>
       <rteGrpName>RTE_GRP_SSP2_1</rteGrpName>
       <ns1:rteRecRef>
         <ns1:rteRec>
           <ns1:rantId>iana-en:222</ns1:rantId>
           <ns1:name>RTE_SSP2_SBE2</ns1:name>
         </ns1:rteRec>
         <ns1:priority>100</ns1:priority>
       </ns1:rteRecRef>
       <ns1:rteRecRef>
         <ns1:rteRec>
           <ns1:rantId>iana-en:222</ns1:rantId>
           <ns1:name>RTE_SSP2_SBE4</ns1:name>
         </ns1:rteRec>
         <ns1:priority>101</ns1:priority>
       </ns1:rteRecRef>
       <dgName>DEST_GRP_SSP2_1</dgName>
       <isInSvc>true</isInSvc>
       <ns1:priority>10</ns1:priority>
     </resultSet>
   </spppQueryResponse>

7.15.  Get Route Group Offers Request

   SSP2 choses to fetch the following elements:

   o    base: As described in previous sections, most objects contain
        exactly one instance of BasicObjType which contains last provisioned route group sharing offer
   to the ID of <peeringOrg> SSP1.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppQueryRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
       xsi:type="ns1:GetRteGrpOffersRqstType">
       <ns1:offeredToPeers>true</ns1:offeredToPeers>
       <ns1:peeringOrg>ssp1</ns1:peeringOrg>
     </rqst>
   </spppQueryRequest>

   Registry completes the registrant organization that owns this object request successfully and returns a favorable
   response.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppQueryResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <overallResult>
       <code>1000</code>
       <msg>success</msg>
     </overallResult>
     <resultSet xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
       xsi:type="ns1:RteGrpOfferType">
       <rantId>iana-en:222</rantId>
       <rarId>iana-en:222</rarId>
       <rteGrpOfferKey>
         <rteGrpKey>
           <rantId>iana-en:222</rantId>
           <name>RTE_GRP_SSP2_1</name>
         </rteGrpKey>
         <offeredTo>iana-en:111</offeredTo>
       </rteGrpOfferKey>
       <status>offered</status>
       <offerDateTime>2006-05-04T18:13:51.0Z</offerDateTime>
     </resultSet>
   </spppQueryResponse>

7.16.  Get Egree Route

   SSP1 wants to verify the ID of
        the registrar organization that last provisioned this object.

   o    egrRteName: The name of the egress route.

   o    pref:

   o    svcs: The ENUM services that record for the egress route should be used for
        if
   called EGR_RTE_01.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppQueryRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
       xsi:type="ns1:GetEgrRtesRqstType">
       <ns1:objKey>
         <rantId>iana-en:111</rantId>
         <name>EGR_RTE_01</name>
       </ns1:objKey>
     </rqst>
   </spppQueryRequest>

   Registry completes the route record is request successfully and returns a NAPTR.

   o    regxRewriteRule: The regular expression re-write rule that
        should be applied favorable
   response.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppQueryResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <overallResult>
       <code>1000</code>
       <msg>success</msg>
     </overallResult>
     <resultSet xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
       xsi:type="ns1:EgrRteType">
       <rantId>iana-en:111</rantId>
       <rarId>iana-en:111</rarId>
       <egrRteName>EGR_RTE_01</egrRteName>
       <pref>50</pref>
       <svcs>E2U+sip</svcs>
       <regxRewriteRule>
         <ere>^(.*)$</ere>
         <repl>sip:\1@sbe1.ssp1.com</repl>
       </regxRewriteRule>
       <ingressRte>
         <rantId>iana-en:222</rantId>
         <name>RTE_GRP_SSP2_1</name>
       </ingressRte>
     </resultSet>
   </spppQueryResponse>

7.17.  Delete Destination Group

   SSP2 initiates a request to delete the regular expression of destination group
   DEST_GRP_SSP2_1.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
       xsi:type="ns1:DelDestGrpRqstType">
       <objKey>
         <rantId>iana-en:222</rantId>
         <name>DEST_GRP_SSP2_1</name>
       </objKey>
     </rqst>
   </spppUpdateRequest>

   Registry completes the ingress
        NAPTR(s) that belong request successfully and returns a favorable
   response.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppUpdateResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <serverTransId>txid-982543123</serverTransId>
     <overallResult>
       <code>1000</code>
       <msg>Success</msg>
     </overallResult>
   </spppUpdateResponse>

7.18.  Delete Public Identity

   SSP2 choses to de-activate the ingress route TN and that have remove it from the Registry.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
       xsi:type="ns1:DelPubIdRqstType">
       <pi xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
         xsi:type="ns1:TNType">
         <rantId>iana-en:222</rantId>
         <rarId>iana-en:222</rarId>
         <tn>+12025556666</tn>
       </pi>
     </rqst>
   </spppUpdateRequest>

   Registry completes the request successfully and returns a favorable
   response.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppUpdateResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <serverTransId>txid-98298273123</serverTransId>
     <overallResult>
       <code>1000</code>
       <msg>success</msg>
     </overallResult>
   </spppUpdateResponse>

7.19.  Delete Route Group Request

   SSP2 removes the
        given ENUM service (ere + repl).

   o    ingressRte: The ingress route group name that called RTE_GRP_SSP2_1.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
       xsi:type="ns1:DelRteGrpRqstType">
       <objKey>
         <rantId>iana-en:222</rantId>
         <name>RTE_GRP_SSP2_1</name>
       </objKey>
     </rqst>
   </spppUpdateRequest>

   Registry completes the egress request successfully and returns a favorable
   response.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppUpdateResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <serverTransId>txid-982543123</serverTransId>
     <overallResult>
       <code>1000</code>
       <msg>msg</msg>
     </overallResult>
   </spppUpdateResponse>

7.20.  Delete Route Group Offers Request

   SSP2 no longer wants to share route
        should be used for.

   o    ext: Point of extensibility described in group RTE_GRP_SSP2_1 with SSP1.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
       xsi:type="ns1:DelRteGrpOfferRqstType">
       <rteGrpOfferKey>
         <rteGrpKey>
           <rantId>iana-en:222</rantId>
           <name>RTE_GRP_SSP2_1</name>
         </rteGrpKey>
         <offeredTo>iana-en:111</offeredTo>
       </rteGrpOfferKey>
     </rqst>
   </spppUpdateRequest>

   Registry completes the request successfully and returns a previous section of favorable
   response.  Restoring this document.

8.8.1.  Add resource sharing will require a new route
   group offer from SSP2 to SSP1 followed by a successful route group
   accept request from SSP1.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppUpdateResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <serverTransId>txid-982543123</serverTransId>
     <overallResult>
       <code>1000</code>
       <msg>Success</msg>
     </overallResult>
   </spppUpdateResponse>

7.21.  Delete Egress Route

   addEgrRtesRqst operation is used

   SSP1 decides to create or overwrite one or more remove the egress routes.

  <element name="addEgrRtesRqst" type="spppb:AddEgrRtesRqstType"/>
  <complexType name="AddEgrRtesRqstType">
    <complexContent>
      <extension base="spppb:BasicRqstType">
        <sequence>
          <element name="egrRte" type="spppb:EgrRteType"
            maxOccurs="unbounded"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="EgrRteType">
    <sequence>
      <element name="base" type="spppb:BasicObjType"/>
      <element name="egrRteName" type="spppb:ObjNameType"/>
      <element name="pref" type="unsignedShort"/>
      <element name="svcs" type="string"/>
      <element name="regxRewriteRule" type="spppb:RegexParamType"/>
      <element name="ingressRte" type="spppb:ObjKeyType" minOccurs="0"/>
      <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
    </sequence>
  </complexType>

   addEgrRtesRqst route with the label EGR_RTE_01.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppUpdateRequest xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <rqst xmlns:ns1="urn:ietf:params:xml:ns:sppp:base:1"
       xsi:type="ns1:DelEgrRteRqstType">
       <objKey>
         <rantId>iana-en:111</rantId>
         <name>EGR_RTE_01</name>
       </objKey>
     </rqst>
   </spppUpdateRequest>

   Registry completes the request successfully and returns a favorable
   response.

   <?xml version="1.0" encoding="UTF-8"?>
   <spppUpdateResponse xmlns="urn:ietf:params:xml:ns:sppp:base:1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:sppp:base:1 sppp.xsd">
     <serverTransId>txid-982543123</serverTransId>
     <overallResult>
       <code>1000</code>
       <msg>Success</msg>
     </overallResult>
   </spppUpdateResponse>

8.  XML Considerations

   XML serves as the encoding format for SPPP, allowing complex
   hierarchical data to be expressed in a text format that can be read,
   saved, and manipulated with both traditional text tools and tools
   specific to XML.

   XML is added case sensitive.  Unless stated otherwise, XML specifications
   and examples provided in the spppRequest root element this document MUST be interpreted in order the
   character case presented to
   send develop a valid request conforming implementation.

   This section discusses a small number of XML-related considerations
   pertaining to SPPP.

8.1.  Namespaces

   All SPPP protocol elements are defined in the server.  A limitation on namespaces in te IANA
   Considerations section and in the maximum
   number Formal Protocol Specification
   section of EgrRteType is enforced by the registry this document.

8.2.  Versioning and will vary from
   one implementation Character Encoding

   All XML instances SHOULD begin with an <?xml?> declaration to
   identify the next.

   The response from version of XML that is being used, optionally identify
   use of the server character encoding used, and optionally provide a hint to
   an XML parser that an external schema file is returned needed to validate the
   XML instance.

   Conformant XML parsers recognize both UTF-8 (defined in addEgrRtesRspns element,
   which [RFC3629])
   and UTF-16 (defined in [RFC2781]); per [RFC2277] UTF-8 is defined as the element of type BasicRspnsType.

8.8.2.  Get Egress Route

   The getEgrRtesRqst
   RECOMMENDED character encoding for use with SPPP.

   Character encodings other than UTF-8 and UTF-16 are allowed by XML.
   UTF-8 is used the default encoding assumed by XML in the absence of an authorized entity to fetch
   "encoding" attribute or a byte order mark (BOM); thus, the well-
   known egress route data.

     <element name="getEgrRtesRqst" type="spppb:GetEgrRtesRqstType"/>
     <complexType name="GetEgrRtesRqstType">
       <complexContent>
         <extension base="spppb:BasicRqstType">
           <sequence>
             <element name="objectKey" type="spppb:ObjKeyType"
               minOccurs="0" maxOccurs="unbounded"/>
           </sequence>
         </extension>

       </complexContent>
     </complexType>

8.8.3.  Delete Egress Route

   delEgressRte "encoding"
   attribute in the XML declaration is used by authorized entities to remove OPTIONAL if UTF-8 encoding is
   used.  SPPP clients and servers MUST accept a well-know
   route.

     <element name="delEgrRtesRqst" type="spppb:DelEgrRtesRqstType"/>
     <complexType name="DelEgrRtesRqstType">
       <complexContent>
         <extension base="spppb:BasicRqstType">
           <sequence>
             <element name="objectKey" type="spppb:ObjKeyType"
               maxOccurs="unbounded"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType> UTF-8 BOM if present,
   though emitting a UTF-8 BOM is NOT RECOMMENDED.

   Example XML declarations:

   <?xml?> version="1.0" encoding="UTF-8" standalone="no"?>

9.  Security Considerations

   The transport protocol section contains some security properties that
   the transport protocol must provide so that authenticated endpoints
   can exchange data confidentially and with integrity protection.

   More details will be provided in a future revision of this document.

10.  IANA Considerations

   This document uses URNs to describe XML namespaces and XML schemas
   conforming to a registry mechanism described in [RFC3688].

   Two URI assignments are requested.

   Registration request for the SPPP XML namespace:
   urn:ietf:params:xml:ns:sppp:base:1
   Registrant Contact: IESG
   XML: None.  Namespace URIs do not represent an XML specification.

   Registration request for the XML schema:
   URI: urn:ietf:params:xml:schema:sppp:1
   Registrant Contact: IESG
   XML: See the "Formal Specification" section of this document
   (Section 11).

   IANA is requested to create a new SPPP registry for Organization
   Identifiers that will indicate valid strings to be used for well-
   known enterprise namespaces.
   This document makes the following assignments for the OrgIdType
   namespaces:

         Namespace                    OrgIdType namespace string
         ----                         ----------------------------
         IANA Enterprise Numbers       iana-en

11.  Formal Specification

   This section provides the draft XML Schema Definition for the SPPP
   protocol.  Please read Section 3.4 for known issues.

<?xml version="1.0" encoding="UTF-8"?>
<schema xmlns:spppb="urn:ietf:params:xml:ns:sppp:base:1"
  xmlns="http://www.w3.org/2001/XMLSchema"
  targetNamespace="urn:ietf:params:xml:ns:sppp:base:1"
  elementFormDefault="qualified" xml:lang="EN">
  <annotation>
    <documentation>
    ------------------ Object Type Definitions --------------
    </documentation>
  </annotation>
  <complexType name="RteGrpType">
    <complexContent>
     <extension base="spppb:BasicObjType">
       <sequence>
         <element name="base" type="spppb:BasicObjType"/>
      <element name="rteGrpName" type="spppb:ObjNameType"/>
         <element name="rteRec" type="spppb:RteRecType" name="rteRecRef" type="spppb:RteRecRefType"
           minOccurs="0" maxOccurs="unbounded"/>
         <element name="dgName" type="spppb:ObjNameType" minOccurs="0"
           maxOccurs="unbounded"/>
         <element name="peeringOrg" type="spppb:OrgIdType" minOccurs="0"
           maxOccurs="unbounded"/>
         <element name="sourceIdent" type="spppb:SourceIdentType"
           minOccurs="0" maxOccurs="unbounded"/>
         <element name="isInSvc" type="boolean"/>
         <element name="priority" type="unsignedShort"/>
         <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
       </sequence>
     </extension>
    </complexContent>
  </complexType>
  <complexType name="DestGrpType">
    <complexContent>
     <extension base="spppb:BasicObjType">
      <sequence>
         <element name="base" type="spppb:BasicObjType"/>
      <element name="dgName" type="spppb:ObjNameType"/>
      </sequence>
     </extension>
    </complexContent>
  </complexType>
  <complexType name="PubIdType" abstract="true">
    <complexContent>
     <extension base="spppb:BasicObjType">
       <sequence>
         <element name="base" type="spppb:BasicObjType"/>
      <element name="dgName" type="spppb:ObjNameType" minOccurs="0"/>
      <element name="rteRec" type="spppb:RteRecType" minOccurs="0"
        maxOccurs="unbounded"/>
       </sequence>
     </extension>
    </complexContent>
  </complexType>
  <complexType name="EmailType">
    <complexContent>
      <extension base="spppb:PubIdType">
        <sequence>
          <element name="email" type="string"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="TNType">
    <complexContent>
      <extension base="spppb:PubIdType">
        <sequence>
          <element name="tn" type="string"/>
          <element name="corClaim" name="rteRecRef" type="spppb:RteRecRefType"
             minOccurs="0" maxOccurs="unbounded"/>
          <element name="corInfo" type="spppb:CORInfoType"
             minOccurs="0"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="TNRType">
    <complexContent>
      <extension base="spppb:TNType">
        <sequence>
          <element name="endTn" type="string"/>
          <element name="corClaim" name="corInfo" type="spppb:CORInfoType"
              minOccurs="0"/>
        </sequence>
        <attribute name="prefix" type="boolean" default="false">
           </attribute>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="RNType">
    <complexContent>
      <extension base="spppb:PubIdType">
        <sequence>
          <element name="rn" type="string" default="true"/>
          <element name="corInfo" type="spppb:CORInfoType"
             minOccurs="0"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="RteRecType" abstract="true">
    <complexContent>
      <extension base="spppb:BasicObjType">
         <sequence>
           <element name="rrName" type="spppb:ObjNameType"/>
         </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="NAPTRType">
    <complexContent>
      <extension base="spppb:RteRecType">
        <sequence>
          <element name="order" type="unsignedShort"/>
          <element name="pref" type="unsignedShort"/>
          <element name="flags" type="string" minOccurs="0"/>
          <element name="svcs" type="string"/>
          <element name="regx" type="spppb:RegexParamType"
            minOccurs="0"/>
          <element name="repl" type="string" minOccurs="0"/>
          <element name="ttl" type="positiveInteger" minOccurs="0"/>
          <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="NSType">
    <complexContent>
      <extension base="spppb:RteRecType">
        <sequence>
          <element name="hostName" type="string"/>
          <element name="ipAddr" type="spppb:IPAddrType" minOccurs="0"
            maxOccurs="unbounded"/>
          <element name="ttl" type="positiveInteger" minOccurs="0"/>
          <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <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>
  <complexType name="RteGrpOfferType">
   <complexContent>
     <extension base="spppb:BasicObjType">
       <sequence>
         <element name="base" type="spppb:BasicObjType"/>
      <element name="rteGrpOfferKey" type="spppb:RteGrpOfferKeyType"/> type="spppb:RteGrpOfferKeyType"
            />
         <element name="status" type="spppb:RteGrpOfferStatusType"/>
         <element name="offerDateTime" type="dateTime"/>
         <element name="acceptDateTime" type="dateTime" minOccurs="0"/>
         <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
       </sequence>
     </extension>
    </complexContent>
  </complexType>
  <complexType name="EgrRteType">
    <complexContent>
     <extension base="spppb:BasicObjType">
       <sequence>
         <element name="base" type="spppb:BasicObjType"/>
      <element name="egrRteName" type="spppb:ObjNameType"/>
         <element name="pref" type="unsignedShort"/>
         <element name="svcs" type="string"/>
      <element name="regxRewriteRule" type="spppb:RegexParamType"/>
         <element name="ingressRte" name="ingrRteRec" type="spppb:ObjKeyType" minOccurs="0"/>
            minOccurs="0" maxOccurs="unbounded"/>
         <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
       </sequence>
     </extension>
    </complexContent>
  </complexType>
  <annotation>
    <documentation> ------------------ Abstract Object and Element
      Type Definitions -------------- </documentation>
  </annotation>
  <complexType name="BasicObjType"> name="BasicObjType" abstract="true">
    <sequence>
      <element name="rantId" type="spppb:OrgIdType"/>
      <element name="rarId" type="spppb:OrgIdType"/>
      <element name="crtDate" type="dateTime" minOccurs="0"/>
      <element name="modDate" type="dateTime" minOccurs="0"/>
      <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
    </sequence>
  </complexType>
  <complexType name="RteRecType" abstract="true">
    <sequence>
      <element name="priority" type="positiveInteger" default="100"/>
    </sequence>
  </complexType>
  <complexType name="RegexParamType">
    <sequence>
      <element name="ere" type="string" default="^(.*)$"/>
      <element name="repl" type="string"/>
    </sequence>
  </complexType>
  <simpleType name="OrgIdType">
    <restriction base="string"/>
  </simpleType>
  <simpleType name="ObjNameType">
    <restriction base="string"/>
  </simpleType>
  <simpleType name="TransIdType">
    <restriction base="string"/>
  </simpleType>
  <simpleType name="MinorVerType">
    <restriction base="unsignedLong"/>
  </simpleType>
  <complexType name="ObjKeyType">
    <sequence>
      <element name="rantId" type="spppb:OrgIdType"/>
      <element name="name" type="spppb:ObjNameType"/>
    </sequence>
  </complexType>
  <complexType name="RteGrpOfferKeyType">
    <sequence>
      <element name="rteGrpKey" type="spppb:ObjKeyType"/>
      <element name="offeredTo" type="spppb:OrgIdType"/>
    </sequence>
  </complexType>
  <complexType name="BasicRqstType">
    <sequence>
      <element name="clientTransId" type="spppb:TransIdType"
        minOccurs="0"/>
      <element name="minorVer" type="spppb:MinorVerType" minOccurs="0"/>
      <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
    </sequence>
  </complexType>
  <complexType name="BasicRspnsType">
    <sequence>
      <element name="clientTransId" type="spppb:TransIdType"
        minOccurs="0"/>
      <element name="serverTransId" type="spppb:TransIdType"/>
      <element name="resCode" type="int"/>
      <element name="resMsg" type="string"/>
      <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
    </sequence>
    <attribute name="clientTransId" type="spppb:TransIdType"/>
    <attribute name="serverTransId" type="spppb:TransIdType"/>
  </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">
    <sequence>
      <element name="rteRec" type="spppb:ObjKeyType"/>
      <element name="priority" type="unsignedShort"/>
      <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
    </sequence>
  </complexType>
  <complexType name="SourceIdentType">
    <sequence>
      <element name="sourceIdentLabel" type="string"/>
      <element name="sourceIdentScheme"
        type="spppb:SourceIdentSchemeType"/>

      <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
    </sequence>
  </complexType>
  <simpleType name="SourceIdentSchemeType">
    <restriction base="token">
      <enumeration value="uri"/>
      <enumeration value="ip"/>
      <enumeration value="rootDomain"/>
    </restriction>
  </simpleType>
  <complexType name="CORInfoType">
    <sequence>
      <element name="corClaim" type="boolean" default="true"/>
      <element name="corClaimApproved" name="cor" type="boolean" default="false"
      />
         minOccurs="0"/>
      <element name="corDateTime" type="dateTime" minOccurs="0"/>
    </sequence>
  </complexType>
  <complexType name="SvcMenuType">
    <sequence>
      <element name="serverStatus" type="spppb:ServerStatusType"/>
      <element name="majMinVersion" type="string"
        maxOccurs="unbounded"/>
      <element name="objURI" type="anyURI" maxOccurs="unbounded"/>
      <element name="extURI" type="anyURI" minOccurs="0"
        maxOccurs="unbounded"/>
    </sequence>
  </complexType>
  <simpleType name="ServerStatusType">
    <restriction base="token">
      <enumeration value="inService"/>
      <enumeration value="outOfService"/>
    </restriction>
  </simpleType>
  <complexType name="RteGrpOfferKeyType">
    <sequence>
      <element name="rteGrpKey" type="spppb:ObjKeyType"/>
      <element name="offeredTo" type="spppb:OrgIdType"/>
    </sequence>
  </complexType>
  <simpleType name="RteGrpOfferStatusType">
    <restriction base="token">
      <enumeration value="offered"/>
      <enumeration value="accepted"/>
    </restriction>
  </simpleType>
  <complexType name="ExtAnyType"> name="ExtAnyType">
    <sequence>
      <any namespace="##other" maxOccurs="unbounded"/>
    </sequence>
  </complexType>
  <annotation>
    <documentation> -------------- Operation Request and Response
      Object Type Definitions ------------ </documentation>
  </annotation>
  <complexType name="ResultCodeType">
    <sequence>
       <element name="code" type="int"/>
       <element name="msg" type="string"/>
    </sequence>
  </complexType>
  <complexType name="RqstObjResultCodeType">
    <complexContent>
       <extension base="spppb:ResultCodeType">
          <sequence>
             <element name="rqstObj" type="spppb:BasicRqstType"/>
          </sequence>
       </extension>
    </complexContent>
  </complexType>

  <complexType name="BasicRqstType" abstract="true">
    <sequence>
      <any namespace="##other" maxOccurs="unbounded"/>
      <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
    </sequence>
  </complexType>
  <complexType name="BasicQueryRqstType" abstract="true">
    <sequence>
      <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/>
    </sequence>
  </complexType>
  <annotation>
    <documentation> -------------- Operation Request and Response
      Object Type Definitions ------------ </documentation>
  </annotation>

  <complexType name="AddRteGrpsRqstType"> name="AddRteGrpRqstType">
    <complexContent>
      <extension base="spppb:BasicRqstType">
        <sequence>
          <element name="rteGrp" type="spppb:RteGrpType"
            maxOccurs="unbounded"/> type="spppb:RteGrpType"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="DelRteGrpsRqstType"> name="DelRteGrpRqstType">
    <complexContent>
      <extension base="spppb:BasicRqstType">
        <sequence>
          <element name="objectKey" type="spppb:ObjKeyType"
            maxOccurs="unbounded"/> name="objKey" type="spppb:ObjKeyType"/>

        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="GetRteGrpsRqstType">
    <complexContent>
      <extension base="spppb:BasicRqstType"> base="spppb:BasicQueryRqstType">
        <sequence>
          <element name="objectKey" name="objKey" type="spppb:ObjKeyType"
            minOccurs="0" maxOccurs="unbounded"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="GetRteGrpsRspnsType"> name="AddRteRecRqstType">
    <complexContent>
      <extension base="spppb:BasicRspnsType"> base="spppb:BasicRqstType">
        <sequence>
          <element name="rteGrp" type="spppb:RteGrpType" minOccurs="0"
            maxOccurs="unbounded"/> name="rteRec" type="spppb:RteRecType"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="AddDestGroupsRqstType"> name="DelRteRecRqstType">
    <complexContent>
      <extension base="spppb:BasicRqstType">
        <sequence>
          <element name="destGrp" type="spppb:DestGrpType"
            maxOccurs="unbounded"/> name="objKey" type="spppb:ObjKeyType"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="DelDestGroupsRqstType"> name="GetRteRecsRqstType">
    <complexContent>
      <extension base="spppb:BasicRqstType"> base="spppb:BasicQueryRqstType">
        <sequence>
          <element name="objectKey" name="objKey" type="spppb:ObjKeyType"
            minOccurs="0" maxOccurs="unbounded"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>

  <complexType name="GetDestGroupsRqstType"> name="AddDestGrpRqstType">
    <complexContent>
      <extension base="spppb:BasicRqstType">
        <sequence>
          <element name="objectKey" type="spppb:ObjKeyType"
            minOccurs="0" maxOccurs="unbounded"/> name="destGrp" type="spppb:DestGrpType"/>

        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="GetDestGroupsRspnsType"> name="DelDestGrpRqstType">
    <complexContent>
      <extension base="spppb:BasicRspnsType"> base="spppb:BasicRqstType">
        <sequence>
          <element name="destGrp" type="spppb:DestGrpType"
            minOccurs="0" maxOccurs="unbounded"/> name="objKey" type="spppb:ObjKeyType"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="AddPubIdsRqstType"> name="GetDestGrpsRqstType">
    <complexContent>
      <extension base="spppb:BasicRqstType"> base="spppb:BasicQueryRqstType">
        <sequence>
          <element name="pi" type="spppb:PubIdType" name="objKey" type="spppb:ObjKeyType"
            minOccurs="0" maxOccurs="unbounded"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="DelPubIdsRqstType"> name="AddPubIdRqstType">
    <complexContent>
      <extension base="spppb:BasicRqstType">
        <sequence>
          <element name="pi" type="spppb:PubIdType"
            maxOccurs="unbounded"/> type="spppb:PubIdType"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="GetPubIdsRqstType"> name="DelPubIdRqstType">
    <complexContent>
      <extension base="spppb:BasicRqstType">
        <sequence>
          <element name="pi" type="spppb:PubIdType" minOccurs="0"
            maxOccurs="unbounded"/> type="spppb:PubIdType"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="GetPubIdsRspnsType"> name="GetPubIdsRqstType">
    <complexContent>
      <extension base="spppb:BasicRspnsType"> base="spppb:BasicQueryRqstType">
        <sequence>
          <element name="pi" type="spppb:PubIdType" minOccurs="0"
            maxOccurs="unbounded"/>
        </sequence>

      </extension>
    </complexContent>
  </complexType>
  <complexType name="AddRteGrpOffersRqstType"> name="AddRteGrpOfferRqstType">
    <complexContent>
      <extension base="spppb:BasicRqstType">
        <sequence>
          <element name="rteGrpOffer" type="spppb:RteGrpOfferType"
            maxOccurs="unbounded"/> type="spppb:RteGrpOfferType"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="DelRteGrpOffersRqstType"> name="DelRteGrpOfferRqstType">
    <complexContent>
      <extension base="spppb:BasicRqstType">
        <sequence>
          <element name="rteGrpOfferKey"
                     type="spppb:RteGrpOfferKeyType" maxOccurs="unbounded"/> />
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="AcceptRteGrpOffersRqstType"> name="AcceptRteGrpOfferRqstType">
    <complexContent>
      <extension base="spppb:BasicRqstType">
        <sequence>
          <element name="rteGrpOfferKey"
            type="spppb:RteGrpOfferKeyType" maxOccurs="unbounded"/>
                    type="spppb:RteGrpOfferKeyType"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="RejectRteGrpOffersRqstType"> name="RejectRteGrpOfferRqstType">
    <complexContent>
      <extension base="spppb:BasicRqstType">
        <sequence>
          <element name="rteGrpOfferKey"
            type="spppb:RteGrpOfferKeyType" maxOccurs="unbounded"/>
                    type="spppb:RteGrpOfferKeyType"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="GetRteGrpOffersRqstType">
    <complexContent>
      <extension base="spppb:BasicRqstType"> base="spppb:BasicQueryRqstType">
        <sequence>
          <element name="offeredByPeers" type="boolean"
             minOccurs="0"/>

          <element name="offeredToPeers" type="boolean"
             minOccurs="0"/>
          <element name="status" type="spppb:RteGrpOfferStatusType"
            minOccurs="0"/>
          <element name="peeringOrg" type="spppb:OrgIdType"
            minOccurs="0" maxOccurs="unbounded"/>
          <element name="rteGrpOfferKey"
            type="spppb:RteGrpOfferKeyType" minOccurs="0"
            maxOccurs="unbounded"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="GetRteGrpOffersRspnsType">
    <complexContent>
      <extension base="spppb:BasicRspnsType">
        <sequence>
          <element name="rteGrpOffer" type="spppb:RteGrpOfferType"
            minOccurs="0" maxOccurs="unbounded"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="AddEgrRtesRqstType"> name="AddEgrRteRqstType">
    <complexContent>
      <extension base="spppb:BasicRqstType">
        <sequence>
          <element name="egrRte" type="spppb:EgrRteType"
            maxOccurs="unbounded"/> type="spppb:EgrRteType"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="DelEgrRtesRqstType"> name="DelEgrRteRqstType">
    <complexContent>
      <extension base="spppb:BasicRqstType">
        <sequence>
          <element name="objectKey" type="spppb:ObjKeyType"
            maxOccurs="unbounded"/> name="objKey" type="spppb:ObjKeyType"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="GetEgrRtesRqstType">
    <complexContent>
      <extension base="spppb:BasicRqstType"> base="spppb:BasicQueryRqstType">
        <sequence>
          <element name="objectKey" name="objKey" type="spppb:ObjKeyType"
            minOccurs="0" maxOccurs="unbounded"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="GetEgrRtesRspnsType">
    <complexContent>
      <extension base="spppb:BasicRspnsType">
        <sequence>
          <element name="rteGrp" type="spppb:RteGrpType" minOccurs="0"
            maxOccurs="unbounded"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="GetSvcMenuRqstType">
    <complexContent>
      <extension base="spppb:BasicRqstType"/>
    </complexContent>
  </complexType>
  <complexType name="GetSvcMenuRspnsType">
    <complexContent>
      <extension base="spppb:BasicRspnsType">
        <sequence>
          <element name="svcMenu" type="spppb:SvcMenuType"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>
  <annotation>
    <documentation> -------------- Operation -------- Generic Request and Response
      Element Definitions ------------ </documentation>
  </annotation>
  <annotation>
    <documentation> -------------- Manage Route Groups
    </documentation>
  </annotation>
  <element name="addRteGrpsRqst" type="spppb:AddRteGrpsRqstType"/>
  <element name="delRteGrpsRqst" type="spppb:DelRteGrpsRqstType"/>
  <element name="getRteGrpsRqst" type="spppb:GetRteGrpsRqstType"/>
  <element name="addRteGrpsRspns" type="spppb:BasicRspnsType"/>
  <element name="delRteGrpsRspns" type="spppb:BasicRspnsType"/>
  <element name="getRteGrpsRspns" type="spppb:GetRteGrpsRspnsType"/>
  <annotation>
    <documentation> -------------- Manage Destination Groups
    </documentation>
  </annotation>
  <element name="addDestGroupsRqst" type="spppb:AddDestGroupsRqstType"/>
  <element name="delDestGroupsRqst" type="spppb:DelDestGroupsRqstType"/>
  <element name="getDestGroupsRqst" type="spppb:GetDestGroupsRqstType"/>
  <element name="addDestGroupsRspns" type="spppb:BasicRspnsType"/>
  <element name="delDestGroupsRspns" type="spppb:BasicRspnsType"/>
  <element name="getDestGroupsRspns"
    type="spppb:GetDestGroupsRspnsType"/>
  <annotation>
    <documentation> -------------- Manage Public Identifiers
    </documentation>
  </annotation>
  <element name="addPubIdsRqst" type="spppb:AddPubIdsRqstType"/>
  <element name="delPubIdsRqst" type="spppb:DelPubIdsRqstType"/>
  <element name="getPubIdsRqst" type="spppb:GetPubIdsRqstType"/>
  <element name="addPubIdsRspns" type="spppb:BasicRspnsType"/>
  <element name="delPubIdsRspns" type="spppb:BasicRspnsType"/>
  <element name="getPubIdsRspns" type="spppb:GetPubIdsRspnsType"/>
  <annotation>
    <documentation> -------------- Manage Route Group Offers
      --------------- </documentation>
  </annotation>
  <element name="addRteGrpOffersRqst"
    type="spppb:AddRteGrpOffersRqstType"/>
  <element name="delRteGrpOffersRqst"
    type="spppb:DelRteGrpOffersRqstType"/>
  <element name="acceptRteGrpOffersRqst"
    type="spppb:AcceptRteGrpOffersRqstType"/>
  <element name="rejectRteGrpOffersRqst"
    type="spppb:RejectRteGrpOffersRqstType"/> name="spppUpdateRequest">
    <complexType>
      <sequence>
        <element name="getRteGrpOffersRqst"
    type="spppb:GetRteGrpOffersRqstType"/> name="clientTransId" type="spppb:TransIdType"
            minOccurs="0"/>
        <element name="addRteGrpOffersRspns" type="spppb:BasicRspnsType"/> name="minorVer" type="spppb:MinorVerType"
            minOccurs="0"/>
        <element name="delRteGrpOffersRspns" type="spppb:BasicRspnsType"/> name="rqst" type="spppb:BasicRqstType"
            maxOccurs="unbounded"/>
      </sequence>
    </complexType>
  </element>
  <element name="acceptRteGrpOffersRspns" type="spppb:BasicRspnsType"/> name="spppUpdateResponse">
    <complexType>
      <sequence>
        <element name="rejectRteGrpOffersRspns" type="spppb:BasicRspnsType"/> name="clientTransId" type="spppb:TransIdType"
            minOccurs="0"/>
        <element name="getRteGrpOffersRspns"
    type="spppb:GetRteGrpOffersRspnsType"/>
  <annotation>
    <documentation> -------------- Manage Egress Routes
    </documentation>
  </annotation> name="serverTransId" type="spppb:TransIdType"/>
        <element name="addEgrRtesRqst" type="spppb:AddEgrRtesRqstType"/> name="overallResult" type="spppb:ResultCodeType"/>
        <element name="delEgrRtesRqst" type="spppb:DelEgrRtesRqstType"/> name="rqstObjResult"
            type="spppb:RqstObjResultCodeType" minOccurs="0"
          maxOccurs="unbounded"/>
      </sequence>
    </complexType>
  </element>
  <element name="getEgrRtesRqst" type="spppb:GetEgrRtesRqstType"/> name="spppQueryRequest">
    <complexType>
      <sequence>
        <element name="addEgrRtesRspns" type="spppb:BasicRspnsType"/> name="minorVer" type="spppb:MinorVerType"
            minOccurs="0"/>
        <element name="delEgrRtesRspns" type="spppb:BasicRspnsType"/> name="rqst" type="spppb:BasicQueryRqstType"/>
      </sequence>
    </complexType>
  </element>
  <element name="getEgrRtesRspns" type="spppb:GetEgrRtesRspnsType"/>
  <annotation>
    <documentation> -------------- Misc Operations </documentation>
  </annotation> name="spppQueryResponse">
    <complexType>
      <sequence>
        <element name="getSvcMenuRqst" type="spppb:GetSvcMenuRqstType"/> name="overallResult" type="spppb:ResultCodeType"/>
        <element name="getSvcMenuRspns" type="spppb:GetSvcMenuRspnsType"/>
  <annotation>
    <documentation> -------- Generic Request and Response Definitions
      --------------- </documentation>
  </annotation> name="resultSet" type="spppb:BasicObjType"
           minOccurs="0" maxOccurs=" unbounded"/>
      </sequence>
    </complexType>
  </element>
  <element name="spppRequest"> name="spppServerStatusRequest">
    <complexType>
      <sequence>
        <any maxOccurs="unbounded"/>
        <element name="minorVer" type="spppb:MinorVerType"
           minOccurs="0"/>
      </sequence>
      <attribute name="transactional" type="boolean" use="optional"/>
    </complexType>
  </element>
  <element name="spppResponse"> name="spppServerStatusResponse">
    <complexType>
      <sequence>
        <any maxOccurs="unbounded"/>
        <element name="overallResult" type="spppb:ResultCodeType"/>
        <element name="svcMenu" type="spppb:SvcMenuType"/>
      </sequence>
    </complexType>
  </element>
</schema>
12.  Specification Extensibility

   The protocol defined in this specification is extensible.  This
   section explains how to extend the protocol and what procedures are
   necessary to follow in order to ensure proper extensions.

13.  Acknowledgments

   This document is a result of various discussions held in the DRINKS
   working group and within the DRINKS protocol design team, which is
   comprised of the following individuals, in alphabetical order:
   Deborah A Guyton (Telcordia), Sumanth Channabasappa (CableLabs),
   Jean-Francois Mule (CableLabs), Kenneth Cartwright (TNSI), Manjul
   Maharishi (TNSI), David Schwartz (XConnect), and the co-chairs
   Richard Shockey and Alexander Mayrhofer (enum.at GmbH).

   The authors of this document thank the following individuals for
   their advice, reviews and comments during the development of this
   protocol: Lisa Dusseault, "YOUR NAME HERE" -- send comments to drinks
   list.

14.  References

14.1.  Normative References

   [I-D.ietf-drinks-sppp-over-soap]
              Cartwright, K., "SPPP Over SOAP and HTTP",
              draft-ietf-drinks-sppp-over-soap-00 (work in progress),
              June 2010.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2277]  Alvestrand, H., "IETF Policy on Character Sets and
              Languages", BCP 18, RFC 2277, January 1998.

   [RFC2781]  Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO
              10646", RFC 2781, February 2000.

   [RFC3629]  Yergeau, F., "UTF-8, a transformation format of ISO
              10646", STD 63, RFC 3629, November 2003.

   [RFC3688]  Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
              January 2004.

   [RFC3986]  Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
              Resource Identifier (URI): Generic Syntax", STD 66,
              RFC 3986, January 2005.

14.2.  Informative References

   [I-D.ietf-drinks-usecases-requirements]
              Channabasappa, S., "DRINKS Use cases and Protocol
              Requirements", draft-ietf-drinks-usecases-requirements-03
              (work in progress), May 2010.

   [RFC2821]  Klensin, J., "Simple Mail Transfer Protocol", RFC 2821,
              April 2001.

   [RFC3261]  Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
              A., Peterson, J., Sparks, R., Handley, M., and E.
              Schooler, "SIP: Session Initiation Protocol", RFC 3261,
              June 2002.

   [RFC3761]  Faltstrom, P. and M. Mealling, "The E.164 to Uniform
              Resource Identifiers (URI) Dynamic Delegation Discovery
              System (DDDS) Application (ENUM)", RFC 3761, April 2004.

   [RFC4725]  Mayrhofer, A. and B. Hoeneisen, "ENUM Validation
              Architecture", RFC 4725, November 2006.

   [RFC5486]  Malas, D. and D. Meyer, "Session Peering for Multimedia
              Interconnect (SPEERMINT) Terminology", RFC 5486,
              March 2009.

Authors' Addresses

   Jean-Francois Mule
   CableLabs
   858 Coal Creek Circle
   Louisville, CO  80027
   USA

   Email: jfm@cablelabs.com

   Kenneth Cartwright
   TNS
   1939 Roland Clarke Place
   Reston, VA  20191
   USA

   Email: kcartwright@tnsi.com

   Syed Wasim Ali
   NeuStar
   46000 Center Oak Plaza
   Sterling, VA  20166
   USA

   Email: syed.ali@neustar.biz

   Alexander Mayrhofer
   enum.at GmbH
   Karlsplatz 1/9
   Wien,   A-1010
   Austria

   Email: alexander.mayrhofer@enum.at