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

Gyan Mishra <hayabusagsm@gmail.com> Sat, 27 July 2024 03:59 UTC

Return-Path: <hayabusagsm@gmail.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 19E5DC1C6340; Fri, 26 Jul 2024 20:59:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.104
X-Spam-Level:
X-Spam-Status: No, score=-7.104 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 s1dmXdPwxzyV; Fri, 26 Jul 2024 20:59:18 -0700 (PDT)
Received: from mail-oi1-x235.google.com (mail-oi1-x235.google.com [IPv6:2607:f8b0:4864:20::235]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39D2DC1840CD; Fri, 26 Jul 2024 20:59:18 -0700 (PDT)
Received: by mail-oi1-x235.google.com with SMTP id 5614622812f47-3db1270da60so1146044b6e.2; Fri, 26 Jul 2024 20:59:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1722052757; x=1722657557; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=uUHt2qdpkse/YDCdT6fXbn9oBY/EU3cPGBFeoFUKqBA=; b=bKoTmXlYcilzKOLRP5+myA+EEfdXyNHo631fXSlRa/nHUpE63PTf8dKknlhP5TnxfW nY3kCzzxBaZgDNMsziKFLE2GiNdcdj+xkUJJb5Fxj4/D1ZPRhYUX6UOw256pwLk+SW+n 5/nrhLSjuXn88Pq/TVldc/hc/gNJ7PBCXuaGfBBN/TbKg2I76S3TVobDLl7pE/QcjO/O 2Spsf4FYvUpGb6BEWoWAABIJEBgL1V5J+q3jVXRkEQkj5ZZO/wYmVV7l4oLLvbKynLzp qmbdAX6zTlmxT+YnCpkg3FhIopNshH9oS0HucUN/EDhGDPpbnLRLhBPs0Gbon7uU+VO/ wJzA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722052757; x=1722657557; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=uUHt2qdpkse/YDCdT6fXbn9oBY/EU3cPGBFeoFUKqBA=; b=tfL4CHy+P1F7+lIN4rVpufzPVDCKEfvDuYSX9odJLaY257VIWZ12SLTurkN3cjRDGm P17VQCBPyMtg1Mmdcg5pNcWt3UllCXdeJoK47MLTQq1xJzDt0LOG+kRZ14BFOKD7s5u2 cgnlja04Ggdbdb5qwplnhNaCZFd3EpsUqd/TPHIRQE/IIi1fqd/ava9VCyh7IcyAvD7/ lzag5lR8Ldtda8fpjcVZYilmolro8e9/fd9La/hmRT2JWCRJ0qEuIw6gDiyBqXjpjd60 kJXKcfWnEX79lUsLdUipTz/1q3CPuUFZ+8Jjrc2u0ye26tfQ1yt+PCIXvIBk6yvkbZou 5k+w==
X-Forwarded-Encrypted: i=1; AJvYcCUIiq7nSaW1hNKQommmmljECZseR0RqPWjs+5FKNt59yaNS4vEtu/Vxe1Jz8FrW9EgXrajfQYgBJz1kkW1z
X-Gm-Message-State: AOJu0YzTRZEdZRubZGdGcT010zKbh3Lsj3hJNO8UAZ97BM8zpNJHRMlN j9I2PmYE8W+T+yBiujzHwsaWt5P5TTyfQfGCsq6n1ciDKp7N5UuQx4lW2yDHb7ZYo7iamDMy+7M Jrf5NrXbKLYcg+kcGJsL97ezyRC8=
X-Google-Smtp-Source: AGHT+IEsOryH9k+PbZ/d6YA/IqXj2A3i0I0+IiGuCgBY5n4tX/HICnFem75OaOmKCYsfMCPdGEibf6SzvsfwXBjtaKU=
X-Received: by 2002:a05:6830:3695:b0:708:d860:e51b with SMTP id 46e09a7af769-70940c1097fmr1963220a34.15.1722052757127; Fri, 26 Jul 2024 20:59:17 -0700 (PDT)
MIME-Version: 1.0
References: <tencent_4609C7A8195E2C4AA5716171BECCF5162006@qq.com>
In-Reply-To: <tencent_4609C7A8195E2C4AA5716171BECCF5162006@qq.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Fri, 26 Jul 2024 23:59:06 -0400
Message-ID: <CABNhwV2BN3jxhpwHd2oAf=YoFP=xV3d-5JLHLoS1QO89g_mdfA@mail.gmail.com>
To: Chongfeng Xie <chongfeng.xie@foxmail.com>
Content-Type: multipart/alternative; boundary="000000000000df8a7c061e32a61b"
Message-ID-Hash: RS5YIGYGJEU7AXV7XCH55RHT5OTATY4J
X-Message-ID-Hash: RS5YIGYGJEU7AXV7XCH55RHT5OTATY4J
X-MailFrom: hayabusagsm@gmail.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>, evyncke <evyncke@cisco.com>
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/3EG4vb5S6FBI5v4mlty9TNDE7wo>
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 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.

With the procedure once the tunnel is established at the beginning once the
dynamic mapping happens would you 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?

Very nice indeed!

Kind Regards

Gyan


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:* 【外部账号】 <internet-drafts@ietf.org>
> *Date:* 2024-07-26 12:25
> *To:* Chongfeng Xie <xiechf@chinatelecom.cn>; Guoliang Han
> <guoliang.han@indirectionnet.com>; Jibin Sun <sunjb@chinatelecom.cn>; Xing
> Li <xing@cernet.edu.cn>
> *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
>