IETF Logo Mail Archive

[v6ops] 答复: Re: Call For Adoption: draft-link-v6ops-6mops

Aijun Wang <wangaijun@tsinghua.org.cn> Thu, 08 August 2024 10:33 UTC

Return-Path: <wangaijun@tsinghua.org.cn>
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 3AF7BC14F713 for <v6ops@ietfa.amsl.com>; Thu, 8 Aug 2024 03:33:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 TUOnxZZrwzQW for <v6ops@ietfa.amsl.com>; Thu, 8 Aug 2024 03:33:05 -0700 (PDT)
Received: from mail-m49198.qiye.163.com (mail-m49198.qiye.163.com [45.254.49.198]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEBEEC151091 for <v6ops@ietf.org>; Thu, 8 Aug 2024 03:33:04 -0700 (PDT)
Received: from LAPTOP09T7970K (unknown [219.142.69.76]) by smtp.qiye.163.com (Hmail) with ESMTPA id A130F7E0162; Thu, 8 Aug 2024 18:32:54 +0800 (CST)
From: Aijun Wang <wangaijun@tsinghua.org.cn>
To: 'Jen Linkova' <furry13@gmail.com>, 'Ron Bonica' <rbonica=40juniper.net@dmarc.ietf.org>
References: <BL0PR05MB5316B10BC93B52412415EC79AEBE2@BL0PR05MB5316.namprd05.prod.outlook.com> <CAFU7BAS7Wez2o=56gOd8OmHHCi6CbopoAsk7jAWUWdZ1FADdag@mail.gmail.com>
In-Reply-To: <CAFU7BAS7Wez2o=56gOd8OmHHCi6CbopoAsk7jAWUWdZ1FADdag@mail.gmail.com>
Date: Thu, 08 Aug 2024 18:32:53 +0800
Message-ID: <001801dae97e$53ef6540$fbce2fc0$@tsinghua.org.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJ/ccS7zu5LXrEELbGPO2ezyoxqzwJyjn3csMCCXvA=
Content-Language: zh-cn
X-HM-Spam-Status: e1kfGhgUHx5ZQUpXWQgPGg8OCBgUHx5ZQUlOS1dZFg8aDwILHllBWSg2Ly tZV1koWUFKTEtLSjdXWS1ZQUlXWQ8JGhUIEh9ZQVlCGB8aVh8dHkMdS0lOHUJIQlYeHw5VEwETFh oSFyQUDg9ZV1kYEgtZQVlJSkJVSk9JVU1CVUxNWVdZFhoPEhUdFFlBWU9LSFVKS0hKTkxJVUpLS1 VKQktLWQY+
X-HM-Tid: 0a91318c76f403a2kunma130f7e0162
X-HM-MType: 10
X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6Nwg6HCo*TzIwAwojHww#LxAD LCpPFDlVSlVKTElISkpISkxOSUpOVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZ EgtZQVlJSkJVSk9JVU1CVUxNWVdZCAFZQUhPTU43Bg++
Message-ID-Hash: YHH7BTMFQYOFCCWGDFQAED6KPTPC5LIE
X-Message-ID-Hash: YHH7BTMFQYOFCCWGDFQAED6KPTPC5LIE
X-MailFrom: wangaijun@tsinghua.org.cn
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: v6ops@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [v6ops] 答复: 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/FELHMmEzu-mXVRGYy_Q2w0Yv_9I>
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>

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] 代表 Jen Linkova
发送时间: 2024年8月5日 22:22
收件人: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>
抄送: 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> 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
> To unsubscribe send an email to v6ops-leave@ietf.org



--
Cheers, Jen Linkova

_______________________________________________
v6ops mailing list -- v6ops@ietf.org
To unsubscribe send an email to v6ops-leave@ietf.org

v2.27.8 | Report a Bug | By Email | System Status