IETF Logo Mail Archive

Re: [v6ops] WG Call For Adoption: draft-xie-v6ops-framework-md-ipv6only-underlay-05

Chongfeng Xie <xiechf@chinatelecom.cn> Thu, 08 December 2022 02:13 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 E87C8C151701 for <v6ops@ietfa.amsl.com>; Wed, 7 Dec 2022 18:13:07 -0800 (PST)
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, URIBL_BLOCKED=0.001, 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 JP-dXwS2Y9sJ for <v6ops@ietfa.amsl.com>; Wed, 7 Dec 2022 18:13:03 -0800 (PST)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.220]) by ietfa.amsl.com (Postfix) with ESMTP id 94491C1516E2 for <v6ops@ietf.org>; Wed, 7 Dec 2022 18:13:02 -0800 (PST)
HMM_SOURCE_IP: 172.18.0.48:42336.1259689306
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-219.142.69.78 (unknown [172.18.0.48]) by chinatelecom.cn (HERMES) with SMTP id 743382800AE; Thu, 8 Dec 2022 10:12:58 +0800 (CST)
X-189-SAVE-TO-SEND: 66040161@chinatelecom.cn
Received: from ([219.142.69.78]) by app0024 with ESMTP id ac4eb1a9d74f4f74b88a6accd68df881 for dhruv.ietf@gmail.com; Thu, 08 Dec 2022 10:13:00 CST
X-Transaction-ID: ac4eb1a9d74f4f74b88a6accd68df881
X-Real-From: xiechf@chinatelecom.cn
X-Receive-IP: 219.142.69.78
X-MEDUSA-Status: 0
Sender: xiechf@chinatelecom.cn
Date: Thu, 08 Dec 2022 10:12:58 +0800
From: Chongfeng Xie <xiechf@chinatelecom.cn>
To: Dhruv Dhody <dhruv.ietf@gmail.com>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>
Cc: list <v6ops@ietf.org>
References: <BL0PR05MB5316CD2222C6E839A9E43F26AE099@BL0PR05MB5316.namprd05.prod.outlook.com>, <CAB75xn5EgqX0KOP_ZDppBaOGAJR6r2eZ23u2Assi5TDq_zYZHw@mail.gmail.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.24.96[cn]
Mime-Version: 1.0
Message-ID: <202212081012581320187@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart117555072451_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/qUK13fBrYQQwn7GmLm0RBt4Ni8U>
Subject: Re: [v6ops] WG Call For Adoption: draft-xie-v6ops-framework-md-ipv6only-underlay-05
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: Thu, 08 Dec 2022 02:13:08 -0000

Hi Dhruv,
Thank you for your support and comments, we will revise section 6.2 based on your comments, and the nits will be amended as well.

Best regards
Chongfeng 



xiechf@chinatelecom.cn
 
From: Dhruv Dhody
Date: 2022-12-08 02:14
To: Ron Bonica
CC: v6ops@ietf.org
Subject: Re: [v6ops] WG Call For Adoption: draft-xie-v6ops-framework-md-ipv6only-underlay-05
Hi Ron, 

I support adoption! Some comments for authors to work on - 

## Minor

- Section 6.2, Figure 3 needs better description in text and consider adding a legend for RM, MD, RP, DF. The interface Ix also gets a bit confusing. If some of them are internal interfaces, do they need to be listed in a standard? I am worried about this section overall. Perhaps better to describe this as an example in the appendix?

## Nits

- Choose a smaller abbreviation for the header - "Multi-domain IPv6-only Underlay Framewor"

- Avoid using the term "IPv6 transfer capabilities", stick to "forwarding". It is used once in abstract! 

- Consider breaking this sentence up
````
   This document specifies
   requirements and proposes a framework for deploying IPv6-only as the
   underlay in multi-domain networks, discusses the requirements of
   service traffic, major components and interfaces, IPv6 mapping prefix
   allocation, typical procedures for service delivery. 
````

- s/considerations with security/security considerations/
- s/As per 2022/As of 2022/
- s/when IPv6 usage is being the dominant/when IPv6 usage is dominant/
- s/should not succeed two/should not exceed two/
- s/addtess/address/
- Expand on first use
    - eBGP
    - XLAT
    - CLAT
    - PLAT

Thanks! 
Dhruv

On Sat, Nov 19, 2022 at 3:24 AM Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org> wrote:
Folks,
 
This message initiates a WG call for adoption for draft-xie-v6ops-framework-md-ipv6only-underlay-05. To accommodate the American holiday, the call for adoption will end on December 9, 2022.
 
                                                       Ron
 

Juniper Business Use Only
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email