[v6ops] Re: I-D: draft-cao-v6ops-ipv6-monitoring-deployment
"赵菁(联通集团本部)" <zhaoj501@chinaunicom.cn> Mon, 02 December 2024 13:21 UTC
Return-Path: <zhaoj501@chinaunicom.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 EE5EAC14F689 for <v6ops@ietfa.amsl.com>; Mon, 2 Dec 2024 05:21:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.325
X-Spam-Level:
X-Spam-Status: No, score=-1.325 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, INVALID_MSGID=0.568, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 n9QFlaOe7oyd for <v6ops@ietfa.amsl.com>; Mon, 2 Dec 2024 05:20:59 -0800 (PST)
Received: from sendd.mailex.chinaunicom.cn (sendb.mailex.chinaunicom.cn [123.138.59.137]) (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 1F2E0C14F610 for <v6ops@ietf.org>; Mon, 2 Dec 2024 05:20:53 -0800 (PST)
Received: from bg5.exmail.qq.com (unknown [10.172.147.156]) by sendd.mailex.chinaunicom.cn (SkyGuard) with ESMTPS id 4Y24D06Z0PznR0sW for <v6ops@ietf.org>; Mon, 2 Dec 2024 21:20:48 +0800 (CST)
X-QQ-mid: qylesmxpt1733145646twieig4gu
Received: from LAPTOP-1TLQUKBE ( [10.252.16.99]) by bizesmtp.qq.com (ESMTP) with id ; Mon, 02 Dec 2024 21:20:46 +0800 (CST)
X-QQ-SSF: 01000000000000303210000A0000000
X-QQ-FEAT: VcsBoJIQY93oWinW+EQbnCdMZWJSiGY6
X-QQ-GoodBg: 0
Date: Mon, 02 Dec 2024 21:20:49 +0800
References: <202411112159360183258@chinaunicom.cn>, <DB9PR07MB77718FD6EFD49F4D1A57CA26D6582@DB9PR07MB7771.eurprd07.prod.outlook.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.25.254[cn]
Mime-Version: 1.0
Message-ID: <2024120221204800720529@chinaunicom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart657371368512_=----"
From: "赵菁(联通集团本部)" <zhaoj501@chinaunicom.cn>
To: Tim Chown <tim.chown=40jisc.ac.uk@dmarc.ietf.org>
X-QQ-SENDSIZE: 520
Feedback-ID: qylesmxpt:chinaunicom.cn:xx-kxq-mail-:xx-kxq-mail-0002.novalocal
Message-ID-Hash: HOEP7I4J6ILLAFBAB6Y562LI4YKCEZCV
X-Message-ID-Hash: HOEP7I4J6ILLAFBAB6Y562LI4YKCEZCV
X-MailFrom: zhaoj501@chinaunicom.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 <v6ops@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [v6ops] Re: I-D: draft-cao-v6ops-ipv6-monitoring-deployment
List-Id: v6ops discussion list <v6ops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/4fTp6h1l6Y4wRXg8ZsoCdlu5QaU>
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>
Dear Tim, Thank you for your assistance! The website you recommended are very helpful to us. About Q1, based on your advice, we have adjusted our document. ( URL: https://www.ietf.org/archive/id/draft-cao-v6ops-ipv6-monitoring-deployment-01.html ) The specific changes we made are as follows: 1. Updated Section 3.1 'IPv6 Deployment Analysis'. We have condensed the section on the driving factors of IPv6 deployment. 2. Added a section 4.1 'Current Approaches to Monitoring IPv6 Deployment'. We have summarized and outlined a list of current monitoring approaches. 3. Added a section 4.2 'Potential Requirements' before section 4.3 'Problem Statement'. (Updated the Abstract of the document) We have not included a comparison of the advantages and disadvantages of current approaches in this document. This is because we conducted a comprehensive analysis of the common shortcomings in current IPv6 deployment monitoring approaches in Section 4.3. Our ultimate goal for the future is to develop an IPv6 deployment monitoring approach that can identify weaknesses in the current IPv6 deployment, thereby enhancing the IPv6 deployment rate. Consequently, this will pose new potential requirements (outlined in Section 4.2) for current approaches. What are your thoughts on this? 4. Changed the title of section 5 to 'Improvement Considerations'. About Q2, technologies such as perfSONAR and RIPE Atlas are the underlying network measurement tools/systems. Our draft focuses more on proposing a method and corresponding interface model. The underlying technology is not limited to what technology is used, and we focus more on finding the bottleneck of IPv6, that is, why IPv6 is not currently being used instead of IPv4, by collecting relevant data to find the reasons. Thank you for your attention to and suggestions on our documents. Look forward suggestions! Many Thanks! Best regards, Jing zhaoj501@chinaunicom.cn From: Tim Chown Date: 2024-11-12 00:04 To: 赵菁(联通集团本部); v6ops Subject: [v6ops] Re: I-D: draft-cao-v6ops-ipv6-monitoring-deployment Hi, On 11/11/2024, 14:01, "赵菁(联通集团本部)" <zhaoj501@chinaunicom.cn> wrote: You don't often get email from zhaoj501@chinaunicom.cn. Learn why this is important Dear all, We have been physically present at IETF 121 and introduced the document concerning IPv6 Network Monitoring Deployment. I would like to draw your attention to our drafts: · https://datatracker.ietf.org/doc/draft-cao-v6ops-ipv6-monitoring-deployment/ I think this draft would benefit from providing examples or even a good list of current approaches to monitoring IPv6 deployment, and comparing the strengths and weaknesses of each. Some of these can be found at https://worldipv6launch.org/measurements/. I’d remove the section on reasons to deploy. · https://datatracker.ietf.org/doc/draft-pang-v6ops-usecases-ipv6-monitoring/ I think there are quite a few e2e monitoring tools that can be used, some of which are quite open like RIPE Atlas, others of which need a little bit of specialist knowledge like perfSONAR. If you are suggesting a couple of use cases, perhaps you have ideas for the requirements for the e2e tools you are arguing are needed? Best wishes, Tim We believe that feedback from the v6ops Working Group (WG) would be invaluable in refining these drafts. We welcome any comments, suggestions, or questions you might have. We look forward to your input! Best regards, Jing zhaoj501@chinaunicom.cn 如果您错误接收了该邮件,请通过电子邮件立即通知我们。请回复邮件到 hqs-spmc@chinaunicom.cn,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to hqs-spmc@chinaunicom.cn ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our.