Re: [sipcore] draft-barnes-sipcore-rfc4244bis

I guess it's somewhat historical.

It's basically saying that the Privacy and Reason "escaped parameters" would 
translate into headers if we were to created a request based on it.

This whole concept falls into the category of "it came from HTTP so it must
be good (TM)". 

> -----Original Message-----
> From: sipcore-bounces@ietf.org 
> [mailto:sipcore-bounces@ietf.org] On Behalf Of Worley, Dale 
> (BL60:9D30)
> Sent: Wednesday, July 08, 2009 11:32
> To: Barnes, Mary (RICH2:AR00)
> Cc: SIPCORE
> Subject: [sipcore] draft-barnes-sipcore-rfc4244bis - privacy syntax
> 
> I'm curious why the privacy attribute of an 
> hi-targeted-to-uri is specified by adding a header-parameter 
> to the URI, rather than being given as a field-parameter.  
> That is, an example of the current syntax
> is:
> 
>   
> <sip:UserB@example.com?Privacy=history&Reason=SIP%3Bcause%3D48
> 6>;index=1.2;mapped
> 
> where I would expect:
> 
>   
> <sip:UserB@example.com?Reason=SIP%3Bcause%3D486>;index=1.2;map
> ped;privacy=history
> 
> This privacy value is an annotation of the URI, whereas the 
> current syntax incorporates it *into* the URI.  And indeed, 
> to reconstitute the actual historical request-URI, one has to 
> remove the Privacy header from the URI part of the name-addr, 
> that is, the stuff inside <...>.
> (Although given that the historical URI can have had no 
> header parameters (due its use as a request-URI), that 
> processing step is not
> ambiguous.)
> 
> In addition, the values of the 4244 Privacy header do not 
> have exactly the same semantics as the same tokens used as 
> values of the Privacy header.
> 
> I guess that for compatibility with RFC 4244, we have to 
> continue to record privacy and reason information in the URI 
> this way, but I'm curious what the motivation was for this 
> rather unusual way to represent this information.
> 
> Dale
> 
> 
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
> 

Re: [sipcore] draft-barnes-sipcore-rfc4244bis - privacy syntax