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