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

Philip Homburg <pch-v6ops-7@u-1.phicoh.com> Fri, 22 September 2017 12:57 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 20E8D134330 for <v6ops@ietfa.amsl.com>; Fri, 22 Sep 2017 05:57:50 -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 LKoVHSIps_gI for <v6ops@ietfa.amsl.com>; Fri, 22 Sep 2017 05:57:49 -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 CEB7A134326 for <v6ops@ietf.org>; Fri, 22 Sep 2017 05:57:46 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #130) id m1dvNWc-0000FgC; Fri, 22 Sep 2017 14:57:46 +0200
Message-Id: <m1dvNWc-0000FgC@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: <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> <m1dvNK7-0000EnC@stereo.hq.phicoh.net> <20170922124641.GB45648@Space.Net>
In-reply-to: Your message of "Fri, 22 Sep 2017 14:46:41 +0200 ." <20170922124641.GB45648@Space.Net>
Date: Fri, 22 Sep 2017 14:57:45 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/afSbH47moR9w5n4t-W8_GF9ZUn8>
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:57:50 -0000

>And why is that a desirable end goal, cement IPv4 in everybody's home
>networks?
>
>Either the goal is "get rid on IPv4 on as many cables as we can" or we
>can just give up and interconnect IPv4 clouds over NAT gateways, using=20
>whatever underlay in between - MPLS, IPv6, IPv4, it will not matter.

I'm perfectly fine with not offering any kind of IPv4 all. Literally, offering
no connection at all to the IPv4 internet.

What I'm not okay with is pretending that NAT64/DNS64 is a good thing for
the internet. If you want to offer some kind of tunneled IPv4, offer a
tunnel that preserves IPv4 headers and terminate it at the first hop router.

Forcing hosts to deal with NAT64 only serves to decrease the overal
reliability of the internet. Terminating NAT64 in a CPE is also bad, but not
quite as bad as requiring hosts to deal with NAT64.