From: Jonathan Rosenberg <jdrosen at cisco.com>
So what is your view on the specific mechanism I was proposing to meet
this objective? Namely, that the registrar would provide you with a
'regular' gruu and a pseudononymous one, and the latter changes every
time you create a new registration (not refresh, a new one entirely).
I agree that you've shown the necessity of modifying GRUU to support
this level of anonymity. But one clarification -- is the
"pseudononymous GRUU" expected to have a longer lifetime than the
registration, or do you envision it having the same lifetime?
If the latter, it seems that implementing "pseudononymous GRUUs" is
simple, and not much of a burden on Registrars, since they can be
created by any method and stored in the record of the registration.
If the former, then we need to consider how a family of pseudononymous
GRUUs for each UA can be managed.
Dale
_______________________________________________
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