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
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)
将WebSocket协议指示为会话启动协议（SIP）公共日志格式（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.
RFC 7118将WebSocket子策略指定为会话启动协议（SIP）实体之间的可靠实时传输机制，以便在面向web的部署中使用SIP。本文档更新了RFC 6873中定义的SIP通用日志格式（CLF），为此类SIP WebSocket传输添加了新的“传输标志”。
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.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 5741第2节。
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.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7355.
Copyright Notice
版权公告
Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2014 IETF信托基金和确定为文件作者的人员。版权所有。
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.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
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
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
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.
WebSocket协议[RFC6455]支持客户端和服务器之间在持久TCP连接（可选使用TLS[RFC5246]进行保护）的基础上进行双向消息交换。初始协议握手利用HTTP[RFC7230]语义，允许WebSocket协议重用现有传输连接。
RFC 7118 [RFC7118] defines a WebSocket subprotocol for transporting SIP messages between a WebSocket client and server.
RFC 7118[RFC7118]定义了一个WebSocket子目录，用于在WebSocket客户端和服务器之间传输SIP消息。
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).
可以使用RFC 6873[RFC6873]中定义的通用日志格式记录SIP消息。为了使通过WebSocket协议传输的SIP消息的SIP CLF日志记录成为可能，必须在RFC 6873[RFC6873]中已经定义的“传输标志”（即UDP、TCP和SCTP）中添加新的WebSocket“传输标志”（“W”）。
This document updates RFC 6873 [RFC6873] by defining a new SIP CLF "Transport Flag" value for WebSocket.
本文档通过为WebSocket定义新的SIP CLF“传输标志”值来更新RFC 6873[RFC6873]。
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].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
This document contains several examples of SIP CLF records showing messages over plain and secure WebSocket connections. The formatting described in this document does not permit the examples to be unambiguously rendered due to the constraints imposed by the formatting rules for RFCs. To avoid ambiguity and to meet the RFC layout requirements, this document uses the <allOneLine/> markup convention established in [RFC4475]. This markup convention is described in detail in Section 3 of RFC 6873 [RFC6873] and used throughout that document for representing the syntax of SIP CLF records.
本文档包含几个SIP CLF记录示例，这些记录显示通过普通和安全WebSocket连接的消息。由于RFC格式规则的限制，本文档中描述的格式不允许明确呈现示例。为避免歧义并满足RFC布局要求，本文件使用[RFC4475]中建立的<allOneLine/>标记约定。RFC 6873[RFC6873]第3节详细描述了该标记约定，并在该文档中用于表示SIP CLF记录的语法。
Section 4.2 of RFC6873 [RFC6873] specifies the mandatory fields in a SIP CLF record. The fourth and fifth bytes of the five-byte "Flags Field" are the "Transport Flag" and the "Encryption Flag", respectively. SIP messages transported over both a plain and secure WebSocket connection can be clearly distinguished by appropriately setting these two flag fields.
RFC6873[RFC6873]第4.2节规定了SIP CLF记录中的必填字段。五字节“标志字段”的第四和第五字节分别是“传输标志”和“加密标志”。通过适当设置这两个标志字段，可以清楚地区分通过普通和安全WebSocket连接传输的SIP消息。
The currently registered values of the "Transport Flag" (Section 9.2 of RFC 6873) are UDP ('U'), TCP ('T'), and SCTP ('S'). This document defines and registers a new "Transport Flag" value 'W' for WebSocket transport of SIP messages and consequently updates RFC 6873 [RFC6873] and the IANA "SIP CLF Transport Flag Values" registry.
“传输标志”（RFC 6873第9.2节）的当前注册值为UDP（'U'）、TCP（'T'）和SCTP（'S'）。本文档为SIP消息的WebSocket传输定义并注册了一个新的“传输标志”值“W”，并因此更新了RFC 6873[RFC6873]和IANA“SIP CLF传输标志值”注册表。
SIP CLF records of messages transported over a plain WebSocket connection (WS) MUST set the "Transport Flag" to this new 'W' value and the "Encryption Flag" value to 'U' (Unencrypted). SIP CLF records of messages transported over a secure WebSocket (WSS) connection (i.e., WS over TLS) MUST set the "Transport Flag" to this new 'W' value and the "Encryption Flag" value to 'E' (Encrypted).
通过普通WebSocket连接（WS）传输的消息的SIP CLF记录必须将“传输标志”设置为新的“W”值，“加密标志”值设置为“U”（未加密）。通过安全WebSocket（WSS）连接（即，通过TLS的WS）传输的消息的SIP CLF记录必须将“传输标志”设置为新的“W”值，“加密标志”值设置为“e”（加密）。
The following examples show sample SIP CLF records logged for SIP messages transported over both plain and secure WebSocket connections.
以下示例显示通过普通和安全WebSocket连接传输的SIP消息的SIP CLF记录示例。
The following example represents a SIP INVITE request sent over a plain WebSocket connection. For the sake of brevity, the Session Description Protocol (SDP) [RFC4566] body is omitted.
以下示例表示通过普通WebSocket连接发送的SIP INVITE请求。为了简洁起见，省略了会话描述协议（SDP）[rfc456]主体。
INVITE sip:bob@example.com SIP/2.0
Via: SIP/2.0/WS df7jal23ls0d.invalid;branch=z9hG4bK56sdasks
From: sip:alice@example.com;tag=asdyka899
To: sip:bob@example.com
Call-ID: asidkj3ss
CSeq: 1 INVITE
Max-Forwards: 70
Date: Thu, 6 Feb 2014 15:02:03 GMT
Supported: path, outbound, gruu
Route: <sip:proxy.example.com:80;transport=ws;lr>
Contact: <sip:alice@example.com;gr=urn:uuid:f81-7dec-14a06cf1;ob>
Content-Type: application/sdp
Content-Length: 418
INVITE sip:bob@example.com SIP/2.0
Via: SIP/2.0/WS df7jal23ls0d.invalid;branch=z9hG4bK56sdasks
From: sip:alice@example.com;tag=asdyka899
To: sip:bob@example.com
Call-ID: asidkj3ss
CSeq: 1 INVITE
Max-Forwards: 70
Date: Thu, 6 Feb 2014 15:02:03 GMT
Supported: path, outbound, gruu
Route: <sip:proxy.example.com:80;transport=ws;lr>
Contact: <sip:alice@example.com;gr=urn:uuid:f81-7dec-14a06cf1;ob>
Content-Type: application/sdp
Content-Length: 418
Shown below is approximately how this message would appear as a single record in a SIP CLF logging file if encoded according to the syntax described in [RFC6873]. Due to RFC conventions, this log entry has been split into five lines, instead of the two lines that actually appear in a log file; and the tab characters have been padded out using spaces to simulate their appearance in a text terminal.
下面显示的是如果按照[RFC6873]中描述的语法进行编码，则该消息在SIP CLF日志文件中显示为单个记录的大致方式。由于RFC约定，此日志条目被分成五行，而不是实际出现在日志文件中的两行；制表符已经用空格填充，以模拟它们在文本终端中的外观。
A0000E7,0053005C005E00720080009200A600A800BE00C800D200DE00E7
<allOneLine>
1328821153.010 RORWU 1 INVITE - sip:bob@example.com
192.0.2.10:80 192.0.2.200:56485 sip:bob@example.com -
sip:alice@example.com asdyka899 asidkj3ss S1781761-88
C67651-11
</allOneLine>
A0000E7,0053005C005E00720080009200A600A800BE00C800D200DE00E7
<allOneLine>
1328821153.010 RORWU 1 INVITE - sip:bob@example.com
192.0.2.10:80 192.0.2.200:56485 sip:bob@example.com -
sip:alice@example.com asdyka899 asidkj3ss S1781761-88
C67651-11
</allOneLine>
A bit-exact version of the actual log entry is provided here, Base64 encoded [RFC4648], using the uuencode utility.
这里提供了实际日志项的位精确版本，即Base64编码的[RFC4648]，使用uuencode实用程序。
begin-base64 644 clf_ws_record QTAwMDBFNywwMDUzMDA1QzAwNUUwMDcyMDA4MDAwOTIwMEE2MDBBODAwQkUwMEM4MDBE MjAwREUwMEU3CjEzMjg4MjExNTMuMDEwCVJPUldVCTEgSU5WSVRFCS0Jc2lwOmJvYkBl eGFtcGxlLmNvbQkxOTIuMC4yLjEwOjgwCTE5Mi4wLjIuMjAwOjU2NDg1CXNpcDpib2JA ZXhhbXBsZS5jb20JLQlzaXA6YWxpY2VAZXhhbXBsZS5jb20JYXNkeWthODk5CWFzaWRr ajNzcwlTMTc4MTc2MS04OAlDNjc2NTEtMTEKCg== ====
begin-base64 644 clf W S_记录QTAWMDBFNYWWMDUZMDA1QZAWNWUWMDCYMDA4MJAWREUWMEU3CJEZMJG4MJEXNTUMDEWCJPULDVCTEG5WSVRFCS0JC2WOMJYKBL EGFTCGXLLMNVBQKXOTIYLYLJWOJWCTE5MI4WLJUMJUAWU2NDG1CXNPCDPIB2ZHBXB6YXBZZ5JB20JYXBYWY2WY2KZ2WWYKZZZY2WWWWc2Wc4KWc4YLZWc4KJJJJWcWcWc4LtWcWcWc4Tc4TjWcWcWc4TcWcWcWcWcWcWcWcWcWcW====
The original SIP CLF format can be obtained by reversing the effects of uuencode by simply applying the uudecode transform. Additionally, to recover the unencoded file, the Base64 text above may be passed as input to the following perl script (the output should be redirected to a file).
原始SIP CLF格式可以通过简单地应用uudecode变换来反转uuencode的效果来获得。此外，要恢复未编码的文件，可以将上面的Base64文本作为输入传递给以下perl脚本（输出应重定向到文件）。
<CODE BEGINS>
<代码开始>
#!/usr/bin/perl
use strict;
my $bdata = "";
use MIME::Base64;
while(<>)
{
if (/begin-base64 644 clf_ws_record/ .. /-- ==== --/)
{
if ( m/^\s*[^\s]+\s*$/)
{
$bdata = $bdata . $_;
}
}
}
print decode_base64($bdata);
#!/usr/bin/perl
use strict;
my $bdata = "";
use MIME::Base64;
while(<>)
{
if (/begin-base64 644 clf_ws_record/ .. /-- ==== --/)
{
if ( m/^\s*[^\s]+\s*$/)
{
$bdata = $bdata . $_;
}
}
}
print decode_base64($bdata);
<CODE ENDS>
<代码结束>
The following example represents a SIP INVITE request sent over a secure WebSocket connection (i.e., WebSocket over TLS [RFC5246]). For the sake of brevity, the SDP body is omitted.
以下示例表示通过安全WebSocket连接发送的SIP INVITE请求（即通过TLS[RFC5246]发送的WebSocket）。为了简洁起见，省略了SDP主体。
INVITE sip:bob@example.com SIP/2.0
Via: SIP/2.0/WSS df7jal23ls0d.invalid;branch=z9hG4bK56sdasks
From: sip:alice@example.com;tag=asdyka899
To: sip:bob@example.com
Call-ID: asidkj3ss
CSeq: 1 INVITE
Max-Forwards: 70
Date: Thu, 6 Feb 2014 15:02:03 GMT
Supported: path, outbound, gruu
Route: <sip:proxy.example.com:443;transport=ws;lr>
Contact: <sip:alice@example.com;gr=urn:uuid:f81-7dec-14a06cf1;ob>
Content-Type: application/sdp
Content-Length: 439
INVITE sip:bob@example.com SIP/2.0
Via: SIP/2.0/WSS df7jal23ls0d.invalid;branch=z9hG4bK56sdasks
From: sip:alice@example.com;tag=asdyka899
To: sip:bob@example.com
Call-ID: asidkj3ss
CSeq: 1 INVITE
Max-Forwards: 70
Date: Thu, 6 Feb 2014 15:02:03 GMT
Supported: path, outbound, gruu
Route: <sip:proxy.example.com:443;transport=ws;lr>
Contact: <sip:alice@example.com;gr=urn:uuid:f81-7dec-14a06cf1;ob>
Content-Type: application/sdp
Content-Length: 439
Shown below is approximately how this message would appear as a single record in a SIP CLF logging file if encoded according to the syntax described in [RFC6873]. Due to RFC conventions, this log entry has been split into five lines, instead of the two lines that actually appear in a log file; and the tab characters have been padded out using spaces to simulate their appearance in a text terminal.
下面显示的是如果按照[RFC6873]中描述的语法进行编码，则该消息在SIP CLF日志文件中显示为单个记录的大致方式。由于RFC约定，此日志条目被分成五行，而不是实际出现在日志文件中的两行；制表符已经用空格填充，以模拟它们在文本终端中的外观。
A0000E8,0053005C005E00720081009300A700A900BF00C900D300DF00E8
<allOneLine>
1328821153.010 RORWE 1 INVITE - sip:bob@example.com
192.0.2.10:443 192.0.2.200:56485 sip:bob@example.com -
sip:alice@example.com:5060 asdyka899 asidkj3ss S1781761-88
C67651-11
</allOneLine>
A0000E8,0053005C005E00720081009300A700A900BF00C900D300DF00E8
<allOneLine>
1328821153.010 RORWE 1 INVITE - sip:bob@example.com
192.0.2.10:443 192.0.2.200:56485 sip:bob@example.com -
sip:alice@example.com:5060 asdyka899 asidkj3ss S1781761-88
C67651-11
</allOneLine>
A bit-exact version of the actual log entry is provided here, Base64 encoded.
这里提供了实际日志项的位精确版本，Base64编码。
begin-base64 644 clf_ws_record QTAwMDBFOCwwMDUzMDA1QzAwNUUwMDcyMDA4MTAwOTMwMEE3MDBBOTAwQkYwMEM5MDBE MzAwREYwMEU4CjEzMjg4MjExNTMuMDEwCVJPUldVCTEgSU5WSVRFCS0Jc2lwOmJvYkBl eGFtcGxlLmNvbQkxOTIuMC4yLjEwOjQ0MwkxOTIuMC4yLjIwMDo1NjQ4NQlzaXA6Ym9i QGV4YW1wbGUuY29tCS0Jc2lwOmFsaWNlQGV4YW1wbGUuY29tCWFzZHlrYTg5OQlhc2lk a2ozc3MJUzE3ODE3NjEtODgJQzY3NjUxLTExCgo= ====
begin-base64 644 clf W S_记录QTAWMDBFOCWWMDUZMDA1QZAWNWUWMDCYMDA4MTAWWOWMEE3MBOTTAWQKYWMEMEMDBE MZAWREYWYWYWYWZMJJJG4MNTMUMDEWCVJULDVCTEGFCS0JC2WOMYKBL EGFTCGXLNVBQKKKKKKYCTYLYLJWOJQ4NJQQZA6YM9YM9YGV4YWZYWZYWZYWZYWQL3NQLKZYWZYWZYWZYLKZYL3NQLKZYWZYWZYLKZYLKZYLKZYLKZYLKZYLKZYLKZYLKZYLKZYLKZYLKZYLKZY====
This document merely adds a new "Transport Flag" value for the WebSocket protocol. This value may be set in a SIP CLF record, but its use does not intrinsically introduce any new security considerations. When logging protocol information, such as with SIP CLF, there are a myriad of security, privacy, and data protection issues to consider. These are exhaustively described in RFC 6872 [RFC6872] and RFC 6873 [RFC6873].
本文档仅为WebSocket协议添加了一个新的“传输标志”值。该值可以在SIP CLF记录中设置，但其使用本质上不会引入任何新的安全注意事项。在记录协议信息时，例如SIP CLF，有很多安全性、隐私和数据保护问题需要考虑。这些在RFC 6872[RFC6872]和RFC 6873[RFC6873]中有详细描述。
Any security considerations specific to the WebSocket protocol or its application as a transport for SIP are detailed in the relevant specifications (the WebSocket protocol [RFC6455] and SIP over WebSockets [RFC7118]) and are considered outside the scope of this document.
相关规范（WebSocket协议[RFC6455]和WebSocket上的SIP[RFC7118]）中详细说明了WebSocket协议或其作为SIP传输的应用所特有的任何安全注意事项，这些注意事项不在本文件的范围内。
This document defines a new value ('W') for SIP CLF "Transport Flag". IANA has registered this value in the "SIP CLF Transport Flag Values" registry, as shown in Table 1 below.
本文档为SIP CLF“传输标志”定义了一个新值（“W”）。IANA已在“SIP CLF传输标志值”注册表中注册了该值，如下表1所示。
+-------+--------------------+--------------------+
| Value | Transport Protocol | Reference |
+-------+--------------------+--------------------+
| W | WebSocket | RFC 7118, RFC 7355 |
+-------+--------------------+--------------------+
+-------+--------------------+--------------------+
| Value | Transport Protocol | Reference |
+-------+--------------------+--------------------+
| W | WebSocket | RFC 7118, RFC 7355 |
+-------+--------------------+--------------------+
Table 1: IANA-Registered SIP CLF Transport Flag
表1:IANA注册的SIP CLF传输标志
The authors would like to thank Vijay Gurbani for shepherding this document and Area Director Richard Barnes for his sponsorship. This work benefitted from the thorough review and constructive comments of Richard Barnes, Barry Leiba, Benoit Claise, Pete Resnick, Stephen Farrel, and Vijay Gurbani.
作者要感谢Vijay Gurbani对本文件的指导以及区域总监Richard Barnes的赞助。这项工作得益于Richard Barnes、Barry Leiba、Benoit Claise、Pete Resnick、Stephen Farrel和Vijay Gurbani的全面审查和建设性评论。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC6455] Fette, I. and A. Melnikov, "The WebSocket Protocol", RFC 6455, December 2011.
[RFC6455]Fette，I.和A.Melnikov，“WebSocket协议”，RFC 64552011年12月。
[RFC6872] Gurbani, V., Burger, E., Anjali, T., Abdelnur, H., and O. Festor, "The Common Log Format (CLF) for the Session Initiation Protocol (SIP): Framework and Information Model", RFC 6872, February 2013.
[RFC6872]Gurbani，V.，Burger，E.，Anjali，T.，Abdelnur，H.，和O.Festor，“会话启动协议（SIP）的通用日志格式（CLF）：框架和信息模型”，RFC 6872，2013年2月。
[RFC6873] Salgueiro, G., Gurbani, V., and A. Roach, "Format for the Session Initiation Protocol (SIP) Common Log Format (CLF)", RFC 6873, February 2013.
[RFC6873]Salgueiro，G.，Gurbani，V.，和A.Roach，“会话启动协议（SIP）通用日志格式（CLF）的格式”，RFC 68732013年2月。
[RFC7118] Baz Castillo, I., Millan Villegas, J., and V. Pascual, "The WebSocket Protocol as a Transport for the Session Initiation Protocol (SIP)", RFC 7118, January 2014.
[RFC7118]Baz Castillo，I.，Millan Villegas，J.，和V.Pascual，“作为会话启动协议（SIP）传输的WebSocket协议”，RFC 7118，2014年1月。
[RFC4475] Sparks, R., Hawrylyshen, A., Johnston, A., Rosenberg, J., and H. Schulzrinne, "Session Initiation Protocol (SIP) Torture Test Messages", RFC 4475, May 2006.
[RFC4475]Sparks，R.，Hawrylyshen，A.，Johnston，A.，Rosenberg，J.，和H.Schulzrinne，“会话启动协议（SIP）酷刑测试消息”，RFC 4475，2006年5月。
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session Description Protocol", RFC 4566, July 2006.
[RFC4566]Handley，M.，Jacobson，V.，和C.Perkins，“SDP：会话描述协议”，RFC4566，2006年7月。
[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data Encodings", RFC 4648, October 2006.
[RFC4648]Josefsson，S.，“Base16、Base32和Base64数据编码”，RFC4648，2006年10月。
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS) Protocol Version 1.2", RFC 5246, August 2008.
[RFC5246]Dierks，T.和E.Rescorla，“传输层安全（TLS）协议版本1.2”，RFC 5246，2008年8月。
[RFC7230] Fielding, R. and J. Reschke, "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing", RFC 7230, June 2014.
[RFC7230]Fielding，R.和J.Reschke，“超文本传输协议（HTTP/1.1）：消息语法和路由”，RFC 7230，2014年6月。
Authors' Addresses
作者地址
Gonzalo Salgueiro Cisco Systems, Inc. 7200-12 Kit Creek Road Research Triangle Park, NC 27709 US
Gonzalo Salgueiro Cisco Systems，Inc.美国北卡罗来纳州Kit Creek Road研究三角公园7200-12号，邮编27709
EMail: gsalguei@cisco.com
EMail: gsalguei@cisco.com
Victor Pascual Quobis
维克多·帕斯夸尔·库比斯
EMail: victor.pascual@quobis.com
EMail: victor.pascual@quobis.com
Anton Roman Quobis
安东·罗曼·库比斯
EMail: anton.roman@quobis.com
EMail: anton.roman@quobis.com
Sergio Garcia Ramos Quobis
塞尔吉奥·加西亚·拉莫斯·库比斯
EMail: sergio.garcia@quobis.com
EMail: sergio.garcia@quobis.com