Re: [v6ops] Happy Eyeballs and SIP

["Olle E. Johansson" <[e-mail]>]

8 mar 2011 kl. 08.53 skrev Dan Wing:

>> -----Original Message-----
>> From: [e-mail] [mailto:[e-mail]] On Behalf
>> Of Olle E. Johansson
>> Sent: Monday, March 07, 2011 2:04 PM
>> To: [e-mail]
>> Cc: [e-mail]
>> Subject: Re: [v6ops] Happy Eyeballs and SIP
>> 
>> 
>> 7 mar 2011 kl. 13.51 skrev <[e-mail]>:
>> 
>>> Dear Olle,
>>> 
>>> For the SIP case, if you don't need connectivity checks (e.g., closed
>> networks, which is in France the majority of SIP traffic) you can just
>> use the ALTC attribute defined in http://tools.ietf.org/html/draft-
>> boucadair-mmusic-altc-01.
>> That is a simple fix for the media issue - and something I think
>> developers can easily implement. We still have the issue with
>> signalling and registrations.
>>> 
>>> In case connectivity checks are needed, a variant of the happy
>> eyeballs for SIP (called Happy Eardrums) has been proposed in
>> http://tools.ietf.org/html/draft-wing-dispatch-v6-migration-00 but
>> still you need to be sure you IPv4 connectivity is working ;-).
>> Will look at this tomorrow... :-)
>> 
>> Thanks for the ALTC proposal. I am a bit hesitant to the ICE/TURN/SIP-
>> outbound combo, it will take a long time to convince developers and the
>> market to implement that package...
> 
> I agree that ICE is a big pill to swallow.  (If we're talking only
> IPv4/IPv6 selection, though, TURN is not part of that equation.)
Turn is part of the whole IPv6 migration scenario according to the soon-to-become-RFC.
> 
> However, industry experience with IPv6 on the Internet shows that
> we cannot rely on the "we both have an IPv6 address, therefore we
> have connectivty" assumption.  There are IPv6 islands (on purpose
> or on accident) which are permanent or temporary (failure of a 
> link or a router), and because IPv4 is predominant the IPv6 failure
> is not immediately noticed or corrected -- but impacts users
> that support IPv6.
Fully agree - that's why I'm insisting on the happy eyeballs approach :-)

More info about IPv6 and SIP on http://edvina.net/sipv6 and http://www.facebook.com/sipv6 for those who wants to follow, help or point out my mistakes in thoughts! I appreciate all feedback.

Cheers
/O
> 
> -d
> 
>> /O
>>> 
>>> Cheers,
>>> Med
>>> 
>>> 
>>> -----Message d'origine-----
>>> De : [e-mail] [mailto:[e-mail]] De la
>> part de Olle E. Johansson
>>> Envoyé : lundi 7 mars 2011 10:40
>>> À : [e-mail]
>>> Objet : [v6ops] Happy Eyeballs and SIP
>>> 
>>> Hi!
>>> 
>>> Has anyone considered the issues covered in the happy-eyeballs draft
>> for SIP?
>>> 
>>> A 19 or 32 second time out when placing a call is not a good user
>> experience... I think this applies to SIP over TCP, and possibly also
>> needs to be handled for UDP.
>>> I don't see this handled in the draft for IPv6 transition in the
>> Session Initiation Protocol (soon-to-be RFC 6157)
>>> 
>>> Seems like the scope of the happy eyeballs draft is HTTP, so the
>> question is if this should be expanded or if we need other drafts for
>> other protocols.
>>> 
>>> Regards,
>>> /Olle
>>> 
>>> Ref: http://tools.ietf.org/html/draft-ietf-sipping-v6-transition-07
>>> _______________________________________________
>>> v6ops mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>> 
>>> 
>> ***********************************************************************
>> *********
>>> IMPORTANT.Les informations contenues dans ce message electronique y
>> compris les fichiers attaches sont strictement confidentielles
>>> et peuvent etre protegees par la loi.
>>> Ce message electronique est destine exclusivement au(x)
>> destinataire(s) mentionne(s) ci-dessus.
>>> Si vous avez recu ce message par erreur ou s il ne vous est pas
>> destine, veuillez immediatement le signaler  a l expediteur et effacer
>> ce message
>>> et tous les fichiers eventuellement attaches.
>>> Toute lecture, exploitation ou transmission des informations
>> contenues dans ce message est interdite.
>>> Tout message electronique est susceptible d alteration.
>>> A ce titre, le Groupe France Telecom decline toute responsabilite
>> notamment s il a ete altere, deforme ou falsifie.
>>> De meme, il appartient au destinataire de s assurer de l absence de
>> tout virus.
>>> 
>>> IMPORTANT.This e-mail message and any attachments are strictly
>> confidential and may be protected by law. This message is
>>> intended only for the named recipient(s) above.
>>> If you have received this message in error, or are not the named
>> recipient(s), please immediately notify the sender and delete this e-
>> mail message.
>>> Any unauthorized view, usage or disclosure ofthis message is
>> prohibited.
>>> Since e-mail messages may not be reliable, France Telecom Group shall
>> not be liable for any message if modified, changed or falsified.
>>> Additionally the recipient should ensure they are actually virus
>> free.
>>> 
>> ***********************************************************************
>> *********
>> 
>> ---
>> * Olle E Johansson - [e-mail]
>> * Cell phone [phone], Office [phone], Sweden
>> 
>> 
>> 
>> _______________________________________________
>> v6ops mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/v6ops

---
* Olle E Johansson - [e-mail]
* Cell phone [phone], Office [phone], Sweden