Keith has sent out the call information: > Tuesday 19th September > ---------------------- > > 11:00 am - 1:00 pm Pacific > 12:00 midday - 2:00 pm Mountain > 1:00 pm - 3:00 pm Central > 2:00 pm - 4:00 pm Eastern > 7:00 pm - 9:00 pm UK > > Bridge details > > Access Phone Number: 8007718734 > International Access Phone Number: +1 6477233953 7-Digit Access Code: > 5776249 > > The compiled comments are at: > > http://www.softarmor.com/sipwg/reviews/gruu/index.html The main intent of these reviews is to determine a consensus on whether issues or ideas that have been raised (mostly on the list) require changes to the GRUU specification before sending GRUU to the IESG for IETF Last Call. Where I have found a correlation between this list and the issue tracker at http://www.softarmor.com/sipwg/ reviews/gruu/gruu-10-comments-v2.htm, I have included the reference. The fact that there isn't a tracker entry for each issue (these issues were taken from JDR's list) indicates we may not be tracking all the issues yet. Format for discussion: 1) Moderator introduces the issue. 2) The issue reporter or other party will discuss for clarification if needed. 3) Discussion (brief) follows. 4) Moderator will ask for a sense of whether the issue is a) understood and b) requires changes to the GRUU doc. 5) may repeat 3-4 cycle 6) Secretary records consensus in minutes. 7) Proceed to next issue. Issues for discussion 19Sep06: 1) anonymity of gruus (note we started this on previous call but reached no conclusion -- I suspect list discussion has suggested that "yes, some change to the doc is needed" is the answer. Tracker #124A and others) 2) When to apply GRUU - is it always? (Robert, tracker #4) 3) Lifetime of GRUU 4) Explicit mechanism for canceling a GRUU? Do we need one? 5) Lack of generality in grid/opaque design. Way for a more generic demux? (ekr, many tracker items) 6) retargeting, forwarding services applied to gruu? Is this policy or protocol requirements? 7) GRUU as a header and a URI param (Robert, tracker #5) 8) Statefulness required? (Robert) 9) in vs. out of dialog retargeting (Robert) 10) Determining whether a request is mid-dialog or not, to apply service treatment (and other things) - how to do that? (Robert) 11) Whether gruu needs to be explicitly flagged (This is a GRUU!) or not (Dean, tracker #6) 12) Xavier's alternative proposal on To modification (Tracker #1) 13) Home/edge proxy terminology - where to define, how to define 14) Bit about outbound proxies and what GRUU to use - comments that this is confusing 15) applicability of record-routing languages in basic trapezoid case (Cullen, tracker #112A) 16) Alternative gruu construction algorithm from ekr (Tracker #124) 17) SIP/SIPS text - should we say anything about SIPS? Consolidate SIPS processing? (ekr and others, tracker #49) 18) tel URI handling (Andrew, tracker #91) 19) GRUU/AOR URI equivalence - an issue? (Dale tracker #41, Francois tracker #76) 20) Escaping allowed in GRUU contact header param? (Dale, tracker #116) 21) Do we need client generated instance ID (Aki, tracker #7) 22) Related to whether GRUU is explicit: What do UACs do differently (if anything) if a contact is a GRUU? (ekr, Dean tracker #6, others) 23) Do we need more clarification on the lifetime of GRUUs?This keep coming up in non-registration-bound GRUU usages, like gateways. Can you delete a GRUU? (Robert, tracker #75) 24) Is the GRID functionality of UA-generated URI context something that is more generally useful than just with GRUU? (ekr) 25) Is the GRID functionality of letting a contacted UA know that it was reached via a GRUU both needful and best done with GRID, or would another mechanism be more appropriate? (ekr)