Re: [Idr] Can one Destination Address appear in both Tunnel Encap Attribute and in MP_REACH_NLRI ?

Linda Dunbar <linda.dunbar@futurewei.com> Tue, 22 October 2019 20:25 UTC

Return-Path: <linda.dunbar@futurewei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE329120892; Tue, 22 Oct 2019 13:25:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 5o-zc4zE8V8p; Tue, 22 Oct 2019 13:25:54 -0700 (PDT)
Received: from NAM05-BY2-obe.outbound.protection.outlook.com (mail-eopbgr710104.outbound.protection.outlook.com [40.107.71.104]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E8811208B5; Tue, 22 Oct 2019 13:25:54 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=SrcDJDy8ryIW1LuOt7iUTtW0eEraI5SFy5GRwylPTto9lLleOzsleYdTgj2zxILlAVguvtODeugrRWVEZ2+uwoy3DocOaksrsYM3rZ8YnjU27glhNNyurDwmmBQVjXE+O8HarUiqgWohLxvq3DgRT5q35pXCeLYLAVQ5mnw6cQF30hT+9G3w6oxlPn1gvjXpCrqonrN0JqOAdL6KEbA84x2cE2ktET1KwRgVHLmHl2qv+zM2jErVbaDGcoTZJxxjW4l3QfFJ3jv+3JCnp1dGyua99Pm5rxgncO4O0J6/Np9uK3Y17jGGSh1G1C3uus2IiMqqWZ7/ZQWsid+Y1nHzEA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=uFs+BhqU12QY/ZXwk8g4ws3rLo16J0ezYEIIF8ZqWLQ=; b=Z+KZx6rmvhDaAAQuSP+aGxvlzXnlYKdA9bXuGN0VKD8TF2GrZQf2iGdbxoYSK4GZBotfs4feWyiuqHOXQKahGYsNPxZj4dI1h+GUT0LdduTXAbsEwo2I9iji+uhy/kOxxM7jJoy/5idAkV7y9lgDP8mRwVmU1bYQ+TR3Dzfsk1LDIJbJDdjhtvGyUCMAGG971jOwQxNed7hLWY53FUebwyWacYfX0Y3mSMNpN6i5l/Klt1lOtjhOpSAbzxmtdX7mu/ImHAFjKxt8nIu0YHzmK4yhbjZPVVKsn40XgsObdIhGuhKaUaa//tQY5zSRuy5Cjpnq4wWjk+RgmFp5SR13wQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=uFs+BhqU12QY/ZXwk8g4ws3rLo16J0ezYEIIF8ZqWLQ=; b=r7s9km6/cOQzA7iORxK3u7lvA0fwfK+LbWY0sUvhA12U1L+W5jaPMFecHPZYeLDDL6bUO//hdBS0GDoaTiEekj0SWCdAXAaVXC5tORtB12Szn82KfnhcsuqWOPOaaoaMBxmm+ANj/PLqLlSSlMgTdfaH4dB58D1dcRPfn6E1xEA=
Received: from BN8PR13MB2628.namprd13.prod.outlook.com (20.178.219.10) by BN8PR13MB2899.namprd13.prod.outlook.com (20.178.220.215) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2387.17; Tue, 22 Oct 2019 20:25:50 +0000
Received: from BN8PR13MB2628.namprd13.prod.outlook.com ([fe80::9f3:c754:7ac8:b3dd]) by BN8PR13MB2628.namprd13.prod.outlook.com ([fe80::9f3:c754:7ac8:b3dd%7]) with mapi id 15.20.2387.016; Tue, 22 Oct 2019 20:25:50 +0000
From: Linda Dunbar <linda.dunbar@futurewei.com>
To: Srihari Sangli <ssangli@juniper.net>, Robert Raszuk <robert@raszuk.net>, Srihari Sangli <ssangli=40juniper.net@dmarc.ietf.org>
CC: "idr@ietf.org" <idr@ietf.org>, "draft-ietf-idr-tunnel-encaps@ietf.org" <draft-ietf-idr-tunnel-encaps@ietf.org>
Thread-Topic: [Idr] Can one Destination Address appear in both Tunnel Encap Attribute and in MP_REACH_NLRI ?
Thread-Index: AQHVhL8eOYPqXsxjIUaLnk83IegY9KdeeoqAgAinp0A=
Date: Tue, 22 Oct 2019 20:25:49 +0000
Message-ID: <BN8PR13MB2628AB4B6E3AC7EE6799A33985680@BN8PR13MB2628.namprd13.prod.outlook.com>
References: <MN2PR13MB3582A1E1FE3441CDD54A101985950@MN2PR13MB3582.namprd13.prod.outlook.com> <78F7A474-6F86-4EA3-93A3-001B4E2C2116@juniper.net> <CAOj+MMGqKj=zKbws92ni1fL2O-So=dbcW-mb02uRnQ+G55xm_w@mail.gmail.com> <0B48E5E7-3A1F-45C0-ACF9-B9A0FA323ED4@juniper.net>
In-Reply-To: <0B48E5E7-3A1F-45C0-ACF9-B9A0FA323ED4@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_9784d817-3396-4a4f-b60c-3ef6b345fe55_Enabled=true; MSIP_Label_9784d817-3396-4a4f-b60c-3ef6b345fe55_Name=Juniper Business Use Only; MSIP_Label_9784d817-3396-4a4f-b60c-3ef6b345fe55_Enabled=true; MSIP_Label_9784d817-3396-4a4f-b60c-3ef6b345fe55_SiteId=bea78b3c-4cdb-4130-854a-1d193232e5f4; MSIP_Label_9784d817-3396-4a4f-b60c-3ef6b345fe55_ContentBits=0; MSIP_Label_9784d817-3396-4a4f-b60c-3ef6b345fe55_Method=Standard; MSIP_Label_9784d817-3396-4a4f-b60c-3ef6b345fe55_ActionId=a57d5b42-7b77-45b8-a75e-00006cf5a453; MSIP_Label_9784d817-3396-4a4f-b60c-3ef6b345fe55_SetDate=2019-10-17T08:03:43Z;
authentication-results: spf=none (sender IP is ) smtp.mailfrom=linda.dunbar@futurewei.com;
x-originating-ip: [206.16.17.231]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c64b4185-b0cb-440d-9938-08d7572e078b
x-ms-traffictypediagnostic: BN8PR13MB2899:
x-microsoft-antispam-prvs: <BN8PR13MB2899D4941CDC0AA4E5963C7A85680@BN8PR13MB2899.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 01986AE76B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(136003)(396003)(39850400004)(376002)(366004)(346002)(129404003)(199004)(189003)(102836004)(26005)(71200400001)(6116002)(7736002)(66066001)(1941001)(54896002)(2906002)(99286004)(6506007)(53546011)(7696005)(76176011)(3846002)(6306002)(74316002)(229853002)(186003)(790700001)(5660300002)(52536014)(44832011)(486006)(71190400001)(6436002)(476003)(446003)(9686003)(11346002)(55016002)(76116006)(54906003)(110136005)(256004)(66446008)(64756008)(66556008)(66476007)(66946007)(81156014)(8936002)(316002)(14444005)(8676002)(33656002)(86362001)(25786009)(6246003)(478600001)(14454004)(81166006)(4326008); DIR:OUT; SFP:1102; SCL:1; SRVR:BN8PR13MB2899; H:BN8PR13MB2628.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: vpC6EUZnVdTZWRK2XTY/fGgmRCQal+ZsK4z5kIeNFq4CKYmSi0xNuqa2aZUUc7assOvKwqeceI01M2x7wIKVJuzwyzN0exFaJ89CjYEp94fmXj/nAPOovYI4TzBWRY/3TshmhL77HqMDRx4CVUslhDbOpzIVvFNffzdmd8NIlH5jy2V2qETzglIAza7W+UL73GPYX2jQA+TAb+fxRhAkHs/Twdkm2s75BnQO38zvDlescdeLMW5QiM+zaV0umt6vbqbpazRcDE62C1e4nFrHuEgrtYqwK/HiGKDdBgNH0IBiTU0L2/8Cpkia2Cz7dbju4SLUD87ZmqeVu/pmycKVgifu1cNGRBSmpNIdBh+EH/oPTuxWGWCwCkMqm9SHIivGXKw+Us1TQE5KtVazPGxinsajHFV5LI/UcZDrQpPKJ7Ize7bQO+Jkpj+b1EDVice6
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BN8PR13MB2628AB4B6E3AC7EE6799A33985680BN8PR13MB2628namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: c64b4185-b0cb-440d-9938-08d7572e078b
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Oct 2019 20:25:50.0717 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: GbyMeEuHnUpzbLOR1mT6sQlucPLbInDi5l31hdRYrjan0hsgITkLTR2dvxjLHOIvDCbgxHyDBfDwriVL5xNTJQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN8PR13MB2899
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/C0S3PcXJcJZPvGrBCnaw6V7W24g>
Subject: Re: [Idr] Can one Destination Address appear in both Tunnel Encap Attribute and in MP_REACH_NLRI ?
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Oct 2019 20:26:03 -0000

Srihari and Robert,

Thank you very much for the discussion.

Your explanation indicates that the tunnel information described in Tunnel Path Attributes are applicable to all the NLRI listed in the MP-NLRI Path Attributes, correct?
For example, D1/D2/D3/D4 all have R2 as Next Hop, and R2 supports GRE and VxLAN.  The Update from R2 will have D1, D2, D3, D4 listed in the MP-NLRI (code= 14), and GRE tunnel & VxLAN tunnel listed under the Tunnel Attribute (code = 23).

When R1 receives the UPDATE from R2, R1 can assume that packets to D1, D2, D3, D4 can use either VxLAN or GRE. Is it correct?

So if R2 needs to specifically indicate GRE for D1, VxLAN for D2, D3, and IPinIP for D4, then R2 needs to send 3 separate UPDATE messages. Is it correct?

Thank you very much.



From: Srihari Sangli <ssangli@juniper.net>
Sent: Thursday, October 17, 2019 3:08 AM
To: Robert Raszuk <robert@raszuk.net>et>; Srihari Sangli <ssangli=40juniper.net@dmarc.ietf.org>
Cc: Linda Dunbar <linda.dunbar@futurewei.com>om>; idr@ietf.org; draft-ietf-idr-tunnel-encaps@ietf.org
Subject: Re: [Idr] Can one Destination Address appear in both Tunnel Encap Attribute and in MP_REACH_NLRI ?

Hi Robert,



My reading of Linda's point was a question regarding the case where for prefix A NLRI points to
next hop NH_1 but tunnel endpoint says go to NH_2.

Is such update still valid ?

Has tunnel encapsulation attribute power to "overrule" BGP next hop from MP_REACH ?


The draft in Section 5 explains this. If the update has a valid Tunnel Encapsulation attribute and if any of the tunnel(s) is considered to be feasible, then it MUST use the tunnel. That means in your example, such an update is valid and NH_2 should be used.

Hope this helps. Thanks.

srihari…