RE: [Geopriv] Location-by-value in a SIP Location Header

Much as I'd love to dispute this, I think it's a settled issue; we're
supporting location-by-reference in location-conveyance.  I don't think we
need to continue to debate this.  It's in there.

What is still at issue is whether location-by-value in a header is in there.
We need a real use case.  I'm having trouble understanding how you can have
a SIP proxy that can get a call to the outside of some domain, but can't
provide a server to resolve a reference.

If we have bought off on location-by-value in a body, and
location-by-reference in a header, what case is not covered by those two
options?
Much as I would prefer proxy insertion by value over proxy insertion by
reference (even if I think proxy insertion is a bad idea, that's another
settled issue), I think a proxy can always use by-reference.  Fewer options
are better.

Brian



> -----Original Message-----
> From: Andrew Newton [mailto:[email protected]]
> Sent: Thursday, July 20, 2006 10:25 AM
> To: Drage, Keith (Keith)
> Cc: [email protected]; [email protected]
> Subject: Re: [Geopriv] Location-by-value in a SIP Location Header
> 
> Drage, Keith (Keith) wrote:
> > We will need to consider than outside this mail. Personally I think by
> reference works better for the 3G architecture in this use case. There is
> certainly no explicit 3GPP requirement at the moment.
> 
> 
> Actually, there are many environments where reference works better.
> 
> -andy
> 
> 
> _______________________________________________
> Geopriv mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/geopriv


_______________________________________________
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