RE: [Sipping] new draft on ICE for opening SIPdialogs: draft-lowekamp-sipping-ice-for-sip-00

["Christer Holmberg" <[e-mail]>]

 
Hi,

Some questions.

First, it is true that there may be an intermediate which doesn't need
to be in the path once the call has been established. But, normally is a
reason why a proxy/intermediate insert a Record-Route. Why would they do
that if they at the same time say that it is ok to remove them from the
call path?

Second, in some environments user plane resources are reserved by some
intermediate, and/or gate type-of-functions are controlled by some
intermediate. These resources must be available during the whole call,
but if the resource controlling intermediates are removed from the path,
how will they know when to release the resources? Or, do you assume a
terminal will only once send a "normal" INVITE, resources will be
reserved, and then they will be available "forever"?

Third, you seem to assume that the media path will be end-to-end from
the beginning. But, a B2BUA may also control a media proxy. And, even if
the B2BUA is removed from the signalling path, the media may still
traverse it.

Regards,

Christer
















> Bruce Lowekamp wrote:
> > Title:             Using ICE to establish SIP Dialogs
> > 
> > Abstract:
> > This draft explores a way SIP can be extended to allow a new dialog 
> > directly between the endpoints to replace an initial dialog 
> that had 
> > one or more proxies in the signalling path.  This technique 
> relies on 
> > ICE to perform hole punching that allows a direct connection to be 
> > used in deployments where a sip-outbound proxy or SBC is used to 
> > establish SIP connections across NAT or firewall 
> boundaries.  It can 
> > also be used to replace such a dialog with a secure connection 
> > directly between the endpoints.  This technique can be applied to 
> > traditional proxy-based SIP routing as well as to emerging P2PSIP 
> > deployments that lack centrally located proxies.
> > 
> > This draft describes early work that evolved from ideas initially 
> > developed for P2PSIP that are no longer being pursued.  We are 
> > interested in feedback on whether there is broader interest 
> in these 
> > techniques.
> > 
> > 
> > Author(s):
> > Bruce Lowekamp, [e-mail] David Bryan, 
> > [e-mail]
> > 
> > The automatic submission tool failed on this draft, but 
> it's currently 
> > located at 
> > 
> http://www3.ietf.org/proceedings/staging/draft-lowekamp-sipping-ice-fo
> > r-sip-00.txt
> > 
> > Bruce
> > 
> > 
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP Use 
> > [e-mail] for questions on current sip Use 
> > [e-mail] for new developments of core SIP
> > 
> 
> -- 
> Jonathan D. Rosenberg, Ph.D.                   499 Thornall St.
> Cisco Fellow                                   Edison, NJ 08837
> Cisco, Voice Technology Group
> [e-mail]
> http://www.jdrosen.net                         PHONE: [phone]
> http://www.cisco.com
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP 
> Use [e-mail] for questions on current 
> sip Use [e-mail] for new developments of core SIP
> 


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [e-mail] for questions on current sip
Use [e-mail] for new developments of core SIP