Indicating WebSocket Protocol as a Transport in the Session Initiation Protocol (SIP) Common Log Format (CLF)
RFC 7355
| Document | Type |
RFC - Informational
(September 2014; No errata)
Updates RFC 6873
Was draft-salgueiro-dispatch-websocket-sipclf (individual in rai area)
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | (None) | |
| Document shepherd | Vijay Gurbani | ||
| Shepherd write-up | Show (last changed 2014-05-02) | ||
| IESG | IESG state | RFC 7355 (Informational) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Richard Barnes | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) G. Salgueiro
Request for Comments: 7355 Cisco
Updates: 6873 V. Pascual
Category: Informational A. Roman
ISSN: 2070-1721 S. Garcia
Quobis
September 2014
Indicating WebSocket Protocol as a Transport
in the Session Initiation Protocol (SIP) Common Log Format (CLF)
Abstract
RFC 7118 specifies a WebSocket subprotocol as a reliable real-time
transport mechanism between Session Initiation Protocol (SIP)
entities to enable usage of SIP in web-oriented deployments. This
document updates the SIP Common Log Format (CLF), defined in RFC
6873, with a new "Transport Flag" for such SIP WebSocket transport.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7355.
Salgueiro, et al. Informational [Page 1]
RFC 7355 WebSocket Transport in SIP CLF September 2014
Copyright Notice
Copyright (c) 2014 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
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
3. Document Conventions . . . . . . . . . . . . . . . . . . . . 3
4. Usage of the WebSocket Transport Flag . . . . . . . . . . . . 3
5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.1. SIP over WebSocket (WS) . . . . . . . . . . . . . . . . . 4
5.2. SIP over Secure WebSocket (WSS) . . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
9.1. Normative References . . . . . . . . . . . . . . . . . . 8
9.2. Informative References . . . . . . . . . . . . . . . . . 8
Salgueiro, et al. Informational [Page 2]
RFC 7355 WebSocket Transport in SIP CLF September 2014
1. Introduction
The WebSocket protocol [RFC6455] enables bidirectional message
exchange between clients and servers on top of a persistent TCP
connection (optionally secured with TLS [RFC5246]). The initial
protocol handshake makes use of HTTP [RFC7230] semantics, allowing
the WebSocket protocol to reuse existing transport connections.
RFC 7118 [RFC7118] defines a WebSocket subprotocol for transporting
SIP messages between a WebSocket client and server.
SIP messages can be logged using the Common Log Format defined in RFC
6873 [RFC6873]. In order to make such SIP CLF logging possible for
SIP messages transported over the WebSocket protocol, a new WebSocket
"Transport Flag" ('W') must be added to the "Transport Flags" already
defined in RFC 6873 [RFC6873] (i.e., UDP, TCP, and SCTP).
This document updates RFC 6873 [RFC6873] by defining a new SIP CLF
"Transport Flag" value for WebSocket.
2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
3. Document Conventions
This document contains several examples of SIP CLF records showing
messages over plain and secure WebSocket connections. The formatting
Show full document text