Re: [v6ops] Happy Eyeballs and SIP

<mohamed.boucadair@orange-ftgroup.com> Tue, 08 March 2011 10:11 UTC

Return-Path: <mohamed.boucadair@orange-ftgroup.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E80B03A6835 for <v6ops@core3.amsl.com>; Tue, 8 Mar 2011 02:11:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.894
X-Spam-Level:
X-Spam-Status: No, score=-2.894 tagged_above=-999 required=5 tests=[AWL=-0.246, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8VPG6ldS53Zs for <v6ops@core3.amsl.com>; Tue, 8 Mar 2011 02:11:31 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by core3.amsl.com (Postfix) with ESMTP id 99D853A6834 for <v6ops@ietf.org>; Tue, 8 Mar 2011 02:11:28 -0800 (PST)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id C1B57264112; Tue, 8 Mar 2011 11:12:39 +0100 (CET)
Received: from PUEXCH51.nanterre.francetelecom.fr (unknown [10.101.44.31]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id A62CD23804B; Tue, 8 Mar 2011 11:12:39 +0100 (CET)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.11]) by PUEXCH51.nanterre.francetelecom.fr ([10.101.44.31]) with mapi; Tue, 8 Mar 2011 11:12:39 +0100
From: mohamed.boucadair@orange-ftgroup.com
To: "Olle E. Johansson" <oej@edvina.net>, Dan Wing <dwing@cisco.com>
Date: Tue, 08 Mar 2011 11:12:38 +0100
Thread-Topic: [v6ops] Happy Eyeballs and SIP
Thread-Index: Acvdd2vOfI0kopjRTfKYjI9o0gT6pgAALoVA
Message-ID: <14620_1299579159_4D760117_14620_182275_1_94C682931C08B048B7A8645303FDC9F33C4DA5106C@PUEXCB1B.nanterre.francetelecom.fr>
References: <83928D99-9809-4BF9-A710-28366AF46BBB@edvina.net> <24436_1299502310_4D74D4E6_24436_185484_1_94C682931C08B048B7A8645303FDC9F33C4DA50BCA@PUEXCB1B.nanterre.francetelecom.fr> <A41572A5-B6CE-4699-9580-03E1996B631A@edvina.net> <18c501cbdd65$f7428bc0$e5c7a340$@com> <3CFAED05-4FB9-4596-90A5-E73CB4DC717C@edvina.net>
In-Reply-To: <3CFAED05-4FB9-4596-90A5-E73CB4DC717C@edvina.net>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.5.9.395186, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.3.8.84219
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] Happy Eyeballs and SIP
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2011 10:11:37 -0000

Dear Olle,

Thank you for the link.

You might mention also the following:

* IPv6 IP ABNF is not correct. Rules defined in RFC3986 should be used instead for encoding IPv6 address in SIP URI.
* For the comparison of SIP URIs enclosing an IPv6 address, the rules defined in RFC3261 are broken; you need use those in RFC5954
* SIP Proxy Servers can not rely on the AoC to determine the IP capabilities of the SIP UA. A candidate solution is documented in http://tools.ietf.org/html/draft-boucadair-dispatch-ipv6-atypes-00.
* IPv6 SIP Torture Tests are documented in RFC5118. 

For other points, we can discuss this offline.

Cheers,
Med 


-----Message d'origine-----
De : Olle E. Johansson [mailto:oej@edvina.net] 
Envoyé : mardi 8 mars 2011 10:59
À : Dan Wing
Cc : BOUCADAIR Mohamed OLNC/NAD/TIP; v6ops@ietf.org
Objet : Re: [v6ops] Happy Eyeballs and SIP


8 mar 2011 kl. 08.53 skrev Dan Wing:

>> -----Original Message-----
>> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
>> Of Olle E. Johansson
>> Sent: Monday, March 07, 2011 2:04 PM
>> To: mohamed.boucadair@orange-ftgroup.com
>> Cc: v6ops@ietf.org
>> Subject: Re: [v6ops] Happy Eyeballs and SIP
>> 
>> 
>> 7 mar 2011 kl. 13.51 skrev <mohamed.boucadair@orange-ftgroup.com>:
>> 
>>> 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 : v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] De la
>> part de Olle E. Johansson
>>> Envoyé : lundi 7 mars 2011 10:40
>>> À : v6ops@ietf.org
>>> 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
>>> v6ops@ietf.org
>>> 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 - oej@edvina.net
>> * Cell phone +46 70 593 68 51, Office +46 8 96 40 20, Sweden
>> 
>> 
>> 
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops

---
* Olle E Johansson - oej@edvina.net
* Cell phone +46 70 593 68 51, Office +46 8 96 40 20, Sweden




********************************************************************************
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.
********************************************************************************