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

Chongfeng Xie <chongfeng.xie@foxmail.com> Mon, 29 July 2024 04:31 UTC

Return-Path: <chongfeng.xie@foxmail.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE418C14F6BB; Sun, 28 Jul 2024 21:31:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.171
X-Spam-Level:
X-Spam-Status: No, score=-4.171 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HELO_DYNAMIC_IPADDR=1.951, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_DYNAMIC=0.982, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=foxmail.com
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 StISDRjownl6; Sun, 28 Jul 2024 21:31:05 -0700 (PDT)
Received: from out203-205-221-210.mail.qq.com (out203-205-221-210.mail.qq.com [203.205.221.210]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BA48C14F6A1; Sun, 28 Jul 2024 21:31:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foxmail.com; s=s201512; t=1722227460; bh=yY8q7RTwgkacaGFdI8UDJFdphHjHb4ua+fkduBclxPs=; h=Date:From:To:Cc:Subject:References; b=EFo8CV1adfuadxTF/Lc4L5nxnGU7sBq5W2ZCjq1vTNkETkpYGeDmfJOfiw/mdTg0B HbIIPipWUnTb4vtmYAE3M5T5uKvSVolqKuJyupRk5d0NcVA2JAfKDSnQI9LlnE3bzg gjlGvmI6UhEAbZ0bHZlSKnLv6HsGyLYVj7ntebq4=
Received: from LAPTOP-BOBOCIFS ([219.142.69.77]) by newxmesmtplogicsvrszc19-0.qq.com (NewEsmtp) with SMTP id 635046B5; Mon, 29 Jul 2024 12:24:53 +0800
X-QQ-mid: xmsmtpt1722227093t3gvn4f34
Message-ID: <tencent_76738C991DC68257EA1652E55B5EAB029A0A@qq.com>
X-QQ-XMAILINFO: MxdSvGmuhzbKd0KHqHkmT13/X261G4wupZ2MdrA7zxGyX0NzEg9HtZcLSEv27S ls9wkjQdX8Sj39Ybwfv0hgCHRKvTYTetMHEFkULPu9yWkYGxxyDDLJDhf68PrWSEIJqMx/cBsQjr UPji6GXD7G/fAIIWX/he05Yhi7roLf9iMntPv/0P22W9BWLWy8LtzTt5rEeXVfX+7/EGfCLECz7F vcIyxB+fS5KK0qH0oUV8TB/PpvVkNvleRXvdTUzXVIPajGu8YZUjA+O2CHrD5ODZZVWCwkwpiERQ TeW3qc2M8QjGrZ0ns4Kj66+ghkGs0MNzAgfaaDh6VXX5atu1KLyo0yMLzs5qE2rLpfGDPGcjsyY4 zpcJEbvO/Tj6eZQ7VdXPkTxZoypm/pjKG5FSydPfl1RetoQTNvnxgPeZqQ0A0rmQGmim6mGEXRwm aOBGxD6yBSGKwnzqKYFPvjDDgQ0RklW7br2dOskC/Tl7nvwGmn3CXWQ7Mt4kirChnPMX3osexf9x uPexkrRjlWnbQvKZMcRPVZnB3vCVeSmYQc0PPWtWBhDPq2vbSZxLxugromwa8fR8LUxGQpZgMv8F ntjWIaGbz7ysW0HnTZqMZFkjl87ytofmGH7GNcmpOOSJM3FAds44JnGA1NWBoOMWxGCU2xiMnOMZ uXObafXBVhvBUZ8xWy8IkmRk/7Da1OUQvroI+vzAjvGUGtWGKZ1hwtJIHqDpzw3mPqrcUuX4jzwy m99sI/bAeWeCoE7MShF6/sVRx6wFZTgrLJoWMZjSten8iZ9UcbNBblL/htG0zijUJ4Wzhz5wGbqV KtiB3/3toPd3WEa+Nvav6HGWfBlTBnd7iU4gqHSOKwuYCRoaRw8F5+o0uw6s+czFRu2pAYl56gid EsMRDuQ93HiJhcUt2oDHHPZ/E9vYrwJPhPgIhkmraNwwHPfDYMbKlrlxiul9cJHLkZIStXSIPxYL hE3Vy5GImYevzGLdHMxD8ix2AuS7QiYf0X4zqeKuddYzOAznejoxw9XzkaYPhfXErWLEu9jgHqIi F+0qZtjNyHLL28pF0cCf0ckA3ObyZpJ+Mvf9T8tP/OfXS9AIHYFD9aoHLX3Fc=
X-QQ-XMRINFO: NS+P29fieYNw95Bth2bWPxk=
Date: Mon, 29 Jul 2024 12:24:53 +0800
From: Chongfeng Xie <chongfeng.xie@foxmail.com>
To: Gyan Mishra <hayabusagsm@gmail.com>
References: <tencent_4609C7A8195E2C4AA5716171BECCF5162006@qq.com>, <CABNhwV2BN3jxhpwHd2oAf=YoFP=xV3d-5JLHLoS1QO89g_mdfA@mail.gmail.com>
X-Priority: 3
X-GUID: B3F207BF-B52F-437E-AC28-B892F58555B4
X-Has-Attach: no
X-Mailer: Foxmail 7.2.25.259[cn]
Mime-Version: 1.0
X-OQ-MSGID: <2024072912245259322531@foxmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart462607626853_=----"
Message-ID-Hash: GVMBCWQ2CEQ22IZMQC27JIDSYY6DXMEG
X-Message-ID-Hash: GVMBCWQ2CEQ22IZMQC27JIDSYY6DXMEG
X-MailFrom: chongfeng.xie@foxmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-bess.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: bess <bess@ietf.org>, nvo3 <nvo3@ietf.org>, xing <xing@cernet.edu.cn>, sunjb <sunjb@chinatelecom.cn>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [bess] Re: Fw: New Version Notification for draft-xie-bess-evpn-extension-evn6-00.txt
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/EddUOY71ItqSi2CDoL8kTBnY0kw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Owner: <mailto:bess-owner@ietf.org>
List-Post: <mailto:bess@ietf.org>
List-Subscribe: <mailto:bess-join@ietf.org>
List-Unsubscribe: <mailto:bess-leave@ietf.org>

Hi Gyan,

Thank you for your comments and questions. I tried my best to answer your questions, please see my feedback inline[Chongfeng]:
 
From: Gyan Mishra
Date: 2024-07-27 11:59
To: Chongfeng Xie
CC: bess; nvo3; xing; sunjb; evyncke
Subject: Re: [bess] Fw: New Version Notification for draft-xie-bess-evpn-extension-evn6-00.txt

Hi Chongfeng

This is a very intriguing solution.

The use case for this solution is EVPN L2 stretch  over the internet or disparate IP networks that could be in the same OAD admin domain and have IP connectivity between disparate PEs but do not have the availability to natively extend the EVPN control plane but are able to stitch the data plane.

I think if you are able to extend EVPN control plane natively then you would do regular EVPN but if you cannot then you are stuck and this solution fills that gap.

I guess there could be case of a Telco cloud providet with hybrid cloud on prem and off prem DC CSP cloud provider through a CXP POP and now this could be method of providing L2 stretch of data plane via EVN6 control plane.   

[Chongfeng]: Yes, this case is one that EVN6 can be used.

With the procedure once the tunnel is established at the beginning once the dynamic mapping happens would you not need DF election ?  
[Chongfeng]:  Currently, the approach in this draft de not need DF election.

Since this is all new procedures from RFC 7432 and RFC 8365 base RFCs would you have to write the entire new EVPN control plane procedures.  For example how would RFC 9135 inter subnet forwarding work?

[Chongfeng]: The draft just defines the extensions to EVPN control plane for EVN6, including two new route types and related procedures. Later on, we can add a section related to RFC9135 if it is necessary.

Very nice indeed!
[Chongfeng]: Thanks.

Kind Regards 


Gyan


Thank you.

Best regards
Chongfeng

On Fri, Jul 26, 2024 at 12:52 AM Chongfeng Xie <chongfeng.xie@foxmail.com> wrote:

Hello everyone,
We have submitted a new draft on "EVPN Route Types and Procedures for EVN6" to BESS WG,  it proposes extensions to EVPN for EVN6. EVN6 is a Layer-2 network model built on top of the IPv6 underlay to provide connectivity between dispersed customer sites, the draft of EVN6 has been presented in Intarea and v6ops WGs.  We are looking forward to your review and comments to this new draft. 
Thanks.

Best regards
Chongfeng  

 
From: 【外部账号】
Date: 2024-07-26 12:25
To: Chongfeng Xie; Guoliang Han; Jibin Sun; Xing Li
Subject: New Version Notification for draft-xie-bess-evpn-extension-evn6-00.txt
A new version of Internet-Draft draft-xie-bess-evpn-extension-evn6-00.txt has
been successfully submitted by Chongfeng Xie and posted to the
IETF repository.
 
Name:     draft-xie-bess-evpn-extension-evn6
Revision: 00
Title:    EVPN Route Types and Procedures for EVN6
Date:     2024-07-25
Group:    Individual Submission
Pages:    13
URL:      https://www.ietf.org/archive/id/draft-xie-bess-evpn-extension-evn6-00.txt
Status:   https://datatracker.ietf.org/doc/draft-xie-bess-evpn-extension-evn6/
HTMLized: https://datatracker.ietf.org/doc/html/draft-xie-bess-evpn-extension-evn6
 
 
Abstract:
 
   EVN6 is a mechanism designed to carry Ethernet virtual networks,
   providing Ethernet connectivity to customer sites dispersed on public
   IPv6 networks.  At the data layer, EVN6 directly places the Ethernet
   frames in the payload of IPv6 packet, and dynamically generates the
   IPv6 addresses of the IPv6 header using host MAC addresses and other
   information, then sends them into IPv6 network for transmission.
   This document proposes extensions to EVPN for EVN6, including two new
   route types and related procedures.
 
 
 
The IETF Secretariat
 
 
 
_______________________________________________
BESS mailing list -- bess@ietf.org
To unsubscribe send an email to bess-leave@ietf.org