idnits 2.17.1
draft-ietf-drinks-spp-framework-04.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 (February 25, 2013) is 4071 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 2445, but no explicit
reference was found in the text
== Unused Reference: 'RFC5321' is defined on line 2462, 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.
--------------------------------------------------------------------------------
2 DRINKS K. Cartwright
3 Internet-Draft V. Bhatia
4 Intended status: Standards Track TNS
5 Expires: August 29, 2013 S. Ali
6 NeuStar
7 D. Schwartz
8 XConnect
9 February 25, 2013
11 Session Peering Provisioning Framework (SPPF)
12 draft-ietf-drinks-spp-framework-04
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 August 29, 2013.
40 Copyright Notice
42 Copyright (c) 2013 IETF Trust and the persons identified as the
43 document authors. All rights reserved.
45 This document is subject to BCP 78 and the IETF Trust's Legal
46 Provisions Relating to IETF Documents
47 (http://trustee.ietf.org/license-info) in effect on the date of
48 publication of this document. Please review these documents
49 carefully, as they describe your rights and restrictions with respect
50 to this document. Code Components extracted from this document must
51 include Simplified BSD License text as described in Section 4.e of
52 the Trust Legal Provisions and are provided without warranty as
53 described in the Simplified BSD License.
55 Table of Contents
57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
58 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 8
59 3. Framework High Level Design . . . . . . . . . . . . . . . . . 10
60 3.1. Framework Data Model . . . . . . . . . . . . . . . . . . . 10
61 3.2. Time Value . . . . . . . . . . . . . . . . . . . . . . . . 13
62 3.3. Extensibility . . . . . . . . . . . . . . . . . . . . . . 13
63 4. Transport Protocol Requirements . . . . . . . . . . . . . . . 14
64 4.1. Connection Oriented . . . . . . . . . . . . . . . . . . . 14
65 4.2. Request and Response Model . . . . . . . . . . . . . . . . 14
66 4.3. Connection Lifetime . . . . . . . . . . . . . . . . . . . 14
67 4.4. Authentication . . . . . . . . . . . . . . . . . . . . . . 14
68 4.5. Authorization . . . . . . . . . . . . . . . . . . . . . . 15
69 4.6. Confidentiality and Integrity . . . . . . . . . . . . . . 15
70 4.7. Near Real Time . . . . . . . . . . . . . . . . . . . . . . 15
71 4.8. Request and Response Sizes . . . . . . . . . . . . . . . . 15
72 4.9. Request and Response Correlation . . . . . . . . . . . . . 15
73 4.10. Request Acknowledgement . . . . . . . . . . . . . . . . . 15
74 4.11. Mandatory Transport . . . . . . . . . . . . . . . . . . . 16
75 5. Base Framework Data Structures and Response Codes . . . . . . 17
76 5.1. Basic Object Type and Organization Identifiers . . . . . . 17
77 5.2. Various Object Key Types . . . . . . . . . . . . . . . . . 17
78 5.2.1. Generic Object Key Type . . . . . . . . . . . . . . . 18
79 5.2.2. Derived Object Key Types . . . . . . . . . . . . . . . 18
80 5.3. Response Message Types . . . . . . . . . . . . . . . . . . 20
81 6. Framework Data Model Objects . . . . . . . . . . . . . . . . . 23
82 6.1. Destination Group . . . . . . . . . . . . . . . . . . . . 23
83 6.2. Public Identifier . . . . . . . . . . . . . . . . . . . . 24
84 6.3. SED Group . . . . . . . . . . . . . . . . . . . . . . . . 29
85 6.4. SED Record . . . . . . . . . . . . . . . . . . . . . . . . 33
86 6.5. SED Group Offer . . . . . . . . . . . . . . . . . . . . . 37
87 6.6. Egress Route . . . . . . . . . . . . . . . . . . . . . . . 39
88 7. Framework Operations . . . . . . . . . . . . . . . . . . . . . 41
89 7.1. Add Operation . . . . . . . . . . . . . . . . . . . . . . 41
90 7.2. Delete Operation . . . . . . . . . . . . . . . . . . . . . 41
91 7.3. Get Operations . . . . . . . . . . . . . . . . . . . . . . 42
92 7.4. Accept Operations . . . . . . . . . . . . . . . . . . . . 42
93 7.5. Reject Operations . . . . . . . . . . . . . . . . . . . . 43
94 7.6. Get Server Details Operation . . . . . . . . . . . . . . . 43
95 8. XML Considerations . . . . . . . . . . . . . . . . . . . . . . 45
96 8.1. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 45
97 8.2. Versioning and Character Encoding . . . . . . . . . . . . 45
98 9. Security Considerations . . . . . . . . . . . . . . . . . . . 46
99 9.1. Confidentiality and Authentication . . . . . . . . . . . . 46
100 9.2. Authorization . . . . . . . . . . . . . . . . . . . . . . 46
101 9.3. Denial of Service . . . . . . . . . . . . . . . . . . . . 46
102 9.3.1. DoS Issues Inherited from Transport Mechanism . . . . 46
103 9.3.2. DoS Issues Specific to SPPF . . . . . . . . . . . . . 47
104 9.4. Information Disclosure . . . . . . . . . . . . . . . . . . 48
105 9.5. Non Repudiation . . . . . . . . . . . . . . . . . . . . . 48
106 9.6. Replay Attacks . . . . . . . . . . . . . . . . . . . . . . 48
107 9.7. Man in the Middle . . . . . . . . . . . . . . . . . . . . 48
108 10. Internationalization Considerations . . . . . . . . . . . . . 50
109 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 51
110 12. Formal Specification . . . . . . . . . . . . . . . . . . . . . 52
111 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 61
112 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 62
113 14.1. Normative References . . . . . . . . . . . . . . . . . . . 62
114 14.2. Informative References . . . . . . . . . . . . . . . . . . 62
115 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 64
117 1. Introduction
119 Service providers and enterprises use routing databases known as
120 registries to make session routing decisions for Voice over IP, SMS
121 and MMS traffic exchanges. This document is narrowly focused on the
122 provisioning framework for these registries. This framework
123 prescribes a way for an entity to provision session-related data into
124 a Registry. The data being provisioned can be optionally shared with
125 other participating peering entities. The requirements and use cases
126 driving this framework have been documented in [RFC6461].
128 Three types of provisioning flows have been described in the use case
129 document: client to Registry, Registry to local data repository and
130 Registry to Registry. This document addresses client to Registry
131 flow enabling the need to provision Session Establishment Data (SED).
132 The framework that supports flow of messages to facilitate client to
133 Registry provisioning is referred to as Session Peering Provisioning
134 Framework (SPPF).
136 The role of the "client" and the "server" only applies to the
137 connection, and those roles are not related in any way to the type of
138 entity that participates in a protocol exchange. For example, a
139 Registry might also include a "client" when such a Registry initiates
140 a connection (for example, for data distribution to SSP).
142 *--------* *------------* *------------*
143 | | (1). Client | | (3).Registry | |
144 | Client | ------------> | Registry |<------------->| Registry |
145 | | to Registry | | to Registry | |
146 *--------* *------------* *------------*
147 / \ \
148 / \ \
149 / \ \
150 / \ v
151 / \ ...
152 / \
153 / (2). Distrib \
154 / Registry data \
155 / to local data \
156 V store V
157 +----------+ +----------+
158 |Local Data| |Local Data|
159 |Repository| |Repository|
160 +----------+ +----------+
162 Three Registry Provisioning Flows
164 Figure 1
166 A "terminating" SIP Service Provider (SSP) provisions Session
167 Establishment Data or SED into the Registry to be selectively shared
168 with other peer SSPs.
170 SED is typically used by various downstream SIP signaling systems to
171 route a call to the next hop associated with the called domain.
172 These systems typically use a local data store ("Local Data
173 Repository") as their source of session routing information. More
174 specifically, the SED data is the set of parameters that the outgoing
175 signaling path border elements (SBEs) need to initiate the session.
176 See [RFC5486] for more details.
178 A Registry may distribute the provisioned data into local data
179 repositories or may additionally offer a central query resolution
180 service (not shown in the above figure) for query purposes.
182 A key requirement for the SPPF is to be able to accommodate two basic
183 deployment scenarios:
185 1. A resolution system returns a Look-Up Function (LUF) that
186 comprises the target domain to assist in call routing (as
187 described in [RFC5486]). In this case, the querying entity may
188 use other means to perform the Location Routing Function (LRF)
189 which in turn helps determine the actual location of the
190 Signaling Function in that domain.
192 2. A resolution system returns a Location Routing Function (LRF)
193 that comprises the location (address) of the signaling function
194 in the target domain (as described in [RFC5486]).
196 In terms of framework design, SPPF is agnostic to the transport
197 protocol. This document includes the specification of the data model
198 and identifies, but does not specify, the means to enable protocol
199 operations within a request and response structure. That aspect of
200 the specification has been delegated to the "protocol" specification
201 for the framework. To encourage interoperability, the framework
202 supports extensibility aspects.
204 In this document, XML schema is used to describe the building blocks
205 of the SPPF and to express the data types, the semantic relationships
206 between the various data types, and the various constraints as a
207 binding construct. However, the "protocol" specification is free to
208 choose any data representation format as long as it meets the
209 requirements laid out in the SPPF XML schema definition. As an
210 example, XML and JSON are two widely used data representation
211 formats.
213 This document is organized as follows:
215 o Section 2 provides the terminology
217 o Section 3 provides an overview of SPPF, including functional
218 entities and data model
220 o Section 4 specifies requirements for SPPF transport protocols
222 o Section 5 describes the base framework data structures, the
223 generic response types that MUST be supported by a conforming
224 transport "protocol" specification, and the basic object type
225 most first class objects extend from
227 o Section 6 provides a detailed description of the data model
228 object specifications
230 o Section 8 defines XML considerations XML parsers must meet to
231 conform to this specification
233 o Section 7 describes the operations that are supported by the
234 data model
236 o Section 7 describes the operations that are supported by the
237 data model
239 o Sections 9 - 11 discuss security, internationalization and IANA
240 considerations
242 o Section 12 normatively defines the SPPF using its XML Schema
243 Definition.
245 2. Terminology
247 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
248 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
249 document are to be interpreted as described in [RFC2119].
251 This document reuses terms from [RFC3261], [RFC5486], use cases and
252 requirements documented in [RFC6461] and the ENUM Validation
253 Architecture [RFC4725].
255 In addition, this document specifies the following additional terms:
257 SPPF: Session Peering Provisioning Framework, the framework used by
258 a transport protocol to provision data into a Registry (see arrow
259 labeled "1." in Figure 1 of [RFC6461]). It is the primary scope
260 of this document.
262 Client: In the context of SPPF, this is an application that
263 initiates a provisioning request. It is sometimes referred to as
264 a "Registry client".
266 Server: In the context of SPPF, this is an application that
267 receives a provisioning request and responds accordingly. It is
268 sometimes referred to as a Registry.
270 Registry: The Registry operates a master database of Session
271 Establishment Data for one or more Registrants.
273 Registrant: The definition of a Registrant is based on [RFC4725].
274 It is the end-user, the person or organization that is the
275 "holder" of the Session Establishment Data being provisioned into
276 the Registry by a Registrar. For example, in [RFC6461], a
277 Registrant is pictured as a SIP Service Provider in Figure 2.
279 Within the confines of a Registry, a Registrant is uniquely
280 identified by a well-known ID.
282 Registrar: The definition of a Registrar is based on [RFC4725]. It
283 is an entity that performs provisioning operations on behalf of a
284 Registrant by interacting with the Registry via SPPF operations.
285 In other words the Registrar is the SPPF Client. The Registrar
286 and Registrant roles are logically separate to allow, but not
287 require, a single Registrar to perform provisioning operations on
288 behalf of more than one Registrant.
290 Peering Organization: A Peering Organization is an entity to which
291 a Registrant's SED Groups are made visible using the operations of
292 SPPF.
294 3. Framework High Level Design
296 This section introduces the structure of the data model and provides
297 the information framework for the SPPF. The data model is defined
298 along with all the objects manipulated by a conforming transport
299 protocol and their relationships.
301 3.1. Framework Data Model
303 The data model illustrated and described in Figure 2 defines the
304 logical objects and the relationships between these objects supported
305 by SPPF. SPPF defines protocol operations through which an SPPF
306 client populates a Registry with these logical objects. SPPF clients
307 belonging to different Registrars may provision data into the
308 Registry using a conforming transport protocol that implements these
309 operations
311 The logical structure presented below is consistent with the
312 terminology and requirements defined in [RFC6461].
314 +-------------+ +-----------------+
315 | all object | |Egress Route: |
316 | types | 0..n | rant, |
317 +-------------+ +--| egrRteName, |
318 |0..n / | pref, |
319 | / | regxRewriteRule,|
320 |2 / | ingrSedGrp, |
321 +----------------------+ / | svcs |
322 |Organization: | / +-----------------+
323 | orgId | /
324 +----------------------+ /
325 |0..n /
326 | /
327 |A SED Group is /
328 |associated with /
329 |zero or more / +---[abstract]----+
330 |Peering / | SED Record: |
331 |Organizations / | rant, |
332 | / | sedName, |0..n
333 |0..n / | sedFunction, |------|
334 +--------+--------------+0..n 0..n| isInSvc, | |
335 |SED Group: |------------------| ttl | |
336 | rant, | +-----------------+ |
337 | sedGrpName, | ^ |
338 | isInSvc, | |Various types |
339 | sedRecRef, | |of SED |
340 | peeringOrg, | |Records |
341 | sourceIdent, | +-----+------------+ |
342 | priority, | | | | |
343 | dgName | +----+ +-------+ +----+ |
344 +-----------------------+ | URI| | NAPTR | | NS | |
345 |0..n +----+ +-------+ +----+ |
346 | |
347 | +-----[abstract]------+ |
348 | |Public Identifier: | |
349 |0..n | rant, | |
350 +----------------------+0..n 0..n| publicIdentifier, | |
351 | Dest Group: |--------------| destGrpRef | |
352 | rant, | | | |
353 | dgName | +---------------------+ |
354 +----------------------+ ^Various types |
355 |of Public |
356 |Identifiers |
357 +---------+-------+------+----------+ |
358 | | | | | |
359 +------+ +-----+ +-----+ +-----+ +------+ |
360 | URI | | TNP | | TNR | | RN | |TN |----------|
361 +------+ +-----+ +-----+ +-----+ +------+ 0..n
362 Figure 2
364 The objects and attributes that comprise the data model can be
365 described as follows (objects listed from the bottom up):
367 o Public Identifier:
368 From a broad perspective a public identifier is a well-known
369 attribute that is used as the key to perform resolution lookups.
370 Within the context of SPPF, a public identifier object can be a
371 Telephone Number (TN), a range of Telephone Numbers, a PSTN
372 Routing Number (RN), a TN prefix, or a URI.
374 An SPPF Public Identifier is associated with a Destination Group
375 to create a logical grouping of Public Identifiers that share a
376 common set of Session Establishment Data (e.g. routes).
378 A TN Public Identifier may optionally be associated with zero or
379 more individual SED Records. This ability for a Public Identifier
380 to be directly associated with a SED Record, as opposed to being
381 associated with a Destination Group, supports the use cases where
382 the SED Record contains data specifically tailored to an
383 individual TN Public Identifier.
385 o Destination Group:
386 A named collection of zero or more Public Identifiers that can be
387 associated with one or more SED Groups for the purpose of
388 facilitating the management of their common session establishment
389 information.
391 o SED Group:
392 A SED Group contains a set of SED Record references, a set of
393 Destination Group references, and a set of peering organization
394 identifiers. This is used to establish a three part relationships
395 between a set of Public Identifiers, the session establishment
396 information (SED) shared across these Public Identifiers, and the
397 list of peering organizations whose query responses from the
398 resolution system may include the session establishment
399 information contained in a given SED group. In addition, the
400 sourceIdent element within a SED Group, in concert with the set of
401 peering organization identifiers, enables fine-grained source
402 based routing. For further details about the SED Group and source
403 based routing, refer to the definitions and descriptions in
404 Section 6.1.
406 o SED Record:
407 A SED Record contains the data that a resolution system returns in
408 response to a successful query for a Public Identifier. SED
409 Records are generally associated with a SED Group when the SED
410 within is not specific to a Public Identifier.
411 To support the use cases defined in [RFC6461], SPPF framework
412 defines three type of SED Records: URIType, NAPTRType, and NSType.
413 These SED Records extend the abstract type SedRecType and inherit
414 the common attribute 'priority' that is meant for setting
415 precedence across the SED records defined within a SED Group in a
416 protocol agnostic fashion.
418 o Egress Route:
419 In a high-availability environment, the originating SSP likely has
420 more than one egress paths to the ingress SBE of the target SSP.
421 The Egress Route allows the originating SSP to choose a specific
422 egress SBE to be associated with the target ingress SBE. the
423 'svcs' element identifies 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 time,
449 but it is not approved for use in SPPF messages.
451 3.3. Extensibility
453 The framework contains various points of extensiblity in form of the
454 "ext" elements. Extensions used beyond the scope of privat e 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. SPPF
500 Clients 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 date and time of the object creation and
579 update, if applicable, for all Get operations (see Section 7). If
580 the client passed in either date and time values, the Registry MUST
581 ignore it. The Registrar performs the SPPF operations on behalf of
582 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: "namespace:
597 value" (for example "iana-en:32473"). See the IANA Consideration
598 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 there own abstract key types. Because these object
650 key types are abstract, these 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
660 being offered, as one of its attributes. In addition to the
661 Delete and Get operations, these key types are used in Accept
662 and Reject operations on a SED Group Offer object. The
663 structure of abstract 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
686 identify the value and type of Public Identity and also contain
687 the organization ID of the Registrant that is the owner of the
688 Public Identity object. A Public Identity object key in SPPF is
689 uniquely identified by the the Registrant's organization ID, the
690 value of the public identity, and, optionally, the Destination
691 Group name the public identity belongs to. Consequently, any
692 concrete representation of the PubIdKeyType MUST contain the
693 following attributes:
695 * Registrant Id: The unique organization ID that identifies
696 the Registrant.
698 * Destination Group name: The name of the Destination Group
699 the Public Identity is associated with. This is an
700 optional attribute.
702 * Type: The type of Public Identity.
704 * Value: The value of the Public Identity.
706 The PubIdKeyType is used in Delete and Get operations on a
707 Public Identifier object.
709 o The structure of abstract PubIdKeyType is as follows:
711
712
713
714
715
716 ---- Generic type that represents the key for a Pub Id. ----
717
718
719
720
721
723 A Public Identity object MUST use attributes of PubIdKeyType for its
724 unique identification . Refer to Section 6 for a description of
725 Public Identity object.
727 5.3. Response Message Types
729 This section contains the listing of response types that MUST be
730 defined by the SPPF conforming transport protocol specification and
731 implemented by a conforming SPPF server.
733 +---------------------+---------------------------------------------+
734 | Response Type | Description |
735 +---------------------+---------------------------------------------+
736 | Request Succeeded | Any conforming specification MUST define a |
737 | | response to indicate that a given request |
738 | | succeeded. |
739 | | |
740 | Request syntax | Any conforming specification MUST define a |
741 | invalid | response to indicate that a syntax of a |
742 | | given request was found invalid. |
743 | | |
744 | Request too large | Any conforming specification MUST define a |
745 | | response to indicate that the count of |
746 | | entities in the request is larger than the |
747 | | server is willing or able to process. |
748 | | |
749 | Version not | Any conforming specification MUST define a |
750 | supported | response to indicate that the server does |
751 | | not support the version of the SPPF |
752 | | protocol specified in the request. |
753 | | |
754 | Command invalid | Any conforming specification MUST define a |
755 | | response to indicate that the operation |
756 | | and/or command being requested by the |
757 | | client is invalid and/or not supported by |
758 | | the server. |
759 | | |
760 | System temporarily | Any conforming specification MUST define a |
761 | unavailable | response to indicate that the SPPF server |
762 | | is temporarily not available to serve |
763 | | client request. |
764 | | |
765 | Unexpected internal | Any conforming specification MUST define a |
766 | system or server | response to indicate that the SPPF server |
767 | error. | encountered an unexpected error that |
768 | | prevented the server from fulfilling the |
769 | | request. |
770 | | |
771 | Attribute value | Any conforming specification MUST define a |
772 | invalid | response to indicate that the SPPF server |
773 | | encountered an attribute or property in the |
774 | | request that had an invalid/bad value. |
775 | | Optionally, the specification MAY provide a |
776 | | way to indicate the Attribute Name and the |
777 | | Attribute Value to identify the object that |
778 | | was found to be invalid. |
779 | | |
780 | Object does not | Any conforming specification MUST define a |
781 | exist | response to indicate that an object present |
782 | | in the request does not exist on the SPPF |
783 | | server. Optionally, the specification MAY |
784 | | provide a way to indicate the Attribute |
785 | | Name and the Attribute Value that |
786 | | identifies the non-existent object. |
787 | | |
788 | Object status or | Any conforming specification MUST define a |
789 | ownership does not | response to indicate that the operation |
790 | allow for | requested on an object present in the |
791 | operation. | request cannot be performed because the |
792 | | object is in a status that does not allow |
793 | | the said operation or the user requesting |
794 | | the operation is not authorized to perform |
795 | | the said operation on the object. |
796 | | Optionally, the specification MAY provide a |
797 | | way to indicate the Attribute Name and the |
798 | | Attribute Value that identifies the object. |
799 +---------------------+---------------------------------------------+
801 Table 1: Response Types
803 When the response messages are "parameterized" with the Attribute
804 Name and Attribute Value, then the use of these parameters MUST
805 adhere to the following rules:
807 o Any value provided for the Attribute Name parameter MUST be an
808 exact XSD element name of the protocol data element that the
809 response message is referring to. For example, valid values for
810 "attribute name" are "dgName", "sedGrpName", "sedRec", etc.
812 o The value for Attribute Value MUST be the value of the data
813 element to which the preceding Attribute Name refers.
815 o Response type "Attribute value invalid" MUST be used whenever an
816 element value does not adhere to data validation rules.
818 o Response types "Attribute value invalid" and "Object does not
819 exist" MUST not be used interchangeably. Response type "Object
820 does not exist" MUST be returned by an Update/Del/Accept/Reject
821 operation when the data element(s) used to uniquely identify a
822 pre-existing object do not exist. If the data elements used to
823 uniquely identify an object are malformed, then response type
824 "Attribute value invalid" MUST be returned.
826 6. Framework Data Model Objects
828 This section provides a description of the specification of each
829 supported data model object (the nouns) and identifies the commands
830 (the verbs) that MUST be supported for each data model object.
831 However, the specification of the data structures necessary to
832 support each command is delegated to an SPPF conforming transport
833 protocol specification.
835 6.1. Destination Group
837 Destination Group represents a set of Public Identifiers with common
838 session establishment information. The transport protocol MUST
839 support the ability to Create, Modify, Get, and Delete Destination
840 Groups (refer the "Framework Operations" section of this document for
841 a generic description of various operations).
843 A Destination Group object MUST be uniquely identified by attributes
844 as defined in the description of "ObjKeyType" in the section "Generic
845 Object Key Type" of this document.
847 The DestGrpType object structure is defined as follows:
849
850
851
852
853
854
855
856
857
859 The DestGrpType object is composed of the following elements:
861 o base: All first class objects extend BasicObjType (see
862 Section 5.1).
864 o dgName: The character string that contains the name of the
865 Destination Group.
867 o ext: Point of extensibility described in Section 3.3.
869 6.2. Public Identifier
871 A Public Identifier is the search key used for locating the session
872 establishment data (SED). In many cases, a Public Identifier is
873 attributed to the end user who has a retail relationship with the
874 service provider or Registrant organization. SPPF supports the
875 notion of the carrier-of-record as defined in [RFC5067]. Therefore,
876 the Registrant under whom the Public Identity is being created can
877 optionally claim to be a carrier-of-record.
879 SPPF identifies three types of Public Identifiers: telephone numbers
880 (TN), routing numbers (RN), and URI type of Public Identifiers. SPPF
881 provides structures to manage a single TN, a contiguous range of TNs,
882 and a TN prefix. The transport protocol MUST support the ability to
883 Create, Modify, Get, and Delete Public Identifiers (refer the
884 "Framework Operations" section of this document for a generic
885 description of various operations).
887 A Public Identity object MUST be uniquely identified by attributes as
888 defined in the description of "PubIdKeyType" in the section
889 Section 5.2.2.
891 The abstract XML schema type definition PubIDType is a generalization
892 for the concrete Public Identifier schema types. PubIDType element
893 'dgName' represents the name of the destination group that a given
894 Public Identifier may be a member of. The PubIDType object structure
895 is defined as follows:
897
898
899
900
901
902
903
904
905
907 A Public Identifier may be provisioned as a member of a Destination
908 Group or provisioned outside of a Destination Group. A Public
909 Identifier that is provisioned as a member of a Destination Group is
910 intended to be associated with its SED through the SED Group(s) that
911 are associated with its containing Destination Group. A Public
912 Identifier that is not provisioned as a member of a Destination Group
913 is intended to be associated with its SED through the SED Records
914 that are directly associated with the Public Identifier.
916 A telephone number is provisioned using the TNType, an extension of
917 PubIDType. When a Public Identifier is provisioned as a member of a
918 Destination Group, each TNType object is uniquely identified by the
919 combination of its value contained within element, and the
920 unique key of its parent Destination Group (dgName and rantId). In
921 other words a given telephone number string may exist within one or
922 more Destination Groups, but must not exist more than once within a
923 Destination Group. A Public Identifier that is not provisioned as a
924 member of a Destination Group is uniquely identified by the
925 combination of its value, and its Registrant ID. TNType is defined
926 as follows:
928
929
930
931
932
933
934
936
937
938
939
941
942
943
944
945
946
947
949
950
951
952
953
954
956 TNType consists of the following attributes:
958 o tn: Telephone number to be added to the Registry.
960 o sedRecRef: Optional reference to SED records that are directly
961 associated with the TN Public Identifier. Following the SPPF
962 data model, the SED record could be a protocol agnostic URIType
963 or another type.
965 o corInfo: corInfo is an optional parameter of type CORInfoType
966 that allows the Registrant organization to set forth a claim to
967 be the carrier-of-record (see [RFC5067]). This is done by
968 setting the value of element of the CORInfoType
969 object structure to "true". The other two parameters of the
970 CORInfoType, and are set by the Registry to
971 describe the outcome of the carrier-of-record claim by the
972 Registrant. In general, inclusion of parameter is
973 useful if the Registry has the authority information, such as,
974 the number portability data, etc., in order to qualify whether
975 the Registrant claim can be satisfied. If the carrier-of-record
976 claim disagrees with the authority data in the Registry, whether
977 the TN add operation fails or not is a matter of policy and it
978 is beyond the scope of this document.
980 A routing number is provisioned using the RNType, an extension of
981 PubIDType. The Registrant organization can add the RN and associate
982 it with the appropriate destination group to share the route
983 information. This allows SSPs to use the RN search key to derive the
984 ingress routes for session establishment at the runtime resolution
985 process (see [RFC3761]. Each RNType object is uniquely identified by
986 the combination of its value inside the element, and the unique
987 key of its parent Destination Group (dgName and rantId). In other
988 words a given routing number string may exist within one or more
989 Destination Groups, but must not exist more than once within a
990 Destination Group. RNType is defined as follows:
992
993
994
995
996
997
998
999
1000
1001
1003 RNType has the following attributes:
1005 o rn: Routing Number used as the search key.
1007 o corInfo: corInfo is an optional parameter of type CORInfoType
1008 that allows the Registrant organization to set forth a claim to
1009 be the carrier-of-record (see [RFC5067])
1011 TNRType structure is used to provision a contiguous range of
1012 telephone numbers. The object definition requires a starting TN and
1013 an ending TN that together define the span of the TN range. Use of
1014 TNRType is particularly useful when expressing a TN range that does
1015 not include all the TNs within a TN block or prefix. The TNRType
1016 definition accommodates the open number plan as well such that the
1017 TNs that fall between the start and end TN range may include TNs with
1018 different length variance. Whether the Registry can accommodate the
1019 open number plan semantics is a matter of policy and is beyond the
1020 scope of this document. Each TNRType object is uniquely identified
1021 by the combination of its value that in turn is a combination of the
1022 and elements, and the unique key of its parent
1023 Destination Group (dgName and rantId). In other words a given TN
1024 Range may exist within one or more Destination Groups, but must not
1025 exist more than once within a Destination Group. TNRType object
1026 structure definition is as follows:
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1039
1040
1041
1042
1043
1044
1046 TNRType has the following attributes:
1048 o startTn: Starting TN in the TN range
1050 o endTn: The last TN in the TN range
1052 o corInfo: corInfo is an optional parameter of type CORInfoType
1053 that allows the Registrant organization to set forth a claim to
1054 be the carrier-of-record (see [RFC5067])
1056 In some cases, it is useful to describe a set of TNs with the help of
1057 the first few digits of the telephone number, also referred to as the
1058 telephone number prefix or a block. A given TN prefix may include
1059 TNs with different length variance in support of open number plan.
1060 Once again, whether the Registry supports the open number plan
1061 semantics is a matter of policy and it is beyond the scope of this
1062 document. The TNPType data structure is used to provision a TN
1063 prefix. Each TNPType object is uniquely identified by the
1064 combination of its value in the element, and the unique
1065 key of its parent Destination Group (dgName and rantId). TNPType is
1066 defined as follows:
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1079 TNPType consists of the following attributes:
1081 o tnPrefix: The telephone number prefix
1083 o corInfo: corInfo is an optional parameter of type CORInfoType
1084 that allows the Registrant organization to set forth a claim to
1085 be the carrier-of-record (see [RFC5067])
1087 In some cases, a Public Identifier may be a URI, such as an email
1088 address. The URIPubIdType object is comprised of the data element
1089 necessary to house such Public Identifiers. Each URIPubIdType object
1090 is uniquely identified by the combination of its value in the
1091 element, and the unique key of its parent Destination Group (dgName
1092 and rantId). URIPubIdType is defined as follows:
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1105 URIPubIdType consists of the following attributes:
1107 o uri: The value that acts a Public Identifier.
1109 o ext: Point of extensibility described in Section 3.3.
1111 6.3. SED Group
1113 SED Group is a grouping of one or more Destination Group, the common
1114 SED Records, and the list of peer organizations with access to the
1115 SED Records associated with a given SED Group. It is this indirect
1116 linking of public identifiers to their Session Establishment Data
1117 that significantly improves the scalability and manageability of the
1118 peering data. Additions and changes to SED information are reduced
1119 to a single operation on a SED Group or SED Record , rather than
1120 millions of data updates to individual public identifier records that
1121 individually contain their peering data. The transport protocol MUST
1122 support the ability to Create, Modify, Get, and Delete SED Groups
1123 (refer the "Framework Operations" section of this document for a
1124 generic description of various operations).
1126 A SED Group object MUST be uniquely identified by attributes as
1127 defined in the description of "ObjKeyType" in the section "Generic
1128 Object Key Type" of this document.
1130 The SedGrpType object structure is defined as follows:
1132
1133
1134
1135
1136
1137
1139
1141
1143
1145
1146
1147
1148
1149
1150
1151
1153
1154
1155
1156
1157
1158
1159
1161 The SedGrpType object is composed of the following elements:
1163 o base: All first class objects extend BasicObjType (see
1164 Section 5.1).
1166 o sedGrpName: The character string that contains the name of the
1167 SED Group. It uniquely identifies this object within the
1168 context of the Registrant ID (a child element of the base
1169 element as described above).
1171 o sedRecRef: Set of zero or more objects of type SedRecRefType
1172 that house the unique keys of the SED Records (containing the
1173 session establishment data) that the SedGrpType object refers to
1174 and their relative priority within the context of this SED
1175 Group.
1177 o dgName: Set of zero or more names of DestGrpType object
1178 instances. Each dgName name, in association with this SED
1179 Group's Registrant ID, uniquely identifies a DestGrpType object
1180 instance whose public identifiers are reachable using the
1181 session establishment information housed in this SED Group. An
1182 intended side affect of this is that a SED Group cannot provide
1183 session establishment information for a Destination Group
1184 belonging to another Registrant.
1186 o peeringOrg: Set of zero or more peering organization IDs that
1187 have accepted an offer to receive this SED Group's information.
1188 Note that this identifier "peeringOrg" is an instance of
1189 OrgIdType. The set of peering organizations in this list is not
1190 directly settable or modifiable using the addSedGrpsRqst
1191 operation. This set is instead controlled using the SED offer
1192 and accept operations.
1194 o sourceIdent: Set of zero or more SourceIdentType object
1195 instances. These objects, described further below, house the
1196 source identification schemes and identifiers that are applied
1197 at resolution time as part of source based routing algorithms
1198 for the SED Group.
1200 o isInSvc: A boolean element that defines whether this SED Group
1201 is in service. The session establishment information contained
1202 in a SED Group that is in service is a candidate for inclusion
1203 in resolution responses for public identities residing in the
1204 Destination Group associated with this SED Group. The session
1205 establishment information contained in a SED Group that is not
1206 in service is not a candidate for inclusion in resolution
1207 responses.
1209 o priority: Zero or one priority value that can be used to provide
1210 a relative value weighting of one SED Group over another. The
1211 manner in which this value is used, perhaps in conjunction with
1212 other factors, is a matter of policy.
1214 o ext: Point of extensibility described in Section 3.3.
1216 As described above, the SED Group contains a set of references to SED
1217 record objects. A SED record object is based on an abstract type:
1218 SedRecType. The concrete types that use SedRecType as an extension
1219 base are NAPTRType, NSType, and URIType. The definitions of these
1220 types are included the SED Record section of this document.
1222 The SedGrpType object provides support for source-based routing via
1223 the peeringOrg data element and more granular source base routing via
1224 the source identity element. The source identity element provides
1225 the ability to specify zero or more of the following in association
1226 with a given SED Group: a regular expression that is matched against
1227 the resolution client IP address, a regular expression that is
1228 matched against the root domain name(s), and/or a regular expression
1229 that is matched against the calling party URI(s). The result will be
1230 that, after identifying the visible SED Groups whose associated
1231 Destination Group(s) contain the lookup key being queried and whose
1232 peeringOrg list contains the querying organizations organization ID,
1233 the resolution server will evaluate the characteristics of the Source
1234 URI, and Source IP address, and root domain of the lookup key being
1235 queried. The resolution server then compares these criteria against
1236 the source identity criteria associated with the SED Groups. The
1237 session establishment information contained in SED Groups that have
1238 source based routing criteria will only be included in the resolution
1239 response if one or more of the criteria matches the source criteria
1240 from the resolution request. The Source Identity data element is of
1241 type SourceIdentType, whose structure is defined as follows:
1243
1244
1245
1246
1248
1249
1250
1252
1253
1254
1255
1256
1257
1258
1260 The SourceIdentType object is composed of the following data
1261 elements:
1263 o sourceIdentScheme: The source identification scheme that this
1264 source identification criteria applies to and that the
1265 associated sourceIdentRegex should be matched against.
1267 o sourceIdentRegex: The regular expression that should be used to
1268 test for a match against the portion of the resolution request
1269 that is dictated by the associated sourceIdentScheme.
1271 o ext: Point of extensibility described in Section 3.3.
1273 6.4. SED Record
1275 SED Group represents a combined grouping of SED Records that define
1276 session establishment information. However, SED Records need not be
1277 created to just serve a single SED Group. SED Records can be created
1278 and managed to serve multiple SED Groups. As a result, a change for
1279 example to the properties of a network node used for multiple routes,
1280 would necessitate just a single update operation to change the
1281 properties of that node. The change would then be reflected in all
1282 the SED Groups whose SED record set contains a reference to that
1283 node. The transport protocol MUST support the ability to Create,
1284 Modify, Get, and Delete SED Records (refer the "Framework Operations"
1285 section of this document for a generic description of various
1286 operations).
1288 A SED Record object MUST be uniquely identified by attributes as
1289 defined in the description of "ObjKeyType" in the section "Generic
1290 Object Key Type" of this document.
1292 The SedRecType object structure is defined as follows:
1294
1295
1296
1297
1298
1299
1301
1302
1303
1304
1305
1306
1308
1309
1310
1311
1312
1313
1315 The SedRecType object is composed of the following elements:
1317 o base: All first class objects extend BasicObjType (see
1318 Section 5.1).
1320 o sedName: The character string that contains the name of the SED
1321 Record. It uniquely identifies this object within the context
1322 of the Registrant ID (a child element of the base element as
1323 described above).
1325 o sedFunction: As described in [RFC6461], SED or Session
1326 Establishment Data falls primarily into one of two categories or
1327 functions, LUF and LRF. To remove any ambiguity as to the
1328 function a SED record is intended to provide, this optional
1329 element allows the provisioning party to make his or her
1330 intentions explicit.
1332 o isInSvc: A boolean element that defines whether this SED Record
1333 is in service or not. The session establishment information
1334 contained in a SED Record which is in service is a candidate for
1335 inclusion in resolution responses for Telephone Numbers that are
1336 either directly associated to this SED Record, or for Public
1337 Identities residing in a Destination Group that is associated to
1338 a SED Group which in turn has an association to this SED Record.
1340 o ttl: Number of seconds that an addressing server may cache a
1341 particular SED Record.
1343 As described above, SED records are based on an abstract type:
1344 SedRecType. The concrete types that use SedRecType as an extension
1345 base are NAPTRType, NSType, and URIType. The definitions of these
1346 types are included below. The NAPTRType object is comprised of the
1347 data elements necessary for a NAPTR (see [RFC3403]that contains
1348 routing information for a SED Group. The NSType object is comprised
1349 of the data elements necessary for a DNS name server that points to
1350 another DNS server that contains the desired routing information.
1351 The NSType is relevant only when the resolution protocol is ENUM (see
1352 [RFC3761]). The URIType object is comprised of the data elements
1353 necessary to house a URI.
1355 The data provisioned in a Registry can be leveraged for many purposes
1356 and queried using various protocols including SIP, ENUM and others.
1357 As such, the resolution data represented by the Sed records must be
1358 in a form suitable for transport using one of these protocols. In
1359 the NPATRType for example, if the URI is associated with a
1360 destination group, the user part of the replacement string that
1361 may require the Public Identifier cannot be preset. As a SIP
1362 Redirect, the resolution server will apply pattern on the input
1363 Public Identifier in the query and process the replacement string by
1364 substituting any back reference(s) in the to arrive at the
1365 final URI that is returned in the SIP Contact header. For an ENUM
1366 query, the resolution server will simply return the values of the
1367 and members of the URI.
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1384
1385
1386
1387
1388
1389
1391
1392
1393
1394
1395
1397
1398
1399
1400
1401
1402
1403
1405
1406
1407
1408
1409
1410
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1424
1425
1426
1427
1428
1429
1431 The NAPTRType object is composed of the following elements:
1433 o order: Order value in an ENUM NAPTR, relative to other NAPTRType
1434 objects in the same SED Group.
1436 o svcs: ENUM service(s) that are served by the SBE. This field's
1437 value must be of the form specified in [RFC6116] (e.g., E2U+
1438 pstn:sip+sip). The allowable values are a matter of policy and
1439 not limited by this protocol.
1441 o regx: NAPTR's regular expression field. If this is not included
1442 then the Repl field must be included.
1444 o repl: NAPTR replacement field, should only be provided if the
1445 Regex field is not provided, otherwise the server will ignore it
1447 o ext: Point of extensibility described in Section 3.3.
1449 The NSType object is composed of the following elements:
1451 o hostName: Root-relative host name of the name server.
1453 o ipAddr: Zero or more objects of type IpAddrType. Each object
1454 holds an IP Address and the IP Address type, IPv4 or IP v6.
1456 o ext: Point of extensibility described in Section 3.3.
1458 The URIType object is composed of the following elements:
1460 o ere: The POSIX Extended Regular Expression (ere) as defined in
1461 [RFC3986].
1463 o uri: the URI as defined in [RFC3986]. In some cases, this will
1464 serve as the replacement string and it will be left to the
1465 resolution server to arrive at the final usable URI.
1467 6.5. SED Group Offer
1469 The list of peer organizations whose resolution responses can include
1470 the session establishment information contained in a given SED Group
1471 is controlled by the organization to which a SED Group object belongs
1472 (its Registrant), and the peer organization that submits resolution
1473 requests (a data recipient, also know as a peering organization).
1474 The Registrant offers access to a SED Group by submitting a SED Group
1475 Offer. The data recipient can then accept or reject that offer. Not
1476 until access to a SED Group has been offered and accepted will the
1477 data recipient's organization ID be included in the peeringOrg list
1478 in a SED Group object, and that SED Group's peering information
1479 become a candidate for inclusion in the responses to the resolution
1480 requests submitted by that data recipient. The transport protocol
1481 MUST support the ability to Create, Modify, Get, Delete, Accept and
1482 Reject SED Group Offers (refer the "Framework Operations" section of
1483 this document for a generic description of various operations).
1485 A SED Group Offer object MUST be uniquely identified by attributes as
1486 defined in the description of "SedGrpOfferKeyType" in the section
1487 "Derived Object Key Types" of this document.
1489 The SedGrpOfferType object structure is defined as follows:
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1505
1506
1507
1508 -- Generic type that represents the key for a SED group offer. Must
1509 be defined in concrete form in the transport specificaiton. --
1510
1511
1512
1514
1515
1516
1517
1518
1519
1521 The SedGrpOfferType object is composed of the following elements:
1523 o base: All first class objects extend BasicObjType (see
1524 Section 5.1).
1526 o sedGrpOfferKey: The object that identifies the SED that is or
1527 has been offered and the organization that it is or has been
1528 offered to.
1530 o status: The status of the offer, offered or accepted. The
1531 server controls the status. It is automatically set to
1532 "offered" when ever a new SED Group Offer is added, and is
1533 automatically set to "accepted" if and when that offer is
1534 accepted. The value of the element is ignored when passed in by
1535 the client.
1537 o offerDateTime: Date and time in UTC when the SED Group Offer was
1538 added.
1540 o acceptDateTime: Date and time in UTC when the SED Group Offer
1541 was accepted.
1543 6.6. Egress Route
1545 In a high-availability environment, the originating SSP likely has
1546 more than one egress path to the ingress SBE of the target SSP. If
1547 the originating SSP wants to exercise greater control and choose a
1548 specific egress SBE to be associated to the target ingress SBE, it
1549 can do so using the EgrRteType object.
1551 An Egress Route object MUST be uniquely identified by attributes as
1552 defined in the description of "ObjKeyType" in the section "Generic
1553 Object Key Type" of this document.
1555 Lets assume that the target SSP has offered as part of his session
1556 establishment data, to share one or more ingress routes and that the
1557 originating SSP has accepted the offer. In order to add the egress
1558 route to the Registry, the originating SSP uses a valid regular
1559 expression to rewrite ingress route in order to include the egress
1560 SBE information. Also, more than one egress route can be associated
1561 with a given ingress route in support of fault-tolerant
1562 configurations. The supporting SPPF structure provides a way to
1563 include route precedence information to help manage traffic to more
1564 than one outbound egress SBE.
1566 The transport protocol MUST support the ability to Add, Modify, Get,
1567 and Delete Egress Routes (refer the "Framework Operations" section of
1568 this document for a generic description of various operations). The
1569 EgrRteType object structure is defined as follows:
1571
1572
1573
1574
1575
1576
1577
1578
1580
1581
1582
1583
1584
1585
1586 The EgrRteType object is composed of the following elements:
1588 o base: All first class objects extend BasicObjType (see
1589 Section 5.1).
1591 o egrRteName: The name of the egress route.
1593 o pref: The preference of this egress route relative to other
1594 egress routes that may get selected when responding to a
1595 resolution request.
1597 o regxRewriteRule: The regular expression re-write rule that
1598 should be applied to the regular expression of the ingress
1599 NAPTR(s) that belong to the ingress route.
1601 o ingrSedGrp: The ingress SED group that the egress route should
1602 be used for.
1604 o svcs: ENUM service(s) that are served by an Egress Route. This
1605 element is used to identify the ingress NAPTRs associated with
1606 the SED Group to which an Egress Route's regxRewriteRule should
1607 be applied. If no ENUM service(s) are associated with an Egress
1608 Route, then the Egress Route's regxRewriteRule should be applied
1609 to all the NAPTRs associated with the SED Group. This field's
1610 value must be of the form specified in [RFC6116] (e.g., E2U+
1611 pstn:sip+sip). The allowable values are a matter of policy and
1612 not limited by this protocol.
1614 o ext: Point of extensibility described in Section 3.3.
1616 7. Framework Operations
1618 7.1. Add Operation
1620 Any conforming transport protocol specification MUST provide a
1621 definition for the operation that adds one or more SPPF objects into
1622 the Registry. If the object, as identified by the request attributes
1623 that form part of the object's key, does not exist, then the Registry
1624 MUST create the object. If the object does exist, then the Registry
1625 MUST replace the current properties of the object with the properties
1626 passed in as part of the Add operation.
1628 If the entity that issued the command is not authorized to perform
1629 this operation an appropriate error message MUST be returned from
1630 amongst the response messages defined in "Response Message Types"
1631 section of the document.
1633 7.2. Delete Operation
1635 Any conforming transport protocol specification MUST provide a
1636 definition for the operation that deletes one or more SPPF objects
1637 from the Registry using the object's key.
1639 If the entity that issued the command is not authorized to perform
1640 this operation an appropriate error message MUST be returned from
1641 amongst the response messages defined in "Response Message Types"
1642 section of the document.
1644 When an object is deleted, any references to that object must of
1645 course also be removed as the SPPF server implementation fulfills the
1646 deletion request. Furthermore, the deletion of a composite object
1647 must also result in the deletion of the objects it contains. As a
1648 result, the following rules apply to the deletion of SPPF object
1649 types:
1651 o Destination Groups: When a destination group is deleted all
1652 public identifiers within that destination group must also be
1653 automatically deleted by the SPPF implementation as part of
1654 fulfilling the deletion request. And any references between
1655 that destination group and any SED group must be automatically
1656 removed by the SPPF implementation as part of fulfilling the
1657 deletion request.
1659 o SED Groups: When a SED group is deleted any references between
1660 that SED group and any destination group must be automatically
1661 removed by the SPPF implementation as part of fulfilling the
1662 deletion request. Similarly any references between that SED
1663 group and any SED records must be removed by the SPPF
1664 implementation as part of fulfilling the deletion request.
1665 Furthermore, SED group offers relating that SED group must also
1666 be deleted as part of fulfilling the deletion request.
1668 o SED Records: When a SED record is deleted any references between
1669 that SED record and any SED group must be removed by the SPPF
1670 implementation as part of fulfilling the deletion request.
1672 o Public Identifiers: When a public identifier is deleted any
1673 references between that public identifier and its containing
1674 destination group must be removed by the SPPF implementation as
1675 part of fulfilling the deletion request. Any SED records
1676 contained directly within that Public Identifier must be deleted
1677 by the SPPF implementation as part of fulfilling the deletion
1678 request.
1680 7.3. Get Operations
1682 At times, on behalf of the Registrant, the Registrar may need to get
1683 information about SPPF objects that were previously provisioned in
1684 the Registry. A few examples include logging, auditing, and pre-
1685 provisioning dependency checking. This query mechanism is limited to
1686 aid provisioning scenarios and should not be confused with query
1687 protocols provided as part of the resolution system (e.g. ENUM and
1688 SIP).
1690 Any conforming "protocol" specification MUST provide a definition for
1691 the operation that queries the details of one or more SPPF objects
1692 from the Registry using the object's key. If the entity that issued
1693 the command is not authorized to perform this operation an
1694 appropriate error message MUST be returned from amongst the response
1695 messages defined in Section 5.3.
1697 If the response to the Get operation includes object(s) that extend
1698 the BasicObjType, the Registry MUST include the 'cDate' and 'mDate',
1699 if applicable.
1701 7.4. Accept Operations
1703 In SPPF, a SED Group Offer can be accepted or rejected by, or on
1704 behalf of, the Registrant to whom the SED Group has been offered
1705 (refer "Framework Data Model Objects" section of this document for a
1706 description of the SED Group Offer object). The Accept operation is
1707 used to accept the SED Group Offers. Any conforming transport
1708 protocol specification MUST provide a definition for the operation to
1709 accept SED Group Offers by, or on behalf of the Registrant, using the
1710 SED Group Offer object key.
1712 Not until access to a SED Group has been offered and accepted will
1713 the Registrant's organization ID be included in the peeringOrg list
1714 in that SED Group object, and that SED Group's peering information
1715 become a candidate for inclusion in the responses to the resolution
1716 requests submitted by that Registrant. A SED Group Offer that is in
1717 the "offered" status is accepted by, or on behalf of, the Registrant
1718 to which it has been offered. When the SED Group Offer is accepted
1719 the the SED Group Offer is moved to the "accepted" status and adds
1720 that data recipient's organization ID into the list of peerOrgIds for
1721 that SED Group.
1723 If the entity that issued the command is not authorized to perform
1724 this operation an appropriate error message MUST be returned from
1725 amongst the response messages defined in "Response Message Types"
1726 section of the document.
1728 7.5. Reject Operations
1730 In SPPF, a SED Group Offer object can be accepted or rejected by, or
1731 on behalf of, the Registrant to whom the SED Group has been offered
1732 (refer "Framework Data Model Objects" section of this document for a
1733 description of the SED Group Offer object). Furthermore, that offer
1734 may be rejected, regardless of whether or not it has been previously
1735 accepted. The Reject operation is used to reject the SED Group
1736 Offers. When the SED Group Offer is rejected that SED Group Offer is
1737 deleted, and, if appropriate, the data recipient's organization ID is
1738 removed from the list of peeringOrg IDs for that SED Group. Any
1739 conforming transport protocol specification MUST provide a definition
1740 for the operation to reject SED Group Offers by, or on behalf of the
1741 Registrant, using the SED Group Offer object key.
1743 If the entity that issued the command is not authorized to perform
1744 this operation an appropriate error message MUST be returned from
1745 amongst the response messages defined in "Response Message Types"
1746 section of the document.
1748 7.6. Get Server Details Operation
1750 In SPPF, Get Server Details operation can be used to request certain
1751 details about the SPPF server that include the SPPF server's current
1752 status, the major/minor version of the SPPF protocol supported by the
1753 SPPF server.
1755 Any conforming transport protocol specification MUST provide a
1756 definition for the operation to request such details from the SPPF
1757 server. If the entity that issued the command is not authorized to
1758 perform this operation an appropriate error message MUST be returned
1759 from amongst the response messages defined in "Response Message
1760 Types" section of the document.
1762 8. XML Considerations
1764 XML serves as the encoding format for SPPF, allowing complex
1765 hierarchical data to be expressed in a text format that can be read,
1766 saved, and manipulated with both traditional text tools and tools
1767 specific to XML.
1769 XML is case sensitive. Unless stated otherwise, XML specifications
1770 and examples provided in this document MUST be interpreted in the
1771 character case presented to develop a conforming implementation.
1773 This section discusses a small number of XML-related considerations
1774 pertaining to SPPF.
1776 8.1. Namespaces
1778 All SPPF elements are defined in the namespaces in the IANA
1779 Considerations section and in the Formal Framework Specification
1780 section of this document.
1782 8.2. Versioning and Character Encoding
1784 All XML instances SHOULD begin with an declaration to
1785 identify the version of XML that is being used, optionally identify
1786 use of the character encoding used, and optionally provide a hint to
1787 an XML parser that an external schema file is needed to validate the
1788 XML instance.
1790 Conformant XML parsers recognize both UTF-8 (defined in [RFC3629])
1791 and UTF-16 (defined in [RFC2781]); per [RFC2277] UTF-8 is the
1792 RECOMMENDED character encoding for use with SPPF.
1794 Character encodings other than UTF-8 and UTF-16 are allowed by XML.
1795 UTF-8 is the default encoding assumed by XML in the absence of an
1796 "encoding" attribute or a byte order mark (BOM); thus, the "encoding"
1797 attribute in the XML declaration is OPTIONAL if UTF-8 encoding is
1798 used. SPPF clients and servers MUST accept a UTF-8 BOM if present,
1799 though emitting a UTF-8 BOM is NOT RECOMMENDED.
1801 Example XML declarations:
1803
1805 9. Security Considerations
1807 Many SPPF implementations manage data that is considered confidential
1808 and critical. Furthermore, SPPF implementations can support
1809 provisioning activities for multiple Registrars and Registrants. As
1810 a result any SPPF implementation must address the requirements for
1811 confidentiality, authentication, and authorization.
1813 9.1. Confidentiality and Authentication
1815 With respect to confidentiality and authentication, the transport
1816 protocol requirements section of this document contains security
1817 properties that the transport protocol must provide so that
1818 authenticated endpoints can exchange data confidentially and with
1819 integrity protection. Refer to that section and the resulting
1820 transport protocol specification document for the specific solutions
1821 to authentication and confidentiality.
1823 9.2. Authorization
1825 With respect to authorization, the SPPF server implementation must
1826 define and implement a set of authorization rules that precisely
1827 address (1) which Registrars will be authorized to create/modify/
1828 delete each SPPF object type for given Registrant(s) and (2) which
1829 Registrars will be authorized to view/get each SPPF object type for
1830 given Registrant(s). These authorization rules are a matter of
1831 policy and are not specified within the context of SPPF. However,
1832 any SPPF implementation must specify these authorization rules in
1833 order to function in a reliable and safe manner.
1835 9.3. Denial of Service
1837 Guidance on Denial-of-Service (DoS) issues in general is given in
1838 [RFC4732], "Internet Denial of Service Considerations", which also
1839 gives a general vocabulary for describing the DoS issue.
1841 SPPF is a high-level client-server protocol that can be implemented
1842 on lower-level mechanisms such as remote procedure call and web-
1843 service API protocols. As such, it inherits any Denial-of-Service
1844 issues inherent to the specific lower-level mechanism used for any
1845 implementation of SPPF. SPPF also has its own set of higher-level
1846 exposures that are likely to be independent of lower-layer mechanism
1847 choices.
1849 9.3.1. DoS Issues Inherited from Transport Mechanism
1851 SPPF implementation is in general dependent on the selection and
1852 implementation of a lower-level transport protocol and a binding
1853 between that protocol and SPPF. The archetypal SPPF implementation
1854 uses XML (http://www.w3.org/TR/xml/) representation in a SOAP
1855 (http://www.w3.org/TR/soap/) request/response framework over HTTP
1856 ([RFC2616]), and probably also uses TLS ([RFC5246]) for on-the wire
1857 data integrity and participant authentication, and might use HTTP
1858 Digest authentication ([RFC2609]).
1860 The typical deployment scenario for SPPF is to have servers in a
1861 managed facility, and therefore techniques such as Network Ingress
1862 Filtering ([RFC2609]) are generally applicable. In short, any DoS
1863 mechanism affecting a typical HTTP implementation would affect such
1864 an SPPF implementation, and the mitigation tools for HTTP in general
1865 also therefore apply to SPPF.
1867 SPPF does not directly specify an authentication mechanism, instead
1868 relying on the lower-level transport protocol to provide for
1869 authentication. In general, authentication is an expensive
1870 operation, and one apparent attack vector is to flood an SPPF server
1871 with repeated requests for authentication, thereby exhausting its
1872 resources. SPPF implementations SHOULD therefore be prepared to
1873 handle authentication floods, perhaps by noting repeated failed login
1874 requests from a given source address and blocking that source
1875 address.
1877 9.3.2. DoS Issues Specific to SPPF
1879 The primary defense mechanism against DoS within SPPF is
1880 authentication. Implementations MUST tightly control access to the
1881 SPPF service, SHOULD implement DoS and other policy control
1882 screening, and MAY employ a variety of policy violation reporting and
1883 response measures such as automatic blocking of specific users and
1884 alerting of operations personnel. In short, the primary SPPF
1885 response to DoS-like activity by a user is to block that user or
1886 subject their actions to additional review.
1888 SPPF allows a client to submit multiple-element or "batch" requests
1889 that may insert or otherwise affect a large amount of data with a
1890 single request. In the simplest case, the server progresses
1891 sequentially through each element in a batch, completing one and
1892 before starting the next. Mid-batch failures are handled by stopping
1893 the batch and rolling-back the data store to its pre-request state.
1894 This "stop and roll-back" design provides a DoS opportunity. A
1895 hostile client could repeatedly issue large batch requests with one
1896 or more failing elements, causing the server to repeatedly stop and
1897 roll-back large transactions. The suggested response is to monitor
1898 clients for such failures, and take administrative action (such as
1899 blocking the user) when an excessive number of roll-backs is
1900 reported.
1902 An additional suggested response is for an implementer to set their
1903 maximum allowable XML message size, and their maximum allowable batch
1904 size at a level that they feel protects their operational instance,
1905 given the hardware sizing they have in place and the expected load
1906 and size needs that their users expect.
1908 9.4. Information Disclosure
1910 It is not uncommon for the logging systems to document on-the-wire
1911 messages for various purposes, such as, debug, audit, and tracking.
1912 At the minimum, the various support and administration staff will
1913 have access to these logs. Also, if an unprivileged user gains
1914 access to the SPPF deployments and/or support systems, it will have
1915 access to the information that is potentially deemed confidential.
1916 To manage information disclosure concerns beyond the transport level,
1917 SPPF implementations MAY provide support for encryption at the SPPF
1918 object level.
1920 9.5. Non Repudiation
1922 In some situations, it may be required to protect against denial of
1923 involvement (see [RFC4949]) and tackle non-repudiation concerns in
1924 regards to SPPF messages. This type of protection is useful to
1925 satisfy authenticity concerns related to SPPF messages beyond the
1926 end-to-end connection integrity, confidentiality, and authentication
1927 protection that the transport layer provides. This is an optional
1928 feature and some SPPF implementations MAY provide support for it.
1930 9.6. Replay Attacks
1932 Anti-replay protection ensures that a given SPPF object replayed at a
1933 later time doesn't affect the integrity of the system. SPPF provides
1934 at least one mechanism to fight against replay attacks. Use of the
1935 optional client transaction identifier allows the SPPF client to
1936 correlate the request message with the response and to be sure that
1937 it is not a replay of a server response from earlier exchanges. Use
1938 of unique values for the client transaction identifier is highly
1939 encouraged to avoid chance matches to a potential replay message.
1941 9.7. Man in the Middle
1943 The SPPF client or Registrar can be a separate entity acting on
1944 behalf of the Registrant in facilitating provisioning transactions to
1945 the Registry. Further, the transport layer provides end-to-end
1946 connection protection between SPPF client and the SPPF server.
1947 Therefore, man-in-the-middle attack is a possibility that may affect
1948 the integrity of the data that belongs to the Registrant and/or
1949 expose peer data to unintended actors in case well-established
1950 peering relationships already exist.
1952 10. Internationalization Considerations
1954 Character encodings to be used for SPPF elements are described in
1955 Section 8.2. The use of time elements in the protocol is specified
1956 in Section 3.2. Where human-readable languages are used in the
1957 protocol, those messages SHOULD be tagged according to [RFC5646], and
1958 the transport protocol MUST support a respective mechanism to
1959 transmit such tags together with those human-readable messages. If
1960 tags are absent, the language of the message defaults to "en"
1961 (English).
1963 11. IANA Considerations
1965 This document uses URNs to describe XML namespaces and XML schemas
1966 conforming to a Registry mechanism described in [RFC3688].
1968 Two URI assignments are requested.
1970 Registration request for the SPPF XML namespace:
1971 urn:ietf:params:xml:ns:sppf:base:1
1972 Registrant Contact: IESG
1973 XML: None. Namespace URIs do not represent an XML specification.
1975 Registration request for the XML schema:
1976 URI: urn:ietf:params:xml:schema:sppf:1
1977 Registrant Contact: IESG
1978 XML: See the "Formal Specification" section of this document
1979 (Section 12).
1981 IANA is requested to create a new SPPF Registry for Organization
1982 Identifiers that will indicate valid strings to be used for well-
1983 known enterprise namespaces.
1984 This document makes the following assignments for the OrgIdType
1985 namespaces:
1987 Namespace OrgIdType namespace string
1988 ---- ----------------------------
1989 IANA Enterprise Numbers iana-en
1991 12. Formal Specification
1993 This section provides the draft XML Schema Definition for SPPF
1994 Protocol.
1996
1997
2001
2002
2003 ---- Generic Object key types to be defined by specific
2004 Transport/Architecture. The types defined here can
2005 be extended by the specific architecture to
2006 define the Object Identifiers ----
2007
2008
2009
2011
2012
2013 ---- Generic type that represents the
2014 key for various objects in SPPF. ----
2015
2016
2017
2019
2020
2021
2022
2023
2024 ---- Generic type that represents
2025 the key for a SED group offer. ----
2026
2027
2028
2029
2030
2032
2033
2034
2035
2036
2037 ----Generic type that
2038 represents the key
2039 for a Pub Id. ----
2040
2041
2042
2043
2044
2046
2047
2048 ---- Object Type Definitions ----
2049
2050
2052
2053
2054
2055
2056
2057
2059
2061
2063
2065
2066
2067
2069
2070
2071
2072
2073
2074
2075
2076
2077
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2178
2179
2180
2181
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2217
2218
2219
2220
2221
2222
2223
2224
2225 ---- Abstract Object and Element Type Definitions ----
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2392 13. Acknowledgments
2394 This document is a result of various discussions held in the DRINKS
2395 working group and within the DRINKS protocol design team, with
2396 contributions from the following individuals, in alphabetical order:
2397 Alexander Mayrhofer, David Schwartz, Deborah A Guyton, Lisa
2398 Dusseault, Manjul Maharishi, Mickael Marrache, Otmar Lendl, Richard
2399 Shockey, Samuel Melloul, Sumanth Channabasappa, Syed Ali, Vikas
2400 Bhatia, and Jeremy Barkan
2402 14. References
2404 14.1. Normative References
2406 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
2407 Requirement Levels", BCP 14, RFC 2119, March 1997.
2409 [RFC2277] Alvestrand, H., "IETF Policy on Character Sets and
2410 Languages", BCP 18, RFC 2277, January 1998.
2412 [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
2413 10646", STD 63, RFC 3629, November 2003.
2415 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
2416 January 2004.
2418 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
2419 Resource Identifier (URI): Generic Syntax", STD 66,
2420 RFC 3986, January 2005.
2422 [RFC4949] Shirey, R., "Internet Security Glossary, Version 2",
2423 RFC 4949, August 2007.
2425 [RFC5067] Lind, S. and P. Pfautz, "Infrastructure ENUM
2426 Requirements", RFC 5067, November 2007.
2428 14.2. Informative References
2430 [RFC2609] Guttman, E., Perkins, C., and J. Kempf, "Service Templates
2431 and Service: Schemes", RFC 2609, June 1999.
2433 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
2434 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
2435 Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
2437 [RFC2781] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO
2438 10646", RFC 2781, February 2000.
2440 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
2441 A., Peterson, J., Sparks, R., Handley, M., and E.
2442 Schooler, "SIP: Session Initiation Protocol", RFC 3261,
2443 June 2002.
2445 [RFC3403] Mealling, M., "Dynamic Delegation Discovery System (DDDS)
2446 Part Three: The Domain Name System (DNS) Database",
2447 RFC 3403, October 2002.
2449 [RFC3761] Faltstrom, P. and M. Mealling, "The E.164 to Uniform
2450 Resource Identifiers (URI) Dynamic Delegation Discovery
2451 System (DDDS) Application (ENUM)", RFC 3761, April 2004.
2453 [RFC4725] Mayrhofer, A. and B. Hoeneisen, "ENUM Validation
2454 Architecture", RFC 4725, November 2006.
2456 [RFC4732] Handley, M., Rescorla, E., and IAB, "Internet Denial-of-
2457 Service Considerations", RFC 4732, December 2006.
2459 [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
2460 (TLS) Protocol Version 1.2", RFC 5246, August 2008.
2462 [RFC5321] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321,
2463 October 2008.
2465 [RFC5486] Malas, D. and D. Meyer, "Session Peering for Multimedia
2466 Interconnect (SPEERMINT) Terminology", RFC 5486,
2467 March 2009.
2469 [RFC5646] Phillips, A. and M. Davis, "Tags for Identifying
2470 Languages", BCP 47, RFC 5646, September 2009.
2472 [RFC6116] Bradner, S., Conroy, L., and K. Fujiwara, "The E.164 to
2473 Uniform Resource Identifiers (URI) Dynamic Delegation
2474 Discovery System (DDDS) Application (ENUM)", RFC 6116,
2475 March 2011.
2477 [RFC6461] Channabasappa, S., "Data for Reachability of Inter-/
2478 Intra-NetworK SIP (DRINKS) Use Cases and Protocol
2479 Requirements", RFC 6461, January 2012.
2481 [Unicode6.1]
2482 The Unicode Consortium, "The Unicode Standard - Version
2483 6.1", Unicode 6.1, January 2012.
2485 Authors' Addresses
2487 Kenneth Cartwright
2488 TNS
2489 1939 Roland Clarke Place
2490 Reston, VA 20191
2491 USA
2493 Email: kcartwright@tnsi.com
2495 Vikas Bhatia
2496 TNS
2497 1939 Roland Clarke Place
2498 Reston, VA 20191
2499 USA
2501 Email: vbhatia@tnsi.com
2503 Syed Wasim Ali
2504 NeuStar
2505 46000 Center Oak Plaza
2506 Sterling, VA 20166
2507 USA
2509 Email: syed.ali@neustar.biz
2511 David Schwartz
2512 XConnect
2513 316 Regents Park Road
2514 London, N3 2XJ
2515 United Kingdom
2517 Email: dschwartz@xconnect.net