Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps

Andrew Allen <> Mon, 02 December 2013 16:28 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 8D4611AC499 for <>; Mon, 2 Dec 2013 08:28:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id c9JiqlJYxkY9 for <>; Mon, 2 Dec 2013 08:27:59 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 8FBE71A8032 for <>; Mon, 2 Dec 2013 08:27:59 -0800 (PST)
Received: from ([]) by with ESMTP/TLS/AES128-SHA; 02 Dec 2013 11:27:53 -0500
Received: from ([fe80::2494:a63d:e3:723b]) by ([fe80::2c7e:1215:d554:35b5%20]) with mapi id 14.03.0158.001; Mon, 2 Dec 2013 10:27:53 -0600
From: Andrew Allen <>
To: "" <>, "" <>
Thread-Topic: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps
Thread-Index: AQHO73F92zk1+07b8Ee86abct8exYJpBGAEw
Date: Mon, 2 Dec 2013 16:27:51 +0000
Message-ID: <>
In-Reply-To: <>
Accept-Language: en-CA, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps
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: Mon, 02 Dec 2013 16:28:02 -0000

I think it might be wise to indicate in the IANA registry that the value "isdn-network" is reserved for historical reasons and its use has been deprecated.

----- Original Message -----
From: Vijay K. Gurbani []
Sent: Monday, December 02, 2013 10:16 AM Eastern Standard Time
To: <>
Subject: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps


The WGLC for draft-ietf-cuss-sip-uui-isdn is now over.

Below is my personal interpretation of where the matter stands, i.e.,
what I write below is not written as a co-chair but rather to determine
if the WG agree that this is where matters now stand.  Please comment
if I deviate from what you all agree.

- "isdn-network" is tacitly supported, but not overtly so.

- More specifically, "isdn-network" is not IANA registered, and all
   text related to it is not normative.

- The addition of the Note uses non-normative language, i.e.,

      "The 'isdn-interwork' value for purpose parameter was used
      in Internet-Drafts that have led to the publication of the
      present RFC. Although these documents had no other status than
      "work in progress", this value is implemented by some vendors.
      Therefore, it is recommended to support parsing and interpreting
      'isdn-interwork' the same way as 'isdn-uui' when receiving

Is this an accurate representation?

Now back with the co-chair hat on ...

There has been reviews of the draft [1,2,3] by key WG members.  Can the
draft authors please comment on next steps with respect to revising the
draft.  Enrico and I will start the shepherding step in parallel to the
revision to be submitted.



- vijay
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{,} /
Web:  | Calendar:
cuss mailing list
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.