idnits 2.17.1 draft-drinks-spprov-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document date (July 2, 2010) is 5047 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'ObjecTypeName' is mentioned on line 1027, but not defined == Missing Reference: 'OperationName' is mentioned on line 1027, but not defined == Unused Reference: 'RFC3761' is defined on line 2776, but no explicit reference was found in the text == Outdated reference: A later version (-07) exists of draft-ietf-drinks-sppp-over-soap-00 ** Downref: Normative reference to an Informational RFC: RFC 2781 == Outdated reference: A later version (-06) exists of draft-ietf-drinks-usecases-requirements-03 -- Obsolete informational reference (is this intentional?): RFC 2821 (Obsoleted by RFC 5321) -- Obsolete informational reference (is this intentional?): RFC 3761 (Obsoleted by RFC 6116, RFC 6117) Summary: 1 error (**), 0 flaws (~~), 7 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DRINKS J-F. Mule 3 Internet-Draft CableLabs 4 Intended status: Standards Track K. Cartwright 5 Expires: January 3, 2011 TNS 6 S. Ali 7 NeuStar 8 A. Mayrhofer 9 enum.at GmbH 10 July 2, 2010 12 Session Peering Provisioning Protocol 13 draft-drinks-spprov-00 15 Abstract 17 This document defines a protocol for provisioning session 18 establishment data into Session Data Registries and SIP Service 19 Provider data stores. The provisioned data is typically used by 20 various network elements for session peering. 22 This document describes the Session Peering Provisioning Protocol 23 used by clients to provision registries. The document provides a set 24 of guiding principles for the design of this protocol including 25 extensibility and independent transport definitions, a basic data 26 model and an XML Schema Document. 28 Status of this Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at http://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on January 3, 2011. 45 Copyright Notice 47 Copyright (c) 2010 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 7 64 3. Protocol Definition . . . . . . . . . . . . . . . . . . . . . 9 65 3.1. Protocol Overview and Layering . . . . . . . . . . . . . . 9 66 3.2. Data Model . . . . . . . . . . . . . . . . . . . . . . . . 10 67 3.2.1. Structure of the SPPP Data Model . . . . . . . . . . . 10 68 3.2.2. Data Model Objects and Attributes . . . . . . . . . . 12 69 3.2.3. Applicability for LUF-only Data Provisioning . . . . . 13 70 3.2.4. Applicability for LUF+LRF data Provisioning . . . . . 15 71 3.3. Common Attributes . . . . . . . . . . . . . . . . . . . . 17 72 3.4. Known Issues and Current Limitations of the Data Model . . 17 73 4. Transport Protocol Requirements . . . . . . . . . . . . . . . 18 74 4.1. Connection Oriented . . . . . . . . . . . . . . . . . . . 19 75 4.2. Request & Response Model . . . . . . . . . . . . . . . . . 19 76 4.3. Connection Lifetime . . . . . . . . . . . . . . . . . . . 19 77 4.4. Authentication . . . . . . . . . . . . . . . . . . . . . . 19 78 4.5. Confidentiality & Integrity . . . . . . . . . . . . . . . 20 79 4.6. Near Real Time . . . . . . . . . . . . . . . . . . . . . . 20 80 4.7. Request & Response Sizes . . . . . . . . . . . . . . . . . 20 81 4.8. Request and Response Correlation . . . . . . . . . . . . . 20 82 4.9. Request Acknowledgement . . . . . . . . . . . . . . . . . 20 83 4.10. Mandatory Transport . . . . . . . . . . . . . . . . . . . 21 84 5. XML Considerations . . . . . . . . . . . . . . . . . . . . . . 22 85 5.1. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 22 86 5.2. Versioning . . . . . . . . . . . . . . . . . . . . . . . . 22 87 6. Request and Reply Model . . . . . . . . . . . . . . . . . . . 23 88 6.1. Request . . . . . . . . . . . . . . . . . . . . . . . . . 23 89 6.2. Reply . . . . . . . . . . . . . . . . . . . . . . . . . . 25 90 7. Response Codes and Messages . . . . . . . . . . . . . . . . . 27 91 8. Protocol Commands . . . . . . . . . . . . . . . . . . . . . . 29 92 8.1. Add Route Group Operation . . . . . . . . . . . . . . . . 29 93 8.2. Get Route Groups Operation . . . . . . . . . . . . . . . . 36 94 8.3. Add Route Group Offers Operation . . . . . . . . . . . . . 37 95 8.4. Accept Route Group Offers Operation . . . . . . . . . . . 40 96 8.5. Reject Route Group Offers Operation . . . . . . . . . . . 42 97 8.6. Get Route Group Offers Operation . . . . . . . . . . . . . 44 98 8.7. Public Identifier Operations . . . . . . . . . . . . . . . 47 99 8.7.1. Add Public Identifier . . . . . . . . . . . . . . . . 47 100 8.7.2. Get Public Identifier . . . . . . . . . . . . . . . . 50 101 8.7.3. Delete Public Identifier . . . . . . . . . . . . . . . 51 102 8.8. Egress Route Operations . . . . . . . . . . . . . . . . . 52 103 8.8.1. Add Egress Route . . . . . . . . . . . . . . . . . . . 52 104 8.8.2. Get Egress Route . . . . . . . . . . . . . . . . . . . 52 105 8.8.3. Delete Egress Route . . . . . . . . . . . . . . . . . 52 106 9. Security Considerations . . . . . . . . . . . . . . . . . . . 53 107 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 54 108 11. Formal Specification . . . . . . . . . . . . . . . . . . . . . 55 109 12. Specification Extensibility . . . . . . . . . . . . . . . . . 68 110 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 69 111 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 70 112 14.1. Normative References . . . . . . . . . . . . . . . . . . . 70 113 14.2. Informative References . . . . . . . . . . . . . . . . . . 70 114 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 72 116 1. Introduction 118 Service providers and enterprises use registries to make call or 119 session routing decisions for Voice over IP, SMS and MMS traffic 120 exchanges. This document is narrowly focused on the provisioning 121 protocol for these registries. This protocol prescribes a way for an 122 entity to provision session-related data into a registry. The data 123 being provisioned can be optionally shared with other participating 124 peering entities. The requirements and use cases driving this 125 protocol have been documented in 126 [I-D.ietf-drinks-usecases-requirements]. The reader is expected to 127 be familiar with the terminology defined in the previously mentioned 128 document. 130 Three types of provisioning flows have been described in the use case 131 document: client to registry provisioning, registry to local data 132 repository and registry-to-registry. This document addresses a 133 subset (client-to-registry provisioning) by defining a Session 134 Peering Provisioning Protocol (SPPP) for provisioning Session 135 Establishment Data (SED) into a Registry (arrow numbered one in the 136 figure below). While the other "provisioning flows" are shown below 137 as separate message flows, no determination has been made for whether 138 one common baseline protocol could be used for all three, or whether 139 distinct protocols are required. 141 *------------* *------------* 142 (1). Provisioning SED | | (3).Registry | | 143 -----------------------> | Registry |<------------->| Registry | 144 data into Registries| | to Registry | | 145 *------------* exchanges *------------* 146 / \ \ 147 / \ \ 148 / \ \ 149 / \ v 150 / \ ... 151 / \ 152 / (2). \ 153 / Distributing \ 154 / SED \ 155 V V 156 +----------+ +----------+ 157 |Local Data| |Local Data| 158 |Repository| |Repository| 159 +----------+ +----------+ 161 Three Registry Provisioning Flows 163 Figure 1 165 The data provisioned for session establishment is typically used by 166 various downstream SIP signaling systems to route a call to the next 167 hop associated with the called domain. These systems typically use a 168 local data store ("Local Data Repository") as their source of session 169 routing information. More specifically, the SED data is the set of 170 parameters that the outgoing signaling path border elements (SBEs) 171 need to initiate the session. See [RFC5486] for more details. 173 A "terminating" SIP Service Provider (SSP) provisions SED into the 174 registry to be selectively shared with other peer SSPs. 175 Subsequently, a Registry may distribute the provisioned data into 176 local Data Repositories used for look-up queries (identifier -> URI) 177 or for lookup and location resolution (identifier -> URI -> ingress 178 SBE of terminating SSP). In some cases, the Registry may 179 additionally offer a central query resolution service (not shown in 180 the above figure). 182 A key requirement for the SPPP protocol is to be able to accommodate 183 two basic deployment scenarios: 185 1. A Look-Up Function (LUF) to determine the target domain to assist 186 in call routing (as described in [RFC5486]). In this case, the 187 querying entity may use other means to perform the Location 188 Routing Function (LRF) which in turn helps determine the actual 189 location of the Signaling Function in that domain. 191 2. Both Look-Up function (LUF) and Location Routing Function (LRF) 192 to locate the SED data fully. 194 In terms of protocol design, SPPP protocol is agnostic to the 195 transport. This document includes the description of the data model 196 and the means to enable protocol operations within a request and 197 response structure. To encourage interoperability, the protocol 198 supports extensibility aspects. 200 Transport requirements are provided in this document to help with the 201 selection of the optimum transport mechanism. 202 ([I-D.ietf-drinks-sppp-over-soap]) identifies a SOAP transport 203 mechanism for SPPP. 205 This document is organized as follows: 207 o Section 3 provides an overview of the SPPP protocol, including 208 the layering approach, functional entities and data model; 210 o Section 4 defines requirements for SPPP transport protocols; 212 o Section 5 defines XML considerations that XML parsers must meet 213 to conform to this specification. 215 o Section 6 describes the protocol request-reply model; 217 o Section 8 defines the protocol commands for this version of 218 SPPP, and how to extend them; 220 2. Terminology 222 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 223 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 224 document are to be interpreted as described in [RFC2119]. 226 This document reuses terms from [RFC3261], [RFC5486], use cases and 227 requirements documented in [I-D.ietf-drinks-usecases-requirements] 228 and the ENUM Validation Architecture [RFC4725]. 230 In addition, this document specifies the following additional terms: 232 SPPP: Session Peering Provisioning Protocol, the protocol used to 233 provision data into a Registry (see arrow labeled "1." in Figure 1 234 of [I-D.ietf-drinks-usecases-requirements]). It is the primary 235 scope of this document. 237 SPDP: Session Peering Distribution Protocol, the protocol used to 238 distribute data to Local Data Repository (see arrow labeled "2." 239 in Figure 1 of [I-D.ietf-drinks-usecases-requirements]). 241 Client: An application that supports an SPPP Client; it is 242 sometimes referred to as a "Registry Client". 244 Registry: The Registry operates a master database of Session 245 Establishment Data for one or more Registrants. 247 A Registry acts as an SPPP Server. 249 Registrant: In this document, we extend the definition of a 250 Registrant based on [RFC4725]. The Registrant is the end-user, 251 the person or organization who is the "holder" of the Session 252 Establishment Data being provisioned into the Registry. For 253 example, in [I-D.ietf-drinks-usecases-requirements], a Registrant 254 is pictured as a SIP Service Provider in Figure 2. 256 A Registrant is identified by its name in the data model. 258 Registrar: In this document, we also extend the definition of a 259 Registrar from [RFC4725]. A Registrar performs provisioning 260 operations on behalf of a Registrant by interacting with the 261 Registry, in our case via the SPPP protocol defined in this 262 document. 264 A Registrar is identified by its name in the data model. 266 3. Protocol Definition 268 This section introduces the structure of the data model and provides 269 the information framework for the SPPP protocol. An overview of the 270 protocol operations is first provided with a typical deployment 271 scenario. The data model is then defined along with all the objects 272 manipulated by the protocol and their relationships. 274 3.1. Protocol Overview and Layering 276 SPPP is a simple request/reply protocol that allows a client 277 application to submit provisioning data and query requests to a 278 server. The SPPP data structures are designed to be protocol 279 agnostic. Concerns regarding encryption, non-repudiation, and 280 authentication are beyond the scope of this document. For more 281 details, please refer to the Transport Protocol Requirements section. 283 Layer Example 284 +-------------+ +-----------------------------+ 285 (5) |Data Objects | | RteGrpType, etc. | 286 +-------------+ +-----------------------------+ 287 | | 288 +-------------+ +-----------------------------+ 289 (4) | Operations | | addRteGrpsRqst, etc. | 290 +-------------+ +-----------------------------+ 291 | | 292 +-------------+ +-----------------------------+ 293 (3) | Message | | spppRequest, spppResponse | 294 +-------------+ +-----------------------------+ 295 | | 296 +-------------+ +-----------------------------+ 297 (2) | Message | | HTTP, SOAP, None, etc. | 298 | Envelope | | | 299 +-------------+ +-----------------------------+ 300 | | 301 +-------------+ +-----------------------------+ 302 (1) | Transport | | TCP, TLS, BEEP, etc. | 303 | Protocol | | | 304 +-------------+ +-----------------------------+ 306 SPPP Layering 308 Figure 2 310 SPPP can be viewed as a set of layers that collectively define the 311 structure of an SPPP request and response. Layers 1 and 2, as 312 detailed below, are left to separate specifications to allow for 313 potentially multiple SPPP transport, envelope, and authentication 314 technologies. This document defines layers 3, 4, and 5 below. 316 1. The transport protocol layer provides a communication mechanism 317 between the client and server. SPPP can be layered over any 318 transport protocol that provides a set of basic requirements 319 defined in the Transport Protocol Requirements section. 321 2. The message envelope layer is optional, but can provide features 322 that are above the transport technology layer but below the 323 application messaging layer. Technologies such as HTTP and SOAP 324 are examples of messaging envelope technologies. 326 3. The message layer provides a simple, envelope-independent and 327 transport-independent, SPPP wrapper for SPPP request and response 328 messages. 330 4. The operation layer defines the set of base SPPP actions that can 331 be invoked using an SPPP message. Operations are encoded using 332 XML encoded actions and objects. 334 5. The data object layer defines the base set of SPPP data objects 335 that can be included in update operations or returned in 336 operation responses. 338 3.2. Data Model 340 The data model illustrated and described in Figure 3 defines the 341 logical objects and the relationships between these objects that the 342 SPPP protocol supports. SPPP defines the protocol operations through 343 which an SPPP Client populates a Registry with these logical objects. 344 Various clients belonging to different Registrants and distinct 345 Registrars may use the protocol for populating the Registry's data. 347 3.2.1. Structure of the SPPP Data Model 349 The logical structure presented below is consistent with the 350 terminology and requirements defined in 351 [I-D.ietf-drinks-usecases-requirements]. Note that the current 352 version of this data model does not yet address the notion of Data 353 Recipient Groups (left for a future revision of this document). 355 +-------------+ +------------------+ 356 | all object | |Organization: | 357 | types | |orgName*, | 358 +------+------+ |sourceIdentLabels,| 359 +------------>|peerPrefs, | 360 |extension | 361 All objects are | | 362 associated with 2 | | 363 Organizations to +------------------+ 364 identify the ^ 365 registrant and |A Route Group is 366 the registrar |associated with 367 |zero or more 368 |Organizations 369 | 370 +--------+--------------+ 371 |Route Group: | +-----[abstract]-+ 372 | registrantOrgName*, | | | 373 | registrarOrgName, | | Route Record: | 374 | rteGrpName*, | | rteRecName*, | 375 | dgName*, +------->| priority, | 376 | isInService, | | extension | 377 | rteRec*, | | | 378 | sourceOrgs, | +----------------+ 379 | sourceIdentLabels, | ^ 380 | extension | |Various types 381 +-----------------------+ |of Route 382 ^ |Records... 383 | +------+------------... 384 | | | | 385 | +----+ +-------+ +----+ 386 | | URI| | NAPTR | | NS | 387 +----------------+-----+ +----+ +-------+ +----+ 388 |Destination | 389 |Group: | +----------[abstract]-+ 390 | registrantOrgName*, | |Public | 391 | registrarOrgName, | |Identifier: | 392 | dgName*, | | registrantOrgName*,| 393 | extension |<----+ registrarOrgName, | 394 +----------------------+ | publicIdentifier*, | 395 | dgName*, | 396 | extension | 397 +---------------------+ 399 SPPP Data Model 401 Figure 3 403 Note that the attributes whose names end with the character * are 404 mandatory attributes. 406 3.2.2. Data Model Objects and Attributes 408 The objects and attributes that comprise the data model can be 409 described as follows (objects listed from the bottom up): 411 o Public Identifier (publicIdentifier): 412 A public identifier is a well known attribute that is often used 413 to perform lookup functions. For the purposes of this document, a 414 Public Identifier can be an email address, a telephone number, a 415 range of telephone numbers or a PSTN Routing Number (RN). 417 A Destination Group may be associated with a Public Identifier to 418 create a logical grouping and share a common set of Routes. 420 A Public Identifier may optionally be associated with zero or more 421 individual route records. This ability for a Public Identifier to 422 be directly associated with a set of routes (e.g. target URI), as 423 opposed to being associated with a Destination Group, supports the 424 use cases where the target URI contains data specifically tailored 425 to an individual Public Identifier. 427 o Telephone Number Range (TNRType, tn, endTn): 428 A public identifier may represent an inclusive range of telephone 429 numbers. The TN range is defined by the first and last telephone 430 number of the inclusive range. For example, a TN range of 431 (tn=12125550000, endTn=12125560000) means all the TNs from 432 12125550000 to 12125560000 are included. 434 o Destination Group (dgName): 435 A collection of zero or more Public Identifiers that are related 436 to one or more Route Group relationships. 438 o Route Group (rteGrpName): 439 A Route Group contains a set of route records (RteRecs) that are 440 associated with Public Identifiers. To support the use cases 441 defined in [I-D.ietf-drinks-usecases-requirements], this document 442 defines the following types of RteRecs: NAPTRType, NSType, and 443 URIType. To support the Look-Up Function resolution, it is 444 assumed that the administrative domain will be defined as a URI 445 and it can be expressed as a URIType or a NAPTRType. 446 A Route Group can be either in or out of service (as indicated by 447 'isInService' attribute). It also contains a list of 448 organizations that can query the object (peeringOrg) and have 449 access to its content (sourceIdent). 451 o Source Identity (SourceIdentType, sourceIdentLabels, 452 sourceIdentScheme): 453 In some scenarios, it is important to identify the source of a 454 query. The source identity label is a character string that 455 identifies the source of a resolution lookup and can be used for 456 source-based routing. We define several ways of identifying the 457 source: by IP address, by the source URI or a domain name. 459 o Route Record (RteRecType): 460 A Route Record is the data that the resolution systems return in 461 response to a successful query with the Public Identifier as the 462 query string. It is associated with a Route Group for routes that 463 are not specific to a Public Identifier. 464 To support the use cases defined in 465 [I-D.ietf-drinks-usecases-requirements], SPPP protocol defines 466 three type of Route Records: URIType, NAPTRType, and NSType. 467 These Route Records extend the abstract type RteRecType and 468 inherit the common attribute 'priority' that is meant for setting 469 precedence across the route records defined within a Route Group 470 in a protocol agnostic fashion. 472 o Organization (OrgIdType): 473 An Organization represents an entity that is authorized to access 474 given data elements. All objects are associated with two 475 organizations to identify the registrant and the registrar. An 476 entity authorized to view a Route Group (typically a SSP peering 477 partner) is identified a peering Organization (peeringOrg). 479 3.2.3. Applicability for LUF-only Data Provisioning 481 This section describes the data model for SPPP clients that only 482 provision data for LUF resolution. 484 The purpose of LUF data provisioning is to provide the administrative 485 domain given a destination group. As such, a client provisioning 486 LUF-only data only needs to provide one or more route groups that 487 contain a route group name and a URI for the target domain. 489 Note that source-based routing is supported: depending on what entity 490 requests the look-up resolution (sourceIdent), a different URI may be 491 returned by using different Route Groups. 493 Certain protocol operations could be added in future revisions of 494 this document as "short-cuts" for LUF related data provisioning. 496 +-----------------------+ 497 |Route Group: | 498 | rteGrpName*, | 499 | isInService, | 500 | rteRec*, | 501 | extension | 502 | | 503 +-----------------------+ 504 ^ 505 | 506 +---------+------------+ 507 |Destination | 508 |Group: | 509 | dgName*, |<----+ 510 | extension | | 511 +----------------------+ | 512 | 513 +-------------+---------+ 514 |Public | 515 |Identifier: | 516 | publicIdentifier*, | 517 | dgName*, | 518 | extension | 519 +-----------------------+ 521 LUF-only Data Model Example for SPPP 523 Figure 4 525 As an example, a request to add a route group where public 526 identifiers resolve into the URI sip:ssp1.example.com during look-up 527 resolution would be: 529 530 533 id-12317123 534 20 535 536 537 registrantID123 538 registrarId0 539 540 route_grp_1 541 542 ^(.*)$ 543 urn:ssp1.example.com 544 545 true 546 547 549 Figure 5 551 3.2.4. Applicability for LUF+LRF data Provisioning 553 This section provides a read-out of the data model for SPPP clients 554 that provision data for both LUF and LRF resolution. 556 The purpose of LUF+LRF data provisioning is to provide a URI given a 557 destination group as well as the location routing for that target 558 domain. As such, a client provisioning LUF+LRF data provides one or 559 more route groups that contain a route group name and a URI for the 560 target domain and each route group is associated with a Route Record 561 which can be in the form of a URI, NAPTR or NS resource record. 563 +-----------------------+ 564 |Route Group: | +-----[abstract]-+ 565 | rteGrpName*, | | | 566 | isInService, | | Route Record: | 567 | targetDomain, +------->| rteRecName*, | 568 | extension | | priority, | 569 | | | extension | 570 +-----------------------+ | | 571 ^ +----------------+ 572 | 573 +---------+------------+ 574 |Destination | 575 |Group: | 576 | dgName*, |<----+ 577 | extension | | 578 +----------------------+ | 579 | 580 +-------------+-[abstract]-+ 581 |Public | 582 |Identifier: | 583 | publicIdentifier*, | 584 | dgName*, | 585 | extension | 586 +--------------------------+ 588 LUF+LRF Data Model Example for SPPP for DRINKS WG Review 590 Figure 6 592 As an example, a request to add a route group where public 593 identifiers resolve into the URI ssp1.example.com and NAPTR 594 associated with that domain based on the source Organization would 595 be: 597 598 600 id-12317123 601 20 602 603 604 registrantID123 605 registrarId0 606 607 route_grp_1 608 true 609 610 ^(.*)$ 611 urn:ssp1.example.com 612 613 true 614 615 617 Figure 7 619 3.3. Common Attributes 621 This section defines common object attributes. The protocol 622 exchanges and operations in SPPP take various parameters. Some of 623 these are common to several objects. 625 Two organization roles have been identified in the use cases and in 626 this protocol. A registrant is the organization or business entity 627 that "owns" the object while a registrar is an entity that can 628 provision an object. 630 3.4. Known Issues and Current Limitations of the Data Model 632 The data model described in Figure 3 does not yet address all of the 633 requirements and use cases defined in 634 [I-D.ietf-drinks-usecases-requirements]. 636 This section will list known protocol issues to be addressed in 637 future revisions. 639 4. Transport Protocol Requirements 641 This section provides requirements for transport protocols suitable 642 for SPPP. More specifically, this section specifies the services, 643 features, and assumptions that SPPP delegates to the chosen transport 644 and envelope technologies. 646 Two different groups of use cases are specified in 647 [I-D.ietf-drinks-usecases-requirements]. One group of use cases 648 describes the provisioning of data by a client into a Registry 649 (Section 3.1 of the above referenced document), while the other group 650 describes the distribution of data into local data repositories 651 (Section 3.2). The current version of this document focuses on the 652 first set of use cases (client to registry provisioning). 654 These use cases may involve the provisioning of very small data sets 655 like the modification or update of a single public identifier. Other 656 provisioning operations may deal with huge datasets like the 657 "download" of a whole local number portability database to a 658 Registry. 660 As a result, a transport protocol for SPPP must be very flexible and 661 accommodate various sizes of data set sizes. 663 For the reasons outlined above, it is conceivable that provisioning 664 and distributing may use different transport protocols. This 665 document focuses on the provisioning protocol. 667 A few topics remain open for discussion: 669 o The ability to establish multiple connections between a client and 670 server may be desirable. If so, we may want to specify the 671 relation of transactions between the various connections. 673 o Pipelining of requests is required at the SPPP protocol layer. It 674 may have impacts at the transport level that need to be outlined. 676 o Scope: the current scope of this effort is based upon having a 677 connection oriented transport. Is there any need to support a 678 transport protocol with asynchronous operation? 680 o If it is required that responses arrive in the order of the 681 requests, this must be specified clearly. 683 4.1. Connection Oriented 685 The SPPP protocol follows a model where a Client establishes a 686 connection to a Server in order to further exchange provisioning 687 transactions over such point-to-point connection. A transport 688 protocol for SPPP MUST therefore be connection oriented. 690 Note that the role of the "Client" and the "Server" only applies to 691 the connection, and those roles are not related in any way to the 692 type of entity that participates in a protocol exchange. For 693 example, a Registry might also include a "Client" when such a 694 Registry initiates a connection (for example, for data distribution 695 to SSP). 697 4.2. Request & Response Model 699 Provisioning operations in SPPP follow the request - response model, 700 where a transaction is initiated by a Client using a Request command, 701 and the Server responds to the Client by means of a Response. 703 Multiple subsequent request-response exchanges MAY be performed over 704 a single connection. 706 Therefore, a transport protocol for SPPP MUST follow the request- 707 response model by allowing a response to be sent to the request 708 initiator. 710 4.3. Connection Lifetime 712 Some use cases involve provisioning a single request to a network 713 element - connections supporting such provisioning requests might be 714 short-lived, and only established on demand. 716 Other use cases involve either provisioning a huge set of data, or a 717 constant stream of small updates, which would require long-lived 718 connections. 720 Therefore, a protocol suitable for SPPP SHOULD support short lived as 721 well as long lived connections. 723 4.4. Authentication 725 Many use cases require the Server to authenticate the Client, and 726 potentially also the Client to authenticate the Server. While 727 authentication of the Server by the Client is expected to be used 728 only to prevent impersonation of the Server, authentication of the 729 Client by the Server is expected to be used to identify and further 730 authorize the Client to certain resources on the Server. 732 Therefore, an SPPP transport protocol MUST provide means for a Server 733 to authenticate and authorize a Client, and MAY provide means for 734 Clients to authenticate a Server. 736 However, SPPP transport SHOULD also allow for unauthenticated 737 connections. 739 4.5. Confidentiality & Integrity 741 Data that is transported over the protocol is deemed confidential. 742 Therefore, a transport protocol suitable for SPPP MUST ensure 743 confidentiality and integrity protection by providing encryption 744 capabilities. 746 Additionally, a DRINKS protocol MUST NOT use an unreliable lower- 747 layer transport protocol that does not provide confidentiality and 748 integrity protection. 750 4.6. Near Real Time 752 Many use cases require near real-time responses from the Server. 753 Therefore, a DRINKS transport protocol MUST support near-real-time 754 response to requests submitted by the Client. 756 4.7. Request & Response Sizes 758 SPPP covers a range of use cases - from cases where provisioning a 759 single public identifier will create very small request and response 760 sizes to cases where millions of data records are submitted or 761 retrieved in one transaction. Therefore, a transport protocol 762 suitable for SPPP MUST support a great variety of request and 763 response sizes. 765 A transport protocol MAY allow splitting large chunks of data into 766 several smaller chunks. 768 4.8. Request and Response Correlation 770 A transport protocol suitable for SPPP MUST allow responses to be 771 correlated with requests. 773 4.9. Request Acknowledgement 775 Data transported in the SPPP protocol is likely crucial for the 776 operation of the communication network that is being provisioned. 778 Failed transactions can lead to situations where a subset of public 779 identifiers (or even SSPs) might not be reachable, or situations 780 where the provisioning state of the network is inconsistent. 782 Therefore, a transport protocol for SPPP MUST provide a Response for 783 each Request, so that a Client can identify whether a Request 784 succeeded or failed. 786 4.10. Mandatory Transport 788 As of this writing of this revision, one transport protocol proposal 789 has been provided in [I-D.ietf-drinks-sppp-over-soap]. 791 This section will define a mandatory transport protocol to be 792 compliant with this RFC. 794 5. XML Considerations 796 XML serves as the encoding format for SPPP, allowing complex 797 hierarchical data to be expressed in a text format that can be read, 798 saved, and manipulated with both traditional text tools and tools 799 specific to XML. 801 XML is case sensitive. Unless stated otherwise, XML specifications 802 and examples provided in this document MUST be interpreted in the 803 character case presented to develop a conforming implementation. 805 This section discusses a small number of XML-related considerations 806 pertaining to SPPP. 808 5.1. Namespaces 810 All SPPP protocol elements are defined in the following namespace: 811 urn:ietf:params:xml:ns:sppp:base:1 813 Namespace and schema definitions are used to identify both the base 814 protocol schema and the schemas for managed objects. 816 5.2. Versioning 818 All XML instances SHOULD begin with an declaration to 819 identify the version of XML that is being used, optionally identify 820 use of the character encoding used, and optionally provide a hint to 821 an XML parser that an external schema file is needed to validate the 822 XML instance. 824 Conformant XML parsers recognize both UTF-8 (defined in [RFC3629]) 825 and UTF-16 (defined in [RFC2781]); per [RFC2277] UTF-8 is the 826 RECOMMENDED character encoding for use with SPPP. 828 Character encodings other than UTF-8 and UTF-16 are allowed by XML. 829 UTF-8 is the default encoding assumed by XML in the absence of an 830 "encoding" attribute or a byte order mark (BOM); thus, the "encoding" 831 attribute in the XML declaration is OPTIONAL if UTF-8 encoding is 832 used. SPPP clients and servers MUST accept a UTF-8 BOM if present, 833 though emitting a UTF-8 BOM is NOT RECOMMENDED. 835 Example XML declarations: 837 version="1.0" encoding="UTF-8" standalone="no"?> 839 6. Request and Reply Model 841 An SPPP client interacts with an SPPP server by using one of the 842 supported transport mechanisms to send one or more requests to the 843 server and receive corresponding replies from the server. An SPPP 844 request is wrapped within the element while an SPPP 845 reply is wrapped within an element. Furthermore, fully 846 formed SPPP requests and replies are comprised of constructs required 847 by the chosen transport technology, and the chosen envelope 848 technology. The supported transport technology and envelope 849 technology specifications will be defined in separate documents, and 850 are not discussed here. 852 6.1. Request 854 An SPPP request object, common to any transport and envelope 855 technology, is contained within the generic element. 857 858 859 860 861 862 863 865 Within any element is the request object specific to 866 the type of object(s) being operated on and the action(s) being 867 performed on that object. For example, the addRteGroupRqst object, 868 used to create Route Groups, that would be passed within an 869 is defined as follows: 871 872 873 874 876 879 880 881 883 All update requests contain a BasicRqstType object. This object is 884 defined as follows: 886 887 888 890 892 895 896 898 899 900 902 903 904 906 The data elements within the BasicRqstType object are primarily 907 "house keeping" data elements. They are described as follows: 909 o clientTransId: The client generated transaction ID that 910 identifies this request for tracking purposes. This value is 911 also echoed back to the client in the response. This value will 912 not be checked for uniqueness. 914 o minorVer: This identifies the minor version of the SPPP API that 915 the client is attempting to use. This is used in conjunction 916 with the major version identifier in the XML namespace. Refer 917 to the Versioning section of this document for more detail. 919 o ext: This is the standard extension element for this object. 920 Refer to the Extensibility section of this document for more 921 details. 923 6.2. Reply 925 An SPPP reply object, common to any transport and envelope 926 technology, is contained within the generic element. 928 929 930 931 932 933 934 936 Within any element is the reply object containing the 937 result of the request. All create, update, and delete operations 938 result in a common response object structure, defined as follows: 940 941 942 943 944 945 946 948 949 950 952 954 956 958 961 962 964 The data elements within the BasicRspnseType object are described as 965 follows: 967 o clientTransId: The echoed back client transaction ID that 968 explicitly identifies this request for tracking purposes. This 969 value is not guaranteed to be unique. 971 o serverTransId: The server transaction ID that identifies this 972 request for tracking purposes. This value is guaranteed to be 973 unique. 975 o resCode: The response code that explicitly identifies the result 976 of the request. See the Response Code section for further 977 details. 979 o resMsg: The human readable response message that accompanies the 980 response code. See the Response Code section for further 981 details. 983 o ext: This is the standard extension element for this object. 984 Refer to the Extensibility section for more details. 986 7. Response Codes and Messages 988 This section contains an initial listing of response codes and their 989 corresponding human readable text. 991 The response code numbering scheme generally adheres to the theory 992 formalized in section 4.2.1 of [RFC2821]: 994 o The first digit of the response code can only be 1 or 2: 1 = a 995 positive result, 2 = a negative result. 997 o The second digit of the response code indicates the category: 0 998 = Protocol Syntax, 1 = Implementation Specific Business Rule, 2 999 = Security, 3 = Server System. 1001 o The third and fourth digits of the response code indicate the 1002 individual message event within the category defines by the 1003 first two digits. 1005 +--------+----------------------------------------------------------+ 1006 | Result | Text | 1007 | Code | | 1008 +--------+----------------------------------------------------------+ 1009 | 1000 | Request Succeeded. | 1010 | | | 1011 | 2001 | Request syntax invalid. | 1012 | | | 1013 | 2002 | Request too large. | 1014 | | | 1015 | 2003 | Version not supported. | 1016 | | | 1017 | 2103 | Command invalid. | 1018 | | | 1019 | 2104 | Attribute value invalid: [ObjecTypeName]:[Object's | 1020 | | rantId]:[Object's name]:{[Embedded | 1021 | | ObjecTypeName]}:[attribute name]:[attribute value]. | 1022 | | | 1023 | 2105 | Object does not exist: [ObjecTypeName]:[Object's | 1024 | | rantId]:[Object's name]. | 1025 | | | 1026 | 2106 | Object status or ownership does not allow for operation: | 1027 | | [OperationName]:[ObjecTypeName]:[Object's | 1028 | | rantId]:[Object's name]. | 1029 | | | 1030 | 2301 | System temporarily unavailable. | 1031 | | | 1032 | 2302 | Unexpected internal system or server error. | 1033 +--------+----------------------------------------------------------+ 1034 Table 1: Response Codes Numbering Scheme and Messages 1036 Some response messages are "parameterized" with one or more of the 1037 following parameters: "attribute name", "attribute value", 1038 "objectType-objectId", and "operation name". 1040 The use of these parameters MUST adhere to the following rules: 1042 o All parameters within a response message are mandatory and MUST 1043 be present. Parameters within a response message MUST NOT be 1044 left empty. 1046 o Any value provided for the "attribute name" parameter MUST be an 1047 exact element name of the protocol data element that the 1048 response message is referring to. For example, valid values for 1049 "attribute name" are "destGrpName", "rteGrpName", etc. 1051 o A value provided for the "command/request type" parameter MUST 1052 be an exact request object name that the response message is 1053 referring to. For example, a valid value for "request object 1054 name" is "delRteGrpsRqst". 1056 o The value for "attribute value" MUST be the value of the data 1057 element to which the preceding "attribute name" refers. 1059 o Result code 2104 SHOULD be used whenever an element value does 1060 not adhere to data validation rules. 1062 o Result codes 2104 and 2105 MUST NOT be used interchangeably. 1063 Response code 2105 SHOULD be returned when the data element(s) 1064 used to uniquely identify a pre-existing object do not exist. 1065 If the data elements used to uniquely identify an object are 1066 malformed, then response code 2104 SHOULD be returned. 1068 8. Protocol Commands 1070 This section provides a preliminary list of SPPP protocol commands. 1071 At this early stage of the protocol development, the commands are 1072 only listed with a brief description. 1074 8.1. Add Route Group Operation 1076 As described in the introductory sections, a Route Group represents a 1077 combined grouping of Route Records that define route information, 1078 Destination Groups that contain a set of Public Identifiers with 1079 common routing information, and the list of peer organizations that 1080 have access to these public identifiers using this route information. 1081 It is this indirect linking of public identities to route information 1082 that significantly improves the scalability and manageability of the 1083 peering data. Additions and changes to routing information are 1084 reduced to a single operation on a Route Group, rather than millions 1085 of data updates to individual public identity records that 1086 individually contain their peering point data. 1088 The addRteGrpsRqst operation creates or overwrites one or more Route 1089 Group objects. If a Route Group with the given name and registrant 1090 ID does not exist, then the server MUST create the Route Group. If a 1091 Route Group with the given name and registrant does exist, then the 1092 server MUST replace the current properties of the Route Group with 1093 the properties passed into the addRteGrpsRqst operation. The XSD 1094 declarations of the operation request object are as follows: 1096 1097 1098 1099 1100 1101 1103 1104 1105 1106 1108 The element passed into the spppRequest element for this operation is 1109 the addRteGrpsRqst element. This element is of type 1110 AddRteGrpsRqstType, which extends BasicRqstType and contains one or 1111 more RteGrpType objects. Any limitation on the maximum number of 1112 RteGrpType objects that may be passed into this operation is a policy 1113 decision and is not limited by the protocol. The RteGrpType object 1114 structure is defined as follows: 1116 1117 1118 1119 1120 1122 1124 1126 1128 1129 1131 1132 1134 The RteGrpType object is composed of the following elements: 1136 o base: As described in previous sections, most objects contain 1137 exactly one instance of BasicObjType which contains the ID of 1138 the registrant organization that owns this object and the ID of 1139 the registrar organization that provisioned this object. 1141 o rteGrpName: The character string that contains the name of the 1142 Route Group. It uniquely identifies this object within the 1143 context of the registrant ID (a child element of the base 1144 element as described above). 1146 o rteRec: Set of zero or more objects of type RteRecType that 1147 house the routing information, sometimes referred to as SED, 1148 that the RteGrpType object contains. 1150 o dgName: Set of zero or more names of DestGrpType object 1151 instances. Each dgName name, in association with this Route 1152 Group's registrant ID, uniquely identifies a DestGrpType object 1153 instance whose public identities are reachable using the routing 1154 information housed in this Route Group. 1156 o peeringOrg: Set of zero or more peering organization IDs that 1157 have accepted an offer to receive this Route Group's 1158 information. The set of peering organizations in this list is 1159 not directly settable or modifiable using the addRteGrpsRqst 1160 operation. This set is instead controlled using the route offer 1161 and accept operations. 1163 o sourceIdent: Set of zero or more SourceIdentType object 1164 instances. These objects, described further below, house the 1165 source identification schemes and identifiers that are applied 1166 at resolution time as part of source based routing algorithms 1167 for the Route Group. 1169 o isInSvc: A boolean element that defines whether this Route Group 1170 is in service. The routing information contained in a Route 1171 Group that is in service is a candidate for inclusion in 1172 resolution responses for public identities residing in the 1173 Destination Group associated with this Route Group. The routing 1174 information contained in a Route Group that is not in service is 1175 not a candidate for inclusion is resolution responses. 1177 o ext: Point of extensibility described in a previous section of 1178 this document. 1180 As described above, the Route Group contains a set of RteRecType 1181 objects. The RteRecType object is an abstract type. The concrete 1182 types that use RteRecType as an extension base are NAPTRType, NSType, 1183 and URIType. The definitions of these types are included below. The 1184 NAPTRType object is comprised of the data elements necessary for a 1185 NAPTR that contains routing information the Route Group. The NSType 1186 object is comprised of the data elements necessary for a Name Server 1187 that points to another DNS server that contains the desired routing 1188 information. The URIType object is comprised of the data elements 1189 necessary to house a URI. 1191 1192 1193 1195 1196 1198 1199 1200 1201 1202 1203 1204 1205 1206 1208 1209 1211 1213 1214 1215 1216 1218 1219 1220 1221 1222 1223 1225 1227 1229 1230 1231 1232 1234 1235 1236 1237 1238 1240 1241 1243 1244 1245 1246 1247 1248 1250 1251 1252 1253 1254 1255 1256 1258 1259 1260 1261 1263 The NAPTRType object is composed of the following elements: 1265 o order: Order value in an ENUM NAPTR, relative to other NAPTRType 1266 objects in the same Route Group. 1268 o pref: Preference value in an ENUM NAPTR. 1270 o svcs: ENUM service(s) that are served by the SBE. This field's 1271 value must be of the form specified in RFC 3761 (e.g., E2U+ 1272 pstn:sip+sip). The allowable values are a matter of policy and 1273 not limited by this protocol. 1275 o regx: NAPTR's regular expression field. If this is not included 1276 then the Repl field must be included. 1278 o repl: NAPTR replacement field, should only be provided if the 1279 Regex field is not provided, otherwise it will be ignored by the 1280 server. 1282 o ttl: Number of seconds that an addressing server may cache this 1283 NAPTR. 1285 o ext: Point of extensibility described in a previous section of 1286 this document. 1288 The NSType object is composed of the following elements: 1290 o hostName: Fully qualified host name of the name server. 1292 o ipAddr: Zero or more objects of type IpAddrType. Each object 1293 holds an IP Address and the IP Address type, IPv4 or IP v6. 1295 o ttl: Number of seconds that an addressing server may cache this 1296 Name Server. 1298 o ext: Point of extensibility described in a previous section of 1299 this document. 1301 The URIType object is composed of the following elements: 1303 o ere: The POSIX Extended Regular Expression (ere) as defined in 1304 [RFC3986] 1306 o uri: the URI as defined in [RFC3986] 1308 The RteGrpType object provides support for source-based routing via 1309 the source identity element. The source-based routing criteria 1310 provides the ability to specify zero or more of the following in 1311 association with a given Route Group: a regular expression that is 1312 matched against the resolution client IP address, a regular 1313 expression that is matched against the root domain name(s), and/or a 1314 regular expression that is matched against the calling party URI(s). 1315 The result will be that, after identifying the visible Route Groups 1316 whose associated Destination Group(s) contain the lookup key being 1317 queried, the resolution server will evaluate the characteristics of 1318 the Source URI, and Source IP address, and root domain of the lookup 1319 key being queried. The resolution server compares these criteria 1320 against source based routing criteria associated with the Route 1321 Groups. The routing information contained in Route Groups that have 1322 source based routing criteria will only be included in the resolution 1323 response if one or more of the criteria matches the source criteria 1324 from the resolution request. 1326 1327 1328 1329 1331 1333 1334 1336 1337 1338 1339 1340 1341 1342 1344 The SourceIdentType object is composed of the following data 1345 elements: 1347 o sourceIdentScheme: The source identification scheme that this 1348 source identification criteria applies to and that the 1349 associated sourceIdentRegex should be matched against. 1351 o sourceIdentRegex: The regular expression that should be used to 1352 test for a match against the portion of the resolution request 1353 that is dictated by the associated sourceIdentScheme. 1355 o ext: Point of extensibility described in a previous section of 1356 this document. 1358 The result of the addRteGrpsRqst operation is the addRteGrpsRspns 1359 element defined below. As with all SPPP requests, the result is all- 1360 or-nothing. If more than one RteRecType is passed into this request, 1361 then they will either all succeed or all fail. In the case of 1362 failure, the failure response code(s) and message(s) will indicate 1363 the reason for the failure and the object(s) that caused the failure. 1365 1367 The response codes that the addRteGrpsRqst operation can return are 1368 as follows: 1370 o 1000: Request Succeeded. 1372 o 2001: Request syntax invalid. 1374 o 2002: Request too large. 1376 o 2003: Version not supported. 1378 o 2103: Command invalid. 1380 o 2104: Attribute value invalid. 1382 o 2105: Object does not exist. 1384 o 2106: Object status or ownership does not allow for request. 1386 o 2301: System temporarily unavailable. 1388 o 2302: Unexpected internal system or server error. 1390 8.2. Get Route Groups Operation 1392 The getRteGrpsRqst operation allows a client to get the properties of 1393 Route Group objects that a registrar organization is authorized to 1394 view. The server will attempt to find a Route Group object that has 1395 the registrant ID and route group name pair contained in each 1396 ObjKeyType object instance. If the set of ObjKeyType objects is 1397 empty then the server will return the list of Route Group objects 1398 that the querying client has the authority to view. If there are no 1399 matching Route Groups found then an empty result set will be 1400 returned. 1402 The element passed into the spppRequest element for this operation is 1403 the getRteGrpsRqst element. This element is of type 1404 GetRteGrpsRqstType, which extends BasicRqstType and contains zero or 1405 more ObjKeyType objects. Any limitation on the maximum number of 1406 objects that may be passed into or returned by this operation is a 1407 policy decision and not limited by the protocol. The XSD declaration 1408 of the operation is as follows: 1410 1412 1413 1414 1415 1416 1418 1419 1420 1421 1423 The result of the getRteGrpsRqst operation returned in the 1424 spppResponse element is the getRteGrpsRspns element defined below. 1425 This object contains the resulting set of RteGrpType objects, or an 1426 empty set if there were no matches. 1428 1431 1432 1433 1434 1435 1437 1438 1439 1440 1442 The response codes that the getRteGrpsRqst operation can return are 1443 as follows: 1445 o 1000: Request Succeeded. 1447 o 2001: Request syntax invalid. 1449 o 2002: Request too large. 1451 o 2003: Version not supported. 1453 o 2103: Command invalid. 1455 o 2104: Attribute value invalid. 1457 o 2301: System temporarily unavailable. 1459 o 2302: Unexpected internal system or server error. 1461 8.3. Add Route Group Offers Operation 1463 The list of peer organizations whose resolution responses can include 1464 the routing information contained in a given Route Group is 1465 controlled by the organization to which a Route Group object belongs, 1466 its registrant, and the peer organization that submits resolution 1467 requests, a data recipient or peering organization. The registrant 1468 offers access to a Route Group by submitting a Route Group Offer and 1469 the data recipient can then accept or reject that offer. Not until 1470 access to a Route Group has been offered and accepted will the data 1471 recipient's organization ID be included in the peeringOrg list in a 1472 Route Group object, and that Route Group's peering information become 1473 a candidate for inclusion in the responses to the resolution requests 1474 submitted by that data recipient. The addRteGrpOffersRqst operation 1475 creates or overwrites one or more Route Group Offer objects. If a 1476 Route Group Offer for the given Route key (route name and registrant 1477 ID) and offeredToOrg ID does not exist, then the server creates the 1478 Route Group Offer object. If a such a Route Group Offer does exist, 1479 then the server replaces the current object with the new object. The 1480 XSD declarations of the operation request object are as follows: 1482 1485 1486 1487 1488 1489 1491 1492 1493 1494 1496 The element passed into the spppRequest element for this operation is 1497 the addRteGrpOffersRqst element. This element is of type 1498 AddRteGrpOffersRqstType, which extends BasicRqstType and contains one 1499 or more RteGrpOfferType objects. Any limitation on the maximum 1500 number of objects that may be passed into or returned by this 1501 operation is a policy decision and not limited by the protocol. The 1502 XSD declaration of the operation is as follows: 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1521 1522 1523 1524 1525 1526 1528 The RteGrpOfferType object is composed of the following elements: 1530 o base: As described in previous sections, most objects contain 1531 exactly one instance of BasicObjType which contains the ID of 1532 the registrant organization that owns this object and the ID of 1533 the registrar organization that provisioned this object. 1535 o rteGrpOfferKey: The object that identifies the route that is or 1536 has been offered and the organization that it is or has been 1537 offered to. The combination of these three data elements 1538 uniquely identify a Route Group Offer. 1540 o status: The status of the offer, offered or accepted. This 1541 status is controlled by the server. It is automatically set to 1542 "offered" when ever a new Route Group Offer is added, and is 1543 automatically set to "accepted" if and when that offer is 1544 accepted. The value of the element is ignored when passed in by 1545 the client. 1547 o offerDateTime: Date and time in GMT when the Route Group Offer 1548 was added. 1550 o acceptDateTime: Date and time in GMT when the Route Group Offer 1551 was accepted. 1553 The result of addRteGrpOffersRqst is the addRteGrpOffersRspns element 1554 defined below. As with all SPPP requests, the result is all-or- 1555 nothing. If more than one RteGrpOfferType is passed into this 1556 request, then they will either all succeed or all fail. In the case 1557 of failure, the failure response code(s) and message(s) will indicate 1558 the reason for the failure and the object(s) that caused the failure. 1560 1562 The response codes that the addRteGrpOffersRqst operation can return 1563 are as follows: 1565 o 1000: Request Succeeded. 1567 o 2001: Request syntax invalid. 1569 o 2002: Request too large. 1571 o 2003: Version not supported. 1573 o 2103: Command invalid. 1575 o 2104: Attribute value invalid. 1577 o 2105: Object does not exist. 1579 o 2106: Object status or ownership does not allow for request. 1581 o 2301: System temporarily unavailable. 1583 o 2302: Unexpected internal system or server error. 1585 8.4. Accept Route Group Offers Operation 1587 Not until access to a Route Group has been offered and accepted will 1588 the data recipient's organization ID be included in the peeringOrg 1589 list in that Route Group object, and that Route Group's peering 1590 information become a candidate for inclusion in the responses to the 1591 resolution requests submitted by that data recipient.The 1592 acceptRteGrpOffersRqst operation is called by, or on behalf of, the 1593 data recipient to accept one or more Route Group Offers that are 1594 pending in the "offered" status for the data recipient's organization 1595 ID. If a Route Group Offer for the given Route Group Offer key 1596 (route name, route registrant ID, data recipient's organization ID) 1597 exists, then the server moves the Route Group Offer to the "accepted" 1598 status and adds that data recipient's organization ID into the list 1599 of peerOrgIds for that Route Group. If a such a Route Group Offer 1600 does not exist, then the server returns the appropriate error code 1601 2105. The XSD declarations for the operation request object are as 1602 follows: 1604 1607 1608 1609 1610 1611 1613 1614 1615 1616 1618 The element passed into the spppRequest element for this operation is 1619 the acceptRteGrpOffersRqst element. This element is of type 1620 AcceptRteGrpOffersRqstType, which extends BasicRqstType and contains 1621 one or more RteGrpOfferKeyType objects. Any limitation on the 1622 maximum number of objects that may be passed into or returned by this 1623 operation is a policy decision and not limited by the protocol. 1625 The result of acceptRteGrpOffersRqst is the acceptRteGrpOffersRspns 1626 element defined below. As with all SPPP requests, the result is all- 1627 or-nothing. If more than one RteGrpOfferKeyType is passed into this 1628 request, then they will either all succeed or all fail. In the case 1629 of failure, the failure response code(s) and message(s) will indicate 1630 the reason for the failure and the object(s) that caused the failure. 1632 1635 The response codes that the acceptRteGrpOffersRspns operation can 1636 return are as follows: 1638 o 1000: Request Succeeded. 1640 o 2001: Request syntax invalid. 1642 o 2002: Request too large. 1644 o 2003: Version not supported. 1646 o 2103: Command invalid. 1648 o 2104: Attribute value invalid. 1650 o 2105: Object does not exist. 1652 o 2106: Object status or ownership does not allow for request. 1654 o 2301: System temporarily unavailable. 1656 o 2302: Unexpected internal system or server error. 1658 8.5. Reject Route Group Offers Operation 1660 Not until access to a Route Group has been offered and accepted will 1661 the data recipient's organization ID be included in the peeringOrg 1662 list in that Route Group object, and that Route Group's peering 1663 information become a candidate for inclusion in the responses to the 1664 resolution requests submitted by that data recipient. However, the 1665 data recipient that the Route Group has been offered to has the 1666 option of rejecting a Route Group Offer that has been offered but not 1667 accepted or that has been offered and accepted. The 1668 rejectRteGrpOffersRqst operation is used for these purposes and is 1669 called by, or on behalf of, the data recipient to accept one or more 1670 Route Group Offers that are pending in the "offered" status or the 1671 "accepted" status for the data recipient's organization ID. If a 1672 Route Group Offer for the given Route Group Offer key (route name, 1673 route registrant ID, data recipient's organization ID) exists in 1674 either the offered or accepted status, then the server deletes that 1675 Route Group Offer object , and, if appropriate, removes the data 1676 recipients organization ID from the list of peerOrgIds for that Route 1677 Group. If the Route Group Offer does not exist, then the server 1678 returns the appropriate error code 2105. The XSD declarations for 1679 the operation request object are as follows: 1681 1684 1685 1686 1687 1688 1690 1691 1692 1693 1695 The element passed into the spppRequest element for this operation is 1696 the rejectRteGrpOffersRqst element. This element is of type 1697 RejectRteGrpOffersRqstType, which extends BasicRqstType and contains 1698 one or more RteGrpOfferKeyType objects. Any limitation on the 1699 maximum number of objects that may be passed into or returned by this 1700 operation is a policy decision and not limited by the protocol. 1702 The result of rejectRteGrpOffersRqst is the rejectRteGrpOffersRspns 1703 element defined below. As with all SPPP requests, the result is all- 1704 or-nothing. If more than one RteGrpOfferKeyType is passed into this 1705 request, then they will either all succeed or all fail. In the case 1706 of failure, the failure response code(s) and message(s) will indicate 1707 the reason for the failure and the object(s) that caused the failure. 1709 1712 The response codes that the rejectRteGrpOffersRspns operation can 1713 return are as follows: 1715 o 1000: Request Succeeded. 1717 o 2001: Request syntax invalid. 1719 o 2002: Request too large. 1721 o 2003: Version not supported. 1723 o 2103: Command invalid. 1725 o 2104: Attribute value invalid. 1727 o 2105: Object does not exist. 1729 o 2106: Object status or ownership does not allow for request. 1731 o 2301: System temporarily unavailable. 1733 o 2302: Unexpected internal system or server error. 1735 8.6. Get Route Group Offers Operation 1737 The getRteGrpOffersRqst operation allows a client to get the 1738 properties of zero or more Route Group Offer objects that that 1739 registrar is authorized to view. The server will attempt to find 1740 Route Group Offer objects that has all the properties specified in 1741 the criteria passed into the operation. If no criteria is passed in 1742 then the server will return the list of Route Group Offer objects 1743 that the querying client has the authority to view. If there are no 1744 matching Route Group Offers found then an empty result set will be 1745 returned. 1747 The element passed into the spppRequest element for this operation is 1748 the getRteGrpOffersRqst element. This element is of type 1749 GetRteGrpOffersRqstType, which extends BasicRqstType and contains the 1750 criteria that the returnedRoute Group Offer objects must match. Any 1751 limitation on the maximum number of objects that may be passed into 1752 or returned by this operation is a policy decision and not limited by 1753 the protocol. The XSD declaration of the operation is as follows: 1755 1758 1759 1760 1761 1762 1764 1766 1768 1770 1772 1773 1774 1775 1777 The GetRteGrpOffersRqstType object is composed of the following 1778 elements: 1780 o offeredByPeers: Zero or one boolean value that, if true, 1781 indicates that only offers that are offered by peering 1782 organizations to the querying registrant should be included in 1783 the result set. If this value is false, the offers by peering 1784 organizations to the querying registrant should not be included 1785 in the result set. The result set is also subject to other 1786 query criteria in the request. 1788 o offeredToPeers: Zero or one boolean value that, if true, 1789 indicates that only offers that are offered to peering 1790 organizations by the querying registrant should be included in 1791 the result set. If this value is false, the offers to peering 1792 organizations by the querying registrant should not be included 1793 in the result set. The result set is also subject to other 1794 query criteria in the request. 1796 o status: The status of the offer, offered or accepted. Only 1797 offers in the specified status should be included in the result 1798 set. If this element is not present then the status of the 1799 offer should not be considered in the query. The result set is 1800 also subject to other query criteria in the request. 1802 o peeringOrg: Zero or more organization IDs. Only offers that are 1803 offered to or offered by the organization IDs in this list 1804 should be included in the result set. The result set is also 1805 subject to other query criteria in the request. 1807 o rteGrpOfferKey: Zero or more Route Group Offer Keys. Only 1808 offers having one of these keys should be included in the result 1809 set. The result set is also subject to other query criteria in 1810 the request. 1812 The result of the getRteGrpOffersRqst operation returned in the 1813 spppResponse element is the getRteGrpOffersRspns element defined 1814 below. This object contains the resulting set of RteGrpOfferType 1815 objects, or an empty set if there were no matches. 1817 1820 1821 1822 1823 1824 1826 1827 1828 1829 1831 The response codes that the getRteGrpOffersRqst operation can return 1832 are as follows: 1834 o 1000: Request Succeeded. 1836 o 2001: Request syntax invalid. 1838 o 2002: Request too large. 1840 o 2003: Version not supported. 1842 o 2103: Command invalid. 1844 o 2104: Attribute value invalid. 1846 o 2301: System temporarily unavailable. 1848 o 2302: Unexpected internal system or server error. 1850 8.7. Public Identifier Operations 1852 Public Identifier is a well-known attribute that is used as the 1853 search key to find the routes associated with it. There are three 1854 types of public identifiers defined in this document: TNType for the 1855 telephone number, EmailType for the email address, and RNType for 1856 PSTN routing number. Further, TNRangeType is used to add a range of 1857 telephone numbers. 1859 8.7.1. Add Public Identifier 1861 addPubIdsRqst operation is used to create or overwrite one or more 1862 public identifier(s). When activating a new public identifier that 1863 can be reached using a common set of routes, it is often associated 1864 with a well-known destination group. In some cases, such as the 1865 email public identifier, the routing information is unique, and 1866 therefore, addPubIdsRqst allows the public identifier to be directly 1867 associated with a route record. 1869 PubIdType in the schema represents the public identifier and it is 1870 defined as an abstract type. TNType, EmailType, and RNType, the 1871 concrete types of PubIdType, are inputs to 'addPubIdRqst' operation. 1872 The declaration of 'addPubIdsRqst' is as follows: 1874 1875 1876 1877 1878 1879 1881 1882 1883 1884 1886 For the 'addPubIdsRqst' operation to succeed, each public identifier 1887 should be associated with at least a valid destination group or a 1888 valid route type as defined within the PubIdType definition. If not, 1889 the provisioning server will deem the request a failure and return an 1890 appropriate failure code in the response. 1892 TNType is a concrete public identifier that extends PubIdType 1893 definition. If the entity provisioning the telephone number is the 1894 carrier of record [see RFC 5067], then it SHOULD include the 1895 'corClaim' element with a value 'true'. If the SPPP server records 1896 disagree with the COR claim of the provisioning entity, an 1897 appropriate failure response MUST be returned. 1899 1900 1901 1902 1903 1905 1906 1907 1908 1909 1910 1911 1912 1914 1915 1916 1917 1919 For added flexibility, there is support to add a range of telephone 1920 numbers and associate them with a destination group. TNRType extends 1921 TNType and adds the 'endTn' attribute to mark the end of the range. 1922 In the TNRType context, the extended 'tn' attribute is used for the 1923 starting TN of a given telephone number range. 1925 1926 1927 1928 1929 1930 1931 1932 1933 1935 The element passed into the spppRequest element for this operation is 1936 the addPubIdsRqst element. This element is of type 1937 AddPubIdsRqstType, which extends BasicRqstType and contians one or 1938 more PubIdType objects. Any limitation on the maximum number of 1939 PubIdType objects that may be passed into this operatoin is a policy 1940 decision and is not limited by the protocol. 1942 The response from the server is returned in addPubIdsRspns element. 1943 If more than one public identifiers are passed in the addPubIdsRqst, 1944 then a failure to add one will result in the failure of addPubIdsRqst 1945 operation. If the 'transactional' attribute is set to 'true' in the 1946 root element spppRequest and more than one operation request elements 1947 are included, then a failure of any one operation will result in the 1948 overall failure of spppRequest. In the case of a failure, the 1949 response code(s) and message(s) will indicate the reason of failure. 1951 1953 The response codes that the addRteGrpsRqst operation can return are 1954 as follows: 1956 o 1000: Request Succeeded. 1958 o 2001: Request syntax invalid. 1960 o 2002: Request too large. 1962 o 2003: Version not supported. 1964 o 2103: Command invalid. 1966 o 2104: Attribute value invalid. 1968 o 2105: Object does not exist. 1970 o 2106: Object status or ownership does not allow for request. 1972 o 2301: System temporarily unavailable. 1974 o 2302: Unexpected internal system or server error. 1976 8.7.2. Get Public Identifier 1978 The getPubIdsRqst can be used by an authorized entity to obtain the 1979 properties of one or more public identifiers. In case of an 1980 authorization failure or if no matching public identifiers are found, 1981 an appropriate failure code will be returned. 1983 To make a successful query, getPubIdsRqst element is set within the 1984 spppRequest root element. getPubIdsRqst is of type GetPubIdsRqstType, 1985 which extends from the common BasicRqstType. 1987 1988 1989 1990 1991 1992 1994 1995 1996 1997 1999 The result of the getPubIdsRqst operation returned in the 2000 spppResponse element is the getPubIdsRspns element of type 2001 GetPubIdsRspnsType. If the matching record is found, getPubIdsRspns 2002 element will include one or more pi elements with destination group 2003 name and/or the route record associations. 2005 2006 2007 2008 2009 2010 2012 2013 2014 2015 2017 The response codes that the addRteGrpsRqst operation can return are 2018 as follows: 2020 o 1000: Request Succeeded. 2022 o 2001: Request syntax invalid. 2024 o 2002: Request too large. 2026 o 2003: Version not supported. 2028 o 2103: Command invalid. 2030 o 2104: Attribute value invalid. 2032 o 2105: Object does not exist. 2034 o 2106: Object status or ownership does not allow for request. 2036 o 2301: System temporarily unavailable. 2038 o 2302: Unexpected internal system or server error. 2040 8.7.3. Delete Public Identifier 2042 In order to remove the public identifier, an authorized entity can 2043 use the delPubIdsRqst operation. If the entity that issued the 2044 command is not authorized to perform this operation or if the public 2045 identifier doesn't exist, an appropriate error code will be returned 2046 in the response. 2048 delPubIdsRqst element is set in the root spppRequest element. 2049 delPubIdsRqst element is of type DelPubIdsRqstType as shown below: 2051 2052 2053 2054 2055 2056 2058 2059 2060 2061 2063 The result of the delPubIdsRqst operation returned in the 2064 spppResponse element is the getPubIdsRspns element of type 2065 GetPubIdsRspnsType. 2067 2069 8.8. Egress Route Operations 2071 8.8.1. Add Egress Route 2073 8.8.2. Get Egress Route 2075 8.8.3. Delete Egress Route 2076 9. Security Considerations 2078 The transport protocol section contains some security properties that 2079 the transport protocol must provide so that authenticated endpoints 2080 can exchange data confidentially and with integrity protection. 2082 More details will be provided in a future revision of this document. 2084 10. IANA Considerations 2086 This document uses URNs to describe XML namespaces and XML schemas 2087 conforming to a registry mechanism described in [RFC3688]. 2089 Two URI assignments are requested. 2091 Registration request for the SPPP XML namespace: 2092 urn:ietf:params:xml:ns:sppp:base:1 2093 Registrant Contact: IESG 2094 XML: None. Namespace URIs do not represent an XML specification. 2096 Registration request for the XML schema: 2097 URI: urn:ietf:params:xml:schema:sppp:1 2098 Registrant Contact: IESG 2099 XML: See the "Formal Specification" section of this document 2100 (Section 11). 2102 11. Formal Specification 2104 This section provides the draft XML Schema Definition for the SPPP 2105 protocol. Please read Section 3.4 for known issues. 2107 2108 2112 2113 ------------------ Object Type Definitions 2114 -------------- 2115 2116 2117 2118 2119 2120 2122 2124 2126 2128 2129 2130 2131 2132 2133 2134 2135 2136 2137 2138 2139 2140 2141 2142 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2210 2211 2212 2213 2214 2215 2216 2217 2218 2219 2220 2221 2222 2223 2224 2225 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 ------------------ Abstract Object and Element 2250 Type Definitions -------------- 2251 2252 2253 2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 2283 2284 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 2295 2296 2298 2299 2300 2301 2302 2303 2304 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323 2324 2325 2326 2327 2328 2329 2330 2332 2333 2334 2335 2336 2337 2338 2339 2340 2341 2342 2343 2344 2345 2347 2348 2349 2350 2351 2352 2354 2355 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2369 2370 2371 2372 2373 2374 2375 2376 2377 -------------- Operation Request and Response 2378 Object Type Definitions ------------ 2379 2380 2381 2382 2383 2384 2386 2388 2389 2390 2391 2392 2393 2394 2395 2397 2398 2399 2400 2401 2402 2403 2404 2405 2407 2408 2409 2410 2411 2412 2413 2414 2415 2417 2418 2419 2420 2421 2422 2423 2424 2425 2427 2428 2429 2430 2431 2432 2433 2434 2435 2437 2438 2439 2440 2441 2442 2443 2444 2445 2447 2448 2449 2450 2451 2452 2453 2454 2455 2457 2458 2459 2460 2461 2462 2463 2464 2465 2467 2468 2469 2470 2471 2472 2473 2474 2475 2477 2478 2479 2480 2481 2482 2483 2484 2485 2487 2488 2489 2490 2491 2492 2493 2494 2495 2497 2498 2499 2500 2501 2502 2503 2504 2505 2507 2508 2509 2510 2511 2512 2513 2514 2515 2517 2518 2519 2520 2521 2522 2523 2524 2525 2527 2528 2529 2530 2531 2532 2533 2534 2535 2537 2538 2539 2540 2541 2542 2543 2544 2545 2546 2547 2549 2551 2554 2555 2556 2557 2558 2559 2560 2561 2562 2564 2565 2566 2567 2568 2569 2570 2571 2572 2574 2575 2576 2577 2578 2579 2580 2581 2582 2584 2585 2586 2587 2588 2589 2590 2591 2592 2594 2595 2596 2597 2598 2599 2600 2601 2602 2604 2605 2606 2607 2608 2609 2610 2611 2612 2613 2614 2615 2616 2617 2618 2619 2620 2621 2622 2623 -------------- Operation Request and Response 2624 Element Definitions ------------ 2625 2626 2627 -------------- Manage Route Groups 2628 2629 2630 2631 2632 2633 2634 2635 2636 2637 -------------- Manage Destination Groups 2638 2639 2640 2641 2642 2643 2644 2645 2647 2648 -------------- Manage Public Identifiers 2649 2650 2651 2652 2653 2654 2655 2656 2657 2658 -------------- Manage Route Group Offers 2659 2660 2661 2663 2665 2667 2669 2671 2672 2673 2674 2675 2677 2678 -------------- Manage Egress Routes 2679 2680 2681 2682 2683 2684 2685 2686 2687 2688 -------------- Misc Operations 2689 2690 2691 2692 2693 -------- Generic Request and Response Definitions 2694 --------------- 2695 2696 2697 2698 2699 2700 2701 2702 2703 2704 2705 2706 2707 2708 2709 2710 2711 2712 12. Specification Extensibility 2714 The protocol defined in this specification is extensible. This 2715 section explains how to extend the protocol and what procedures are 2716 necessary to follow in order to ensure proper extensions. 2718 13. Acknowledgments 2720 This document is a result of various discussions held in the DRINKS 2721 working group and within the DRINKS protocol design team, which is 2722 comprised of the following individuals, in alphabetical order: 2723 Deborah A Guyton (Telcordia), Sumanth Channabasappa (CableLabs), 2724 Jean-Francois Mule (CableLabs), Kenneth Cartwright (TNSI), Manjul 2725 Maharishi (TNSI), David Schwartz (XConnect), and the co-chairs 2726 Richard Shockey and Alexander Mayrhofer (enum.at GmbH). 2728 The authors of this document thank the following individuals for 2729 their advice, reviews and comments during the development of this 2730 protocol: Lisa Dusseault, "YOUR NAME HERE" -- send comments to drinks 2731 list. 2733 14. References 2735 14.1. Normative References 2737 [I-D.ietf-drinks-sppp-over-soap] 2738 Cartwright, K., "SPPP Over SOAP and HTTP", 2739 draft-ietf-drinks-sppp-over-soap-00 (work in progress), 2740 June 2010. 2742 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2743 Requirement Levels", BCP 14, RFC 2119, March 1997. 2745 [RFC2277] Alvestrand, H., "IETF Policy on Character Sets and 2746 Languages", BCP 18, RFC 2277, January 1998. 2748 [RFC2781] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO 2749 10646", RFC 2781, February 2000. 2751 [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 2752 10646", STD 63, RFC 3629, November 2003. 2754 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 2755 January 2004. 2757 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 2758 Resource Identifier (URI): Generic Syntax", STD 66, 2759 RFC 3986, January 2005. 2761 14.2. Informative References 2763 [I-D.ietf-drinks-usecases-requirements] 2764 Channabasappa, S., "DRINKS Use cases and Protocol 2765 Requirements", draft-ietf-drinks-usecases-requirements-03 2766 (work in progress), May 2010. 2768 [RFC2821] Klensin, J., "Simple Mail Transfer Protocol", RFC 2821, 2769 April 2001. 2771 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 2772 A., Peterson, J., Sparks, R., Handley, M., and E. 2773 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 2774 June 2002. 2776 [RFC3761] Faltstrom, P. and M. Mealling, "The E.164 to Uniform 2777 Resource Identifiers (URI) Dynamic Delegation Discovery 2778 System (DDDS) Application (ENUM)", RFC 3761, April 2004. 2780 [RFC4725] Mayrhofer, A. and B. Hoeneisen, "ENUM Validation 2781 Architecture", RFC 4725, November 2006. 2783 [RFC5486] Malas, D. and D. Meyer, "Session Peering for Multimedia 2784 Interconnect (SPEERMINT) Terminology", RFC 5486, 2785 March 2009. 2787 Authors' Addresses 2789 Jean-Francois Mule 2790 CableLabs 2791 858 Coal Creek Circle 2792 Louisville, CO 80027 2793 USA 2795 Email: jfm@cablelabs.com 2797 Kenneth Cartwright 2798 TNS 2799 1939 Roland Clarke Place 2800 Reston, VA 20191 2801 USA 2803 Email: kcartwright@tnsi.com 2805 Syed Wasim Ali 2806 NeuStar 2807 46000 Center Oak Plaza 2808 Sterling, VA 20166 2809 USA 2811 Email: syed.ali@neustar.biz 2813 Alexander Mayrhofer 2814 enum.at GmbH 2815 Karlsplatz 1/9 2816 Wien, A-1010 2817 Austria 2819 Email: alexander.mayrhofer@enum.at