RFC 7976 on Updates to Private Header (P-Header) Extension Usage in Session Initiation Protocol (SIP) Requests and Responses

rfc-editor@rfc-editor.org Mon, 19 September 2016 21:35 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 652C212B549 for <ietf-announce@ietfa.amsl.com>; Mon, 19 Sep 2016 14:35:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.918
X-Spam-Status: No, score=-104.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id XBIhWX0XAiSK for <ietf-announce@ietfa.amsl.com>; Mon, 19 Sep 2016 14:35:41 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 145ED12B553 for <ietf-announce@ietf.org>; Mon, 19 Sep 2016 14:35:27 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 00799B8118D; Mon, 19 Sep 2016 14:35:26 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7976 on Updates to Private Header (P-Header) Extension Usage in Session Initiation Protocol (SIP) Requests and Responses
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160919213527.00799B8118D@rfc-editor.org>
Date: Mon, 19 Sep 2016 14:35:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/t4eRO1ZBIbBxqubMTjSYKN_9XtA>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Sep 2016 21:35:43 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 7976

        Title:      Updates to Private Header (P-Header) 
                    Extension Usage in Session Initiation Protocol 
                    (SIP) Requests and Responses 
        Author:     C. Holmberg, N. Biondic, G. Salgueiro
        Status:     Informational
        Stream:     IETF
        Date:       September 2016
        Mailbox:    christer.holmberg@ericsson.com, 
        Pages:      8
        Characters: 17246
        Updates:    RFC 7315

        I-D Tag:    draft-holmberg-dispatch-rfc7315-updates-09.txt

        URL:        https://www.rfc-editor.org/info/rfc7976

        DOI:        http://dx.doi.org/10.17487/RFC7976

The Third Generation Partnership Project (3GPP) has identified cases
where different SIP private header extensions referred to as "P-"
header fields, and 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.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC