Updates to Private Header (P-Header) Extension Usage in Session Initiation Protocol (SIP) Requests/Responses
draft-holmberg-dispatch-rfc7315-updates-06

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-06-20 (latest revision 2016-04-27)
Stream IETF
Intended RFC status Informational
Formats pdf htmlized bibtex
Reviews
Stream WG state (None)
Document shepherd Jean Mahoney
Shepherd write-up Show (last changed 2016-05-18)
IESG IESG state In Last Call
Consensus Boilerplate Unknown
Telechat date
Responsible AD Ben Campbell
Send notices to (None)
IANA IANA review state IANA - Review Needed
Network Working Group                                        C. Holmberg
Internet-Draft                                                N. Biondic
Updates: 7315 (if approved)                                     Ericsson
Intended status: Informational                              G. Salgueiro
Expires: October 29, 2016                                          Cisco
                                                          April 27, 2016

    Updates to Private Header (P-Header) Extension Usage in Session
              Initiation Protocol (SIP) Requests/Responses
               draft-holmberg-dispatch-rfc7315-updates-06

Abstract

   The 3rd-Generation Partnership Project 3GPP has identified cases
   where different SIP private header extensions referred to as P-
   header fields, defined in RFC 7315, need to be included in SIP
   requests and responses currently not allowed according to RFC 7315.
   This document updates RFC 7315, in order to allow inclusion of the
   affected P- header fields in such requests and responses.

   This document also makes updates for RFC 7315 in order to fix
   misalignments that occurred when RFC 3455 was updated and obsoleted
   by RFC 7315.

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 October 29, 2016.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Holmberg, et al.        Expires October 29, 2016                [Page 1]
Internet-Draft                7315 Updates                    April 2016

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Misalignments and 3GPP use-cases  . . . . . . . . . . . . . .   3
     3.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  Misalignments . . . . . . . . . . . . . . . . . . . . . .   3
     3.3.  3GPP Use-cases  . . . . . . . . . . . . . . . . . . . . .   4
       3.3.1.  General . . . . . . . . . . . . . . . . . . . . . . .   4
       3.3.2.  P-Access-Network-Info . . . . . . . . . . . . . . . .   4
       3.3.3.  P-Charging-Vector . . . . . . . . . . . . . . . . . .   5
   4.  Updates to RFC 7315 . . . . . . . . . . . . . . . . . . . . .   6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   7
   8.  Change Log  . . . . . . . . . . . . . . . . . . . . . . . . .   7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   The 3rd-Generation Partnership Project (3GPP) has identified cases
   where different Session Initiation Protocol (SIP) [RFC3261] private
   header extensions referred to as P- header fields, defined in RFC
   7315 [RFC7315], need to be included in SIP requests and responses
   currently not allowed according to RFC 7315.  This document updates
   RFC 7315, in order to allow inclusion of the affected P- header
   fields in such requests and responses.

   This document also makes updates for RFC 7315 in order to fix
   misalignments that occurred when RFC 3455 [RFC3455] was updated and
   obsoleted by RFC 7315.

   As the P- header fields are mainly used in (and in most cases, only
   defined for) networks defined by the 3rd-Generation Partnership
   Project (3GPP), where the updates defined in this document are
Show full document text