[v6ops] Re: 答复: Re: 答复: Re: Call For Adoption: draft-link-v6ops-6mops
Vasilenko Eduard <vasilenko.eduard@huawei.com> Thu, 08 August 2024 12:27 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 A7606C14F6BB for <v6ops@ietfa.amsl.com>; Thu, 8 Aug 2024 05:27:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.644
X-Spam-Level:
X-Spam-Status: No, score=-1.644 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QOmdzybA6esm for <v6ops@ietfa.amsl.com>; Thu, 8 Aug 2024 05:27:17 -0700 (PDT)
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 4392AC14F6F2 for <v6ops@ietf.org>; Thu, 8 Aug 2024 05:27:17 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4WfmSX0Ndfz6K9G9; Thu, 8 Aug 2024 20:24:28 +0800 (CST)
Received: from mscpeml500004.china.huawei.com (unknown [7.188.26.250]) by mail.maildlp.com (Postfix) with ESMTPS id 384851406AD; Thu, 8 Aug 2024 20:27:14 +0800 (CST)
Received: from mscpeml500004.china.huawei.com (7.188.26.250) by mscpeml500004.china.huawei.com (7.188.26.250) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.34; Thu, 8 Aug 2024 15:27:13 +0300
Received: from mscpeml500004.china.huawei.com ([7.188.26.250]) by mscpeml500004.china.huawei.com ([7.188.26.250]) with mapi id 15.02.1258.034; Thu, 8 Aug 2024 15:27:13 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: Aijun Wang <wangaijun@tsinghua.org.cn>, 'Tim Chown' <Tim.Chown@jisc.ac.uk>, 'Brian Carpenter' <brian.e.carpenter@gmail.com>
Thread-Topic: [v6ops] 答复: Re: 答复: Re: Call For Adoption: draft-link-v6ops-6mops
Thread-Index: AQHa6Yi0M2UJsHjcLEWvHXXlTMJLk7IdSDew
Date: Thu, 08 Aug 2024 12:27:13 +0000
Message-ID: <948bbd6728c547c495be11fa2f0cc5c7@huawei.com>
References: <BL0PR05MB5316B10BC93B52412415EC79AEBE2@BL0PR05MB5316.namprd05.prod.outlook.com> <CAFU7BAS7Wez2o=56gOd8OmHHCi6CbopoAsk7jAWUWdZ1FADdag@mail.gmail.com> <001801dae97e$53ef6540$fbce2fc0$@tsinghua.org.cn> <CANMZLAbZiYhLGB5m_RHbh1aYok770ca3_K_TghSMGqTUvGmNRg@mail.gmail.com> <DB9PR07MB7771686DB74D4C7D3905E3FFD6B92@DB9PR07MB7771.eurprd07.prod.outlook.com> <003801dae988$8b84ef20$a28ecd60$@tsinghua.org.cn>
In-Reply-To: <003801dae988$8b84ef20$a28ecd60$@tsinghua.org.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.199.59.222]
Content-Type: multipart/alternative; boundary="_000_948bbd6728c547c495be11fa2f0cc5c7huaweicom_"
MIME-Version: 1.0
Message-ID-Hash: CH7PTCF35BJESQBRLY5O5JGTAP4SJ2RG
X-Message-ID-Hash: CH7PTCF35BJESQBRLY5O5JGTAP4SJ2RG
X-MailFrom: vasilenko.eduard@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-v6ops.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: 'Ron Bonica' <rbonica=40juniper.net@dmarc.ietf.org>, 'IPv6 Ops WG' <v6ops@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [v6ops] Re: 答复: Re: 答复: Re: Call For Adoption: draft-link-v6ops-6mops
List-Id: v6ops discussion list <v6ops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/KJx2crXlK-M-8KFM6EM5JqGBumk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Owner: <mailto:v6ops-owner@ietf.org>
List-Post: <mailto:v6ops@ietf.org>
List-Subscribe: <mailto:v6ops-join@ietf.org>
List-Unsubscribe: <mailto:v6ops-leave@ietf.org>
Carriers do not care about IPv6-mostly, because the last link is typically not visible for carriers. (Mobile is an exception but IPv6-mostly is not for mobiles) Carriers would still see DualStack from a gateway (CPE?) demarcating such a link. Nothing would change for Carriers. Ed/ From: Aijun Wang <wangaijun@tsinghua.org.cn> Sent: Thursday, August 8, 2024 14:46 To: 'Tim Chown' <Tim.Chown@jisc.ac.uk>; 'Brian Carpenter' <brian.e.carpenter@gmail.com> Cc: 'Ron Bonica' <rbonica=40juniper.net@dmarc.ietf.org>; 'IPv6 Ops WG' <v6ops@ietf.org> Subject: [v6ops] 答复: Re: 答复: Re: Call For Adoption: draft-link-v6ops-6mops No. Declaring the “IPv6-Only” network does not preclude that the network can support IPv4 communication. The IPv4 communication can still be transmitted via the tunnel technology, that is “IPv4 Communication as a IPv6 service” Comparing with evolution of mobile technologies, there is no operator declare their network is “4G-mostly network” when they want to put forward to the 4G phase, but need still support the 3G host/endpoint. Introducing the “IPv6-Mostly Network” concept, in my POV, is worse than the “Dual Stack”, and it will also mask some hinder problems that can’t be emerged at the dual-stack phase. When the operators declare clearly they are toward to the “IPv6-Only Network”, they can certainly accelerate the conversion of IPv6-only application, and also the gradual removal of the outdated hosts. But, introduce the concept of “IPv6-Mostly Network”, can give the transition more time to take action-----Similar with the effect of “Dual Stack”. Best Regards Aijun Wang China Telecom 发件人: Tim Chown [mailto:Tim.Chown@jisc.ac.uk] 发送时间: 2024年8月8日 18:55 收件人: Brian Carpenter <brian.e.carpenter@gmail.com<mailto:brian.e.carpenter@gmail.com>>; Aijun Wang <wangaijun@tsinghua.org.cn<mailto:wangaijun@tsinghua.org.cn>> 抄送: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org<mailto:rbonica=40juniper.net@dmarc.ietf.org>>; IPv6 Ops WG <v6ops@ietf.org<mailto:v6ops@ietf.org>> 主题: Re: [v6ops] Re: 答复: Re: Call For Adoption: draft-link-v6ops-6mops Indeed, it’s a very nice way to get on the path to removing IPv4 and a nice term for that process; the “most” referring to the property that most hosts on a subnet switch to IPv6-only, while those not capable continue to use IPv4 for some or all operation. Tim From: Brian Carpenter <brian.e.carpenter@gmail.com<mailto:brian.e.carpenter@gmail.com>> Date: Thursday, 8 August 2024 at 11:51 To: Aijun Wang <wangaijun@tsinghua.org.cn<mailto:wangaijun@tsinghua.org.cn>> Cc: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org<mailto:rbonica=40juniper.net@dmarc.ietf.org>>, IPv6 Ops WG <v6ops@ietf.org<mailto:v6ops@ietf.org>> Subject: [v6ops] Re: 答复: Re: Call For Adoption: draft-link-v6ops-6mops Aijun, I disagree. When talking to site operators who want to proceed towards IPv6 infastructure but have vital systems that cannot be updated from IPv4 immediately, the new term "IPv6 mostly" is exactly what they want to hear. Many sites are in that situation but would like to avoid dual stack on the wire. (via tiny screen & keyboard) Regards, Brian Carpenter On Thu, 8 Aug 2024, 22:33 Aijun Wang, <wangaijun@tsinghua.org.cn<mailto:wangaijun@tsinghua.org.cn>> wrote: Hi, It seems that the newly assigned name "IPv6-Mostly network" may lead confusion or need more explanations to the customers. How about change the document name solely to "Deployment and Operations Consideration on IPv6-Only Network", and omit the introduction of new concept of "IPv6-Mostly network"? And, for the operator transit to IPv6-Only network, besides the C2S(client to server) communication, the C2C(client to client) communication requirement should also need to be addressed. It seems the document is lack of consideration for such part. Best Regards Aijun Wang China Telecom -----邮件原件----- 发件人: forwardingalgorithm@ietf.org<mailto:forwardingalgorithm@ietf.org> [mailto:forwardingalgorithm@ietf.org<mailto:forwardingalgorithm@ietf.org>] 代表 Jen Linkova 发送时间: 2024年8月5日 22:22 收件人: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org<mailto:40juniper.net@dmarc.ietf.org>> 抄送: v6ops@ietf.org<mailto:v6ops@ietf.org> 主题: [v6ops] Re: Call For Adoption: draft-link-v6ops-6mops The draft can be found at https://datatracker.ietf.org/doc/draft-link-v6ops-6mops/ On Mon, Aug 5, 2024 at 11:21 PM Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org<mailto:40juniper.net@dmarc.ietf.org>> wrote: > > Friends, > > This message begins a Call For Adoption for draft-link-v6ops-6mops. Please read the draft and send your comments in response to this email. > > The call for adoption will close on August 19, 2024. > > Ron > > > > Juniper Business Use Only > > _______________________________________________ > v6ops mailing list -- v6ops@ietf.org<mailto:v6ops@ietf.org> > To unsubscribe send an email to v6ops-leave@ietf.org<mailto:v6ops-leave@ietf.org> -- Cheers, Jen Linkova _______________________________________________ v6ops mailing list -- v6ops@ietf.org<mailto:v6ops@ietf.org> To unsubscribe send an email to v6ops-leave@ietf.org<mailto:v6ops-leave@ietf.org> _______________________________________________ v6ops mailing list -- v6ops@ietf.org<mailto:v6ops@ietf.org> To unsubscribe send an email to v6ops-leave@ietf.org<mailto:v6ops-leave@ietf.org>
- [v6ops] Call For Adoption: draft-link-v6ops-6mops Ron Bonica
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… Jen Linkova
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… Vasilenko Eduard
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… Xipengxiao
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… Mark Smith
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… Paolo Volpato
- [v6ops] 答复: Re: Call For Adoption: draft-link-v6o… Aijun Wang
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… Kawashima Masanobu(川島 正伸)
- [v6ops] Re: 答复: Re: Call For Adoption: draft-link… Brian Carpenter
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… Brian E Carpenter
- [v6ops] Re: 答复: Re: Call For Adoption: draft-link… Tim Chown
- [v6ops] 答复: Re: 答复: Re: Call For Adoption: draft-… Aijun Wang
- [v6ops] Re: 答复: Re: 答复: Re: Call For Adoption: dr… Vasilenko Eduard
- [v6ops] Re: 答复: Re: 答复: Re: Call For Adoption: dr… Nick Buraglio
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… Jen Linkova
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… Chongfeng Xie
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… tom petch
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… jordi.palet@consulintel.es
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… Nick Buraglio
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… Jen Linkova
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… jordi.palet@consulintel.es
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… Jen Linkova
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… jordi.palet@consulintel.es
- [v6ops] Re: 答复: Re: 答复: Re: Call For Adoption: dr… Jen Linkova
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… Brian E Carpenter
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… Tim Chown
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… Costello, Tom
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… Gyan Mishra
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… Tommy Jensen
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… Jeremy Duncan
- [v6ops] Re: Call For Adoption: draft-link-v6ops-6… Nick Buraglio