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

Atle Monrad <atle.monrad@ericsson.com> Tue, 03 December 2013 06:53 UTC

Return-Path: <atle.monrad@ericsson.com>
X-Original-To: cuss@ietfa.amsl.com
Delivered-To: cuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B8121AE069 for <cuss@ietfa.amsl.com>; Mon, 2 Dec 2013 22:53:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q93erOfm4FVI for <cuss@ietfa.amsl.com>; Mon, 2 Dec 2013 22:53:50 -0800 (PST)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id D147D1AE066 for <cuss@ietf.org>; Mon, 2 Dec 2013 22:53:49 -0800 (PST)
X-AuditID: c1b4fb38-b7f2c8e000006d25-bb-529d7ffa1dd0
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.253.125]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id A9.F1.27941.AFF7D925; Tue, 3 Dec 2013 07:53:46 +0100 (CET)
Received: from ESESSMB203.ericsson.se ([169.254.3.134]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.02.0347.000; Tue, 3 Dec 2013 07:53:46 +0100
From: Atle Monrad <atle.monrad@ericsson.com>
To: Andrew Allen <aallen@blackberry.com>, "vkg@bell-labs.com" <vkg@bell-labs.com>, "cuss@ietf.org" <cuss@ietf.org>
Thread-Topic: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps
Thread-Index: AQHO73F9QurHFH6wtESVPvq1tc09QJpBBz2AgAD0qhA=
Date: Tue, 3 Dec 2013 06:53:45 +0000
Message-ID: <7D2F7D7ADBA812449F25F4A69922881C22FC60@ESESSMB203.ericsson.se>
References: <529CA43D.3090900@bell-labs.com> <BBF5DDFE515C3946BC18D733B20DAD2338E708E9@XMB104ADS.rim.net>
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2338E708E9@XMB104ADS.rim.net>
Accept-Language: nb-NO, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrGLMWRmVeSWpSXmKPExsUyM+Jvre6v+rlBBldXyVvcn7eV0eJG+wtm i4Y1cg7MHn2XXTxmNaxl91iy5CdTAHMUl01Kak5mWWqRvl0CV0br6tksBbdUKz6f3sHawNgi 38XIySEhYCKxfeJRFghbTOLCvfVsXYxcHEICRxglLp68zQrhLGaUeH35KjNIFZuAjsS5n3dY QWwRgRKJLZ+eMoLYwgJeEv82f2GDiHtL/H86lwXCtpKYdXguUJyDg0VAReLTqhqQMC9QyaJX a1lBwkIC2RJnjgWBmJwCnhKHZ2WDmIwCshJzm3hBipkFxCVuPZnPBHGlgMSSPeeZIWxRiZeP /7FC2EoSK7ZfYoSo15FYsPsTG4StLbFs4WtmiKWCEidnPmGZwCg6C8nYWUhaZiFpmYWkZQEj yypGjuLU4qTcdCODTYzAuDi45bfFDsbLf20OMUpzsCiJ83586xwkJJCeWJKanZpakFoUX1Sa k1p8iJGJg1OqgZFzjc9MPX/L+ydeWG75WWS/SfhZSnBKo9mdJ3KWWX9NfteoRMevvsNw4IDz xYVWR32T4nVK/LfeUPj24q7ixptbtp4+PU3adh/vifZcL8ELbVu3FdnbMR1y52aeYDHX3ej8 IgvpJyek/N/fiW92YGzh1Dur75PgHDtDPIR7fqPniZeyL2c2syixFGckGmoxFxUnAgAa11Da WQIAAA==
Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps
X-BeenThere: cuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" <cuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cuss>, <mailto:cuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/cuss/>
List-Post: <mailto:cuss@ietf.org>
List-Help: <mailto:cuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cuss>, <mailto:cuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Dec 2013 06:53:52 -0000

Folks

When I came to Vancouver to discuss how to complete the draft, it was also my understanding that the involved parties could live with an informative note, thus I support Vijays conclusion. 

I'd like to add that while [1] and [3] are easy nits, on [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00539.html, there are some further comments from Keith + the fact that we have moved to an informative note, thus I'm not that sure how much that is left of this comment.

Note also that if the current authors cannot find time to complete the work rather soon, I still have the backup author - Roland Jesske. I assume that Vijay will contact him if necessary. I would hope that 3GPP does not need to wait for too long for completion. I'd propose to give people time until end-of-the-week to revise the draft.

__________


On the IANA-registry, I have nothing against this as long as it is formally correct with the current phrased note by Vijay and doesn't cause more work to the draft and/or delay the completion process. However, IMHO we shouldn't restart the debate if IANA-registries isn't possible without normative statements in the drafts.

thanks
/atle

________________________________ 


Atle Monrad
3GPP CT Chairman

Group Function Technology - Standardization and Technical Regulation 
Ericsson



-----Original Message-----
From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of Andrew Allen
Sent: 3. desember 2013 01:28
To: vkg@bell-labs.com; cuss@ietf.org
Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps


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 [mailto:vkg@bell-labs.com]
Sent: Monday, December 02, 2013 10:16 AM Eastern Standard Time
To: cuss@ietf.org <cuss@ietf.org>
Subject: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps

Folks:

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
      messages."

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.

[1] http://www.ietf.org/mail-archive/web/cuss/current/msg00531.html
[2] http://www.ietf.org/mail-archive/web/cuss/current/msg00539.html
[3] http://www.ietf.org/mail-archive/web/cuss/current/msg00522.html

Thanks,

- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq _______________________________________________
cuss mailing list
cuss@ietf.org
https://www.ietf.org/mailman/listinfo/cuss
---------------------------------------------------------------------
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.

_______________________________________________
cuss mailing list
cuss@ietf.org
https://www.ietf.org/mailman/listinfo/cuss