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

"Templin, Fred L" <Fred.L.Templin@boeing.com> Fri, 08 October 2010 18:59 UTC

Return-Path: <Fred.L.Templin@boeing.com>
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 2FEA13A6923; Fri, 8 Oct 2010 11:59:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.024
X-Spam-Level:
X-Spam-Status: No, score=-5.024 tagged_above=-999 required=5 tests=[AWL=-0.725, BAYES_00=-2.599, MANGLED_PAIN=2.3, 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 e7lr2dC7JX3c; Fri, 8 Oct 2010 11:59:50 -0700 (PDT)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id 09B283A68F1; Fri, 8 Oct 2010 11:59:49 -0700 (PDT)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by stl-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id o98J0kTC022689 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 8 Oct 2010 14:00:46 -0500 (CDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id o98J0kfQ016176; Fri, 8 Oct 2010 14:00:46 -0500 (CDT)
Received: from XCH-NWHT-02.nw.nos.boeing.com (xch-nwht-02.nw.nos.boeing.com [130.247.70.248]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id o98J0j6S016109 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 8 Oct 2010 14:00:45 -0500 (CDT)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.97]) by XCH-NWHT-02.nw.nos.boeing.com ([130.247.70.248]) with mapi; Fri, 8 Oct 2010 12:00:44 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Yiu L. Lee" <yiu_lee@cable.comcast.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Ole Troan <otroan@employees.org>
Date: Fri, 8 Oct 2010 12:00:42 -0700
Thread-Topic: [Softwires] [v4tov6transition] ISP support of Native IPv6acrossNAT44 CPEs -Proposed 6a44 Specification
Thread-Index: ActnF7R6jvgfJyrK10S6cPP1kINWwgAAjU1wAAAzXykAAAZbcA==
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65C59B7951A@XCH-NW-01V.nw.nos.boeing.com>
References: <E1829B60731D1740BB7A0626B4FAF0A65C59B7950E@XCH-NW-01V.nw.nos.boeing.com> <C8D4E1F3.3EE9A%yiu_lee@cable.comcast.com>
In-Reply-To: <C8D4E1F3.3EE9A%yiu_lee@cable.comcast.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Softwires <softwires@ietf.org>, "v4tov6transition@ietf.org" <v4tov6transition@ietf.org>
Subject: Re: [v4tov6transition] [Softwires] ISP support of Native IPv6acrossNAT44 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: Fri, 08 Oct 2010 18:59:51 -0000

HI Yiu, 

> -----Original Message-----
> From: softwires-bounces@ietf.org 
> [mailto:softwires-bounces@ietf.org] On Behalf Of Yiu L. Lee
> Sent: Friday, October 08, 2010 11:58 AM
> To: Templin, Fred L; Brian E Carpenter; Ole Troan
> Cc: Softwires; v4tov6transition@ietf.org
> Subject: Re: [Softwires] [v4tov6transition] ISP support of 
> Native IPv6acrossNAT44 CPEs -Proposed 6a44 Specification
> 
> Hi Fred,
>  
> > But then the dongle/CPE becomes the ball-and-chain that
> > locks the customer into the SP's PA addressing scheme...
> > 
> This is what most ISPs offer to residential and small home 
> office users. So
> this is no worse.

Understood that it is PA in the underlay network space,
and that is all well and good. But, PI in the overlay
network space (instead of PA) is an option that should
be made available to customers.

Thanks - Fred
fred.l.templin@boeing.com

> Cheers,
> Yiu
> 
> 
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>