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

Giuseppe Fioccola <giuseppe.fioccola@huawei.com> Thu, 03 March 2022 09:35 UTC

Return-Path: <giuseppe.fioccola@huawei.com>
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 1C1733A1495; Thu, 3 Mar 2022 01:35:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id senmfXQXtVTJ; Thu, 3 Mar 2022 01:35:01 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A32B3A1494; Thu, 3 Mar 2022 01:35:01 -0800 (PST)
Received: from fraeml709-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4K8Qlq6b4zz67NYn; Thu, 3 Mar 2022 17:33:43 +0800 (CST)
Received: from fraeml714-chm.china.huawei.com (10.206.15.33) by fraeml709-chm.china.huawei.com (10.206.15.37) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.21; Thu, 3 Mar 2022 10:34:58 +0100
Received: from fraeml714-chm.china.huawei.com ([10.206.15.33]) by fraeml714-chm.china.huawei.com ([10.206.15.33]) with mapi id 15.01.2308.021; Thu, 3 Mar 2022 10:34:58 +0100
From: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
To: Chongfeng Xie <xiechf@chinatelecom.cn>, V6Ops-Chairs <v6ops-chairs@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] Fwd: New Version Notification for draft-xie-v6ops-reqirements-multi-domain-ipv6only-00.txt
Thread-Index: AQHYFYJe3grcoSGP50i8JJR0sja6Tqyti6JQ
Date: Thu, 03 Mar 2022 09:34:57 +0000
Message-ID: <7e370541c4b34aa588b600b885d261b2@huawei.com>
References: <164350909149.25132.16206084059279334692@ietfa.amsl.com> <94961E2C-DEFE-429B-BCEC-2228472747D7@chinatelecom.cn>
In-Reply-To: <94961E2C-DEFE-429B-BCEC-2228472747D7@chinatelecom.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.48.206.88]
Content-Type: multipart/alternative; boundary="_000_7e370541c4b34aa588b600b885d261b2huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Gv-4pYKDjDwcsp9ZzYWL6VmkGE8>
Subject: Re: [v6ops] Fwd: New Version Notification for draft-xie-v6ops-reqirements-multi-domain-ipv6only-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Mar 2022 09:35:04 -0000

Hi Chongfeng,
Thank you for proposing this draft.
I think that a document about the requirements of multi-domain IPv6-only network make a lot of sense, especially if we consider large-scale operators composed of multiple ASes.

I also read draft-ietf-bess-ipv6-only-pe-design and it aims to address a similar issue. It would be good to have cross-reference and collaboration between these documents.

Regarding Section 8 on Requirements, I think these can be further discussed in the WG based on the experience of network operators. I would suggest to distinguish between Basic Requirements, that a solution must satisfy, and Optional Requirements, that are instead desirable. The rationale is that some requirements may not be easily addressed in every operator networks but this would not prevent to have a multi-domain IPv6-only network.

Regards,

Giuseppe


From: v6ops <v6ops-bounces@ietf.org> On Behalf Of Chongfeng Xie
Sent: Sunday, January 30, 2022 3:37 AM
To: V6Ops-Chairs <v6ops-chairs@ietf.org>; v6ops@ietf.org
Subject: [v6ops] Fwd: New Version Notification for draft-xie-v6ops-reqirements-multi-domain-ipv6only-00.txt


Hi, all,
We have submitted a new draft as below. It mainly specifies requirements of multi-domain IPv6-only network from the perspective of operators.  Mutli-domain herein means a network is compose of multiple ASes and serves multiple scenarios, which is a common model for large-size operators.  This is only -00 draft and a start point, we are looking forward to receiving more comments and suggestions.   Thank you!

Best regards
Chongfeng






A new version of I-D, draft-xie-v6ops-reqirements-multi-domain-ipv6only-00.txt
has been successfully submitted by Chongfeng Xie and posted to the
IETF repository.

Name:                draft-xie-v6ops-reqirements-multi-domain-ipv6only
Revision:            00
Title:                   Requirements to multi-domain IPv6-only network
Document date:              2022-01-29
Group:                Individual Submission
Pages:                 13
URL:            https://www.ietf.org/archive/id/draft-xie-v6ops-reqirements-multi-domain-ipv6only-00.txt
Status:         https://datatracker.ietf.org/doc/draft-xie-v6ops-reqirements-multi-domain-ipv6only/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-xie-v6ops-reqirements-multi-domain-ipv6only


Abstract:
  Dual-stack requires IPv4 and IPv6 are deployed in parallel, as it
  costs more to run two technologies than one.  IPv6-only is considered
  to be the next stage of IPv6 development from dual-stack.  This
  document specifies requirements when deploying IPv6-only in multi-
  domain networks.




The IETF Secretariat