Re: there _is_ IPv6 NAT - just look for it

Hesham Soliman <hesham@elevatemobile.com> Tue, 18 March 2014 03:09 UTC

Return-Path: <hesham@elevatemobile.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30D051A0233 for <ipv6@ietfa.amsl.com>; Mon, 17 Mar 2014 20:09:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10-U4yHYZV2C for <ipv6@ietfa.amsl.com>; Mon, 17 Mar 2014 20:09:10 -0700 (PDT)
Received: from smtp-1.servers.netregistry.net (smtp.netregistry.net [202.124.241.204]) by ietfa.amsl.com (Postfix) with ESMTP id EBA321A0360 for <ipv6@ietf.org>; Mon, 17 Mar 2014 20:09:09 -0700 (PDT)
Received: from [203.219.211.243] (helo=[192.168.0.8]) by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.69 #1 (Debian)) id 1WPkOg-0002fk-B2; Tue, 18 Mar 2014 14:08:59 +1100
User-Agent: Microsoft-MacOutlook/14.3.9.131030
Date: Tue, 18 Mar 2014 14:08:21 +1100
Subject: Re: there _is_ IPv6 NAT - just look for it
From: Hesham Soliman <hesham@elevatemobile.com>
To: Lorenzo Colitti <lorenzo@google.com>, "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Message-ID: <CF4E0397.4C3B7%hesham@elevatemobile.com>
Thread-Topic: there _is_ IPv6 NAT - just look for it
References: <E2C06D73-99FF-42B5-A3BE-337C307BCB0E@gmail.com> <CAKD1Yr0fjSWfPDkvc9Z53xBKxMGzYcVGzH3tLUGbjCKmgR_Duw@mail.gmail.com> <532374CD.3040100@gmail.com> <532401CB.8000003@gmail.com> <5324A1FF.3010109@gmail.com> <53255C09.7060900@gmail.com> <021E64FECA7E5A4699562F4E66716481189E49E8@XCH-PHX-503.sw.nos.boeing.com> <CAKD1Yr3sA4_4y18KBmBGOmY=PLOn1W4_F-3cgKyAfp4BQMUa=Q@mail.gmail.com> <021E64FECA7E5A4699562F4E66716481189E4C3D@XCH-PHX-503.sw.nos.boeing.com> <CAKD1Yr00jqpL+i02veXfvB2reOGmZJGr=QONe+4wSnscJbjAJQ@mail.gmail.com> <CF4E021B.4C3AC%hesham@elevatemobile.com>
In-Reply-To: <CF4E021B.4C3AC%hesham@elevatemobile.com>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-Authenticated-User: hesham@elevatemobile.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/x1KXV7UOjX1U_4pC4upSlGxDM-M
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Tue, 18 Mar 2014 03:09:12 -0000

-----Original Message-----
From: Hesham Soliman <hesham@elevatemobile.com>
Date: Tuesday, 18 March 2014 2:05 pm
To: Lorenzo Colitti <lorenzo@google.com>, "Manfredi, Albert E"
<albert.e.manfredi@boeing.com>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: there _is_ IPv6 NAT - just look for it

>>
>>mobile hotspots, and any of a host of new applications, such as
>>in-vehicle communications and IoT in general.
>>
>>
>>
>>
>>
>>Is there a reason why this stuff can't be bridged at L2?
>
>=> I haven¹t seen a general case for mobile hot spots that need multiple
>IP subnets, so I don¹t see a massive case there for shorter prefixes. But
>you can imagine a case easily enough for in-vehicle communications where
>it makes sense to have complete network separation between the vehicle¹s
>internals and the passengers traffic. Sure you can still bridge
>everything 
>but IP sub-netting gives you in-built separation for IP layer traffic
>like 
>ND ..etc relatively easily. So it would be good to support that.
>
>I just don¹t understand why all of this can¹t be done today for mobile
>routers with PD! People keep talking about it not being deployed but all
>that means is that there hasn¹t been enough demand for it yet. I don¹t
>see 
>the IETF¹s role as an organisation as one that dedicates itself to
>developing temporary workarounds. The salutations are there for people to
                                        ^^^^^ I meant solutions of course.
Looks like my auto-correct was developed by a yoga instructor :)
> 
>deploy. 
>
>Hesham
>
>
>>
>>
>>
>>--------------------------------------------------------------------
>>IETF IPv6 working group mailing list
>>ipv6@ietf.org
>>Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>--------------------------------------------------------------------