IETF Logo Mail Archive

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

"Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.com> Mon, 01 July 2019 06:50 UTC

Return-Path: <jorge.rabadan@nokia.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 30DF512000E for <bess@ietfa.amsl.com>; Sun, 30 Jun 2019 23:50:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.401
X-Spam-Level:
X-Spam-Status: No, score=-0.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=1.5, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.com
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 xM-x0tFEba8h for <bess@ietfa.amsl.com>; Sun, 30 Jun 2019 23:50:43 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-he1eur04on0706.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe0d::706]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7697120018 for <bess@ietf.org>; Sun, 30 Jun 2019 23:50:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=WTmNmFD9T7PH9i3iOJGlqi3tgwD5WEOwF9hQntgwIvE=; b=QVzTQhGSfB/anBni85zFBSDdKYEjb2NAQlVrSMhy+BYiwybqQMmUeo41ImloV5bfShbqKOaWIXXcRLi0ClzKDXoaRchdjUh0lfZAENu1jp3RSiLmIi6yBSx0Jwr9FB1CAkxQVopbslLEt7eMfbOUGgm2G3bSyNnj4Lg7eMbDXqg=
Received: from AM0PR07MB3844.eurprd07.prod.outlook.com (52.134.82.20) by AM0PR07MB3892.eurprd07.prod.outlook.com (52.134.82.32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2052.14; Mon, 1 Jul 2019 06:50:40 +0000
Received: from AM0PR07MB3844.eurprd07.prod.outlook.com ([fe80::2ce0:636d:59e3:5654]) by AM0PR07MB3844.eurprd07.prod.outlook.com ([fe80::2ce0:636d:59e3:5654%3]) with mapi id 15.20.2052.010; Mon, 1 Jul 2019 06:50:40 +0000
From: "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.com>
To: "huangyang (E)" <yang.huang@huawei.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+7VEA==
Date: Mon, 01 Jul 2019 06:50:40 +0000
Message-ID: <EE4C2A95-2503-424D-B83B-C7085DCC28AB@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1a.0.190609
authentication-results: spf=none (sender IP is ) smtp.mailfrom=jorge.rabadan@nokia.com;
x-originating-ip: [88.14.49.217]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 04a71759-d12b-483c-80f8-08d6fdf06e4d
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:AM0PR07MB3892;
x-ms-traffictypediagnostic: AM0PR07MB3892:
x-microsoft-antispam-prvs: <AM0PR07MB3892B416C38AA2270BA74ADDF7F90@AM0PR07MB3892.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 00851CA28B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(376002)(136003)(39860400002)(366004)(396003)(346002)(199004)(189003)(256004)(81166006)(478600001)(81156014)(110136005)(8676002)(99286004)(58126008)(6306002)(54896002)(2616005)(8936002)(2906002)(316002)(86362001)(53936002)(9326002)(14454004)(5660300002)(66574012)(68736007)(7736002)(71200400001)(33656002)(71190400001)(186003)(6246003)(6512007)(53546011)(66066001)(6506007)(26005)(476003)(6436002)(6486002)(2501003)(66476007)(229853002)(76116006)(91956017)(25786009)(36756003)(66446008)(64756008)(66556008)(73956011)(66946007)(102836004)(486006)(6116002)(3846002); DIR:OUT; SFP:1102; SCL:1; SRVR:AM0PR07MB3892; H:AM0PR07MB3844.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: nokia.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: i8tZxBg2YaeS78+FgVjRhfO9tkwMOJNFnSGDQ6INOpkoTxaUGTg41CUnX5FH4VpVDjhAy0ZFQ5GFUWsA76/cIyxdCE/kT+NqXCHobDrULFdiMaYU+avMncZ3W3UYbEnfibFr6ZR4+N1CfVN7UkSWW8jR2mZo2H0EnRQQO7ScHI63jYeMwuLhDp/PzQ5Z7bVe7mVdGcwyOLm3vb2JCNrkvtCZu5+vUkSHnUY9OmGKm1Hd4WIe0DKo4aucvOSeIx0jq8GeuoBUXYOOMluO/GAHwD/bRXVhIPJyBqk5vZk7wCz39+s1FnmUPczNAhvtn+JoFc+wJLyLSEtQ+OyDkjwJuBaRAlMcALHjizAUigVDifbqnWZwPUx/vfHoswLjcgnzLi9TvUWtDO6KJMML+3MJC+nTs9jF1+NY8J6AEgvjbUs=
Content-Type: multipart/alternative; boundary="_000_EE4C2A952503424DB83BC7085DCC28ABnokiacom_"
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 04a71759-d12b-483c-80f8-08d6fdf06e4d
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Jul 2019 06:50:40.3065 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: jorge.rabadan@nokia.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB3892
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/4f6CRa3O70N0gA6jMCu5kvuflOw>
Subject: Re: [bess] [Mail regarding rfc7432]Could you clarify which IP address we use to construct P2P tunnel for ingress replication.
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 06:50:45 -0000

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> on behalf of "huangyang (E)" <yang.huang@huawei.com>
Date: Monday, July 1, 2019 at 8:46 AM
To: "bess@ietf.org" <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

v2.23.0 | Report a Bug | By Email