Subject: [dispatch] TR: New Version Notification for draft-mohali-dispatch-cause-for-service-number-02.txt

From: <[email-masked]>
Date: Mon, 11 May 2015 12:31:58 +0000

Hi all,

FYI, a new version of the draft is available.
This version takes into account Paul's comment concerning the presence of the cause-param in the Request-URI.

BR,
Marianne

A new version of I-D, draft-mohali-dispatch-cause-for-service-number-02.txt
has been successfully submitted by Marianne Mohali and posted to the IETF repository.

Name:		draft-mohali-dispatch-cause-for-service-number
Revision:	02
Title:		Session Initiation Protocol (SIP) Cause URI parameter for Service Number translation
Document date:	2015-05-11
Group:		Individual Submission
Pages:		7
URL:            https://www.ietf.org/internet-drafts/draft-mohali-dispatch-cause-for-service-number-02.txt
Status:         https://datatracker.ietf.org/doc/draft-mohali-dispatch-cause-for-service-number/
Htmlized:       https://tools.ietf.org/html/draft-mohali-dispatch-cause-for-service-number-02
Diff:           https://www.ietf.org/rfcdiff?url2=draft-mohali-dispatch-cause-for-service-number-02

Abstract:
   [RFC4458] defines a "cause" URI parameter as having predefined values
   for Redirecting reasons as a mapping from ITU-T Q.732.2-5 Redirecting
   Reasons.  The "cause" URI parameter is to be used in SIP or SIPs URI.
   In particular, it may appear in the Request-URI and in the History-
   Info header field defined in [RFC7044] in some specific retargeted
   requests defined in this document.
   This specification creates a new predefined value for cases when the
   retargeting is caused by a specific service action leading to a
   called service access number translation.
   This document updates [RFC4458].

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.