idnits 2.17.1 draft-hildebrand-xmpp-sdpng-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == 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 separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There is 1 instance of too long lines in the document, the longest one being 3 characters in excess of 72. ** There are 5 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- 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 (February 21, 2003) is 7734 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) == Unused Reference: '5' is defined on line 279, but no explicit reference was found in the text == Outdated reference: A later version (-08) exists of draft-ietf-mmusic-sdpng-05 == Outdated reference: A later version (-24) exists of draft-ietf-xmpp-core-03 -- Possible downref: Non-RFC (?) normative reference: ref. '5' Summary: 4 errors (**), 0 flaws (~~), 6 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Hildebrand 3 Internet-Draft Jabber, Inc. 4 Expires: August 22, 2003 February 21, 2003 6 TINS: A Transport for Initiating and Negotiating Sessions using SDPng 7 over XMPP 8 draft-hildebrand-xmpp-sdpng-00 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with 13 all provisions of Section 10 of RFC2026. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that 17 other groups may also distribute working documents as Internet- 18 Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at http:// 26 www.ietf.org/ietf/1id-abstracts.txt. 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 This Internet-Draft will expire on August 22, 2003. 33 Copyright Notice 35 Copyright (C) The Internet Society (2003). All Rights Reserved. 37 Abstract 39 This document describes a method of initiating and negotiating media 40 sessions by using SDPng on top of the eXtensible Messaging and 41 Presence Protocol (XMPP) as the signalling protocol. 43 Table of Contents 45 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 46 1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 47 1.2 Discussion Venue . . . . . . . . . . . . . . . . . . . . . . . 3 48 1.3 Intellectual Property Notice . . . . . . . . . . . . . . . . . 3 49 2. Stanza Flow Overview . . . . . . . . . . . . . . . . . . . . . 4 50 3. Transactions . . . . . . . . . . . . . . . . . . . . . . . . . 8 51 4. TINS Methods . . . . . . . . . . . . . . . . . . . . . . . . . 9 52 4.1 INVITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 53 4.2 ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 54 4.3 BYE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 55 5. Results . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 56 6. Security Considerations . . . . . . . . . . . . . . . . . . . 11 57 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 58 References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 59 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 13 60 Full Copyright Statement . . . . . . . . . . . . . . . . . . . 14 62 1. Introduction 64 The MMUSIC WG has defined an XML format for Session Description and 65 Capability Negotiation (SDPng [1]). Given the availability of a 66 native XML transport in the form of the Extensible Messaging and 67 Presence Protocol (XMPP [2]), it may be valuable to explore how to 68 build a framework for media stream/session initiation and negotiation 69 over XMPP. This document explores such a framework, with SDPng over 70 XMPP providing a semantics for signalling call setup that is similar 71 to the semantics alternatively provided by the Session Initiation 72 Protocol (SIP [3]). 74 1.1 Terminology 76 This document inherits terminology defined in SDPng [1] and in XMPP 77 Core [2]. 79 The capitalized key words "MUST", "MUST NOT", "REQUIRED", "SHALL", 80 "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 81 "OPTIONAL" in this document are to be interpreted as described in RFC 82 2119 [4]. 84 1.2 Discussion Venue 86 The author welcomes discussion and comments related to the topics 87 presented in this document. The preferred forum is the 88 mailing list, for which archives and subscription 89 information are available at . 92 1.3 Intellectual Property Notice 94 This document is in full compliance with all provisions of Section 10 95 of RFC 2026. 97 2. Stanza Flow Overview 99 The following is an example flow of XMPP stanzas to initiate a call. 100 The from addresses will usually be added by the XMPP server, but are 101 shown for clarity. 103 Step 1: A sends an invite to B: 105 106 1234@hostA.example.com 107 This message contains a TINS invite, 108 but your client does not support TINS. 109 112 113 116 118 120 121 122 123 125 127 128 129 130 132 133 135 137 138 Telephony media stream 139 140 141 142 143 Step 2: B tells A that it is trying: 145 146 1234@hostA.example.com 147 149 151 Step 3: B tells A that it is ringing: 153 154 1234@hostA.example.com 155 157 158 Step 4: B sends A updated description: 160 161 1234@hostA.example.com 162 165 166 169 171 173 174 175 176 178 180 182 183 184 185 186 187 189 Step 5: A sends an ACKnowldgement: 191 192 1234@hostA.example.com 193 195 196 Step 6: B hangs up: 198 199 1234@hostA.example.com 200 202 204 Step 7: A acknowledges the hang up: 206 207 1234@hostA.example.com 208 210 212 3. Transactions 214 The element from XMPP is used to group TINS messages 215 together into a shared context. A unique thread value MUST be used 216 for each transaction. An example of a transaction might be a single 217 voice call. 219 4. TINS Methods 221 The following methods can be used in a TINS message. 223 4.1 INVITE 225 Invite the target user to an out-of-band session. The content inside 226 the element MAY be SDPng descriptions of the connection types 227 offered. If a session is already established for this transaction, 228 the new INVITE serves as a renegotiation of session parameters. 230 4.2 ACK 232 The initiator tells the invitee that an out-of-band session has been 233 established. 235 4.3 BYE 237 Either side of the conversation decides to terminate the transaction. 238 This message SHOULD cause all resources associated with this 239 transaction to be freed, and any associated network connections to be 240 terminated. 242 5. Results 244 In reply to each of the method messages, the receiver sends 0 or more 245 replies, with the method set to 'result'. Result codes are as 246 specified in RFC 3261, section 21. 248 6. Security Considerations 250 TINS is subject to the same security considerations as XMPP, 251 particularly with regard to authentication and channel encryption. 253 This document does not describe how the media protocols (e.g. RTP) 254 traverse firewalls and NATs. 256 There is no general-purpose way to ensure that media protocol 257 connections are associated with the in-band TINS conversation. 259 7. IANA Considerations 261 None 263 References 265 [1] Ott, J., Bormann, C. and D. Kutscher, "Session Description and 266 Capability Negotiation", draft-ietf-mmusic-sdpng-05 (work in 267 progress), July 2002. 269 [2] Saint-Andre, P. and J. Miller, "XMPP Core (draft-ietf-xmpp-core- 270 03, work in progress)", February 2003. 272 [3] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., 273 Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP: 274 Session Initiation Protocol", RFC 3261, June 2002. 276 [4] Bradner, S., "Key words for use in RFCs to Indicate Requirement 277 Levels", BCP 14, RFC 2119, March 1997. 279 [5] Internet Assigned Numbers Authority, "Internet Assigned Numbers 280 Authority", January 1998, . 282 Author's Address 284 Joe Hildebrand 285 Jabber, Inc. 287 EMail: jhildebrand@jabber.com 288 URI: http://www.jabber.com/ 290 Full Copyright Statement 292 Copyright (C) The Internet Society (2003). All Rights Reserved. 294 This document and translations of it may be copied and furnished to 295 others, and derivative works that comment on or otherwise explain it 296 or assist in its implementation may be prepared, copied, published 297 and distributed, in whole or in part, without restriction of any 298 kind, provided that the above copyright notice and this paragraph are 299 included on all such copies and derivative works. However, this 300 document itself may not be modified in any way, such as by removing 301 the copyright notice or references to the Internet Society or other 302 Internet organizations, except as needed for the purpose of 303 developing Internet standards in which case the procedures for 304 copyrights defined in the Internet Standards process must be 305 followed, or as required to translate it into languages other than 306 English. 308 The limited permissions granted above are perpetual and will not be 309 revoked by the Internet Society or its successors or assigns. 311 This document and the information contained herein is provided on an 312 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 313 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 314 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 315 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 316 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 318 Acknowledgement 320 Funding for the RFC Editor function is currently provided by the 321 Internet Society.