Internet Engineering Task Force Internet Draft Schulzrinne draft-schulzrinne-sip-urls-00.txt Columbia U. April 22, 2001 Expires: December 2001 SIP URLs for Common Services, Roles and Functions STATUS OF THIS MEMO This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress". The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt To view the list Internet-Draft Shadow Directories, see http://www.ietf.org/shadow.html. Abstract This document defines a number of names for common services, roles and functions found in SIP-based voice-over-IP networks. It extends RFC 2142. 1 Terminology In this document, the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALLNOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in RFC 2119 [1] and indicate requirement levels for compliant implementations. 2 Common Functional Names The names below SHOULD be reachable by SMTP (email), instant messaging [2] as well as SIP [3], in both lower-case, upper-case and Schulzrinne [Page 1] Internet Draft SIP URLs April 22, 2001 combinations thereof. (For example, variations such as Sos, SoS, SOS should all be valid.) This extends the names enumerated in RFC 2142 [4]. sos emergency services for members of this organization [5] 911 alias for "sos" 112 alias for "sos" operator voice operator for organization sipmaster contact for technical issues with SIP services voicemail voicemail address (see also RFC 3087 [6]) TBD: Conferences? 3 Functional Designations sales sales department info general, typically automated, information help general help, e.g., with locating other resources within an organization support marketing See Section 3, RFC 2142. Any functional name designated by an email aliases SHOULD also be available via SIP. Local language versions of these names SHOULD also be defined. 4 Naming Users It is RECOMMENDED that organizations allow "first.last" and "first.m.last" (where "m" is the middle initial) as aliases for their users, with variations that differ only in the case of the letters, such as "First.Last" or "FIRST.M.LAST" considered equivalent to the canonical all-lower-case form. 5 Bibliography [1] S. Bradner, "Key words for use in RFCs to indicate requirement levels," Request for Comments 2119, Internet Engineering Task Force, Mar. 1997. [2] M. Day, J. Rosenberg, and H. Sugano, "A model for presence and instant messaging," Request for Comments 2778, Internet Engineering Task Force, Feb. 2000. Schulzrinne [Page 2] Internet Draft SIP URLs April 22, 2001 [3] M. Handley, H. Schulzrinne, E. Schooler, and J. Rosenberg, "SIP: session initiation protocol," Request for Comments 2543, Internet Engineering Task Force, Mar. 1999. [4] D. Crocker, "Mailbox names for common services, roles and functions," Request for Comments 2142, Internet Engineering Task Force, May 1997. [5] H. Schulzrinne, "Providing emergency call services for SIP-based internet telephony," Internet Draft, Internet Engineering Task Force, Mar. 2001. Work in progress. [6] B. Campbell and R. Sparks, "Control of service context using SIP Request-URI," Request for Comments 3087, Internet Engineering Task Force, Apr. 2001. 6 Acknowledgements TBD. 7 Authors' Addresses Henning Schulzrinne Dept. of Computer Science Columbia University 1214 Amsterdam Avenue New York, NY 10027 USA electronic mail: schulzrinne@cs.columbia.edu Schulzrinne [Page 3]