Re: [cuss] "isdn-uui" versus "isdn-network"

There are many use cases where the calling device sends UUI to a call center but is not expecting any. Such devices (or associated interworking units) would not have to be updated to support the new value.

BC

De : cuss [mailto:cuss-bounces@ietf.org] De la part de Christer Holmberg
Envoyé : samedi 23 novembre 2013 15:21
À : Vijay K. Gurbani; cuss@ietf.org
Objet : Re: [cuss] "isdn-uui" versus "isdn-network"

Hi,

I already gave some comments, but in case the outcome was clear: I think we should move the draft forward.

Existing entities that implement the old value will anyway have to be updated to support the new value. And, if new entities will have to support the old value, I am sure the buyer will inform the vendor about that :)

Regards,

Christer

From: cuss [cuss-bounces@ietf.org] on behalf of Vijay K. Gurbani [vkg@bell-labs.com]
Sent: Friday, 22 November 2013 8:56 PM
To: cuss@ietf.org<mailto:cuss@ietf.org>
Subject: Re: [cuss] "isdn-uui" versus "isdn-network"

On 11/22/2013 12:36 PM, Atle Monrad wrote:
> Hi
>
> I guess each of the "shall we allow multiple representations" needs
> to be handled on a case-by-case basis, but generally speaking I
> understand that the chairs and ADs aren't too enthusiastic with too
> many ...
>
> What 3GPP really wants for Christmas is the draft to be completed.
> Somebody must take a decision on this soon.

... which means that by Nov 29, 2013 it'd be nice to hear from others
who have an opinion.

Many thanks to those who have already expressed one.

Cheers,

- 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}<mailto:vkg@%7bbell-labs.com,acm.org%7d> / vijay.gurbani@alcatel-lucent.com<mailto:vijay.gurbani@alcatel-lucent.com>
Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq
_______________________________________________
cuss mailing list
cuss@ietf.org<mailto:cuss@ietf.org>
https://www.ietf.org/mailman/listinfo/cuss

_________________________________________________________________________________________________________________________

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.