Alan and Joanne, Looking at the redirection example, I could imagine a similar case but using proxying (retargeting or rerouting) rather than redirection. In this case the proxy would insert the UUI in the forwarded request. Is see no requirement for this in section 3. However, PSTN/ISDN does not support capabilities equivalent to insertion by a proxying or redirecting entity. Yet in section 1 it states: "This document looks only at the requirements and mechanisms for replicating the existing, widely used and deployed ISDN UUI service." Therefore we should either: - remove the redirection case, on the grounds that it doesn't replicate existing ISDN UUI operation; or - clarify the statement in section 1 so as not to preclude the redirection case. Furthermore, if we adopt the second of these approaches we might wish to consider adding a requirement for insertion by a proxy. Fortunately the chosen mechanism would seem to permit this. I have no strong feelings which approach we should take. I just wish to see consistency. John > -----Original Message----- > From: sipping-bounces@xxxxxxxx > [mailto:sipping-bounces@xxxxxxxx] On Behalf Of Mary Barnes > Sent: 02 December 2008 00:49 > To: sipping@xxxxxxxx > Cc: Gonzalo Camarillo > Subject: Initial WG review: draft-johnston-sipping-cc-uui-06 > > Hi folks, > > This email is intended to announce an initial WG review for > the following document: > http://www.ietf.org/internet-drafts/draft-johnston-sipping-cc- > uui-06.txt > <http://www.ietf.org/internet-drafts/draft-johnston-sipping-cc > -uui-06.txt> > > There was strong consensus to complete the problem statement > and requirements in the SIPPING WG session (i.e., WGLC) and > then propose that the solution be worked in SIP WG - with the > obvious understanding that SIP WG must go through the process > of taking on a new work item. And, of course, the chairs > will work with the AD to get the appropriate milestones added > to SIPPING WG charter. > > In order to progress this document in the SIPPING WG, we > would like at least 3 (ideally 4) dedicated reviewers. So, > please let us know ASAP if you would be willing to serve as a > reviewer. If we don't get volunteers, I will pick on people, > but it would be great to get some new reviewers into the pool. > > In terms of feedback, as well as technical comments, we would > like to hear views on whether this doc is ready for WGLC > (note that this document has been in the WG as an individual > draft for over two years). > > Please send any and all comments on or before Dec. 22nd, 2008 > (3 weeks time). > > Regards, > Mary. > SIPPING WG co-chair > > _______________________________________________ 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
