[要約] RFC 6118は、Enumservicesの遺産的なIANA登録の更新に関するものであり、Enumservicesの登録情報を最新化することを目的としています。
Internet Engineering Task Force (IETF) B. Hoeneisen
Request for Comments: 6118 Ucom.ch
Updates: 3762, 3764, 3953, 4143, 4002, A. Mayrhofer
4238, 4355, 4415, 4769, 4969, enum.at
4979, 5028, 5278, 5333 March 2011
Category: Standards Track
ISSN: 2070-1721
Update of Legacy IANA Registrations of Enumservices
EnumservicesのレガシーIANA登録の更新
Abstract
概要
This document revises all Enumservices that were IANA registered under the now obsolete specification of the Enumservice registry defined in RFC 3761.
このドキュメントは、RFC 3761で定義されているEnumserviceレジストリの現在廃止された仕様に基づいて登録されているIANAに登録されているすべてのEnumservicesを修正します。
Status of This Memo
本文書の位置付け
This is an Internet Standards Track document.
これは、インターネット標準トラックドキュメントです。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
このドキュメントは、インターネットエンジニアリングタスクフォース（IETF）の製品です。IETFコミュニティのコンセンサスを表しています。公開レビューを受けており、インターネットエンジニアリングステアリンググループ（IESG）からの出版が承認されています。インターネット標準の詳細については、RFC 5741のセクション2で入手できます。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6118.
このドキュメントの現在のステータス、任意のERRATA、およびそのフィードバックを提供する方法に関する情報は、http：//www.rfc-editor.org/info/rfc6118で取得できます。
Copyright Notice
著作権表示
Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.
Copyright（c）2011 IETF Trustおよび文書著者として特定された人。全著作権所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
このドキュメントは、BCP 78およびIETFドキュメント（http://trustee.ietf.org/license-info）に関連するIETF Trustの法的規定の対象となります。この文書に関するあなたの権利と制限を説明するので、これらの文書を注意深く確認してください。このドキュメントから抽出されたコードコンポーネントには、セクション4.Eで説明されている法的規定のセクション4.Eで説明されており、単純化されたBSDライセンスで説明されているように保証なしで提供される簡略化されたBSDライセンステキストを含める必要があります。
This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.
このドキュメントには、2008年11月10日までに公開または公開されたIETFドキュメントまたはIETFの寄付からの資料が含まれている場合があります。IETF標準プロセスの外。そのような資料の著作権を制御する人から適切なライセンスを取得せずに、このドキュメントはIETF標準プロセスの外側に変更されない場合があり、その派生作業は、ITF標準プロセスの外側で作成されない場合があります。RFCとしての出版またはそれを英語以外の言語に翻訳するため。
Table of Contents
目次
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. IESG Action . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Legacy Enumservice Registrations Converted to XML Chunks . . . 5
4.1. email:mailto . . . . . . . . . . . . . . . . . . . . . . . 6
4.2. ems:mailto . . . . . . . . . . . . . . . . . . . . . . . . 7
4.3. ems:tel . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.4. fax:tel . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.5. ft:ftp . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.6. h323 . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.7. ical-access:http . . . . . . . . . . . . . . . . . . . . . 12
4.8. ical-access:https . . . . . . . . . . . . . . . . . . . . 13
4.9. ical-sched:mailto . . . . . . . . . . . . . . . . . . . . 14
4.10. ifax:mailto . . . . . . . . . . . . . . . . . . . . . . . 15
4.11. im . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.12. mms:mailto . . . . . . . . . . . . . . . . . . . . . . . . 17
4.13. mms:tel . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.14. pres . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.15. pstn:sip . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.16. pstn:tel . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.17. sip . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.18. sms:mailto . . . . . . . . . . . . . . . . . . . . . . . . 24
4.19. sms:tel . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.20. unifmsg:http . . . . . . . . . . . . . . . . . . . . . . . 26
4.21. unifmsg:https . . . . . . . . . . . . . . . . . . . . . . 27
4.22. unifmsg:sip . . . . . . . . . . . . . . . . . . . . . . . 28
4.23. unifmsg:sips . . . . . . . . . . . . . . . . . . . . . . . 29
4.24. vcard . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.25. videomsg:http . . . . . . . . . . . . . . . . . . . . . . 31
4.26. videomsg:https . . . . . . . . . . . . . . . . . . . . . . 32
4.27. videomsg:sip . . . . . . . . . . . . . . . . . . . . . . . 33
4.28. videomsg:sips . . . . . . . . . . . . . . . . . . . . . . 34
4.29. voice:tel . . . . . . . . . . . . . . . . . . . . . . . . 35
4.30. voicemsg:http . . . . . . . . . . . . . . . . . . . . . . 37
4.31. voicemsg:https . . . . . . . . . . . . . . . . . . . . . . 38
4.32. voicemsg:sip . . . . . . . . . . . . . . . . . . . . . . . 39
4.33. voicemsg:sips . . . . . . . . . . . . . . . . . . . . . . 40
4.34. voicemsg:tel . . . . . . . . . . . . . . . . . . . . . . . 41
4.35. vpim:ldap . . . . . . . . . . . . . . . . . . . . . . . . 42
4.36. vpim:mailto . . . . . . . . . . . . . . . . . . . . . . . 43
4.37. web:http . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.38. web:https . . . . . . . . . . . . . . . . . . . . . . . . 46
4.39. xmpp . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 47
6. Security Considerations . . . . . . . . . . . . . . . . . . . 47
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 47
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 48
8.1. Normative References . . . . . . . . . . . . . . . . . . . 48
8.2. Informative References . . . . . . . . . . . . . . . . . . 49
Appendix A. Former Content of the IANA Repository . . . . . . . . 49
[RFC6117] has obsoleted the IANA registration section of [RFC3761]. Since the IANA Enumservice registry contains various Enumservices registered under the regime of RFC 3761, those registrations do not conform to the new guidelines as specified in [RFC6117]. To ensure consistency among all Enumservice registrations at IANA, this document adds the (nowadays) missing elements to those legacy registrations. Furthermore, all legacy Enumservice registrations are converted to the new XML-chunk format, and, where deemed necessary, minor editorial corrections are applied.
[RFC6117]は、[RFC3761]のIANA登録セクションを廃止しました。IANA Enumserviceレジストリには、RFC 3761の制度に登録されているさまざまなencresvicesが含まれているため、これらの登録は[RFC6117]で指定されているように新しいガイドラインに準拠していません。IANAのすべてのEnumservice登録間の一貫性を確保するために、このドキュメントは、これらのレガシー登録に（最近の）欠落要素を追加します。さらに、すべてのLegacy Enumservice登録は新しいXML-Chunk形式に変換され、必要と思われる場合、マイナーな編集修正が適用されます。
However, this document only adds the missing elements to the XML chunks as specified in the IANA Considerations section of [RFC6117], but it does not complete the (nowadays) missing sections of the corresponding Enumservice Specifications. In order to conform with the new registration regime as specified in [RFC6117], those Enumservice Specifications still have to be revised.
ただし、このドキュメントは、[RFC6117]のIANA考慮事項セクションで指定されているように、欠落している要素をXMLチャンクに追加するだけですが、対応するEnamservice仕様の（最近の）欠落セクションは完了しません。[RFC6117]で指定されている新しい登録制度に準拠するためには、これらのEnumservice仕様を改訂する必要があります。
It is important to note that this document does not update the functional specification of the concerned Enumservices.
このドキュメントでは、関係するエンスムサービスの機能的な仕様を更新しないことに注意することが重要です。
The following RFCs are updated by this document:
次のRFCは、このドキュメントで更新されます。
o [RFC3762]
o [RFC3764]
o [RFC3953]
o [RFC4143]
o [RFC4002]
o [RFC4238]
o [RFC4355]
o [RFC4415]
o [RFC4769]
o [RFC4969]
o [RFC4979]
o [RFC5028]
o [RFC5278]
o [RFC5333]
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
この文書のキーワード "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", および "OPTIONAL" はRFC 2119 [RFC2119]で説明されているように解釈されます。
According to [RFC3761], any Enumservice registration had to be published as a Standards Track, Experimental, or BCP (Best Current Practice) RFC. [RFC6117] no longer has this requirement, i.e., "Specification Required", which implies the use of a Designated Expert [RFC5226], is sufficient.
[RFC3761]によると、Enumservice登録は、標準トラック、実験、またはBCP（最新の実践）RFCとして公開する必要がありました。[RFC6117]は、この要件、つまり、指定された専門家[RFC5226]の使用を暗示する「仕様が必要」という要件はもうありません。
This document changes the approval requirement for updates to Enumservice registrations to Specification Required, whereby the specification and request are reviewed by a Designated Expert as described in [RFC6117].
このドキュメントは、[RFC6117]に記載されているように、指定された専門家によって仕様と要求がレビューされるため、必要な仕様への登録登録への更新の承認要件を変更します。
In the following, the legacy Enumservice Registrations are converted to XML chunks that include the new elements introduced by [RFC6117].
以下では、[RFC6117]によって導入された新しい要素を含むXMLチャンクに変換されます。
(Note that references in Sections 4.1 - 4.39 refer to the references section within the respective Enumservice Specification.)
（セクション4.1-4.39の参照は、それぞれのEnumservice仕様内の参照セクションを参照してください。）
<record>
<!-- email:mailto -->
<class>Application-Based, Common</class>
<type>email</type>
<subtype>mailto</subtype>
<urischeme>mailto</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource can be
addressed by the associated URI in order to send an
email.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc4355"/>, Section 6.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc4355"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Rudolf_Brandner"/>
<xref type="person" data="Lawrence_Conroy"/>
<xref type="person" data="Richard_Stastny"/>
</requesters>
</record>
<record>
<!-- ems:mailto -->
<class>Application-Based, Common</class>
<type>ems</type>
<subtype>mailto</subtype>
<urischeme>mailto</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource
identified by the associated URI is capable
of receiving a message using an email protocol.
</paragraph>
<paragraph>
EMS content is sent over SMTP using the format
specified by TS 23.140 [15] Section 8.4.4 and TS
26.140 [16] Section 4, as an MMS message. Within
such a message, EMS content is carried as either a
text or application/octet-stream MIME sub-part (see
TS 26.140 [16], Section 4.1).
</paragraph>
<paragraph>
References are contained in <xref type="rfc" data="rfc4355"/>.
</paragraph>
</functionalspec>
<security>
<paragraph>
There are no specific security issues with this
Enumservice. However, the general considerations of
Section 6 of <xref type="rfc" data="rfc4355"/> apply.
</paragraph>
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc4355"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Rudolf_Brandner"/>
<xref type="person" data="Lawrence_Conroy"/>
<xref type="person" data="Richard_Stastny"/>
</requesters>
</record>
<record>
<!-- ems:tel -->
<class>Application-Based, Common</class>
<type>ems</type>
<subtype>tel</subtype>
<urischeme>tel</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource
identified by the associated URI is capable
of receiving a message using the Enhanced Message
Service (EMS) [14].
</paragraph>
<paragraph>
References are contained in <xref type="rfc" data="rfc4355"/>.
</paragraph>
</functionalspec>
<security>
<paragraph>
There are no specific security issues with this
Enumservice. However, the general considerations of
Section 6 of <xref type="rfc" data="rfc4355"/> apply.
</paragraph>
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc4355"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Rudolf_Brandner"/>
<xref type="person" data="Lawrence_Conroy"/>
<xref type="person" data="Richard_Stastny"/>
</requesters>
<additionalinfo>
<paragraph>
Note that an indication of EMS can be taken as
implying that the recipient is capable of receiving
SMS messages at this address as well.
</paragraph>
</additionalinfo>
</record>
<record>
<!-- fax:tel -->
<class>Application-Based, Subset</class>
<type>fax</type>
<subtype>tel</subtype>
<urischeme>tel</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource
identified by the associated URI is capable
of being contacted to provide a communication
session during which facsimile documents can be
sent.
</paragraph>
<paragraph>
A client selecting this NAPTR will have support
for generating and sending facsimile documents to
the recipient using the PSTN session and transfer
protocols specified in [12] and [13] in
<xref type="rfc" data="rfc4355"/> -
in short, they will have a fax program with a local
or shared PSTN access over which they can send
faxes.
</paragraph>
<paragraph>
References are contained in <xref type="rfc" data="rfc4355"/>.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc4355"/>, Section 6.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc4355"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Rudolf_Brandner"/>
<xref type="person" data="Lawrence_Conroy"/>
<xref type="person" data="Richard_Stastny"/>
</requesters>
</record>
<record>
<!-- ft:ftp -->
<class>Application-Based, Subset</class>
<type>ft</type>
<subtype>ftp</subtype>
<urischeme>ftp</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource
identified by the associated URI is a file
service from which a file or file listing can be
retrieved.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc4002"/>, Section 5.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc4002"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Rudolf_Brandner"/>
<xref type="person" data="Lawrence_Conroy"/>
<xref type="person" data="Richard_Stastny"/>
</requesters>
</record>
<record>
<!-- h323 -->
<class>Protocol-Based</class>
<type>h323</type>
<!-- No subtype -->
<urischeme>h323</urischeme>
<functionalspec>
See <xref type="rfc" data="rfc3762"/>, Section 3.
</functionalspec>
<security>
See <xref type="rfc" data="rfc3762"/>, Section 5.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc3762"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Orit_Levin"/>
</requesters>
</record>
<record>
<!-- ical-access:http -->
<class>Application-Based, Common</class>
<type>ical-access</type>
<subtype>http</subtype>
<urischeme>http</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource identified
can be addressed by the associated URI in order to access
a user's calendar (for example free/busy status) using
the CalDAV [7] protocol for Internet calendaring.
</paragraph>
<paragraph>
References are contained in <xref type="rfc" data="rfc5333"/>.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc5333"/>, Section 4.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc5333"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Rohan_Mahy"/>
</requesters>
</record>
<record>
<!-- ical-access:https -->
<class>Application-Based, Common</class>
<type>ical-access</type>
<subtype>https</subtype>
<urischeme>https</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource identified
can be addressed by the associated URI in order to access
a user's calendar (for example free/busy status) using
the CalDAV [7] protocol for Internet calendaring.
</paragraph>
<paragraph>
References are contained in <xref type="rfc" data="rfc5333"/>.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc5333"/>, Section 4.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc5333"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Rohan_Mahy"/>
</requesters>
</record>
<record>
<!-- ical-sched:mailto -->
<class>Application-Based, Common</class>
<type>ical-sched</type>
<subtype>mailto</subtype>
<urischeme>mailto</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource identified
can be addressed by the associated URI used for
scheduling using Internet calendaring via Internet mail
with the iMIP [6] protocol.
</paragraph>
<paragraph>
References are contained in <xref type="rfc" data="rfc5333"/>.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc5333"/>, Section 4.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc5333"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Rohan_Mahy"/>
</requesters>
</record>
<record>
<!-- ifax:mailto -->
<class>Application-Based, Subset</class>
<type>ifax</type>
<subtype>mailto</subtype>
<urischeme>mailto</urischeme>
<functionalspec>
See <xref type="rfc" data="rfc4143"/>, Section 1.
</functionalspec>
<security>
See <xref type="rfc" data="rfc4143"/>, Section 3.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc4143"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Kiyoshi_Toyoda"/>
<xref type="person" data="Dave_Crocker"/>
</requesters>
<additionalinfo>
<paragraph>
The URI Scheme is 'mailto' because facsimile is a
profile of standard Internet mail and uses standard
Internet mail addressing.
</paragraph>
</additionalinfo>
</record>
<record>
<!-- im -->
<class>Application-Based, Common</class>
<type>im</type>
<!-- No subtype -->
<urischeme>im</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource
identified is an 'im:' URI. The 'im:' URI scheme
does not identify any particular protocol that will
be used to handle instant messaging receipt or
delivery, rather the mechanism in RFC 3861 [4] is
used to discover whether an IM protocol supported by
the party querying ENUM is also supported by the
target resource.
</paragraph>
<paragraph>
References are contained in <xref type="rfc" data="rfc5028"/>.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc5028"/>, Section 3.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc5028"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Rohan_Mahy"/>
</requesters>
</record>
<record>
<!-- mms:mailto -->
<class>Application-Based, Common</class>
<type>mms</type>
<subtype>mailto</subtype>
<urischeme>mailto</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource
identified by the associated URI is capable
of receiving a message using an email protocol.
</paragraph>
<paragraph>
MMS messages are sent over SMTP using the format
specified by TS 23.140 [15] Section 8.4.4 and TS
26.140 [16] Section 4.
</paragraph>
<paragraph>
Within and between MMS Environments (MMSE,
network infrastructures that support the MultiMedia
Service), other pieces of state data (for example,
charging-significant information) are exchanged
between MMS Relay Servers. Thus, although these
servers use SMTP as the "bearer" for their
application exchanges, they map their internal state
to specialized header fields carried in the SMTP message
exchanges. The header fields used in such MMSE are
described in detail in [17].
</paragraph>
<paragraph>
References are contained in <xref type="rfc" data="rfc4355"/>.
</paragraph>
</functionalspec>
<security>
<paragraph>
There are no specific security issues with this
Enumservice. However, the general considerations of
Section 6 of <xref type="rfc" data="rfc4355"/> apply.
</paragraph>
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc4355"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Rudolf_Brandner"/>
<xref type="person" data="Lawrence_Conroy"/>
<xref type="person" data="Richard_Stastny"/>
</requesters>
<additionalinfo>
<paragraph>
The MMS Architecture describes an interface
between the MMSE and "legacy messaging systems"
(labelled as MM3) that accepts "standard" SMTP
messages. Thus, although the MMS Relay Server that
supports this interface appears as a standard SMTP
server from the perspective of an Internet-based
mail server, it acts as a gateway and translator,
adding the internal state data that is used within
and between the MMS Environments. This mechanism is
described in [17], which also includes references to
the specifications agreed by those bodies
responsible for the design of the MMS.
</paragraph>
<paragraph>
References are contained in <xref type="rfc" data="rfc4355"/>.
</paragraph>
</additionalinfo>
</record>
<record>
<!-- mms:tel -->
<class>Application-Based, Common</class>
<type>mms</type>
<subtype>tel</subtype>
<urischeme>tel</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource
identified by the associated URI is capable
of receiving a message using the Multimedia
Messaging Service (MMS) [15].
</paragraph>
<paragraph>
References are contained in <xref type="rfc" data="rfc4355"/>.
</paragraph>
</functionalspec>
<security>
<paragraph>
There are no specific security issues with this
Enumservice. However, the general considerations of
Section 6 of <xref type="rfc" data="rfc4355"/> apply.
</paragraph>
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc4355"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Rudolf_Brandner"/>
<xref type="person" data="Lawrence_Conroy"/>
<xref type="person" data="Richard_Stastny"/>
</requesters>
<additionalinfo>
<paragraph>
Note that MMS can be used as an alternative to
deliver an SMS RP-DATA RPDU if, for example, the
SMS bearer is not supported. If an entry includes
this Enumservice, then in effect this can be taken
as implying that the recipient is capable of
receiving EMS or SMS messages at this address. Such
choices on the end system design do have two small
caveats; whilst in practice all terminals supporting
MMS today support SMS as well, it might not
necessarily be the case in the future, and there may
be tariff differences in using the MMS rather than
using the SMS or EMS.
</paragraph>
</additionalinfo>
</record>
<record>
<!-- pres -->
<class>Application-Based, Common</class>
<type>pres</type>
<!-- No subtype -->
<urischeme>pres</urischeme>
<functionalspec>
See <xref type="rfc" data="rfc3953"/>, Section 4.
</functionalspec>
<security>
See <xref type="rfc" data="rfc3953"/>, Section 6.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc3953"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Jon_Peterson"/>
</requesters>
<additionalinfo>
<paragraph>
See <xref type="rfc" data="rfc3953"/>, Section 3.
</paragraph>
</additionalinfo>
</record>
<record>
<!-- pstn:sip -->
<class>Application-Based, Common</class>
<type>pstn</type>
<subtype>sip</subtype>
<urischeme>sip</urischeme>
<functionalspec>
<paragraph>
These Enumservices indicate that the
resource identified can be addressed by the
associated URI in order to initiate a
telecommunication session, which may include two-way
voice or other communications, to the PSTN.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc4769"/>, Section 7.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc4769"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Jason_Livingood"/>
<xref type="person" data="Richard_Shockey"/>
</requesters>
<additionalinfo>
<paragraph>
A Number Portability Dip Indicator (npdi) should
be used in practice
(see <xref type="rfc" data="rfc4769"/>, Section 4).
</paragraph>
</additionalinfo>
</record>
<record>
<!-- pstn:tel -->
<class>Application-Based, Ancillary</class>
<type>pstn</type>
<subtype>tel</subtype>
<urischeme>tel</urischeme>
<functionalspec>
<paragraph>
These Enumservices indicate that the
resource identified can be addressed by the
associated URI in order to initiate a
telecommunication session, which may include two-way
voice or other communications, to the PSTN. These
URIs may contain number portability data as
specified in RFC4694 [10].
</paragraph>
<paragraph>
References are contained in <xref type="rfc" data="rfc4769"/>.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc4769"/>, Section 7.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc4769"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Jason_Livingood"/>
<xref type="person" data="Richard_Shockey"/>
</requesters>
<additionalinfo>
<paragraph>
A Number Portability Dip Indicator (npdi) should
be used in practice
(see <xref type="rfc" data="rfc4769"/>, Section 4).
</paragraph>
</additionalinfo>
</record>
<record>
<!-- sip -->
<class>Protocol-Based</class>
<type>sip</type>
<!-- No subtype -->
<urischeme>sip</urischeme>
<urischeme>sips</urischeme>
<functionalspec>
See <xref type="rfc" data="rfc3764"/>, Section 4.
</functionalspec>
<security>
See <xref type="rfc" data="rfc3764"/>, Section 6.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc3764"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Jon_Peterson"/>
</requesters>
<additionalinfo>
<paragraph>
See <xref type="rfc" data="rfc3764"/>, Section 3.
</paragraph>
</additionalinfo>
</record>
<record>
<!-- sms:mailto -->
<class>Application-Based, Common</class>
<type>sms</type>
<subtype>mailto</subtype>
<urischeme>mailto</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource
identified by the associated URI is capable
of receiving a message using an email protocol.
</paragraph>
<paragraph>
SMS content is sent over SMTP using the format
specified by TS 23.140 [15] Section 8.4.4 and TS
26.140 [16] Section 4, as an MMS message. Within
such a message, SMS content is carried as either a
text or application/octet-stream MIME sub-part (see
TS 26.140 [16], Section 4.1)
</paragraph>
<paragraph>
References are contained in <xref type="rfc" data="rfc4355"/>.
</paragraph>
</functionalspec>
<security>
<paragraph>
There are no specific security issues with this
Enumservice. However, the general considerations of
Section 6 of <xref type="rfc" data="rfc4355"/> apply.
</paragraph>
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc4355"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Rudolf_Brandner"/>
<xref type="person" data="Lawrence_Conroy"/>
<xref type="person" data="Richard_Stastny"/>
</requesters>
</record>
<record>
<!-- sms:tel -->
<class>Application-Based, Common</class>
<type>sms</type>
<subtype>tel</subtype>
<urischeme>tel</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource
identified by the associated URI is capable
of receiving a message using the Short Message
Service (SMS) [14].
</paragraph>
<paragraph>
References are contained in <xref type="rfc" data="rfc4355"/>.
</paragraph>
</functionalspec>
<security>
<paragraph>
There are no specific security issues with this
Enumservice. However, the general considerations of
Section 6 of <xref type="rfc" data="rfc4355"/> apply.
</paragraph>
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc4355"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Rudolf_Brandner"/>
<xref type="person" data="Lawrence_Conroy"/>
<xref type="person" data="Richard_Stastny"/>
</requesters>
</record>
<record>
<!-- unifmsg:http -->
<class>Application-Based, Common</class>
<type>unifmsg</type>
<subtype>http</subtype>
<urischeme>http</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource identified by
the associated URI scheme is capable of being a source of
information.
</paragraph>
<paragraph>
Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'http:' [11] URI
provides a document. This document can contain references
that will trigger the download of many different kinds of
information, such as text, audio, video, executable code, or
even video message files. Thus, one cannot be more specific
about the kind of information expected when contacting the
resource.
</paragraph>
<paragraph>
References are contained in <xref type="rfc" data="rfc5278"/>.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc5278"/>, Section 3.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc5278"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Jason_Livingood"/>
<xref type="person" data="Don_Troshynski"/>
</requesters>
<additionalinfo>
<paragraph>
Implementers should review a non-exclusive list of examples
in Section 7 of <xref type="rfc" data="rfc5278"/>.
</paragraph>
</additionalinfo>
</record>
<record>
<!-- unifmsg:https -->
<class>Application-Based, Common</class>
<type>unifmsg</type>
<subtype>https</subtype>
<urischeme>https</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource identified by
the associated URI scheme is capable of being a source of
information, which can be contacted using TLS or the Secure
Socket Layer protocol.
</paragraph>
<paragraph>
Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'https:' [12] URI
provides a document. This document can contain references
that will trigger the download of many different kinds of
information, such as text, audio, video, executable code, or
even video message files. Thus, one cannot be more specific
about the kind of information expected when contacting the
resource.
</paragraph>
<paragraph>
References are contained in <xref type="rfc" data="rfc5278"/>.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc5278"/>, Section 3.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc5278"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Jason_Livingood"/>
<xref type="person" data="Don_Troshynski"/>
</requesters>
<additionalinfo>
<paragraph>
Implementers should review a non-exclusive list of examples
in Section 7 of <xref type="rfc" data="rfc5278"/>.
</paragraph>
</additionalinfo>
</record>
<record>
<!-- unifmsg:sip -->
<class>Application-Based, Common</class>
<type>unifmsg</type>
<subtype>sip</subtype>
<urischeme>sip</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource identified can
be addressed by the associated URI scheme in order to
initiate a unified communication session to a unified
messaging system.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc5278"/>, Section 3.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc5278"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Jason_Livingood"/>
<xref type="person" data="Don_Troshynski"/>
</requesters>
<additionalinfo>
<paragraph>
Implementers should review a non-exclusive list of examples
in Section 7 of <xref type="rfc" data="rfc5278"/>.
</paragraph>
</additionalinfo>
</record>
<record>
<!-- unifmsg:sips -->
<class>Application-Based, Common</class>
<type>unifmsg</type>
<subtype>sips</subtype>
<urischeme>sips</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource identified can
be addressed by the associated URI scheme in order to
initiate a unified communication session to a unified
messaging system.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc5278"/>, Section 3.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc5278"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Jason_Livingood"/>
<xref type="person" data="Don_Troshynski"/>
</requesters>
<additionalinfo>
<paragraph>
Implementers should review a non-exclusive list of examples
in Section 7 of <xref type="rfc" data="rfc5278"/>.
</paragraph>
</additionalinfo>
</record>
<record>
<!-- vcard -->
<class>Data Type-Based</class>
<type>vcard</type>
<!-- No subtype -->
<urischeme>http</urischeme>
<urischeme>https</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource
identified is a plain vCard, according to RFC2426,
which may be accessed using HTTP / HTTPS [7].
</paragraph>
<paragraph>
Clients fetching the vCard from the resource
indicated should expect access to be
restricted. Additionally, the comprehension of the
data provided may vary depending on the client's
identity.
</paragraph>
<paragraph>
References are contained in <xref type="rfc" data="rfc4969"/>.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc4969"/>, Section 5.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc4969"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Alexander_Mayrhofer"/>
</requesters>
</record>
<record>
<!-- videomsg:http -->
<class>Application-Based, Common</class>
<type>videomsg</type>
<subtype>http</subtype>
<urischeme>http</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource identified by
the associated URI scheme is capable of being a source of
information.
</paragraph>
<paragraph>
Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'http:' [11] URI
provides a document. This document can contain references
that will trigger the download of many different kinds of
information, such as text, audio, video, executable code, or
even video message files. Thus, one cannot be more specific
about the kind of information expected when contacting the
resource.
</paragraph>
<paragraph>
References are contained in <xref type="rfc" data="rfc5278"/>.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc5278"/>, Section 3.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc5278"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Jason_Livingood"/>
<xref type="person" data="Don_Troshynski"/>
</requesters>
<additionalinfo>
<paragraph>
Implementers should review a non-exclusive list of examples
in Section 7 of <xref type="rfc" data="rfc5278"/>.
</paragraph>
</additionalinfo>
</record>
<record>
<!-- videomsg:https -->
<class>Application-Based, Common</class>
<type>videomsg</type>
<subtype>https</subtype>
<urischeme>https</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource identified by
the associated URI scheme is capable of being a source of
information, which can be contacted using TLS or the Secure
Socket Layer protocol.
</paragraph>
<paragraph>
Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'https:' [12] URI
provides a document. This document can contain references
that will trigger the download of many different kinds of
information, such as text, audio, video, executable code, or
even video message files. Thus, one cannot be more specific
about the kind of information expected when contacting the
resource.
</paragraph>
<paragraph>
References are contained in <xref type="rfc" data="rfc5278"/>.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc5278"/>, Section 3.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc5278"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Jason_Livingood"/>
<xref type="person" data="Don_Troshynski"/>
</requesters>
<additionalinfo>
<paragraph>
Implementers should review a non-exclusive list of examples
in Section 7 of <xref type="rfc" data="rfc5278"/>.
</paragraph>
</additionalinfo>
</record>
<record>
<!-- videomsg:sip -->
<class>Application-Based, Common</class>
<type>videomsg</type>
<subtype>sip</subtype>
<urischeme>sip</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource identified can
be addressed by the associated URI scheme in order to
initiate a video communication session to a video messaging
system.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc5278"/>, Section 3.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc5278"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Jason_Livingood"/>
<xref type="person" data="Don_Troshynski"/>
</requesters>
<additionalinfo>
<paragraph>
Implementers should review a non-exclusive list of examples
in Section 7 of <xref type="rfc" data="rfc5278"/>.
</paragraph>
</additionalinfo>
</record>
<record>
<!-- videomsg:sips -->
<class>Application-Based, Common</class>
<type>videomsg</type>
<subtype>sips</subtype>
<urischeme>sips</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource identified can
be addressed by the associated URI scheme in order to
initiate a video communication session to a video messaging
system.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc5278"/>, Section 3.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc5278"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Jason_Livingood"/>
<xref type="person" data="Don_Troshynski"/>
</requesters>
<additionalinfo>
<paragraph>
Implementers should review a non-exclusive list of examples
in Section 7 of <xref type="rfc" data="rfc5278"/>.
</paragraph>
</additionalinfo>
</record>
<record>
<!-- voice:tel -->
<class>Application-Based, Common</class>
<type>voice</type>
<subtype>tel</subtype>
<urischeme>tel</urischeme>
<functionalspec>
<paragraph>
The kind of communication indicated by this
Enumservice is "Interactive Voice". From a protocol
perspective, this communication is expected to
involve bidirectional media streams carrying audio
data.
</paragraph>
<paragraph>
A client may imply that the person controlling
population of a NAPTR holding this Enumservice
indicates their capability to engage in an
interactive voice session when contacted using the
URI generated by this NAPTR.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc4415"/>, Section 5.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc4415"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Rudolf_Brandner"/>
<xref type="person" data="Lawrence_Conroy"/>
<xref type="person" data="Richard_Stastny"/>
</requesters>
<additionalinfo>
<paragraph>
This Enumservice indicates that the person
responsible for the NAPTR is accessible via the PSTN
(Public Switched Telephone Network) or PLMN (Public
Land Mobile Network) using the value of the
generated URI.
</paragraph>
<paragraph>The kind of subsystem required to initiate a
Voice Enumservice with this Subtype is a "Dialler".
This is a subsystem that either provides a local
connection to the PSTN or PLMN, or that provides an
indirect connection to those networks. The
subsystem will use the telephone number held in the
generated URI to place a voice call. The voice call
is placed to a network that uses E.164 numbers to
route calls to an appropriate destination.
</paragraph>
<paragraph>
Note that the PSTN/PLMN connection may be
indirect. The end user receiving this NAPTR may
have a relationship with a Communications Service
Provider that accepts call initiation requests from
that subsystem using an IP-based protocol such as
SIP or H.323, and places the call to the PSTN using
a remote gateway service. In this case, the Provider
may either accept requests using "tel:" URIs or has
a defined mechanism to convert "tel:" URI values
into a "protocol-native" form.
</paragraph>
<paragraph>
The "tel:" URI value SHOULD be fully qualified
(using the "global phone number" form of RFC 3966
[10]). A "local phone number" as defined in that
document SHOULD NOT be used unless the controller of
the zone in which the NAPTR appears is sure that it
can be distinguished unambiguously by all clients
that can access the resource record and that a call
from their network access points can be routed to
that destination.
</paragraph>
<paragraph>
References are contained in <xref type="rfc" data="rfc4415"/>.
</paragraph>
</additionalinfo>
</record>
<record>
<!-- voicemsg:http -->
<class>Application-Based, Common</class>
<type>voicemsg</type>
<subtype>http</subtype>
<urischeme>http</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource identified by
the associated URI scheme is capable of being a source of
information.
</paragraph>
<paragraph>
Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'http:' [11] URI
provides a document. This document can contain references
that will trigger the download of many different kinds of
information, such as text, audio, video, executable code, or
even voice message files. Thus, one cannot be more specific
about the kind of information expected when contacting the
resource.
</paragraph>
<paragraph>
References are contained in <xref type="rfc" data="rfc5278"/>.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc5278"/>, Section 3.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc5278"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Jason_Livingood"/>
<xref type="person" data="Don_Troshynski"/>
</requesters>
<additionalinfo>
<paragraph>
Implementers should review a non-exclusive list of examples
in Section 7 of <xref type="rfc" data="rfc5278"/>.
</paragraph>
</additionalinfo>
</record>
<record>
<!-- voicemsg:https -->
<class>Application-Based, Common</class>
<type>voicemsg</type>
<subtype>https</subtype>
<urischeme>https</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource identified by
the associated URI scheme is capable of being a source of
information, which can be contacted using TLS or the Secure
Socket Layer protocol.
</paragraph>
<paragraph>
Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'https:' [12] URI
provides a document. This document can contain references
that will trigger the download of many different kinds of
information, such as text, audio, video, executable code, or
even voice message files. Thus, one cannot be more specific
about the kind of information expected when contacting the
resource.
</paragraph>
<paragraph>
References are contained in <xref type="rfc" data="rfc5278"/>.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc5278"/>, Section 3.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc5278"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Jason_Livingood"/>
<xref type="person" data="Don_Troshynski"/>
</requesters>
<additionalinfo>
<paragraph>
Implementers should review a non-exclusive list of examples
in Section 7 of <xref type="rfc" data="rfc5278"/>.
</paragraph>
</additionalinfo>
</record>
<record>
<!-- voicemsg:sip -->
<class>Application-Based, Common</class>
<type>voicemsg</type>
<subtype>sip</subtype>
<urischeme>sip</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource identified can
be addressed by the associated URI scheme in order to
initiate a voice communication session to a voice messaging
system.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc5278"/>, Section 3.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc5278"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Jason_Livingood"/>
<xref type="person" data="Don_Troshynski"/>
</requesters>
<additionalinfo>
<paragraph>
Implementers should review a non-exclusive list of examples
in Section 7 of <xref type="rfc" data="rfc5278"/>.
</paragraph>
</additionalinfo>
</record>
<record>
<!-- voicemsg:sips -->
<class>Application-Based, Common</class>
<type>voicemsg</type>
<subtype>sips</subtype>
<urischeme>sips</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource identified can
be addressed by the associated URI scheme in order to
initiate a voice communication session to a voice messaging
system.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc5278"/>, Section 3.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc5278"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Jason_Livingood"/>
<xref type="person" data="Don_Troshynski"/>
</requesters>
<additionalinfo>
<paragraph>
Implementers should review a non-exclusive list of examples
in Section 7 of <xref type="rfc" data="rfc5278"/>.
</paragraph>
</additionalinfo>
</record>
<record>
<!-- voicemsg:tel -->
<class>Application-Based, Common</class>
<type>voicemsg</type>
<subtype>tel</subtype>
<urischeme>tel</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource identified can
be addressed by the associated URI scheme in order to
initiate a voice communication session to a voice messaging
system.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc5278"/>, Section 3.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc5278"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Jason_Livingood"/>
<xref type="person" data="Don_Troshynski"/>
</requesters>
<additionalinfo>
<paragraph>
Implementers should review a non-exclusive list of examples
in Section 7 of <xref type="rfc" data="rfc5278"/>.
</paragraph>
</additionalinfo>
</record>
<record>
<!-- vpim:ldap -->
<class>Data Type-Based</class>
<type>vpim</type>
<subtype>ldap</subtype>
<urischeme>ldap</urischeme>
<functionalspec>
See <xref type="rfc" data="rfc4238"/>, Section 3.2 - 3.3.
</functionalspec>
<security>
<paragraph>
Malicious Redirection:
One of the fundamental dangers related to any
service such as this is that a malicious entry in a
resolver's database will cause clients to resolve
the E.164 into the wrong LDAP URI. The possible
intent may be to cause the client to connect to a
rogue LDAP server and retrieve (or fail to retrieve)
a resource containing fraudulent or damaging
information.
</paragraph>
<paragraph>
Denial of Service:
By removing the URI to which the E.164 maps, a
malicious intruder may remove the client's ability
to access the LDAP directory server.
</paragraph>
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc4238"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Greg_Vaudreuil"/>
</requesters>
</record>
<record>
<!-- vpim:mailto -->
<class>Data Type-Based</class>
<type>vpim</type>
<subtype>mailto</subtype>
<urischeme>mailto</urischeme>
<functionalspec>
See <xref type="rfc" data="rfc4238"/>, Section 4.2 - 4.4.
</functionalspec>
<security>
<paragraph>
Malicious Redirection:
One of the fundamental dangers related to any
service such as this is that a malicious entry in a
resolver's database will cause clients to resolve
the E.164 into the wrong email URI. The possible
intent may be to cause the client to send the
information to an incorrect destination.
</paragraph>
<paragraph>
Denial of Service:
By removing the URI to which the E.164 maps, a
malicious intruder may remove the client's ability
to access the resource.
</paragraph>
<paragraph>
Unsolicited Bulk Email:
The exposure of email addresses through the ENUM
service provides a bulk mailer access to large
numbers of email addresses where only the telephone
number was previously known.
</paragraph>
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc4238"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Greg_Vaudreuil"/>
</requesters>
<additionalinfo>
<paragraph>
Error Conditions:
</paragraph>
<paragraph>
E.164 number not in the numbering plan
</paragraph>
<paragraph>
E.164 number in the numbering plan, but no
URIs exist for that number
</paragraph>
<paragraph>
E2U+vpim:mailto Service unavailable of email
addresses where only the telephone number was
previously known.
</paragraph>
</additionalinfo>
</record>
<record>
<!-- web:http -->
<class>Application-Based, Common</class>
<type>web</type>
<subtype>http</subtype>
<urischeme>http</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource
identified by the associated URI is capable
of being a source of information. It has to be
noted that the kind of information retrieved can be
manifold. Usually, contacting a resource by an
"http:" URI provides a document. This document can
contain references that will trigger download of
many different kinds of information, like audio or
video or executable code. Thus, one cannot be more
specific about the kind of information that can be
expected when contacting the resource.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc4002"/>, Section 5.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc4002"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Rudolf_Brandner"/>
<xref type="person" data="Lawrence_Conroy"/>
<xref type="person" data="Richard_Stastny"/>
</requesters>
</record>
<record>
<!-- web:https -->
<class>Application-Based, Common</class>
<type>web</type>
<subtype>https</subtype>
<urischeme>https</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource
identified by the associated URI is capable
of being a source of information, which can be
contacted by using TLS or the Secure Socket Layer
protocol. It has to be noted that the kind of
information retrieved can be manifold. Usually,
contacting a resource by an "https:" URI provides a
document. This document can contain all different
kinds of information, like audio or video or
executable code. Thus, one cannot be more specific
what information to expect when contacting the
resource.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc4002"/>, Section 5.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc4002"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Rudolf_Brandner"/>
<xref type="person" data="Lawrence_Conroy"/>
<xref type="person" data="Richard_Stastny"/>
</requesters>
</record>
<record>
<!-- xmpp -->
<class>Protocol-Based</class>
<type>xmpp</type>
<!-- No subtype -->
<urischeme>xmpp</urischeme>
<functionalspec>
<paragraph>
This Enumservice indicates that the resource
identified is an XMPP entity.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="rfc4979"/>, Section 6.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfc4979"/> (updated by RFC 6118)
<xref type="rfc" data="RFC 6118"/>
</registrationdocs>
<requesters>
<xref type="person" data="Alexander_Mayrhofer"/>
</requesters>
</record>
IANA replaced all legacy Enumservice Registrations as per Section 4.
IANAは、セクション4に従って、すべてのLegacy Enumservice登録を交換しました。
Since this document does not introduce any technology or protocol, there are no security issues to be considered for this document itself.
このドキュメントはテクノロジーやプロトコルを導入していないため、このドキュメント自体について考慮すべきセキュリティの問題はありません。
The authors would like to thank the following people who have provided feedback or significant contributions to the development of this document: Jari Arkko, Scott Bradner, Gonzalo Camarillo, Alfred Hoenes, Ari Keranen, and Alexey Melnikov.
著者は、この文書の開発にフィードバックまたは多大な貢献を提供した以下の人々に感謝したいと思います：Jari Arkko、Scott Bradner、Gonzalo Camarillo、Alfred Hoenes、Ari Keranen、およびAlexey Melnikov。
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996.
[RFC2026] Bradner、S。、「インターネット標準プロセス - 改訂3」、BCP 9、RFC 2026、1996年10月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119] Bradner、S。、「要件レベルを示すためにRFCで使用するためのキーワード」、BCP 14、RFC 2119、1997年3月。
[RFC3761] Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)", RFC 3761, April 2004.
[RFC3761] Faltstrom、P。and M. Mealling、「E.164へのユニフォームリソース識別子（URI）動的委任ディスカバリーシステム（DDDS）アプリケーション（ENUM）」、RFC 3761、2004年4月。
[RFC3762] Levin, O., "Telephone Number Mapping (ENUM) Service Registration for H.323", RFC 3762, April 2004.
[RFC3762] Levin、O。、 "H.323の電話番号マッピング（Enum）サービス登録"、RFC 3762、2004年4月。
[RFC3764] Peterson, J., "enumservice registration for Session Initiation Protocol (SIP) Addresses-of-Record", RFC 3764, April 2004.
[RFC3764] Peterson、J。、「セッション開始プロトコル（SIP）アドレスの登録登録」、RFC 3764、2004年4月。
[RFC3953] Peterson, J., "Telephone Number Mapping (ENUM) Service Registration for Presence Services", RFC 3953, January 2005.
[RFC3953] Peterson、J。、「プレゼンスサービスの電話番号マッピング（列挙）サービス登録」、RFC 3953、2005年1月。
[RFC4002] Brandner, R., Conroy, L., and R. Stastny, "IANA Registration for Enumservice 'web' and 'ft'", RFC 4002, February 2005.
[RFC4002] Brandner、R.、Conroy、L。、およびR. Stastny、「Enumservice 'web'および 'ft'のIANA登録」、RFC 4002、2005年2月。
[RFC4143] Toyoda, K. and D. Crocker, "Facsimile Using Internet Mail (IFAX) Service of ENUM", RFC 4143, November 2005.
[RFC4143] Toyoda、K。およびD. Crocker、「Internet Mail（IFAX）サービスを使用したファクシミリ」、RFC 4143、2005年11月。
[RFC4238] Vaudreuil, G., "Voice Message Routing Service", RFC 4238, October 2005.
[RFC4238] Vaudreuil、G。、「音声メッセージルーティングサービス」、RFC 4238、2005年10月。
[RFC4355] Brandner, R., Conroy, L., and R. Stastny, "IANA Registration for Enumservices email, fax, mms, ems, and sms", RFC 4355, January 2006.
[RFC4355] Brandner、R.、Conroy、L。、およびR. Stastny、「Enumservices Email、Fax、MMS、EMS、およびSMSのIANA登録」、RFC 4355、2006年1月。
[RFC4415] Brandner, R., Conroy, L., and R. Stastny, "IANA Registration for Enumservice Voice", RFC 4415, February 2006.
[RFC4415] Brandner、R.、Conroy、L。、およびR. Stastny、「Enumservice VoiceのIANA登録」、RFC 4415、2006年2月。
[RFC4769] Livingood, J. and R. Shockey, "IANA Registration for an Enumservice Containing Public Switched Telephone Network (PSTN) Signaling Information", RFC 4769, November 2006.
[RFC4769] Livingood、J。およびR. Shockey、「2006年11月、RFC 4769、RFC 4769、RFC 4769、RFC 4769、RFC 4769を含むIANA登録」。
[RFC4969] Mayrhofer, A., "IANA Registration for vCard Enumservice", RFC 4969, August 2007.
[RFC4969] Mayrhofer、A。、「VCard EnumserviceのIANA登録」、RFC 4969、2007年8月。
[RFC4979] Mayrhofer, A., "IANA Registration for Enumservice 'XMPP'", RFC 4979, August 2007.
[RFC4979] Mayrhofer、A。、「Enumservice 'XMPP'のIANA登録」、RFC 4979、2007年8月。
[RFC5028] Mahy, R., "A Telephone Number Mapping (ENUM) Service Registration for Instant Messaging (IM) Services", RFC 5028, October 2007.
[RFC5028] Mahy、R。、「インスタントメッセージング（IM）サービスの電話番号マッピング（列挙）サービス登録」、RFC 5028、2007年10月。
[RFC5278] Livingood, J. and D. Troshynski, "IANA Registration of Enumservices for Voice and Video Messaging", RFC 5278, July 2008.
[RFC5278] Livingood、J。およびD. Troshynski、「Voice and Video MessagingのEnumservicesのIANA登録」、RFC 5278、2008年7月。
[RFC5333] Mahy, R. and B. Hoeneisen, "IANA Registration of Enumservices for Internet Calendaring", RFC 5333, October 2009.
[RFC5333] Mahy、R。およびB. Hoeneisen、「インターネットカレンダーのためのEnumservicesのIANA登録」、RFC 5333、2009年10月。
[RFC6117] Hoeneisen, B., Mayrhofer, A., and J. Livingood, "IANA Registration of Enumservices: Guide, Template, and IANA Considerations", RFC 6117, March 2011.
[RFC6117] Hoeneisen、B.、Mayrhofer、A。、およびJ. Livingood、「EnumservicesのIANA登録：ガイド、テンプレート、およびIANAの考慮事項」、RFC 6117、2011年3月。
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
[RFC5226] Narten、T。およびH. Alvestrand、「RFCSでIANA考慮事項セクションを書くためのガイドライン」、BCP 26、RFC 5226、2008年5月。
Enumservice Registrations
Enumservice登録
(last updated 2009-10-13)
（最終更新2009-10-13）
Registries included below: - Enumservice Registrations
以下を含むレジストリ：-Enumservice登録
Registry Name: Enumservice Registrations Reference: [RFC3761] Registration Procedures: Require an RFC approved by the IESG
レジストリ名：Enumservice登録リファレンス：[RFC3761]登録手順：IESGによって承認されたRFCが必要です
Note: Enumservice specifications contain the functional specification (i.e. what it can be used for), the valid protocols, and the URI schemes that may be returned.
注：Enumservice仕様には、機能仕様（つまり、使用できるもの）、有効なプロトコル、および返される可能性のあるURIスキームが含まれています。
Registry:
Service Name: "H323"
URI Scheme(s): "h323:"
Functional Specification:
See Section "3. The E2U+H323 ENUM Service" of [RFC3762]
Security considerations:
see section "5. Security Considerations" of [RFC3762]
Intended usage: COMMON
Author: Orit Levin
[RFC3762]
Service Name: "SIP"
Type(s): "SIP"
Subtype(s): N/A
URI Scheme(s): "sip", "sips:"
Functional Specification: see Section 4 of [RFC3764]
Security considerations: see Section 6 of [RFC3764]
Intended usage: COMMON
Author: Jon Peterson (jon.peterson&neustar.biz)
Any other information that the author deems interesting:
see Section 3 of [RFC3764]
[RFC3764]
Service Name: "ifax"
Type: "ifax"
Subtype: "mailto"
URI Scheme: "mailto"
The URI Scheme is "mailto" because facsimile is a profile of
standard Internet mail and uses standard Internet mail
addressing.
Functional Specification: see section 1 of [RFC4143]
Security Considerations: see section 3 of [RFC4143]
Intended usage: COMMON
Author: Kiyoshi Toyoda(toyoda.kiyoshi&jp.panasonic.com)
Dave Crocker(dcrocker&brandenburg.com)
[RFC4143]
Service Name: "pres"
URI Scheme(s): "pres:"
Functional Specification: see Section 4 of [RFC3953]
Security considerations: see Section 6 of [RFC3953]
Intended usage: COMMON
Author: Jon Peterson (jon.peterson&neustar.biz)
Any other information that the author deems interesting:
See Section 3 of [RFC3953]
[RFC3953]
Service Name: "web" Type: "web" Subtype: "http" URI Scheme: 'http:' Functional Specification: This ENUMservice indicates that the resource identified by the associated URI scheme is capable of being a source of information. It has to be noted that the kind of information retrieved can be manifold. Usually, contacting a resource by an 'http:' URI provides a document. This document can contain references that will trigger download of many different kinds of information, like audio or video or executable code. Thus, one can not be more specific about the kind of information that can be expected when contacting the resource. Security Considerations: See section 5 of [RFC4002]. Intended Usage: COMMON Authors: Rudolf Brandner (rudolf.brandner&siemens.com) Lawrence Conroy (lwc&roke.co.uk) Richard Stastny (richard.stastny&oefeg.at) Any other information the author deems interesting: None [RFC4002]
サービス名： "web"タイプ： "web"サブタイプ： "http" uriスキーム： 'http：' functional仕様：このenmserviceは、関連するURIスキームによって識別されるリソースが情報源であることを示します。取得された情報の種類は多様である可能性があることに注意する必要があります。通常、 'http：' uriがドキュメントを提供してリソースに連絡します。このドキュメントには、オーディオやビデオ、実行可能コードなど、さまざまな種類の情報のダウンロードをトリガーする参照を含めることができます。したがって、リソースに連絡するときに期待できる情報の種類について、より具体的には具体的ではありません。セキュリティ上の考慮事項：[RFC4002]のセクション5を参照してください。意図された使用法：一般的な著者：Rudolf Brandner（Rudolf.Brandner＆Siemens.com）Lawrence Conroy（LWC＆Roke.co.uk）Richard Stastny（Richard.Stastny＆Oefeg.at）著者が考えるその他の情報
Service Name: "web" Type: "web" Subtype: "https" URI Scheme: 'https:' Functional Specification: This ENUMservice indicates that the resource identified by the associated URI scheme is capable of being a source of information, which can be contacted by using TLS or Secure Socket Layer protocol. It has to be noted that the kind of information retrieved can be manifold. Usually, contacting a resource by an 'https:' URI provides a document. This document can contain all different kind of information, like audio or video or executable code. Thus, one can not be more specific what information to expect when contacting the resource. Security Considerations: See section 5 of [RFC4002]. Intended Usage: COMMON Authors: Rudolf Brandner (rudolf.brandner&siemens.com) Lawrence Conroy (lwc&roke.co.uk) Richard Stastny (richard.stastny&oefeg.at) Any other information the author deems interesting: None [RFC4002]
サービス名： "web"タイプ： "web" subtype： "https" uriスキーム： 'https：' functional仕様：このenmserviceは、関連するURIスキームによって識別されるリソースが情報源であることを示しています。TLSまたはセキュアソケットレイヤープロトコルを使用して連絡します。取得された情報の種類は多様である可能性があることに注意する必要があります。通常、 'https：' uriがドキュメントを提供してリソースに連絡します。このドキュメントには、オーディオ、ビデオ、実行可能なコードなど、あらゆる種類の情報を含めることができます。したがって、リソースに連絡するときにどの情報が期待するかをより具体的にすることはできません。セキュリティ上の考慮事項：[RFC4002]のセクション5を参照してください。意図された使用法：一般的な著者：Rudolf Brandner（Rudolf.Brandner＆Siemens.com）Lawrence Conroy（LWC＆Roke.co.uk）Richard Stastny（Richard.Stastny＆Oefeg.at）著者が考えるその他の情報
Service Name: "ft" Type: "ft" Subtype: "ftp" URI Scheme: 'ftp:' Functional Specification: This ENUMservice indicates that the resource identified by the associated URI scheme is a file service from which a file or file listing can be retrieved. Security Considerations: See section 5 of [RFC4002]. Intended Usage: COMMON Authors: Rudolf Brandner (rudolf.brandner&siemens.com) Lawrence Conroy (lwc&roke.co.uk) Richard Stastny (richard.stastny&oefeg.at) Any other information the author deems interesting: None [RFC4002]
サービス名： "ft"タイプ： "ft"サブタイプ： "ftp" uriスキーム： 'ftp：' functional仕様：このenmserviceは、関連するURIスキームによって識別されるリソースがファイルまたはファイルリストができるファイルサービスであることを示します。検索されます。セキュリティ上の考慮事項：[RFC4002]のセクション5を参照してください。意図された使用法：一般的な著者：Rudolf Brandner（Rudolf.Brandner＆Siemens.com）Lawrence Conroy（LWC＆Roke.co.uk）Richard Stastny（Richard.Stastny＆Oefeg.at）著者が考えるその他の情報
Enumservice Name: "email" Enumservice Type: "email" Enumservice Subtype: "mailto" URI Scheme: 'mailto:' Functional Specification: This Enumservice indicates that the remote resource can be addressed by the associated URI scheme in order to send an email. Security Considerations: See Section 6 of [RFC4355] Intended Usage: COMMON Authors: Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author contact detail see [RFC4355]) Any other information the author deems interesting: None
Enumservice名： "email" enumserviceタイプ： "email" enumservice subtype： "mailto" uriスキーム： 'mailto：' functional仕様：このEnumserviceは、電子メールを送信するために関連するURIスキームでリモートリソースに対処できることを示します。セキュリティ上の考慮事項：[RFC4355]のセクション6を参照してください。意図した使用法：共通著者：Rudolf Brandner、Lawrence Conroy、Richard Stastny（著者の連絡先の詳細については[RFC4355]を参照）
Enumservice Name: "fax" Enumservice Type: "fax" Enumservice Subtype: "tel" URI Scheme: 'tel:' Functional Specification: This Enumservice indicates that the resource identified by the associated URI scheme is capable of being contacted to provide a communication session during which facsimile documents can be sent. A client selecting this NAPTR will have support for generating and sending facsimile documents to the recipient using the PSTN session and transfer protocols specified in [12] and [13] in [RFC4355] - in short, they will have a fax program with a local or shared PSTN access over which they can send faxes. Security Considerations: See Section 6 of [RFC4355] Intended Usage: COMMON Authors: Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author contact detail see [RFC4355]) Any other information the author deems interesting: None
Enumservice名： "fax" enumserviceタイプ： "fax" enumservice subtype： "tel" uriスキーム： 'tel：' functional仕様：このenmserviceは、関連するURIスキームによって識別されるリソースが連絡できるように連絡できることを示しています。その間にファクシミリドキュメントを送信できます。このNAPTRを選択するクライアントは、[12]および[13]で[RFC4355]で指定されたPSTNセッションと転送プロトコルを使用して、受信者にファクシミリドキュメントを生成および送信することをサポートします。または、ファックスを送信できるPSTNアクセスを共有します。セキュリティ上の考慮事項：[RFC4355]のセクション6を参照してください。意図した使用法：共通著者：Rudolf Brandner、Lawrence Conroy、Richard Stastny（著者の連絡先の詳細については[RFC4355]を参照）
Enumservice Name: "sms" Enumservice Type: "sms" Enumservice Subtypes: "tel" URI Scheme: 'tel:' Functional Specification: This Enumservice indicates that the resource identified by the associated URI scheme is capable of receiving a message using the Short Message Service (SMS) [14] in [RFC4355]. Security Considerations: There are no specific security issues with this Enumservice. However, the general considerations of Section 6 apply. Intended Usage: COMMON Authors: Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author contact detail see [RFC4355]) Any other information the author deems interesting: None
Enumservice名： "sms" enumserviceタイプ： "sms" enumservice subtypes： "tel" uriスキーム： 'tel：' functional仕様：このenmserviceは、関連するURIスキームによって識別されるリソースが短いメッセージを使用してメッセージを受信できることを示しています。[RFC4355]のサービス（SMS）[14]。セキュリティ上の考慮事項：このEnumserviceには特定のセキュリティの問題はありません。ただし、セクション6の一般的な考慮事項が適用されます。意図された使用法：一般的な著者：Rudolf Brandner、Lawrence Conroy、Richard Stastny（著者の連絡先の詳細については[RFC4355]を参照）著者が興味深いと思うその他の情報：なし
Enumservice Name: "sms" Enumservice Type: "sms" Enumservice Subtypes: "mailto" URI Scheme: 'mailto:' Functional Specification: This Enumservice indicates that the resource identified by the associated URI scheme is capable of receiving a message using an email protocol. SMS content is sent over SMTP using the format specified by TS 23.140 [15] section 8.4.4 and TS 26.140 [16] section 4 (for references see [RFC4355]), as an MMS message. Within such a message, SMS content is carried as either a text or application/octet-stream MIME sub-part (see TS 26.140 [16] , section 4.1) For references see [RFC4355]. Security Considerations: There are no specific security issues with this Enumservice. However, the general considerations of Section 6 apply, see [RFC4355]. Intended Usage: COMMON Authors: Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author contact detail see [RFC4355]) Any other information the author deems interesting: None
Enumservice名： "sms" enumserviceタイプ： "sms" enumservice subtypes： "mailto" uriスキーム： 'mailto：' functional仕様：このenmserviceは、関連するURIスキームによって識別されるリソースが電子メールプロトコルを使用してメッセージを受信できることを示しています。。SMSコンテンツは、TS 23.140 [15]セクション8.4.4およびTS 26.140 [16]セクション4（参照については[RFC4355]を参照）でMMSメッセージとして指定された形式を使用してSMTPを介して送信されます。このようなメッセージ内で、SMSコンテンツは、テキストまたはアプリケーション/オクテットストリームMIMEサブパート（TS 26.140 [16]、セクション4.1を参照）として運ばれます[RFC4355]を参照してください。セキュリティ上の考慮事項：このEnumserviceには特定のセキュリティの問題はありません。ただし、セクション6の一般的な考慮事項は適用されます。[RFC4355]を参照してください。意図された使用法：一般的な著者：Rudolf Brandner、Lawrence Conroy、Richard Stastny（著者の連絡先の詳細については[RFC4355]を参照）著者が興味深いと思うその他の情報：なし
Enumservice Name: "ems" Enumservice Type: "ems" Enumservice Subtype: "tel" URI Scheme: 'tel:' Functional Specification: This Enumservice indicates that the resource identified by the associated URI scheme is capable of receiving a message using the Enhanced Message Service (EMS) [14] (For reference see [RFC4355]). Security Considerations: There are no specific security issues with this Enumservice. However, the general considerations of Section 6 apply. See [RFC4355] Intended Usage: COMMON Authors: Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author contact detail see [RFC4355]) Any other information the author deems interesting: Note that an indication of EMS can be taken as implying that the recipient is capable of receiving SMS messages at this address as well.
Enumservice名： "ems" enumserviceタイプ： "ems" enumservice subtype： "tel" uriスキーム： 'tel：' functional仕様：このenmserviceは、関連するURIスキームによって識別されるリソースが拡張メッセージを使用してメッセージを受信できることを示しています。サービス（EMS）[14]（参照については[RFC4355]を参照）。セキュリティ上の考慮事項：このEnumserviceには特定のセキュリティの問題はありません。ただし、セクション6の一般的な考慮事項が適用されます。[RFC4355]を参照してください。使用法を参照：一般的な著者：Rudolf Brandner、Lawrence Conroy、Richard Stastny（著者の連絡先の詳細については[RFC4355]を参照）著者が興味深いとみなすもの：EMSの兆候は、受信者が受信者を意味すると見なすことができることに注意してくださいこのアドレスでSMSメッセージを受信することもできます。
Enumservice Name: "ems" Enumservice Type: "ems" Enumservice Subtypes: "mailto" URI Scheme: 'mailto:' Functional Specification: This Enumservice indicates that the resource identified by the associated URI scheme is capable of receiving a message using an email protocol. EMS content is sent over SMTP using the format specified by TS 23.140 [15] section 8.4.4 and TS 26.140 [16] section 4, as an MMS message. Within such a message, EMS content is carried as either a text or application/octet-stream MIME sub-part (see TS 26.140 [16] , section 4.1). For references see [RFC4355] Security Considerations: There are no specific security issues with this Enumservice. However, the general considerations of Section 6 of [RFC4355] apply. Intended Usage: COMMON Authors: Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author contact detail see [RFC4355]) Any other information the author deems interesting: None
Enumservice名： "ems" enumserviceタイプ： "ems" enumservice subtypes： "mailto" uriスキーム： 'mailto：' functional仕様：このenmserviceは、関連するURIスキームによって識別されるリソースが電子メールプロトコルを使用してメッセージを受信できることを示しています。。EMSコンテンツは、MMSメッセージとしてTS 23.140 [15]セクション8.4.4およびTS 26.140 [16]セクション4で指定された形式を使用してSMTPを介して送信されます。このようなメッセージ内で、EMSコンテンツはテキストまたはアプリケーション/オクテットストリームMIMEサブパートのいずれかとして運ばれます（TS 26.140 [16]、セクション4.1を参照）。参照については、[rfc4355]セキュリティに関する考慮事項を参照してください。このeNumserviceには具体的なセキュリティの問題はありません。ただし、[RFC4355]のセクション6の一般的な考慮事項が適用されます。意図された使用法：一般的な著者：Rudolf Brandner、Lawrence Conroy、Richard Stastny（著者の連絡先の詳細については[RFC4355]を参照）著者が興味深いと思うその他の情報：なし
Enumservice Name: "mms" Enumservice Type: "mms" Enumservice Subtype: "tel" URI Scheme: 'tel:' Functional Specification: This Enumservice indicates that the resource identified by the associated URI scheme is capable of receiving a message using the Multimedia Messaging Service (MMS) [15]. For references see [RFC4355] Security Considerations: There are no specific security issues with this Enumservice. However, the general considerations of Section 6 of [RFC4355] apply. Intended Usage: COMMON Authors: Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author contact detail see [RFC4355]) Any other information the author deems interesting: Note that MMS can be used as an alternative to deliver an SMS RP-DATA RPDU if, for example, the SMS bearer is not supported. If an entry includes this Enumservice, then in effect this can be taken as implying that the recipient is capable of receiving EMS or SMS messages at this address. Such choices on the end system design do have two small caveats; whilst in practice all terminals supporting MMS today support SMS as well, it might not necessarily be the case in the future, and there may be tariff differences in using the MMS rather than using the SMS or EMS.
Enumservice名： "mms" enumserviceタイプ： "mms" enumservice subtype： "tel" uriスキーム： 'tel：' functional仕様：このenmserviceは、関連するURIスキームによって識別されるリソースがマルチメディアメッセージングを使用してメッセージを受信できることを示しています。サービス（MMS）[15]。参照については、[rfc4355]セキュリティに関する考慮事項を参照してください。このeNumserviceには具体的なセキュリティの問題はありません。ただし、[RFC4355]のセクション6の一般的な考慮事項が適用されます。意図された使用法：一般的な著者：Rudolf Brandner、Lawrence Conroy、Richard Stastny（著者の連絡先の詳細については[RFC4355]を参照）著者は興味深いと思うものを参照してください。、たとえば、SMSベアラーはサポートされていません。エントリにこのEnumserviceが含まれている場合、事実上、これは受信者がこのアドレスでEMSまたはSMSメッセージを受信できることを暗示していると見なすことができます。このような最終システム設計の選択には、2つの小さな注意事項があります。実際には、MMSをサポートするすべてのターミナルもSMSをサポートしていますが、将来的には必ずしもそうではないかもしれませんし、SMSまたはEMSを使用するのではなく、MMSの使用に関税の違いがあるかもしれません。
Enumservice Name: "mms" Enumservice Type: "mms" Enumservice Subtypes: "mailto" URI Scheme: 'mailto:' Functional Specification: This Enumservice indicates that the resource identified by the associated URI scheme is capable of receiving a message using an email protocol. MMS messages are sent over SMTP using the format specified by TS 23.140 [15] section 8.4.4 and TS 26.140 [16] section 4. Within and between MMS Environments (MMSE, network infrastructures that support the MultiMedia Service), other pieces of state data (for example, charging-significant information) are exchanged between MMS Relay Servers. Thus, although these servers use SMTP as the "bearer" for their application exchanges, they map their internal state to specialised headers carried in the SMTP message exchanges. The headers used in such MMSE are described in detail in [17]. For references see [RFC4355]
Enumservice名： "mms" enumserviceタイプ： "mms" enumservice subtypes： "mailto" uriスキーム： 'mailto：' functional仕様：このenmserviceは、関連するURIスキームによって識別されるリソースが電子メールプロトコルを使用してメッセージを受信できることを示しています。。MMSメッセージは、TS 23.140 [15]セクション8.4.4およびTS 26.140 [16]セクション4で指定された形式を使用してSMTPを介して送信されます。データ（たとえば、充電に有意な情報など）は、MMSリレーサーバー間で交換されます。したがって、これらのサーバーはアプリケーション交換の「ベアラー」としてSMTPを使用していますが、内部状態をSMTPメッセージ交換で運ばれる専門のヘッダーにマッピングします。このようなMMSEで使用されるヘッダーは、[17]で詳細に説明されています。参照については[RFC4355]を参照してください
Security Considerations: There are no specific security issues with this Enumservice. However, the general considerations of Section 6 of [RFC4355] apply. Intended Usage: COMMON Authors: Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author contact detail see [RFC4355]) Any other information the author deems interesting: The MMS Architecture describes an interface between the MMSE and "legacy messaging systems" (labelled as MM3) which accepts "standard" SMTP messages. Thus although the MMS Relay Server that supports this interface appears as a standard SMTP server from the perspective of an Internet-based mail server, it acts as a gateway and translator, adding the internal state data that is used within and between the MMS Environments. This mechanism is described in [17], which also includes references to the specifications agreed by those bodies responsible for the design of the MMS.
セキュリティ上の考慮事項：このEnumserviceには特定のセキュリティの問題はありません。ただし、[RFC4355]のセクション6の一般的な考慮事項が適用されます。意図された使用法：一般的な著者：Rudolf Brandner、Lawrence Conroy、Richard Stastny（著者の連絡先の詳細については[RFC4355]を参照）著者が興味深いとみなすもの：MMSアーキテクチャはMMSEと「レガシーメッセージシステム」の間のインターフェイスを説明しています（MM3）「標準」SMTPメッセージを受け入れます。したがって、このインターフェイスをサポートするMMSリレーサーバーは、インターネットベースのメールサーバーの観点から標準のSMTPサーバーとして表示されますが、ゲートウェイと翻訳者として機能し、MMS環境内およびMMS環境間で使用される内部状態データを追加します。このメカニズムは[17]で説明されています。これには、MMSの設計に責任がある身体によって合意された仕様への参照も含まれています。
Service Name: E.164 to VPIM MailTo: URL
URI Type: "Mailto:"
Type: VPIM
Subtype: MAILTO
Functional Specification: See section 4.2 through 4.4 of [RFC4238]
Intended Usage: COMMON
Author: Greg Vaudreuil (gregv&ieee.org)
Error Conditions:
o E.164 number not in the numbering plan
o E.164 number in the numbering plan, but no URLs exist for that
number
o E2U+VPIM:Mailto Service unavailable
Security Considerations:
o Malicious Redirection
One of the fundamental dangers related to any service such as
this is that a malicious entry in a resolver's database will
cause clients to resolve the E.164 into the wrong email URL.
The possible intent may be to cause the client to send the
information to an incorrect destination.
o Denial of Service
By removing the URL to which the E.164 maps, a malicious
intruder may remove the client's ability to access the
resource.
o Unsolicited Bulk Email
The exposure of email addresses through the ENUM
service provides a bulk mailer access to large numbers
of email addresses where only the telephone number was
previously known.
Service Name: E.164 to VPIM LDAP URL URI Type: "LDAP:" Type: VPIM Subtype: LDAP Functional Specification: See section 3.2 through 3.3 of [RFC4238] Intended Usage: COMMON Author: Greg Vaudreuil (gregv&ieee.org) Security Considerations: o Malicious Redirection One of the fundamental dangers related to any service such as this is that a malicious entry in a resolver's database will cause clients to resolve the E.164 into the wrong LDAP URL. The possible intent may be to cause the client to connect to a rogue LDAP server and retrieve (or fail to retrieve) a resource containing fraudulent or damaging information. o Denial of Service By removing the URL to which the E.164 maps, a malicious intruder may remove the client's ability to access the LDAP directory server.
サービス名：E.164からVPIM LDAP URL URIタイプ： "LDAP："タイプ：VPIMサブタイプ：LDAP機能仕様：[RFC4238]のセクション3.2から3.3を参照してください。：o悪意のあるリダイレクトこのようなサービスに関連する基本的な危険の1つは、Resolverのデータベースに悪意のあるエントリにより、クライアントがE.164を間違ったLDAP URLに解決することです。考えられる意図は、クライアントにRogue LDAPサーバーに接続し、詐欺的または損害を受けた情報を含むリソースを取得（または取得できない）することです。oサービスの拒否E.164マップをマップするURLを削除することにより、悪意のある侵入者がLDAPディレクトリサーバーにアクセスするクライアントの機能を削除する場合があります。
Enumservice Name: "voice"
Enumservice Type: "voice"
Enumservice Subtype: "tel"
URI Scheme: 'tel:'
Functional Specification:
The kind of communication indicated by this Enumservice is
"Interactive Voice". From a protocol perspective, this
communication is expected to involve bidirectional media streams
carrying audio data.
A client may imply that the person controlling population of a
NAPTR holding this Enumservice indicates their capability to
engage in an interactive voice session when contacted using the
URI generated by this NAPTR.
Security Considerations:
See Section 5 of [RFC4415]
Intended Usage: COMMON
Authors: Rudolf Brandner, Lawrence Conroy, Richard Stastny (for
author contact detail see Authors' Addresses section)
Any other information the author deems interesting:
o This Enumservice indicates that the person responsible for the
NAPTR is accessible via the PSTN (Public Switched Telephone
Network) or PLMN (Public Land Mobile Network) using the value of
the generated URI.
o The kind of subsystem required to initiate a Voice Enumservice
with this sub-type is a "Dialler". This is a subsystem that
either provides a local connection to the PSTN or PLMN, or that
provides an indirect connection to those networks. The
subsystem will use the telephone number held in the generated
URI to place a voice call. The voice call is placed to a
network that uses E.164 numbers to route calls to an appropriate
destination.
o Note that the PSTN/PLMN connection may be indirect. The end
user receiving this NAPTR may have a relationship with a
Communications Service Provider that accepts call initiation
requests from that subsystem using an IP-based protocol such as
SIP or H.323, and places the call to the PSTN using a remote
gateway service. In this case the Provider may either accept
requests using "tel:" URIs or has a defined mechanism to convert
"tel:" URI values into a "protocol-native" form.
o The "tel:" URI value SHOULD be fully qualified (using the
"global phone number" form of RFC3966 [10]). A "local phone
number" as defined in that document SHOULD NOT be used unless
the controller of the zone in which the NAPTR appears is sure
that it can be distinguished unambiguously by all clients that
can access the resource record and that a call from their
network access points can be routed to that destination.
Enumservice Name: "pstn" Enumservice Type: "pstn" Enumservice Subtype: "tel" URI Scheme: 'tel:' Functional Specification: These Enumservices indicate that the remote resource identified can be addressed by the associated URI scheme in order to initiate a telecommunication session, which may include two-way voice or other communications, to the PSTN. These URIs may contain number portability data as specified in RFC 4694 [10]. Security Considerations: See Section 7 of [RFC4769]. Intended Usage: COMMON Authors: Jason Livingood (jason_livingood&cable.comcast.com) Richard Shockey (richard.shockey&neustar.biz) Any other information the author deems interesting: A Number Portability Dip Indicator (npdi) should be used in practice (see examples below in Section 4 of [RFC4769]).
Enumservice名： "PSTN" Enumservice Type： "PSTN" Enumservice Subtype： "Tel" URIスキーム： 'Tel：'機能仕様：これらのencresvicesは、識別されたリモートリソースが、電気共産化を開始するために関連するURIスキームによって対処できることを示しています。PSTNへの双方向の音声またはその他の通信を含むセッション。これらのURIには、RFC 4694 [10]で指定されている数字の携帯性データが含まれている場合があります。セキュリティ上の考慮事項：[RFC4769]のセクション7を参照してください。意図された使用法：一般的な著者：Jason Livingood（jason_livingood＆cable.comcast.com）Richard Shockey（richard.shockey＆neustar.biz）著者が興味深いとみなすその他の情報：数の移植性のDIPインジケーター（NPDI）は実践で使用する必要があります（以下の例を参照してください[RFC4769]のセクション4）。
Enumservice Name: "pstn" Enumservice Type: "pstn" Enumservice Subtype: "sip" URI Scheme: 'sip:' Functional Specification: These Enumservices indicate that the remote resource identified can be addressed by the associated URI scheme in order to initiate a telecommunication session, which may include two-way voice or other communications, to the PSTN. Security Considerations: See Section 7 of [RFC4769]. Intended Usage: COMMON Authors: Jason Livingood (jason_livingood&cable.comcast.com) Richard Shockey (richard.shockey&neustar.biz) Any other information the author deems interesting: A Number Portability Dip Indicator (npdi) should be used in practice (see examples below in Section 4 of [RFC4769]).
Enumservice名： "PSTN" ENUMSERVICEタイプ： "PSTN" Enumservice Subtype： "SIP" URIスキーム： 'SIP：'機能仕様：これらのエンスムサービスは、識別されたリモートリソースが電気通信を開始するために関連するURIスキームによって対処できることを示しています。PSTNへの双方向の音声またはその他の通信を含むセッション。セキュリティ上の考慮事項：[RFC4769]のセクション7を参照してください。意図された使用法：一般的な著者：Jason Livingood（jason_livingood＆cable.comcast.com）Richard Shockey（richard.shockey＆neustar.biz）著者が興味深いとみなすその他の情報：数の移植性のDIPインジケーター（NPDI）は実践で使用する必要があります（以下の例を参照してください[RFC4769]のセクション4）。
Enumservice Name: "vCard" Enumservice Name: "vCard" Enumservice Type: "vcard" Enumservice Subtype: n/a URI Schemes: "http", "https" Functional Specification: This Enumservice indicates that the resource identified is a plain vCard, according to RFC 2426, which may be accessed using HTTP/ HTTPS [7]. Clients fetching the vCard from the resource indicated should expect access to be restricted. Additionally, the comprehension of the data provided may vary depending on the client's identity. Security Considerations: see Section 5 [RFC4969] Intended Usage: COMMON Author: Alexander Mayrhofer <alexander.mayrhofer&enum.at>
Enumservice名： "vcard" enumservice名： "vcard" enumserviceタイプ： "vcard" enumservice subtype：n/a uriスキーム： "http"、 "https" functional仕様：このenmserviceは、識別されたリソースが平凡なvcardであることを示しています。HTTP/ HTTPS [7]を使用してアクセスできるRFC 2426へ。指定されたリソースからVCARDを取得するクライアントは、アクセスが制限されることを期待する必要があります。さらに、提供されるデータの理解は、クライアントのIDによって異なる場合があります。セキュリティ上の考慮事項：セクション5 [rfc4969]を参照してください。
Enumservice Name: "XMPP" Enumservice Type: "xmpp" Enumservice Subtype: n/a URI Schemes: "xmpp" Functional Specification: This Enumservice indicates that the resource identified is an XMPP entity. Security Considerations: see Section 6 of [RFC4979] Intended Usage: COMMON Author: Alexander Mayrhofer <alexander.mayrhofer&enum.at>
Enumservice名： "xmpp" enumserviceタイプ： "xmpp" enumservice subtype：n/a uriスキーム： "xmpp" functional仕様：このenmserviceは、識別されたリソースがxmppエンティティであることを示します。セキュリティ上の考慮事項：[RFC4979]のセクション6を参照してください。
Enumservice Name: "im" Enumservice Type: "im" Enumservice Subtypes: N/A URI scheme(s): "im:" Functional Specification: This Enumservice indicates that the resource identified is an 'im:' URI. The 'im:' URI scheme does not identify any particular protocol that will be used to handle instant messaging receipt or delivery, rather the mechanism in RFC 3861 [4] is used to discover whether an IM protocol supported by the party querying ENUM is also supported by the target resource. Security considerations: See section 3 of [RFC5028] Intended usage: COMMON Author: Rohan Mahy (rohan&ekabal.com)
Enumservice名： "IM" Enumservice Type： "im" Enumserviceサブタイプ：n/a URIスキーム： "IM："機能仕様：このenmserviceは、識別されたリソースが「im： 'uri」であることを示します。「IM：」URIスキームは、インスタントメッセージングの受領または配信を処理するために使用される特定のプロトコルを識別しません。むしろRFC 3861 [4]のメカニズムを使用して、パーティークエリの列挙でサポートされているIMプロトコルが列挙であるかどうかを発見します。ターゲットリソースによってサポートされています。セキュリティ上の考慮事項：[RFC5028]のセクション3を参照してください。
Enumservice Name: "voicemsg" Enumservice Type: "voicemsg" Enumservice Subtypes: "sip" URI Schemes: 'sip:' Functional Specification: This Enumservice indicates that the remote resource identified can be addressed by the associated URI scheme in order to initiate a voice communication session to a voice messaging system. Security Considerations: See Section 3 of [RFC5278] Intended Usage: COMMON Authors: Jason Livingood (jason_livingood&cable.comcast.com) Don Troshynski (dtroshynski&acmepacket.com) Any other information the author deems interesting: Implementers should review a non-exclusive list of examples below in Section 7 of [RFC5278]
Enumservice名： "Voicemsg" enumserviceタイプ： "voicemsg" enumservice subtypes： "sip" uriスキーム： 'sip：' functional仕様：このenmserviceは、識別されたリモートリソースが、声を開始するために関連するURIスキームによって対処できることを示します。音声メッセージングシステムへの通信セッション。セキュリティ上の考慮事項：[RFC5278]のセクション3を参照してください。意図した使用法：一般的な著者：Jason Livingood（jason_livingood＆cable.comcast.com）don troshynski（dtroshynski＆acmepacket.com）任意の情報著者は興味深いとみなします。[RFC5278]のセクション7の以下
Enumservice Name: "voicemsg" Enumservice Type: "voicemsg" Enumservice Subtypes: "sips" URI Schemes: 'sips:' Functional Specification: This Enumservice indicates that the remote resource identified can be addressed by the associated URI scheme in order to initiate a voice communication session to a voice messaging system. Security Considerations: See Section 3 of [RFC5278] Intended Usage: COMMON Authors: Jason Livingood (jason_livingood&cable.comcast.com) Don Troshynski (dtroshynski&acmepacket.com)
Enumservice名： "Voicemsg" enumserviceタイプ： "voicemsg" enumservice subtypes： "sips" uriスキーム： 'sips：' functional仕様：このenmserviceは、識別されたリモートリソースが、声を開始するために関連するURIスキームによって対処できることを示します。音声メッセージングシステムへの通信セッション。セキュリティ上の考慮事項：[RFC5278]のセクション3を参照してください。意図した使用法：一般的な著者：Jason Livingood（jason_livingood＆cable.comcast.com）don troshynski（dtroshynski＆acmepacket.com）
Any other information the author deems interesting: Implementers should review a non-exclusive list of examples below in Section 7 of [RFC5278]
著者が興味深いと思うその他の情報：実装者は、[RFC5278]のセクション7で以下の例の非独占的なリストを確認する必要があります。
Enumservice Name: "voicemsg" Enumservice Type: "voicemsg" Enumservice Subtype: "tel" URI Schemes: 'tel:' Functional Specification: This Enumservice indicates that the remote resource identified can be addressed by the associated URI scheme in order to initiate a voice communication session to a voice messaging system. Security Considerations: See Section 3 of [RFC5278] Intended Usage: COMMON Authors: Jason Livingood (jason_livingood&cable.comcast.com) Don Troshynski (dtroshynski&acmepacket.com) Any other information the author deems interesting: Implementers should review a non-exclusive list of examples below in Section 7 of [RFC5278]
Enumservice名： "voicemsg" enumserviceタイプ： "voicemsg" enumservice subtype： "tel" uriスキーム： 'tel：' functional仕様：このenmserviceは、識別されたリモートリソースが、声を開始するために関連するURIスキームによって対処できることを示しています。音声メッセージングシステムへの通信セッション。セキュリティ上の考慮事項：[RFC5278]のセクション3を参照してください。意図した使用法：一般的な著者：Jason Livingood（jason_livingood＆cable.comcast.com）don troshynski（dtroshynski＆acmepacket.com）任意の情報著者は興味深いとみなします。[RFC5278]のセクション7の以下
Enumservice Name: "voicemsg" Enumservice Type: "voicemsg" Enumservice Subtype: "http" URI Schemes: 'http:' Functional Specification: This Enumservice indicates that the remote resource identified by the associated URI scheme is capable of being a source of information. Note that the kind of information retrieved can be manifold. Usually, contacting a resource by an 'http:' [11] URI provides a document. This document can contain references that will trigger the download of many different kinds of information, such as text, audio, video, executable code, or even voice message files. Thus, one cannot be more specific about the kind of information expected when contacting the resource. Security Considerations: See Section 3 of [RFC5278] Intended Usage: COMMON Authors: Jason Livingood (jason_livingood&cable.comcast.com) Don Troshynski (dtroshynski&acmepacket.com) Any other information the author deems interesting: Implementers should review a non-exclusive list of examples below in Section 7 of [RFC5278]
Enumservice名： "voicemsg" enumserviceタイプ： "voicemsg" enumservice subtype： "http" uriスキーム： 'http：' functional仕様：このenmserviceは、関連するURIスキームによって識別されるリモートリソースが情報源であることを示します。取得された情報の種類は多様である可能性があることに注意してください。通常、 'http：' [11] uriでリソースに連絡することはドキュメントを提供します。このドキュメントには、テキスト、オーディオ、ビデオ、実行可能コード、または音声メッセージファイルなど、さまざまな種類の情報のダウンロードをトリガーする参照を含めることができます。したがって、リソースに連絡するときに予想される情報の種類について、より具体的にすることはできません。セキュリティ上の考慮事項：[RFC5278]のセクション3を参照してください。意図した使用法：一般的な著者：Jason Livingood（jason_livingood＆cable.comcast.com）don troshynski（dtroshynski＆acmepacket.com）任意の情報著者は興味深いとみなします。[RFC5278]のセクション7の以下
Enumservice Name: "voicemsg" Enumservice Type: "voicemsg" Enumservice Subtype: "https" URI Schemes: 'https:' Functional Specification: This Enumservice indicates that the remote resource identified by the associated URI scheme is capable of being a source of information, which can be contacted using TLS or the Secure Socket Layer protocol. Note that the kind of information retrieved can be manifold. Usually, contacting a resource by an 'https:' [12] URI provides a document. This document can contain references that will trigger the download of many different kinds of information, such as text, audio, video, executable code, or even voice message files. Thus, one cannot be more specific about the kind of information expected when contacting the resource. Security Considerations: See Section 3 of [RFC5278] Intended Usage: COMMON Authors: Jason Livingood (jason_livingood&cable.comcast.com) Don Troshynski (dtroshynski&acmepacket.com) Any other information the author deems interesting: Implementers should review a non-exclusive list of examples below in Section 7 of [RFC5278]
Enumservice名： "Voicemsg" Enumservice Type： "Voicemsg" Enumservice subtype： "https" uriスキーム： 'https：' functional Specification：このenmserviceは、関連するURIスキームによって識別されるリモートリソースが情報源であることを示しています。TLSまたは安全なソケットレイヤープロトコルを使用して連絡できます。取得された情報の種類は多様である可能性があることに注意してください。通常、 'https：' [12] uriでリソースに連絡することはドキュメントを提供します。このドキュメントには、テキスト、オーディオ、ビデオ、実行可能コード、または音声メッセージファイルなど、さまざまな種類の情報のダウンロードをトリガーする参照を含めることができます。したがって、リソースに連絡するときに予想される情報の種類について、より具体的にすることはできません。セキュリティ上の考慮事項：[RFC5278]のセクション3を参照してください。意図した使用法：一般的な著者：Jason Livingood（jason_livingood＆cable.comcast.com）don troshynski（dtroshynski＆acmepacket.com）任意の情報著者は興味深いとみなします。[RFC5278]のセクション7の以下
Enumservice Name: "videomsg" Enumservice Type: "videomsg" Enumservice Subtypes: "sip" URI Schemes: 'sip:' Functional Specification: This Enumservice indicates that the remote resource identified can be addressed by the associated URI scheme in order to initiate a video communication session to a video messaging system. Security Considerations: See Section 3 of [RFC5278] Intended Usage: COMMON Authors: Jason Livingood (jason_livingood&cable.comcast.com) Don Troshynski (dtroshynski&acmepacket.com) Any other information the author deems interesting: Implementers should review a non-exclusive list of examples below in Section 7 of [RFC5278]
Enumservice名： "VideoMsg" Enumservice Type： "VideoMsg" Enumserviceサブタイプ： "sip" uriスキーム： 'sip：' functional仕様：このenmserviceは、識別されたリモートリソースが、ビデオを開始するために関連するURIスキームによって対処できることを示します。ビデオメッセージングシステムへの通信セッション。セキュリティ上の考慮事項：[RFC5278]のセクション3を参照してください。意図した使用法：一般的な著者：Jason Livingood（jason_livingood＆cable.comcast.com）don troshynski（dtroshynski＆acmepacket.com）任意の情報著者は興味深いとみなします。[RFC5278]のセクション7の以下
Enumservice Name: "videomsg" Enumservice Type: "videomsg" Enumservice Subtypes: "sips" URI Schemes: 'sips:' Functional Specification: This Enumservice indicates that the remote resource identified can be addressed by the associated URI scheme in order to initiate a video communication session to a video messaging system. Security Considerations: See Section 3 of [RFC5278] Intended Usage: COMMON Authors: Jason Livingood (jason_livingood&cable.comcast.com) Don Troshynski (dtroshynski&acmepacket.com) Any other information the author deems interesting: Implementers should review a non-exclusive list of examples below in Section 7 of [RFC5278]
Enumservice名： "VideoMsg" Enumservice Type： "VideoMsg" Enumservice Subtypes： "sips" uri Schemes： 'sips：' functional Specification：このEnumserviceは、識別されたリモートリソースが、ビデオを開始するために関連するURIスキームによって対処できることを示します。ビデオメッセージングシステムへの通信セッション。セキュリティ上の考慮事項：[RFC5278]のセクション3を参照してください。意図した使用法：一般的な著者：Jason Livingood（jason_livingood＆cable.comcast.com）don troshynski（dtroshynski＆acmepacket.com）任意の情報著者は興味深いとみなします。[RFC5278]のセクション7の以下
Enumservice Name: "videomsg" Enumservice Type: "videomsg" Enumservice Subtype: "http" URI Schemes: 'http:' Functional Specification: This Enumservice indicates that the remote resource identified by the associated URI scheme is capable of being a source of information. Note that the kind of information retrieved can be manifold. Usually, contacting a resource by an 'http:' [11] URI provides a document. This document can contain references that will trigger the download of many different kinds of information, such as text, audio, video, executable code, or even video message files. Thus, one cannot be more specific about the kind of information expected when contacting the resource. Security Considerations: See Section 3 of [RFC5278] Intended Usage: COMMON Authors: Jason Livingood (jason_livingood&cable.comcast.com) Don Troshynski (dtroshynski&acmepacket.com) Any other information the author deems interesting: Implementers should review a non-exclusive list of examples below in Section 7 of [RFC5278]
Enumservice名： "VideoMsg" Enumservice Type： "VideoMsg" Enumservice Subtype： "http" URIスキーム： 'http：'機能仕様：このEnamserviceは、関連するURIスキームによって識別されるリモートリソースが情報源であることを示すことを示します。取得された情報の種類は多様である可能性があることに注意してください。通常、 'http：' [11] uriでリソースに連絡することはドキュメントを提供します。このドキュメントには、テキスト、オーディオ、ビデオ、実行可能コード、ビデオメッセージファイルなど、さまざまな種類の情報のダウンロードをトリガーする参照を含めることができます。したがって、リソースに連絡するときに予想される情報の種類について、より具体的にすることはできません。セキュリティ上の考慮事項：[RFC5278]のセクション3を参照してください。意図した使用法：一般的な著者：Jason Livingood（jason_livingood＆cable.comcast.com）don troshynski（dtroshynski＆acmepacket.com）任意の情報著者は興味深いとみなします。[RFC5278]のセクション7の以下
Enumservice Name: "videomsg" Enumservice Type: "videomsg" Enumservice Subtype: "https" URI Schemes: 'https:' Functional Specification: This Enumservice indicates that the remote resource identified by the associated URI scheme is capable of being a source of information, which can be contacted using TLS or the Secure Socket Layer protocol. Note that the kind of information retrieved can be manifold. Usually, contacting a resource by an 'https:' [12] URI provides a document. This document can contain references that will trigger the download of many different kinds of information, such as text, audio, video, executable code, or even video message files. Thus, one cannot be more specific about the kind of information expected when contacting the resource. Security Considerations: See Section 3 of [RFC5278] Intended Usage: COMMON Authors: Jason Livingood (jason_livingood&cable.comcast.com) Don Troshynski (dtroshynski&acmepacket.com) Any other information the author deems interesting: Implementers should review a non-exclusive list of examples below in Section 7 of [RFC5278]
Enumservice名： "VideoMsg" Enumservice Type： "VideoMsg" Enumservice Subtype： "https" URIスキーム： 'https：'機能仕様：このEnamserviceは、関連するURIスキームによって識別されるリモートリソースが情報源であることで有能であることを示しています。TLSまたは安全なソケットレイヤープロトコルを使用して連絡できます。取得された情報の種類は多様である可能性があることに注意してください。通常、 'https：' [12] uriでリソースに連絡することはドキュメントを提供します。このドキュメントには、テキスト、オーディオ、ビデオ、実行可能コード、ビデオメッセージファイルなど、さまざまな種類の情報のダウンロードをトリガーする参照を含めることができます。したがって、リソースに連絡するときに予想される情報の種類について、より具体的にすることはできません。セキュリティ上の考慮事項：[RFC5278]のセクション3を参照してください。意図した使用法：一般的な著者：Jason Livingood（jason_livingood＆cable.comcast.com）don troshynski（dtroshynski＆acmepacket.com）任意の情報著者は興味深いとみなします。[RFC5278]のセクション7の以下
Enumservice Name: "unifmsg" Enumservice Type: "unifmsg" Enumservice Subtypes: "sip" URI Schemes: 'sip:' Functional Specification: This Enumservice indicates that the remote resource identified can be addressed by the associated URI scheme in order to initiate a unified communication session to a unified messaging system. Security Considerations: See Section 3 of [RFC5278] Intended Usage: COMMON Authors: Jason Livingood (jason_livingood&cable.comcast.com) Don Troshynski (dtroshynski&acmepacket.com) Any other information the author deems interesting: Implementers should review a non-exclusive list of examples below in Section 7 of [RFC5278]
Enumservice名： "unifmsg" enumserviceタイプ： "unifmsg" enumservice subtypes： "sip" uriスキーム： 'sip：' functional仕様：このenmserviceは、特定されたリモートリソースが、統一されたURIスキームによって対処できることを示します。統一されたメッセージングシステムへの通信セッション。セキュリティ上の考慮事項：[RFC5278]のセクション3を参照してください。意図した使用法：一般的な著者：Jason Livingood（jason_livingood＆cable.comcast.com）don troshynski（dtroshynski＆acmepacket.com）任意の情報著者は興味深いとみなします。[RFC5278]のセクション7の以下
Enumservice Name: "unifmsg" Enumservice Type: "unifmsg" Enumservice Subtypes: "sips" URI Schemes: 'sips:' Functional Specification: This Enumservice indicates that the remote resource identified can be addressed by the associated URI scheme in order to initiate a unified communication session to a unified messaging system. Security Considerations: See Section 3 of [RFC5278] Intended Usage: COMMON Authors: Jason Livingood (jason_livingood&cable.comcast.com) Any other information the author deems interesting: Implementers should review a non-exclusive list of examples below in Section 7 of [RFC5278]
Enumservice名： "unifmsg" enumserviceタイプ： "unifmsg" enumservice subtypes： "sips" uriスキーム： 'sips：' functional仕様：このenmserviceは、統合されたURIスキームによって識別されたリモートリソースに対処できることを示します。統一されたメッセージングシステムへの通信セッション。セキュリティ上の考慮事項：[RFC5278]のセクション3を参照してください使用法：一般著者：Jason Livingood（jason_livingood＆cable.comcast.com）その他の情報著者は興味深いものです。]
Enumservice Name: "unifmsg" Enumservice Type: "unifmsg" Enumservice Subtype: "http" URI Schemes: 'http:' Functional Specification: This Enumservice indicates that the remote resource identified by the associated URI scheme is capable of being a source of information. Note that the kind of information retrieved can be manifold. Usually, contacting a resource by an 'http:' [11] URI provides a document. This document can contain references that will trigger the download of many different kinds of information, such as text, audio, video, executable code, or even video message files. Thus, one cannot be more specific about the kind of information expected when contacting the resource. Security Considerations: See Section 3 of [RFC5278] Intended Usage: COMMON Authors: Jason Livingood (jason_livingood&cable.comcast.com) Don Troshynski (dtroshynski&acmepacket.com) Any other information the author deems interesting: Implementers should review a non-exclusive list of examples below in Section 7 of [RFC5278]
Enumservice名： "unifmsg" enumserviceタイプ： "unifmsg" enumservice subtype： "http" uriスキーム： 'http：' functional仕様：このenmserviceは、関連するURIスキームによって識別されるリモートリソースが情報源であることで有能であることを示します。取得された情報の種類は多様である可能性があることに注意してください。通常、 'http：' [11] uriでリソースに連絡することはドキュメントを提供します。このドキュメントには、テキスト、オーディオ、ビデオ、実行可能コード、ビデオメッセージファイルなど、さまざまな種類の情報のダウンロードをトリガーする参照を含めることができます。したがって、リソースに連絡するときに予想される情報の種類について、より具体的にすることはできません。セキュリティ上の考慮事項：[RFC5278]のセクション3を参照してください。意図した使用法：一般的な著者：Jason Livingood（jason_livingood＆cable.comcast.com）don troshynski（dtroshynski＆acmepacket.com）任意の情報著者は興味深いとみなします。[RFC5278]のセクション7の以下
Enumservice Name: "unifmsg" Enumservice Type: "unifmsg" Enumservice Subtype: "https" URI Schemes: 'https:' Functional Specification: This Enumservice indicates that the remote resource identified by the associated URI scheme is capable of being a source of information, which can be contacted using TLS or the Secure Socket Layer protocol. Note that the kind of information retrieved can be manifold. Usually, contacting a resource by an 'https:' [12] URI provides a document. This document can contain references that will trigger the download of many different kinds of information, such as text, audio, video, executable code, or even video message files. Thus, one cannot be more specific about the kind of information expected when contacting the resource. Security Considerations: See Section 3 of [RFC5278] Intended Usage: COMMON Authors: Jason Livingood (jason_livingood&cable.comcast.com) Don Troshynski (dtroshynski&acmepacket.com) Any other information the author deems interesting: Implementers should review a non-exclusive list of examples below in Section 7 of [RFC5278]
Enumservice名： "unifmsg" enumserviceタイプ： "unifmsg" enumservice subtype： "https" uriスキーム： 'https：' functional仕様：このenmserviceは、関連するURIスキームによって識別されるリモートリソースが情報源であることで有能であることを示します。TLSまたは安全なソケットレイヤープロトコルを使用して連絡できます。取得された情報の種類は多様である可能性があることに注意してください。通常、 'https：' [12] uriでリソースに連絡することはドキュメントを提供します。このドキュメントには、テキスト、オーディオ、ビデオ、実行可能コード、ビデオメッセージファイルなど、さまざまな種類の情報のダウンロードをトリガーする参照を含めることができます。したがって、リソースに連絡するときに予想される情報の種類について、より具体的にすることはできません。セキュリティ上の考慮事項：[RFC5278]のセクション3を参照してください。意図した使用法：一般的な著者：Jason Livingood（jason_livingood＆cable.comcast.com）don troshynski（dtroshynski＆acmepacket.com）任意の情報著者は興味深いとみなします。[RFC5278]のセクション7の以下
Enumservice Name: "ical-sched" Enumservice Type: "ical-sched" Enumservice Subtypes: "mailto" URI scheme(s): 'mailto:' Functional Specification: This Enumservice indicates that the resource identified can be addressed by the associated URI used for scheduling using Internet calendaring via Internet mail with the iMIP [6] protocol. Security considerations: See Section 4 of [RFC5333]. Intended usage: COMMON Author: Rohan Mahy (rohan&ekabal.com)
Enumservice名： "ICALSCHED" Enumservice Type： "ICAL-sched" Enumservice Subtypes： "Mailto" URIスキーム： 'MailTo：'機能仕様：このEnumserviceは、識別されたリソースが使用されている関連するURIによって対処できることを示しています。IMIP [6]プロトコルを使用して、インターネットメールを介してインターネットカレンダーを使用してスケジュールするため。セキュリティ上の考慮事項：[RFC5333]のセクション4を参照してください。意図された使用法：共通著者：Rohan Mahy（Rohan＆Ekabal.com）
Enumservice Name: "ical-access" Enumservice Type: "ical-access" Enumservice Subtypes: "http" URI scheme(s): 'http:' Functional Specification: This Enumservice indicates that the resource identified can be addressed by the associated URI in order to access a user's calendar (for example free/busy status) using the CalDAV [7] protocol for Internet calendaring. Security considerations: See Section 4 of [RFC5333]. Intended usage: COMMON Author: Rohan Mahy (rohan&ekabal.com)
Enumservice名： "ICAL-ACCESS" Enumservice Type： "ical-access" enumservice subtypes： "http" uriスキーム： 'http：' functional仕様：識別されたリソースが、関連するURIが関連するURIによって対処できることを示します。インターネットカレンダーのためのCalDAV [7]プロトコルを使用して、ユーザーのカレンダー（たとえば無料/ビジーステータス）にアクセスするため。セキュリティ上の考慮事項：[RFC5333]のセクション4を参照してください。意図された使用法：共通著者：Rohan Mahy（Rohan＆Ekabal.com）
Enumservice Name: "ical-access" Enumservice Type: "ical-access" Enumservice Subtypes: "https" URI scheme(s): 'https:' Functional Specification: This Enumservice indicates that the resource identified can be addressed by the associated URI in order to access a user's calendar (for example free/busy status) using the CalDAV [7] protocol for Internet calendaring. Security considerations: See Section 4 of [RFC5333]. Intended usage: COMMON Author: Rohan Mahy (rohan&ekabal.com)
Enumservice名： "ICAL-ACCESS" Enumservice Type： "ical-access" enumservice subtypes： "https" uriスキーム： 'https：' functional仕様：識別されたリソースが、関連するURIが関連するURIによって対処できることを示します。インターネットカレンダーのためのCalDAV [7]プロトコルを使用して、ユーザーのカレンダー（たとえば無料/ビジーステータス）にアクセスするため。セキュリティ上の考慮事項：[RFC5333]のセクション4を参照してください。意図された使用法：共通著者：Rohan Mahy（Rohan＆Ekabal.com）
Authors' Addresses
著者のアドレス
Bernie Hoeneisen Ucom Standards Track Solutions GmbH CH-8000 Zuerich Switzerland
Bernie Hoeneisen UCom Standards Track Solutions GmbH CH-8000 Zuerich Switzerland
Phone: +41 44 500 52 44
EMail: bernie@ietf.hoeneisen.ch (bernhard.hoeneisen AT ucom.ch)
URI: http://www.ucom.ch/
Alexander Mayrhofer enum.at GmbH Karlsplatz 1/9 Wien A-1010 Austria
Alexander Mayrhofer Enum.at GmbH Karlsplatz 1/9 Wien A-1010 Austria
Phone: +43 1 5056416 34
EMail: alexander.mayrhofer@enum.at
URI: http://www.enum.at/