Re: [v6ops] New Version Notification for draft-xiao-v6ops-nd-deployment-guidelines-02.txt
Chongfeng XIE <xiechf@chinatelecom.cn> Sat, 02 July 2022 02:25 UTC
Return-Path: <xiechf@chinatelecom.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 3D8FFC157B33 for <v6ops@ietfa.amsl.com>; Fri, 1 Jul 2022 19:25:00 -0700 (PDT)
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_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 KVARbgNxJq-D for <v6ops@ietfa.amsl.com>; Fri, 1 Jul 2022 19:24:56 -0700 (PDT)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.227]) by ietfa.amsl.com (Postfix) with ESMTP id 62FFAC157B54 for <v6ops@ietf.org>; Fri, 1 Jul 2022 19:24:37 -0700 (PDT)
HMM_SOURCE_IP: 172.18.0.48:40590.319081508
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-114.250.180.45 (unknown [172.18.0.48]) by chinatelecom.cn (HERMES) with SMTP id 5F14428008E; Sat, 2 Jul 2022 10:24:29 +0800 (CST)
X-189-SAVE-TO-SEND: 66040161@chinatelecom.cn
Received: from ([172.18.0.48]) by app0024 with ESMTP id b5e92e8033bd43c6b0f3c9f641fe7532 for xipengxiao=40huawei.com@dmarc.ietf.org; Sat, 02 Jul 2022 10:24:32 CST
X-Transaction-ID: b5e92e8033bd43c6b0f3c9f641fe7532
X-Real-From: xiechf@chinatelecom.cn
X-Receive-IP: 172.18.0.48
X-MEDUSA-Status: 0
Sender: xiechf@chinatelecom.cn
Date: Sat, 02 Jul 2022 10:24:30 +0800
From: Chongfeng XIE <xiechf@chinatelecom.cn>
To: Xipengxiao <xipengxiao=40huawei.com@dmarc.ietf.org>, list <v6ops@ietf.org>
Cc: Gyan Mishra <gyan.s.mishra@verizon.com>
References: <165668326774.27360.2092628030855259850@ietfa.amsl.com>, <99c4576853804cd3895f65bb66b18ab0@huawei.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.23.121[cn]
Mime-Version: 1.0
Message-ID: <202207021024293115595@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart871540318524_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/KBWHxpp_2pORBLoVH--FMii7AME>
Subject: Re: [v6ops] New Version Notification for draft-xiao-v6ops-nd-deployment-guidelines-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
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: Sat, 02 Jul 2022 02:25:00 -0000
Hi, Xipeng, I 'd like to make a personal comment on the term "deployment". Usually, this term refers to the deployment and application of a device or system for network operators or enterprise customers who operate their own network. Specific protocols such as ND are part of the device or system. Whether or how the device supports ND should be decided prior to the phase of operator deployment. So is it replaced by other terms? What's your opinion? Best regards Chongfeng From: Xipengxiao Date: 2022-07-01 22:02 To: list CC: Gyan Mishra Subject: Re: [v6ops] New Version Notification for draft-xiao-v6ops-nd-deployment-guidelines-02.txt Dear folks, We submitted a major revision of ND-deployment-guidelines draft. We believe its quality is significantly improved. The key points are below. Your review and comments will be greatly appreciated. XiPeng & the co-authors Problem statement: • Various issues and solutions are documented in more than 30 RFCs. It is difficult to keep track of all these issues and solutions, and how the various solutions fit together. These include: ND Proxy, Optimistic ND, ND for mobile broadband, ND for fixed broadband, ND Mediation, Operational ND Problems, Wireless ND (WiND), DAD Proxy, SAVI/RA-Guard/RA-Guard+, Enhanced DAD, Scalable ARP, Reducing Router Advertisements, Unique Prefix Per Host, GRAND, Proxy ARP/ND for EVPN etc. This draft: • Summarizes the known ND issues and optimization solutions into a one-stop reference. • Present an insight: isolating hosts is effective in solving ND issues. • Propose 4 isolation methods and discuss their applicability: P2P link & subnet isolation, P2MP link & subnet isolation, GUA isolation, proxy isolation • Describe guidelines for selecting a suitable isolation method based on the deployment scenario. Regards, Xipeng Xiao, Ph.D. +49 162 2047 661 xipengxiao@huawei.com Dusseldorf, Germany -----Original Message----- From: internet-drafts@ietf.org <internet-drafts@ietf.org> Sent: Friday, July 1, 2022 3:48 PM To: Vasilenko Eduard <vasilenko.eduard@huawei.com>; Eduard Metz <eduard.metz@kpn.com>; Vasilenko Eduard <vasilenko.eduard@huawei.com>; Gyan Mishra <gyan.s.mishra@verizon.com>; Xipengxiao <xipengxiao@huawei.com> Subject: New Version Notification for draft-xiao-v6ops-nd-deployment-guidelines-02.txt A new version of I-D, draft-xiao-v6ops-nd-deployment-guidelines-02.txt has been successfully submitted by XiPeng Xiao and posted to the IETF repository. Name: draft-xiao-v6ops-nd-deployment-guidelines Revision: 02 Title: Selectively Applying Host Isolation to Simplify IPv6 First-hop Deployment Document date: 2022-07-01 Group: Individual Submission Pages: 29 URL: https://www.ietf.org/archive/id/draft-xiao-v6ops-nd-deployment-guidelines-02.txt Status: https://datatracker.ietf.org/doc/draft-xiao-v6ops-nd-deployment-guidelines/ Htmlized: https://datatracker.ietf.org/doc/html/draft-xiao-v6ops-nd-deployment-guidelines Diff: https://www.ietf.org/rfcdiff?url2=draft-xiao-v6ops-nd-deployment-guidelines-02 Abstract: Neighbor Discovery (ND) is the key protocol of IPv6 first-hop. ND uses multicast extensively and trusts all hosts. In some scenarios like wireless networks, multicast can be inefficient. In other scenarios like public access networks, hosts may not be trustable. Consequently, ND issues may happen in various scenarios. The issues and solutions are documented in more than 30 RFCs. It is difficult to keep track of all these issues and solutions, and how the various solutions fit together. Therefore, deployment guidelines are needed. This document firstly summarizes the known ND issues and optimization solutions into a one-stop reference. Analyzing these solutions reveals an insight: isolating hosts is effective in solving ND issues. Four isolation methods are proposed and their applicability is discussed. Guidelines are then described for selecting a suitable isolation method based on the deployment scenario. The IETF Secretariat
- Re: [v6ops] New Version Notification for draft-xi… Xipengxiao
- Re: [v6ops] New Version Notification for draft-xi… Chongfeng XIE
- Re: [v6ops] New Version Notification for draft-xi… Xipengxiao