The WebSocket Protocol as a Transport for the Session Initiation Protocol (SIP)
draft-ietf-sipcore-sip-websocket-09
The information below is for an old version of the document | |||
---|---|---|---|
Document | Type | Active Internet-Draft (sipcore WG) | |
Authors | Inaki Castillo , Jose Millan , Victor Pascual | ||
Last updated | 2013-06-13 (latest revision 2013-06-12) | ||
Replaces | draft-ibc-sipcore-sip-websocket | ||
Stream | IETF | ||
Intended RFC status | Proposed Standard | ||
Formats | pdf htmlized (tools) htmlized bibtex | ||
Reviews | |||
Stream | WG state | WG Document | |
Document shepherd | Paul Kyzivat | ||
IESG | IESG state | IESG Evaluation::Revised I-D Needed | |
Consensus Boilerplate | Unknown | ||
Telechat date |
Needs a YES. Needs 9 more YES or NO OBJECTION positions to pass. |
||
Responsible AD | Richard Barnes | ||
IESG note | Paul Kyzivat (pkyzivat@alum.mit.edu) is the document shepherd. | ||
Send notices to | sipcore-chairs@tools.ietf.org, draft-ietf-sipcore-sip-websocket@tools.ietf.org | ||
IANA | IANA review state | IANA OK - Actions Needed |
SIPCORE Working Group I. Baz Castillo Internet-Draft J. Millan Villegas Updates: 3261 (if approved) Versatica Intended status: Standards Track V. Pascual Expires: December 15, 2013 Acme Packet June 13, 2013 The WebSocket Protocol as a Transport for the Session Initiation Protocol (SIP) draft-ietf-sipcore-sip-websocket-09 Abstract The WebSocket protocol enables two-way realtime communication between clients and servers in web-based applications. This document specifies a WebSocket sub-protocol as a reliable transport mechanism between SIP (Session Initiation Protocol) entities to enable usage of SIP in web-oriented deployments. This document normatively updates RFC 3261. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. 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." This Internet-Draft will expire on December 15, 2013. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. 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 Baz Castillo, et al. Expires December 15, 2013 [Page 1] Internet-Draft WebSocket as a Transport for SIP June 2013 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. Baz Castillo, et al. Expires December 15, 2013 [Page 2] Internet-Draft WebSocket as a Transport for SIP June 2013 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Definitions . . . . . . . . . . . . . . . . . . . . . . . 4 3. The WebSocket Protocol . . . . . . . . . . . . . . . . . . . . 5 4. The WebSocket SIP Sub-Protocol . . . . . . . . . . . . . . . . 5 4.1. Handshake . . . . . . . . . . . . . . . . . . . . . . . . 6 4.2. SIP Encoding . . . . . . . . . . . . . . . . . . . . . . . 6 5. SIP WebSocket Transport . . . . . . . . . . . . . . . . . . . 7 5.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 7 5.2. Updates to RFC 3261 . . . . . . . . . . . . . . . . . . . 7 5.2.1. Via Transport Parameter . . . . . . . . . . . . . . . 7 5.2.2. SIP URI Transport Parameter . . . . . . . . . . . . . 7 5.2.3. Via received Parameter . . . . . . . . . . . . . . . . 8 5.2.4. SIP Transport Implementation Requirements . . . . . . 8 5.3. Locating a SIP Server . . . . . . . . . . . . . . . . . . 9 6. Connection Keep-Alive . . . . . . . . . . . . . . . . . . . . 9 7. Authentication . . . . . . . . . . . . . . . . . . . . . . . . 10 8. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 8.1. Registration . . . . . . . . . . . . . . . . . . . . . . . 11 8.2. INVITE Dialog through a Proxy . . . . . . . . . . . . . . 12 9. Security Considerations . . . . . . . . . . . . . . . . . . . 16 9.1. Secure WebSocket Connection . . . . . . . . . . . . . . . 16 9.2. Usage of SIPS Scheme . . . . . . . . . . . . . . . . . . . 17 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 10.1. Registration of the WebSocket SIP Sub-Protocol . . . . . . 17 10.2. Registration of new NAPTR Service Field Values . . . . . . 17 10.3. SIP/SIPS URI Parameters Sub-Registry . . . . . . . . . . . 18 10.4. Header Fields Sub-Registry . . . . . . . . . . . . . . . . 18 10.5. Header Field Parameters and Parameter Values Sub-Registry . . . . . . . . . . . . . . . . . . . . . . . 18 10.6. SIP Transport Sub-Registry . . . . . . . . . . . . . . . . 18Show full document text