Mayumi, "If the "temp-gruu" URI parameter and value exist within the REGISTER response, the user agent SHOULD use the value of the "temp-gruu" as an anonymous URI representing the originator. This URI SHOULD be used for Contact and From, for example, wherever the originator of the URI is required." I have not heard of using a temp GRUU in the From header field before. Normally the From header field contains the AoR, not the contact URI, and where anonymity is required if contains a value such as sip:[EMAIL PROTECTED] or a domain part of "anonymous.invalid". Of course, a temp GRUU does provide anonymity (given that you are prepared to disclose the domain), so I suppose it might work. There may be one or two side effects:
1. A UAS that simply displays the From URI would display the temp GRUU rather than something like "sip:[EMAIL PROTECTED]". 2. If the outbound proxy provides an Authentication Service, it would need to recognise that this is a temporary GRUU and sign the Identity header field even though the From URI does not match the identity in the Proxy-Authorization header field. I would like to hear opinions on this. John _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
