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: [email protected]
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 [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
