[nat66] Residential use case

Fred Baker <fred@cisco.com> Mon, 25 October 2010 17:11 UTC

Return-Path: <fred@cisco.com>
X-Original-To: nat66@core3.amsl.com
Delivered-To: nat66@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C891E3A6B03 for <nat66@core3.amsl.com>; Mon, 25 Oct 2010 10:11:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.272
X-Spam-Level:
X-Spam-Status: No, score=-110.272 tagged_above=-999 required=5 tests=[AWL=0.328, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 5r2oaZtl-5Dc for <nat66@core3.amsl.com>; Mon, 25 Oct 2010 10:11:04 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id F22553A6B7D for <nat66@ietf.org>; Mon, 25 Oct 2010 10:11:02 -0700 (PDT)
Authentication-Results: sj-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAHtXxUyrRN+J/2dsb2JhbAChTnGhVpw7hUgEhFSFeYMG
X-IronPort-AV: E=Sophos;i="4.58,236,1286150400"; d="scan'208";a="286880034"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-2.cisco.com with ESMTP; 25 Oct 2010 17:12:48 +0000
Received: from stealth-10-32-244-222.cisco.com (stealth-10-32-244-222.cisco.com [10.32.244.222]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o9PHCejm028872; Mon, 25 Oct 2010 17:12:43 GMT
Received: from [127.0.0.1] by stealth-10-32-244-222.cisco.com (PGP Universal service); Mon, 25 Oct 2010 10:12:48 -0700
X-PGP-Universal: processed; by stealth-10-32-244-222.cisco.com on Mon, 25 Oct 2010 10:12:48 -0700
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <9FCA5FEC-FB26-41EB-AD67-E4D4CC7DC9B4@gmail.com>
Date: Mon, 25 Oct 2010 10:12:33 -0700
Message-Id: <795ED9F8-227E-41A3-9B96-39D7A79A8FF6@cisco.com>
References: <F55FF9C4FDB76643AE0CEC06D0F5CEB306BCC4418F@Skyhawk> <64699DF7-4F81-4AE6-80D6-1505E5EE7F2F@free.fr> <20101025155939.GU32268@Space.Net> <3C7FE7D7-83CE-4751-910C-C8CD0FC452D1@free.fr> <9FCA5FEC-FB26-41EB-AD67-E4D4CC7DC9B4@gmail.com>
To: Margaret Wasserman <margaretw42@gmail.com>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: Keith Moore <moore@network-heretics.com>, "nat66@ietf.org HappyFunBall" <nat66@ietf.org>
Subject: [nat66] Residential use case
X-BeenThere: nat66@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for discussion of IPv6-to-IPv6 NAT." <nat66.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nat66>, <mailto:nat66-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nat66>
List-Post: <mailto:nat66@ietf.org>
List-Help: <mailto:nat66-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nat66>, <mailto:nat66-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 17:11:08 -0000

On Oct 25, 2010, at 10:05 AM, Margaret Wasserman wrote:

> On Oct 25, 2010, at 12:09 PM, Rémi Després wrote:
>> It seems you accept that it may do some "harm" in the residential case (which is the case I discuss: unmanaged CPEs).
> 
> Then we are in complete agreement.  NAT66 isn't needed for most home users -- a stateful firewall would serve the same purpose.

You may be interested to review 
http://tools.ietf.org/html/draft-troan-multihoming-without-nat66
  "IPv6 Multihoming without Network Address Translation", Ole Troan, David
  Miles, Satoru Matsushima, Tadahisa Okimoto, Dan Wing, 26-Jul-10

The question of multihoming with or without NAT66 (specifically referring to this draft) was brought up by a large residential access provider, who given current solutions sees NAT66 as the only solution to its *residential* problems. Basically, the point of the draft is to describe their scenario and state that they need solutions to three residential problems or they will consider themselves as having no alternative to NAT66.