Subject: [sipcore] Moving forward with draft-ietf-sipcore-originating-cdiv-parameter

From: <[email-masked]>
Date: Mon, 6 Nov 2017 17:12:16 +0000

Hi folks,

This draft was adopted in SIPCORE WG in May. 
A new version including Christer's comments has been published in September 27th. 
Since there was no additional feedback on this I-D, I would like to take the opportunity of the upcoming meeting to ask if it should move forward going to WGLC.

Feedbacks are welcomed!

Regards,
Marianne

> -----Message d'origine-----
> De : sipcore [mailto:[email-masked]] De la part de
> [email-masked]
> Envoyé : jeudi 28 septembre 2017 00:42
> À : [email-masked]; [email-masked]
> Objet : [sipcore] New version of draft-ietf-sipcore-originating-cdiv-parameter
> 
> Hi,
> 
> Here is the -01 version of the working group document draft-ietf-sipcore-originating-
> cdiv-parameter.
> In this version I have splitted the introduction section into the normal use case (as
> defined in RFC5502) and the problem statement by which it has been decided to
> propose an extension of the P-Served-User header.
> Call Flows section has also been added to illustrate usage of the new proposed
> session case.
> 
> Review and comments are welcome.
> 
> Best regards,
> Marianne
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-sipcore-originating-cdiv-parameter/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-sipcore-originating-cdiv-parameter-01
> https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-originating-cdiv-parameter-01
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-sipcore-originating-cdiv-parameter-01
> 
> 
> ____________________________________________________________________
> _____________________________________________________
> 
> 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.
> 
> _______________________________________________
> sipcore mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/sipcore

_________________________________________________________________________________________________________________________

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.