Re: [v6ops] Fw: New Version Notification for draft-xie-v6ops-evn6-00.txt

Paolo Volpato <paolo.volpato@huawei.com> Wed, 03 January 2024 15:25 UTC

Return-Path: <paolo.volpato@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 11D9CC14F693 for <v6ops@ietfa.amsl.com>; Wed, 3 Jan 2024 07:25:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 PgeSIgc_2ACR for <v6ops@ietfa.amsl.com>; Wed, 3 Jan 2024 07:25:24 -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 07EF5C339ADA for <v6ops@ietf.org>; Wed, 3 Jan 2024 07:03:24 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4T4tGn3gjrz6K6Hm for <v6ops@ietf.org>; Wed, 3 Jan 2024 23:01:53 +0800 (CST)
Received: from frapeml500004.china.huawei.com (unknown [7.182.85.22]) by mail.maildlp.com (Postfix) with ESMTPS id 601B914102E for <v6ops@ietf.org>; Wed, 3 Jan 2024 23:03:00 +0800 (CST)
Received: from frapeml500002.china.huawei.com (7.182.85.205) by frapeml500004.china.huawei.com (7.182.85.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Wed, 3 Jan 2024 16:02:55 +0100
Received: from frapeml500002.china.huawei.com ([7.182.85.205]) by frapeml500002.china.huawei.com ([7.182.85.205]) with mapi id 15.01.2507.035; Wed, 3 Jan 2024 16:02:55 +0100
From: Paolo Volpato <paolo.volpato@huawei.com>
To: Chongfeng Xie <chongfeng.xie@foxmail.com>
CC: list <v6ops@ietf.org>
Thread-Topic: [v6ops] Fw: New Version Notification for draft-xie-v6ops-evn6-00.txt
Thread-Index: AQIhkUWuQN0LwhZmxGa+1nGOyEzcjbA5hUSQ
Date: Wed, 03 Jan 2024 15:02:55 +0000
Message-ID: <a3bc39a9c32f4e0b85909a600a125a50@huawei.com>
References: <tencent_88D499E1C652545616EEE4A35DA300EE700A@qq.com>
In-Reply-To: <tencent_88D499E1C652545616EEE4A35DA300EE700A@qq.com>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.81.206.214]
Content-Type: multipart/alternative; boundary="_000_a3bc39a9c32f4e0b85909a600a125a50huaweicom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/biaHUv2B5CSIvJNs65gLXnZm9Lc>
Subject: Re: [v6ops] Fw: New Version Notification for draft-xie-v6ops-evn6-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: Wed, 03 Jan 2024 15:25:29 -0000

Hi Chongfeng,

After reading your draft, I’d like to share a few comments.

In the introduction, you could highlight the relationship between your work and EPVN (RFC 7432).
It is true that EVPN assumes an MPLS data plane, and in your case the data plane is pure IPv6. But, apart from the different data planes, my impression is that your draft could be seen as a different flavor to carry EVPN, as the control plane should be pretty much the same.

You could also add a mention to SRv6 as an alternative option to carry EVN. In particular with SRv6 BE (with no SRH) the difference with a pure IPv6 underlay should be minimal.

In figure 2 it could be useful to show the length of the fields (e.g. 48 bit for the MAC address, 32 for the VEI, etc.). This because I am not sure how long the field “Length of Pref6” should be. Is it 8 bits? I guess that the field “Pref6” should be 64 bits.

In section 3 it is clearly said that the mechanisms to propagate the MAC address across the EVN are out of scope (e.g. they may be based on BGP). I just wonder if in section 4.2 you can just add a few words on how H2 determines the MAC address of H1 to communicate the first time (e.g. through ARP/NDP). Reading section 4.2 it seems that host H2 already knows everything of H1.

In the normative reference, RFC8200 could be added.

Best regards
Paolo

From: v6ops <v6ops-bounces@ietf.org> On Behalf Of Chongfeng Xie
Sent: Thursday, November 9, 2023 6:32 AM
To: list <v6ops@ietf.org>
Subject: [v6ops] Fw: New Version Notification for draft-xie-v6ops-evn6-00.txt


Folks,

We have just submitted a new draft of EVN6, which is about the mapping of ethernet virtual network to IPv6 Underlay for transmission. Myabe you have noticed that it has been discussed in 6man WG. We are looking forward to receiving more comments and suggestions from you.

Best regards
Chongfeng

From: 【外部账号】<mailto:internet-drafts@ietf.org>
Date: 2023-11-09 13:19
To: Chongfeng Xie<mailto:xiechf@chinatelecom.cn>; Congxiao Bao<mailto:congxiao@cernet.edu.cn>; Mark Smith<mailto:markzzzsmith@gmail.com>; Xing Li<mailto:xing@cernet.edu.cn>
Subject: New Version Notification for draft-xie-v6ops-evn6-00.txt
A new version of Internet-Draft draft-xie-v6ops-evn6-00.txt has been
successfully submitted by Chongfeng Xie and posted to the
IETF repository.

Name:     draft-xie-v6ops-evn6
Revision: 00
Title:    EVN6: A Framework of Mapping of Ethernet Virtual Network to IPv6 Underlay
Date:     2023-11-09
Group:    Individual Submission
Pages:    14
URL:      https://www.ietf.org/archive/id/draft-xie-v6ops-evn6-00.txt
Status:   https://datatracker.ietf.org/doc/draft-xie-v6ops-evn6/
HTMLized: https://datatracker.ietf.org/doc/html/draft-xie-v6ops-evn6


Abstract:

   This document describes the mechanism of mapping of Ethernet Virtual
   Network to IPv6 Underlay for transmission.  Unlike the existing
   methods, this approach places the Ethernet frames to be transmitted
   directly in the payload of IPv6 packets, i.e., L2 over IPv6, and uses
   stateless mapping to generate IPv6 source and destination addresses
   from the host's MAC addresses, Ethernet Virtual Network identifier
   and site prefixes.  The IPv6 packets generated in this way carry
   Ethernet frames and are routed to the destination site across public
   IPv6 network.



The IETF Secretariat