IETF Logo Mail Archive

Re: [v6ops] AWS ipv6-only features

Vasilenko Eduard <vasilenko.eduard@huawei.com> Fri, 26 November 2021 09:43 UTC

Return-Path: <vasilenko.eduard@huawei.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 509523A0C75 for <v6ops@ietfa.amsl.com>; Fri, 26 Nov 2021 01:43:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 Exysy0oZlyPw for <v6ops@ietfa.amsl.com>; Fri, 26 Nov 2021 01:43:26 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C9343A0C71 for <v6ops@ietf.org>; Fri, 26 Nov 2021 01:43:26 -0800 (PST)
Received: from fraeml701-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4J0qTB2swnz67Zjl; Fri, 26 Nov 2021 17:39:26 +0800 (CST)
Received: from mscpeml500002.china.huawei.com (7.188.26.138) by fraeml701-chm.china.huawei.com (10.206.15.50) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.20; Fri, 26 Nov 2021 10:43:22 +0100
Received: from mscpeml500001.china.huawei.com (7.188.26.142) by mscpeml500002.china.huawei.com (7.188.26.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.20; Fri, 26 Nov 2021 12:43:22 +0300
Received: from mscpeml500001.china.huawei.com ([7.188.26.142]) by mscpeml500001.china.huawei.com ([7.188.26.142]) with mapi id 15.01.2308.020; Fri, 26 Nov 2021 12:43:22 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: Mark Smith <markzzzsmith@gmail.com>, Ole Troan <otroan@employees.org>
CC: IPv6 Ops WG <v6ops@ietf.org>, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
Thread-Topic: [v6ops] AWS ipv6-only features
Thread-Index: AQHX4fsZSlp8ExgGPkarucfdaUPk/qwUenAAgAAJBgCAAAIfAIAAA8QAgAAvPYCAAJnlgIAACO6AgAAzckA=
Date: Fri, 26 Nov 2021 09:43:22 +0000
Message-ID: <15a5feb601874171a2967a165f8bf085@huawei.com>
References: <CAD6AjGRAkpMDaAh31mVL=+Gcz5PHejUxxLazr4Xb=vVRHfaSpw@mail.gmail.com> <CAO42Z2z8u_DQMd9eNSQp_RhBinXk2KyH4pdbVLMEqOta-hoG1w@mail.gmail.com> <CADzU5g5odQ82FJ0TsdNxFB42OkgLZ+PWanLLrK1roLojAUS54A@mail.gmail.com> <CAO42Z2z+ZJ_pLwZmBjZ_HFsNXQ6jok-PMRTP23ZD2UMch61wtw@mail.gmail.com> <12900505-8861-cdb4-0895-09e4db18e2eb@gmail.com> <CAKD1Yr3jZwORdNsg=FzObaY+7DDGwZR=6EVmu1GjeUgibwTsvQ@mail.gmail.com> <16AC2071-32D3-4CFE-B6A4-337FBB7AC39C@employees.org> <CAO42Z2yrvuZHZma51nSKwYVXyE7e586UDN4BzA_Qf98ocwLC-A@mail.gmail.com>
In-Reply-To: <CAO42Z2yrvuZHZma51nSKwYVXyE7e586UDN4BzA_Qf98ocwLC-A@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.195.243]
Content-Type: multipart/alternative; boundary="_000_15a5feb601874171a2967a165f8bf085huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/g4ZItAotvh1F4rvX29osHRvLtP0>
Subject: Re: [v6ops] AWS ipv6-only features
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 26 Nov 2021 09:43:31 -0000

NPT is 2-way communication.
I do not understand why people are still talking about NAT66
If NPT exists.
It is better and cover all use cases.
Hence, 1-way communication is not an argument. Use NPT.

Renumbering is not an argument
Because it is always the case for PA addresses and people are happy with it now.

Why NPT is bad?

Ed/
From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Mark Smith
Sent: Friday, November 26, 2021 12:35 PM
To: Ole Troan <otroan@employees.org>
Cc: IPv6 Ops WG <v6ops@ietf.org>; Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
Subject: Re: [v6ops] AWS ipv6-only features


On Fri, 26 Nov 2021, 20:03 , <otroan@employees.org<mailto:otroan@employees.org>> wrote:
Lorenzo,

> True, and I can't condone it, but as long as they don't leak it, the only
> operator that can be damaged is AWS itself, so it's an own goal. In fact,
> even if they do leak it, any competent ISP will drop it.
>
> The damage is not to operators, it is to application developers. Using fd00:ec2::/16 pretty much guarantees that there will be collisions within EC2 itself. If collisions can happen, that means that applications will need to learn to work with NAT66 or at least with NPTv6. That's pretty much the worst thing they could have done for IPv6 I think.

I agree that damage is bad. Unfortunately that cat is already out of the bag.
IPv6 applications already need to work through NAT64.

And likely enterprises running on ULAs with NPTv6 gateways and "firewall in the cloud" style services which typically use NAT66/NPTv6 too.


Here's an example I think of to demonstrate the point.

I've had the same mobile phone number since 1995, and anybody who knows it can still call me on it.

That's across multiple carriers due to number portability (and I'm quite aware of the scaling issue of doing that, however it seems to be working well enough).

Imagine not even knowing your own phone number. That's what NAT is doing. It makes things callers-only, even when being a receiver would be far better.





O.

_______________________________________________
v6ops mailing list
v6ops@ietf.org<mailto:v6ops@ietf.org>
https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email