Debian Codegraph @

rfc5278.html

raw
1 <pre>Network Working Group J. Livingood
2 Request for Comments: 5278 Comcast Cable Communications
3 Category: Standards Track D. Troshynski
4 Acme Packet
5 July 2008
6
7
8 <span class="h1">IANA Registration of Enumservices for Voice and Video Messaging</span>
9
10 Status of This Memo
11
12 This document specifies an Internet standards track protocol for the
13 Internet community, and requests discussion and suggestions for
14 improvements. Please refer to the current edition of the "Internet
15 Official Protocol Standards" (STD 1) for the standardization state
16 and status of this protocol. Distribution of this memo is unlimited.
17
18 Abstract
19
20 This document registers the Enumservice named "vmsg", which is used
21 to facilitate the real-time routing of voice, video, and unified
22 communications to a messaging system. This vmsg Enumservice
23 registers three Enumservice types: "voicemsg", "videomsg", and
24 "unifmsg". Each type also registers the subtypes "sip", "sips",
25 "http", and "https", as well as the subtype "tel" for the "voicemsg"
26 type.
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Livingood &amp; Troshynski Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc5278">RFC 5278</a> VMSG Enumservice July 2008</span>
55
56
57 Table of Contents
58
59 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a>
60 <a href="#section-1.1">1.1</a>. Selected Use Cases for Illustrative Purposes ...............<a href="#page-4">4</a>
61 <a href="#section-1.2">1.2</a>. Consideration of Other Existing Enumservices ...............<a href="#page-5">5</a>
62 <a href="#section-2">2</a>. Distribution of Data ............................................<a href="#page-5">5</a>
63 <a href="#section-3">3</a>. Security Considerations .........................................<a href="#page-5">5</a>
64 <a href="#section-4">4</a>. ENUM Service Registration for voicemsg ..........................<a href="#page-6">6</a>
65 <a href="#section-4.1">4.1</a>. Registration for "voicemsg" with Subtype "sip" .............<a href="#page-6">6</a>
66 <a href="#section-4.2">4.2</a>. Registration for "voicemsg" with Subtype "sips" ............<a href="#page-7">7</a>
67 <a href="#section-4.3">4.3</a>. Registration for "voicemsg" with Subtype "tel" .............<a href="#page-7">7</a>
68 <a href="#section-4.4">4.4</a>. Registration for "voicemsg" with Subtype "http" ............<a href="#page-8">8</a>
69 <a href="#section-4.5">4.5</a>. Registration for "voicemsg" with Subtype "https" ...........<a href="#page-9">9</a>
70 <a href="#section-5">5</a>. ENUM Service Registration for videomsg .........................<a href="#page-10">10</a>
71 <a href="#section-5.1">5.1</a>. Registration for "videomsg" with Subtype "sip" ............<a href="#page-10">10</a>
72 <a href="#section-5.2">5.2</a>. Registration for "videomsg" with Subtype "sips" ...........<a href="#page-10">10</a>
73 <a href="#section-5.3">5.3</a>. Registration for "videomsg" with Subtype "http" ...........<a href="#page-11">11</a>
74 <a href="#section-5.4">5.4</a>. Registration for "videomsg" with Subtype "https" ..........<a href="#page-12">12</a>
75 <a href="#section-6">6</a>. ENUM Service Registration for unifmsg ..........................<a href="#page-13">13</a>
76 <a href="#section-6.1">6.1</a>. Registration for "unifmsg" with Subtype "sip" .............<a href="#page-13">13</a>
77 <a href="#section-6.2">6.2</a>. Registration for "unifmsg" with Subtype "sips" ............<a href="#page-13">13</a>
78 <a href="#section-6.3">6.3</a>. Registration for "unifmsg" with Subtype "http" ............<a href="#page-14">14</a>
79 <a href="#section-6.4">6.4</a>. Registration for "unifmsg" with Subtype "https" ...........<a href="#page-15">15</a>
80 <a href="#section-7">7</a>. Selected Examples for Illustrative Purposes ....................<a href="#page-16">16</a>
81 <a href="#section-7.1">7.1</a>. Example Using a 'sip' URI .................................<a href="#page-16">16</a>
82 <a href="#section-7.2">7.2</a>. Example Using a 'tel' URI .................................<a href="#page-16">16</a>
83 <a href="#section-7.3">7.3</a>. Example Using a Backreference .............................<a href="#page-16">16</a>
84 <a href="#section-7.4">7.4</a>. Example Using a 'sip' URI without a Telephone Number ......<a href="#page-17">17</a>
85 <a href="#section-7.5">7.5</a>. Example of Failover Using E2U+videomsg:sip ................<a href="#page-17">17</a>
86 <a href="#section-8">8</a>. Implementation Recommendations .................................<a href="#page-17">17</a>
87 <a href="#section-8.1">8.1</a>. Call Processing When Multiple Records Are Returned ........<a href="#page-17">17</a>
88 <a href="#section-8.2">8.2</a>. NAPTR Configuration Issues ................................<a href="#page-18">18</a>
89 <a href="#section-9">9</a>. IANA Considerations ............................................<a href="#page-18">18</a>
90 <a href="#section-10">10</a>. Acknowledgements ..............................................<a href="#page-18">18</a>
91 <a href="#section-11">11</a>. Contributors ..................................................<a href="#page-19">19</a>
92 <a href="#section-12">12</a>. References ....................................................<a href="#page-19">19</a>
93 <a href="#section-12.1">12.1</a>. Normative References .....................................<a href="#page-19">19</a>
94 <a href="#section-12.2">12.2</a>. Informative References ...................................<a href="#page-20">20</a>
95
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Livingood &amp; Troshynski Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc5278">RFC 5278</a> VMSG Enumservice July 2008</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
114
115 ENUM (E.164 Number Mapping, <a href="./rfc3761">RFC 3761</a> [<a href="#ref-1" title="&quot;The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)&quot;">1</a>]) is a technology that
116 transforms E.164 numbers (the International Public Telecommunication
117 Numbering Plan, ITU-T Recommendation E.164 [<a href="#ref-2" title="&quot;The International Public Telecommunication Numbering Plan&quot;">2</a>]) into domain names and
118 then uses DNS (Domain Name System, <a href="./rfc1034">RFC 1034</a> [<a href="#ref-3" title="&quot;Domain names - concepts and facilities&quot;">3</a>]) delegation through
119 NS records and Naming Authority Pointer (NAPTR) records (Dynamic
120 Delegation Discovery System (DDDS) Part Three: The Domain Name System
121 (DNS) Database, <a href="./rfc3403">RFC 3403</a> [<a href="#ref-4" title="&quot;Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database&quot;">4</a>]) to look up what services are available
122 for a specific domain name.
123
124 This document registers Enumservices according to the guidelines
125 given in <a href="./rfc3761">RFC 3761</a> [<a href="#ref-1" title="&quot;The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)&quot;">1</a>] to be used for provisioning in the services
126 field of a NAPTR [<a href="#ref-4" title="&quot;Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database&quot;">4</a>] resource record to indicate the types of
127 functionality associated with an end point and/or telephone number.
128 The registration is defined within the DDDS (Dynamic Delegation
129 Discovery System [<a href="#ref-4" title="&quot;Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database&quot;">4</a>][5][<a href="#ref-6" title="&quot;Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm&quot;">6</a>][7][<a href="#ref-8" title="&quot;Dynamic Delegation Discovery System (DDDS) Part Five: URI.ARPA Assignment Procedures&quot;">8</a>]) hierarchy, for use with the "E2U"
130 DDDS Application defined in <a href="./rfc3761">RFC 3761</a>.
131
132 Voice messaging systems are used widely with telephony and voice
133 communication services. The need for a voice messaging service type
134 has become clear in order to provide certain applications with direct
135 access to various voice messaging services (for example, voicemail),
136 most typically via the use of SIP.
137
138 The authors considered the use of Voice Profile for Internet Mail
139 (VPIM) [<a href="#ref-14" title="&quot;Voice Message Routing Service&quot;">14</a>] but found that VPIM was best suited to the non-real-time
140 and non-session-based routing of a voice message once it had been
141 deposited into a voice messaging system. Thus, VPIM was a good
142 solution for the non-real-time and non-session-based routing of voice
143 messages between and within domains, but it did not enable real-time
144 interaction with a voice messaging system.
145
146 Thus, a need has been identified for this voice messaging service
147 type that would enable, for example, some of the use cases listed in
148 this section.
149
150 Video messaging systems, sometimes called visual voice messaging
151 systems, are beginning to be used with real-time communication
152 services. The need for a video messaging service type has become
153 clear in order to provide certain applications with direct access to
154 various video messaging services, most typically via the use of SIP.
155 Thus, a need has been identified for this video messaging service
156 type that would enable, for example, some of the use cases listed in
157 this section.
158
159
160
161
162
163
164 <span class="grey">Livingood &amp; Troshynski Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc5278">RFC 5278</a> VMSG Enumservice July 2008</span>
167
168
169 Finally, several service providers and software developers have
170 indicated that their system for voice messaging and video messaging
171 either have been or soon will be unified into a single system. As
172 such, they desired to have the option of using an Enumservice type
173 that represents a subscriber's mailbox as being a so-called unified
174 messaging repository. Thus, a need has been identified for this
175 unified voice and video messaging service type that would enable, for
176 example, some of the use cases listed in this section.
177
178 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Selected Use Cases for Illustrative Purposes</span>
179
180 The following is a partial, non-exclusive list of use cases that the
181 vmsg Enumservice could address:
182
183 * A called party is busy or does not answer a call. A client or
184 server then determines that a messaging service should be used and
185 sends the calling party's session to such a service. The client or
186 server needs to be able to determine which server to direct this
187 real-time session to, whether that is within or outside of the
188 called party's domain.
189
190 * Similar to the above use case, a real-time session is attempted to
191 a messaging system, but that system is currently unavailable.
192 Since multiple service type records may be returned by the original
193 ENUM query, the client or server could then attempt to initiate a
194 session with one or more backup messaging servers in a manner that
195 is transparent to the calling party and that supports better
196 overall availability of a messaging service.
197
198 * Similar to the above use case, this service type could be used to
199 balance load across multiple messaging servers, whether those are
200 in the same or in different physical locations.
201
202 * A user with an account on a messaging service needs to connect to
203 the messaging service in order to retrieve messages. They initiate
204 a real-time session, and an ENUM query is performed to discover the
205 messaging server that holds its mailbox.
206
207 * In the process of invoking and supporting a real-time, automated
208 and interactive session with a user, whether for message deposit or
209 retrieval, VoiceXML files are referenced and utilized, via either
210 HTTP or HTTPS. Multiple VoiceXML servers could be associated with
211 a user and returned via ENUM query, for the purposes of load
212 balancing, for example.
213
214
215
216
217
218
219
220 <span class="grey">Livingood &amp; Troshynski Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc5278">RFC 5278</a> VMSG Enumservice July 2008</span>
223
224
225 <span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Consideration of Other Existing Enumservices</span>
226
227 The authors considered whether this service type could simply use the
228 SIP Enumservice type [<a href="#ref-19" title="&quot;enumservice registration for Session Initiation Protocol (SIP) Addresses-of-Record&quot;">19</a>], but found that it does not satisfy their
229 voice messaging requirements, particularly given the non-SIP URI sub-
230 types specified herein. Even with sub-types for SIP URIs, however,
231 there are challenges to using the SIP Enumservice type. For example,
232 a request for access to such a service could be extended to the
233 requesting SIP client, or User Agent Client (UAC), rather than
234 relying upon the local policy of a SIP server, or User Agent Server
235 (UAS), which means that special routing logic within a UAS cannot be
236 relied upon to solve this problem. More importantly, however, the
237 authors have found that without this service type, a UAC or UAS will
238 be presented with multiple SIP URIs, with no ability other than in
239 non-standards-based routing rules or application logic to recognize
240 which one is related to a voice messaging, video messaging, or
241 unified voice and video messaging service.
242
243 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Distribution of Data</span>
244
245 The authors believe that it is more likely that these records will be
246 distributed on a purely private basis, but they may also be
247 distributed in public ENUM trees. Distribution of this NAPTR data
248 could be either (a) on a private basis within a service provider's
249 internal network, (b) on a private basis between one or more parties
250 using a variety of security mechanisms to prohibit general public
251 access, or (c) openly available.
252
253 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security Considerations</span>
254
255 DNS, as used by ENUM, is a global, distributed database. Should
256 implementers of this specification use e164.arpa or any other
257 publicly available domain as the tree for maintaining voicemsg
258 Enumservice data, this information would be visible to anyone
259 anonymously. While this is not qualitatively different from
260 publication in a Telephone Directory, it does open or ease access to
261 such data without any indication that such data has been accessed or
262 by whom it has been accessed.
263
264 Such data harvesting by third parties is often used to generate lists
265 of targets for unsolicited information. Thus, a third party could
266 use this to generate a list that it can use to make unsolicited
267 telemarketing phone calls, or so-called SPAM over Internet Telephony
268 (SPIT). Many countries have do-not-call registries or other legal or
269 regulatory mechanisms in place to deal with such abuses.
270
271
272
273
274
275
276 <span class="grey">Livingood &amp; Troshynski Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc5278">RFC 5278</a> VMSG Enumservice July 2008</span>
279
280
281 As noted earlier, carriers, service providers, and other users may
282 simply choose not to publish such information in the public e164.arpa
283 tree, but may instead simply publish this in their internal ENUM
284 routing database that is only able to be queried by trusted elements
285 of their network and/or partner networks, such as softswitches and
286 SIP proxy servers. They may also choose to publish such information
287 in a carrier-only branch of the e164.arpa tree, should one be
288 created.
289
290 Although an E.164 telephone number does not appear to reveal as much
291 identity information about a user as a name in the format
292 sip:username@hostname or email:username@hostname, the information is
293 still publicly available; thus, there is still the risk of unwanted
294 communication.
295
296 An analysis of threats specific to the dependence of ENUM on the DNS
297 and the applicability of DNSSEC [<a href="#ref-16" title="&quot;Protocol Modifications for the DNS Security Extensions&quot;">16</a>] to this is provided in <a href="./rfc3761">RFC 3761</a>
298 [<a href="#ref-1" title="&quot;The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)&quot;">1</a>]. A thorough analysis of threats to the DNS itself is covered in
299 <a href="./rfc3833">RFC 3833</a> [<a href="#ref-17" title="&quot;Threat Analysis of the Domain Name System (DNS)&quot;">17</a>].
300
301 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. ENUM Service Registration for voicemsg</span>
302
303 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Registration for "voicemsg" with Subtype "sip"</span>
304
305 Enumservice Name: "voicemsg"
306
307 Enumservice Type: "voicemsg"
308
309 Enumservice Subtypes: "sip"
310
311 URI Schemes: 'sip:'
312
313 Functional Specification:
314
315 This Enumservice indicates that the remote resource identified can be
316 addressed by the associated URI scheme in order to initiate a voice
317 communication session to a voice messaging system.
318
319 Security Considerations: See <a href="#section-3">Section 3</a>.
320
321 Intended Usage: COMMON
322
323 Authors:
324
325 Jason Livingood ([email protected])
326 Don Troshynski ([email protected])
327
328
329
330
331
332 <span class="grey">Livingood &amp; Troshynski Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc5278">RFC 5278</a> VMSG Enumservice July 2008</span>
335
336
337 Any other information the author deems interesting:
338
339 Implementers should review a non-exclusive list of examples below in
340 <a href="#section-7">Section 7</a>.
341
342 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Registration for "voicemsg" with Subtype "sips"</span>
343
344 Enumservice Name: "voicemsg"
345
346 Enumservice Type: "voicemsg"
347
348 Enumservice Subtypes: "sips"
349
350 URI Schemes: 'sips:'
351
352 Functional Specification:
353
354 This Enumservice indicates that the remote resource identified can be
355 addressed by the associated URI scheme in order to initiate a voice
356 communication session to a voice messaging system.
357
358 Security Considerations: See <a href="#section-3">Section 3</a>.
359
360 Intended Usage: COMMON
361
362 Authors:
363
364 Jason Livingood ([email protected])
365 Don Troshynski ([email protected])
366
367 Any other information the author deems interesting:
368
369 Implementers should review a non-exclusive list of examples below in
370 <a href="#section-7">Section 7</a>.
371
372 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Registration for "voicemsg" with Subtype "tel"</span>
373
374 Enumservice Name: "voicemsg"
375
376 Enumservice Type: "voicemsg"
377
378 Enumservice Subtype: "tel"
379
380 URI Schemes: 'tel:'
381
382
383
384
385
386
387
388 <span class="grey">Livingood &amp; Troshynski Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc5278">RFC 5278</a> VMSG Enumservice July 2008</span>
391
392
393 Functional Specification:
394
395 This Enumservice indicates that the remote resource identified can be
396 addressed by the associated URI scheme in order to initiate a voice
397 communication session to a voice messaging system.
398
399 Security Considerations: See <a href="#section-3">Section 3</a>.
400
401 Intended Usage: COMMON
402
403 Authors:
404
405 Jason Livingood ([email protected])
406 Don Troshynski ([email protected])
407
408 Any other information the author deems interesting:
409
410 Implementers should review a non-exclusive list of examples below in
411 <a href="#section-7">Section 7</a>.
412
413 <span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. Registration for "voicemsg" with Subtype "http"</span>
414
415 Enumservice Name: "voicemsg"
416
417 Enumservice Type: "voicemsg"
418
419 Enumservice Subtype: "http"
420
421 URI Schemes: 'http:'
422
423 Functional Specification:
424
425 This Enumservice indicates that the remote resource identified by the
426 associated URI scheme is capable of being a source of information.
427
428 Note that the kind of information retrieved can be manifold. Usually,
429 contacting a resource by an 'http:' [<a href="#ref-11" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">11</a>] URI provides a document.
430 This document can contain references that will trigger the download
431 of many different kinds of information, such as text, audio, video,
432 executable code, or even voice message files. Thus, one cannot be
433 more specific about the kind of information expected when contacting
434 the resource.
435
436 Security Considerations: See <a href="#section-3">Section 3</a>.
437
438 Intended Usage: COMMON
439
440
441
442
443
444 <span class="grey">Livingood &amp; Troshynski Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc5278">RFC 5278</a> VMSG Enumservice July 2008</span>
447
448
449 Authors:
450
451 Jason Livingood ([email protected])
452 Don Troshynski ([email protected])
453
454 Any other information the author deems interesting:
455
456 Implementers should review a non-exclusive list of examples below in
457 <a href="#section-7">Section 7</a>.
458
459 <span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. Registration for "voicemsg" with Subtype "https"</span>
460
461 Enumservice Name: "voicemsg"
462
463 Enumservice Type: "voicemsg"
464
465 Enumservice Subtype: "https"
466
467 URI Schemes: 'https:'
468
469 Functional Specification:
470
471 This Enumservice indicates that the remote resource identified by the
472 associated URI scheme is capable of being a source of information,
473 which can be contacted using TLS or the Secure Socket Layer protocol.
474
475 Note that the kind of information retrieved can be manifold. Usually,
476 contacting a resource by an 'https:' [<a href="#ref-12" title="&quot;HTTP Over TLS&quot;">12</a>] URI provides a document.
477 This document can contain references that will trigger the download
478 of many different kinds of information, such as text, audio, video,
479 executable code, or even voice message files. Thus, one cannot be
480 more specific about the kind of information expected when contacting
481 the resource.
482
483 Security Considerations: See <a href="#section-3">Section 3</a>.
484
485 Intended Usage: COMMON
486
487 Authors:
488
489 Jason Livingood ([email protected])
490 Don Troshynski ([email protected])
491
492 Any other information the author deems interesting:
493
494 Implementers should review a non-exclusive list of examples below in
495 <a href="#section-7">Section 7</a>.
496
497
498
499
500 <span class="grey">Livingood &amp; Troshynski Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc5278">RFC 5278</a> VMSG Enumservice July 2008</span>
503
504
505 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. ENUM Service Registration for videomsg</span>
506
507 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Registration for "videomsg" with Subtype "sip"</span>
508
509 Enumservice Name: "videomsg"
510
511 Enumservice Type: "videomsg"
512
513 Enumservice Subtypes: "sip"
514
515 URI Schemes: 'sip:'
516
517 Functional Specification:
518
519 This Enumservice indicates that the remote resource identified can be
520 addressed by the associated URI scheme in order to initiate a video
521 communication session to a video messaging system.
522
523 Security Considerations: See <a href="#section-3">Section 3</a>.
524
525 Intended Usage: COMMON
526
527 Authors:
528
529 Jason Livingood ([email protected])
530 Don Troshynski ([email protected])
531
532 Any other information the author deems interesting:
533
534 Implementers should review a non-exclusive list of examples below in
535 <a href="#section-7">Section 7</a>.
536
537 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Registration for "videomsg" with Subtype "sips"</span>
538
539 Enumservice Name: "videomsg"
540
541 Enumservice Type: "videomsg"
542
543 Enumservice Subtypes: "sips"
544
545 URI Schemes: 'sips:'
546
547 Functional Specification:
548
549 This Enumservice indicates that the remote resource identified can be
550 addressed by the associated URI scheme in order to initiate a video
551 communication session to a video messaging system.
552
553
554
555
556 <span class="grey">Livingood &amp; Troshynski Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc5278">RFC 5278</a> VMSG Enumservice July 2008</span>
559
560
561 Security Considerations: See <a href="#section-3">Section 3</a>.
562
563 Intended Usage: COMMON
564
565 Authors:
566
567 Jason Livingood ([email protected])
568 Don Troshynski ([email protected])
569
570 Any other information the author deems interesting:
571
572 Implementers should review a non-exclusive list of examples below in
573 <a href="#section-7">Section 7</a>.
574
575 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Registration for "videomsg" with Subtype "http"</span>
576
577 Enumservice Name: "videomsg"
578
579 Enumservice Type: "videomsg"
580
581 Enumservice Subtype: "http"
582
583 URI Schemes: 'http:'
584
585 Functional Specification:
586
587 This Enumservice indicates that the remote resource identified by the
588 associated URI scheme is capable of being a source of information.
589
590 Note that the kind of information retrieved can be manifold. Usually,
591 contacting a resource by an 'http:' [<a href="#ref-11" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">11</a>] URI provides a document.
592 This document can contain references that will trigger the download
593 of many different kinds of information, such as text, audio, video,
594 executable code, or even video message files. Thus, one cannot be
595 more specific about the kind of information expected when contacting
596 the resource.
597
598 Security Considerations: See <a href="#section-3">Section 3</a>.
599
600 Intended Usage: COMMON
601
602 Authors:
603
604 Jason Livingood ([email protected])
605 Don Troshynski ([email protected])
606
607
608
609
610
611
612 <span class="grey">Livingood &amp; Troshynski Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc5278">RFC 5278</a> VMSG Enumservice July 2008</span>
615
616
617 Any other information the author deems interesting:
618
619 Implementers should review a non-exclusive list of examples below in
620 <a href="#section-7">Section 7</a>.
621
622 <span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. Registration for "videomsg" with Subtype "https"</span>
623
624 Enumservice Name: "videomsg"
625
626 Enumservice Type: "videomsg"
627
628 Enumservice Subtype: "https"
629
630 URI Schemes: 'https:'
631
632 Functional Specification:
633
634 This Enumservice indicates that the remote resource identified by the
635 associated URI scheme is capable of being a source of information,
636 which can be contacted using TLS or the Secure Socket Layer protocol.
637
638 Note that the kind of information retrieved can be manifold. Usually,
639 contacting a resource by an 'https:' [<a href="#ref-12" title="&quot;HTTP Over TLS&quot;">12</a>] URI provides a document.
640 This document can contain references that will trigger the download
641 of many different kinds of information, such as text, audio, video,
642 executable code, or even video message files. Thus, one cannot be
643 more specific about the kind of information expected when contacting
644 the resource.
645
646 Security Considerations: See <a href="#section-3">Section 3</a>.
647
648 Intended Usage: COMMON
649
650 Authors:
651
652 Jason Livingood ([email protected])
653 Don Troshynski ([email protected])
654
655 Any other information the author deems interesting:
656
657 Implementers should review a non-exclusive list of examples below in
658 <a href="#section-7">Section 7</a>.
659
660
661
662
663
664
665
666
667
668 <span class="grey">Livingood &amp; Troshynski Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc5278">RFC 5278</a> VMSG Enumservice July 2008</span>
671
672
673 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. ENUM Service Registration for unifmsg</span>
674
675 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Registration for "unifmsg" with Subtype "sip"</span>
676
677 Enumservice Name: "unifmsg"
678
679 Enumservice Type: "unifmsg"
680
681 Enumservice Subtypes: "sip"
682
683 URI Schemes: 'sip:'
684
685 Functional Specification:
686
687 This Enumservice indicates that the remote resource identified can be
688 addressed by the associated URI scheme in order to initiate a unified
689 communication session to a unified messaging system.
690
691 Security Considerations: See <a href="#section-3">Section 3</a>.
692
693 Intended Usage: COMMON
694
695 Authors:
696
697 Jason Livingood ([email protected])
698 Don Troshynski ([email protected])
699
700 Any other information the author deems interesting:
701
702 Implementers should review a non-exclusive list of examples below in
703 <a href="#section-7">Section 7</a>.
704
705 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Registration for "unifmsg" with Subtype "sips"</span>
706
707 Enumservice Name: "unifmsg"
708
709 Enumservice Type: "unifmsg"
710
711 Enumservice Subtypes: "sips"
712
713 URI Schemes: 'sips:'
714
715 Functional Specification:
716
717 This Enumservice indicates that the remote resource identified can be
718 addressed by the associated URI scheme in order to initiate a unified
719 communication session to a unified messaging system.
720
721
722
723
724 <span class="grey">Livingood &amp; Troshynski Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc5278">RFC 5278</a> VMSG Enumservice July 2008</span>
727
728
729 Security Considerations: See <a href="#section-3">Section 3</a>.
730
731 Intended Usage: COMMON
732
733 Authors:
734
735 Jason Livingood ([email protected])
736 Don Troshynski ([email protected])
737
738 Any other information the author deems interesting:
739
740 Implementers should review a non-exclusive list of examples below in
741 <a href="#section-7">Section 7</a>.
742
743 <span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Registration for "unifmsg" with Subtype "http"</span>
744
745 Enumservice Name: "unifmsg"
746
747 Enumservice Type: "unifmsg"
748
749 Enumservice Subtype: "http"
750
751 URI Schemes: 'http:'
752
753 Functional Specification:
754
755 This Enumservice indicates that the remote resource identified by the
756 associated URI scheme is capable of being a source of information.
757
758 Note that the kind of information retrieved can be manifold. Usually,
759 contacting a resource by an 'http:' [<a href="#ref-11" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">11</a>] URI provides a document.
760 This document can contain references that will trigger the download
761 of many different kinds of information, such as text, audio, video,
762 executable code, or even video message files. Thus, one cannot be
763 more specific about the kind of information expected when contacting
764 the resource.
765
766 Security Considerations: See <a href="#section-3">Section 3</a>.
767
768 Intended Usage: COMMON
769
770 Authors:
771
772 Jason Livingood ([email protected])
773 Don Troshynski ([email protected])
774
775
776
777
778
779
780 <span class="grey">Livingood &amp; Troshynski Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc5278">RFC 5278</a> VMSG Enumservice July 2008</span>
783
784
785 Any other information the author deems interesting:
786
787 Implementers should review a non-exclusive list of examples below in
788 <a href="#section-7">Section 7</a>.
789
790 <span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. Registration for "unifmsg" with Subtype "https"</span>
791
792 Enumservice Name: "unifmsg"
793
794 Enumservice Type: "unifmsg"
795
796 Enumservice Subtype: "https"
797
798 URI Schemes: 'https:'
799
800 Functional Specification:
801
802 This Enumservice indicates that the remote resource identified by the
803 associated URI scheme is capable of being a source of information,
804 which can be contacted using TLS or the Secure Socket Layer protocol.
805
806 Note that the kind of information retrieved can be manifold. Usually,
807 contacting a resource by an 'https:' [<a href="#ref-12" title="&quot;HTTP Over TLS&quot;">12</a>] URI provides a document.
808 This document can contain references that will trigger the download
809 of many different kinds of information, such as text, audio, video,
810 executable code, or even video message files. Thus, one cannot be
811 more specific about the kind of information expected when contacting
812 the resource.
813
814 Security Considerations: See <a href="#section-3">Section 3</a>.
815
816 Intended Usage: COMMON
817
818 Authors:
819
820 Jason Livingood ([email protected])
821 Don Troshynski ([email protected])
822
823 Any other information the author deems interesting:
824
825 Implementers should review a non-exclusive list of examples below in
826 <a href="#section-7">Section 7</a>.
827
828
829
830
831
832
833
834
835
836 <span class="grey">Livingood &amp; Troshynski Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc5278">RFC 5278</a> VMSG Enumservice July 2008</span>
839
840
841 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Selected Examples for Illustrative Purposes</span>
842
843 The following sub-sections document several examples that
844 implementers may find informative. These examples shall in no way
845 limit the various forms that this Enumservice may take.
846
847 <span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Example Using a 'sip' URI</span>
848
849 $ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa.
850 NAPTR 10 100 "u" "E2U+voicemsg:sip"
851 "!^.*$!sip:[email protected]!".
852
853 In this example, a calling party has attempted a session that has
854 gone unanswered after a certain period of time. The calling party's
855 session is sent to the appropriate voice messaging server, a
856 personalized greeting is played to the calling party, after which it
857 records a voice message to the called party.
858
859 <span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Example Using a 'tel' URI</span>
860
861 $ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa.
862 NAPTR 10 100 "u" "E2U+voicemsg:tel"
863 "!^.*$!tel:1-215-555-0123!".
864
865 In this example, a calling party has attempted a session that has
866 gone unanswered after a certain period of time. The calling party's
867 session is sent to the appropriate voice messaging server, a
868 personalized greeting is played to the calling party, after which it
869 records a voice message to the called party.
870
871 <span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a>. Example Using a Backreference</span>
872
873 $ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa.
874 NAPTR 10 100 "u" "E2U+voicemsg:sip"
875 "!(^.*)$!sip:\[email protected]!".
876
877 In this example, a backreference is used to reduce the size of the
878 NAPTR record. The sip URI uses "\1", which would dynamically replace
879 the expression with the TN, in this case +12155550123.
880
881
882
883
884
885
886
887
888
889
890
891
892 <span class="grey">Livingood &amp; Troshynski Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc5278">RFC 5278</a> VMSG Enumservice July 2008</span>
895
896
897 <span class="h3"><a class="selflink" id="section-7.4" href="#section-7.4">7.4</a>. Example Using a 'sip' URI without a Telephone Number</span>
898
899 $ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa.
900 NAPTR 10 100 "u" "E2U+voicemsg:sip"
901 "!^.*$!sip:[email protected]!".
902
903 In this example, a calling party has attempted a session that has
904 gone unanswered after a certain period of time. The calling party's
905 session is sent to the appropriate voice messaging server, a
906 personalized greeting is played to the calling party, after which it
907 records a voice message to the called party. The URI that this
908 session is directed to does not include a telephone number, as this
909 user has multiple service that are not particularly tied to telephone
910 numbers whereby text, audio, video and other multimedia messages can
911 be received and accessed.
912
913 <span class="h3"><a class="selflink" id="section-7.5" href="#section-7.5">7.5</a>. Example of Failover Using E2U+videomsg:sip</span>
914
915 $ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa.
916 NAPTR 10 100 "u" "E2U+videomsg:sip"
917 "!^.*$!sip:[email protected]!".
918
919 $ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa.
920 NAPTR 10 200 "u" "E2U+videomsg:sip"
921 "!^.*$!sip:[email protected]!".
922
923 In this example, the preference indicates that gw1.example.com is
924 used first (100), and if this is unreachable, then the next higher
925 preference (200) is used and gw2.example.com is contacted. While out
926 of scope for this document, a service provider could thus mirror or
927 cluster a message store and fail from the primary to secondary using
928 the DNS in an active-standby mode.
929
930 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Implementation Recommendations</span>
931
932 <span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Call Processing When Multiple Records Are Returned</span>
933
934 It is likely that both E2U+sip and E2U+voicemsg, E2U+videomsg, and/or
935 E2U+unifmsg Enumservice type records will be returned for a given
936 query. In this case, this could result in what is essentially
937 E2U+sip records for real-time communications with an end user, while,
938 for example, the E2U+voicemsg records will be used for real-time
939 communications with a voice messaging service, when the called party
940 is not available or does not wish to be disturbed. Therefore, the
941 network element that receives the results of this ENUM query will
942 need to know enough information in order to select the voicemsg
943 service type, rather than the sip service type.
944
945
946
947
948 <span class="grey">Livingood &amp; Troshynski Standards Track [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc5278">RFC 5278</a> VMSG Enumservice July 2008</span>
951
952
953 In addition, it is likely that multiple E2U+voicemsg, E2U+videomsg,
954 and/or E2U+unifmsg Enumservice type records will be returned for a
955 given query. In this case, multiple records may include order and
956 preference to allow recursion or load balancing. Order could be used
957 to designate a primary and a backup voice, video, or unified voice
958 and video messaging service. Preference could be used to load
959 balance across multiple voice, video, and/or unified voice and video
960 messaging servers by weight, for example.
961
962 Finally, as with multiple records resulting from a typical ENUM query
963 of the e164.arpa tree, it is up to the application using an ENUM
964 resolver to determine which record(s) to use and which record(s) to
965 ignore. Implementers should take this into consideration and build
966 logic into their applications that can select appropriately from
967 multiple records based on business, network, or other rules.
968
969 <span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. NAPTR Configuration Issues</span>
970
971 Implementers may wish to consider using regular expressions in order
972 to reduce the size of individual NAPTRs. This will have a
973 significant effect on the overall size of the database involved.
974
975 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. IANA Considerations</span>
976
977 This document registers the 'voicemsg' Enumservice type and the
978 subtype "tel", "sip", "sips", "http", and "https" under the
979 Enumservice registry described in the IANA considerations in <a href="./rfc3761">RFC</a>
980 <a href="./rfc3761">3761</a>. Details of this registration are provided in <a href="#section-4">Section 4</a> of this
981 document.
982
983 This document registers the 'videomsg' Enumservice type and the
984 subtype "sip", "sips", "http", and "https" under the Enumservice
985 registry described in the IANA considerations in <a href="./rfc3761">RFC 3761</a>. Details
986 of this registration are provided in <a href="#section-5">Section 5</a> of this document.
987
988 This document registers the 'unifmsg' Enumservice type and the
989 subtype "sip", "sips", "http", and "https" under the Enumservice
990 registry described in the IANA considerations in <a href="./rfc3761">RFC 3761</a>. Details
991 of this registration are provided in <a href="#section-6">Section 6</a> of this document.
992
993 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Acknowledgements</span>
994
995 The authors thank Rich Ferrise, Chris Harvey, Tong Zhou, and Hadriel
996 Kaplan for their detailed assistance in developing the ideas behind
997 this document in numerous brainstorming sessions, with information
998 gleaned from their work to solve real application architecture
999 issues. The authors also thank Lawrence Conroy and Jean-Francois
1000 Mule for their feedback in developing this document.
1001
1002
1003
1004 <span class="grey">Livingood &amp; Troshynski Standards Track [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc5278">RFC 5278</a> VMSG Enumservice July 2008</span>
1007
1008
1009 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Contributors</span>
1010
1011 Tong Zhou
1012 Comcast Cable Communications
1013 Email: [email protected]
1014
1015 Richard Ferrise
1016 Comcast Cable Communications
1017 Email: [email protected]
1018
1019 Chris Harvey
1020 Comcast Cable Communications
1021 Email: [email protected]
1022
1023 Hadriel Kaplan
1024 Acme Packet
1025 Email: [email protected]
1026
1027 <span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. References</span>
1028
1029 <span class="h3"><a class="selflink" id="section-12.1" href="#section-12.1">12.1</a>. Normative References</span>
1030
1031 [<a id="ref-1">1</a>] Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource
1032 Identifiers (URI) Dynamic Delegation Discovery System (DDDS)
1033 Application (ENUM)", <a href="./rfc3761">RFC 3761</a>, April 2004.
1034
1035 [<a id="ref-2">2</a>] ITU-T, "The International Public Telecommunication Numbering
1036 Plan", Recommendation E.164, May 1997.
1037
1038 [<a id="ref-3">3</a>] Mockapetris, P., "Domain names - concepts and facilities", STD
1039 13, <a href="./rfc1034">RFC 1034</a>, November 1987.
1040
1041 [<a id="ref-4">4</a>] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part
1042 Three: The Domain Name System (DNS) Database", <a href="./rfc3403">RFC 3403</a>,
1043 October 2002.
1044
1045 [<a id="ref-5">5</a>] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part
1046 One: The Comprehensive DDDS", <a href="./rfc3401">RFC 3401</a>, October 2002.
1047
1048 [<a id="ref-6">6</a>] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part
1049 Two: The Algorithm", <a href="./rfc3402">RFC 3402</a>, October 2002.
1050
1051 [<a id="ref-7">7</a>] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part
1052 Four: The Uniform Resource Identifiers (URI)", <a href="./rfc3404">RFC 3404</a>,
1053 October 2002.
1054
1055
1056
1057
1058
1059
1060 <span class="grey">Livingood &amp; Troshynski Standards Track [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc5278">RFC 5278</a> VMSG Enumservice July 2008</span>
1063
1064
1065 [<a id="ref-8">8</a>] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part
1066 Five: URI.ARPA Assignment Procedures", <a href="https://www.rfc-editor.org/bcp/bcp65">BCP 65</a>, <a href="./rfc3405">RFC 3405</a>,
1067 October 2002.
1068
1069 [<a id="ref-9">9</a>] Schulzrinne, H., "The tel URI for Telephone Numbers", <a href="./rfc3966">RFC 3966</a>,
1070 December 2004.
1071
1072 [<a id="ref-10">10</a>] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,
1073 Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP:
1074 Session Initiation Protocol", <a href="./rfc3261">RFC 3261</a>, June 2002.
1075
1076 [<a id="ref-11">11</a>] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L.,
1077 Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol --
1078 HTTP/1.1", <a href="./rfc2616">RFC 2616</a>, June 1999.
1079
1080 [<a id="ref-12">12</a>] Rescorla, E., "HTTP Over TLS", <a href="./rfc2818">RFC 2818</a>, May 2000.
1081
1082 <span class="h3"><a class="selflink" id="section-12.2" href="#section-12.2">12.2</a>. Informative References</span>
1083
1084 [<a id="ref-13">13</a>] Peterson, J., Liu, H., Yu, J., and B. Campbell, "Using E.164
1085 numbers with the Session Initiation Protocol (SIP)", <a href="./rfc3824">RFC 3824</a>,
1086 June 2004.
1087
1088 [<a id="ref-14">14</a>] Vaudreuil, G., "Voice Message Routing Service", <a href="./rfc4238">RFC 4238</a>,
1089 October 2005.
1090
1091 [<a id="ref-15">15</a>] Brandner, R., Conroy, L., and R. Stastny, "IANA Registration
1092 for Enumservices email, fax, mms, ems, and sms", <a href="./rfc4355">RFC 4355</a>,
1093 January 2006.
1094
1095 [<a id="ref-16">16</a>] Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose,
1096 "Protocol Modifications for the DNS Security Extensions", <a href="./rfc4035">RFC</a>
1097 <a href="./rfc4035">4035</a>, March 2005.
1098
1099 [<a id="ref-17">17</a>] Atkins, D. and R. Austein, "Threat Analysis of the Domain Name
1100 System (DNS)", <a href="./rfc3833">RFC 3833</a>, August 2004.
1101
1102 [<a id="ref-18">18</a>] Foster, M., McGarry, T., and J. Yu, "Number Portability in the
1103 Global Switched Telephone Network (GSTN): An Overview", <a href="./rfc3482">RFC</a>
1104 <a href="./rfc3482">3482</a>, February 2003.
1105
1106 [<a id="ref-19">19</a>] Peterson, J., "enumservice registration for Session Initiation
1107 Protocol (SIP) Addresses-of-Record", <a href="./rfc3764">RFC 3764</a>, April 2004.
1108
1109
1110
1111
1112
1113
1114
1115
1116 <span class="grey">Livingood &amp; Troshynski Standards Track [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc5278">RFC 5278</a> VMSG Enumservice July 2008</span>
1119
1120
1121 Authors' Addresses
1122
1123 Jason Livingood
1124 Comcast Cable Communications
1125 One Comcast Center
1126 1701 John F. Kennedy Boulevard
1127 Philadelphia, PA 19103
1128 USA
1129 EMail: [email protected]
1130
1131 Donald Troshynski
1132 Acme Packet
1133 EMail: [email protected]
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172 <span class="grey">Livingood &amp; Troshynski Standards Track [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc5278">RFC 5278</a> VMSG Enumservice July 2008</span>
1175
1176
1177 Full Copyright Statement
1178
1179 Copyright (C) The IETF Trust (2008).
1180
1181 This document is subject to the rights, licenses and restrictions
1182 contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
1183 retain all their rights.
1184
1185 This document and the information contained herein are provided on an
1186 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
1187 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
1188 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
1189 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
1190 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
1191 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1192
1193 Intellectual Property
1194
1195 The IETF takes no position regarding the validity or scope of any
1196 Intellectual Property Rights or other rights that might be claimed to
1197 pertain to the implementation or use of the technology described in
1198 this document or the extent to which any license under such rights
1199 might or might not be available; nor does it represent that it has
1200 made any independent effort to identify any such rights. Information
1201 on the procedures with respect to rights in RFC documents can be
1202 found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
1203
1204 Copies of IPR disclosures made to the IETF Secretariat and any
1205 assurances of licenses to be made available, or the result of an
1206 attempt made to obtain a general license or permission for the use of
1207 such proprietary rights by implementers or users of this
1208 specification can be obtained from the IETF on-line IPR repository at
1209 <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
1210
1211 The IETF invites any interested party to bring to its attention any
1212 copyrights, patents or patent applications, or other proprietary
1213 rights that may cover technology that may be required to implement
1214 this standard. Please address the information to the IETF at
1215 [email protected].
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228 Livingood &amp; Troshynski Standards Track [Page 22]
1229 </pre>