Re: [sipcore] #38: How is the mapping of a GRUU into its UA Contact marked?

Be very careful here. RFC 5627 describes a technique for constructing 
gruus that are associated with AORs. It also describes "self made GRUUs" 
which are simply URIs that are naturally globally routable. Both kinds 
get the gr parameter. Self made gruus may have *no* association with an 
AOR at all.

While it might "work", tagging a self made gruu as an AOR would at least 
be confusing.

	Thanks,
	Paul

Shida Schubert wrote:
>  I just re-read GRUU and realized that, for some 
> reason I thought public GRUU was specified as 
> a type of AoR in the spec. 
> 
>  I guess the question then is whether we want to 
> expand the semantics of "rc" to include GRUU's 
> mapping to contact address.
>  
>  After all GRUU can still be identified in the H-I 
> using the "gr" parameter, so keeping the text 
> as is may not be such a big deal. So may be 
> adding text to identify GRUU in H-I is all we need. 
> 
>  Regards
>   Shida
> 
> On Sep 3, 2010, at 3:53 AM, Worley, Dale R (Dale) wrote:
> 
>> ________________________________________
>> From: sipcore-bounces@ietf.org [sipcore-bounces@ietf.org] On Behalf Of Shida Schubert [shida@ntt-at.com]
>>
>> AFAIK mapping of GRUU to registered contact
>> when proxy is retargeting will result to registered
>> contact marked with "rc".
>> ________________________________________
>>
>> A GRUU is not an AOR and the text states that "rc" is to be used *only* for the mappings from AORs to their registered contacts.
>>
>> Dale
> 
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
> 