TLS ALPN usage in the Session Initiation Protocol (SIP)
draft-johansson-sip-alpn-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Olle E. Johansson | ||
| Last updated | 2022-08-25 (Latest revision 2022-02-21) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Many SIP specifications use other protocols in addition to the core SIP protocol, like HTTP and MSRP. In order to be able to use multiple protocols on the same port with TLS, a TLS Application Protocol Negotiation Extension (ALPN) protocol ID is needed (RFC 7301 [RFC7301]). This document registers "sip/2" as the ALPN protocol ID for the SIP protocol version 2.0.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)