Re: TR: I-DAction:draft-boucadair-sipping-ipv6-atypes-00.txt

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> -----Original Message-----
> From: Dan Wing [mailto:dwing@xxxxxxxxx]
> Sent: Monday, March 09, 2009 11:44 PM
> 
> If there are other SIP or SIPPING documents which describe the
> IPv4/IPv6 transition, please share.

Oh, I didn't know we had to have a separate RFC X to state how to use another RFC Y, and that without X there was no way to use Y.
Should we have an sdp-cap-neg-transition document too?  ;)


> > It turns out we have a means of detecting that already: the
> > human will hang up if they don't hear anything.  But more
> > seriously, it's not like you need ICE to detect which one is
> > working either.  You can use RTCP, for example.
> 
> RTCP isn't sent too often or reliably, though (how is a=rtcp and
> even/odd port support working out in practice?).

My comment was a trap actually: if you argue RTCP can't be used for such a check because it isn't supported too often, I can turn that argument around on ICE very easily.  In fact I'd wager there're more devices doing RTCP than ICE, by a big margin.
(How is a=candidate working out in practice? :)

[BTW, a=rtcp is broken and should be deprecated, as you know, but you don't need it to use RTCP obviously]

> Contrary to everyone's hopes and desires, IPv6 endpoints are not
> universally deployed.  
> So getting v6 endpoints to include
> features that are necessary for a successful IPv4/IPv6 transition
> is exactly aligned with the the needs of vendors implementing
> IPv6 endpoints.

Sure, we need to put the burden of interworking with IPv4 legacy devices squarely on the shoulders of IPv6, no doubt. (whether it'll be solely handled by IPv6 endpoints in all cases is debatable, but that's orthogonal)  

But I fail to see how ICE is necessary or sufficient to fit that bill.  Either way, we need to provide IPv6 devices with as *many* tools as possible, so that your failed-session example does not occur.


> Of course, if they just grin and expect the SBC solves the
> problem, we can all sleep easier at night. 

I didn't say that, and I don't even believe it.  There are many SIP domains which have no SBC's, and shouldn't.  For them, ICE is great.  For others, not so much.  We should let the two communicate.

-hadriel
_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip
Use sip@xxxxxxxx for new developments of core SIP

[Index of Archives]     [IETF Announce]     [IETF Discussion]     [Linux SCSI]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Big List of Linux Books]

  Powered by Linux