RE: Allowing sip: in location header not good

"Thomson, Martin" <[email protected]>
Newsgroups gmane.ietf.sip,gmane.ietf.geopriv
Message-ID <[email protected]>
I don't think that you need to preclude the use of SIP here, but there are a lot of things that need to be considered before SUB/NOT are allowed.

That is to say - the location conveyance document doesn't cover its use, and nothing else does...yet.  When someone does a using-protocol specification for SUB/NOT, then we have a place to describe how to use sip[s]: in the Location header.

Fact is - I don't think that we have ANY using-protocol defined, hence the problems we are having in deciding what goes in the header.


>                  (and I'm not so sure about 'pres')

A pres: URI is in effect a sip[s]: URI for these purposes.


Cheers,
Martin
------------------------------------------------------------------------------------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information.  
If you have received it in error, please notify the sender
immediately and delete the original.  Any unauthorized use of
this email is prohibited.
------------------------------------------------------------------------------------------------
[mf2]

_______________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.