IETF Logo Mail Archive

Re: [v6ops] Fw: New Version Notification for draft-xie-v6ops-framework-multi-domain-ipv6only-00.txt

Chongfeng XIE <xiechf@chinatelecom.cn> Thu, 23 June 2022 01:05 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 E4BCEC14CF0D for <v6ops@ietfa.amsl.com>; Wed, 22 Jun 2022 18:05:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 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, T_SCC_BODY_TEXT_LINE=-0.01] 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 kA7668s8YseN for <v6ops@ietfa.amsl.com>; Wed, 22 Jun 2022 18:05:22 -0700 (PDT)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.219]) by ietfa.amsl.com (Postfix) with ESMTP id BC71CC14CF00 for <v6ops@ietf.org>; Wed, 22 Jun 2022 18:05:21 -0700 (PDT)
HMM_SOURCE_IP: 172.18.0.48:48386.267057431
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 6CD2C28016A; Thu, 23 Jun 2022 09:05:12 +0800 (CST)
X-189-SAVE-TO-SEND: 66040161@chinatelecom.cn
Received: from ([172.18.0.48]) by app0024 with ESMTP id f41df987d9364c52a87f89658acb0d4c for brian.e.carpenter@gmail.com; Thu, 23 Jun 2022 09:05:13 CST
X-Transaction-ID: f41df987d9364c52a87f89658acb0d4c
X-Real-From: xiechf@chinatelecom.cn
X-Receive-IP: 172.18.0.48
X-MEDUSA-Status: 0
Sender: xiechf@chinatelecom.cn
Date: Thu, 23 Jun 2022 09:05:12 +0800
From: Chongfeng XIE <xiechf@chinatelecom.cn>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: list <v6ops@ietf.org>
References: <202206211427054870437@chinatelecom.cn>, <CA+nkc8C89AmmrNS3ZkP=VVFt1fQ_8mHcz1YOMZi090V5Ofnbmg@mail.gmail.com>, <2a300ad3-2da3-a911-4035-92f9e2481b80@gmail.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.23.121[cn]
Mime-Version: 1.0
Message-ID: <2022062309051226771415@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart030017578683_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/IuYtPGlUU1YfYZ82RYjij3QIFpU>
Subject: Re: [v6ops] Fw: New Version Notification for draft-xie-v6ops-framework-multi-domain-ipv6only-00.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: Thu, 23 Jun 2022 01:05:23 -0000

Hi，Brian,
Thank you for your comments and suggestion. I agree with you, this draft is mainly about underlay with IPv6 instead of dual-stack, meanwhile, the service can be dual-stack.  Based on your judicious suggestion, we  plan to limit the scope and change the name to,   

           "Framework of Multi-domain IPv6-only Underlay Network and IPv4aaS" 
       
Do you think this is ok?

Best regards
Chongfeng



xiechf@chinatelecom.cn
 
From: Brian E Carpenter
Date: 2022-06-22 06:14
To: Chongfeng XIE
CC: IPv6 Operations
Subject: Re: [v6ops] Fw: New Version Notification for draft-xie-v6ops-framework-multi-domain-ipv6only-00.txt
Hi,
 
I'd like to repeat my plea to *not* use the phrase "IPv6-only" in this way. It is a very misleading phrase because you do not propose to provide an IPv6-only service to users, but a dual stack service.
 
What you describe is an IPv6 underlay or an IPv6 transport network. It concerns internal choices by operators, not what the user sees. The title, file name, and Abstract of the draft should, in my opinion, carefully avoid the phrase "IPv6-only" to prevent irrational reactions. The objective is to provide dual-stack *service* without needing dual-stack infrastructure.
 
Something like:
 
 
               Framework of Multi-domain IPv6 Underlay Network
            draft-xie-v6ops-framework-multi-domain-ipv6-underlay-00
 
Abstract
 
    Dual-stack deployments originally required both IPv4 and IPv6
    transfer capabilities to be deployed in parallel.  For operators,
    supporting only IPv6 infrastructure, with global IPv4 provided
    as a an overlay service, is a preferable ultimate stage.  This
    document specifies requirements and proposes a general framework
    when deploying IPv6 as the underlay in a multi-domain network.
 
 
Regards
    Brian Carpenter

v2.23.0 | Report a Bug | By Email