idnits 2.17.1 draft-ietf-drinks-spp-framework-02.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 exact meaning of the all-uppercase expression 'MAY NOT' is not defined in RFC 2119. If it is intended as a requirements expression, it should be rewritten using one of the combinations defined in RFC 2119; otherwise it should not be all-uppercase. == The expression 'MAY NOT', while looking like RFC 2119 requirements text, is not defined in RFC 2119, and should not be used. Consider using 'MUST NOT' instead (if that is what you mean). Found 'MAY NOT' in this paragraph: In some deployments, the SPPF objects that an SPPF registry manages can be private in nature. As a result it MAY NOT be appropriate to for transmission in plain text over a connection to the SPPF registry. Therefore, the transport protocol SHOULD provide means for end-to-end encryption between the SPPF client and server. -- The document date (July 16, 2012) is 4292 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) == Unused Reference: 'RFC5321' is defined on line 2454, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 4949 ** Downref: Normative reference to an Informational RFC: RFC 5067 -- Obsolete informational reference (is this intentional?): RFC 2616 (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) -- Obsolete informational reference (is this intentional?): RFC 5246 (Obsoleted by RFC 8446) Summary: 2 errors (**), 0 flaws (~~), 4 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DRINKS K. Cartwright 3 Internet-Draft V. Bhatia 4 Intended status: Standards Track TNS 5 Expires: January 17, 2013 S. Ali 6 NeuStar 7 D. Schwartz 8 XConnect 9 July 16, 2012 11 Session Peering Provisioning Framework (SPPF) 12 draft-ietf-drinks-spp-framework-02 14 Abstract 16 This document specifies the data model and the overall structure for 17 a framework to provision session establishment data into Session Data 18 Registries and SIP Service Provider data stores. The framework is 19 called the Session Peering Provisioning Framework (SPPF). The 20 provisioned data is typically used by network elements for session 21 peering. 23 Status of this Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on January 17, 2013. 40 Copyright Notice 42 Copyright (c) 2012 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 58 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 7 59 3. Framework High Level Design . . . . . . . . . . . . . . . . . 9 60 3.1. Framework Data Model . . . . . . . . . . . . . . . . . . . 9 61 3.2. Time Value . . . . . . . . . . . . . . . . . . . . . . . . 12 62 4. Transport Protocol Requirements . . . . . . . . . . . . . . . 13 63 4.1. Connection Oriented . . . . . . . . . . . . . . . . . . . 13 64 4.2. Request and Response Model . . . . . . . . . . . . . . . . 13 65 4.3. Connection Lifetime . . . . . . . . . . . . . . . . . . . 13 66 4.4. Authentication . . . . . . . . . . . . . . . . . . . . . . 13 67 4.5. Authorization . . . . . . . . . . . . . . . . . . . . . . 14 68 4.6. Confidentiality and Integrity . . . . . . . . . . . . . . 14 69 4.7. Near Real Time . . . . . . . . . . . . . . . . . . . . . . 14 70 4.8. Request and Response Sizes . . . . . . . . . . . . . . . . 14 71 4.9. Request and Response Correlation . . . . . . . . . . . . . 14 72 4.10. Request Acknowledgement . . . . . . . . . . . . . . . . . 14 73 4.11. Mandatory Transport . . . . . . . . . . . . . . . . . . . 15 74 5. Base Framework Data Structures and Response Codes . . . . . . 16 75 5.1. Basic Object Type and Organization Identifiers . . . . . . 16 76 5.2. Various Object Key Types . . . . . . . . . . . . . . . . . 16 77 5.2.1. Generic Object Key Type . . . . . . . . . . . . . . . 17 78 5.2.2. Derived Object Key Types . . . . . . . . . . . . . . . 17 79 5.3. Response Message Types . . . . . . . . . . . . . . . . . . 19 80 6. Framework Data Model Objects . . . . . . . . . . . . . . . . . 22 81 6.1. Destination Group . . . . . . . . . . . . . . . . . . . . 22 82 6.2. Public Identifier . . . . . . . . . . . . . . . . . . . . 23 83 6.3. SED Group . . . . . . . . . . . . . . . . . . . . . . . . 28 84 6.4. SED Record . . . . . . . . . . . . . . . . . . . . . . . . 32 85 6.5. SED Group Offer . . . . . . . . . . . . . . . . . . . . . 36 86 6.6. Egress Route . . . . . . . . . . . . . . . . . . . . . . . 38 87 7. Framework Operations . . . . . . . . . . . . . . . . . . . . . 41 88 7.1. Add Operation . . . . . . . . . . . . . . . . . . . . . . 41 89 7.2. Delete Operation . . . . . . . . . . . . . . . . . . . . . 41 90 7.3. Get Operations . . . . . . . . . . . . . . . . . . . . . . 42 91 7.4. Accept Operations . . . . . . . . . . . . . . . . . . . . 42 92 7.5. Reject Operations . . . . . . . . . . . . . . . . . . . . 43 93 7.6. Get Server Details Operation . . . . . . . . . . . . . . . 43 94 8. XML Considerations . . . . . . . . . . . . . . . . . . . . . . 44 95 8.1. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 44 96 8.2. Versioning and Character Encoding . . . . . . . . . . . . 44 97 9. Security Considerations . . . . . . . . . . . . . . . . . . . 45 98 9.1. Confidentiality and Authentication . . . . . . . . . . . . 45 99 9.2. Authorization . . . . . . . . . . . . . . . . . . . . . . 45 100 9.3. Denial of Service . . . . . . . . . . . . . . . . . . . . 45 101 9.3.1. DoS Issues Inherited from Transport Mechanism . . . . 45 102 9.3.2. DoS Issues Specific to SPPF . . . . . . . . . . . . . 46 103 9.4. Information Disclosure . . . . . . . . . . . . . . . . . . 47 104 9.5. Non Repudiation . . . . . . . . . . . . . . . . . . . . . 47 105 9.6. Replay Attacks . . . . . . . . . . . . . . . . . . . . . . 47 106 9.7. Man in the Middle . . . . . . . . . . . . . . . . . . . . 47 107 10. Internationalization Considerations . . . . . . . . . . . . . 49 108 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50 109 12. Formal Specification . . . . . . . . . . . . . . . . . . . . . 51 110 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 60 111 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 61 112 14.1. Normative References . . . . . . . . . . . . . . . . . . . 61 113 14.2. Informative References . . . . . . . . . . . . . . . . . . 61 114 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 63 116 1. Introduction 118 Service providers and enterprises use registries to make session 119 routing decisions for Voice over IP, SMS and MMS traffic exchanges. 120 This document is narrowly focused on the provisioning framework for 121 these registries. This framework prescribes a way for an entity to 122 provision session-related data into a registry. The data being 123 provisioned can be optionally shared with other participating peering 124 entities. The requirements and use cases driving this framework have 125 been documented in [RFC6461]. The reader is expected to be familiar 126 with the terminology defined in the previously mentioned document. 128 Three types of provisioning flows have been described in the use case 129 document: client to registry provisioning, registry to local data 130 repository and registry to registry. This document addresses client 131 to registry aspect to fulfill the need to provision Session 132 Establishment Data (SED). The framework that supports flow of 133 messages to facilitate client to registry provisioning is referred to 134 as Session Peering Provisioning Framework (SPPF). 136 Please note that the role of the "client" and the "server" only 137 applies to the connection, and those roles are not related in any way 138 to the type of entity that participates in a protocol exchange. For 139 example, a registry might also include a "client" when such a 140 registry initiates a connection (for example, for data distribution 141 to SSP). 143 *--------* *------------* *------------* 144 | | (1). Client | | (3).Registry | | 145 | Client | ------------> | Registry |<------------->| Registry | 146 | | to Registry | | to Registry | | 147 *--------* *------------* *------------* 148 / \ \ 149 / \ \ 150 / \ \ 151 / \ v 152 / \ ... 153 / \ 154 / (2). Distrib \ 155 / Registry data \ 156 / to local data \ 157 V store V 158 +----------+ +----------+ 159 |Local Data| |Local Data| 160 |Repository| |Repository| 161 +----------+ +----------+ 163 Three Registry Provisioning Flows 165 Figure 1 167 The data provisioned for session establishment is typically used by 168 various downstream SIP signaling systems to route a call to the next 169 hop associated with the called domain. These systems typically use a 170 local data store ("Local Data Repository") as their source of session 171 routing information. More specifically, the SED data is the set of 172 parameters that the outgoing signaling path border elements (SBEs) 173 need to initiate the session. See [RFC5486] for more details. 175 A "terminating" SIP Service Provider (SSP) provisions SED into the 176 registry to be selectively shared with other peer SSPs. 177 Subsequently, a registry may distribute the provisioned data into 178 local data repositories used for look-up queries (identifier -> URI) 179 or for lookup and location resolution (identifier -> URI -> ingress 180 SBE of terminating SSP). In some cases, the registry may 181 additionally offer a central query resolution service (not shown in 182 the above figure). 184 A key requirement for the SPPF is to be able to accommodate two basic 185 deployment scenarios: 187 1. A resolution system returns a Look-Up Function (LUF) that 188 comprises the target domain to assist in call routing (as 189 described in [RFC5486]). In this case, the querying entity may 190 use other means to perform the Location Routing Function (LRF) 191 which in turn helps determine the actual location of the 192 Signaling Function in that domain. 194 2. A resolution system returns a Location Routing Function (LRF) 195 that comprises the location (address) of the signaling function 196 in the target domain (as described in [RFC5486]). 198 In terms of framework design, SPPF is agnostic to the transport 199 protocol. This document includes the specification of the data model 200 and identifies, but does not specify, the means to enable protocol 201 operations within a request and response structure. That aspect of 202 the specification has been delegated to the "protocol" specification 203 for the framework. To encourage interoperability, the framework 204 supports extensibility aspects. 206 Transport requirements are provided in this document to help with the 207 selection of the optimum transport mechanism. The SPP Protocol over 208 SOAP document identifies a protocol for SPPF that uses SOAP/HTTP as 209 the transport mechanism. 211 This document is organized as follows: 213 o Section 2 provides the terminology; 215 o Section 3 provides an overview of SPPF, including functional 216 entities and data model; 218 o Section 4 specifies requirements for SPPF transport protocols; 220 o Section 5 describes the base framework data structures, the 221 generic response types that MUST be supported by a conforming 222 "protocol" specification, and the basic object type most first 223 class objects extend from; 225 o Section 6 detailed description of the data model object 226 specifications; 228 o Section 8 defines XML considerations XML parsers must meet to 229 conform to this specification; 231 o Section 12 normatively defines the SPPF using its XML Schema 232 Definition. 234 2. Terminology 236 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 237 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 238 document are to be interpreted as described in [RFC2119]. 240 This document reuses terms from [RFC3261], [RFC5486], use cases and 241 requirements documented in [RFC6461] and the ENUM Validation 242 Architecture [RFC4725]. 244 In addition, this document specifies the following additional terms: 246 SPPF: Session Peering Provisioning Framework, the framework used by 247 a transport protocol to provision data into a Registry (see arrow 248 labeled "1." in Figure 1 of [RFC6461]). It is the primary scope 249 of this document. 251 SPDP: Session Peering Distribution Protocol, the protocol used to 252 distribute data to Local Data Repository (see arrow labeled "2." 253 in Figure 1 of [RFC6461]). 255 Client: An application that supports an SPPF client; it is 256 sometimes referred to as a "registry client". 258 Registry: The Registry operates a master database of Session 259 Establishment Data for one or more Registrants. 261 A Registry acts as an SPPF server. 263 Registrant: In this document we extend the definition of a 264 Registrant based on [RFC4725]. The Registrant is the end-user, 265 the person or organization that is the "holder" of the Session 266 Establishment Data being provisioned into the Registry by a 267 Registrar. For example, in [RFC6461], a Registrant is pictured as 268 a SIP Service Provider in Figure 2. 270 Within the confines of a Registry, a Registrant is uniquely 271 identified by a well-known ID. 273 Registrar: In this document we extend the definition of a Registrar 274 from [RFC4725]. A Registrar is an entity that performs 275 provisioning operations on behalf of a Registrant by interacting 276 with the Registry via SPPF operations. In other words the 277 Registrar is the SPPF Client. The Registrar and Registrant roles 278 are logically separate to allow, but not require, a single 279 Registrar to perform provisioning operations on behalf of more 280 than one Registrant. 282 Peering Organization: A Peering Organization is an entity to which 283 a Registrant's SED Groups are made visible using the operations of 284 SPPF. 286 3. Framework High Level Design 288 This section introduces the structure of the data model and provides 289 the information framework for the SPPF. The data model is defined 290 along with all the objects manipulated by the protocol and their 291 relationships. 293 3.1. Framework Data Model 295 The data model illustrated and described in Figure 2 defines the 296 logical objects and the relationships between these objects that the 297 SPPF protocol supports. SPPF defines the protocol operations through 298 which an SPPF client populates a registry with these logical objects. 299 Various clients belonging to different registrars may use the 300 protocol for populating the registry's data. 302 The logical structure presented below is consistent with the 303 terminology and requirements defined in [RFC6461]. 305 +-------------+ +-----------------+ 306 | all object | |Egress Route: | 307 | types | 0..n | rant, | 308 +-------------+ +--| egrRteName, | 309 |0..n / | pref, | 310 | / | regxRewriteRule,| 311 |2 / | ingrSedGrp, | 312 +----------------------+ / | svcs | 313 |Organization: | / +-----------------+ 314 | orgId | / 315 +----------------------+ / 316 |0..n / 317 | / 318 |A SED Group is / 319 |associated with / 320 |zero or more / +---[abstract]----+ 321 |Peering / | SED Record: | 322 |Organizations / | rant, | 323 | / | sedName, |0..n 324 |0..n / | sedFunction, |------| 325 +--------+--------------+0..n 0..n| isInSvc, | | 326 |SED Group: |------------------| ttl | | 327 | rant, | +-----------------+ | 328 | sedGrpName, | ^ | 329 | isInSvc, | |Various types | 330 | sedRecRef, | |of SED | 331 | peeringOrg, | |Records | 332 | sourceIdent, | +-----+------------+ | 333 | priority, | | | | | 334 | dgName | +----+ +-------+ +----+ | 335 +-----------------------+ | URI| | NAPTR | | NS | | 336 |0..n +----+ +-------+ +----+ | 337 | | 338 | +-----[abstract]------+ | 339 | |Public Identifier: | | 340 |0..n | rant, | | 341 +----------------------+0..n 0..n| publicIdentifier, | | 342 | Dest Group: |--------------| destGrpRef, | | 343 | rant, | | sedRecRef | | 344 | dgName | +---------------------+ | 345 +----------------------+ ^Various types | 346 |of Public | 347 |Identifiers | 348 +---------+-------+------+----------+ | 349 | | | | | | 350 +------+ +-----+ +-----+ +-----+ +------+ | 351 | URI | | TNP | | TNR | | RN | |TN |----------| 352 +------+ +-----+ +-----+ +-----+ +------+ 0..n 353 Figure 2 355 The objects and attributes that comprise the data model can be 356 described as follows (objects listed from the bottom up): 358 o Public Identifier: 359 From a broad perspective a public identifier is a well-known 360 attribute that is used as the key to perform resolution lookups. 361 Within the context of SPPF, a public identifier object can be a 362 Telephone Number (TN), a range of Telephone Numbers, a PSTN 363 Routing Number (RN), a TN prefix, or a URI. 365 An SPPF Public Identifier is associated with a Destination Group 366 to create a logical grouping of Public Identifiers that share a 367 common set of Session Establishment Data (e.g. routes). 369 A TN Public Identifier may optionally be associated with zero or 370 more individual SED Records. This ability for a Public Identifier 371 to be directly associated with a SED Record, as opposed to being 372 associated with a Destination Group, supports the use cases where 373 the SED Record contains data specifically tailored to an 374 individual TN Public Identifier. 376 o Destination Group: 377 A named collection of zero or more Public Identifiers that can be 378 associated with one or more SED Groups for the purpose of 379 facilitating the management of their common session establishment 380 information. 382 o SED Group: 383 A SED Group contains a set of SED Record references, a set of 384 Destination Group references, and a set of peering organization 385 identifiers. This is used to establish a three part relationships 386 between a set of Public Identifiers, the session establishment 387 information (SED) shared across these Public Identifiers, and the 388 list of peering organizations whose query responses from the 389 resolution system may include the session establishment 390 information contained in a given SED group. In addition, the 391 sourceIdent element within a SED Group, in concert with the set of 392 peering organization identifiers, enables fine-grained source 393 based routing. For further details about the SED Group and source 394 based routing, refer to the definitions and descriptions of the 395 SED Group operations found later in this document. 397 o SED Record: 398 A SED Record contains the data that a resolution system returns in 399 response to a successful query for a Public Identifier. SED 400 Records are generally associated with a SED Group when the SED 401 within is not specific to a Public Identifier. 402 To support the use cases defined in [RFC6461], SPPF framework 403 defines three type of SED Records: URIType, NAPTRType, and NSType. 404 These SED Records extend the abstract type SedRecType and inherit 405 the common attribute 'priority' that is meant for setting 406 precedence across the SED records defined within a SED Group in a 407 protocol agnostic fashion. 409 o Egress Route: 410 In a high-availability environment, the originating SSP likely has 411 more than one egress paths to the ingress SBE of the target SSP. 412 The Egress Route allows the originating SSP to choose a specific 413 egress SBE to be associated with the target ingress SBE. the 414 'svcs' element identifies the SED records associated with the SED 415 Group that will be modified by the originating SSP. 417 o Organization: 418 An Organization is an entity that may fulfill any combination of 419 three roles: Registrant, Registrar, and Peering Organization. All 420 objects in SPPF framework are associated with two organization 421 identifiers to identify each object's registrant and registrar. A 422 SED Group object is also associated with a set of zero or more 423 organization identifiers that identify the peering organization(s) 424 whose resolution query responses may include the session 425 establishment information (SED) defined in the SED Records within 426 that SED Group. A peering organization is an entity that the 427 registrant intends to share the SED data with. 429 3.2. Time Value 431 Some request and response messages in SPPF framework include time 432 value(s) defined as type xs:dateTime, a built-in W3C XML Schema 433 Datatype. Use of unqualified local time value is discouraged as it 434 can lead to interoperability issues. The value of time attribute 435 MUST BE expressed in Coordinated Universal Time (UTC) format without 436 the timezone digits. 438 "2010-05-30T09:30:10Z" is an example of an acceptable time value for 439 use in SPPF messages. "2010-05-30T06:30:10+3:00" is a valid UTC time, 440 but it is not approved for use in SPPF messages. 442 4. Transport Protocol Requirements 444 This section provides requirements for transport protocols suitable 445 for SPPF framework. More specifically, this section specifies the 446 services, features, and assumptions that SPPF framework delegates to 447 the chosen transport and envelope technologies. 449 4.1. Connection Oriented 451 The SPPF follows a model where a client establishes a connection to a 452 server in order to further exchange SPPF messages over such point-to- 453 point connection. A transport protocol for SPPF MUST therefore be 454 connection oriented. 456 4.2. Request and Response Model 458 Provisioning operations in SPPF follow the request-response model, 459 where a client sends a request message to initiate a transaction and 460 the server responds with a response. Multiple subsequent request- 461 response exchanges MAY be performed over a single persistent 462 connection. 464 Therefore, a transport protocol for SPPF MUST follow the request- 465 response model by allowing a response to be sent to the request 466 initiator. 468 4.3. Connection Lifetime 470 Some use cases involve provisioning a single request to a network 471 element. Connections supporting such provisioning requests might be 472 short-lived, and may be established only on demand. Other use cases 473 involve either provisioning a large dataset, or a constant stream of 474 small updates, either of which would likely require long-lived 475 connections. 477 Therefore, a protocol suitable for SPPF SHOULD be able to support 478 both short-lived as well as long-lived connections. 480 4.4. Authentication 482 All SPPF objects are associated with a registrant identifier. SPPF 483 Clients provisions SPPF objects on behalf of registrants. An 484 authenticated SPP Client is a registrar. Therefore, the SPPF 485 transport protocol MUST provide means for an SPPF server to 486 authenticate an SPPF Client. 488 4.5. Authorization 490 After successful authentication of the SPPF client as a registrar the 491 registry performs authorization checks to determine if the registrar 492 is authorized to act on behalf of the Registrant whose identifier is 493 included in the SPPF request. Refer to the Security Considerations 494 section for further guidance. 496 4.6. Confidentiality and Integrity 498 In some deployments, the SPPF objects that an SPPF registry manages 499 can be private in nature. As a result it MAY NOT be appropriate to 500 for transmission in plain text over a connection to the SPPF 501 registry. Therefore, the transport protocol SHOULD provide means for 502 end-to-end encryption between the SPPF client and server. 504 For some SPPF implementations, it may be acceptable for the data to 505 be transmitted in plain text, but the failure to detect a change in 506 data after it leaves the SPPF client and before it is received at the 507 server, either by accident or with a malicious intent, will adversely 508 affect the stability and integrity of the registry. Therefore, the 509 transport protocol SHOULD provide means for data integrity 510 protection. 512 4.7. Near Real Time 514 Many use cases require near real-time responses from the server. 515 Therefore, a DRINKS transport protocol MUST support near real-time 516 response to requests submitted by the client. 518 4.8. Request and Response Sizes 520 Use of SPPF may involve simple updates that may consist of small 521 number of bytes, such as, update of a single public identifier. 522 Other provisioning operations may constitute large number of dataset 523 as in adding millions records to a registry. As a result, a suitable 524 transport protocol for SPPF SHOULD accommodate dataset of various 525 sizes. 527 4.9. Request and Response Correlation 529 A transport protocol suitable for SPPF MUST allow responses to be 530 correlated with requests. 532 4.10. Request Acknowledgement 534 Data transported in the SPPF is likely crucial for the operation of 535 the communication network that is being provisioned. A SPPF client 536 responsible for provisioning SED to the registry has a need to know 537 if the submitted requests have been processed correctly. 539 Failed transactions can lead to situations where a subset of public 540 identifiers or even SSPs might not be reachable, or the provisioning 541 state of the network is inconsistent. 543 Therefore, a transport protocol for SPPF MUST provide a response for 544 each request, so that a client can identify whether a request 545 succeeded or failed. 547 4.11. Mandatory Transport 549 At the time of this writing, a choice of transport protocol has been 550 provided in SPP Protocol over SOAP document. To encourage 551 interoperability, the SPPF server MUST provide support for this 552 transport protocol. With time, it is possible that other transport 553 layer choices may surface that agree with the requirements discussed 554 above. 556 5. Base Framework Data Structures and Response Codes 558 SPPF contains some common data structures for most of the supported 559 object types. This section describes these common data structures. 561 5.1. Basic Object Type and Organization Identifiers 563 This section introduces the basic object type that most first class 564 objects derive from. 566 All first class objects extend the basic object type BasicObjType 567 that contains the identifier of the registrant organization that owns 568 this object, the identifier of the registrar organization that 569 created this object, the date and time that the object was created by 570 the server, and the date and time that the object was last modified. 572 573 574 575 576 577 578 579 580 582 The identifiers used for registrants (rant), registrars (rar), and 583 peering organizations (peeringOrg) are instances of OrgIdType. The 584 OrgIdType is defined as a string and all OrgIdType instances SHOULD 585 follow the textual convention: "namespace:value" (for example "iana- 586 en:32473"). See the IANA Consideration section for more details. 588 5.2. Various Object Key Types 590 The SPPF data model contains various object relationships. In some 591 cases, these object relationships are established by embedding the 592 unique identity of the related object inside the relating object. In 593 addition, an object's unique identity is required to Delete or Get 594 the details of an object. The following sub-sections normatively 595 define the various object keys in SPPF and the attributes of those 596 keys . 598 "Name" attributes that are used as components of object key types 599 MUST be treated case insensitive. 601 5.2.1. Generic Object Key Type 603 Most objects in SPPF are uniquely identified by an object key that 604 has the object's name, object's type and its registrant's 605 organization ID as its attributes. The abstract type called 606 ObjKeyType is where this unique identity is housed. Any concrete 607 representation of the ObjKeyType MUST contain the following: 609 Object Name: The name of the object. 611 Registrant Id: The unique organization ID that identifies the 612 Registrant. 614 Type: The value that represents the type of SPPF object that. 615 This is required as different types of objects in SPPF, that 616 belong to the same registrant, can have the same name. 618 The structure of abstract ObjKeyType is as follows: 620 621 622 623 ---- Generic type that represents the 624 key for various objects in SPPF. ---- 625 626 627 629 5.2.2. Derived Object Key Types 631 The SPPF data model contains certain objects that are uniquely 632 identified by attributes, different from or in addition to, the 633 attributes in the generic object key described in previous section. 634 These kind of object keys are derived from the abstract ObjKeyType 635 and defined in there own abstract key types. Because these object 636 key types are abstract, these MUST be specified in a concrete form in 637 any conforming SPPF "protocol" specification. These are used in 638 Delete and Get operations, and may also be used in Accept and Reject 639 operations. 641 Following are the derived object keys in SPPF data model: 643 o SedGrpOfferKeyType: This uniquely identifies a SED Group object 644 offer. This key type extends from ObjKeyType and MUST also have 645 the organization ID of the Registrant to whom the object is 646 being offered, as one of its attributes. In addition to the 647 Delete and Get operations, these key types are used in Accept 648 and Reject operations on a SED Group Offer object. The 649 structure of abstract SedGrpOfferKeyType is as follows: 651 653 654 655 656 657 ---- Generic type that represents 658 the key for a object offer. ---- 659 660 661 662 663 665 A SED Group Offer object MUST use SedGrpOfferKeyType. Refer the 666 "Framework Data Model Objects" section of this document for 667 description of SED Group Offer object. 669 o PubIdKeyType: This uniquely identifies a Public Identity object. 670 This key type extends from abstract ObjKeyType. Any concrete 671 definition of PubIdKeyType MUST contain the elements that 672 identify the value and type of Public Identity and also contain 673 the organization ID of the Registrant that is the owner of the 674 Public Identity object. A Public Identity object key in SPPF is 675 uniquely identified by the the registrant's organization ID, the 676 value of the public identity, and, optionally, the Destination 677 Group name the public identity belongs to. Consequently, any 678 concrete representation of the PubIdKeyType MUST contain the 679 following attributes: 681 * Registrant Id: The unique organization ID that identifies 682 the Registrant. 684 * Destination Group name: The name of the Destination Group 685 the Public Identity is associated with. This is an 686 optional attribute. 688 * Type: The type of Public Identity. 690 * Value: The value of the Public Identity. 692 The .PubIdKeyType is used in Delete and Get operations on a 693 Public Identifier object. 695 o The structure of abstract PubIdKeyType is as follows: 697 698 699 700 701 702 ---- Generic type that represents the key for a Pub Id. ---- 703 704 705 706 707 709 A Public Identity object MUST use attributes of PubIdKeyType for its 710 unique identification . Refer the "Framework Data Model Objects" 711 section of this document for a description of Public Identity object. 713 5.3. Response Message Types 715 This section contains the listing of response types that MUST be 716 defined by the conforming "protocol" specification and implemented by 717 a conforming SPPF server. 719 +---------------------+---------------------------------------------+ 720 | Response Type | Description | 721 +---------------------+---------------------------------------------+ 722 | Request Succeeded | Any conforming specification MUST define a | 723 | | response to indicate that a given request | 724 | | succeeded. | 725 | | | 726 | Request syntax | Any conforming specification MUST define a | 727 | invalid | response to indicate that a syntax of a | 728 | | given request was found invalid. | 729 | | | 730 | Request too large | Any conforming specification MUST define a | 731 | | response to indicate that the count of | 732 | | entities in the request is larger than the | 733 | | server is willing or able to process. | 734 | | | 735 | Version not | Any conforming specification MUST define a | 736 | supported | response to indicate that the server does | 737 | | not support the version of the SPPF | 738 | | protocol specified in the request. | 739 | | | 740 | Command invalid | Any conforming specification MUST define a | 741 | | response to indicate that the operation | 742 | | and/or command being requested by the | 743 | | client is invalid and/or not supported by | 744 | | the server. | 745 | | | 746 | System temporarily | Any conforming specification MUST define a | 747 | unavailable | response to indicate that the SPPF server | 748 | | is temporarily not available to serve | 749 | | client request. | 750 | | | 751 | Unexpected internal | Any conforming specification MUST define a | 752 | system or server | response to indicate that the SPPF server | 753 | error. | encountered an unexpected error that | 754 | | prevented the server from fulfilling the | 755 | | request. | 756 | | | 757 | Attribute value | Any conforming specification MUST define a | 758 | invalid | response to indicate that the SPPF server | 759 | | encountered an attribute or property in the | 760 | | request that had an invalid/bad value. | 761 | | Optionally, the specification MAY provide a | 762 | | way to indicate the Attribute Name and the | 763 | | Attribute Value to identify the object that | 764 | | was found to be invalid. | 765 | | | 766 | Object does not | Any conforming specification MUST define a | 767 | exist | response to indicate that an object present | 768 | | in the request does not exist on the SPPF | 769 | | server. Optionally, the specification MAY | 770 | | provide a way to indicate the Attribute | 771 | | Name and the Attribute Value that | 772 | | identifies the non-existent object. | 773 | | | 774 | Object status or | Any conforming specification MUST define a | 775 | ownership does not | response to indicate that the operation | 776 | allow for | requested on an object present in the | 777 | operation. | request cannot be performed because the | 778 | | object is in a status that does not allow | 779 | | the said operation or the user requesting | 780 | | the operation is not authorized to perform | 781 | | the said operation on the object. | 782 | | Optionally, the specification MAY provide a | 783 | | way to indicate the Attribute Name and the | 784 | | Attribute Value that identifies the object. | 785 +---------------------+---------------------------------------------+ 787 Table 1: Response Types 789 When the response messages are "parameterized" with the Attribute 790 Name and Attribute Value, then the use of these parameters MUST 791 adhere to the following rules: 793 o Any value provided for the Attribute Name parameter MUST be an 794 exact XSD element name of the protocol data element that the 795 response message is referring to. For example, valid values for 796 "attribute name" are "dgName", "sedGrpName", "sedRec", etc. 798 o The value for Attribute Value MUST be the value of the data 799 element to which the preceding Attribute Name refers. 801 o Response type "Attribute value invalid" SHOULD be used whenever 802 an element value does not adhere to data validation rules. 804 o Response types "Attribute value invalid" and "Object does not 805 exist" MUST NOT be used interchangeably. Response type "Object 806 does not exist" SHOULD be returned by an Add/Del/Accept/Reject 807 operation when the data element(s) used to uniquely identify a 808 pre-existing object do not exist. If the data elements used to 809 uniquely identify an object are malformed, then response type 810 "Attribute value invalid" SHOULD be returned. 812 6. Framework Data Model Objects 814 This section provides a description of the specification of each 815 supported data model object (the nouns) and identifies the commands 816 (the verbs) that MUST be supported for each data model object. 817 However, the specification of the data structures necessary to 818 support each command is delegated to the "protocol" specification. 820 6.1. Destination Group 822 As described in the introductory sections, a Destination Group 823 represents a set of Public Identifiers with common session 824 establishment information. The transport protocol MUST support the 825 ability to Create, Modify, Get, and Delete Destination Groups (refer 826 the "Framework Operations" section of this document for a generic 827 description of various operations). 829 A Destination Group object MUST be uniquely identified by attributes 830 as defined in the description of "ObjKeyType" in the section "Generic 831 Object Key Type" of this document. 833 The DestGrpType object structure is defined as follows: 835 836 837 838 839 840 841 842 843 845 The DestGrpType object is composed of the following elements: 847 o base: All first class objects extend BasicObjType that contains 848 the ID of the registrant organization that owns this object, 849 registrar organization that provisioned this object on behalf of 850 the registrant, the date and time that the object was created by 851 the server, and the date and time that the object was last 852 modified. If the client passed in either the created date or 853 the modification date, the server will ignore them. The server 854 sets these two date/time values. 856 o dgName: The character string that contains the name of the 857 Destination Group. 859 o ext: Point of extensibility described in a previous section of 860 this document. 862 6.2. Public Identifier 864 A Public Identifier is the search key used for locating the session 865 establishment data (SED). In many cases, a Public Identifier is 866 attributed to the end user who has a retail relationship with the 867 service provider or registrant organization. SPPF supports the 868 notion of the carrier-of-record as defined in [RFC5067]. Therefore, 869 the registrant under whom the Public Identity is being created can 870 optionally claim to be a carrier-of-record. 872 SPPF identifies three types of Public Identifiers: telephone numbers 873 (TN), routing numbers (RN), and URI type of Public Identifiers (like 874 an email address). SPPF provides structures to manage a single TN, a 875 contiguous range of TNs, and a TN prefix. The transport protocol 876 MUST support the ability to Create, Modify, Get, and Delete Public 877 Identifiers (refer the "Framework Operations" section of this 878 document for a generic description of various operations). 880 A Public Identity object MUST be uniquely identified by attributes as 881 defined in the description of "PubIdKeyType" in the section "Derived 882 Object Key Types" of this document. 884 The abstract XML schema type definition PubIDType is a generalization 885 for the concrete Public Identifier schema types. PubIDType element 886 'dgName' represents the name of the destination group that a given 887 Public Identifier MAY be a member of. The PubIDType object structure 888 is defined as follows: 890 891 892 893 894 895 896 897 898 900 A Public Identifier may be provisioned as a member of a Destination 901 Group or provisioned outside of a Destination Group. A Public 902 Identifier that is provisioned as a member of a Destination Group is 903 intended to be associated with its SED through the SED Group(s) that 904 are associated with its containing Destination Group. A Public 905 Identifier that is not provisioned as a member of a Destination Group 906 is intended to be associated with its SED through the SED Records 907 that are directly associated with the Public Identifier. 909 A telephone number is provisioned using the TNType, an extension of 910 PubIDType. When a Public Identifier is provisioned as a member of a 911 Destination Group, each TNType object is uniquely identified by the 912 combination of its value contained within element, and the 913 unique key of its parent Destination Group (dgName and rantId). In 914 other words a given telephone number string may exist within one or 915 more Destination Groups, but must not exist more than once within a 916 Destination Group. A Public Identifier that is not provisioned as a 917 member of a Destination Group is uniquely identified by the 918 combination of its value, and its registrant ID. TNType is defined 919 as follows: 921 922 923 924 925 926 927 929 930 931 932 934 935 936 937 938 939 941 TNType consists of the following attributes: 943 o tn: Telephone number to be added to the registry. 945 o sedRecRef: Optional reference to SED records that are directly 946 associated with the TN Public Identifier. Following the SPPF 947 data model, the SED record could be a protocol agnostic URIType 948 or another type. 950 o corInfo: corInfo is an optional parameter of type CORInfoType 951 that allows the registrant organization to set forth a claim to 952 be the carrier-of-record (see [RFC5067]). This is done by 953 setting the value of element of the CORInfoType 954 object structure to "true". The other two parameters of the 955 CORInfoType, and are set by the registry to 956 describe the outcome of the carrier-of-record claim by the 957 registrant. In general, inclusion of parameter is 958 useful if the registry has the authority information, such as, 959 the number portability data, etc., in order to qualify whether 960 the registrant claim can be satisfied. If the carrier-of-record 961 claim disagrees with the authority data in the registry, whether 962 the TN add operation fails or not is a matter of policy and it 963 is beyond the scope of this document. 965 A routing number is provisioned using the RNType, an extension of 966 PubIDType. SSPs that possess the number portability data may be able 967 to leverage the RN search key to discover the ingress routes for 968 session establishment. Therefore, the registrant organization can 969 add the RN and associate it with the appropriate destination group to 970 share the route information. Each RNType object is uniquely 971 identified by the combination of its value inside the element, 972 and the unique key of its parent Destination Group (dgName and 973 rantId). In other words a given routing number string may exist 974 within one or more Destination Groups, but must not exist more than 975 once within a Destination Group. RNType is defined as follows: 977 978 979 980 981 982 983 984 985 986 988 RNType has the following attributes: 990 o rn: Routing Number used as the search key. 992 o corInfo: Optional element of type CORInfoType. 994 TNRType structure is used to provision a contiguous range of 995 telephone numbers. The object definition requires a starting TN and 996 an ending TN that together define the span of the TN range. Use of 997 TNRType is particularly useful when expressing a TN range that does 998 not include all the TNs within a TN block or prefix. The TNRType 999 definition accommodates the open number plan as well such that the 1000 TNs that fall between the start and end TN range may include TNs with 1001 different length variance. Whether the registry can accommodate the 1002 open number plan semantics is a matter of policy and is beyond the 1003 scope of this document. Each TNRType object is uniquely identified 1004 by the combination of its value that in turn is a combination of the 1005 and elements, and the unique key of its parent 1006 Destination Group (dgName and rantId). In other words a given TN 1007 Range may exist within one or more Destination Groups, but must not 1008 exist more than once within a Destination Group. TNRType object 1009 structure definition is as follows: 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1022 1023 1024 1025 1026 1027 1029 TNRType has the following attributes: 1031 o startTn: Starting TN in the TN range 1033 o endTn: The last TN in the TN range 1035 o corInfo: Optional element of type CORInfoType 1037 In some cases, it is useful to describe a set of TNs with the help of 1038 the first few digits of the telephone number, also referred to as the 1039 telephone number prefix or a block. A given TN prefix may include 1040 TNs with different length variance in support of open number plan. 1041 Once again, whether the registry supports the open number plan 1042 semantics is a matter of policy and it is beyond the scope of this 1043 document. The TNPType data structure is used to provision a TN 1044 prefix. Each TNPType object is uniquely identified by the 1045 combination of its value in the element, and the unique 1046 key of its parent Destination Group (dgName and rantId). TNPType is 1047 defined as follows: 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1060 TNPType consists of the following attributes: 1062 o tnPrefix: The telephone number prefix 1064 o corInfo: Optional element of type CORInfoType. 1066 In some cases, a Public Identifier may be a URI, such as an email 1067 address. The URIPubIdType object is comprised of the data element 1068 necessary to house such Public Identifiers. Each URIPubIdType object 1069 is uniquely identified by the combination of its value in the 1070 element, and the unique key of its parent Destination Group (dgName 1071 and rantId). URIPubIdType is defined as follows: 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1084 URIPubIdType consists of the following attributes: 1086 o uri: The value that acts a Public Identifier. 1088 o ext: Point of extensibility. 1090 6.3. SED Group 1092 As described in the introductory sections, a SED Group represents a 1093 combined grouping of Destination Groups containing a set of Public 1094 Identifiers with common Session Establishment Data(SED), The common 1095 Session Establishment Data Records, and the list of peer 1096 organizations that have access to these public identifiers using the 1097 associated SED information. It is this indirect linking of public 1098 identifiers to their Session Establishment Data that significantly 1099 improves the scalability and manageability of the peering data. 1100 Additions and changes to SED information are reduced to a single 1101 operation on a SED Group or SED Record , rather than millions of data 1102 updates to individual public identifier records that individually 1103 contain their peering data. The transport protocol MUST support the 1104 ability to Create, Modify, Get, and Delete SED Groups (refer the 1105 "Framework Operations" section of this document for a generic 1106 description of various operations). 1108 A SED Group object MUST be uniquely identified by attributes as 1109 defined in the description of "ObjKeyType" in the section "Generic 1110 Object Key Type" of this document. 1112 The SedGrpType object structure is defined as follows: 1114 1115 1116 1117 1118 1119 1121 1123 1125 1127 1128 1129 1130 1131 1132 1133 1135 1136 1137 1138 1139 1140 1141 1143 The SedGrpType object is composed of the following elements: 1145 o base: All first class objects extend BasicObjType that contains 1146 the ID of the registrant organization that owns this object, the 1147 date and time that the object was created by the server, and the 1148 date and time that the object was last modified. If the client 1149 passes in either the created date or the modification date, the 1150 server will ignore them. The server sets these two date/time 1151 values. 1153 o sedGrpName: The character string that contains the name of the 1154 SED Group. It uniquely identifies this object within the 1155 context of the registrant ID (a child element of the base 1156 element as described above). 1158 o sedRecRef: Set of zero or more objects of type SedRecRefType 1159 that house the unique keys of the SED Records (containing the 1160 session establishment data) that the SedGrpType object refers to 1161 and their relative priority within the context of this SED 1162 Group. 1164 o dgName: Set of zero or more names of DestGrpType object 1165 instances. Each dgName name, in association with this SED 1166 Group's registrant ID, uniquely identifies a DestGrpType object 1167 instance whose public identifiers are reachable using the 1168 session establishment information housed in this SED Group. An 1169 intended side affect of this is that a SED Group cannot provide 1170 session establishment information for a Destination Group 1171 belonging to another registrant. 1173 o peeringOrg: Set of zero or more peering organization IDs that 1174 have accepted an offer to receive this SED Group's information. 1175 The set of peering organizations in this list is not directly 1176 settable or modifiable using the addSedGrpsRqst operation. This 1177 set is instead controlled using the SED offer and accept 1178 operations. 1180 o sourceIdent: Set of zero or more SourceIdentType object 1181 instances. These objects, described further below, house the 1182 source identification schemes and identifiers that are applied 1183 at resolution time as part of source based routing algorithms 1184 for the SED Group. 1186 o isInSvc: A boolean element that defines whether this SED Group 1187 is in service. The session establishment information contained 1188 in a SED Group that is in service is a candidate for inclusion 1189 in resolution responses for public identities residing in the 1190 Destination Group associated with this SED Group. The session 1191 establishment information contained in a SED Group that is not 1192 in service is not a candidate for inclusion in resolution 1193 responses. 1195 o priority: Zero or one priority value that can be used to provide 1196 a relative value weighting of one SED Group over another. The 1197 manner in which this value is used, perhaps in conjunction with 1198 other factors, is a matter of policy. 1200 o ext: Point of extensibility described in a previous section of 1201 this document. 1203 As described above, the SED Group contains a set of references to SED 1204 record objects. A SED record object is based on an abstract type: 1205 SedRecType. The concrete types that use SedRecType as an extension 1206 base are NAPTRType, NSType, and URIType. The definitions of these 1207 types are included the SED Record section of this document. 1209 The SedGrpType object provides support for source-based routing via 1210 the peeringOrg data element and more granular source base routing via 1211 the source identity element. The source identity element provides 1212 the ability to specify zero or more of the following in association 1213 with a given SED Group: a regular expression that is matched against 1214 the resolution client IP address, a regular expression that is 1215 matched against the root domain name(s), and/or a regular expression 1216 that is matched against the calling party URI(s). The result will be 1217 that, after identifying the visible SED Groups whose associated 1218 Destination Group(s) contain the lookup key being queried and whose 1219 peeringOrg list contains the querying organizations organization ID, 1220 the resolution server will evaluate the characteristics of the Source 1221 URI, and Source IP address, and root domain of the lookup key being 1222 queried. The resolution server then compares these criteria against 1223 the source identity criteria associated with the SED Groups. The 1224 session establishment information contained in SED Groups that have 1225 source based routing criteria will only be included in the resolution 1226 response if one or more of the criteria matches the source criteria 1227 from the resolution request. The Source Identity data element is of 1228 type SourceIdentType, whose structure is defined as follows: 1230 1231 1232 1233 1235 1236 1237 1239 1240 1241 1242 1243 1244 1245 1247 The SourceIdentType object is composed of the following data 1248 elements: 1250 o sourceIdentScheme: The source identification scheme that this 1251 source identification criteria applies to and that the 1252 associated sourceIdentRegex should be matched against. 1254 o sourceIdentRegex: The regular expression that should be used to 1255 test for a match against the portion of the resolution request 1256 that is dictated by the associated sourceIdentScheme. 1258 o ext: Point of extensibility described in a previous section of 1259 this document. 1261 6.4. SED Record 1263 As described in the introductory sections, a SED Group represents a 1264 combined grouping of SED Records that define session establishment 1265 information. However, SED Records need not be created to just serve 1266 a single SED Group. SED Records can be created and managed to serve 1267 multiple SED Groups. As a result, a change for example to the 1268 properties of a network node used for multiple routes, would 1269 necessitate just a single update operation to change the properties 1270 of that node. The change would then be reflected in all the SED 1271 Groups whose SED record set contains a reference to that node. The 1272 transport protocol MUST support the ability to Create, Modify, Get, 1273 and Delete SED Records (refer the "Framework Operations" section of 1274 this document for a generic description of various operations). 1276 A SED Record object MUST be uniquely identified by attributes as 1277 defined in the description of "ObjKeyType" in the section "Generic 1278 Object Key Type" of this document. 1280 The SedRecType object structure is defined as follows: 1282 1283 1284 1285 1286 1287 1289 1290 1291 1292 1293 1294 1296 1297 1298 1299 1300 1301 1303 The SedRecType object is composed of the following elements: 1305 o base: All first class objects extend BasicObjType that contains 1306 the ID of the registrant organization that owns this object, the 1307 date and time that the object was created by the server, and the 1308 date and time that the object was last modified. If the client 1309 passes in either the created date or the modification date, the 1310 server will ignore them. The server sets these two date/time 1311 values. 1313 o sedName: The character string that contains the name of the SED 1314 Record. It uniquely identifies this object within the context 1315 of the registrant ID (a child element of the base element as 1316 described above). 1318 o sedFunction: As described in [RFC6461], SED or Session 1319 Establishment Data falls primarily into one of two categories or 1320 functions, LUF and LRF. To remove any ambiguity as to the 1321 function a SED record is intended to provide, this optional 1322 element allows the provisioning party to make his or her 1323 intentions explicit. 1325 o isInSvc: A boolean element that defines whether this SED Record 1326 is in service or not. The session establishment information 1327 contained in a SED Record which is in service is a candidate for 1328 inclusion in resolution responses for Telephone Numbers that are 1329 either directly associated to this SED Record, or for Public 1330 Identities residing in a Destination Group that is associated to 1331 a SED Group which in turn has an association to this SED Record. 1333 o ttl: Number of seconds that an addressing server may cache a 1334 particular SED Record. 1336 As described above, SED records are based on an abstract type: 1337 SedRecType. The concrete types that use SedRecType as an extension 1338 base are NAPTRType, NSType, and URIType. The definitions of these 1339 types are included below. The NAPTRType object is comprised of the 1340 data elements necessary for a NAPTR that contains routing information 1341 for a SED Group. The NSType object is comprised of the data elements 1342 necessary for a DNS name server that points to another DNS server 1343 that contains the desired routing information. The NSType is 1344 relevant only when the resolution protocol is ENUM. The URIType 1345 object is comprised of the data elements necessary to house a URI. 1347 The data provisioned in a registry can be leveraged for many purposes 1348 and queried using various protocols including SIP, ENUM and others. 1349 As such, the resolution data represented by the SedRecords must be in 1350 a form suitable for transport using one of these protocols. In the 1351 NPATRType for example, if the URI is associated with a destination 1352 group, the user part of the replacement string that may require 1353 the Public Identifier cannot be preset. As a SIP Redirect, the 1354 resolution server will apply pattern on the input Public 1355 Identifier in the query and process the replacement string by 1356 substituting any back reference(s) in the to arrive at the 1357 final URI that is returned in the SIP Contact header. For an ENUM 1358 query, the resolution server will simply return the values of the 1359 and members of the URI. 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1376 1377 1378 1379 1380 1381 1383 1384 1385 1386 1387 1389 1390 1391 1392 1393 1394 1395 1397 1398 1399 1400 1401 1402 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1416 1417 1418 1419 1420 1421 1423 The NAPTRType object is composed of the following elements: 1425 o order: Order value in an ENUM NAPTR, relative to other NAPTRType 1426 objects in the same SED Group. 1428 o svcs: ENUM service(s) that are served by the SBE. This field's 1429 value must be of the form specified in [RFC6116] (e.g., E2U+ 1430 pstn:sip+sip). The allowable values are a matter of policy and 1431 not limited by this protocol. 1433 o regx: NAPTR's regular expression field. If this is not included 1434 then the Repl field must be included. 1436 o repl: NAPTR replacement field, should only be provided if the 1437 Regex field is not provided, otherwise the server will ignore it 1439 o ext: Point of extensibility described in a previous section of 1440 this document. 1442 The NSType object is composed of the following elements: 1444 o hostName: Fully qualified host name of the name server. 1446 o ipAddr: Zero or more objects of type IpAddrType. Each object 1447 holds an IP Address and the IP Address type, IPv4 or IP v6. 1449 o ext: Point of extensibility described in a previous section of 1450 this document. 1452 The URIType object is composed of the following elements: 1454 o ere: The POSIX Extended Regular Expression (ere) as defined in 1455 [RFC3986]. 1457 o uri: the URI as defined in [RFC3986]. In some cases, this will 1458 serve as the replacement string and it will be left to the 1459 resolution server to arrive at the final usable URI. 1461 6.5. SED Group Offer 1463 The list of peer organizations whose resolution responses can include 1464 the session establishment information contained in a given SED Group 1465 is controlled by the organization to which a SED Group object belongs 1466 (its registrant), and the peer organization that submits resolution 1467 requests (a data recipient, also know as a peering organization). 1468 The registrant offers access to a SED Group by submitting a SED Group 1469 Offer. The data recipient can then accept or reject that offer. Not 1470 until access to a SED Group has been offered and accepted will the 1471 data recipient's organization ID be included in the peeringOrg list 1472 in a SED Group object, and that SED Group's peering information 1473 become a candidate for inclusion in the responses to the resolution 1474 requests submitted by that data recipient. The transport protocol 1475 MUST support the ability to Create, Modify, Get, Delete, Accept and 1476 Reject SED Group Offers (refer the "Framework Operations" section of 1477 this document for a generic description of various operations). 1479 A SED Group Offer object MUST be uniquely identified by attributes as 1480 defined in the description of "SedGrpOfferKeyType" in the section 1481 "Derived Object Key Types" of this document. 1483 The SedGrpOfferType object structure is defined as follows: 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1499 1500 1501 1502 -- Generic type that represents the key for a SED group offer. Must 1503 be defined in concrete form in the transport specificaiton. -- 1504 1505 1506 1508 1509 1510 1511 1512 1513 1515 The SedGrpOfferType object is composed of the following elements: 1517 o base: All first class objects extend BasicObjType that contains 1518 the ID of the registrant organization that owns this object, the 1519 date and time that the object was created by the server, and the 1520 date and time that the object was last modified. If the client 1521 passed in either the created date or the modification date, the 1522 will ignore them. The server sets these two date/time values. 1524 o sedGrpOfferKey: The object that identifies the SED that is or 1525 has been offered and the organization that it is or has been 1526 offered to. 1528 o status: The status of the offer, offered or accepted. The 1529 server controls the status. It is automatically set to 1530 "offered" when ever a new SED Group Offer is added, and is 1531 automatically set to "accepted" if and when that offer is 1532 accepted. The value of the element is ignored when passed in by 1533 the client. 1535 o offerDateTime: Date and time in UTC when the SED Group Offer was 1536 added. 1538 o acceptDateTime: Date and time in UTC when the SED Group Offer 1539 was accepted. 1541 6.6. Egress Route 1543 In a high-availability environment, the originating SSP likely has 1544 more than one egress paths to the ingress SBE of the target SSP. If 1545 the originating SSP wants to exercise greater control and choose a 1546 specific egress SBE to be associated to the target ingress SBE, it 1547 can do so using the EgrRteType object. 1549 A Egress Route object MUST be uniquely identified by attributes as 1550 defined in the description of "ObjKeyType" in the section "Generic 1551 Object Key Type" of this document. 1553 Lets assume that the target SSP has offered as part of his session 1554 establishment data, to share one or more ingress routes and that the 1555 originating SSP has accepted the offer. In order to add the egress 1556 route to the registry, the originating SSP uses a valid regular 1557 expression to rewrite ingress route in order to include the egress 1558 SBE information. Also, more than one egress route can be associated 1559 with a given ingress route in support of fault-tolerant 1560 configurations. The supporting SPPF structure provides a way to 1561 include route precedence information to help manage traffic to more 1562 than one outbound egress SBE. 1564 The transport protocol MUST support the ability to Add, Modify, Get, 1565 and Delete Egress Routes (refer the "Framework Operations" section of 1566 this document for a generic description of various operations). The 1567 EgrRteType object structure is defined as follows: 1569 1570 1571 1572 1573 1574 1575 1576 1578 1579 1580 1581 1582 1583 1585 The EgrRteType object is composed of the following elements: 1587 o base: All first class objects extend BasicObjType that contains 1588 the ID of the registrant organization that owns this object, the 1589 date and time that the object was created by the server, and the 1590 date and time that the object was last modified. If the client 1591 passes in either the created date or the modification date, the 1592 server will ignore them. The server sets these two date/time 1593 values. 1595 o egrRteName: The name of the egress route. 1597 o pref: The preference of this egress route relative to other 1598 egress routes that may get selected when responding to a 1599 resolution request. 1601 o regxRewriteRule: The regular expression re-write rule that 1602 should be applied to the regular expression of the ingress 1603 NAPTR(s) that belong to the ingress route. 1605 o ingrSedGrp: The ingress SED group that the egress route should 1606 be used for. 1608 o svcs: ENUM service(s) that are served by an Egress Route. This 1609 element is used to identify the ingress NAPTRs associated with 1610 the SED Group to which an Egress Route's regxRewriteRule should 1611 be applied. If no ENUM service(s) are associated with an Egress 1612 Route, then the Egress Route's regxRewriteRule should be applied 1613 to all the NAPTRs associated with the SED Group. This field's 1614 value must be of the form specified in [RFC6116] (e.g., E2U+ 1615 pstn:sip+sip). The allowable values are a matter of policy and 1616 not limited by this protocol. 1618 o ext: Point of extensibility described in a previous section of 1619 this document. 1621 7. Framework Operations 1623 7.1. Add Operation 1625 Any conforming "protocol" specification MUST provide a definition for 1626 the operation that adds one or more SPPF objects into the registry. 1627 If the object, as identified by the request attributes that form part 1628 of the object's key, does not exist, then the registry MUST create 1629 the object. If the object does exist, then the registry MUST replace 1630 the current properties of the object with the properties passed in as 1631 part of the Add operation. 1633 If the entity that issued the command is not authorized to perform 1634 this operation an appropriate error message MUST be returned from 1635 amongst the response messages defined in "Response Message Types" 1636 section of the document. 1638 7.2. Delete Operation 1640 Any conforming "protocol" specification MUST provide a definition for 1641 the operation that deletes one or more SPPF objects from the registry 1642 using the object's key. 1644 If the entity that issued the command is not authorized to perform 1645 this operation an appropriate error message MUST be returned from 1646 amongst the response messages defined in "Response Message Types" 1647 section of the document. 1649 When an object is deleted, any references to that object must of 1650 course also be removed as the SPPF server implementation fulfills the 1651 deletion request. Furthermore, the deletion of a composite object 1652 must also result in the deletion of the objects it contains. As a 1653 result, the following rules apply to the deletion of SPPF object 1654 types: 1656 o Destination Groups: When a destination group is deleted all 1657 public identifiers within that destination group must also be 1658 automatically deleted by the SPPF implementation as part of 1659 fulfilling the deletion request. And any references between 1660 that destination group and any SED group must be automatically 1661 removed by the SPPF implementation as part of fulfilling the 1662 deletion request. 1664 o SED Groups: When a SED group is deleted any references between 1665 that SED group and any destination group must be automatically 1666 removed by the SPPF implementation as part of fulfilling the 1667 deletion request. Similarly any references between that SED 1668 group and any SED records must be removed by the SPPF 1669 implementation as part of fulfilling the deletion request. 1670 Furthermore, SED group offers relating that SED group must also 1671 be deleted as part of fulfilling the deletion request. 1673 o SED Records: When a SED record is deleted any references between 1674 that SED record and any SED group must be removed by the SPPF 1675 implementation as part of fulfilling the deletion request. 1677 o Public Identifiers: When a public identifier is deleted any 1678 references between that public identifier and its containing 1679 destination group must be removed by the SPPF implementation as 1680 part of fulfilling the deletion request. Any SED records 1681 contained directly within that Public Identifier must be deleted 1682 by the SPPF implementation as part of fulfilling the deletion 1683 request. 1685 7.3. Get Operations 1687 At times, on behalf of the registrant, the registrar may need to have 1688 access to SPPF objects that were previously provisioned in the 1689 registry. A few examples include logging, auditing, and pre- 1690 provisioning dependency checking. This query mechanism is limited to 1691 aid provisioning scenarios and should not be confused with query 1692 protocols provided as part of the resolution system (e.g. ENUM and 1693 SIP). Any conforming "protocol" specification MUST provide a 1694 definition for the operation that queries the details of one or more 1695 SPPF objects from the registry using the object's key. If the entity 1696 that issued the command is not authorized to perform this operation 1697 an appropriate error message MUST be returned from amongst the 1698 response messages defined in "Response Message Types" section of the 1699 document. 1701 7.4. Accept Operations 1703 In SPPF, a SED Group Offer can be accepted or rejected by, or on 1704 behalf of, the registrant to whom the SED Group has been offered 1705 (refer "Framework Data Model Objects" section of this document for a 1706 description of the SED Group Offer object). The Accept operation is 1707 used to accept the SED Group Offers. Any conforming "protocol" 1708 specification MUST provide a definition for the operation to accept 1709 SED Group Offers by, or on behalf of the Registrant, using the SED 1710 Group Offer object key. 1712 Not until access to a SED Group has been offered and accepted will 1713 the registrant's organization ID be included in the peeringOrg list 1714 in that SED Group object, and that SED Group's peering information 1715 become a candidate for inclusion in the responses to the resolution 1716 requests submitted by that registrant. A SED Group Offer that is in 1717 the "offered" status is accepted by, or on behalf of, the registrant 1718 to which it has been offered. When the SED Group Offer is accepted 1719 the the SED Group Offer is moved to the "accepted" status and adds 1720 that data recipient's organization ID into the list of peerOrgIds for 1721 that SED Group. 1723 If the entity that issued the command is not authorized to perform 1724 this operation an appropriate error message MUST be returned from 1725 amongst the response messages defined in "Response Message Types" 1726 section of the document. 1728 7.5. Reject Operations 1730 In SPPF, a SED Group Offer object can be accepted or rejected by, or 1731 on behalf of, the registrant to whom the SED Group has been offered 1732 (refer "Framework Data Model Objects" section of this document for a 1733 description of the SED Group Offer object). Furthermore, that offer 1734 may be rejected, regardless of whether or not it has been previously 1735 accepted. The Reject operation is used to reject the SED Group 1736 Offers. When the SED Group Offer is rejected that SED Group Offer is 1737 deleted, and, if appropriate, the data recipient's organization ID is 1738 removed from the list of peeringOrg IDs for that SED Group. Any 1739 conforming "protocol" specification MUST provide a definition for the 1740 operation to reject SED Group Offers by, or on behalf of the 1741 Registrant, using the SED Group Offer object key. 1743 If the entity that issued the command is not authorized to perform 1744 this operation an appropriate error message MUST be returned from 1745 amongst the response messages defined in "Response Message Types" 1746 section of the document. 1748 7.6. Get Server Details Operation 1750 In SPPF, Get Server Details operation can be used to request certain 1751 details about the SPPF server that include the SPPF server's current 1752 status, the major/minor version of the SPPF protocol supported by the 1753 SPPF server. 1755 Any conforming "protocol" specification MUST provide a definition for 1756 the operation to request such details from the SPPF server. If the 1757 entity that issued the command is not authorized to perform this 1758 operation an appropriate error message MUST be returned from amongst 1759 the response messages defined in "Response Message Types" section of 1760 the document. 1762 8. XML Considerations 1764 XML serves as the encoding format for SPPF, allowing complex 1765 hierarchical data to be expressed in a text format that can be read, 1766 saved, and manipulated with both traditional text tools and tools 1767 specific to XML. 1769 XML is case sensitive. Unless stated otherwise, XML specifications 1770 and examples provided in this document MUST be interpreted in the 1771 character case presented to develop a conforming implementation. 1773 This section discusses a small number of XML-related considerations 1774 pertaining to SPPF. 1776 8.1. Namespaces 1778 All SPPF elements are defined in the namespaces in the IANA 1779 Considerations section and in the Formal Framework Specification 1780 section of this document. 1782 8.2. Versioning and Character Encoding 1784 All XML instances SHOULD begin with an declaration to 1785 identify the version of XML that is being used, optionally identify 1786 use of the character encoding used, and optionally provide a hint to 1787 an XML parser that an external schema file is needed to validate the 1788 XML instance. 1790 Conformant XML parsers recognize both UTF-8 (defined in [RFC3629]) 1791 and UTF-16 (defined in [RFC2781]); per [RFC2277] UTF-8 is the 1792 RECOMMENDED character encoding for use with SPPF. 1794 Character encodings other than UTF-8 and UTF-16 are allowed by XML. 1795 UTF-8 is the default encoding assumed by XML in the absence of an 1796 "encoding" attribute or a byte order mark (BOM); thus, the "encoding" 1797 attribute in the XML declaration is OPTIONAL if UTF-8 encoding is 1798 used. SPPF clients and servers MUST accept a UTF-8 BOM if present, 1799 though emitting a UTF-8 BOM is NOT RECOMMENDED. 1801 Example XML declarations: 1803 1805 9. Security Considerations 1807 Many SPPF implementations manage data that is considered confidential 1808 and critical. Furthermore, SPPF implementations can support 1809 provisioning activities for multiple registrars and registrants. As 1810 a result any SPPF implementation must address the requirements for 1811 confidentiality, authentication, and authorization. 1813 9.1. Confidentiality and Authentication 1815 With respect to confidentiality and authentication, the transport 1816 protocol requirements section of this document contains security 1817 properties that the transport protocol must provide so that 1818 authenticated endpoints can exchange data confidentially and with 1819 integrity protection. Refer to that section and the resulting 1820 transport protocol specification document for the specific solutions 1821 to authentication and confidentiality. 1823 9.2. Authorization 1825 With respect to authorization, the SPPF server implementation must 1826 define and implement a set of authorization rules that precisely 1827 address (1) which registrars will be authorized to create/modify/ 1828 delete each SPPF object type for given registrant(s) and (2) which 1829 registrars will be authorized to view/get each SPPF object type for 1830 given registrant(s). These authorization rules are a matter of 1831 policy and are not specified within the context of SPPF. However, 1832 any SPPF implementation must specify these authorization rules in 1833 order to function in a reliable and safe manner. 1835 9.3. Denial of Service 1837 Guidance on Denial-of-Service (DoS) issues in general is given in 1838 [RFC4732], "Internet Denial of Service Considerations", which also 1839 gives a general vocabulary for describing the DoS issue. 1841 SPPF is a high-level client-server protocol that can be implemented 1842 on lower-level mechanisms such as remote procedure call and web- 1843 service API protocols. As such, it inherits any Denial-of-Service 1844 issues inherent to the specific lower-level mechanism used for any 1845 implementation of SPPF. SPPF also has its own set of higher-level 1846 exposures that are likely to be independent of lower-layer mechanism 1847 choices. 1849 9.3.1. DoS Issues Inherited from Transport Mechanism 1851 SPPF implementation is in general dependent on the selection and 1852 implementation of a lower-level transport protocol and a binding 1853 between that protocol and SPPF. The archetypal SPPF implementation 1854 uses XML (http://www.w3.org/TR/xml/) representation in a SOAP 1855 (http://www.w3.org/TR/soap/) request/response framework over HTTP 1856 ([RFC2616]), and probably also uses TLS ([RFC5246]) for on-the wire 1857 data integrity and participant authentication, and might use HTTP 1858 Digest authentication ([RFC2609]). 1860 The typical deployment scenario for SPPF is to have servers in a 1861 managed facility, and therefor techniques such as Network Ingress 1862 Filtering ([RFC2609]) are generally applicable. In short, any DoS 1863 mechanism affecting a typical HTTP implementation would affect such 1864 an SPPF implementation, and the mitigation tools for HTTP in general 1865 also therefore apply to SPPF. 1867 SPPF does not directly specify an authentication mechanism, instead 1868 relying on the lower-level transport protocol to provide for 1869 authentication. In general, authentication is an expensive 1870 operation, and one apparent attack vector is to flood an SPPF server 1871 with repeated requests for authentication, thereby exhausting its 1872 resources. SPPF implementations SHOULD therefore be prepared to 1873 handle authentication floods, perhaps by noting repeated failed login 1874 requests from a given source address and blocking that source 1875 address. 1877 9.3.2. DoS Issues Specific to SPPF 1879 The primary defense mechanism against DoS within SPPF is 1880 authentication. Implementations MUST tightly control access to the 1881 SPPF service, SHOULD implement DoS and other policy control 1882 screening, and MAY employ a variety of policy violation reporting and 1883 response measures such as automatic blocking of specific users and 1884 alerting of operations personnel. In short, the primary SPPF 1885 response to DoS-like activity by a user is to block that user or 1886 subject their actions to additional review. 1888 SPPF allows a client to submit multiple-element or "batch" requests 1889 that may insert or otherwise affect a large amount of data with a 1890 single request. In the simplest case, the server progresses 1891 sequentially through each element in a batch, completing one and 1892 before starting the next. Mid-batch failures are handled by stopping 1893 the batch and rolling-back the data store to its pre-request state. 1894 This "stop and roll-back" design provides a DoS opportunity. A 1895 hostile client could repeatedly issue large batch requests with one 1896 or more failing elements, causing the server to repeatedly stop and 1897 roll-back large transactions. The suggested response is to monitor 1898 clients for such failures, and take administrative action (such as 1899 blocking the user) when an excessive number of roll-backs is 1900 reported. 1902 An additional suggested response is for an implementer to set their 1903 maximum allowable XML message size, and their maximum allowable batch 1904 size at a level that they feel protects their operational instance, 1905 given the hardware sizing they have in place and the expected load 1906 and size needs that their users expect. 1908 9.4. Information Disclosure 1910 It is not uncommon for the logging systems to document on-the-wire 1911 messages for various purposes, such as, debug, audit, and tracking. 1912 At the minimum, the various support and administration staff will 1913 have access to these logs. Also, if an unprivileged user gains 1914 access to the SPPF deployments and/or support systems, it will have 1915 access to the information that is potentially deemed confidential. 1916 To manage information disclosure concerns beyond the transport level, 1917 SPPF implementations MAY provide support for encryption at the SPPF 1918 object level. 1920 9.5. Non Repudiation 1922 In some situations, it may be required to protect against denial of 1923 involvement (see [RFC4949]) and tackle non-repudiation concerns in 1924 regards to SPPF messages. This type of protection is useful to 1925 satisfy authenticity concerns related to SPPF messages beyond the 1926 end-to-end connection integrity, confidentiality, and authentication 1927 protection that the transport layer provides. This is an optional 1928 feature and some SPPF implementations MAY provide support for it. 1930 9.6. Replay Attacks 1932 Anti-replay protection ensures that a given SPPF object replayed at a 1933 later time doesn't affect the integrity of the system. SPPF provides 1934 at least one mechanism to fight against replay attacks. Use of the 1935 optional client transaction identifier allows the SPPF client to 1936 correlate the request message with the response and to be sure that 1937 it is not a replay of a server response from earlier exchanges. Use 1938 of unique values for the client transaction identifier is highly 1939 encouraged to avoid chance matches to a potential replay message. 1941 9.7. Man in the Middle 1943 The SPPF client or registrar can be a separate entity acting on 1944 behalf of the registrant in facilitating provisioning transactions to 1945 the registry. Further, the transport layer provides end-to-end 1946 connection protection between SPPF client and the SPPF server. 1947 Therefore, man-in-the-middle attack is a possibility that may affect 1948 the integrity of the data that belongs to the registrant and/or 1949 expose peer data to unintended actors in case well-established 1950 peering relationships already exist. 1952 10. Internationalization Considerations 1954 Character encodings to be used for SPPF elements are described in 1955 Section 8.2. The use of time elements in the protocol is specified 1956 in Section 3.2. Where human-readable languages are used in the 1957 protocol, those messages SHOULD be tagged according to [RFC5646], and 1958 the transport protocol MUST support a respective mechanism to 1959 transmit such tags together with those human-readable messages. If 1960 tags are absent, the language of the message defaults to "en" 1961 (English). 1963 11. IANA Considerations 1965 This document uses URNs to describe XML namespaces and XML schemas 1966 conforming to a registry mechanism described in [RFC3688]. 1968 Two URI assignments are requested. 1970 Registration request for the SPPF XML namespace: 1971 urn:ietf:params:xml:ns:sppf:base:1 1972 Registrant Contact: IESG 1973 XML: None. Namespace URIs do not represent an XML specification. 1975 Registration request for the XML schema: 1976 URI: urn:ietf:params:xml:schema:sppf:1 1977 Registrant Contact: IESG 1978 XML: See the "Formal Specification" section of this document 1979 (Section 12). 1981 IANA is requested to create a new SPPF registry for Organization 1982 Identifiers that will indicate valid strings to be used for well- 1983 known enterprise namespaces. 1984 This document makes the following assignments for the OrgIdType 1985 namespaces: 1987 Namespace OrgIdType namespace string 1988 ---- ---------------------------- 1989 IANA Enterprise Numbers iana-en 1991 12. Formal Specification 1993 This section provides the draft XML Schema Definition for SPPF 1994 Protocol. 1996 1997 2001 2002 2003 ---- Generic Object key types to be defined by specific 2004 Transport/Architecture. The types defined here can 2005 be extended by the specific architecture to 2006 define the Object Identifiers ---- 2007 2008 2009 2011 2012 2013 ---- Generic type that represents the 2014 key for various objects in SPPF. ---- 2015 2016 2017 2019 2020 2021 2022 2023 2024 ---- Generic type that represents 2025 the key for a SED group offer. ---- 2026 2027 2028 2029 2030 2032 2033 2034 2035 2036 2037 ----Generic type that 2038 represents the key 2039 for a Pub Id. ---- 2040 2041 2042 2043 2044 2046 2047 2048 ---- Object Type Definitions ---- 2049 2050 2052 2053 2054 2055 2056 2057 2059 2061 2063 2065 2066 2067 2069 2070 2071 2072 2073 2074 2075 2076 2077 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 2119 2120 2121 2122 2123 2124 2125 2126 2127 2128 2129 2130 2131 2132 2133 2134 2135 2136 2137 2138 2139 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2178 2179 2180 2181 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 2215 2217 2218 2219 2220 2221 2222 2223 2224 2225 ---- Abstract Object and Element Type Definitions ---- 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 2256 2257 2258 2259 2260 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2280 2281 2282 2283 2284 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 2295 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 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 2331 2332 2333 2334 2335 2336 2337 2338 2339 2340 2341 2342 2343 2344 2345 2346 2347 2348 2349 2350 2351 2352 2353 2354 2355 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2369 2370 2371 2372 2373 2374 2375 2377 2378 2379 2380 2381 2382 2383 2384 2385 2386 2387 2388 2389 2390 2392 13. Acknowledgments 2394 This document is a result of various discussions held in the DRINKS 2395 working group and within the DRINKS protocol design team, with 2396 contributions from the following individuals, in alphabetical order: 2397 Alexander Mayrhofer, David Schwartz, Deborah A Guyton, Lisa 2398 Dusseault, Manjul Maharishi, Mickael Marrache, Otmar Lendl, Richard 2399 Shockey, Samuel Melloul, Sumanth Channabasappa, Syed Ali, and Vikas 2400 Bhatia . 2402 14. References 2404 14.1. Normative References 2406 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2407 Requirement Levels", BCP 14, RFC 2119, March 1997. 2409 [RFC2277] Alvestrand, H., "IETF Policy on Character Sets and 2410 Languages", BCP 18, RFC 2277, January 1998. 2412 [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 2413 10646", STD 63, RFC 3629, November 2003. 2415 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 2416 January 2004. 2418 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 2419 Resource Identifier (URI): Generic Syntax", STD 66, 2420 RFC 3986, January 2005. 2422 [RFC4949] Shirey, R., "Internet Security Glossary, Version 2", 2423 RFC 4949, August 2007. 2425 [RFC5067] Lind, S. and P. Pfautz, "Infrastructure ENUM 2426 Requirements", RFC 5067, November 2007. 2428 14.2. Informative References 2430 [RFC2609] Guttman, E., Perkins, C., and J. Kempf, "Service Templates 2431 and Service: Schemes", RFC 2609, June 1999. 2433 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., 2434 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext 2435 Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. 2437 [RFC2781] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO 2438 10646", RFC 2781, February 2000. 2440 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 2441 A., Peterson, J., Sparks, R., Handley, M., and E. 2442 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 2443 June 2002. 2445 [RFC4725] Mayrhofer, A. and B. Hoeneisen, "ENUM Validation 2446 Architecture", RFC 4725, November 2006. 2448 [RFC4732] Handley, M., Rescorla, E., and IAB, "Internet Denial-of- 2449 Service Considerations", RFC 4732, December 2006. 2451 [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security 2452 (TLS) Protocol Version 1.2", RFC 5246, August 2008. 2454 [RFC5321] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321, 2455 October 2008. 2457 [RFC5486] Malas, D. and D. Meyer, "Session Peering for Multimedia 2458 Interconnect (SPEERMINT) Terminology", RFC 5486, 2459 March 2009. 2461 [RFC5646] Phillips, A. and M. Davis, "Tags for Identifying 2462 Languages", BCP 47, RFC 5646, September 2009. 2464 [RFC6116] Bradner, S., Conroy, L., and K. Fujiwara, "The E.164 to 2465 Uniform Resource Identifiers (URI) Dynamic Delegation 2466 Discovery System (DDDS) Application (ENUM)", RFC 6116, 2467 March 2011. 2469 [RFC6461] Channabasappa, S., "Data for Reachability of Inter-/ 2470 Intra-NetworK SIP (DRINKS) Use Cases and Protocol 2471 Requirements", RFC 6461, January 2012. 2473 Authors' Addresses 2475 Kenneth Cartwright 2476 TNS 2477 1939 Roland Clarke Place 2478 Reston, VA 20191 2479 USA 2481 Email: kcartwright@tnsi.com 2483 Vikas Bhatia 2484 TNS 2485 1939 Roland Clarke Place 2486 Reston, VA 20191 2487 USA 2489 Email: vbhatia@tnsi.com 2491 Syed Wasim Ali 2492 NeuStar 2493 46000 Center Oak Plaza 2494 Sterling, VA 20166 2495 USA 2497 Email: syed.ali@neustar.biz 2499 David Schwartz 2500 XConnect 2501 316 Regents Park Road 2502 London, N3 2XJ 2503 United Kingdom 2505 Email: dschwartz@xconnect.net