The WebSocket Protocol as a Transport for the Session Initiation Protocol (SIP)
draft-ietf-sipcore-sip-websocket-05

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05
• 06
• 07
• 08
• 09
• 10

SIPCORE Working Group                                    I. Baz Castillo
Internet-Draft                                        J. Millan Villegas
Updates: 3261 (if approved)                                    Versatica
Intended status: Standards Track                              V. Pascual
Expires: April 24, 2013                                      Acme Packet
                                                        October 21, 2012

    The WebSocket Protocol as a Transport for the Session Initiation
                             Protocol (SIP)
                  draft-ietf-sipcore-sip-websocket-05

Abstract

   The WebSocket protocol enables two-way realtime communication between
   clients and servers.  This document specifies a new WebSocket sub-
   protocol as a reliable transport mechanism between SIP (Session
   Initiation Protocol) entities to enable usage of SIP in new
   scenarios.  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 April 24, 2013.

Copyright Notice

   Copyright (c) 2012 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
   to this document.  Code Components extracted from this document must

Baz Castillo, et al.     Expires April 24, 2013                 [Page 1]
Internet-Draft      WebSocket as a Transport for SIP        October 2012

   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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
     2.1.  Definitions  . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  The WebSocket Protocol . . . . . . . . . . . . . . . . . . . .  4
   4.  The WebSocket SIP Sub-Protocol . . . . . . . . . . . . . . . .  4
     4.1.  Handshake  . . . . . . . . . . . . . . . . . . . . . . . .  5
     4.2.  SIP encoding . . . . . . . . . . . . . . . . . . . . . . .  5
   5.  SIP WebSocket Transport  . . . . . . . . . . . . . . . . . . .  5
     5.1.  General  . . . . . . . . . . . . . . . . . . . . . . . . .  6
     5.2.  Updates to RFC 3261  . . . . . . . . . . . . . . . . . . .  6
       5.2.1.  Via Transport Parameter  . . . . . . . . . . . . . . .  6
       5.2.2.  SIP URI Transport Parameter  . . . . . . . . . . . . .  6
       5.2.3.  Via received parameter . . . . . . . . . . . . . . . .  7
       5.2.4.  SIP transport implementation requirements  . . . . . .  7
     5.3.  Locating a SIP Server  . . . . . . . . . . . . . . . . . .  8
   6.  Connection Keep Alive  . . . . . . . . . . . . . . . . . . . .  8
   7.  Authentication . . . . . . . . . . . . . . . . . . . . . . . .  9
   8.  Examples . . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     8.1.  Registration . . . . . . . . . . . . . . . . . . . . . . .  9
     8.2.  INVITE dialog through a proxy  . . . . . . . . . . . . . . 11
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 15
     9.1.  Secure WebSocket Connection  . . . . . . . . . . . . . . . 15
     9.2.  Usage of SIPS Scheme . . . . . . . . . . . . . . . . . . . 16
   10. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 16
     10.1. Registration of the WebSocket SIP Sub-Protocol . . . . . . 16
     10.2. Registration of new NAPTR service field values . . . . . . 16
     10.3. SIP/SIPS URI Parameters Sub-Registry . . . . . . . . . . . 16
     10.4. Header Fields Sub-Registry . . . . . . . . . . . . . . . . 17
     10.5. Header Field Parameters and Parameter Values
           Sub-Registry . . . . . . . . . . . . . . . . . . . . . . . 17
   11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17
   12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
     12.1. Normative References . . . . . . . . . . . . . . . . . . . 17
     12.2. Informative References . . . . . . . . . . . . . . . . . . 18