[bess] 答复: [Mail regarding rfc7432]Could you clarify which IP address we use to construct P2P tunnel for ingress replication.

"huangyang (E)" <yang.huang@huawei.com> Mon, 01 July 2019 07:07 UTC

Return-Path: <yang.huang@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 8DDA412000E for <bess@ietfa.amsl.com>; Mon, 1 Jul 2019 00:07:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 iPFO5d9Pnlt3 for <bess@ietfa.amsl.com>; Mon, 1 Jul 2019 00:07:23 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06F9F12021B for <bess@ietf.org>; Mon, 1 Jul 2019 00:07:23 -0700 (PDT)
Received: from LHREML710-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 31B943A93753D5CBA269 for <bess@ietf.org>; Mon, 1 Jul 2019 08:07:21 +0100 (IST)
Received: from dggeme759-chm.china.huawei.com (10.3.19.105) by LHREML710-CAH.china.huawei.com (10.201.108.33) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 1 Jul 2019 08:07:20 +0100
Received: from dggeme759-chm.china.huawei.com (10.3.19.105) by dggeme759-chm.china.huawei.com (10.3.19.105) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Mon, 1 Jul 2019 15:07:18 +0800
Received: from dggeme759-chm.china.huawei.com ([10.7.64.73]) by dggeme759-chm.china.huawei.com ([10.7.64.73]) with mapi id 15.01.1591.008; Mon, 1 Jul 2019 15:07:18 +0800
From: "huangyang (E)" <yang.huang@huawei.com>
To: "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.com>, "bess@ietf.org" <bess@ietf.org>
Thread-Topic: [bess] [Mail regarding rfc7432]Could you clarify which IP address we use to construct P2P tunnel for ingress replication.
Thread-Index: AQHVL9lLSLygf9/6REqLri6O1+7VEKa1VLiw
Date: Mon, 1 Jul 2019 07:07:18 +0000
Message-ID: <222809693f164161ad59f92e189ae8c2@huawei.com>
References: <EE4C2A95-2503-424D-B83B-C7085DCC28AB@nokia.com>
In-Reply-To: <EE4C2A95-2503-424D-B83B-C7085DCC28AB@nokia.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.217.172]
Content-Type: multipart/alternative; boundary="_000_222809693f164161ad59f92e189ae8c2huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/N63VmOeZ7aslyboi-quY6Egp5mE>
Subject: [bess] =?utf-8?b?562U5aSNOiAgW01haWwgcmVnYXJkaW5nIHJmYzc0MzJd?= =?utf-8?q?Could_you_clarify_which_IP_address_we_use_to_construct_P2P_tunn?= =?utf-8?q?el_for_ingress_replication=2E?=
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
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, 01 Jul 2019 07:07:25 -0000

Hi,
Thanks for your reply, but I see in RFC 8365, there is description like this :

In section “9.  Support for Multicast”: “The originating router's IP address field is set to the NVE's IP address.”

In section “5.1.3.  Constructing EVPN BGP Routes” : “The Next Hop field of the MP_REACH_NLRI attribute of the route MUST
   be set to the IPv4 or IPv6 address of the NVE.  The remaining fields
   in each route are set as per [RFC7432].”

It is confused that if the addresses described in above two places is the same ip address or not. So I am not confirm that there

may be some situations where the originating router's IP address is not equal to bgp next hop.

Or the IMET route construction in vxlan scenario is not follow the same rule as in mpls scenario(rfc7432) ?

Thanks

Yang Huang

发件人: Rabadan, Jorge (Nokia - US/Mountain View) [mailto:jorge.rabadan@nokia.com]
发送时间: 2019年7月1日 14:51
收件人: huangyang (E) <yang.huang@huawei.com>; bess@ietf.org
主题: Re: [bess] [Mail regarding rfc7432]Could you clarify which IP address we use to construct P2P tunnel for ingress replication.

Hi,

I think you should construct the ingress replication tunnels using the next hop of the IMET routes, otherwise you will have issues with inter-as model B scenarios. The received originating IP and next-hop at the ingress PE do not need to be the same.
Thanks.
Jorge

From: BESS <bess-bounces@ietf.org<mailto:bess-bounces@ietf.org>> on behalf of "huangyang (E)" <yang.huang@huawei.com<mailto:yang.huang@huawei.com>>
Date: Monday, July 1, 2019 at 8:46 AM
To: "bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>
Subject: [bess] [Mail regarding rfc7432]Could you clarify which IP address we use to construct P2P tunnel for ingress replication.

Hi WG,

In the charpter 11.2 of RFC 7432:

11.2.  P-Tunnel Identification
"...+ If the PE that originates the advertisement uses ingress
replication for the P-tunnel for EVPN, the route MUST include the
PMSI Tunnel attribute with the Tunnel Type set to Ingress
Replication and the Tunnel Identifier set to a routable address of
the PE."

a routable address of the PE is not so strict. And does this mean
we use the Tunnel Identifier to construct P2P tunnel for ingress
replication, or we use the Originating Router's IP Address in the
IMET route key, or they are equivalent meaning?

And I see it use the BGP Next hop to construct P2P tunnel for BUM
ingress relication in RFC8365, Should Originating Router’s IP Address,
the IP address of BGP Next hop, Tunnel Identifier in PMSI, be the same
IP address?

Now, this may cause interact problems when it implements differently.
Could you clarify this? Thanks.

Brgds,

Yang Huang