idnits 2.17.1
draft-ietf-enum-enumservices-transition-06.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 :
----------------------------------------------------------------------------
-- The draft header indicates that this document updates RFC4143, but the
abstract doesn't seem to mention this, which it should.
-- The draft header indicates that this document updates RFC3953, but the
abstract doesn't seem to mention this, which it should.
-- The draft header indicates that this document updates RFC3762, but the
abstract doesn't seem to mention this, which it should.
-- The draft header indicates that this document updates RFC3764, but the
abstract doesn't seem to mention this, which it should.
Miscellaneous warnings:
----------------------------------------------------------------------------
== The copyright year in the IETF Trust and authors Copyright Line does not
match the current year
(Using the creation date from RFC3762, updated by this document, for
RFC5378 checks: 2003-02-19)
-- The document seems to contain a disclaimer for pre-RFC5378 work, and may
have content which was first submitted before 10 November 2008. The
disclaimer is necessary when there are original authors that you have
been unable to contact, or if some do not wish to grant the BCP78 rights
to the IETF Trust. If you are able to get all authors (current and
original) to grant those rights, you can and should remove the
disclaimer; otherwise, the disclaimer is needed and you can ignore this
comment. (See the Legal Provisions document at
https://trustee.ietf.org/license-info for more information.)
-- The document date (June 30, 2010) is 5046 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)
-- Looks like a reference, but probably isn't: '15' on line 2208
-- Looks like a reference, but probably isn't: '16' on line 2208
-- Looks like a reference, but probably isn't: '14' on line 2130
-- Looks like a reference, but probably isn't: '12' on line 2674
-- Looks like a reference, but probably isn't: '13' on line 2065
-- Looks like a reference, but probably isn't: '7' on line 2724
-- Looks like a reference, but probably isn't: '6' on line 2696
-- Looks like a reference, but probably isn't: '4' on line 2409
-- Looks like a reference, but probably isn't: '17' on line 2234
-- Looks like a reference, but probably isn't: '10' on line 2344
-- Looks like a reference, but probably isn't: '11' on line 2649
== Outdated reference: A later version (-22) exists of
draft-ietf-enum-enumservices-guide-20
** Obsolete normative reference: RFC 3761 (Obsoleted by RFC 6116, RFC 6117)
-- Obsolete informational reference (is this intentional?): RFC 5226
(Obsoleted by RFC 8126)
Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 18 comments (--).
Run idnits with the --verbose option for more detailed information about
the items above.
--------------------------------------------------------------------------------
2 ENUM -- Telephone Number Mapping B. Hoeneisen
3 Working Group Ucom.ch
4 Internet-Draft A. Mayrhofer
5 Updates: 3762, 3764, 3953, 4143, enum.at
6 4002, 4238, 4355, 4415, 4769, June 30, 2010
7 4969, 4979, 5028, 5278, 5333
8 (if approved)
9 Intended status: Standards Track
10 Expires: January 1, 2011
12 Update of legacy IANA Registrations of Enumservices
13 draft-ietf-enum-enumservices-transition-06
15 Abstract
17 This document revises all Enumservices that were IANA registered
18 under the now obsolete specification of the Enumservice registry
19 defined in RFC 3761.
21 Status of this Memo
23 This Internet-Draft is submitted in full conformance with the
24 provisions of BCP 78 and BCP 79.
26 Internet-Drafts are working documents of the Internet Engineering
27 Task Force (IETF). Note that other groups may also distribute
28 working documents as Internet-Drafts. The list of current Internet-
29 Drafts is at http://datatracker.ietf.org/drafts/current/.
31 Internet-Drafts are draft documents valid for a maximum of six months
32 and may be updated, replaced, or obsoleted by other documents at any
33 time. It is inappropriate to use Internet-Drafts as reference
34 material or to cite them other than as "work in progress."
36 This Internet-Draft will expire on January 1, 2011.
38 Copyright Notice
40 Copyright (c) 2010 IETF Trust and the persons identified as the
41 document authors. All rights reserved.
43 This document is subject to BCP 78 and the IETF Trust's Legal
44 Provisions Relating to IETF Documents
45 (http://trustee.ietf.org/license-info) in effect on the date of
46 publication of this document. Please review these documents
47 carefully, as they describe your rights and restrictions with respect
48 to this document. Code Components extracted from this document must
49 include Simplified BSD License text as described in Section 4.e of
50 the Trust Legal Provisions and are provided without warranty as
51 described in the Simplified BSD License.
53 This document may contain material from IETF Documents or IETF
54 Contributions published or made publicly available before November
55 10, 2008. The person(s) controlling the copyright in some of this
56 material may not have granted the IETF Trust the right to allow
57 modifications of such material outside the IETF Standards Process.
58 Without obtaining an adequate license from the person(s) controlling
59 the copyright in such materials, this document may not be modified
60 outside the IETF Standards Process, and derivative works of it may
61 not be created outside the IETF Standards Process, except to format
62 it for publication as an RFC or to translate it into languages other
63 than English.
65 Table of Contents
67 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
69 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
71 3. IESG Action . . . . . . . . . . . . . . . . . . . . . . . . . 5
73 4. Legacy Enumservice Registrations Converted to XML Chunks . . . 5
74 4.1. email:mailto . . . . . . . . . . . . . . . . . . . . . . . 6
75 4.2. ems:mailto . . . . . . . . . . . . . . . . . . . . . . . . 7
76 4.3. ems:tel . . . . . . . . . . . . . . . . . . . . . . . . . 8
77 4.4. fax:tel . . . . . . . . . . . . . . . . . . . . . . . . . 9
78 4.5. ft:ftp . . . . . . . . . . . . . . . . . . . . . . . . . . 10
79 4.6. h323 . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
80 4.7. ical-access:http . . . . . . . . . . . . . . . . . . . . . 12
81 4.8. ical-access:https . . . . . . . . . . . . . . . . . . . . 13
82 4.9. ical-sched:mailto . . . . . . . . . . . . . . . . . . . . 14
83 4.10. ifax:mailto . . . . . . . . . . . . . . . . . . . . . . . 15
84 4.11. im . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
85 4.12. mms:mailto . . . . . . . . . . . . . . . . . . . . . . . . 17
86 4.13. mms:tel . . . . . . . . . . . . . . . . . . . . . . . . . 19
87 4.14. pres . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
88 4.15. pstn:sip . . . . . . . . . . . . . . . . . . . . . . . . . 21
89 4.16. pstn:tel . . . . . . . . . . . . . . . . . . . . . . . . . 22
90 4.17. sip . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
91 4.18. sms:mailto . . . . . . . . . . . . . . . . . . . . . . . . 24
92 4.19. sms:tel . . . . . . . . . . . . . . . . . . . . . . . . . 25
93 4.20. unifmsg:http . . . . . . . . . . . . . . . . . . . . . . . 26
94 4.21. unifmsg:https . . . . . . . . . . . . . . . . . . . . . . 27
95 4.22. unifmsg:sip . . . . . . . . . . . . . . . . . . . . . . . 28
96 4.23. unifmsg:sips . . . . . . . . . . . . . . . . . . . . . . . 29
97 4.24. vcard . . . . . . . . . . . . . . . . . . . . . . . . . . 30
98 4.25. videomsg:http . . . . . . . . . . . . . . . . . . . . . . 31
99 4.26. videomsg:https . . . . . . . . . . . . . . . . . . . . . . 32
100 4.27. videomsg:sip . . . . . . . . . . . . . . . . . . . . . . . 33
101 4.28. videomsg:sips . . . . . . . . . . . . . . . . . . . . . . 34
102 4.29. voice:tel . . . . . . . . . . . . . . . . . . . . . . . . 35
103 4.30. voicemsg:http . . . . . . . . . . . . . . . . . . . . . . 37
104 4.31. voicemsg:https . . . . . . . . . . . . . . . . . . . . . . 38
105 4.32. voicemsg:sip . . . . . . . . . . . . . . . . . . . . . . . 39
106 4.33. voicemsg:sips . . . . . . . . . . . . . . . . . . . . . . 40
107 4.34. voicemsg:tel . . . . . . . . . . . . . . . . . . . . . . . 41
108 4.35. vpim:ldap . . . . . . . . . . . . . . . . . . . . . . . . 42
109 4.36. vpim:mailto . . . . . . . . . . . . . . . . . . . . . . . 43
110 4.37. web:http . . . . . . . . . . . . . . . . . . . . . . . . . 45
111 4.38. web:https . . . . . . . . . . . . . . . . . . . . . . . . 46
112 4.39. xmpp . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
114 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 47
116 6. Security Considerations . . . . . . . . . . . . . . . . . . . 47
118 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 47
120 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 48
121 8.1. Normative References . . . . . . . . . . . . . . . . . . . 48
122 8.2. Informative References . . . . . . . . . . . . . . . . . . 49
124 Appendix A. Former Content of the IANA Repository . . . . . . . . 49
126 Appendix B. Document Changelog . . . . . . . . . . . . . . . . . 66
128 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 68
130 1. Introduction
132 [I-D.ietf-enum-enumservices-guide] has obsoleted the IANA
133 registration section of [RFC3761]. Since the IANA Enumservice
134 registry contains various Enumservices registered under the regime of
135 RFC 3761, those registrations do not conform to the new guidelines as
136 specified in [I-D.ietf-enum-enumservices-guide]. To ensure
137 consistency among all Enumservice registrations at IANA, this
138 document adds the (nowadays) missing elements to those legacy
139 registrations. Furthermore, all legacy Enumservice registrations are
140 converted to the new XML chunk format, and, where deemed necessary,
141 minor editorial corrections are applied.
143 However, this document does only add the missing elements to the XML
144 chunks as specified in the IANA Considerations section of
145 [I-D.ietf-enum-enumservices-guide], but does not complete the
146 (nowadays) missing sections of the corresponding Enumservice
147 Specifications. In order to conform with the new registration regime
148 as specified in [I-D.ietf-enum-enumservices-guide], those Enumservice
149 Specifications still have to be revised.
151 It is important to note that this document does not update the
152 functional specification of the concerned Enumservices.
154 The following RFCs are updated by this document:
156 o [RFC3762]
157 o [RFC3764]
158 o [RFC3953]
159 o [RFC4143]
160 o [RFC4002]
161 o [RFC4238]
162 o [RFC4355]
163 o [RFC4415]
164 o [RFC4769]
165 o [RFC4969]
166 o [RFC4979]
167 o [RFC5028]
168 o [RFC5278]
169 o [RFC5333]
171 2. Terminology
173 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
174 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
175 document are to be interpreted as described in RFC 2119 [RFC2119].
177 3. IESG Action
179 According to [RFC3761], any Enumservice registration had to be
180 published as RFC on the Standards Track, Experimental RFC, or as a
181 BCP. [I-D.ietf-enum-enumservices-guide] no longer has this
182 requirement, i.e. "Specification Required", which implies the use of
183 a Designated Expert, [RFC5226] is sufficient. As any update to an
184 existing specification must have at least the same Maturity Level
185 (see [RFC2026]) as the document it updates, an IETF action (approval
186 of this document) is required to override this requirement.
188 This document changes the approval required for updates of
189 Enumservice registrations to Specification Required including that
190 the specification and request are reviewed by a Designated Expert as
191 described in [I-D.ietf-enum-enumservices-guide].
193 4. Legacy Enumservice Registrations Converted to XML Chunks
195 In the following the legacy Enumservice Registrations converted to
196 XML chunks including the new elements introduced by
197 [I-D.ietf-enum-enumservices-guide].
199 (Note that any references in Sections 4.1 - 4.39 refer to the
200 references section within the respective Enumservice Specification.)
202 [Note for RFC Editor: Please replace any instance of RFCTHIS with
203 the RFC number of this document before publication]
205 4.1. email:mailto
207
208
209 Application-Based, Common
210 email
211 mailto
212 mailto
213
214
215 This Enumservice indicates that the resource can be
216 addressed by the associated URI in order to send an
217 email.
218
219
220
221 See , Section 6.
222
223 COMMON
224
225 (updated by RFCTHIS)
226
227
228
229
230
231
232
233
235 4.2. ems:mailto
237
238
239 Application-Based, Common
240 ems
241 mailto
242 mailto
243
244
245 This Enumservice indicates that the resource
246 identified by the associated URI is capable
247 of receiving a message using an email protocol.
248
249
250 EMS content is sent over SMTP using the format
251 specified by TS 23.140 [15] Section 8.4.4 and TS
252 26.140 [16] Section 4, as an MMS message. Within
253 such a message, EMS content is carried as either a
254 text or application/octet-stream MIME sub-part (see
255 TS 26.140 [16], Section 4.1).
256
257
258 References are contained in .
259
260
261
262
263 There are no specific security issues with this
264 Enumservice. However, the general considerations of
265 Section 6 of apply.
266
267
268 COMMON
269
270 (updated by RFCTHIS)
271
272
273
274
275
276
277
278
280 4.3. ems:tel
282
283
284 Application-Based, Common
285 ems
286 tel
287 tel
288
289
290 This Enumservice indicates that the resource
291 identified by the associated URI is capable
292 of receiving a message using the Enhanced Message
293 Service (EMS) [14].
294
295
296 References are contained in .
297
298
299
300
301 There are no specific security issues with this
302 Enumservice. However, the general considerations of
303 Section 6 of apply.
304
305
306 COMMON
307
308 (updated by RFCTHIS)
309
310
311
312
313
314
315
316
317
318 Note that an indication of EMS can be taken as
319 implying that the recipient is capable of receiving
320 SMS messages at this address as well.
321
322
323
325 4.4. fax:tel
327
328
329 Application-Based, Subset
330 fax
331 tel
332 tel
333
334
335 This Enumservice indicates that the resource
336 identified by the associated URI is capable
337 of being contacted to provide a communication
338 session during which facsimile documents can be
339 sent.
340
341
342 A client selecting this NAPTR will have support
343 for generating and sending facsimile documents to
344 the recipient using the PSTN session and transfer
345 protocols specified in [12] and [13] in
346 -
347 in short, they will have a fax program with a local
348 or shared PSTN access over which they can send
349 faxes.
350
351
352 References are contained in .
353
354
355
356 See , Section 6.
357
358 COMMON
359
360 (updated by RFCTHIS)
361
362
363
364
365
366
367
368
370 4.5. ft:ftp
372
373
374 Application-Based, Subset
375 ft
376 ftp
377 ftp
378
379
380 This Enumservice indicates that the resource
381 identified by the associated URI is a file
382 service from which a file or file listing can be
383 retrieved.
384
385
386
387 See , Section 5.
388
389 COMMON
390
391 (updated by RFCTHIS)
392
393
394
395
396
397
398
399
401 4.6. h323
403
404
405 Protocol-Based
406 h323
407
408 h323
409
410 See , Section 3.
411
412
413 See , Section 5.
414
415 COMMON
416
417 (updated by RFCTHIS)
418
419
420
421
422
423
425 4.7. ical-access:http
427
428
429 Application-Based, Common
430 ical-access
431 http
432 http
433
434
435 This Enumservice indicates that the resource identified
436 can be addressed by the associated URI in order to access
437 a user's calendar (for example free/busy status) using
438 the CalDAV [7] protocol for Internet calendaring.
439
440
441 References are contained in .
442
443
444
445 See , Section 4.
446
447 COMMON
448
449 (updated by RFCTHIS)
450
451
452
453
454
455
457 4.8. ical-access:https
459
460
461 Application-Based, Common
462 ical-access
463 https
464 https
465
466
467 This Enumservice indicates that the resource identified
468 can be addressed by the associated URI in order to access
469 a user's calendar (for example free/busy status) using
470 the CalDAV [7] protocol for Internet calendaring.
471
472
473 References are contained in .
474
475
476
477 See , Section 4.
478
479 COMMON
480
481 (updated by RFCTHIS)
482
483
484
485
486
487
489 4.9. ical-sched:mailto
491
492
493 Application-Based, Common
494 ical-sched
495 mailto
496 mailto
497
498
499 This Enumservice indicates that the resource identified
500 can be addressed by the associated URI used for
501 scheduling using Internet calendaring via Internet mail
502 with the iMIP [6] protocol.
503
504
505 References are contained in .
506
507
508
509 See , Section 4.
510
511 COMMON
512
513 (updated by RFCTHIS)
514
515
516
517
518
519
521 4.10. ifax:mailto
523
524
525 Application-Based, Subset
526 ifax
527 mailto
528 mailto
529
530 See , Section 1.
531
532
533 See , Section 3.
534
535 COMMON
536
537 (updated by RFCTHIS)
538
539
540
541
542
543
544
545
546 The URI Scheme is 'mailto' because facsimile is a
547 profile of standard Internet mail and uses standard
548 Internet mail addressing.
549
550
551
553 4.11. im
555
556
557 Application-Based, Common
558 im
559
560 im
561
562
563 This Enumservice indicates that the resource
564 identified is an 'im:' URI. The 'im:' URI scheme
565 does not identify any particular protocol that will
566 be used to handle instant messaging receipt or
567 delivery, rather the mechanism in RFC3861 [4] is
568 used to discover whether an IM protocol supported by
569 the party querying ENUM is also supported by the
570 target resource.
571
572
573 References are contained in .
574
575
576
577 See , Section 3.
578
579 COMMON
580
581 (updated by RFCTHIS)
582
583
584
585
586
587
589 4.12. mms:mailto
591
592
593 Application-Based, Common
594 mms
595 mailto
596 mailto
597
598
599 This Enumservice indicates that the resource
600 identified by the associated URI is capable
601 of receiving a message using an email protocol.
602
603
604 MMS messages are sent over SMTP using the format
605 specified by TS 23.140 [15] Section 8.4.4 and TS
606 26.140 [16] Section 4.
607
608
609 Within and between MMS Environments (MMSE,
610 network infrastructures that support the MultiMedia
611 Service), other pieces of state data (for example,
612 charging-significant information) are exchanged
613 between MMS Relay Servers. Thus, although these
614 servers use SMTP as the "bearer" for their
615 application exchanges, they map their internal state
616 to specialized header fields carried in the SMTP message
617 exchanges. The header fields used in such MMSE are
618 described in detail in [17].
619
620
621 References are contained in .
622
623
624
625
626 There are no specific security issues with this
627 Enumservice. However, the general considerations of
628 Section 6 of apply.
629
630
631 COMMON
632
633 (updated by RFCTHIS)
634
635
636
637
638
639
640
641
642
643 The MMS Architecture describes an interface
644 between the MMSE and "legacy messaging systems"
645 (labelled as MM3) which accepts "standard" SMTP
646 messages. Thus although the MMS Relay Server that
647 supports this interface appears as a standard SMTP
648 server from the perspective of an Internet-based
649 mail server, it acts as a gateway and translator,
650 adding the internal state data that is used within
651 and between the MMS Environments. This mechanism is
652 described in [17], which also includes references to
653 the specifications agreed by those bodies
654 responsible for the design of the MMS.
655
656
657 References are contained in .
658
659
660
662 4.13. mms:tel
664
665
666 Application-Based, Common
667 mms
668 tel
669 tel
670
671
672 This Enumservice indicates that the resource
673 identified by the associated URI is capable
674 of receiving a message using the Multimedia
675 Messaging Service (MMS) [15].
676
677
678 References are contained in .
679
680
681
682
683 There are no specific security issues with this
684 Enumservice. However, the general considerations of
685 Section 6 of apply.
686
687
688 COMMON
689
690 (updated by RFCTHIS)
691
692
693
694
695
696
697
698
699
700 Note that MMS can be used as an alternative to
701 deliver an SMS RP-DATA RPDU if, for example, the
702 SMS bearer is not supported. If an entry includes
703 this Enumservice, then in effect this can be taken
704 as implying that the recipient is capable of
705 receiving EMS or SMS messages at this address. Such
706 choices on the end system de do have two small
707 caveats; whilst in practice all terminals supporting
708 MMS today support SMS as well, it might not
709 necessarily be the case in the future, and there may
710 be tariff differences in using the MMS rather than
711 using the SMS or EMS.
712
713
714
716 4.14. pres
718
719
720 Application-Based, Common
721 pres
722
723 pres
724
725 See , Section 4.
726
727
728 See , Section 6.
729
730 COMMON
731
732 (updated by RFCTHIS)
733
734
735
736
737
738
739
740 See , Section 3.
741
742
743
745 4.15. pstn:sip
747
748
749 Application-Based, Common
750 pstn
751 sip
752 sip
753
754
755 These Enumservices indicate that the
756 resource identified can be addressed by the
757 associated URI in order to initiate a
758 telecommunication session, which may include two-way
759 voice or other communications, to the PSTN.
760
761
762
763 See , Section 7.
764
765 COMMON
766
767 (updated by RFCTHIS)
768
769
770
771
772
773
774
775
776 A Number Portability Dip Indicator (npdi) should
777 be used in practice
778 (see , Section 4).
779
780
781
783 4.16. pstn:tel
785
786
787 Application-Based, Ancillary
788 pstn
789 tel
790 tel
791
792
793 These Enumservices indicate that the
794 resource identified can be addressed by the
795 associated URI in order to initiate a
796 telecommunication session, which may include two-way
797 voice or other communications, to the PSTN. These
798 URIs may contain number portability data as
799 specified in RFC4694 [10].
800
801
802 References are contained in .
803
804
805
806 See , Section 7.
807
808 COMMON
809
810 (updated by RFCTHIS)
811
812
813
814
815
816
817
818
819 A Number Portability Dip Indicator (npdi) should
820 be used in practice
821 (see , Section 4).
822
823
824
826 4.17. sip
828
829
830 Protocol-Based
831 sip
832
833 sip
834 sips
835
836 See , Section 4.
837
838
839 See , Section 6.
840
841 COMMON
842
843 (updated by RFCTHIS)
844
845
846
847
848
849
850
851 See , Section 3.
852
853
854
856 4.18. sms:mailto
858
859
860 Application-Based, Common
861 sms
862 mailto
863 mailto
864
865
866 This Enumservice indicates that the resource
867 identified by the associated URI is capable
868 of receiving a message using an email protocol.
869
870
871 SMS content is sent over SMTP using the format
872 specified by TS 23.140 [15] Section 8.4.4 and TS
873 26.140 [16] Section 4, as an MMS message. Within
874 such a message, SMS content is carried as either a
875 text or application/octet-stream MIME sub-part (see
876 TS 26.140 [16], Section 4.1)
877
878
879 References are contained in .
880
881
882
883
884 There are no specific security issues with this
885 Enumservice. However, the general considerations of
886 Section 6 of apply.
887
888
889 COMMON
890
891 (updated by RFCTHIS)
892
893
894
895
896
897
898
899
901 4.19. sms:tel
903
904
905 Application-Based, Common
906 sms
907 tel
908 tel
909
910
911 This Enumservice indicates that the resource
912 identified by the associated URI is capable
913 of receiving a message using the Short Message
914 Service (SMS) [14].
915
916
917 References are contained in .
918
919
920
921
922 There are no specific security issues with this
923 Enumservice. However, the general considerations of
924 Section 6 of apply.
925
926
927 COMMON
928
929 (updated by RFCTHIS)
930
931
932
933
934
935
936
937
939 4.20. unifmsg:http
941
942
943 Application-Based, Common
944 unifmsg
945 http
946 http
947
948
949 This Enumservice indicates that the resource identified by
950 the associated URI scheme is capable of being a source of
951 information.
952
953
954 Note that the kind of information retrieved can be manifold.
955 Usually, contacting a resource by an 'http:' [11] URI
956 provides a document. This document can contain references
957 that will trigger the download of many different kinds of
958 information, such as text, audio, video, executable code, or
959 even video message files. Thus, one cannot be more specific
960 about the kind of information expected when contacting the
961 resource.
962
963
964 References are contained in .
965
966
967
968 See , Section 3.
969
970 COMMON
971
972 (updated by RFCTHIS)
973
974
975
976
977
978
979
980
981 Implementers should review a non-exclusive list of examples
982 in Section 7 of .
983
984
985
987 4.21. unifmsg:https
989
990
991 Application-Based, Common
992 unifmsg
993 https
994 https
995
996
997 This Enumservice indicates that the resource identified by
998 the associated URI scheme is capable of being a source of
999 information, which can be contacted using TLS or the Secure
1000 Socket Layer protocol.
1001
1002
1003 Note that the kind of information retrieved can be manifold.
1004 Usually, contacting a resource by an 'https:' [12] URI
1005 provides a document. This document can contain references
1006 that will trigger the download of many different kinds of
1007 information, such as text, audio, video, executable code, or
1008 even video message files. Thus, one cannot be more specific
1009 about the kind of information expected when contacting the
1010 resource.
1011
1012
1013 References are contained in .
1014
1015
1016
1017 See , Section 3.
1018
1019 COMMON
1020
1021 (updated by RFCTHIS)
1022
1023
1024
1025
1026
1027
1028
1029
1030 Implementers should review a non-exclusive list of examples
1031 in Section 7 of .
1032
1033
1034
1036 4.22. unifmsg:sip
1038
1039
1040 Application-Based, Common
1041 unifmsg
1042 sip
1043 sip
1044
1045
1046 This Enumservice indicates that the resource identified can
1047 be addressed by the associated URI scheme in order to
1048 initiate a unified communication session to a unified
1049 messaging system.
1050
1051
1052
1053 See , Section 3.
1054
1055 COMMON
1056
1057 (updated by RFCTHIS)
1058
1059
1060
1061
1062
1063
1064
1065
1066 Implementers should review a non-exclusive list of examples
1067 in Section 7 of .
1068
1069
1070
1072 4.23. unifmsg:sips
1074
1075
1076 Application-Based, Common
1077 unifmsg
1078 sips
1079 sips
1080
1081
1082 This Enumservice indicates that the resource identified can
1083 be addressed by the associated URI scheme in order to
1084 initiate a unified communication session to a unified
1085 messaging system.
1086
1087
1088
1089 See , Section 3.
1090
1091 COMMON
1092
1093 (updated by RFCTHIS)
1094
1095
1096
1097
1098
1099
1100
1101
1102 Implementers should review a non-exclusive list of examples
1103 in Section 7 of .
1104
1105
1106
1108 4.24. vcard
1110
1111
1112 Data Type-Based
1113 vcard
1114
1115 http
1116 https
1117
1118
1119 This Enumservice indicates that the resource
1120 identified is a plain vCard, according to RFC2426,
1121 which may be accessed using HTTP / HTTPS [7].
1122
1123
1124 Clients fetching the vCard from the resource
1125 indicated should expect access to be
1126 restricted. Additionally, the comprehension of the
1127 data provided may vary depending on the client's
1128 identity.
1129
1130
1131 References are contained in .
1132
1133
1134
1135 See , Section 5.
1136
1137 COMMON
1138
1139 (updated by RFCTHIS)
1140
1141
1142
1143
1144
1145
1147 4.25. videomsg:http
1149
1150
1151 Application-Based, Common
1152 videomsg
1153 http
1154 http
1155
1156
1157 This Enumservice indicates that the resource identified by
1158 the associated URI scheme is capable of being a source of
1159 information.
1160
1161
1162 Note that the kind of information retrieved can be manifold.
1163 Usually, contacting a resource by an 'http:' [11] URI
1164 provides a document. This document can contain references
1165 that will trigger the download of many different kinds of
1166 information, such as text, audio, video, executable code, or
1167 even video message files. Thus, one cannot be more specific
1168 about the kind of information expected when contacting the
1169 resource.
1170
1171
1172 References are contained in .
1173
1174
1175
1176 See , Section 3.
1177
1178 COMMON
1179
1180 (updated by RFCTHIS)
1181
1182
1183
1184
1185
1186
1187
1188
1189 Implementers should review a non-exclusive list of examples
1190 in Section 7 of .
1191
1192
1193
1195 4.26. videomsg:https
1197
1198
1199 Application-Based, Common
1200 videomsg
1201 https
1202 https
1203
1204
1205 This Enumservice indicates that the resource identified by
1206 the associated URI scheme is capable of being a source of
1207 information, which can be contacted using TLS or the Secure
1208 Socket Layer protocol.
1209
1210
1211 Note that the kind of information retrieved can be manifold.
1212 Usually, contacting a resource by an 'https:' [12] URI
1213 provides a document. This document can contain references
1214 that will trigger the download of many different kinds of
1215 information, such as text, audio, video, executable code, or
1216 even video message files. Thus, one cannot be more specific
1217 about the kind of information expected when contacting the
1218 resource.
1219
1220
1221 References are contained in .
1222
1223
1224
1225 See , Section 3.
1226
1227 COMMON
1228
1229 (updated by RFCTHIS)
1230
1231
1232
1233
1234
1235
1236
1237
1238 Implementers should review a non-exclusive list of examples
1239 in Section 7 of .
1240
1241
1242
1244 4.27. videomsg:sip
1246
1247
1248 Application-Based, Common
1249 videomsg
1250 sip
1251 sip
1252
1253
1254 This Enumservice indicates that the resource identified can
1255 be addressed by the associated URI scheme in order to
1256 initiate a video communication session to a video messaging
1257 system.
1258
1259
1260
1261 See , Section 3.
1262
1263 COMMON
1264
1265 (updated by RFCTHIS)
1266
1267
1268
1269
1270
1271
1272
1273
1274 Implementers should review a non-exclusive list of examples
1275 in Section 7 of .
1276
1277
1278
1280 4.28. videomsg:sips
1282
1283
1284 Application-Based, Common
1285 videomsg
1286 sips
1287 sips
1288
1289
1290 This Enumservice indicates that the resource identified can
1291 be addressed by the associated URI scheme in order to
1292 initiate a video communication session to a video messaging
1293 system.
1294
1295
1296
1297 See , Section 3.
1298
1299 COMMON
1300
1301 (updated by RFCTHIS)
1302
1303
1304
1305
1306
1307
1308
1309
1310 Implementers should review a non-exclusive list of examples
1311 in Section 7 of .
1312
1313
1314
1316 4.29. voice:tel
1318
1319
1320 Application-Based, Common
1321 voice
1322 tel
1323 tel
1324
1325
1326 The kind of communication indicated by this
1327 Enumservice is "Interactive Voice". From a protocol
1328 perspective, this communication is expected to
1329 involve bidirectional media streams carrying audio
1330 data.
1331
1332
1333 A client may imply that the person controlling
1334 population of a NAPTR holding this Enumservice
1335 indicates their capability to engage in an
1336 interactive voice session when contacted using the
1337 URI generated by this NAPTR.
1338
1339
1340
1341 See , Section 5.
1342
1343 COMMON
1344
1345 (updated by RFCTHIS)
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355 This Enumservice indicates that the person
1356 responsible for the NAPTR is accessible via the PSTN
1357 (Public Switched Telephone Network) or PLMN (Public
1358 Land Mobile Network) using the value of the
1359 generated URI.
1360
1361 The kind of subsystem required to initiate a
1362 Voice Enumservice with this Subtype is a "Dialler".
1363 This is a subsystem that either provides a local
1364 connection to the PSTN or PLMN, or that provides an
1365 indirect connection to those networks. The
1366 subsystem will use the telephone number held in the
1367 generated URI to place a voice call. The voice call
1368 is placed to a network that uses E.164 numbers to
1369 route calls to an appropriate destination.
1370
1371
1372 Note that the PSTN/PLMN connection may be
1373 indirect. The end user receiving this NAPTR may
1374 have a relationship with a Communications Service
1375 Provider that accepts call initiation requests from
1376 that subsystem using an IP-based protocol such as
1377 SIP or H.323, and places the call to the PSTN using
1378 a remote gateway service. In this case the Provider
1379 may either accept requests using "tel:" URIs or has
1380 a defined mechanism to convert "tel:" URI values
1381 into a "protocol-native" form.
1382
1383
1384 The "tel:" URI value SHOULD be fully qualified
1385 (using the "global phone number" form of RFC3966
1386 [10]). A "local phone number" as defined in that
1387 document SHOULD NOT be used unless the controller of
1388 the zone in which the NAPTR appears is sure that it
1389 can be distinguished unambiguously by all clients
1390 that can access the resource record and that a call
1391 from their network access points can be routed to
1392 that destination.
1393
1394
1395 References are contained in .
1396
1397
1398
1400 4.30. voicemsg:http
1402
1403
1404 Application-Based, Common
1405 voicemsg
1406 http
1407 http
1408
1409
1410 This Enumservice indicates that the resource identified by
1411 the associated URI scheme is capable of being a source of
1412 information.
1413
1414
1415 Note that the kind of information retrieved can be manifold.
1416 Usually, contacting a resource by an 'http:' [11] URI
1417 provides a document. This document can contain references
1418 that will trigger the download of many different kinds of
1419 information, such as text, audio, video, executable code, or
1420 even voice message files. Thus, one cannot be more specific
1421 about the kind of information expected when contacting the
1422 resource.
1423
1424
1425 References are contained in .
1426
1427
1428
1429 See , Section 3.
1430
1431 COMMON
1432
1433 (updated by RFCTHIS)
1434
1435
1436
1437
1438
1439
1440
1441
1442 Implementers should review a non-exclusive list of examples
1443 in Section 7 of .
1444
1445
1446
1448 4.31. voicemsg:https
1450
1451
1452 Application-Based, Common
1453 voicemsg
1454 https
1455 https
1456
1457
1458 This Enumservice indicates that the resource identified by
1459 the associated URI scheme is capable of being a source of
1460 information, which can be contacted using TLS or the Secure
1461 Socket Layer protocol.
1462
1463
1464 Note that the kind of information retrieved can be manifold.
1465 Usually, contacting a resource by an 'https:' [12] URI
1466 provides a document. This document can contain references
1467 that will trigger the download of many different kinds of
1468 information, such as text, audio, video, executable code, or
1469 even voice message files. Thus, one cannot be more specific
1470 about the kind of information expected when contacting the
1471 resource.
1472
1473
1474 References are contained in .
1475
1476
1477
1478 See , Section 3.
1479
1480 COMMON
1481
1482 (updated by RFCTHIS)
1483
1484
1485
1486
1487
1488
1489
1490
1491 Implementers should review a non-exclusive list of examples
1492 in Section 7 of .
1493
1494
1495
1497 4.32. voicemsg:sip
1499
1500
1501 Application-Based, Common
1502 voicemsg
1503 sip
1504 sip
1505
1506
1507 This Enumservice indicates that the resource identified can
1508 be addressed by the associated URI scheme in order to
1509 initiate a voice communication session to a voice messaging
1510 system.
1511
1512
1513
1514 See , Section 3.
1515
1516 COMMON
1517
1518 (updated by RFCTHIS)
1519
1520
1521
1522
1523
1524
1525
1526
1527 Implementers should review a non-exclusive list of examples
1528 in Section 7 of .
1529
1530
1531
1533 4.33. voicemsg:sips
1535
1536
1537 Application-Based, Common
1538 voicemsg
1539 sips
1540 sips
1541
1542
1543 This Enumservice indicates that the resource identified can
1544 be addressed by the associated URI scheme in order to
1545 initiate a voice communication session to a voice messaging
1546 system.
1547
1548
1549
1550 See , Section 3.
1551
1552 COMMON
1553
1554 (updated by RFCTHIS)
1555
1556
1557
1558
1559
1560
1561
1562
1563 Implementers should review a non-exclusive list of examples
1564 in Section 7 of .
1565
1566
1567
1569 4.34. voicemsg:tel
1571
1572
1573 Application-Based, Common
1574 voicemsg
1575 tel
1576 tel
1577
1578
1579 This Enumservice indicates that the resource identified can
1580 be addressed by the associated URI scheme in order to
1581 initiate a voice communication session to a voice messaging
1582 system.
1583
1584
1585
1586 See , Section 3.
1587
1588 COMMON
1589
1590 (updated by RFCTHIS)
1591
1592
1593
1594
1595
1596
1597
1598
1599 Implementers should review a non-exclusive list of examples
1600 in Section 7 of .
1601
1602
1603
1605 4.35. vpim:ldap
1607
1608
1609 Data Type-Based
1610 vpim
1611 ldap
1612 ldap
1613
1614 See , Section 3.2 - 3.3.
1615
1616
1617
1618 Malicious Redirection:
1619 One of the fundamental dangers related to any
1620 service such as this is that a malicious entry in a
1621 resolver's database will cause clients to resolve
1622 the E.164 into the wrong LDAP URI. The possible
1623 intent may be to cause the client to connect to a
1624 rogue LDAP server and retrieve (or fail to retrieve)
1625 a resource containing fraudulent or damaging
1626 information.
1627
1628
1629 Denial of Service:
1630 By removing the URI to which the E.164 maps, a
1631 malicious intruder may remove the client's ability
1632 to access the LDAP directory server.
1633
1634
1635 COMMON
1636
1637 (updated by RFCTHIS)
1638
1639
1640
1641
1642
1643
1645 4.36. vpim:mailto
1647
1648
1649 Data Type-Based
1650 vpim
1651 mailto
1652 mailto
1653
1654 See , Section 4.2 - 4.4.
1655
1656
1657
1658 Malicious Redirection:
1659 One of the fundamental dangers related to any
1660 service such as this is that a malicious entry in a
1661 resolver's database will cause clients to resolve
1662 the E.164 into the wrong email URI. The possible
1663 intent may be to cause the client to send the
1664 information to an incorrect destination.
1665
1666
1667 Denial of Service:
1668 By removing the URI to which the E.164 maps, a
1669 malicious intruder may remove the client's ability
1670 to access the resource.
1671
1672
1673 Unsolicited Bulk Email:
1674 The exposure of email addresses through the ENUM
1675 service provides a bulk mailer access to large
1676 numbers of email addresses where only the telephone
1677 number was previously known.
1678
1679
1680 COMMON
1681
1682 (updated by RFCTHIS)
1683
1684
1685
1686
1687
1688
1689
1690 Error Conditions:
1691
1692
1693 E.164 number not in the numbering plan
1694
1695
1696 E.164 number in the numbering plan, but no
1697 URIs exist for that number
1698
1699
1700 E2U+vpim:mailto Service unavailable of email
1701 addresses where only the telephone number was
1702 previously known.
1703
1704
1705
1707 4.37. web:http
1709
1710
1711 Application-Based, Common
1712 web
1713 http
1714 http
1715
1716
1717 This Enumservice indicates that the resource
1718 identified by the associated URI is capable
1719 of being a source of information. It has to be
1720 noted that the kind of information retrieved can be
1721 manifold. Usually, contacting a resource by an
1722 "http:" URI provides a document. This document can
1723 contain references that will trigger download of
1724 many different kinds of information, like audio or
1725 video or executable code. Thus, one can not be more
1726 specific about the kind of information that can be
1727 expected when contacting the resource.
1728
1729
1730
1731 See , Section 5.
1732
1733 COMMON
1734
1735 (updated by RFCTHIS)
1736
1737
1738
1739
1740
1741
1742
1743
1745 4.38. web:https
1747
1748
1749 Application-Based, Common
1750 web
1751 https
1752 https
1753
1754
1755 This Enumservice indicates that the resource
1756 identified by the associated URI is capable
1757 of being a source of information, which can be
1758 contacted by using TLS or Secure Socket Layer
1759 protocol. It has to be noted that the kind of
1760 information retrieved can be manifold. Usually,
1761 contacting a resource by an "https:" URI provides a
1762 document. This document can contain all different
1763 kind of information, like audio or video or
1764 executable code. Thus, one can not be more specific
1765 what information to expect when contacting the
1766 resource.
1767
1768
1769
1770 See , Section 5.
1771
1772 COMMON
1773
1774 (updated by RFCTHIS)
1775
1776
1777
1778
1779
1780
1781
1782
1784 4.39. xmpp
1786
1787
1788 Protocol-Based
1789 xmpp
1790
1791 xmpp
1792
1793
1794 This Enumservice indicates that the resource
1795 identified is an XMPP entity.
1796
1797
1798
1799 See , Section 6.
1800
1801 COMMON
1802
1803 (updated by RFCTHIS)
1804
1805
1806
1807
1808
1809
1811 5. IANA Considerations
1813 IANA are to replace all legacy Enumservice Registrations as per
1814 Section 4.
1816 6. Security Considerations
1818 Since this document does not introduce any technology or protocol,
1819 there are no security issues to be considered for this document
1820 itself.
1822 7. Acknowledgements
1824 The authors would like to thank the following people who have
1825 provided feedback or significant contributions to the development of
1826 this document: Jari Arkko, Scott Bradner, Gonzalo Camarillo, and
1827 Alfred Hoenes, Ari Keranen, Alexey Melnikov
1829 8. References
1831 8.1. Normative References
1833 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
1834 Requirement Levels", BCP 14, RFC 2119, March 1997.
1836 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
1837 3", BCP 9, RFC 2026, October 1996.
1839 [I-D.ietf-enum-enumservices-guide]
1840 Hoeneisen, B., Mayrhofer, A., and J. Livingood, "IANA
1841 Registration of Enumservices: Guide, Template and IANA
1842 Considerations", draft-ietf-enum-enumservices-guide-20
1843 (work in progress), April 2010.
1845 [RFC3761] Faltstrom, P. and M. Mealling, "The E.164 to Uniform
1846 Resource Identifiers (URI) Dynamic Delegation Discovery
1847 System (DDDS) Application (ENUM)", RFC 3761, April 2004.
1849 [RFC3762] Levin, O., "Telephone Number Mapping (ENUM) Service
1850 Registration for H.323", RFC 3762, April 2004.
1852 [RFC3764] Peterson, J., "enumservice registration for Session
1853 Initiation Protocol (SIP) Addresses-of-Record", RFC 3764,
1854 April 2004.
1856 [RFC3953] Peterson, J., "Telephone Number Mapping (ENUM) Service
1857 Registration for Presence Services", RFC 3953,
1858 January 2005.
1860 [RFC4143] Toyoda, K. and D. Crocker, "Facsimile Using Internet Mail
1861 (IFAX) Service of ENUM", RFC 4143, November 2005.
1863 [RFC4002] Brandner, R., Conroy, L., and R. Stastny, "IANA
1864 Registration for Enumservice 'web' and 'ft'", RFC 4002,
1865 February 2005.
1867 [RFC4238] Vaudreuil, G., "Voice Message Routing Service", RFC 4238,
1868 October 2005.
1870 [RFC4355] Brandner, R., Conroy, L., and R. Stastny, "IANA
1871 Registration for Enumservices email, fax, mms, ems, and
1872 sms", RFC 4355, January 2006.
1874 [RFC4415] Brandner, R., Conroy, L., and R. Stastny, "IANA
1875 Registration for Enumservice Voice", RFC 4415,
1876 February 2006.
1878 [RFC4769] Livingood, J. and R. Shockey, "IANA Registration for an
1879 Enumservice Containing Public Switched Telephone Network
1880 (PSTN) Signaling Information", RFC 4769, November 2006.
1882 [RFC4969] Mayrhofer, A., "IANA Registration for vCard Enumservice",
1883 RFC 4969, August 2007.
1885 [RFC4979] Mayrhofer, A., "IANA Registration for Enumservice 'XMPP'",
1886 RFC 4979, August 2007.
1888 [RFC5028] Mahy, R., "A Telephone Number Mapping (ENUM) Service
1889 Registration for Instant Messaging (IM) Services",
1890 RFC 5028, October 2007.
1892 [RFC5278] Livingood, J. and D. Troshynski, "IANA Registration of
1893 Enumservices for Voice and Video Messaging", RFC 5278,
1894 July 2008.
1896 [RFC5333] Mahy, R. and B. Hoeneisen, "IANA Registration of
1897 Enumservices for Internet Calendaring", RFC 5333,
1898 October 2009.
1900 8.2. Informative References
1902 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
1903 IANA Considerations Section in RFCs", BCP 26, RFC 5226,
1904 May 2008.
1906 Appendix A. Former Content of the IANA Repository
1908 Enumservice Registrations
1910 (last updated 2009-10-13)
1912 Registries included below:
1913 - Enumservice Registrations
1915 Registry Name: Enumservice Registrations
1916 Reference: [RFC3761]
1917 Registration Procedures: Require an RFC approved by the IESG
1919 Note:
1920 Enumservice specifications contain the functional specification (i.e.
1921 what it can be used for), the valid protocols, and the URI schemes
1922 that may be returned.
1924 Registry:
1925 Service Name: "H323"
1926 URI Scheme(s): "h323:"
1927 Functional Specification:
1928 See Section "3. The E2U+H323 ENUM Service" of [RFC3762]
1929 Security considerations:
1930 see section "5. Security Considerations" of [RFC3762]
1931 Intended usage: COMMON
1932 Author: Orit Levin
1933 [RFC3762]
1935 Service Name: "SIP"
1936 Type(s): "SIP"
1937 Subtype(s): N/A
1938 URI Scheme(s): "sip", "sips:"
1939 Functional Specification: see Section 4 of [RFC3764]
1940 Security considerations: see Section 6 of [RFC3764]
1941 Intended usage: COMMON
1942 Author: Jon Peterson (jon.peterson&neustar.biz)
1943 Any other information that the author deems interesting:
1944 see Section 3 of [RFC3764]
1945 [RFC3764]
1947 Service Name: "ifax"
1948 Type: "ifax"
1949 Subtype: "mailto"
1950 URI Scheme: "mailto"
1951 The URI Scheme is "mailto" because facsimile is a profile of
1952 standard Internet mail and uses standard Internet mail
1953 addressing.
1954 Functional Specification: see section 1 of [RFC4143]
1955 Security Considerations: see section 3 of [RFC4143]
1956 Intended usage: COMMON
1957 Author: Kiyoshi Toyoda(toyoda.kiyoshi&jp.panasonic.com)
1958 Dave Crocker(dcrocker&brandenburg.com)
1959 [RFC4143]
1961 Service Name: "pres"
1962 URI Scheme(s): "pres:"
1963 Functional Specification: see Section 4 of [RFC3953]
1964 Security considerations: see Section 6 of [RFC3953]
1965 Intended usage: COMMON
1966 Author: Jon Peterson (jon.peterson&neustar.biz)
1967 Any other information that the author deems interesting:
1968 See Section 3 of [RFC3953]
1969 [RFC3953]
1971 Service Name: "web"
1972 Type: "web"
1973 Subtype: "http"
1974 URI Scheme: 'http:'
1975 Functional Specification:
1976 This ENUMservice indicates that the resource identified by the
1977 associated URI scheme is capable of being a source of
1978 information. It has to be noted that the kind of information
1979 retrieved can be manifold. Usually, contacting a resource by an
1980 'http:' URI provides a document. This document can contain
1981 references that will trigger download of many different kinds
1982 of information, like audio or video or executable code. Thus,
1983 one can not be more specific about the kind of information that
1984 can be expected when contacting the resource.
1985 Security Considerations:
1986 See section 5 of [RFC4002].
1987 Intended Usage: COMMON
1988 Authors:
1989 Rudolf Brandner (rudolf.brandner&siemens.com)
1990 Lawrence Conroy (lwc&roke.co.uk)
1991 Richard Stastny (richard.stastny&oefeg.at)
1992 Any other information the author deems interesting: None
1993 [RFC4002]
1995 Service Name: "web"
1996 Type: "web"
1997 Subtype: "https"
1998 URI Scheme: 'https:'
1999 Functional Specification:
2000 This ENUMservice indicates that the resource identified by the
2001 associated URI scheme is capable of being a source of
2002 information, which can be contacted by using TLS or Secure
2003 Socket Layer protocol. It has to be noted that the kind of
2004 information retrieved can be manifold. Usually, contacting a
2005 resource by an 'https:' URI provides a document. This document
2006 can contain all different kind of information, like audio or
2007 video or executable code. Thus, one can not be more specific
2008 what information to expect when contacting the resource.
2009 Security Considerations:
2010 See section 5 of [RFC4002].
2011 Intended Usage: COMMON
2012 Authors:
2013 Rudolf Brandner (rudolf.brandner&siemens.com)
2014 Lawrence Conroy (lwc&roke.co.uk)
2015 Richard Stastny (richard.stastny&oefeg.at)
2016 Any other information the author deems interesting: None
2017 [RFC4002]
2019 Service Name: "ft"
2020 Type: "ft"
2021 Subtype: "ftp"
2022 URI Scheme: 'ftp:'
2023 Functional Specification:
2024 This ENUMservice indicates that the resource identified by the
2025 associated URI scheme is a file service from which a file or
2026 file listing can be retrieved.
2027 Security Considerations:
2028 See section 5 of [RFC4002].
2029 Intended Usage: COMMON
2030 Authors:
2031 Rudolf Brandner (rudolf.brandner&siemens.com)
2032 Lawrence Conroy (lwc&roke.co.uk)
2033 Richard Stastny (richard.stastny&oefeg.at)
2034 Any other information the author deems interesting: None
2035 [RFC4002]
2037 Enumservice Name: "email"
2038 Enumservice Type: "email"
2039 Enumservice Subtype: "mailto"
2040 URI Scheme: 'mailto:'
2041 Functional Specification:
2042 This Enumservice indicates that the remote resource can be
2043 addressed by the associated URI scheme in order to send an
2044 email.
2045 Security Considerations:
2046 See Section 6 of [RFC4355]
2047 Intended Usage: COMMON
2048 Authors:
2049 Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author
2050 contact detail see [RFC4355])
2051 Any other information the author deems interesting:
2052 None
2054 Enumservice Name: "fax"
2055 Enumservice Type: "fax"
2056 Enumservice Subtype: "tel"
2057 URI Scheme: 'tel:'
2058 Functional Specification:
2059 This Enumservice indicates that the resource identified by the
2060 associated URI scheme is capable of being contacted to provide
2061 a communication session during which facsimile documents can be
2062 sent.
2063 A client selecting this NAPTR will have support for generating
2064 and sending facsimile documents to the recipient using the PSTN
2065 session and transfer protocols specified in [12] and [13] in
2066 [RFC4355] - in short, they will have a fax
2067 program with a local or shared PSTN access over which they can
2068 send faxes.
2069 Security Considerations:
2070 See Section 6 of [RFC4355]
2071 Intended Usage: COMMON
2072 Authors:
2073 Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author
2074 contact detail see [RFC4355])
2075 Any other information the author deems interesting:
2076 None
2078 Enumservice Name: "sms"
2079 Enumservice Type: "sms"
2080 Enumservice Subtypes: "tel"
2081 URI Scheme: 'tel:'
2082 Functional Specification:
2083 This Enumservice indicates that the resource identified by the
2084 associated URI scheme is capable of receiving a message using
2085 the Short Message Service (SMS) [14] in [RFC4355].
2086 Security Considerations:
2087 There are no specific security issues with this Enumservice.
2088 However, the general considerations of Section 6 apply.
2089 Intended Usage: COMMON
2090 Authors:
2091 Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author
2092 contact detail see [RFC4355])
2093 Any other information the author deems interesting:
2094 None
2096 Enumservice Name: "sms"
2097 Enumservice Type: "sms"
2098 Enumservice Subtypes: "mailto"
2099 URI Scheme: 'mailto:'
2100 Functional Specification:
2101 This Enumservice indicates that the resource identified by the
2102 associated URI scheme is capable of receiving a message using
2103 an email protocol.
2104 SMS content is sent over SMTP using the format specified by TS
2105 23.140 [15] section 8.4.4 and TS 26.140 [16] section 4 (for
2106 references see [RFC4355]), as an MMS message. Within such a
2107 message, SMS content is carried as either a text or
2108 application/octet-stream MIME sub-part (see TS 26.140 [16] ,
2109 section 4.1)
2110 For references see [RFC4355].
2111 Security Considerations:
2112 There are no specific security issues with this Enumservice.
2113 However, the general considerations of Section 6 apply, see
2114 [RFC4355].
2116 Intended Usage: COMMON
2117 Authors:
2118 Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author
2119 contact detail see [RFC4355])
2120 Any other information the author deems interesting:
2121 None
2123 Enumservice Name: "ems"
2124 Enumservice Type: "ems"
2125 Enumservice Subtype: "tel"
2126 URI Scheme: 'tel:'
2127 Functional Specification:
2128 This Enumservice indicates that the resource identified by the
2129 associated URI scheme is capable of receiving a message using
2130 the Enhanced Message Service (EMS) [14] (For reference see
2131 [RFC4355]).
2132 Security Considerations:
2133 There are no specific security issues with this Enumservice.
2134 However, the general considerations of Section 6 apply.
2135 See [RFC4355]
2136 Intended Usage: COMMON
2137 Authors:
2138 Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author
2139 contact detail see [RFC4355])
2140 Any other information the author deems interesting:
2141 Note that an indication of EMS can be taken as implying that
2142 the recipient is capable of receiving SMS messages at this
2143 address as well.
2145 Enumservice Name: "ems"
2146 Enumservice Type: "ems"
2147 Enumservice Subtypes: "mailto"
2148 URI Scheme: 'mailto:'
2149 Functional Specification:
2150 This Enumservice indicates that the resource identified by the
2151 associated URI scheme is capable of receiving a message using
2152 an email protocol.
2153 EMS content is sent over SMTP using the format specified by TS
2154 23.140 [15] section 8.4.4 and TS 26.140 [16] section 4, as an
2155 MMS message. Within such a message, EMS content is carried as
2156 either a text or application/octet-stream MIME sub-part (see
2157 TS 26.140 [16] , section 4.1).
2158 For references see [RFC4355]
2159 Security Considerations:
2160 There are no specific security issues with this Enumservice.
2161 However, the general considerations of Section 6 of [RFC4355]
2162 apply.
2163 Intended Usage: COMMON
2164 Authors:
2165 Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author
2166 contact detail see [RFC4355])
2167 Any other information the author deems interesting:
2168 None
2170 Enumservice Name: "mms"
2171 Enumservice Type: "mms"
2172 Enumservice Subtype: "tel"
2173 URI Scheme: 'tel:'
2174 Functional Specification:
2175 This Enumservice indicates that the resource identified by the
2176 associated URI scheme is capable of receiving a message using
2177 the Multimedia Messaging Service (MMS) [15].
2178 For references see [RFC4355]
2179 Security Considerations:
2180 There are no specific security issues with this Enumservice.
2181 However, the general considerations of Section 6 of [RFC4355]
2182 apply.
2183 Intended Usage: COMMON
2184 Authors:
2185 Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author
2186 contact detail see [RFC4355])
2187 Any other information the author deems interesting:
2188 Note that MMS can be used as an alternative to deliver an SMS
2189 RP-DATA RPDU if, for example, the SMS bearer is not supported.
2190 If an entry includes this Enumservice, then in effect this can
2191 be taken as implying that the recipient is capable of receiving
2192 EMS or SMS messages at this address. Such choices on the end
2193 system design do have two small caveats; whilst in practice all
2194 terminals supporting MMS today support SMS as well, it might
2195 not necessarily be the case in the future, and there may be
2196 tariff differences in using the MMS rather than using the SMS
2197 or EMS.
2199 Enumservice Name: "mms"
2200 Enumservice Type: "mms"
2201 Enumservice Subtypes: "mailto"
2202 URI Scheme: 'mailto:'
2203 Functional Specification:
2204 This Enumservice indicates that the resource identified by the
2205 associated URI scheme is capable of receiving a message using
2206 an email protocol.
2207 MMS messages are sent over SMTP using the format specified by
2208 TS 23.140 [15] section 8.4.4 and TS 26.140 [16] section 4.
2209 Within and between MMS Environments (MMSE, network
2210 infrastructures that support the MultiMedia Service), other
2211 pieces of state data (for example, charging-significant
2212 information) are exchanged between MMS Relay Servers. Thus,
2213 although these servers use SMTP as the "bearer" for their
2214 application exchanges, they map their internal state to
2215 specialised headers carried in the SMTP message exchanges.
2216 The headers used in such MMSE are described in detail in [17].
2217 For references see [RFC4355]
2218 Security Considerations:
2219 There are no specific security issues with this Enumservice.
2220 However, the general considerations of Section 6 of [RFC4355]
2221 apply.
2222 Intended Usage: COMMON
2223 Authors:
2224 Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author
2225 contact detail see [RFC4355])
2226 Any other information the author deems interesting:
2227 The MMS Architecture describes an interface between the MMSE and
2228 "legacy messaging systems" (labelled as MM3) which accepts
2229 "standard" SMTP messages. Thus although the MMS Relay Server
2230 that supports this interface appears as a standard SMTP server
2231 from the perspective of an Internet-based mail server, it acts
2232 as a gateway and translator, adding the internal state data that
2233 is used within and between the MMS Environments. This mechanism
2234 is described in [17], which also includes references to the
2235 specifications agreed by those bodies responsible for the design
2236 of the MMS.
2238 Service Name: E.164 to VPIM MailTo: URL
2239 URI Type: "Mailto:"
2240 Type: VPIM
2241 Subtype: MAILTO
2242 Functional Specification: See section 4.2 through 4.4 of [RFC4238]
2243 Intended Usage: COMMON
2244 Author: Greg Vaudreuil (gregv&ieee.org)
2245 Error Conditions:
2246 o E.164 number not in the numbering plan
2247 o E.164 number in the numbering plan, but no URLs exist for that
2248 number
2249 o E2U+VPIM:Mailto Service unavailable
2250 Security Considerations:
2251 o Malicious Redirection
2252 One of the fundamental dangers related to any service such as
2253 this is that a malicious entry in a resolver's database will
2254 cause clients to resolve the E.164 into the wrong email URL.
2255 The possible intent may be to cause the client to send the
2256 information to an incorrect destination.
2257 o Denial of Service
2258 By removing the URL to which the E.164 maps, a malicious
2259 intruder may remove the client's ability to access the
2260 resource.
2261 o Unsolicited Bulk Email
2262 The exposure of email addresses through the ENUM
2263 service provides a bulk mailer access to large numbers
2264 of email addresses where only the telephone number was
2265 previously known.
2267 Service Name: E.164 to VPIM LDAP URL
2268 URI Type: "LDAP:"
2269 Type: VPIM
2270 Subtype: LDAP
2271 Functional Specification: See section 3.2 through 3.3 of [RFC4238]
2272 Intended Usage: COMMON
2273 Author: Greg Vaudreuil (gregv&ieee.org)
2274 Security Considerations:
2275 o Malicious Redirection
2276 One of the fundamental dangers related to any service
2277 such as this is that a malicious entry in a resolver's
2278 database will cause clients to resolve the E.164 into
2279 the wrong LDAP URL. The possible intent may be to cause
2280 the client to connect to a rogue LDAP server and
2281 retrieve (or fail to retrieve) a resource containing
2282 fraudulent or damaging information.
2283 o Denial of Service
2284 By removing the URL to which the E.164 maps, a
2285 malicious intruder may remove the client's ability to
2286 access the LDAP directory server.
2288 Enumservice Name: "voice"
2289 Enumservice Type: "voice"
2290 Enumservice Subtype: "tel"
2291 URI Scheme: 'tel:'
2292 Functional Specification:
2293 The kind of communication indicated by this Enumservice is
2294 "Interactive Voice". From a protocol perspective, this
2295 communication is expected to involve bidirectional media streams
2296 carrying audio data.
2297 A client may imply that the person controlling population of a
2298 NAPTR holding this Enumservice indicates their capability to
2299 engage in an interactive voice session when contacted using the
2300 URI generated by this NAPTR.
2301 Security Considerations:
2302 See Section 5 of [RFC4415]
2303 Intended Usage: COMMON
2304 Authors: Rudolf Brandner, Lawrence Conroy, Richard Stastny (for
2305 author contact detail see Authors' Addresses section)
2306 Any other information the author deems interesting:
2307 o This Enumservice indicates that the person responsible for the
2308 NAPTR is accessible via the PSTN (Public Switched Telephone
2309 Network) or PLMN (Public Land Mobile Network) using the value of
2310 the generated URI.
2311 o The kind of subsystem required to initiate a Voice Enumservice
2312 with this sub-type is a "Dialler". This is a subsystem that
2313 either provides a local connection to the PSTN or PLMN, or that
2314 provides an indirect connection to those networks. The
2315 subsystem will use the telephone number held in the generated
2316 URI to place a voice call. The voice call is placed to a
2317 network that uses E.164 numbers to route calls to an appropriate
2318 destination.
2319 o Note that the PSTN/PLMN connection may be indirect. The end
2320 user receiving this NAPTR may have a relationship with a
2321 Communications Service Provider that accepts call initiation
2322 requests from that subsystem using an IP-based protocol such as
2323 SIP or H.323, and places the call to the PSTN using a remote
2324 gateway service. In this case the Provider may either accept
2325 requests using "tel:" URIs or has a defined mechanism to convert
2326 "tel:" URI values into a "protocol-native" form.
2327 o The "tel:" URI value SHOULD be fully qualified (using the
2328 "global phone number" form of RFC3966 [10]). A "local phone
2329 number" as defined in that document SHOULD NOT be used unless
2330 the controller of the zone in which the NAPTR appears is sure
2331 that it can be distinguished unambiguously by all clients that
2332 can access the resource record and that a call from their
2333 network access points can be routed to that destination.
2335 Enumservice Name: "pstn"
2336 Enumservice Type: "pstn"
2337 Enumservice Subtype: "tel"
2338 URI Scheme: 'tel:'
2339 Functional Specification:
2340 These Enumservices indicate that the remote resource identified
2341 can be addressed by the associated URI scheme in order to
2342 initiate a telecommunication session, which may include two-way
2343 voice or other communications, to the PSTN. These URIs may
2344 contain number portability data as specified in RFC 4694 [10].
2345 Security Considerations: See Section 7 of [RFC4769].
2346 Intended Usage: COMMON
2347 Authors:
2348 Jason Livingood (jason_livingood&cable.comcast.com)
2349 Richard Shockey (richard.shockey&neustar.biz)
2350 Any other information the author deems interesting:
2351 A Number Portability Dip Indicator (npdi) should be used in
2352 practice (see examples below in Section 4 of [RFC4769]).
2354 Enumservice Name: "pstn"
2355 Enumservice Type: "pstn"
2356 Enumservice Subtype: "sip"
2357 URI Scheme: 'sip:'
2358 Functional Specification:
2359 These Enumservices indicate that the remote resource identified
2360 can be addressed by the associated URI scheme in order to
2361 initiate a telecommunication session, which may include two-way
2362 voice or other communications, to the PSTN.
2363 Security Considerations: See Section 7 of [RFC4769].
2364 Intended Usage: COMMON
2365 Authors:
2366 Jason Livingood (jason_livingood&cable.comcast.com)
2367 Richard Shockey (richard.shockey&neustar.biz)
2368 Any other information the author deems interesting:
2369 A Number Portability Dip Indicator (npdi) should be used in
2370 practice (see examples below in Section 4 of [RFC4769]).
2372 Enumservice Name: "vCard"
2373 Enumservice Name: "vCard"
2374 Enumservice Type: "vcard"
2375 Enumservice Subtype: n/a
2376 URI Schemes: "http", "https"
2377 Functional Specification:
2378 This Enumservice indicates that the resource identified is a
2379 plain vCard, according to RFC 2426, which may be accessed using
2380 HTTP/ HTTPS [7].
2381 Clients fetching the vCard from the resource indicated should
2382 expect access to be restricted. Additionally, the comprehension
2383 of the data provided may vary depending on the client's
2384 identity.
2385 Security Considerations: see Section 5 [RFC4969]
2386 Intended Usage: COMMON
2387 Author: Alexander Mayrhofer
2389 Enumservice Name: "XMPP"
2390 Enumservice Type: "xmpp"
2391 Enumservice Subtype: n/a
2392 URI Schemes: "xmpp"
2393 Functional Specification:
2394 This Enumservice indicates that the resource identified is an
2395 XMPP entity.
2396 Security Considerations: see Section 6 of [RFC4979]
2397 Intended Usage: COMMON
2398 Author: Alexander Mayrhofer
2400 Enumservice Name: "im"
2401 Enumservice Type: "im"
2402 Enumservice Subtypes: N/A
2403 URI scheme(s): "im:"
2404 Functional Specification:
2405 This Enumservice indicates that the resource identified
2406 is an 'im:' URI. The 'im:' URI scheme does not identify
2407 any particular protocol that will be used to handle
2408 instant messaging receipt or delivery, rather the mechanism
2409 in RFC 3861 [4] is used to discover whether an IM protocol
2410 supported by the party querying ENUM is also supported by
2411 the target resource.
2412 Security considerations: See section 3 of [RFC5028]
2413 Intended usage: COMMON
2414 Author: Rohan Mahy (rohan&ekabal.com)
2416 Enumservice Name: "voicemsg"
2417 Enumservice Type: "voicemsg"
2418 Enumservice Subtypes: "sip"
2419 URI Schemes: 'sip:'
2420 Functional Specification:
2421 This Enumservice indicates that the remote resource identified
2422 can be addressed by the associated URI scheme in order to
2423 initiate a voice communication session to a voice messaging
2424 system.
2425 Security Considerations: See Section 3 of [RFC5278]
2426 Intended Usage: COMMON
2427 Authors:
2428 Jason Livingood (jason_livingood&cable.comcast.com)
2429 Don Troshynski (dtroshynski&acmepacket.com)
2430 Any other information the author deems interesting:
2431 Implementers should review a non-exclusive list of examples
2432 below in Section 7 of [RFC5278]
2434 Enumservice Name: "voicemsg"
2435 Enumservice Type: "voicemsg"
2436 Enumservice Subtypes: "sips"
2437 URI Schemes: 'sips:'
2438 Functional Specification:
2439 This Enumservice indicates that the remote resource identified
2440 can be addressed by the associated URI scheme in order to
2441 initiate a voice communication session to a voice messaging
2442 system.
2443 Security Considerations: See Section 3 of [RFC5278]
2444 Intended Usage: COMMON
2445 Authors:
2446 Jason Livingood (jason_livingood&cable.comcast.com)
2447 Don Troshynski (dtroshynski&acmepacket.com)
2448 Any other information the author deems interesting:
2449 Implementers should review a non-exclusive list of examples
2450 below in Section 7 of [RFC5278]
2452 Enumservice Name: "voicemsg"
2453 Enumservice Type: "voicemsg"
2454 Enumservice Subtype: "tel"
2455 URI Schemes: 'tel:'
2456 Functional Specification:
2457 This Enumservice indicates that the remote resource identified
2458 can be addressed by the associated URI scheme in order to
2459 initiate a voice communication session to a voice messaging
2460 system.
2461 Security Considerations: See Section 3 of [RFC5278]
2462 Intended Usage: COMMON
2463 Authors:
2464 Jason Livingood (jason_livingood&cable.comcast.com)
2465 Don Troshynski (dtroshynski&acmepacket.com)
2466 Any other information the author deems interesting:
2467 Implementers should review a non-exclusive list of examples
2468 below in Section 7 of [RFC5278]
2470 Enumservice Name: "voicemsg"
2471 Enumservice Type: "voicemsg"
2472 Enumservice Subtype: "http"
2473 URI Schemes: 'http:'
2474 Functional Specification:
2475 This Enumservice indicates that the remote resource identified
2476 by the associated URI scheme is capable of being a source of
2477 information.
2478 Note that the kind of information retrieved can be manifold.
2479 Usually, contacting a resource by an 'http:' [11] URI provides a
2480 document. This document can contain references that will trigger
2481 the download of many different kinds of information, such as
2482 text, audio, video, executable code, or even voice message
2483 files. Thus, one cannot be more specific about the kind of
2484 information expected when contacting the resource.
2485 Security Considerations: See Section 3 of [RFC5278]
2486 Intended Usage: COMMON
2487 Authors:
2488 Jason Livingood (jason_livingood&cable.comcast.com)
2489 Don Troshynski (dtroshynski&acmepacket.com)
2490 Any other information the author deems interesting:
2491 Implementers should review a non-exclusive list of examples
2492 below in Section 7 of [RFC5278]
2494 Enumservice Name: "voicemsg"
2495 Enumservice Type: "voicemsg"
2496 Enumservice Subtype: "https"
2497 URI Schemes: 'https:'
2498 Functional Specification:
2499 This Enumservice indicates that the remote resource identified
2500 by the associated URI scheme is capable of being a source of
2501 information, which can be contacted using TLS or the Secure
2502 Socket Layer protocol.
2503 Note that the kind of information retrieved can be manifold.
2504 Usually, contacting a resource by an 'https:' [12] URI provides
2505 a document. This document can contain references that will
2506 trigger the download of many different kinds of information,
2507 such as text, audio, video, executable code, or even voice
2508 message files. Thus, one cannot be more specific about the kind
2509 of information expected when contacting the resource.
2510 Security Considerations: See Section 3 of [RFC5278]
2511 Intended Usage: COMMON
2512 Authors:
2513 Jason Livingood (jason_livingood&cable.comcast.com)
2514 Don Troshynski (dtroshynski&acmepacket.com)
2515 Any other information the author deems interesting:
2516 Implementers should review a non-exclusive list of examples
2517 below in Section 7 of [RFC5278]
2519 Enumservice Name: "videomsg"
2520 Enumservice Type: "videomsg"
2521 Enumservice Subtypes: "sip"
2522 URI Schemes: 'sip:'
2523 Functional Specification:
2524 This Enumservice indicates that the remote resource identified
2525 can be addressed by the associated URI scheme in order to
2526 initiate a video communication session to a video messaging
2527 system.
2528 Security Considerations: See Section 3 of [RFC5278]
2529 Intended Usage: COMMON
2530 Authors:
2531 Jason Livingood (jason_livingood&cable.comcast.com)
2532 Don Troshynski (dtroshynski&acmepacket.com)
2533 Any other information the author deems interesting:
2534 Implementers should review a non-exclusive list of examples
2535 below in Section 7 of [RFC5278]
2537 Enumservice Name: "videomsg"
2538 Enumservice Type: "videomsg"
2539 Enumservice Subtypes: "sips"
2540 URI Schemes: 'sips:'
2541 Functional Specification:
2542 This Enumservice indicates that the remote resource identified
2543 can be addressed by the associated URI scheme in order to
2544 initiate a video communication session to a video messaging
2545 system.
2546 Security Considerations: See Section 3 of [RFC5278]
2547 Intended Usage: COMMON
2548 Authors:
2549 Jason Livingood (jason_livingood&cable.comcast.com)
2550 Don Troshynski (dtroshynski&acmepacket.com)
2551 Any other information the author deems interesting:
2552 Implementers should review a non-exclusive list of examples
2553 below in Section 7 of [RFC5278]
2555 Enumservice Name: "videomsg"
2556 Enumservice Type: "videomsg"
2557 Enumservice Subtype: "http"
2558 URI Schemes: 'http:'
2559 Functional Specification:
2560 This Enumservice indicates that the remote resource identified
2561 by the associated URI scheme is capable of being a source of
2562 information.
2563 Note that the kind of information retrieved can be manifold.
2564 Usually, contacting a resource by an 'http:' [11] URI provides a
2565 document. This document can contain references that will trigger
2566 the download of many different kinds of information, such as
2567 text, audio, video, executable code, or even video message
2568 files. Thus, one cannot be more specific about the kind of
2569 information expected when contacting the resource.
2570 Security Considerations: See Section 3 of [RFC5278]
2571 Intended Usage: COMMON
2572 Authors:
2573 Jason Livingood (jason_livingood&cable.comcast.com)
2574 Don Troshynski (dtroshynski&acmepacket.com)
2575 Any other information the author deems interesting:
2576 Implementers should review a non-exclusive list of examples
2577 below in Section 7 of [RFC5278]
2579 Enumservice Name: "videomsg"
2580 Enumservice Type: "videomsg"
2581 Enumservice Subtype: "https"
2582 URI Schemes: 'https:'
2583 Functional Specification:
2584 This Enumservice indicates that the remote resource identified
2585 by the associated URI scheme is capable of being a source of
2586 information, which can be contacted using TLS or the Secure
2587 Socket Layer protocol.
2588 Note that the kind of information retrieved can be manifold.
2589 Usually, contacting a resource by an 'https:' [12] URI provides
2590 a document. This document can contain references that will
2591 trigger the download of many different kinds of information,
2592 such as text, audio, video, executable code, or even video
2593 message files. Thus, one cannot be more specific about the kind
2594 of information expected when contacting the resource.
2595 Security Considerations: See Section 3 of [RFC5278]
2596 Intended Usage: COMMON
2597 Authors:
2598 Jason Livingood (jason_livingood&cable.comcast.com)
2599 Don Troshynski (dtroshynski&acmepacket.com)
2600 Any other information the author deems interesting:
2601 Implementers should review a non-exclusive list of examples
2602 below in Section 7 of [RFC5278]
2604 Enumservice Name: "unifmsg"
2605 Enumservice Type: "unifmsg"
2606 Enumservice Subtypes: "sip"
2607 URI Schemes: 'sip:'
2608 Functional Specification:
2609 This Enumservice indicates that the remote resource identified
2610 can be addressed by the associated URI scheme in order to
2611 initiate a unified communication session to a unified messaging
2612 system.
2613 Security Considerations: See Section 3 of [RFC5278]
2614 Intended Usage: COMMON
2615 Authors:
2616 Jason Livingood (jason_livingood&cable.comcast.com)
2617 Don Troshynski (dtroshynski&acmepacket.com)
2618 Any other information the author deems interesting:
2619 Implementers should review a non-exclusive list of examples
2620 below in Section 7 of [RFC5278]
2622 Enumservice Name: "unifmsg"
2623 Enumservice Type: "unifmsg"
2624 Enumservice Subtypes: "sips"
2625 URI Schemes: 'sips:'
2626 Functional Specification:
2627 This Enumservice indicates that the remote resource identified
2628 can be addressed by the associated URI scheme in order to
2629 initiate a unified communication session to a unified messaging
2630 system.
2631 Security Considerations: See Section 3 of [RFC5278]
2632 Intended Usage: COMMON
2633 Authors:
2634 Jason Livingood (jason_livingood&cable.comcast.com)
2635 Any other information the author deems interesting:
2636 Implementers should review a non-exclusive list of examples
2637 below in Section 7 of [RFC5278]
2639 Enumservice Name: "unifmsg"
2640 Enumservice Type: "unifmsg"
2641 Enumservice Subtype: "http"
2642 URI Schemes: 'http:'
2643 Functional Specification:
2645 This Enumservice indicates that the remote resource identified
2646 by the associated URI scheme is capable of being a source of
2647 information.
2648 Note that the kind of information retrieved can be manifold.
2649 Usually, contacting a resource by an 'http:' [11] URI provides a
2650 document. This document can contain references that will trigger
2651 the download of many different kinds of information, such as
2652 text, audio, video, executable code, or even video message
2653 files. Thus, one cannot be more specific about the kind of
2654 information expected when contacting the resource.
2655 Security Considerations: See Section 3 of [RFC5278]
2656 Intended Usage: COMMON
2657 Authors:
2658 Jason Livingood (jason_livingood&cable.comcast.com)
2659 Don Troshynski (dtroshynski&acmepacket.com)
2660 Any other information the author deems interesting:
2661 Implementers should review a non-exclusive list of examples
2662 below in Section 7 of [RFC5278]
2664 Enumservice Name: "unifmsg"
2665 Enumservice Type: "unifmsg"
2666 Enumservice Subtype: "https"
2667 URI Schemes: 'https:'
2668 Functional Specification:
2669 This Enumservice indicates that the remote resource identified
2670 by the associated URI scheme is capable of being a source of
2671 information, which can be contacted using TLS or the Secure
2672 Socket Layer protocol.
2673 Note that the kind of information retrieved can be manifold.
2674 Usually, contacting a resource by an 'https:' [12] URI provides
2675 a document. This document can contain references that will
2676 trigger the download of many different kinds of information,
2677 such as text, audio, video, executable code, or even video
2678 message files. Thus, one cannot be more specific about the kind
2679 of information expected when contacting the resource.
2680 Security Considerations: See Section 3 of [RFC5278]
2681 Intended Usage: COMMON
2682 Authors:
2683 Jason Livingood (jason_livingood&cable.comcast.com)
2684 Don Troshynski (dtroshynski&acmepacket.com)
2685 Any other information the author deems interesting:
2686 Implementers should review a non-exclusive list of examples
2687 below in Section 7 of [RFC5278]
2689 Enumservice Name: "ical-sched"
2690 Enumservice Type: "ical-sched"
2691 Enumservice Subtypes: "mailto"
2692 URI scheme(s): 'mailto:'
2693 Functional Specification:
2694 This Enumservice indicates that the resource identified can be
2695 addressed by the associated URI used for scheduling using
2696 Internet calendaring via Internet mail with the iMIP [6]
2697 protocol.
2698 Security considerations: See Section 4 of [RFC5333].
2699 Intended usage: COMMON
2700 Author:
2701 Rohan Mahy (rohan&ekabal.com)
2703 Enumservice Name: "ical-access"
2704 Enumservice Type: "ical-access"
2705 Enumservice Subtypes: "http"
2706 URI scheme(s): 'http:'
2707 Functional Specification:
2708 This Enumservice indicates that the resource identified can be
2709 addressed by the associated URI in order to access a user's
2710 calendar (for example free/busy status) using the CalDAV [7]
2711 protocol for Internet calendaring.
2712 Security considerations: See Section 4 of [RFC5333].
2713 Intended usage: COMMON
2714 Author:
2715 Rohan Mahy (rohan&ekabal.com)
2717 Enumservice Name: "ical-access"
2718 Enumservice Type: "ical-access"
2719 Enumservice Subtypes: "https"
2720 URI scheme(s): 'https:'
2721 Functional Specification:
2722 This Enumservice indicates that the resource identified can be
2723 addressed by the associated URI in order to access a user's
2724 calendar (for example free/busy status) using the CalDAV [7]
2725 protocol for Internet calendaring.
2726 Security considerations: See Section 4 of [RFC5333].
2727 Intended usage: COMMON
2728 Author:
2729 Rohan Mahy (rohan&ekabal.com)
2731 Appendix B. Document Changelog
2733 [RFC Editor: This section is to be removed before publication]
2735 draft-ietf-enum-enumservices-transition-06:
2736 o bernie/alex: added "References are contained in..." in each XML
2737 chunk with references internal to the Enumservice specification
2738 (Alexey / Ari)
2740 o bernie/alex: Added sentence to clarify references in XML chunks
2741 o bernie: fixed multiple (separate elements) (Ari)
2742 o bernie: change back to Standards Track (IESG Request)
2744 draft-ietf-enum-enumservices-transition-05:
2745 o bernie: minor editorial (Feedback Alfred Hoenes)
2746 o bernie: updated my author's address (swisscom -> ucom.ch)
2747 o bernie: clarified IANA registration policy: "Specification
2748 Required", which implies "Expert Review", i.e. point to a single
2749 policy (Feedback Gonzalo Camarillo)
2751 draft-ietf-enum-enumservices-transition-04:
2752 o alex: changed vpim to data-type
2753 o alex: changed ical services to application-based, common
2754 o bernie: Upgraded remaining references from I-D to RFC 5333
2756 draft-ietf-enum-enumservices-transition-03:
2757 o bernie: Added fixed calendaring Enumservices (RFC 5333)
2758 o bernie: Updated my author's address
2759 o bernie: made own sub-section for each registration
2760 o bernie: Split XML Chunk section and IANA Considerations section
2761 o bernie: other editorial changes, e.g. existing -> legacy
2763 draft-ietf-enum-enumservices-transition-02:
2764 o bernie: Temporarily removed calendaring Enumservices (will be
2765 added again, once these are fixed)
2766 o bernie: added current state of IANA repository
2768 draft-ietf-enum-enumservices-transition-01:
2769 o bernie: Added 13 new Enumservices (RFC 5278)
2770 o bernie: Updated 'Open Issues' section
2771 o bernie: Updated ipr attribute to 'pre5378Trust200902' according to
2772 http://www.ietf.org/mail-archive/web/syslog/current/msg02333.html
2773 o alex: Added missing classifications
2774 o alex: Editorial improvements
2775 o bernie: More editorials
2776 o bernie: Changed status to bcp, to avoid downref problem with
2777 enumservice-guide
2778 o bernie: Rewrite of IESG Action
2780 draft-ietf-enum-enumservices-transition-00:
2781 o bernie: Updated affiliation: Switch -> Swisscom
2782 o bernie: Revised all Enumservices to the form of XML chunks
2783 o bernie: Added statement for IESG Actions to downgrade existing all
2784 Enumservice specifications
2785 o bernie: Updated 'Open Issues' section
2787 draft-hoeneisen-enum-enumservices-transition-01:
2789 o bernie: Fixed wrong reference
2791 draft-hoeneisen-enum-enumservices-transition-01:
2792 o bernie: integrated feedback from Alfred Hoenes
2793 * Typos / corrections
2794 * Removed the words "remote" and "scheme" in existing
2795 registrations
2796 * changed "URL" to "URI" in existing registrations
2797 * changed "headers" to "header fields" in existing "mms:mailto"
2798 registration
2799 o bernie: Added Acknowledgments section
2801 draft-hoeneisen-enum-enumservices-transition-00:
2802 o bernie: Initial version
2803 o bernie: Imported and adjusted existing IANA Enumservice
2804 registrations
2805 o bernie: Removed Name and added Class fields
2806 o bernie: Put caption to each Enumservice
2807 o bernie: Sorted alphabetically
2808 o bernie: All URI Schemes without colon
2809 o alex: Added classification
2811 Authors' Addresses
2813 Bernie Hoeneisen
2814 Ucom Standards Track Solutions Company
2815 CH-8049 Zuerich
2816 Switzerland
2818 Phone: +41 44 500 52 44
2819 Email: bernie@ietf.hoeneisen.ch (bernhard.hoeneisen AT ucom.ch)
2820 URI: http://www.ucom.ch/
2822 Alexander Mayrhofer
2823 enum.at GmbH
2824 Karlsplatz 1/9
2825 Wien A-1010
2826 Austria
2828 Phone: +43 1 5056416 34
2829 Email: alexander.mayrhofer@enum.at
2830 URI: http://www.enum.at/