Re: [cuss] FW: I-D Action: draft-ietf-cuss-sip-uui-isdn-11.txt

<> Thu, 20 November 2014 13:14 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id E916B1A040B for <>; Thu, 20 Nov 2014 05:14:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id CAlRyClbGnjM for <>; Thu, 20 Nov 2014 05:14:51 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 934CD1A0271 for <>; Thu, 20 Nov 2014 05:14:51 -0800 (PST)
Received: from (unknown [xx.xx.xx.2]) by (ESMTP service) with ESMTP id 5404F18C1BC; Thu, 20 Nov 2014 14:14:49 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown []) by (ESMTP service) with ESMTP id 33C1927C072; Thu, 20 Nov 2014 14:14:49 +0100 (CET)
Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0210.002; Thu, 20 Nov 2014 14:14:48 +0100
From: <>
To: "DRAGE, Keith (Keith)" <>, "" <>
Thread-Topic: [cuss] FW: I-D Action: draft-ietf-cuss-sip-uui-isdn-11.txt
Thread-Index: AQHP/gQNeOWUg+ySy0aNLFBZEkoYxpxcDEOQgA19/nA=
Date: Thu, 20 Nov 2014 13:14:48 +0000
Message-ID: <24925_1416489289_546DE949_24925_288_2_F8BE5641EC3C954DA088A8350BDDFA48192E29@PEXCVZYM13.corporate.adroot.infra.ftgroup>
References: <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version:, Antispam-Engine:, Antispam-Data: 2014.10.23.100020
Subject: Re: [cuss] FW: I-D Action: draft-ietf-cuss-sip-uui-isdn-11.txt
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 20 Nov 2014 13:14:55 -0000


Sorry for this late comment (I was absent before), in this new version 11 there is an unexpected space in "isdn-interwork" value in section 8 in the following sentence: 
"parsing and interpreting "isdn- interwork" the same way as "isdn-uui" when receiving messages."
This only appears now in version 11 likely because of the change from "purpose parameter" to ""purpose" header field parameter" (a little higher in the text).
I hope this editorial comment could be taken into account before becoming an RFC in order to avoid any misunderstanding.

Celine Serrut-Valette
Orange Labs

-----Message d'origine-----
De : cuss [] De la part de DRAGE, Keith (Keith)
Envoyé : mercredi 12 novembre 2014 00:08
À :
Objet : [cuss] FW: I-D Action: draft-ietf-cuss-sip-uui-isdn-11.txt

This version contains essentially editorial changes from the previous version. Some of those editorials correct names of some protocol elements in DSS1 and ISUP, so they are less than editorial in that respect.



-----Original Message-----
From: cuss [] On Behalf Of
Sent: 11 November 2014 23:06
Subject: [cuss] I-D Action: draft-ietf-cuss-sip-uui-isdn-11.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Call Control UUI Service for SIP Working Group of the IETF.

        Title           : Interworking ISDN Call Control User Information with SIP
        Authors         : Keith Drage
                          Alan Johnston
	Filename        : draft-ietf-cuss-sip-uui-isdn-11.txt
	Pages           : 16
	Date            : 2014-11-11

   The motivation and use cases for interworking and transporting ITU-T
   DSS1 User-user information element data in SIP are described in RFC
   6567.  As networks move to SIP, it is important that applications
   requiring this data can continue to function in SIP networks as well
   as the ability to interwork with this ISDN service for end-to-end
   transparency.  This document defines a usage (a new package called
   the ISDN UUI package) of the User-to-User header field to enable
   interworking with this ISDN service.

   This document covers the interworking with both public ISDN and
   private ISDN capabilities, so the potential interworking with QSIG
   will also be addressed.

   The package is identified by a new value "isdn-uui" of the "purpose"
   header field parameter.

The IETF datatracker status page for this draft is:

There's also a htmlized version available at:

A diff from the previous version is available at:

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

Internet-Drafts are also available by anonymous FTP at:

cuss mailing list

cuss mailing list


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.