Re: [v6ops] I-D Action: draft-ietf-v6ops-framework-md-ipv6only-underlay-01.txt

Chongfeng Xie <xiechf@chinatelecom.cn> Fri, 03 February 2023 23:54 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 DD8AEC1575B9; Fri, 3 Feb 2023 15:54:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.896
X-Spam-Level:
X-Spam-Status: No, score=-6.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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=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 LruY_lca4Uij; Fri, 3 Feb 2023 15:54:08 -0800 (PST)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.223]) by ietfa.amsl.com (Postfix) with ESMTP id 3DF44C151536; Fri, 3 Feb 2023 15:54:06 -0800 (PST)
HMM_SOURCE_IP: 172.18.0.48:43076.1951074795
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-221.217.26.71 (unknown [172.18.0.48]) by chinatelecom.cn (HERMES) with SMTP id 631662800D5; Sat, 4 Feb 2023 07:54:03 +0800 (CST)
X-189-SAVE-TO-SEND: 66040161@chinatelecom.cn
Received: from ([221.217.26.71]) by app0024 with ESMTP id aab9a4177ca242268ec974133fd69b3d for v6ops@ietf.org; Sat, 04 Feb 2023 07:54:05 CST
X-Transaction-ID: aab9a4177ca242268ec974133fd69b3d
X-Real-From: xiechf@chinatelecom.cn
X-Receive-IP: 221.217.26.71
X-MEDUSA-Status: 0
Sender: xiechf@chinatelecom.cn
Date: Sat, 04 Feb 2023 07:54:03 +0800
From: Chongfeng Xie <xiechf@chinatelecom.cn>
To: list <v6ops@ietf.org>, V6Ops-Chairs <v6ops-chairs@ietf.org>
References: <167546808126.40435.17081128425153414655@ietfa.amsl.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.24.96[cn]
Mime-Version: 1.0
Message-ID: <202302040754029209352@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart773085772546_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/tHylpx7tEQ5guf13dy-kDLq4AV8>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-framework-md-ipv6only-underlay-01.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: Fri, 03 Feb 2023 23:54:09 -0000

Hi folks,
We have submitted a new version of this draft. During the call for adoption process, many comments have been received, we really appreciate that, most of them has been accepted and revisions have been made as below, 

1)Nits fixed
- 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/transporation/transport
- s/Addtess/Address
- s/Specificially/Specifically
- s/User-ralated/ User-related

2) Two terms are optimized as below,
RM-->RP (Rule Processing Layer)
RP--> RT (Rule Transport Layer)

3)In order to be shorter, the header title has been changed to “Multi-domain IPv6-only Underlay”.

4) The following terms has been expanded on first use,
    - eBGP
    - XLAT
    - CLAT
    - PLAT
    - AFBR
     -ASBR

5) The following terms have been modified,
Cloud-data center-->Data center
VM-->instance
IPv6 transfer capability--> IPv6 forwarding capability

5) Integration with a transition mechanism at the UE/CPE has been put in a separate section, i.e., section 7. 

6)The term “IPv4-IPv6” in the following statement has been changed to “IPv6-IPv4”.

 “From UE to egress, the packets of IPv4 service can be translated (or encapsulated) into IPv6 packets within the UE or CPE, and there should be no IPv4-IPv6 conversion before they reach the egress of the network.”

7) The following sentence is added in section 5.
“At the ingress/egress an IPv4 forwarding function is needed to forward to the right egress network node (via encapsulation / translation) or right interface towards an external network.”

8) The format of IPv4-Embedded IPv6 address in section 6.1 has been corrected, an example of the new format is 2001:db8:100::192.0.2.33.

9) In section 2, “underlay” is added to the definition of IPv6-only network.

Thank you for your support during the past, we are looking forward to receiving more comments and suggestions in the way ahead.

Best regards
Chongfeng 
on behalf of all the co-authors



xiechf@chinatelecom.cn
 
From: internet-drafts
Date: 2023-02-04 07:48
To: i-d-announce@ietf.org
CC: v6ops
Subject: [v6ops] I-D Action: draft-ietf-v6ops-framework-md-ipv6only-underlay-01.txt
 
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IPv6 Operations WG of the IETF.
 
        Title           : Framework of Multi-domain IPv6-only Underlay Networks and IPv4-as-a-Service
        Authors         : Chongfeng Xie
                          Chenhao Ma
                          Xing Li
                          Gyan Mishra
                          Mohamed Boucadair
                          Thomas Graf
  Filename        : draft-ietf-v6ops-framework-md-ipv6only-underlay-01.txt
  Pages           : 23
  Date            : 2023-02-03
 
Abstract:
   For the IPv6 transition, dual-stack deployments require both IPv4 and
   IPv6 forwarding capabilities to be deployed in parallel.  IPv6-only
   is considered as the ultimate stage where only IPv6 bearer
   capabilities are used while ensuring global reachability for both
   IPv6 and IPv4 service(usually known as IPv4aaS).  This document
   proposes a general framework for deploying IPv6-only in multi-domain
   underlay networks.  It discusses the requirements of service traffic,
   major components and interfaces, IPv6 mapping prefix allocation,
   typical procedures for service delivery.  The document also discusses
   related security considerations.
 
 
The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-v6ops-framework-md-ipv6only-underlay/
 
There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-framework-md-ipv6only-underlay-01
 
A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-v6ops-framework-md-ipv6only-underlay-01
 
 
Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
 
 
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops