Subject: [sipcore] TR: New Version Notification for draft-ietf-sipcore-originating-cdiv-parameter-00.txt

From: <[email-masked]>
Date: Tue, 16 May 2017 06:24:05 +0000

FYI,

Here is the -00 version of the new sipcore wg document draft-ietf-sipcore-originating-cdiv-parameter.

Review and comments are welcome.

Best regards,
Marianne

-----Message d'origine-----
De : [email-masked] [mailto:[email-masked]] 
Envoyé : lundi 15 mai 2017 15:02
À : MOHALI Marianne IMT/OLN
Objet : New Version Notification for draft-ietf-sipcore-originating-cdiv-parameter-00.txt

A new version of I-D, draft-ietf-sipcore-originating-cdiv-parameter-00.txt
has been successfully submitted by Marianne Mohali and posted to the IETF repository.

Name:		draft-ietf-sipcore-originating-cdiv-parameter
Revision:	00
Title:		A P-Served-User Header Field Parameter for Originating CDIV session case in Session Initiation Protocol (SIP)
Document date:	2017-05-15
Group:		sipcore
Pages:		9
URL:            https://www.ietf.org/internet-drafts/draft-ietf-sipcore-originating-cdiv-parameter-00.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-sipcore-originating-cdiv-parameter/
Htmlized:       https://tools.ietf.org/html/draft-ietf-sipcore-originating-cdiv-parameter-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-originating-cdiv-parameter-00

Abstract:
   This specification defines a new parameter of the P-Served-User
   header field in the Session Initiation Protocol (SIP).  This new
   "orig-cdiv" parameter defines the session case used by a proxy when
   handling an originating session after Call Diversion (CDIV) services
   has been invoked for the served user.  The P-Served-User header field
   is defined in RFC5502 to convey the identity of the served user and
   the session case that applies to this particular communication
   session and application invocation.  This document updates RFC5502 to
   add the "originating after CDIV" session case and to provide more
   guidance for using the P-Served-User header field in IP networks that
   were missing in RFC5502.

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.