idnits 2.17.1 draft-ietf-drinks-spp-framework-08.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. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: o Response types "Attribute value invalid" and "Object does not exist" MUST not be used interchangeably. Response type "Object does not exist" MUST be returned by an Update/Del/Accept/Reject operation when the data element(s) used to uniquely identify a pre-existing object do not exist. If the data elements used to uniquely identify an object are malformed, then response type "Attribute value invalid" MUST be returned. -- The document date (October 22, 2014) is 3473 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: 'RFC3403' is defined on line 2457, but no explicit reference was found in the text == Unused Reference: 'RFC5321' is defined on line 2474, 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 normative reference: RFC 5226 (Obsoleted by RFC 8126) -- 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 3761 (Obsoleted by RFC 6116, RFC 6117) -- Obsolete informational reference (is this intentional?): RFC 5246 (Obsoleted by RFC 8446) Summary: 3 errors (**), 0 flaws (~~), 5 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: April 25, 2015 S. Ali 6 NeuStar 7 D. Schwartz 8 XConnect 9 October 22, 2014 11 Session Peering Provisioning Framework (SPPF) 12 draft-ietf-drinks-spp-framework-08 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 establishment. 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 April 25, 2015. 40 Copyright Notice 42 Copyright (c) 2014 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 . . . . . . . . . . . . . . . . . . . . . . . . 3 58 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 59 3. Framework High Level Design . . . . . . . . . . . . . . . . . 7 60 3.1. Framework Data Model . . . . . . . . . . . . . . . . . . 7 61 3.2. Time Value . . . . . . . . . . . . . . . . . . . . . . . 10 62 3.3. Extensibility . . . . . . . . . . . . . . . . . . . . . . 10 63 4. Transport Protocol Requirements . . . . . . . . . . . . . . . 11 64 4.1. Connection Oriented . . . . . . . . . . . . . . . . . . . 11 65 4.2. Request and Response Model . . . . . . . . . . . . . . . 11 66 4.3. Connection Lifetime . . . . . . . . . . . . . . . . . . . 11 67 4.4. Authentication . . . . . . . . . . . . . . . . . . . . . 11 68 4.5. Authorization . . . . . . . . . . . . . . . . . . . . . . 12 69 4.6. Confidentiality and Integrity . . . . . . . . . . . . . . 12 70 4.7. Near Real Time . . . . . . . . . . . . . . . . . . . . . 12 71 4.8. Request and Response Sizes . . . . . . . . . . . . . . . 12 72 4.9. Request and Response Correlation . . . . . . . . . . . . 12 73 4.10. Request Acknowledgement . . . . . . . . . . . . . . . . . 12 74 4.11. Mandatory Transport . . . . . . . . . . . . . . . . . . . 13 75 5. Base Framework Data Structures and Response Codes . . . . . . 13 76 5.1. Basic Object Type and Organization Identifiers . . . . . 13 77 5.2. Various Object Key Types . . . . . . . . . . . . . . . . 14 78 5.2.1. Generic Object Key Type . . . . . . . . . . . . . . . 14 79 5.2.2. Derived Object Key Types . . . . . . . . . . . . . . 15 80 5.3. Response Message Types . . . . . . . . . . . . . . . . . 16 81 6. Framework Data Model Objects . . . . . . . . . . . . . . . . 18 82 6.1. Destination Group . . . . . . . . . . . . . . . . . . . . 18 83 6.2. Public Identifier . . . . . . . . . . . . . . . . . . . . 19 84 6.3. SED Group . . . . . . . . . . . . . . . . . . . . . . . . 24 85 6.4. SED Record . . . . . . . . . . . . . . . . . . . . . . . 28 86 6.5. SED Group Offer . . . . . . . . . . . . . . . . . . . . . 32 87 6.6. Egress Route . . . . . . . . . . . . . . . . . . . . . . 34 88 7. Framework Operations . . . . . . . . . . . . . . . . . . . . 36 89 7.1. Add Operation . . . . . . . . . . . . . . . . . . . . . . 36 90 7.2. Delete Operation . . . . . . . . . . . . . . . . . . . . 36 91 7.3. Get Operations . . . . . . . . . . . . . . . . . . . . . 37 92 7.4. Accept Operations . . . . . . . . . . . . . . . . . . . . 38 93 7.5. Reject Operations . . . . . . . . . . . . . . . . . . . . 38 94 7.6. Get Server Details Operation . . . . . . . . . . . . . . 39 95 8. XML Considerations . . . . . . . . . . . . . . . . . . . . . 39 96 8.1. Namespaces . . . . . . . . . . . . . . . . . . . . . . . 39 97 8.2. Versioning and Character Encoding . . . . . . . . . . . . 39 98 9. Security Considerations . . . . . . . . . . . . . . . . . . . 40 99 9.1. Confidentiality and Authentication . . . . . . . . . . . 40 100 9.2. Authorization . . . . . . . . . . . . . . . . . . . . . . 40 101 9.3. Denial of Service . . . . . . . . . . . . . . . . . . . . 40 102 9.3.1. DoS Issues Inherited from Transport Mechanism . . . . 41 103 9.3.2. DoS Issues Specific to SPPF . . . . . . . . . . . . . 41 104 9.4. Information Disclosure . . . . . . . . . . . . . . . . . 42 105 9.5. Non Repudiation . . . . . . . . . . . . . . . . . . . . . 42 106 9.6. Replay Attacks . . . . . . . . . . . . . . . . . . . . . 42 107 9.7. Man in the Middle . . . . . . . . . . . . . . . . . . . . 43 108 10. Internationalization Considerations . . . . . . . . . . . . . 43 109 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 43 110 11.1. URN Assignments . . . . . . . . . . . . . . . . . . . . 43 111 11.2. Organization Identifier Namespace Registry . . . . . . . 44 112 12. Formal Specification . . . . . . . . . . . . . . . . . . . . 44 113 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 52 114 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 53 115 14.1. Normative References . . . . . . . . . . . . . . . . . . 53 116 14.2. Informative References . . . . . . . . . . . . . . . . . 53 117 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 55 119 1. Introduction 121 Service providers and enterprises use routing databases known as 122 registries to make session routing decisions for Voice over IP, SMS 123 and MMS traffic exchanges. This document is narrowly focused on the 124 provisioning framework for these registries. This framework 125 prescribes a way for an entity to provision session-related data into 126 a Registry. The data being provisioned can be optionally shared with 127 other participating peering entities. The requirements and use cases 128 driving this framework have been documented in [RFC6461]. 130 Three types of provisioning flows have been described in the use case 131 document: client to Registry, Registry to local data repository and 132 Registry to Registry. This document addresses client to Registry 133 flow enabling the need to provision Session Establishment Data (SED). 134 The framework that supports flow of messages to facilitate client to 135 Registry provisioning is referred to as Session Peering Provisioning 136 Framework (SPPF). 138 The role of the "client" and the "server" only applies to the 139 connection, and those roles are not related in any way to the type of 140 entity that participates in a protocol exchange. For example, a 141 Registry might also include a "client" when such a Registry initiates 142 a connection (for example, for data distribution to SSP). 144 *--------* *------------* *------------* 145 | | (1). Client | | (3).Registry | | 146 | Client | ------------> | Registry |<------------->| Registry | 147 | | to Registry | | to Registry | | 148 *--------* *------------* *------------* 149 / \ \ 150 / \ \ 151 / \ \ 152 / \ v 153 / \ ... 154 / \ 155 / (2). Distrib \ 156 / Registry data \ 157 / to local data \ 158 V store V 159 +----------+ +----------+ 160 |Local Data| |Local Data| 161 |Repository| |Repository| 162 +----------+ +----------+ 164 Three Registry Provisioning Flows 166 Figure 1 168 A "terminating" SIP Service Provider (SSP) provisions Session 169 Establishment Data or SED into the Registry to be selectively shared 170 with other peer SSPs. 172 SED is typically used by various downstream SIP signaling systems to 173 route a call to the next hop associated with the called domain. 174 These systems typically use a local data store ("Local Data 175 Repository") as their source of session routing information. More 176 specifically, the SED data is the set of parameters that the outgoing 177 signaling path border elements (SBEs) need to initiate the session. 178 See [RFC5486] for more details. 180 A Registry may distribute the provisioned data into local data 181 repositories or may additionally offer a central query resolution 182 service (not shown in the above figure) for query purposes. 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 In this document, XML schema is used to describe the building blocks 207 of the SPPF and to express the data types, the semantic relationships 208 between the various data types, and the various constraints as a 209 binding construct. However, the "protocol" specification is free to 210 choose any data representation format as long as it meets the 211 requirements laid out in the SPPF XML schema definition. As an 212 example, XML and JSON are two widely used data representation 213 formats. 215 This document is organized as follows: 217 o Section 2 provides the terminology 219 o Section 3 provides an overview of SPPF, including functional 220 entities and data model 222 o Section 4 specifies requirements for SPPF transport protocols 224 o Section 5 describes the base framework data structures, the 225 generic response types that MUST be supported by a conforming 226 transport "protocol" specification, and the basic object type most 227 first class objects extend from 229 o Section 6 provides a detailed description of the data model object 230 specifications 232 o Section 7 describes the operations that are supported by the data 233 model 235 o Section 8 defines XML considerations XML parsers must meet to 236 conform to this specification 238 o Sections 9 - 11 discuss security, internationalization and IANA 239 considerations 241 o Section 12 normatively defines the SPPF using its XML Schema 242 Definition. 244 2. Terminology 246 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 247 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 248 document are to be interpreted as described in [RFC2119]. 250 This document reuses terms from [RFC3261], [RFC5486], use cases and 251 requirements documented in [RFC6461] and the ENUM Validation 252 Architecture [RFC4725]. 254 In addition, this document specifies the following additional terms: 256 SPPF: Session Peering Provisioning Framework, the framework used by 257 a transport protocol to provision data into a Registry (see arrow 258 labeled "1." in Figure 1 of [RFC6461]). It is the primary scope 259 of this document. 261 Client: In the context of SPPF, this is an application that 262 initiates a provisioning request. It is sometimes referred to as 263 a "Registry client". 265 Server: In the context of SPPF, this is an application that 266 receives a provisioning request and responds accordingly. It is 267 sometimes referred to as a Registry. 269 Registry: The Registry operates a master database of Session 270 Establishment Data for one or more Registrants. 272 Registrant: The definition of a Registrant is based on [RFC4725]. 273 It is the end-user, the person or organization that is the 274 "holder" of the Session Establishment Data being provisioned into 275 the Registry by a Registrar. For example, in [RFC6461], a 276 Registrant is pictured as a SIP Service Provider in Figure 2. 278 Within the confines of a Registry, a Registrant is uniquely 279 identified by a well-known ID. 281 Registrar: The definition of a Registrar is based on [RFC4725]. It 282 is an entity that performs provisioning operations on behalf of a 283 Registrant by interacting with the Registry via SPPF operations. 284 In other words the Registrar is the SPPF Client. The Registrar 285 and Registrant roles are logically separate to allow, but not 286 require, a single Registrar to perform provisioning operations on 287 behalf of more than one Registrant. 289 Peering Organization: A Peering Organization is an entity to which 290 a Registrant's SED Groups are made visible using the operations of 291 SPPF. 293 3. Framework High Level Design 295 This section introduces the structure of the data model and provides 296 the information framework for the SPPF. The data model is defined 297 along with all the objects manipulated by a conforming transport 298 protocol and their relationships. 300 3.1. Framework Data Model 302 The data model illustrated and described in Figure 2 defines the 303 logical objects and the relationships between these objects supported 304 by SPPF. SPPF defines protocol operations through which an SPPF 305 client populates a Registry with these logical objects. SPPF clients 306 belonging to different Registrars may provision data into the 307 Registry using a conforming transport protocol that implements these 308 operations 310 The logical structure presented below is consistent with the 311 terminology and requirements defined in [RFC6461]. 313 +-------------+ +-----------------+ 314 | all object | |Egress Route: | 315 | types | 0..n | rant, | 316 +-------------+ +--| egrRteName, | 317 |0..n / | pref, | 318 | / | regxRewriteRule,| 319 |2 / | ingrSedGrp, | 320 +----------------------+ / | svcs | 321 |Organization: | / +-----------------+ 322 | orgId | / 323 +----------------------+ / 324 |0..n / 325 | / 326 |A SED Group is / 327 |associated with / 328 |zero or more / +---[abstract]----+ 329 |Peering / | SED Record: | 330 |Organizations / | rant, | 331 | / | sedName, |0..n 332 |0..n / | sedFunction, |------| 333 +--------+--------------+0..n 0..n| isInSvc, | | 334 |SED Group: |------------------| ttl | | 335 | rant, | +-----------------+ | 336 | sedGrpName, | ^ Various types | 337 | isInSvc, | | of SED Records | 338 | sedRecRef, | | | 339 | peeringOrg, | +-----+------------+ | 340 | sourceIdent, | | | | | 341 | priority, | +----+ +-------+ +----+ | 342 | dgName | | URI| | NAPTR | | NS | | 343 +-----------------------+ +----+ +-------+ +----+ | 344 |0..n | 345 | +-----[abstract]------+ | 346 |0..n |Public Identifier: | | 347 +----------------------+0..n 0..n| rant, | | 348 | Dest Group: |--------------| publicIdentifier, | | 349 | rant, | | dgName | | 350 | dgName | | | | 351 +----------------------+ +---------------------+ | 352 ^ Various types | 353 +---------+-------+------+----------+ of Public | 354 | | | | | Identifiers | 355 +------+ +-----+ +-----+ +-----+ +------+ | 356 | URI | | TNP | | TNR | | RN | | TN |-------------| 357 +------+ +-----+ +-----+ +-----+ +------+ 0..n 359 Figure 2 361 The objects and attributes that comprise the data model can be 362 described as follows (objects listed from the bottom up): 364 o Public Identifier: 365 From a broad perspective a public identifier is a well-known 366 attribute that is used as the key to perform resolution lookups. 367 Within the context of SPPF, a public identifier object can be a 368 Telephone Number (TN), a range of Telephone Numbers, a PSTN 369 Routing Number (RN), a TN prefix, or a URI. 371 An SPPF Public Identifier may be a member of zero or more 372 Destination Groups to create logical groupings of Public 373 Identifiers that share a common set of Session Establishment Data 374 (e.g. routes). 376 A TN Public Identifier may optionally be associated with zero or 377 more individual SED Records. This ability for a Public Identifier 378 to be directly associated with a SED Record, as opposed to forcing 379 membership in one or more Destination Groups, supports use cases 380 where the SED Record contains data specifically tailored to an 381 individual TN Public Identifier. 383 o Destination Group: 384 A named logical grouping of zero or more Public Identifiers that 385 can be associated with one or more SED Groups for the purpose of 386 facilitating the management of their common session establishment 387 information. 389 o SED Group: 390 A SED Group contains a set of SED Record references, a set of 391 Destination Group references, and a set of peering organization 392 identifiers. This is used to establish a three part relationships 393 between a set of Public Identifiers, the session establishment 394 information (SED) shared across these Public Identifiers, and the 395 list of peering organizations whose query responses from the 396 resolution system may include the session establishment 397 information contained in a given SED group. In addition, the 398 sourceIdent element within a SED Group, in concert with the set of 399 peering organization identifiers, enables fine-grained source 400 based routing. For further details about the SED Group and source 401 based routing, refer to the definitions and descriptions in 402 Section 6.1. 404 o SED Record: 405 A SED Record contains the data that a resolution system returns in 406 response to a successful query for a Public Identifier. SED 407 Records are generally associated with a SED Group when the SED 408 within is not specific to a Public Identifier. 410 To support the use cases defined in [RFC6461], SPPF framework 411 defines three type of SED Records: URIType, NAPTRType, and NSType. 412 These SED Records extend the abstract type SedRecType and inherit 413 the common attribute 'priority' that is meant for setting 414 precedence across the SED records defined within a SED Group in a 415 protocol agnostic fashion. 417 o Egress Route: 418 In a high-availability environment, the originating SSP likely has 419 more than one egress paths to the ingress SBE of the target SSP. 420 The Egress Route allows the originating SSP to choose a specific 421 egress SBE to be associated with the target ingress SBE. the 422 'svcs' element specifies ENUM services ((e.g.,E2U+pstn:sip+sip) 423 that are used to identify the SED records associated with the SED 424 Group that will be modified by the originating SSP. 426 o Organization: 427 An Organization is an entity that may fulfill any combination of 428 three roles: Registrant, Registrar, and Peering Organization. All 429 objects in SPPF are associated with two organization identifiers 430 to identify each object's Registrant and Registrar. A SED Group 431 object is also associated with a set of zero or more organization 432 identifiers that identify the peering organization(s) whose 433 resolution query responses may include the session establishment 434 information (SED) defined in the SED Records within that SED 435 Group. A peering organization is an entity that the Registrant 436 intends to share the SED data with. 438 3.2. Time Value 440 Some request and response messages in SPPF include time value(s) 441 defined as type xs:dateTime, a built-in W3C XML Schema Datatype. Use 442 of unqualified local time value is disallowed as it can lead to 443 interoperability issues. The value of time attribute MUST be 444 expressed in Coordinated Universal Time (UTC) format without the 445 timezone digits. 447 "2010-05-30T09:30:10Z" is an example of an acceptable time value for 448 use in SPPF messages. "2010-05-30T06:30:10+3:00" is a valid UTC 449 time, but it is not approved for use in SPPF messages. 451 3.3. Extensibility 453 The framework contains various points of extensibility in form of the 454 "ext" elements. Extensions used beyond the scope of private SPPF 455 installations MUST be documented in an RFC level document, and the 456 first such extension SHOULD define an IANA registry, holding a list 457 of documented extensions. 459 4. Transport Protocol Requirements 461 This section provides requirements for transport protocols suitable 462 for SPPF. More specifically, this section specifies the services, 463 features, and assumptions that SPPF framework delegates to the chosen 464 transport and envelope technologies. 466 4.1. Connection Oriented 468 The SPPF follows a model where a client establishes a connection to a 469 server in order to further exchange SPPF messages over such point-to- 470 point connection. A transport protocol for SPPF MUST therefore be 471 connection oriented. 473 4.2. Request and Response Model 475 Provisioning operations in SPPF follow the request-response model, 476 where a client sends a request message to initiate a transaction and 477 the server responds with a response. Multiple subsequent request- 478 response exchanges MAY be performed over a single persistent 479 connection. 481 Therefore, a transport protocol for SPPF MUST follow the request- 482 response model by allowing a response to be sent to the request 483 initiator. 485 4.3. Connection Lifetime 487 Some use cases involve provisioning a single request to a network 488 element. Connections supporting such provisioning requests might be 489 short-lived, and may be established only on demand. Other use cases 490 involve either provisioning a large dataset, or a constant stream of 491 small updates, either of which would likely require long-lived 492 connections. 494 Therefore, a protocol suitable for SPPF SHOULD be able to support 495 both short-lived as well as long-lived connections. 497 4.4. Authentication 499 All SPPF objects are associated with a Registrant identifier. An 500 SPPF Client provisions SPPF objects on behalf of Registrants. An 501 authenticated SPP Client is a Registrar. Therefore, the SPPF 502 transport protocol MUST provide means for an SPPF server to 503 authenticate an SPPF Client. 505 4.5. Authorization 507 After successful authentication of the SPPF client as a Registrar the 508 Registry performs authorization checks to determine if the Registrar 509 is authorized to act on behalf of the Registrant whose identifier is 510 included in the SPPF request. Refer to the Security Considerations 511 section for further guidance. 513 4.6. Confidentiality and Integrity 515 SPPF objects that the Registry manages can be private in nature. 516 Therefore, the transport protocol MUST provide means for end-to-end 517 encryption between the SPPF client and Registry. 519 If the data is compromised in-flight between the SPPF client and 520 Registry, it will seriously affect the stability and integrity of the 521 system. Therefore, the transport protocol MUST provide means for 522 data integrity protection. 524 4.7. Near Real Time 526 Many use cases require near real-time responses from the server. 527 Therefore, a DRINKS transport protocol MUST support near real-time 528 response to requests submitted by the client. 530 4.8. Request and Response Sizes 532 Use of SPPF may involve simple updates that may consist of small 533 number of bytes, such as, update of a single public identifier. 534 Other provisioning operations may constitute large number of dataset 535 as in adding millions records to a Registry. As a result, a suitable 536 transport protocol for SPPF SHOULD accommodate dataset of various 537 sizes. 539 4.9. Request and Response Correlation 541 A transport protocol suitable for SPPF MUST allow responses to be 542 correlated with requests. 544 4.10. Request Acknowledgement 546 Data transported in the SPPF is likely crucial for the operation of 547 the communication network that is being provisioned. A SPPF client 548 responsible for provisioning SED to the Registry has a need to know 549 if the submitted requests have been processed correctly. 551 Failed transactions can lead to situations where a subset of public 552 identifiers or even SSPs might not be reachable, or the provisioning 553 state of the network is inconsistent. 555 Therefore, a transport protocol for SPPF MUST provide a response for 556 each request, so that a client can identify whether a request 557 succeeded or failed. 559 4.11. Mandatory Transport 561 At the time of this writing, a choice of transport protocol has been 562 provided in SPP Protocol over SOAP document. To encourage 563 interoperability, the SPPF server MUST provide support for this 564 transport protocol. With time, it is possible that other transport 565 layer choices may surface that agree with the requirements discussed 566 above. 568 5. Base Framework Data Structures and Response Codes 570 SPPF contains some common data structures for most of the supported 571 object types. This section describes these common data structures. 573 5.1. Basic Object Type and Organization Identifiers 575 All first class objects extend the type BasicObjType. It consists of 576 the Registrant organization, the Registrar organization, the date and 577 time of object creation, and the last date and time the object was 578 updated. The Registry MUST store the date and time of the object 579 creation and update, if applicable, for all Get operations (see 580 Section 7). If the client passed in either date and time values, the 581 Registry MUST ignore it. The Registrar performs the SPPF operations 582 on behalf of the Registrant, the organization that owns the object. 584 585 586 587 588 589 590 591 592 594 The identifiers used for Registrants (rant) and Registrars (rar) are 595 instances of OrgIdType. The OrgIdType is defined as a string and all 596 OrgIdType instances MUST follow the textual convention: 597 "namespace:value" (for example "iana-en:32473"). See the IANA 598 Consideration section for more details. 600 5.2. Various Object Key Types 602 The SPPF data model contains various object relationships. In some 603 cases, these object relationships are established by embedding the 604 unique identity of the related object inside the relating object. 605 Note that an object's unique identity is required to Delete or Get 606 the details of an object. The following sub-sections normatively 607 define the various object keys in SPPF and the attributes of those 608 keys. 610 "Name" attributes that are used as components of object key types 611 MUST be treated case insensitive, more specifically, comparison 612 operations MUST use the toCasefold() function, as specified in 613 Section 3.13 of [Unicode6.1]. 615 5.2.1. Generic Object Key Type 617 Most objects in SPPF are uniquely identified by an object key that 618 has the object's name, object's type and its Registrant's 619 organization ID as its attributes. The abstract type called 620 ObjKeyType is where this unique identity is housed. Any concrete 621 representation of the ObjKeyType MUST contain the following: 623 Object Name: The name of the object. 625 Registrant Id: The unique organization ID that identifies the 626 Registrant. 628 Type: The value that represents the type of SPPF object that. 629 This is required as different types of objects in SPPF, that 630 belong to the same Registrant, can have the same name. 632 The structure of abstract ObjKeyType is as follows: 634 635 636 637 ---- Generic type that represents the 638 key for various objects in SPPF. ---- 639 640 641 643 5.2.2. Derived Object Key Types 645 The SPPF data model contains certain objects that are uniquely 646 identified by attributes, different from or in addition to, the 647 attributes in the generic object key described in previous section. 648 These kind of object keys are derived from the abstract ObjKeyType 649 and defined in their own abstract key types. Because these object 650 key types are abstract, they MUST be specified in a concrete form in 651 any SPPF conforming transport protocol specification. These are used 652 in Delete and Get operations, and may also be used in Accept and 653 Reject operations. 655 Following are the derived object keys in SPPF data model: 657 o SedGrpOfferKeyType: This uniquely identifies a SED Group object 658 offer. This key type extends from ObjKeyType and MUST also have 659 the organization ID of the Registrant to whom the object is being 660 offered, as one of its attributes. In addition to the Delete and 661 Get operations, these key types are used in Accept and Reject 662 operations on a SED Group Offer object. The structure of abstract 663 SedGrpOfferKeyType is as follows: 665 667 668 669 670 671 ---- Generic type that represents 672 the key for a object offer. ---- 673 674 675 676 677 679 A SED Group Offer object MUST use SedGrpOfferKeyType. Refer the 680 "Framework Data Model Objects" section of this document for 681 description of SED Group Offer object. 683 o PubIdKeyType: This uniquely identifies a Public Identity object. 684 This key type extends from abstract ObjKeyType. Any concrete 685 definition of PubIdKeyType MUST contain the elements that identify 686 the value and type of Public Identity and also contain the 687 organization ID of the Registrant that is the owner of the Public 688 Identity object. A Public Identity object in SPPF is uniquely 689 identified by the Registrant's organization ID, the value of the 690 public identity, and the type of the public identity object. 692 Consequently, any concrete representation of the PubIdKeyType MUST 693 contain the following attributes: 695 * Registrant Id: The unique organization ID that identifies the 696 Registrant. 698 * Value: The value of the Public Identity. 700 * Type: The type of the Public Identity Object. 702 The PubIdKeyType is used in Delete and Get operations on a Public 703 Identifier object. 705 o The structure of abstract PubIdKeyType is as follows: 707 708 709 710 711 712 ---- Generic type that represents the key for a Pub Id. ---- 713 714 715 716 717 719 A Public Identity object MUST use attributes of PubIdKeyType for its 720 unique identification . Refer to Section 6 for a description of 721 Public Identity object. 723 5.3. Response Message Types 725 This section contains the listing of response types that MUST be 726 defined by the SPPF conforming transport protocol specification and 727 implemented by a conforming SPPF server. 729 +---------------------+---------------------------------------------+ 730 | Response Type | Description | 731 +---------------------+---------------------------------------------+ 732 | Request Succeeded | Any conforming specification MUST define a | 733 | | response to indicate that a given request | 734 | | succeeded. | 735 | | | 736 | Request syntax | Any conforming specification MUST define a | 737 | invalid | response to indicate that a syntax of a | 738 | | given request was found invalid. | 739 | | | 740 | Request too large | Any conforming specification MUST define a | 741 | | response to indicate that the count of | 742 | | entities in the request is larger than the | 743 | | server is willing or able to process. | 744 | | | 745 | Version not | Any conforming specification MUST define a | 746 | supported | response to indicate that the server does | 747 | | not support the version of the SPPF | 748 | | protocol specified in the request. | 749 | | | 750 | Command invalid | Any conforming specification MUST define a | 751 | | response to indicate that the operation | 752 | | and/or command being requested by the | 753 | | client is invalid and/or not supported by | 754 | | the server. | 755 | | | 756 | System temporarily | Any conforming specification MUST define a | 757 | unavailable | response to indicate that the SPPF server | 758 | | is temporarily not available to serve | 759 | | client request. | 760 | | | 761 | Unexpected internal | Any conforming specification MUST define a | 762 | system or server | response to indicate that the SPPF server | 763 | error. | encountered an unexpected error that | 764 | | prevented the server from fulfilling the | 765 | | request. | 766 | | | 767 | Attribute value | Any conforming specification MUST define a | 768 | invalid | response to indicate that the SPPF server | 769 | | encountered an attribute or property in the | 770 | | request that had an invalid/bad value. | 771 | | Optionally, the specification MAY provide a | 772 | | way to indicate the Attribute Name and the | 773 | | Attribute Value to identify the object that | 774 | | was found to be invalid. | 775 | | | 776 | Object does not | Any conforming specification MUST define a | 777 | exist | response to indicate that an object present | 778 | | in the request does not exist on the SPPF | 779 | | server. Optionally, the specification MAY | 780 | | provide a way to indicate the Attribute | 781 | | Name and the Attribute Value that | 782 | | identifies the non-existent object. | 783 | | | 784 | Object status or | Any conforming specification MUST define a | 785 | ownership does not | response to indicate that the operation | 786 | allow for | requested on an object present in the | 787 | operation. | request cannot be performed because the | 788 | | object is in a status that does not allow | 789 | | the said operation or the user requesting | 790 | | the operation is not authorized to perform | 791 | | the said operation on the object. | 792 | | Optionally, the specification MAY provide a | 793 | | way to indicate the Attribute Name and the | 794 | | Attribute Value that identifies the object. | 795 +---------------------+---------------------------------------------+ 797 Table 1: Response Types 799 When the response messages are "parameterized" with the Attribute 800 Name and Attribute Value, then the use of these parameters MUST 801 adhere to the following rules: 803 o Any value provided for the Attribute Name parameter MUST be an 804 exact XSD element name of the protocol data element that the 805 response message is referring to. For example, valid values for 806 "attribute name" are "dgName", "sedGrpName", "sedRec", etc. 808 o The value for Attribute Value MUST be the value of the data 809 element to which the preceding Attribute Name refers. 811 o Response type "Attribute value invalid" MUST be used whenever an 812 element value does not adhere to data validation rules. 814 o Response types "Attribute value invalid" and "Object does not 815 exist" MUST not be used interchangeably. Response type "Object 816 does not exist" MUST be returned by an Update/Del/Accept/Reject 817 operation when the data element(s) used to uniquely identify a 818 pre-existing object do not exist. If the data elements used to 819 uniquely identify an object are malformed, then response type 820 "Attribute value invalid" MUST be returned. 822 6. Framework Data Model Objects 824 This section provides a description of the specification of each 825 supported data model object (the nouns) and identifies the commands 826 (the verbs) that MUST be supported for each data model object. 827 However, the specification of the data structures necessary to 828 support each command is delegated to an SPPF conforming transport 829 protocol specification. 831 6.1. Destination Group 833 Destination Group represents a logical grouping of Public Identifiers 834 with common session establishment information. The transport 835 protocol MUST support the ability to Create, Modify, Get, and Delete 836 Destination Groups (refer the "Framework Operations" section of this 837 document for a generic description of various operations). 839 A Destination Group object MUST be uniquely identified by attributes 840 as defined in the description of "ObjKeyType" in the section "Generic 841 Object Key Type" of this document. 843 The DestGrpType object structure is defined as follows: 845 846 847 848 849 850 851 852 853 855 The DestGrpType object is composed of the following elements: 857 o base: All first class objects extend BasicObjType (see 858 Section 5.1). 860 o dgName: The character string that contains the name of the 861 Destination Group. 863 o ext: Point of extensibility described in Section 3.3. 865 6.2. Public Identifier 867 A Public Identifier is the search key used for locating the session 868 establishment data (SED). In many cases, a Public Identifier is 869 attributed to the end user who has a retail relationship with the 870 service provider or Registrant organization. SPPF supports the 871 notion of the carrier-of-record as defined in [RFC5067]. Therefore, 872 the Registrant under whom the Public Identity is being created can 873 optionally claim to be a carrier-of-record. 875 SPPF identifies three types of Public Identifiers: telephone numbers 876 (TN), routing numbers (RN), and URI. SPPF provides structures to 877 manage a single TN, a contiguous range of TNs, and a TN prefix. The 878 transport protocol MUST support the ability to Create, Modify, Get, 879 and Delete Public Identifiers (refer the "Framework Operations" 880 section of this document for a generic description of various 881 operations). 883 A Public Identity object MUST be uniquely identified by attributes as 884 defined in the description of "PubIdKeyType" in the section 885 Section 5.2.2. 887 The abstract XML schema type definition PubIdType is a generalization 888 for the concrete Public Identifier schema types. PubIdType element 889 'dgName' represents the name of a destination group that a given 890 Public Identifier may be a member of. Note that this element may be 891 present multiple times so that a given Public Identifier may be a 892 member of multiple destination groups. The PubIdType object 893 structure is defined as follows: 895 896 897 898 899 901 902 903 904 906 A Public Identifier may be a member of zero or more Destination 907 Groups. When a Public Identifier is member of a Destination Group, 908 it is intended to be associated with SED(s) through the SED Group(s) 909 that are associated with the Destination Group. When a Public 910 Identifier is not member of any Destination Group, it is intended to 911 be associated with SED through the SED Records that are directly 912 associated with the Public Identifier. 914 A telephone number is provisioned using the TNType, an extension of 915 PubIdType. Each TNType object is uniquely identified by the 916 combination of its value contained within element, and its 917 Registrant ID. TNType is defined as follows: 919 920 921 922 923 924 925 927 928 929 930 932 933 934 935 936 937 938 940 941 942 943 944 945 947 TNType consists of the following attributes: 949 o tn: Telephone number to be added to the Registry. 951 o sedRecRef: Optional reference to SED records that are directly 952 associated with the TN Public Identifier. Following the SPPF data 953 model, the SED record could be a protocol agnostic URIType or 954 another type. 956 o corInfo: corInfo is an optional parameter of type CORInfoType that 957 allows the Registrant organization to set forth a claim to be the 958 carrier-of-record (see [RFC5067]). This is done by setting the 959 value of element of the CORInfoType object structure to 960 "true". The other two parameters of the CORInfoType, and 961 are set by the Registry to describe the outcome of the 962 carrier-of-record claim by the Registrant. In general, inclusion 963 of parameter is useful if the Registry has the authority 964 information, such as, the number portability data, etc., in order 965 to qualify whether the Registrant claim can be satisfied. If the 966 carrier-of-record claim disagrees with the authority data in the 967 Registry, whether the TN add operation fails or not is a matter of 968 policy and it is beyond the scope of this document. 970 A routing number is provisioned using the RNType, an extension of 971 PubIDType. The Registrant organization can add the RN and associate 972 it with the appropriate destination group(s) to share the route 973 information. This allows SSPs to use the RN search key to derive the 974 ingress routes for session establishment at the runtime resolution 975 process (see [RFC3761]. Each RNType object is uniquely identified by 976 the combination of its value inside the element, and its 977 Registrant ID. RNType is defined as follows: 979 980 981 982 983 984 985 986 987 988 990 RNType has the following attributes: 992 o rn: Routing Number used as the search key. 994 o corInfo: corInfo is an optional parameter of type CORInfoType that 995 allows the Registrant organization to set forth a claim to be the 996 carrier-of-record (see [RFC5067]) 998 TNRType structure is used to provision a contiguous range of 999 telephone numbers. The object definition requires a starting TN and 1000 an ending TN that together define the span of the TN range. Use of 1001 TNRType is particularly useful when expressing a TN range that does 1002 not include all the TNs within a TN block or prefix. The TNRType 1003 definition accommodates the open number plan as well such that the 1004 TNs that fall between the start and end TN range may include TNs with 1005 different length variance. Whether the Registry can accommodate the 1006 open number plan semantics is a matter of policy and is beyond the 1007 scope of this document. Each TNRType object is uniquely identified 1008 by the combination of its value that in turn is a combination of the 1009 and elements, and its Registrant ID. TNRType 1010 object structure definition is as follows: 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1023 1024 1025 1026 1027 1028 1030 TNRType has the following attributes: 1032 o startTn: Starting TN in the TN range 1034 o endTn: The last TN in the TN range 1036 o corInfo: corInfo is an optional parameter of type CORInfoType that 1037 allows the Registrant organization to set forth a claim to be the 1038 carrier-of-record (see [RFC5067]) 1040 In some cases, it is useful to describe a set of TNs with the help of 1041 the first few digits of the telephone number, also referred to as the 1042 telephone number prefix or a block. A given TN prefix may include 1043 TNs with different length variance in support of open number plan. 1044 Once again, whether the Registry supports the open number plan 1045 semantics is a matter of policy and it is beyond the scope of this 1046 document. The TNPType data structure is used to provision a TN 1047 prefix. Each TNPType object is uniquely identified by the 1048 combination of its value in the element, and its 1049 Registrant ID. TNPType is defined as follows: 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1062 TNPType consists of the following attributes: 1064 o tnPrefix: The telephone number prefix 1066 o corInfo: corInfo is an optional parameter of type CORInfoType that 1067 allows the Registrant organization to set forth a claim to be the 1068 carrier-of-record (see [RFC5067]) 1070 In some cases, a Public Identifier may be a URI, such as an email 1071 address. The URIPubIdType object is comprised of the data element 1072 necessary to house such Public Identifiers. Each URIPubIdType object 1073 is uniquely identified by the combination of its value in the 1074 element, and its Registrant ID. URIPubIdType is defined as follows: 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1087 URIPubIdType consists of the following attributes: 1089 o uri: The value that acts a Public Identifier. 1091 o ext: Point of extensibility described in Section 3.3. 1093 6.3. SED Group 1095 SED Group is a grouping of one or more Destination Group, the common 1096 SED Records, and the list of peer organizations with access to the 1097 SED Records associated with a given SED Group. It is this indirect 1098 linking of public identifiers to their Session Establishment Data 1099 that significantly improves the scalability and manageability of the 1100 peering data. Additions and changes to SED information are reduced 1101 to a single operation on a SED Group or SED Record , rather than 1102 millions of data updates to individual public identifier records that 1103 individually contain their peering data. The transport protocol MUST 1104 support the ability to Create, Modify, Get, and Delete SED Groups 1105 (refer the "Framework Operations" section of this document for a 1106 generic 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 (see 1146 Section 5.1). 1148 o sedGrpName: The character string that contains the name of the SED 1149 Group. It uniquely identifies this object within the context of 1150 the Registrant ID (a child element of the base element as 1151 described above). 1153 o sedRecRef: Set of zero or more objects of type SedRecRefType that 1154 house the unique keys of the SED Records (containing the session 1155 establishment data) that the SedGrpType object refers to and their 1156 relative priority within the context of this SED Group. 1158 o dgName: Set of zero or more names of DestGrpType object instances. 1159 Each dgName name, in association with this SED Group's Registrant 1160 ID, uniquely identifies a DestGrpType object instance whose 1161 associated public identifiers are reachable using the session 1162 establishment information housed in this SED Group. An intended 1163 side affect of this is that a SED Group cannot provide session 1164 establishment information for a Destination Group belonging to 1165 another Registrant. 1167 o peeringOrg: Set of zero or more peering organization IDs that have 1168 accepted an offer to receive this SED Group's information. Note 1169 that this identifier "peeringOrg" is an instance of OrgIdType. 1170 The set of peering organizations in this list is not directly 1171 settable or modifiable using the addSedGrpsRqst operation. This 1172 set is instead controlled using the SED offer and accept 1173 operations. 1175 o sourceIdent: Set of zero or more SourceIdentType object instances. 1176 These objects, described further below, house the source 1177 identification schemes and identifiers that are applied at 1178 resolution time as part of source based routing algorithms for the 1179 SED Group. 1181 o isInSvc: A boolean element that defines whether this SED Group is 1182 in service. The session establishment information contained in a 1183 SED Group that is in service is a candidate for inclusion in 1184 resolution responses for public identities residing in the 1185 Destination Group associated with this SED Group. The session 1186 establishment information contained in a SED Group that is not in 1187 service is not a candidate for inclusion in resolution responses. 1189 o priority: Priority value that can be used to provide a relative 1190 value weighting of one SED Group over another. The manner in 1191 which this value is used, perhaps in conjunction with other 1192 factors, is a matter of policy. 1194 o ext: Point of extensibility described in Section 3.3. 1196 As described above, the SED Group contains a set of references to SED 1197 record objects. A SED record object is based on an abstract type: 1198 SedRecType. The concrete types that use SedRecType as an extension 1199 base are NAPTRType, NSType, and URIType. The definitions of these 1200 types are included the SED Record section of this document. 1202 The SedGrpType object provides support for source-based routing via 1203 the peeringOrg data element and more granular source base routing via 1204 the source identity element. The source identity element provides 1205 the ability to specify zero or more of the following in association 1206 with a given SED Group: a regular expression that is matched against 1207 the resolution client IP address, a regular expression that is 1208 matched against the root domain name(s), and/or a regular expression 1209 that is matched against the calling party URI(s). The result will be 1210 that, after identifying the visible SED Groups whose associated 1211 Destination Group(s) contain the lookup key being queried and whose 1212 peeringOrg list contains the querying organizations organization ID, 1213 the resolution server will evaluate the characteristics of the Source 1214 URI, and Source IP address, and root domain of the lookup key being 1215 queried. The resolution server then compares these criteria against 1216 the source identity criteria associated with the SED Groups. The 1217 session establishment information contained in SED Groups that have 1218 source based routing criteria will only be included in the resolution 1219 response if one or more of the criteria matches the source criteria 1220 from the resolution request. The Source Identity data element is of 1221 type SourceIdentType, whose structure is defined as follows: 1223 1224 1225 1226 1228 1229 1230 1232 1233 1234 1235 1236 1237 1238 1240 The SourceIdentType object is composed of the following data 1241 elements: 1243 o sourceIdentScheme: The source identification scheme that this 1244 source identification criteria applies to and that the associated 1245 sourceIdentRegex should be matched against. 1247 o sourceIdentRegex: The regular expression that should be used to 1248 test for a match against the portion of the resolution request 1249 that is dictated by the associated sourceIdentScheme. 1251 o ext: Point of extensibility described in Section 3.3. 1253 6.4. SED Record 1255 SED Group represents a combined grouping of SED Records that define 1256 session establishment information. However, SED Records need not be 1257 created to just serve a single SED Group. SED Records can be created 1258 and managed to serve multiple SED Groups. As a result, a change for 1259 example to the properties of a network node used for multiple routes, 1260 would necessitate just a single update operation to change the 1261 properties of that node. The change would then be reflected in all 1262 the SED Groups whose SED record set contains a reference to that 1263 node. The transport protocol MUST support the ability to Create, 1264 Modify, Get, and Delete SED Records (refer the "Framework Operations" 1265 section of this document for a generic description of various 1266 operations). 1268 A SED Record object MUST be uniquely identified by attributes as 1269 defined in the description of "ObjKeyType" in the section "Generic 1270 Object Key Type" of this document. 1272 The SedRecType object structure is defined as follows: 1274 1275 1276 1277 1278 1279 1281 1282 1283 1284 1285 1286 1288 1289 1290 1291 1292 1293 1295 The SedRecType object is composed of the following elements: 1297 o base: All first class objects extend BasicObjType (see 1298 Section 5.1). 1300 o sedName: The character string that contains the name of the SED 1301 Record. It uniquely identifies this object within the context of 1302 the Registrant ID (a child element of the base element as 1303 described above). 1305 o sedFunction: As described in [RFC6461], SED or Session 1306 Establishment Data falls primarily into one of two categories or 1307 functions, LUF and LRF. To remove any ambiguity as to the 1308 function a SED record is intended to provide, this optional 1309 element allows the provisioning party to make his or her 1310 intentions explicit. 1312 o isInSvc: A boolean element that defines whether this SED Record is 1313 in service or not. The session establishment information 1314 contained in a SED Record which is in service is a candidate for 1315 inclusion in resolution responses for Telephone Numbers that are 1316 either directly associated to this SED Record, or for Public 1317 Identities residing in a Destination Group that is associated to a 1318 SED Group which in turn has an association to this SED Record. 1320 o ttl: Number of seconds that an addressing server may cache a 1321 particular SED Record. 1323 As described above, SED records are based on an abstract type: 1324 SedRecType. The concrete types that use SedRecType as an extension 1325 base are NAPTRType, NSType, and URIType. The definitions of these 1326 types are included below. The NAPTRType object is comprised of the 1327 data elements necessary for a NAPTR (see [RFC3403]that contains 1328 routing information for a SED Group. The NSType object is comprised 1329 of the data elements necessary for a DNS name server that points to 1330 another DNS server that contains the desired routing information. 1331 The NSType is relevant only when the resolution protocol is ENUM (see 1332 [RFC3761]). The URIType object is comprised of the data elements 1333 necessary to house a URI. 1335 The data provisioned in a Registry can be leveraged for many purposes 1336 and queried using various protocols including SIP, ENUM and others. 1337 As such, the resolution data represented by the SED records must be 1338 in a form suitable for transport using one of these protocols. In 1339 the NAPTRType for example, if the URI is associated with a 1340 destination group, the user part of the replacement string that 1341 may require the Public Identifier cannot be preset. As a SIP 1342 Redirect, the resolution server will apply pattern on the input 1343 Public Identifier in the query and process the replacement string by 1344 substituting any back reference(s) in the to arrive at the 1345 final URI that is returned in the SIP Contact header. For an ENUM 1346 query, the resolution server will simply return the values of the 1347 and members of the URI. 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1364 1365 1366 1367 1368 1369 1372 1373 1374 1375 1376 1378 1379 1380 1381 1382 1383 1384 1386 1387 1388 1389 1390 1391 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1405 1406 1407 1408 1409 1410 1412 The NAPTRType object is composed of the following elements: 1414 o order: Order value in an ENUM NAPTR, relative to other NAPTRType 1415 objects in the same SED Group. 1417 o svcs: ENUM service(s) that are served by the SBE. This field's 1418 value must be of the form specified in [RFC6116] (e.g., 1419 E2U+pstn:sip+sip). The allowable values are a matter of policy 1420 and not limited by this protocol. 1422 o regx: NAPTR's regular expression field. If this is not included 1423 then the Repl field must be included. 1425 o repl: NAPTR replacement field, should only be provided if the 1426 Regex field is not provided, otherwise the server will ignore it 1428 o ext: Point of extensibility described in Section 3.3. 1430 The NSType object is composed of the following elements: 1432 o hostName: Root-relative host name of the name server. 1434 o ipAddr: Zero or more objects of type IpAddrType. Each object 1435 holds an IP Address and the IP Address type, IPv4 or IP v6. 1437 o ext: Point of extensibility described in Section 3.3. 1439 The URIType object is composed of the following elements: 1441 o ere: The POSIX Extended Regular Expression (ere) as defined in 1442 [RFC3986]. 1444 o uri: the URI as defined in [RFC3986]. In some cases, this will 1445 serve as the replacement string and it will be left to the 1446 resolution server to arrive at the final usable URI. 1448 6.5. SED Group Offer 1450 The list of peer organizations whose resolution responses can include 1451 the session establishment information contained in a given SED Group 1452 is controlled by the organization to which a SED Group object belongs 1453 (its Registrant), and the peer organization that submits resolution 1454 requests (a data recipient, also know as a peering organization). 1455 The Registrant offers access to a SED Group by submitting a SED Group 1456 Offer. The data recipient can then accept or reject that offer. Not 1457 until access to a SED Group has been offered and accepted will the 1458 data recipient's organization ID be included in the peeringOrg list 1459 in a SED Group object, and that SED Group's peering information 1460 become a candidate for inclusion in the responses to the resolution 1461 requests submitted by that data recipient. The transport protocol 1462 MUST support the ability to Create, Modify, Get, Delete, Accept and 1463 Reject SED Group Offers (refer the "Framework Operations" section of 1464 this document for a generic description of various operations). 1466 A SED Group Offer object MUST be uniquely identified by attributes as 1467 defined in the description of "SedGrpOfferKeyType" in the section 1468 "Derived Object Key Types" of this document. 1470 The SedGrpOfferType object structure is defined as follows: 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1486 1487 1488 1489 -- Generic type that represents the key for a SED group offer. Must 1490 be defined in concrete form in the transport specification. -- 1491 1492 1493 1495 1496 1497 1498 1499 1500 1502 The SedGrpOfferType object is composed of the following elements: 1504 o base: All first class objects extend BasicObjType (see 1505 Section 5.1). 1507 o sedGrpOfferKey: The object that identifies the SED that is or has 1508 been offered and the organization that it is or has been offered 1509 to. 1511 o status: The status of the offer, offered or accepted. The server 1512 controls the status. It is automatically set to "offered" when 1513 ever a new SED Group Offer is added, and is automatically set to 1514 "accepted" if and when that offer is accepted. The value of the 1515 element is ignored when passed in by the client. 1517 o offerDateTime: Date and time in UTC when the SED Group Offer was 1518 added. 1520 o acceptDateTime: Date and time in UTC when the SED Group Offer was 1521 accepted. 1523 6.6. Egress Route 1525 In a high-availability environment, the originating SSP likely has 1526 more than one egress path to the ingress SBE of the target SSP. If 1527 the originating SSP wants to exercise greater control and choose a 1528 specific egress SBE to be associated to the target ingress SBE, it 1529 can do so using the EgrRteType object. 1531 An Egress Route object MUST be uniquely identified by attributes as 1532 defined in the description of "ObjKeyType" in the section "Generic 1533 Object Key Type" of this document. 1535 Lets assume that the target SSP has offered as part of his session 1536 establishment data, to share one or more ingress routes and that the 1537 originating SSP has accepted the offer. In order to add the egress 1538 route to the Registry, the originating SSP uses a valid regular 1539 expression to rewrite ingress route in order to include the egress 1540 SBE information. Also, more than one egress route can be associated 1541 with a given ingress route in support of fault-tolerant 1542 configurations. The supporting SPPF structure provides a way to 1543 include route precedence information to help manage traffic to more 1544 than one outbound egress SBE. 1546 The transport protocol MUST support the ability to Add, Modify, Get, 1547 and Delete Egress Routes (refer the "Framework Operations" section of 1548 this document for a generic description of various operations). The 1549 EgrRteType object structure is defined as follows: 1551 1552 1553 1554 1555 1556 1557 1558 1560 1561 1562 1563 1564 1565 1567 The EgrRteType object is composed of the following elements: 1569 o base: All first class objects extend BasicObjType (see 1570 Section 5.1). 1572 o egrRteName: The name of the egress route. 1574 o pref: The preference of this egress route relative to other egress 1575 routes that may get selected when responding to a resolution 1576 request. 1578 o regxRewriteRule: The regular expression re-write rule that should 1579 be applied to the regular expression of the ingress NAPTR(s) that 1580 belong to the ingress route. 1582 o ingrSedGrp: The ingress SED group that the egress route should be 1583 used for. 1585 o svcs: ENUM service(s) that are served by an Egress Route. This 1586 element is used to identify the ingress NAPTRs associated with the 1587 SED Group to which an Egress Route's regxRewriteRule should be 1588 applied. If no ENUM service(s) are associated with an Egress 1589 Route, then the Egress Route's regxRewriteRule should be applied 1590 to all the NAPTRs associated with the SED Group. This field's 1591 value must be of the form specified in [RFC6116] (e.g., 1592 E2U+pstn:sip+sip). The allowable values are a matter of policy 1593 and not limited by this protocol. 1595 o ext: Point of extensibility described in Section 3.3. 1597 7. Framework Operations 1599 In addition to the operation specific object types, all operations 1600 MAY specify the minor version of the protocol that when used in 1601 conjunction with the major version (that can be for instance 1602 specified in the protocol namespace) can serve to identify the 1603 version of the SPPF protocol that the client is using. If the minor 1604 version is not specified, the latest minor version supported by the 1605 SPPF server for the given major version will be used. Additionally, 1606 operations that may potentially modify persistent protocol objects 1607 SHOULD include a transaction ID as well. 1609 7.1. Add Operation 1611 Any conforming transport protocol specification MUST provide a 1612 definition for the operation that adds one or more SPPF objects into 1613 the Registry. If the object, as identified by the request attributes 1614 that form part of the object's key, does not exist, then the Registry 1615 MUST create the object. If the object does exist, then the Registry 1616 MUST replace the current properties of the object with the properties 1617 passed in as part of the Add operation. 1619 If the entity that issued the command is not authorized to perform 1620 this operation an appropriate error message MUST be returned from 1621 amongst the response messages defined in "Response Message Types" 1622 section of the document. 1624 7.2. Delete Operation 1626 Any conforming transport protocol specification MUST provide a 1627 definition for the operation that deletes one or more SPPF objects 1628 from the Registry using the object's key. 1630 If the entity that issued the command is not authorized to perform 1631 this operation an appropriate error message MUST be returned from 1632 amongst the response messages defined in "Response Message Types" 1633 section of the document. 1635 When an object is deleted, any references to that object must of 1636 course also be removed as the SPPF server implementation fulfills the 1637 deletion request. Furthermore, the deletion of a composite object 1638 must also result in the deletion of the objects it contains. As a 1639 result, the following rules apply to the deletion of SPPF object 1640 types: 1642 o Destination Groups: When a destination group is deleted any 1643 references between that destination group and any SED group must 1644 be automatically removed by the SPPF implementation as part of 1645 fulfilling the deletion request. Similarly, any references 1646 between that destination group and any Public Identifier must be 1647 removed by the SPPF implementation as part of fulfilling the 1648 deletion request. 1650 o SED Groups: When a SED group is deleted any references between 1651 that SED group and any destination group must be automatically 1652 removed by the SPPF implementation as part of fulfilling the 1653 deletion request. Similarly any references between that SED group 1654 and any SED records must be removed by the SPPF implementation as 1655 part of fulfilling the deletion request. Furthermore, SED group 1656 offers relating that SED group must also be deleted as part of 1657 fulfilling the deletion request. 1659 o SED Records: When a SED record is deleted any references between 1660 that SED record and any SED group must be removed by the SPPF 1661 implementation as part of fulfilling the deletion request. 1662 Similarly, any reference between that SED record and any Public 1663 Identifier must be removed by the SPPF implementation as part of 1664 fulfilling the deletion request. 1666 o Public Identifiers: When a public identifier is deleted any 1667 references between that public identifier and any referenced 1668 destination group must be removed by the SPPF implementation as 1669 part of fulfilling the deletion request. Any references to SED 1670 records associated directly to that Public Identifier must also be 1671 deleted by the SPPF implementation as part of fulfilling the 1672 deletion request. 1674 7.3. Get Operations 1676 At times, on behalf of the Registrant, the Registrar may need to get 1677 information about SPPF objects that were previously provisioned in 1678 the Registry. A few examples include logging, auditing, and pre- 1679 provisioning dependency checking. This query mechanism is limited to 1680 aid provisioning scenarios and should not be confused with query 1681 protocols provided as part of the resolution system (e.g. ENUM and 1682 SIP). 1684 Any conforming "protocol" specification MUST provide a definition for 1685 the operation that queries the details of one or more SPPF objects 1686 from the Registry using the object's key. If the entity that issued 1687 the command is not authorized to perform this operation an 1688 appropriate error message MUST be returned from amongst the response 1689 messages defined in Section 5.3. 1691 If the response to the Get operation includes object(s) that extend 1692 the BasicObjType, the Registry MUST include the 'cDate' and 'mDate', 1693 if applicable. 1695 7.4. Accept Operations 1697 In SPPF, a SED Group Offer can be accepted or rejected by, or on 1698 behalf of, the Registrant to whom the SED Group has been offered 1699 (refer "Framework Data Model Objects" section of this document for a 1700 description of the SED Group Offer object). The Accept operation is 1701 used to accept the SED Group Offers. Any conforming transport 1702 protocol specification MUST provide a definition for the operation to 1703 accept SED Group Offers by, or on behalf of the Registrant, using the 1704 SED Group Offer object key. 1706 Not until access to a SED Group has been offered and accepted will 1707 the Registrant's organization ID be included in the peeringOrg list 1708 in that SED Group object, and that SED Group's peering information 1709 become a candidate for inclusion in the responses to the resolution 1710 requests submitted by that Registrant. A SED Group Offer that is in 1711 the "offered" status is accepted by, or on behalf of, the Registrant 1712 to which it has been offered. When the SED Group Offer is accepted 1713 the the SED Group Offer is moved to the "accepted" status and adds 1714 that data recipient's organization ID into the list of peerOrgIds for 1715 that SED Group. 1717 If the entity that issued the command is not authorized to perform 1718 this operation an appropriate error message MUST be returned from 1719 amongst the response messages defined in "Response Message Types" 1720 section of the document. 1722 7.5. Reject Operations 1724 In SPPF, a SED Group Offer object can be accepted or rejected by, or 1725 on behalf of, the Registrant to whom the SED Group has been offered 1726 (refer "Framework Data Model Objects" section of this document for a 1727 description of the SED Group Offer object). Furthermore, that offer 1728 may be rejected, regardless of whether or not it has been previously 1729 accepted. The Reject operation is used to reject the SED Group 1730 Offers. When the SED Group Offer is rejected that SED Group Offer is 1731 deleted, and, if appropriate, the data recipient's organization ID is 1732 removed from the list of peeringOrg IDs for that SED Group. Any 1733 conforming transport protocol specification MUST provide a definition 1734 for the operation to reject SED Group Offers by, or on behalf of the 1735 Registrant, using the SED Group Offer object key. 1737 If the entity that issued the command is not authorized to perform 1738 this operation an appropriate error message MUST be returned from 1739 amongst the response messages defined in "Response Message Types" 1740 section of the document. 1742 7.6. Get Server Details Operation 1744 In SPPF, Get Server Details operation can be used to request certain 1745 details about the SPPF server that include the SPPF server's current 1746 status, the major/minor version of the SPPF protocol supported by the 1747 SPPF server. 1749 Any conforming transport protocol specification MUST provide a 1750 definition for the operation to request such details from the SPPF 1751 server. If the entity that issued the command is not authorized to 1752 perform this operation an appropriate error message MUST be returned 1753 from amongst the response messages defined in "Response Message 1754 Types" section of the document. 1756 8. XML Considerations 1758 XML serves as the encoding format for SPPF, allowing complex 1759 hierarchical data to be expressed in a text format that can be read, 1760 saved, and manipulated with both traditional text tools and tools 1761 specific to XML. 1763 XML is case sensitive. Unless stated otherwise, XML specifications 1764 and examples provided in this document MUST be interpreted in the 1765 character case presented to develop a conforming implementation. 1767 This section discusses a small number of XML-related considerations 1768 pertaining to SPPF. 1770 8.1. Namespaces 1772 All SPPF elements are defined in the namespaces in the IANA 1773 Considerations section and in the Formal Framework Specification 1774 section of this document. 1776 8.2. Versioning and Character Encoding 1778 All XML instances SHOULD begin with an declaration to 1779 identify the version of XML that is being used, optionally identify 1780 use of the character encoding used, and optionally provide a hint to 1781 an XML parser that an external schema file is needed to validate the 1782 XML instance. 1784 Conformant XML parsers recognize both UTF-8 (defined in [RFC3629]) 1785 and UTF-16 (defined in [RFC2781]); per [RFC2277] UTF-8 is the 1786 RECOMMENDED character encoding for use with SPPF. 1788 Character encodings other than UTF-8 and UTF-16 are allowed by XML. 1789 UTF-8 is the default encoding assumed by XML in the absence of an 1790 "encoding" attribute or a byte order mark (BOM); thus, the "encoding" 1791 attribute in the XML declaration is OPTIONAL if UTF-8 encoding is 1792 used. SPPF clients and servers MUST accept a UTF-8 BOM if present, 1793 though emitting a UTF-8 BOM is NOT RECOMMENDED. 1795 Example XML declarations: 1797 1799 9. Security Considerations 1801 Many SPPF implementations manage data that is considered confidential 1802 and critical. Furthermore, SPPF implementations can support 1803 provisioning activities for multiple Registrars and Registrants. As 1804 a result any SPPF implementation must address the requirements for 1805 confidentiality, authentication, and authorization. 1807 9.1. Confidentiality and Authentication 1809 With respect to confidentiality and authentication, the transport 1810 protocol requirements section of this document contains security 1811 properties that the transport protocol must provide so that 1812 authenticated endpoints can exchange data confidentially and with 1813 integrity protection. Refer to that section and the resulting 1814 transport protocol specification document for the specific solutions 1815 to authentication and confidentiality. 1817 9.2. Authorization 1819 With respect to authorization, the SPPF server implementation must 1820 define and implement a set of authorization rules that precisely 1821 address (1) which Registrars will be authorized to create/modify/ 1822 delete each SPPF object type for given Registrant(s) and (2) which 1823 Registrars will be authorized to view/get each SPPF object type for 1824 given Registrant(s). These authorization rules are a matter of 1825 policy and are not specified within the context of SPPF. However, 1826 any SPPF implementation must specify these authorization rules in 1827 order to function in a reliable and safe manner. 1829 9.3. Denial of Service 1831 Guidance on Denial-of-Service (DoS) issues in general is given in 1832 [RFC4732], "Internet Denial of Service Considerations", which also 1833 gives a general vocabulary for describing the DoS issue. 1835 SPPF is a high-level client-server protocol that can be implemented 1836 on lower-level mechanisms such as remote procedure call and web- 1837 service API protocols. As such, it inherits any Denial-of-Service 1838 issues inherent to the specific lower-level mechanism used for any 1839 implementation of SPPF. SPPF also has its own set of higher-level 1840 exposures that are likely to be independent of lower-layer mechanism 1841 choices. 1843 9.3.1. DoS Issues Inherited from Transport Mechanism 1845 SPPF implementation is in general dependent on the selection and 1846 implementation of a lower-level transport protocol and a binding 1847 between that protocol and SPPF. The archetypal SPPF implementation 1848 uses XML (http://www.w3.org/TR/xml/) representation in a SOAP 1849 (http://www.w3.org/TR/soap/) request/response framework over HTTP 1850 ([RFC2616]), and probably also uses TLS ([RFC5246]) for on-the wire 1851 data integrity and participant authentication, and might use HTTP 1852 Digest authentication ([RFC2609]). 1854 The typical deployment scenario for SPPF is to have servers in a 1855 managed facility, and therefore techniques such as Network Ingress 1856 Filtering ([RFC2609]) are generally applicable. In short, any DoS 1857 mechanism affecting a typical HTTP implementation would affect such 1858 an SPPF implementation, and the mitigation tools for HTTP in general 1859 also therefore apply to SPPF. 1861 SPPF does not directly specify an authentication mechanism, instead 1862 relying on the lower-level transport protocol to provide for 1863 authentication. In general, authentication is an expensive 1864 operation, and one apparent attack vector is to flood an SPPF server 1865 with repeated requests for authentication, thereby exhausting its 1866 resources. SPPF implementations SHOULD therefore be prepared to 1867 handle authentication floods, perhaps by noting repeated failed login 1868 requests from a given source address and blocking that source 1869 address. 1871 9.3.2. DoS Issues Specific to SPPF 1873 The primary defense mechanism against DoS within SPPF is 1874 authentication. Implementations MUST tightly control access to the 1875 SPPF service, SHOULD implement DoS and other policy control 1876 screening, and MAY employ a variety of policy violation reporting and 1877 response measures such as automatic blocking of specific users and 1878 alerting of operations personnel. In short, the primary SPPF 1879 response to DoS-like activity by a user is to block that user or 1880 subject their actions to additional review. 1882 SPPF allows a client to submit multiple-element or "batch" requests 1883 that may insert or otherwise affect a large amount of data with a 1884 single request. In the simplest case, the server progresses 1885 sequentially through each element in a batch, completing one and 1886 before starting the next. Mid-batch failures are handled by stopping 1887 the batch and rolling-back the data store to its pre-request state. 1888 This "stop and roll-back" design provides a DoS opportunity. A 1889 hostile client could repeatedly issue large batch requests with one 1890 or more failing elements, causing the server to repeatedly stop and 1891 roll-back large transactions. The suggested response is to monitor 1892 clients for such failures, and take administrative action (such as 1893 blocking the user) when an excessive number of roll-backs is 1894 reported. 1896 An additional suggested response is for an implementer to set their 1897 maximum allowable XML message size, and their maximum allowable batch 1898 size at a level that they feel protects their operational instance, 1899 given the hardware sizing they have in place and the expected load 1900 and size needs that their users expect. 1902 9.4. Information Disclosure 1904 It is not uncommon for the logging systems to document on-the-wire 1905 messages for various purposes, such as, debug, audit, and tracking. 1906 At the minimum, the various support and administration staff will 1907 have access to these logs. Also, if an unprivileged user gains 1908 access to the SPPF deployments and/or support systems, it will have 1909 access to the information that is potentially deemed confidential. 1910 To manage information disclosure concerns beyond the transport level, 1911 SPPF implementations MAY provide support for encryption at the SPPF 1912 object level. 1914 9.5. Non Repudiation 1916 In some situations, it may be required to protect against denial of 1917 involvement (see [RFC4949]) and tackle non-repudiation concerns in 1918 regards to SPPF messages. This type of protection is useful to 1919 satisfy authenticity concerns related to SPPF messages beyond the 1920 end-to-end connection integrity, confidentiality, and authentication 1921 protection that the transport layer provides. This is an optional 1922 feature and some SPPF implementations MAY provide support for it. 1924 9.6. Replay Attacks 1926 Anti-replay protection ensures that a given SPPF object replayed at a 1927 later time doesn't affect the integrity of the system. SPPF provides 1928 at least one mechanism to fight against replay attacks. Use of the 1929 optional client transaction identifier allows the SPPF client to 1930 correlate the request message with the response and to be sure that 1931 it is not a replay of a server response from earlier exchanges. Use 1932 of unique values for the client transaction identifier is highly 1933 encouraged to avoid chance matches to a potential replay message. 1935 9.7. Man in the Middle 1937 The SPPF client or Registrar can be a separate entity acting on 1938 behalf of the Registrant in facilitating provisioning transactions to 1939 the Registry. Further, the transport layer provides end-to-end 1940 connection protection between SPPF client and the SPPF server. 1941 Therefore, man-in-the-middle attack is a possibility that may affect 1942 the integrity of the data that belongs to the Registrant and/or 1943 expose peer data to unintended actors in case well-established 1944 peering relationships already exist. 1946 10. Internationalization Considerations 1948 Character encodings to be used for SPPF elements are described in 1949 Section 8.2. The use of time elements in the protocol is specified 1950 in Section 3.2. Where human-readable languages are used in the 1951 protocol, those messages SHOULD be tagged according to [RFC5646], and 1952 the transport protocol MUST support a respective mechanism to 1953 transmit such tags together with those human-readable messages. If 1954 tags are absent, the language of the message defaults to "en" 1955 (English). 1957 11. IANA Considerations 1959 11.1. URN Assignments 1961 This document uses URNs to describe XML namespaces and XML schemas 1962 conforming to a Registry mechanism described in [RFC3688]. 1964 Two URI assignments are requested. 1966 Registration request for the SPPF XML namespace: 1967 urn:ietf:params:xml:ns:sppf:base:1 1968 Registrant Contact: IESG 1969 XML: None. Namespace URIs do not represent an XML specification. 1971 Registration request for the XML schema: 1972 URI: urn:ietf:params:xml:schema:sppf:1 1973 Registrant Contact: IESG 1974 XML: See the "Formal Specification" section of this document 1975 (Section 12). 1977 11.2. Organization Identifier Namespace Registry 1979 IANA is requested to create and maintain a Registry entitled "SPPF 1980 OrgIdType Namespaces". Strings used as OrgIdType Namespace 1981 identifiers MUST conform to the following syntax in the Augmented 1982 Backus-Naur Form (ABNF) [RFC5234] 1984 namespace = ALPHA * (ALPHA/DIGIT/"-") 1986 Assignments consist of the OrgIdType namespace string, and the 1987 definition of the associated namespace. This document makes the 1988 following initial assignment for the OrgIdType Namespaces: 1990 OrgIdType namespace string Namespace 1991 -------------------------- --------- 1992 IANA Enterprise Numbers iana-en 1994 Future assignments are to be made through the well known IANA Policy 1995 "RFC Required" (see section 4.1 of [RFC5226]) 1997 12. Formal Specification 1999 This section provides the draft XML Schema Definition for SPPF 2000 Protocol. 2002 2003 2007 2008 2009 ---- Generic Object key types to be defined by specific 2010 Transport/Architecture. The types defined here can 2011 be extended by the specific architecture to 2012 define the Object Identifiers ---- 2013 2014 2015 2017 2018 2019 ---- Generic type that represents the 2020 key for various objects in SPPF. ---- 2021 2022 2023 2024 2025 2026 2027 2028 2029 ---- Generic type that represents 2030 the key for a SED group offer. ---- 2031 2032 2033 2034 2035 2037 2038 2039 2040 2041 2042 ----Generic type that 2043 represents the key 2044 for a Pub Id. ---- 2045 2046 2047 2048 2049 2051 2052 2053 ---- Object Type Definitions ---- 2054 2055 2057 2058 2059 2060 2061 2062 2064 2066 2068 2070 2071 2072 2074 2075 2076 2077 2078 2079 2080 2081 2082 2084 2085 2086 2087 2088 2089 2090 2091 2092 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 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 2150 2151 2152 2153 2154 2155 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 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 2216 2217 2218 2219 2220 2222 2223 2224 2225 2226 2227 2228 2229 2230 ---- Abstract Object and Element Type Definitions ---- 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 2261 2262 2263 2264 2265 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 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 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 2362 2363 2364 2365 2366 2367 2368 2369 2370 2371 2372 2373 2374 2375 2376 2377 2378 2379 2380 2381 2382 2383 2384 2385 2386 2387 2388 2389 2390 2391 2392 2393 2394 2395 2397 13. Acknowledgments 2399 This document is a result of various discussions held in the DRINKS 2400 working group and within the DRINKS protocol design team, with 2401 contributions from the following individuals, in alphabetical order: 2402 Alexander Mayrhofer, David Schwartz, Deborah A Guyton, Lisa 2403 Dusseault, Manjul Maharishi, Mickael Marrache, Otmar Lendl, Richard 2404 Shockey, Samuel Melloul, Sumanth Channabasappa, Syed Ali, Vikas 2405 Bhatia, and Jeremy Barkan 2407 14. References 2409 14.1. Normative References 2411 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2412 Requirement Levels", BCP 14, RFC 2119, March 1997. 2414 [RFC2277] Alvestrand, H., "IETF Policy on Character Sets and 2415 Languages", BCP 18, RFC 2277, January 1998. 2417 [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 2418 10646", STD 63, RFC 3629, November 2003. 2420 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 2421 January 2004. 2423 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 2424 Resource Identifier (URI): Generic Syntax", STD 66, RFC 2425 3986, January 2005. 2427 [RFC4949] Shirey, R., "Internet Security Glossary, Version 2", RFC 2428 4949, August 2007. 2430 [RFC5067] Lind, S. and P. Pfautz, "Infrastructure ENUM 2431 Requirements", RFC 5067, November 2007. 2433 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 2434 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 2435 May 2008. 2437 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 2438 Specifications: ABNF", STD 68, RFC 5234, January 2008. 2440 14.2. Informative References 2442 [RFC2609] Guttman, E., Perkins, C., and J. Kempf, "Service Templates 2443 and Service: Schemes", RFC 2609, June 1999. 2445 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., 2446 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext 2447 Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. 2449 [RFC2781] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO 2450 10646", RFC 2781, February 2000. 2452 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 2453 A., Peterson, J., Sparks, R., Handley, M., and E. 2454 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 2455 June 2002. 2457 [RFC3403] Mealling, M., "Dynamic Delegation Discovery System (DDDS) 2458 Part Three: The Domain Name System (DNS) Database", RFC 2459 3403, October 2002. 2461 [RFC3761] Faltstrom, P. and M. Mealling, "The E.164 to Uniform 2462 Resource Identifiers (URI) Dynamic Delegation Discovery 2463 System (DDDS) Application (ENUM)", RFC 3761, April 2004. 2465 [RFC4725] Mayrhofer, A. and B. Hoeneisen, "ENUM Validation 2466 Architecture", RFC 4725, November 2006. 2468 [RFC4732] Handley, M., Rescorla, E., and IAB, "Internet Denial-of- 2469 Service Considerations", RFC 4732, December 2006. 2471 [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security 2472 (TLS) Protocol Version 1.2", RFC 5246, August 2008. 2474 [RFC5321] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321, 2475 October 2008. 2477 [RFC5486] Malas, D. and D. Meyer, "Session Peering for Multimedia 2478 Interconnect (SPEERMINT) Terminology", RFC 5486, March 2479 2009. 2481 [RFC5646] Phillips, A. and M. Davis, "Tags for Identifying 2482 Languages", BCP 47, RFC 5646, September 2009. 2484 [RFC6116] Bradner, S., Conroy, L., and K. Fujiwara, "The E.164 to 2485 Uniform Resource Identifiers (URI) Dynamic Delegation 2486 Discovery System (DDDS) Application (ENUM)", RFC 6116, 2487 March 2011. 2489 [RFC6461] Channabasappa, S., "Data for Reachability of Inter-/Intra- 2490 NetworK SIP (DRINKS) Use Cases and Protocol Requirements", 2491 RFC 6461, January 2012. 2493 [Unicode6.1] 2494 The Unicode Consortium, "The Unicode Standard - Version 2495 6.1", Unicode 6.1, January 2012. 2497 Authors' Addresses 2499 Kenneth Cartwright 2500 TNS 2501 1939 Roland Clarke Place 2502 Reston, VA 20191 2503 USA 2505 Email: kcartwright@tnsi.com 2507 Vikas Bhatia 2508 TNS 2509 1939 Roland Clarke Place 2510 Reston, VA 20191 2511 USA 2513 Email: vbhatia@tnsi.com 2515 Syed Wasim Ali 2516 NeuStar 2517 46000 Center Oak Plaza 2518 Sterling, VA 20166 2519 USA 2521 Email: syed.ali@neustar.biz 2523 David Schwartz 2524 XConnect 2525 316 Regents Park Road 2526 London N3 2XJ 2527 United Kingdom 2529 Email: dschwartz@xconnect.net