Cullen,
Within the Deutsche Telekom (fixed networks) we identified a strong need for UUI as a way to transport information within SIP messages UA-to-UA, UA-to-AS, AS-to-UA, AS-to-AS. We already have Alan's draft in the requirements for MGC and Application Servers. In the future we may have scenarios as described by Alan in the Use Case 4.3 Redirection, but this depends on the future product management requirements.
My feeling is that Alan wonderfully catched the requirements.
We will prefer the Header-Field approach because it is more flexible and covers the most use cases. I think there is the only way to fulfill the REQ-6 in the draft.
The MIME-Body approach would cover our current needs, but probably will not cover the needs for products we will build within two or three years. In this case we will have to choose between replacing redirect servers with B2BUAs just to be able to use UUI or introducing some proprietary headers. I think this is what REQ-6 tries to avoid.
Laura
-----Ursprüngliche Nachricht-----
Von: sipping-bounces@xxxxxxxx [mailto:sipping-bounces@xxxxxxxx] Im Auftrag von Cullen Jennings
Gesendet: Donnerstag, 13. November 2008 01:06
An: Alan Johnston
Cc: Joanne McMillen; sipping
Betreff: Re: [Fwd: New Version Notification fordraft-johnston-sipping-cc-uui-05]
I just started actually thinking about this draft and it made me
wonder about the requirements.
Is the need here to tunnel the ISDN UUIE from UAC to UAS or is it a
requirement that all the SIP routing elements need to understand the
UUIE? Without understand what part of the network is required to
support this, makes it sort of hard to decide what is the best way to
do this.
I was also wondering if Q.1980.1 NSS pretty much solved this problem
or if something more was needed.
Cullen <with my individual contributor hat on>
On Oct 31, 2008, at 13:17 , Alan Johnston wrote:
> We have revised the UUI draft based on comments in Dublin.
>
> The major changes are:
>
> 1. Added 7 requirements for the mechanism.
> 2. Removed some controversial proxy use cases.
>
> Comments are most welcome.
>
> Thanks,
> Alan
>
> -------- Original Message --------
> Subject: New Version Notification for draft-johnston-sipping-cc-
> uui-05
> Date: Fri, 31 Oct 2008 13:13:58 -0700 (PDT)
> From: IETF I-D Submission Tool <idsubmission@xxxxxxxx>
> To: alan@xxxxxxxxxxxxxx
> CC: joanne@xxxxxxxxx
>
>
>
> A new version of I-D, draft-johnston-sipping-cc-uui-05.txt has been
> successfuly submitted by Alan Johnston and posted to the IETF
> repository.
>
> Filename: draft-johnston-sipping-cc-uui
> Revision: 05
> Title: Transporting User to User Call Control Information in SIP
> for ISDN Interworking
> Creation_date: 2008-10-31
> WG ID: Independent Submission
> Number_of_pages: 16
>
> Abstract:
> Several approaches to transporting the ITU-T Q.931 User to User
> Information Element (UU IE) data in SIP have been proposed. 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 the information to/from ISDN for end-to-end
> transparency. This extension will also be used for native SIP
> endpoints implementing similar services and interworking with ISDN
> services. This document discusses requirements and approaches and
> recommends a new header field User-to-User be standardized. Example
> use cases include an exchange between two User Agents, retargeting by
> a proxy, and redirection. An example application is in an Automatic
> Call Distributor (ACD) in a contact center.
>
>
> The IETF Secretariat.
>
>
>
>
>
> _______________________________________________
> Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip
> Use sip@xxxxxxxx for new developments of core SIP
_______________________________________________
Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip
Use sip@xxxxxxxx for new developments of core SIP
_______________________________________________
Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip
Use sip@xxxxxxxx for new developments of core SIP
