Re: [v4tov6transition] [Softwires] ISP support of Native IPv6 across NAT44 CPEs - Proposed 6a44 Specification

Olivier Vautrin <ovautrin@juniper.net> Thu, 07 October 2010 03:21 UTC

Return-Path: <ovautrin@juniper.net>
X-Original-To: v4tov6transition@core3.amsl.com
Delivered-To: v4tov6transition@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3850F3A6D53; Wed, 6 Oct 2010 20:21:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.506
X-Spam-Level:
X-Spam-Status: No, score=-6.506 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 sbL8Uj85QnxZ; Wed, 6 Oct 2010 20:21:34 -0700 (PDT)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169]) by core3.amsl.com (Postfix) with ESMTP id BD0973A6C43; Wed, 6 Oct 2010 20:21:34 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP ID DSNKTK08+zrm2tUQp75Kxz2pdFrgg1lbJJMr@postini.com; Wed, 06 Oct 2010 20:22:36 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB02-HQ.jnpr.net ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Wed, 6 Oct 2010 20:21:06 -0700
From: Olivier Vautrin <ovautrin@juniper.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Softwires <softwires@ietf.org>
Date: Wed, 6 Oct 2010 20:21:02 -0700
Thread-Topic: [Softwires] ISP support of Native IPv6 across NAT44 CPEs - Proposed 6a44 Specification
Thread-Index: Actkzvxqwpwxgg7tQnu5mZEaWIjmeAA/KUMQ
Message-ID: <84600D05C20FF943918238042D7670FD37326C5FF3@EMBX01-HQ.jnpr.net>
References: <31672657-0CCB-4C2B-B44A-AEE73B588960@free.fr> <4CAB8F97.90501@gmail.com>
In-Reply-To: <4CAB8F97.90501@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 07 Oct 2010 18:34:08 -0700
Cc: "v4tov6transition@ietf.org" <v4tov6transition@ietf.org>
Subject: Re: [v4tov6transition] [Softwires] ISP support of Native IPv6 across NAT44 CPEs - Proposed 6a44 Specification
X-BeenThere: v4tov6transition@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <v4tov6transition.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4tov6transition>, <mailto:v4tov6transition-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v4tov6transition>
List-Post: <mailto:v4tov6transition@ietf.org>
List-Help: <mailto:v4tov6transition-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4tov6transition>, <mailto:v4tov6transition-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2010 03:21:36 -0000

Hi all, very interesting draft.

I think it would be worthwhile to elaborate a bit more in the draft why Teredo is not viable and thus an alternative is needed.

In this draft, I see 2 issues described for Teredo:
1) "clients sometimes believing that they have Teredo connectivity when in fact they don't"
Clients could have the same issue in 6a44 AFAIK. There is no mechanism in 6a44 to check the data path connectivity. I think the real issue here is lack of reliable teredo relay or lack of reliable data path (MTU issues).
2) "Teredo server and relay being very remote"

Both issues can be fixed if ISPs deploy their own Teredo server/relay. Which is basically what they will do with 6a44. So, I don't really see the issues described in the paper as important enough to create another protocol.

I do think there are other issues with Teredo:
1) Use of a WK prefix instead of an ISP prefix. This means the return path can be broken as with 6to4.
2) Most client Teredo implementation need a full cone NAT on the CPE. Most CPE use symmetric NAT. so a CPE upgrade could be needed.
3) Most OS still prefer IPv4 over Teredo. This means it does not increase the Ipv6 traffic.
4) On vista, it seems that traffic is sent to a Teredo tunnel only if another Ipv6@ is created (I didn't check this though). Source: http://yorickdowne.wordpress.com/2008/01/26/ipv6-at-home-part-1-overview-teredo/

/Olivier

> -----Original Message-----
> From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On
> Behalf Of Brian E Carpenter
> Sent: Tuesday, October 05, 2010 9:51 PM
> To: Softwires
> Cc: v4tov6transition@ietf.org
> Subject: Re: [Softwires] ISP support of Native IPv6 across NAT44 CPEs -
> Proposed 6a44 Specification
> 
> On 2010-10-05 22:26, Rémi Després wrote:
> > Hi all,
> >
> > Draft-despres-softwire-6a44-00, coauthored with Brian and Sheng, has
> just been posted (http://tools.ietf.org/html/draft-despres-softwire-
> 6a44-00).
> > It describes a solution for ISPs to offer native IPv6 across IPv4-
> only CPEs (NAT44 CPEs).
> >
> > It results from convergence discussion between authors of draft-
> carpenter-6man-sample-00 and draft-despres-softwire-6rdplus-00, taking
> into account comments made by authors of draft-lee-softwire-6rd-udp-01,
> and those made other Softwire WG participants since IETF 78.
> >
> > It is submitted to become, after discussion in the WG, a Softwire I-
> D.
> 
> By the way, we do discuss in the draft why it's a useful alternative to
> both tunnel brokers (such as Hexago and SixXs) or Teredo. We don't
> explicitly discuss why we think it's also a useful alternative to an
> L2TP
> solution, but the arguments are, I think, similar to those for the
> tunnel
> brokers (apart from our "hobbyist" comment).
> 
>     Brian
> 
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires