RE: what problem is solved by proscribing non-64 bit prefixes?
"Dunn, Jeffrey H." <jdunn@mitre.org> Wed, 01 October 2008 19:28 UTC
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipngwg-archive@lists.ietf.org
Delivered-To: ietfarch-ipngwg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 732EE3A6C3F; Wed, 1 Oct 2008 12:28:42 -0700 (PDT)
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 23B813A6A8F for <ipv6@core3.amsl.com>; Wed, 1 Oct 2008 12:28:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.149
X-Spam-Level:
X-Spam-Status: No, score=-6.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, 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 JHmYR4RJTI6y for <ipv6@core3.amsl.com>; Wed, 1 Oct 2008 12:28:40 -0700 (PDT)
Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id 4E34A3A6AEC for <ipv6@ietf.org>; Wed, 1 Oct 2008 12:28:40 -0700 (PDT)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id m91JT2kY027239 for <ipv6@ietf.org>; Wed, 1 Oct 2008 15:29:03 -0400
Received: from imcfe2.MITRE.ORG (imcfe2.mitre.org [129.83.29.4]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id m91JT2Lw027234; Wed, 1 Oct 2008 15:29:02 -0400
Received: from IMCSRV7.MITRE.ORG ([129.83.20.57]) by imcfe2.MITRE.ORG with Microsoft SMTPSVC(6.0.3790.1830); Wed, 1 Oct 2008 15:29:01 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: what problem is solved by proscribing non-64 bit prefixes?
Date: Wed, 01 Oct 2008 15:28:59 -0400
Message-ID: <0AC4B700F00DBB4C94F95727E0991414014B250C@IMCSRV7.MITRE.ORG>
In-Reply-To: <alpine.LRH.2.00.0810010906020.13394@cust11798.lava.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: what problem is solved by proscribing non-64 bit prefixes?
thread-index: Ackj+QdH5l7XDVwgTCGSHwIUB8qf7gAAtb5g
References: <48DB374B.1000308@piuha.net> <0AC4B700F00DBB4C94F95727E0991414014B2441@IMCSRV7.MITRE.ORG> <48E230D5.3040204@gmail.com> <0AC4B700F00DBB4C94F95727E0991414014B24D2@IMCSRV7.MITRE.ORG> <48E263AD.3020801@gmail.com> <alpine.LRH.2.00.0810010906020.13394@cust11798.lava.net>
From: "Dunn, Jeffrey H." <jdunn@mitre.org>
To: Antonio Querubin <tony@lava.net>, Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-OriginalArrivalTime: 01 Oct 2008 19:29:01.0926 (UTC) FILETIME=[F57EC860:01C923FB]
Cc: "Sherman, Kurt T." <ksherman@mitre.org>, IETF IPv6 Mailing List <ipv6@ietf.org>, Ron Bonica <rbonica@juniper.net>, Steve_Eiserman@ao.uscourts.gov, Pasi Eronen <Pasi.Eronen@nokia.com>, draft-ietf-v6ops-addcon@tools.ietf.org, ralph.liguori@disa.mil, night@nist.gov, dougm@nist.gov, V6ops Chairs <v6ops-chairs@tools.ietf.org>, "Martin, Cynthia E." <cemartin@mitre.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org
Antonio, So are you suggesting that we replace IPv4 NAT with IPv6 routing proxy? Best Regards, Jeffrey Dunn Info Systems Eng., Lead MITRE Corporation. (301) 448-6965 (mobile) -----Original Message----- From: Antonio Querubin [mailto:tony@lava.net] Sent: Wednesday, October 01, 2008 3:08 PM To: Alexandru Petrescu Cc: Dunn, Jeffrey H.; IETF IPv6 Mailing List; Ron Bonica; Steve_Eiserman@ao.uscourts.gov; Pasi Eronen; Sherman, Kurt T.; ralph.liguori@disa.mil; night@nist.gov; draft-ietf-v6ops-addcon@tools.ietf.org; dougm@nist.gov; V6ops Chairs; Martin, Cynthia E. Subject: Re: what problem is solved by proscribing non-64 bit prefixes? On Tue, 30 Sep 2008, Alexandru Petrescu wrote: > In a typical WiFi Access Point landscape... > > Sellers of these devices don't have a solution to program the WiFi AP > IPv6 in the same way they'd do it for IPv4. For IPv4, the AP receives > an IPv4 address on the wired Ethernet and then does NAT and subnet > further on the wireless interface. For IPv6, although it receives a > huge /64 IPv6 prefix on the wire it can't offer Stateless Autoconfig on > the wireless interface. This begs again for IPv6 NAT. I'd say it begs for assigning the user a /56 or /48 routed to them on the /64 link. -- Antonio Querubin whois: AQ7-ARIN -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
- v6ops-addcon and longer than 64 bit prefixes Jari Arkko
- RE: v6ops-addcon and longer than 64 bit prefixes Tony Hain
- Re: v6ops-addcon and longer than 64 bit prefixes Erik Kline
- Re: v6ops-addcon and longer than 64 bit prefixes Fred Baker
- RE: v6ops-addcon and longer than 64 bit prefixes Dunn, Jeffrey H.
- Re: v6ops-addcon and longer than 64 bit prefixes Turchanyi Geza
- Re: v6ops-addcon and longer than 64 bit prefixes Brian E Carpenter
- Re: v6ops-addcon and longer than 64 bit prefixes Geoff Huston
- RE: the IPv6 Ethernet lost bits - fffe TJ
- Re: v6ops-addcon and longer than 64 bit prefixes Fred Baker
- Re: what problem is solved by proscribing non-64 … Alexandru Petrescu
- RE: v6ops-addcon and longer than 64 bit prefixes Azinger, Marla
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- Re: what problem is solved by proscribing non-64 … Brian Dickson
- RE: what problem is solved by proscribing non-64 … michael.dillon
- Re: the IPv6 Ethernet lost bits - fffe Jeroen Massar
- Re: what problem is solved by proscribing non-64 … Pekka Savola
- Re: what problem is solved by proscribing non-64 … Alexandru Petrescu
- Re: what problem is solved by proscribing non-64 … Brian Dickson
- Re: v6ops-addcon and longer than 64 bit prefixes Brian E Carpenter
- Re: what problem is solved by proscribing non-64 … Brian E Carpenter
- RE: what problem is solved by proscribing non-64 … Manfredi, Albert E
- Re: what problem is solved by proscribing non-64 … Brian Dickson
- RE: what problem is solved by proscribing non-64 … TJ
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- Re: what problem is solved by proscribing non-64 … Alexandru Petrescu
- RE: what problem is solved by proscribing non-64 … michael.dillon
- RE: what problem is solved by proscribing non-64 … michael.dillon
- Re: what problem is solved by proscribing non-64 … Alexandru Petrescu
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- Re: what problem is solved by proscribing non-64 … Mohacsi Janos
- Re: what problem is solved by proscribing non-64 … Alexandru Petrescu
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- RE: what problem is solved by proscribing non-64 … TJ
- RE: what problem is solved by proscribing non-64 … TJ
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- Re: the IPv6 Ethernet lost bits - fffe (was: what… Alexandru Petrescu
- Re: the IPv6 Ethernet lost bits - fffe Jeroen Massar
- RE: what problem is solved by proscribing non-64 … TJ
- Re: the IPv6 Ethernet lost bits - fffe Tim Chown
- RE: the IPv6 Ethernet lost bits - fffe TJ
- RE: what problem is solved by proscribing non-64 … Azinger, Marla
- RE: what problem is solved by proscribing non-64 … Azinger, Marla
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- Re: Why would anyone want to use a 64 bit interfa… Alexandru Petrescu
- RE: Why would anyone want to use a 64 bit interfa… Dunn, Jeffrey H.
- RE: what problem is solved by proscribing non-64 … TJ
- RE: the IPv6 Ethernet lost bits - fffe Dunn, Jeffrey H.
- RE: Why would anyone want to use a 64 bit interfa… TJ
- Re: Why would anyone want to use a 64 bit interfa… Alexandru Petrescu
- RE: the IPv6 Ethernet lost bits - fffe TJ
- RE: Why would anyone want to use a 64 bit interfa… TJ
- Re: the IPv6 Ethernet lost bits - fffe Alexandru Petrescu
- Re: Why would anyone want to use a 64 bit interfa… Alexandru Petrescu
- RE: Why would anyone want to use a 64 bit interfa… TJ
- RE: the IPv6 Ethernet lost bits - fffe Chip Popoviciu (cpopovic)
- Re: what problem is solved by proscribing non-64 … Antonio Querubin
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- RE: what problem is solved by proscribing non-64 … TJ
- Re: what problem is solved by proscribing non-64 … Brian E Carpenter
- Re: what problem is solved by proscribing non-64 … Brian Dickson
- Re: what problem is solved by proscribing non-64 … Brian E Carpenter
- RE: what problem is solved by proscribing non-64 … michael.dillon
- RE: what problem is solved by proscribing non-64 … Antonio Querubin
- Re: what problem is solved by proscribing non-64 … slblake
- Re: the IPv6 Ethernet lost bits - fffe Francis Dupont
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- Re: what problem is solved by proscribing non-64 … Christopher Morrow
- Re: Why would anyone want to use a 64 bit interfa… Mark Andrews
- Re: Why would anyone want to use a 64 bit interfa… Jeroen Massar
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- RE: what problem is solved by proscribing non-64 … Pekka Savola
- RE: what problem is solved by proscribing non-64 … TJ
- RE: what problem is solved by proscribing non-64 … TJ
- RE: what problem is solved by proscribing non-64 … TJ
- RE: what problem is solved by proscribing non-64 … TJ
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- RE: what problem is solved by proscribing non-64 … TJ
- Re: what problem is solved by proscribing non-64 … Brian E Carpenter
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- RE: what problem is solved by proscribing non-64 … Pekka Savola
- Re: what problem is solved by proscribing non-64 … Alexandru Petrescu
- Re: what problem is solved by proscribing non-64 … Alexandru Petrescu
- Re: what problem is solved by proscribing non-64 … Alexandru Petrescu
- Re: IPv6 Firewire - fffe (was: what problem is so… Alexandru Petrescu
- Re: IPv6 Firewire - fffe Brian E Carpenter
- Re: what problem is solved by proscribing non-64 … Mark Smith
- Re: v6ops-addcon and longer than 64 bit prefixes Jari Arkko
- Re: what problem is solved by proscribing non-64 … Jari Arkko