Re: [Sip] New I-D - TOTE

Nope.  As I tried to explain a bit in the To/from uri changes draft, it's not that SBCs want to block such things, it's up to the owner of the SBC to decide whether to allow it or not.

-hadriel

> -----Original Message-----
> From: Hannes Tschofenig [mailto:Hannes.Tschofenig@gmx.net]
> Sent: Monday, February 25, 2008 10:08 AM
> To: Hadriel Kaplan
> Cc: Jonathan Rosenberg; IETF SIP List
> Subject: Re: [Sip] New I-D - TOTE - "INFO" on the media path
>
> Hadriel,
>
> would you box block it since it travels along the media path?
>
>
> Hadriel Kaplan wrote:
> > Sweet draft.
> >
> > I would actually define the session-based IM usage for this first.  It
> would fix a lot of the NAT traversal issues we can't currently get around
> with MSRP. (the basic lesson being: don't put IP Addresses/ports in
> application layer messages when you don't need to)
> >
> > -hadriel
> >
> >
> >
> >> -----Original Message-----
> >> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
> >> Jonathan Rosenberg
> >> Sent: Friday, February 15, 2008 7:55 PM
> >> To: IETF SIP List
> >> Subject: [Sip] New I-D - TOTE - "INFO" on the media path
> >>
> >> 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.
> >>
> >> Thanks,
> >> Jonathan R.
> >> --
> >> Jonathan D. Rosenberg, Ph.D.                   499 Thornall St.
> >> Cisco Fellow                                   Edison, NJ 08837
> >> Cisco, Voice Technology Group
> >> jdrosen@cisco.com
> >> http://www.jdrosen.net                         PHONE: (408) 902-3084
> >> http://www.cisco.com
> >> _______________________________________________
> >> 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
> >>
> > _______________________________________________
> > 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
> >

_______________________________________________
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