idnits 2.17.1 draft-loreto-simple-im-srv-label-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (Jan 15, 2009) is 5580 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 SIMPLE Working Group S. Loreto 3 Internet-Draft Ericsson 4 Intended status: Standards Track Jan 15, 2009 5 Expires: July 19, 2009 7 Internet Assigned Numbers Authority (IANA) Registration of Instant 8 Messaging and Presence DNS SRV RRs for the Session Initiation Protocol 9 (SIP) 10 draft-loreto-simple-im-srv-label-03 12 Status of this Memo 14 This Internet-Draft is submitted to IETF in full conformance with the 15 provisions of BCP 78 and BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on July 19, 2009. 35 Copyright Notice 37 Copyright (c) 2009 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. 47 Abstract 49 This document registers with IANA two new DNS SRV Protocol Labels for 50 resolving Instant Messaging and Presence services with SIP. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 3. DNS SRV usage of SIP with 'im' and 'pres' URIs . . . . . . . . 3 57 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 58 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 59 5.1. Instant Messaging SRV Protocol Label Registration . . . . . 4 60 5.2. Presence SRV Protocol Label Registration . . . . . . . . . 5 61 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5 62 7. Normative References . . . . . . . . . . . . . . . . . . . . . 5 63 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 65 1. Introduction 67 The Service Record (SRV) [RFC2782] identifies the host(s) that will 68 support particular services. The DNS is queried for SRV RR in the 69 general form: 71 _Service._Proto.Name 73 Service: the symbolic name of the desired service. 74 Proto: the protocol of the desired service 75 Name: the domain name for which this record is valid. 77 Address Resolution for Instant Messaging and Presence [RFC3861] 78 provides guidance for locating the services associated with URIs that 79 employ two Uniform Resource Identifier (URI) [RFC3986]: 'im' for 80 INSTANT INBOXes [RFC3860] and 'pres' for PRESENTITIES [RFC3859]. 82 In order to ensure that the association between "_im" and "_pres" and 83 their respective underlying services are deterministic, the IANA has 84 created two independent registries: the Instant Messaging SRV 85 Protocol Label registry and the Presence SRV Protocol Label registry. 87 This document defines and registers the "_sip" protocol label in both 88 registries so that computer programs can resolve 'im:' and 'pres:' 89 URIs down to SIP addresses. 91 Moreover this document explains how the SIP usage for Presence and 92 Instant Messaging protocol uses SRV. 94 2. Terminology 96 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 97 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 98 document are to be interpreted as described in RFC 2119 [RFC2119]. 100 3. DNS SRV usage of SIP with 'im' and 'pres' URIs 102 Altough there are standard procedures for resolving im and pres URI 103 (section 3 of [RFC3861]), the labels for SIP are not registered. 105 Section 5 of [RFC3428] states that if a UA is presented with an IM 106 URI (e.g."im:fred@example.com") as the address for an instant 107 message, it SHOULD resolve it to a SIP URI, and place the resulting 108 URI in the Request-URI of the MESSAGE request before sending". 110 Following the procedures defined in [RFC3861], in order to resolve 111 the IM URI the UA performs a SRV lookup for: 113 _im._sip.example.com 115 Assuming that the example.com domain offers a SIP service for instant 116 messaging at simple.example.com, this will result in a resolution of 117 _im._sip.example.com. to simple.example.com. Thus the instant 118 messaging URI im:fred@example.com would resolve to a SIP URI of 119 sip:fred@simple.example.com. 121 Section 5 of [RFC3856] states that procedures defined in [RFC3861] 122 are also used to resolve the protocol-independent PRES URI for a 123 presentity (e.g. "pres:fred@example.com") into a SIP URI. 125 Following the procedures defined in [RFC3861], in order to resolve 126 the PRES URI the UA performs a SRV lookup for: 128 _pres._sip.example.com 130 Assuming that the example.com domain offers a SIP presence service at 131 simple.example.com, this will result in a resolution of 132 _pres._sip.example.com. to simple.example.com. Thus the protocol 133 independent PRES URI pres:fred@example.com would resolve to a SIP URI 134 of sip:fred@simple.example.com. 136 4. Security Considerations 138 This document merely serves for the registration of DNS SRV labels in 139 the appropriate IANA registry. The document does not specify a 140 protocol, therefore, there are no security issues associated with it. 142 5. IANA Considerations 144 This specification registers a new SRV Protocol Label in each of the 145 Instant Messaging SRV Protocol Label registry and the Presence SRV 146 Protocol Label registry, respectively. 148 5.1. Instant Messaging SRV Protocol Label Registration 150 Address Resolution for Instant Messaging and Presence[RFC3861] 151 defines an Instant Messaging SRV Protocol Label registry for 152 protocols that can provide services that conform to the "_im" SRV 153 Service label. Because SIP is one such protocol, IANA registers the 154 "_sip" protocol label in the "Instant Messaging SRV Protocol Label 155 Registry", as follows: 157 Protocol label: _sip 158 Specification: RFCXXXX 159 Description: Instant messaging protocol label for the SIP usage for 160 Presence and Instant Messaging protocol as defined by [RFC3428]. 161 Registrant Contact: Salvatore Loreto 163 5.2. Presence SRV Protocol Label Registration 165 Address Resolution for Instant Messaging and Presence [RFC3861] 166 defines a Presence SRV Protocol Label registry for protocols that can 167 provide services that conform to the "_pres" SRV Service label. 168 Because SIP usage for Presence and Instant Messaging is one such 169 protocol, the IANA registers the "_sip" protocol label in the 170 "Presence SRV Protocol Label Registry", as follows: 172 Protocol label: _sip 173 Specification: RFCXXXX 174 Description: Presence protocol label for the SIP usage for Presence 175 and Instant Messaging protocol as defined by [RFC3856]. 176 Registrant Contact: Salvatore Loreto 178 Note to RFC editor: Please replace RFCXXXX with the RFC number 179 assigned to this document. 181 6. Acknowledgments 183 The need for this registration was discussed with Jon Peterson and 184 Peter Saint-Andre. 186 Miguel Garcia reviewed this document on behalf of the Real-time 187 Applications and Infrastructure (RAI) Area Review Team (ART). 189 7. Normative References 191 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 192 Requirement Levels", BCP 14, RFC 2119, March 1997. 194 [RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for 195 specifying the location of services (DNS SRV)", RFC 2782, 196 February 2000. 198 [RFC3428] Campbell, B., Rosenberg, J., Schulzrinne, H., Huitema, C., 199 and D. Gurle, "Session Initiation Protocol (SIP) Extension 200 for Instant Messaging", RFC 3428, December 2002. 202 [RFC3856] Rosenberg, J., "A Presence Event Package for the Session 203 Initiation Protocol (SIP)", RFC 3856, August 2004. 205 [RFC3859] Peterson, J., "Common Profile for Presence (CPP)", 206 RFC 3859, August 2004. 208 [RFC3860] Peterson, J., "Common Profile for Instant Messaging 209 (CPIM)", RFC 3860, August 2004. 211 [RFC3861] Peterson, J., "Address Resolution for Instant Messaging 212 and Presence", RFC 3861, August 2004. 214 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 215 Resource Identifier (URI): Generic Syntax", STD 66, 216 RFC 3986, January 2005. 218 Author's Address 220 Salvatore Loreto 221 Ericsson 222 Hirsalantie 11 223 Jorvas 02420 224 Finland 226 Email: Salvatore.Loreto@ericsson.com