Re: [v6ops] ipv6-only features

Vasilenko Eduard <vasilenko.eduard@huawei.com> Mon, 29 November 2021 17:34 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 20F8A3A07D4 for <v6ops@ietfa.amsl.com>; Mon, 29 Nov 2021 09:34:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.886
X-Spam-Level:
X-Spam-Status: No, score=-1.886 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, T_KAM_HTML_FONT_INVALID=0.01, 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 FV1ObAa5WEgx for <v6ops@ietfa.amsl.com>; Mon, 29 Nov 2021 09:34:21 -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 7CB593A07B7 for <v6ops@ietf.org>; Mon, 29 Nov 2021 09:34:21 -0800 (PST)
Received: from fraeml708-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4J2sn45MDbz67NKb; Tue, 30 Nov 2021 01:30:16 +0800 (CST)
Received: from mscpeml500002.china.huawei.com (7.188.26.138) by fraeml708-chm.china.huawei.com (10.206.15.36) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.20; Mon, 29 Nov 2021 18:34:17 +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; Mon, 29 Nov 2021 20:34:17 +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; Mon, 29 Nov 2021 20:34:17 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] ipv6-only features
Thread-Index: AQHX5TlY5RSbsA4INkqOwiMmu6eHnKwaw9pQ
Date: Mon, 29 Nov 2021 17:34:16 +0000
Message-ID: <317f09d5b37f4ebcb9ec6d8aa5d97bfa@huawei.com>
References: <CAD6AjGRAkpMDaAh31mVL=+Gcz5PHejUxxLazr4Xb=vVRHfaSpw@mail.gmail.com> <c9da6dde-d1e1-55b8-c860-08a82dbafeab@gmail.com>
In-Reply-To: <c9da6dde-d1e1-55b8-c860-08a82dbafeab@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.204.152]
Content-Type: multipart/alternative; boundary="_000_317f09d5b37f4ebcb9ec6d8aa5d97bfahuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/YvDy90N69j7ac484FU-0ICmjpdA>
Subject: Re: [v6ops] 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: Mon, 29 Nov 2021 17:34:26 -0000

I have a proposition to add one clarification word. Example:

·       IPv6-only for this node

·       IPv6-only for this service

·       IPv6-only for this domain

·       IPv6 only for <any other limiting zone>

Ed/

-----Original Message-----
From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Alexandre Petrescu
Sent: Monday, November 29, 2021 6:53 PM
To: v6ops@ietf.org
Subject: Re: [v6ops] ipv6-only features



We should clarify what we mean by IPv6-only.



Many people in this discussion mean that an IPv6-only server is reachable from an IPv4-only client, via a conversion mechanism.



However, there exist also IPv6-only servers that are not reachable from IPv4-only clients.



As such, I think there are two kinds of 'IPv6-only' serverrs: those who are reachable from IPv4-only clients and those who are not.



Alex



Le 25/11/2021 à 13:50, Ca By a écrit :

> Fyi, aws has gone beyond perfunctory ipv6 support and has released a

> series of enhancements, with a focus on ipv6-only scenarios, including

> nat64 / dns64

>

> https://aws.amazon.com/about-aws/whats-new/2021/11/aws-nat64-dns64-com

> munication-ipv6-ipv4-services/

> <https://aws.amazon.com/about-aws/whats-new/2021/11/aws-nat64-dns64-co

> mmunication-ipv6-ipv4-services/>

>

> AWS has lapped Google and Azure in advanced network features, which is

> really surprising given the early muscle Google developed at IPv6

> launch and a stronger need to differentiate …

>

> _______________________________________________

> v6ops mailing list

> v6ops@ietf.org<mailto:v6ops@ietf.org>

> https://www.ietf.org/mailman/listinfo/v6ops

>



_______________________________________________

v6ops mailing list

v6ops@ietf.org<mailto:v6ops@ietf.org>

https://www.ietf.org/mailman/listinfo/v6ops