Re: [Sip] New I-D - TOTE

Jonathan Rosenberg wrote:
> I just submitted a new I-D, which proposes a protocol called TOTE:
> http://www.ietf.org/internet-drafts/draft-rosenberg-sip-tote-00.txt
> 
> Basically, TOTE provides the ability to exchange MIME objects of any 
> type and "purpose" over a tcp/tls connection established e2e through SDP 
> O/A procedures and ICE-tcp. This ties into the INFO disussion; it 
> provides the media-plane equivalent of the INFO-events framework.
> 
> This draft should arguably go in mmusic but since the INFO debate is 
> happening here I submitted it as a -sip.

Very cool draft.

So with the right MIME object (octet-stream?) and Purpose token 
(iptunnel?), we appear to have an instant answer for the "How do we use 
SIP to set up a VPN connection" problem. Subject to the constraints of 
TCP, of course, which some people don't like. And we have a solution for 
the problem of establishing a device management connection with a device 
that's behind a NAT router.

Seriously: This draft is an exact answer to the question "what is the 
extension model for SIP?" We very much need to come to an agreement on 
that model, and stop extending SIP along three different and 
incompatible axes.

If we choose the model of TOTE, then we might start considering 
deprecation of INFO, MESSAGE, SUBSCRIBE, and NOTIFY. We can also 
probably deprecate MSRP. And PUBLISH, of course. This would really clean 
up the protocol suite, at least for one way of looking at it.

This is a lot to think about. So start thinking!

--
Dean
_______________________________________________
Sip mailing list  http://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip

Re: [Sip] New I-D - TOTE - "INFO" on the media path