RFC 8498 on A P-Served-User Header Field Parameter for an Originating Call Diversion (CDIV) Session Case in the Session Initiation Protocol (SIP)
rfc-editor@rfc-editor.org Fri, 15 February 2019 05:48 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B0EF130F83; Thu, 14 Feb 2019 21:48:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uFC4g8mapOiu; Thu, 14 Feb 2019 21:48:08 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 859C3130F7E; Thu, 14 Feb 2019 21:48:08 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 69669B8005C; Thu, 14 Feb 2019 21:47:57 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8498 on A P-Served-User Header Field Parameter for an Originating Call Diversion (CDIV) Session Case in the Session Initiation Protocol (SIP)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, sipcore@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190215054757.69669B8005C@rfc-editor.org>
Date: Thu, 14 Feb 2019 21:47:57 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/f1eP2T4ocoHipbQ1MhhhGQgaV_k>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Fri, 15 Feb 2019 05:48:10 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8498
Title: A P-Served-User Header Field Parameter
for an Originating Call Diversion (CDIV)
Session Case in the Session Initiation
Protocol (SIP)
Author: M. Mohali
Status: Informational
Stream: IETF
Date: February 2019
Mailbox: marianne.mohali@orange.com
Pages: 15
Characters: 33188
Updates: RFC 5502
I-D Tag: draft-ietf-sipcore-originating-cdiv-parameter-08.txt
URL: https://www.rfc-editor.org/info/rfc8498
DOI: 10.17487/RFC8498
The P-Served-User header field was defined based on a requirement
from the 3rd Generation Partnership Project (3GPP) IMS (IP Multimedia
Subsystem) in order to convey the identity of the served user, his/
her registration state, and the session case that applies to that
particular communication session and application invocation. A
session case is metadata that captures the status of the session of a
served user regardless of whether or not the served user is
registered or the session originates or terminates with the served
user. This document updates RFC 5502 by defining a new P-Served-User
header field parameter, "orig-cdiv". The parameter conveys the
session case used by a proxy when handling an originating session
after Call Diversion (CDIV) services have been invoked for the served
user. This document also fixes the ABNF in RFC 5502 and provides
more guidance for using the P-Served-User header field in IP
networks.
This document is a product of the Session Initiation Protocol Core Working Group of the IETF.
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
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
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