[sipcore] I-D Action: draft-ietf-sipcore-rfc7976bis-01.txt
internet-drafts@ietf.org Mon, 10 February 2025 07:27 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from mail2.ietf.org (mail2.ietf.org [166.84.6.31]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 6A955C14F6B5; Sun, 9 Feb 2025 23:27:30 -0800 (PST)
Received: from mail.ietf.org (mail.ietf.org [50.223.129.194]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPSA id BCF295CCA1; Mon, 10 Feb 2025 07:27:29 +0000 (UTC)
Received: from [10.244.8.212] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id E146CC14F694; Sun, 9 Feb 2025 23:27:28 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.35.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <173917244847.447448.14437749093494708093@dt-datatracker-75c44cbbdf-pxnd6>
Date: Sun, 09 Feb 2025 23:27:28 -0800
Message-ID-Hash: WYB2VZKYXLWH2BM5HQE4Z3EYCBTCG27K
X-Message-ID-Hash: WYB2VZKYXLWH2BM5HQE4Z3EYCBTCG27K
X-MailFrom: internet-drafts@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-sipcore.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: sipcore@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: sipcore@ietf.org
Subject: [sipcore] I-D Action: draft-ietf-sipcore-rfc7976bis-01.txt
List-Id: SIP Core Working Group <sipcore.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/PlrRWzu6063E0FbsOyVaO54oZbs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Owner: <mailto:sipcore-owner@ietf.org>
List-Post: <mailto:sipcore@ietf.org>
List-Subscribe: <mailto:sipcore-join@ietf.org>
List-Unsubscribe: <mailto:sipcore-leave@ietf.org>
Internet-Draft draft-ietf-sipcore-rfc7976bis-01.txt is now available. It is a
work item of the Session Initiation Protocol Core (SIPCORE) WG of the IETF.
Title: Updates to Private Header (P-Header) Extension Usage in Session Initiation Protocol (SIP) Requests and Responses
Authors: Christer Holmberg
Nevenka Biondic
Gonzalo Salgueiro
Roland Jesske
Name: draft-ietf-sipcore-rfc7976bis-01.txt
Pages: 8
Dates: 2025-02-09
Abstract:
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.
The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-sipcore-rfc7976bis/
There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-rfc7976bis-01
A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-sipcore-rfc7976bis-01
Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts
- [sipcore] I-D Action: draft-ietf-sipcore-rfc7976b… internet-drafts