[Sip] draft-ietf-sip-gruu-10 comments

[Cullen Jennings <fluffy at cisco.com>]

One significant issue...

Would you agree to put in the security section that any UA that is  
sending a request where it has set the From header field value to  
Anonymous MUST not use a GRUU that does not have the anonymous  
property? I suspect the answer to this will be yes - I'm still trying  
to think about the implications of this and trade offs.


Few smaller things:

Section 8.1.1. para 4. I really can't figure out what this says - I  
suspect that I know what is trying to say but when I try to parse the  
paragraph, my stack overflows. Sorry for such a useless comment - I'm  
not exactly sure how to improve it.

Section 8.2.1 para 2, last sentence. I think the term "unknown" is  
not what we want here. Often the device will not be registered, (say  
it is powered off), but the device id will be "known" to the domain  
as it created the GRUU in the past, it still have provisioning  
information for this device etc. It seems like we might want  
something more like "not registered" instead of unknown

Section 8.2.2

I think I am likely confused here. I basically don't see why a simple  
classic sip trapezoid deployment would ever need to Record Route. The  
fact that the GRUU refereed to the "home" domain would cause it work  
get back here. As a side note, I find the terms "home", "edge" etc  
very undefined outside the IMS context. Anyways, I believe this  
section might be all right but I am failing to understand what needs  
to be done and why. If I was a non IMS proxy implementer, I suspect I  
would just ignore this whole section.

Section 8.2.3 - This is probably just my missing something in reading  
this but I did not see how the procession of mid dialog requests was  
different that than 8.2.1. Can we delete this section.

Cullen (with my individual hat on)

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip