Security Mechanism Names for Media
draft-dawes-sipcore-mediasec-parameter-11

Document Type Expired Internet-Draft (individual)
Last updated 2020-05-29 (latest revision 2019-11-26)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-dawes-sipcore-mediasec-parameter-11.txt

Abstract

Negotiating the security mechanisms used between a Session Initiation Protocol (SIP) user agent and its next-hop SIP entity is described in [2]. This document adds the capability to distinguish security mechanisms that apply to the media plane by defining a new Session Initiation Protocol (SIP) header field parameter to label such security mechanisms.

Authors

Peter Dawes (peter.dawes@vodafone.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)