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

Document Type Active Internet-Draft (individual)
Last updated 2017-05-09
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                                 P. Dawes
Internet-Draft                                            Vodafone Group
Intended status: Informational                               May 9, 2017
Expires: November 10, 2017

                   Security Mechanism Names for Media
             draft-dawes-sipcore-mediasec-parameter-06.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.

Requirements Language

   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 [1].

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 November 10, 2017.

Copyright Notice

   Copyright (c) 2017 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

Dawes                   Expires November 10, 2017               [Page 1]
Internet-Draft     Security Mechanism Names for Media           May 2017

   (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.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Access Network Protection . . . . . . . . . . . . . . . . . .   4
   4.  Solution  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Signaling security negotiation  . . . . . . . . . . . . .   4
     4.2.  Header fields for signaling security negotiation  . . . .   5
     4.3.  Syntax  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     4.4.  Protocol Operation  . . . . . . . . . . . . . . . . . . .   5
       4.4.1.  The "mediasec" Header Field Parameter . . . . . . . .   5
       4.4.2.  Client Initiated  . . . . . . . . . . . . . . . . . .   5
     4.5.  Security Mechanism Initiation . . . . . . . . . . . . . .   7
     4.6.  Duration of Security Assocations  . . . . . . . . . . . .   7
     4.7.  Summary of Header Field Use . . . . . . . . . . . . . . .   7
   5.  Backwards Compatibility . . . . . . . . . . . . . . . . . . .   7
   6.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  Initial Registration 3GPP . . . . . . . . . . . . . . . .   7
     6.2.  Re-Registration 3GPP  . . . . . . . . . . . . . . . . . .  12
     6.3.  Client Initiated as per RFC 3329  . . . . . . . . . . . .  14
     6.4.  Server Initiated as per RFC 3329  . . . . . . . . . . . .  16
     6.5.  Using Media Plane Security  . . . . . . . . . . . . . . .  18
   7.  Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . .  20
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  20
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  20
     9.1.  Registry for Media Plane Security Mechanisms  . . . . . .  20
     9.2.  Registration Template . . . . . . . . . . . . . . . . . .  21
     9.3.  Header Field Names  . . . . . . . . . . . . . . . . . . .  21
     9.4.  Response Codes  . . . . . . . . . . . . . . . . . . . . .  21
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  21
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  21
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  21
Show full document text