idnits 2.17.1 draft-ietf-mmusic-sip-url-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://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. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** Expected the document's filename to be given on the first page, but didn't find any == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 63: '... MUST NOT be used if the host part o...' Miscellaneous warnings: ---------------------------------------------------------------------------- == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (May 14, 1997) is 9843 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) -- Missing reference section? '1' on line 91 looks like a reference -- Missing reference section? '2' on line 95 looks like a reference Summary: 11 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force MMUSIC WG 3 Internet Draft H. Schulzrinne 4 ietf-mmusic-sip-url-00.txt Columbia U. 5 May 14, 1997 6 Expires: November 1, 1997 8 SIP URL Scheme 10 STATUS OF THIS MEMO 12 This document is an Internet-Draft. Internet-Drafts are working 13 documents of the Internet Engineering Task Force (IETF), its areas, 14 and its working groups. Note that other groups may also distribute 15 working documents as Internet-Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six months 18 and may be updated, replaced, or obsoleted by other documents at any 19 time. It is inappropriate to use Internet-Drafts as reference 20 material or to cite them other than as ``work in progress''. 22 To learn the current status of any Internet-Draft, please check the 23 ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow 24 Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 25 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or 26 ftp.isi.edu (US West Coast). 28 Distribution of this document is unlimited. 30 ABSTRACT 32 A family of new URL schemes, "sip*:", is defined. It is 33 used to establish multimedia conferences using the 34 Session Initiation Protocol (SIP). 36 1 URL Syntax 38 This URL does not designate a data object, but rather requests the 39 initiation of a conference with the designated party using the 40 Session Initation Protocol (SIP) [1]. The details of this conference, 41 such as the type and parameters of media to be used, are not 42 specified by this URL but may be negotiated by the protocol itself. 44 A SIP URL is based on the Common Internet Scheme Syntax described in 45 section 3.1 of RFC 1738 [2]. It has the general forms: 47 sip://:@,: 48 sips://:@,: 49 sipt://:@,: 50 sipu://:@,: 52 The " : ", " , ", " : " parts are optional. If 53 the port is omitted, then port TBD is assumed for schemes sip: , 54 sipu: , and sipt: and port TBD for scheme sips: 56 The URL scheme name also designates the transport protocol to be used 57 by SIP. For sip: , either UDP or TCP may be used, depending on the 58 preference of the entity resolving the URL. sipu: and sipt: 59 explicitly request use of UDP and TCP. sips: requests use of SSL 60 over TCP. 62 The ttl value designates the multicast time-to-live value. This field 63 MUST NOT be used if the host part of the URL is a unicast address. 64 The default value is one. The ttl value is mandatory if the host 65 address designates an IPv6 multicast address. (The textual 66 representation of IPv6 addresses contain colons and thus cannot be 67 delineated from the port identifier.) 69 2 SIP URL BNF 71 The following BNF includes the generic definitions of RFC 1738, 72 Section 5. 74 sip_URL = ( "sip:" | "sips:" | "sipt:" | "sipu:" ) "//" login 75 login = [ user [ ":" password ] "@" ] host_ttl_port 76 host_ttl_port = host [ "," ttl ] [ ":" port ] 77 ttl = digits 79 3 Author's Address 81 Henning Schulzrinne 82 Dept. of Computer Science 83 Columbia University 84 1214 Amsterdam Avenue 85 New York, MY 10027 86 USA 87 electronic mail: schulzrinne@cs.columbia.edu 89 4 Bibliography 91 [1] M. Handley, H. Schulzrinne, and E. Schooler, "SIP: session 92 initiation protocol," Internet Draft, Internet Engineering Task 93 Force, Mar. 1997. Work in progress. 95 [2] T. Berners-Lee, L. Masinter, and M. McCahill, "Uniform resource 96 locators (URL)," RFC 1738, Internet Engineering Task Force, Dec. 97 1994.