IETF Logo Mail Archive

Re: [bess] A new draft for MVPN in IPv6-only network.

duanfanghong <duanfanghong@huawei.com> Mon, 30 May 2022 06:32 UTC

Return-Path: <duanfanghong@huawei.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 39479C14F738 for <bess@ietfa.amsl.com>; Sun, 29 May 2022 23:32:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 49XF3yo6g50e for <bess@ietfa.amsl.com>; Sun, 29 May 2022 23:32:03 -0700 (PDT)
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 7FDB8C14F746 for <bess@ietf.org>; Sun, 29 May 2022 23:32:03 -0700 (PDT)
Received: from fraeml737-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4LBQSY2G9fz67xX4 for <bess@ietf.org>; Mon, 30 May 2022 14:27:41 +0800 (CST)
Received: from kwepemi100002.china.huawei.com (7.221.188.188) by fraeml737-chm.china.huawei.com (10.206.15.218) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Mon, 30 May 2022 08:31:59 +0200
Received: from dggpemm100009.china.huawei.com (7.185.36.113) by kwepemi100002.china.huawei.com (7.221.188.188) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Mon, 30 May 2022 14:31:58 +0800
Received: from dggpemm100009.china.huawei.com ([7.185.36.113]) by dggpemm100009.china.huawei.com ([7.185.36.113]) with mapi id 15.01.2375.024; Mon, 30 May 2022 14:31:57 +0800
From: duanfanghong <duanfanghong@huawei.com>
To: "Jeffrey (Zhaohui) Zhang" <zzhang=40juniper.net@dmarc.ietf.org>, "bess@ietf.org" <bess@ietf.org>
CC: "Xiejingrong (Jingrong)" <xiejingrong@huawei.com>, "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>, "Wangheng (MCAST, P&S)" <wangheng21@huawei.com>
Thread-Topic: [bess] A new draft for MVPN in IPv6-only network.
Thread-Index: AdhvaLnt9w7l5WvrSm+DKhZircOGtABopP7QAK/mKTA=
Date: Mon, 30 May 2022 06:31:57 +0000
Message-ID: <eaf255a23f59425ab4a33e293ef070c9@huawei.com>
References: <16b002685b9849f291dc55fd1e340fcf@huawei.com> <BL0PR05MB5652BFECA4AFBA71698F2178D4D99@BL0PR05MB5652.namprd05.prod.outlook.com>
In-Reply-To: <BL0PR05MB5652BFECA4AFBA71698F2178D4D99@BL0PR05MB5652.namprd05.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.128.119]
Content-Type: multipart/alternative; boundary="_000_eaf255a23f59425ab4a33e293ef070c9huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/hHWpKJ8yDu-o7JhxR6-vYwa_F00>
Subject: Re: [bess] A new draft for MVPN in IPv6-only network.
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 May 2022 06:32:06 -0000

Hi Jeffrey,

I have read your draft carefully, as you mentioned in this draft, it is a less optimal solution for PE to PE C-Multicast signaling.

In the draft I just published, we describe IPv6-only infrastructure and dual-stack infrastructure issues and solutions for regular option B scenario in RFC 6514. So, both the scenario and solution are different from the one you published.

Thanks.
Fanghong.

From: Jeffrey (Zhaohui) Zhang [mailto:zzhang=40juniper.net@dmarc.ietf.org]
Sent: Thursday, May 26, 2022 10:23 PM
To: duanfanghong <duanfanghong@huawei.com>; bess@ietf.org
Cc: Xiejingrong (Jingrong) <xiejingrong@huawei.com>; Gengxuesong (Geng Xuesong) <gengxuesong@huawei.com>; Wangheng (MCAST, P&S) <wangheng21@huawei.com>
Subject: RE: [bess] A new draft for MVPN in IPv6-only network.

Hi Fanghong,

It seems that https://datatracker.ietf.org/doc/html/draft-zzhang-bess-mvpn-evpn-cmcast-enhancements-01#section-1.3 talked about the problems and a more general solution.

That draft also has other enhancements considerations. It has stalled but looks like we should get it going.

Thanks.
Jeffrey



Juniper Business Use Only
From: BESS <bess-bounces@ietf.org<mailto:bess-bounces@ietf.org>> On Behalf Of duanfanghong
Sent: Tuesday, May 24, 2022 8:24 AM
To: bess@ietf.org<mailto:bess@ietf.org>
Cc: Xiejingrong (Jingrong) <xiejingrong@huawei.com<mailto:xiejingrong@huawei.com>>; Gengxuesong (Geng Xuesong) <gengxuesong@huawei.com<mailto:gengxuesong@huawei.com>>; Wangheng (MCAST, P&S) <wangheng21@huawei.com<mailto:wangheng21@huawei.com>>
Subject: [bess] A new draft for MVPN in IPv6-only network.

[External Email. Be cautious of content]

Hi All,

  MVPN(RFC 6513/RFC 6514/RFC 6515) faces some problems in IPv6-only networks, especially in the non-segmented inter-AS scenario and IPv4 to IPv6 migration scenario.
  We have published a new draft https://datatracker.ietf.org/doc/draft-duan-bess-mvpn-ipv6-infras/, aiming to solve these problems.

  Please provide your valuable comments and help evolving it further.

  Thanks.

Regards,
Fanghong

v2.23.0 | Report a Bug | By Email