IETF Logo Mail Archive

Re: [v6ops] reclassify 464XLAT as standard instead of info

Philip Homburg <pch-v6ops-7@u-1.phicoh.com> Fri, 22 September 2017 12:44 UTC

Return-Path: <pch-bCE2691D2@u-1.phicoh.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEA50132D51 for <v6ops@ietfa.amsl.com>; Fri, 22 Sep 2017 05:44:54 -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] autolearn=ham autolearn_force=no
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 Y-kFbhE6D3CG for <v6ops@ietfa.amsl.com>; Fri, 22 Sep 2017 05:44:53 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id CB8AA132031 for <v6ops@ietf.org>; Fri, 22 Sep 2017 05:44:52 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #130) id m1dvNK7-0000EnC; Fri, 22 Sep 2017 14:44:51 +0200
Message-Id: <m1dvNK7-0000EnC@stereo.hq.phicoh.net>
To: v6ops@ietf.org
From: Philip Homburg <pch-v6ops-7@u-1.phicoh.com>
Sender: pch-bCE2691D2@u-1.phicoh.com
References: <E48DDA04-C058-4992-906E-8C8BC0E102AB@consulintel.es> <1BFA3605-4B16-4331-A7BA-3BDECBCA64EC@gmail.com> <85868796-18C7-48F4-BE69-8D50A1F47EF3@jisc.ac.uk> <472CC0F7-73C2-4A21-8F96-BBC966B01B77@employees.org> <de6b9aac-a3cc-0915-77c7-9fb880c3a16a@gmail.com> <20170921223305.B72A8878E716@rock.dv.isc.org> <CAKD1Yr13ijKCB_71_2vMyGurc3-kSraLJycGxZwf121tjp8u1Q@mail.gmail.com> <20170922070719.74AA687A424E@rock.dv.isc.org> <20170922114847.GV45648@Space.Net> <369B3917-D9F3-41D4-A7BD-DAE134310004@employees.org> <20170922122146.GY45648@Space.Net>
In-reply-to: Your message of "Fri, 22 Sep 2017 14:21:46 +0200 ." <20170922122146.GY45648@Space.Net>
Date: Fri, 22 Sep 2017 14:44:50 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/J643f48wKaXMEoRpiCV8uv997cs>
Subject: Re: [v6ops] reclassify 464XLAT as standard instead of info
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Sep 2017 12:44:55 -0000

>Yeah, but you can't have the cake and eat it.  Either we go v6-only
>everywhere, or we keep running IPv4 everywhere until everybody else
>is done, or we introduce v4/v6 NATs, or we add a CLAT to every single
>operating system out there.

You left out the option where the CPE or other first hop router offers native
IPv4 to the host (probably involving some kind of IPv4 NAT, but that is
more or less standard these days) and tunnels the complete IPv4 packet to
the network's IPv4 gateway.

This avoid all of the NAT64/DNS64 problems.

v2.23.0 | Report a Bug | By Email