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

Linda Dunbar <linda.dunbar@futurewei.com> Wed, 09 October 2019 20:26 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 EF6E112004F; Wed, 9 Oct 2019 13:26:03 -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_IMAGE_RATIO_02=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NONE=0.001] autolearn=ham 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 xPNysCS_OpT2; Wed, 9 Oct 2019 13:26:01 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-eopbgr750134.outbound.protection.outlook.com [40.107.75.134]) (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 176DE120251; Wed, 9 Oct 2019 13:26:00 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DXYf+J5TYXNe9EdY4EXydgnlccvUZkwvh2ZNnGQnxVNvW0Rhdl7gs4f8Dj0QrT9eGG1r7XFZoqYZbvF/zkda0bFkglzjAJN1A69uBuMvgoDyF4BY3D+2KHjRdf/bjye9SrXXtswzLZnvOPcUcoGy3VpT6MYJJkDBuxBugEYhSziqPNKvBYJl3z3sbGfGbHr9PZ/tjmo7Ooj2I50Vs3LKXjuutqpfhAbOeuW+gWQGVJrOahuTMKJt3ehRMInt0GVHPRZmMWJtqTRCkuSgcOSHt6GQV7JWuRr7djEwQaKnEwnh9eVhk8zg/B5fUCU+q58pEfFc4Lo+YmTq4P27QInHgw==
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=Od5etwSfyid6ff2uReAFE28zp7zom3ZC7O3Obf3cXZI=; b=SJ4mh+XL4pUdJ9ezUNln9OnsTDWUccaAfgDBA7mjiPpYd/GqeyYWTR6ShhMzhHQc3rSLaO5xJSN1i427afjNn6fZC/e+i83mzjRAeOSqUJgCVHjuRWMMQerOn7Gc5B77/S/0fT0eb9E+cvIdbSNm/AbULBNe2GM4gDVwQxTAWhte5h+g3oSiGDRZGCU1k9/x1U7kby20sCiPZgd8aDUWhykIkFUv+mRGQl7KIDST9pYhVOlylhzuIBrfZ9JXSiaS2b/tp1dCgCyzMKm5B8UMgJKFlrV8GRjbH9Tb8TUmWmeh3//yyO9wCucZ2uJasncbT91UdFYTF7o81O8uYZTKxg==
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=Od5etwSfyid6ff2uReAFE28zp7zom3ZC7O3Obf3cXZI=; b=WGSyRXw5YnBqiAWkQE/eA6Oq45ttDERO+58e+QeMivshY0J8yArO3Qw4zQCEL81cQD4EuE6WoE0WChySD9IQqOHMaagvS0kh1u9+jI6VZ1vjBlf/RDcA5tJfti4VC+iZInBrW9l3sWrnPjBZw7TMfRRolFDwcJUainw5D4Jq0kQ=
Received: from MN2PR13MB3582.namprd13.prod.outlook.com (10.255.239.156) by MN2PR13MB2670.namprd13.prod.outlook.com (20.178.251.213) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.14; Wed, 9 Oct 2019 20:25:58 +0000
Received: from MN2PR13MB3582.namprd13.prod.outlook.com ([fe80::6dcb:88a5:b3a9:e05c]) by MN2PR13MB3582.namprd13.prod.outlook.com ([fe80::6dcb:88a5:b3a9:e05c%4]) with mapi id 15.20.2347.016; Wed, 9 Oct 2019 20:25:58 +0000
From: Linda Dunbar <linda.dunbar@futurewei.com>
To: "idr@ietf.org" <idr@ietf.org>, "draft-ietf-idr-tunnel-encaps@ietf.org" <draft-ietf-idr-tunnel-encaps@ietf.org>
Thread-Topic: Can one Destination Address appear in both Tunnel Encap Attribute and in MP_REACH_NLRI ?
Thread-Index: AdV+31YOey/wlRogSQu2ak3Czg/rBg==
Date: Wed, 9 Oct 2019 20:25:57 +0000
Message-ID: <MN2PR13MB3582A1E1FE3441CDD54A101985950@MN2PR13MB3582.namprd13.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=linda.dunbar@futurewei.com;
x-originating-ip: [72.180.73.64]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 84109d65-e083-450c-879d-08d74cf6e4d2
x-ms-traffictypediagnostic: MN2PR13MB2670:
x-microsoft-antispam-prvs: <MN2PR13MB26709166E2D1572F216728AC85950@MN2PR13MB2670.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 018577E36E
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(136003)(376002)(346002)(366004)(396003)(39850400004)(199004)(189003)(6436002)(71190400001)(256004)(733005)(3846002)(6116002)(790700001)(7696005)(6506007)(71200400001)(316002)(4744005)(14454004)(450100002)(4743002)(110136005)(478600001)(25786009)(8676002)(52536014)(66446008)(66476007)(66556008)(66576008)(99936001)(64756008)(86362001)(81166006)(54896002)(2906002)(5660300002)(8936002)(81156014)(186003)(7736002)(2501003)(44832011)(26005)(66066001)(102836004)(99286004)(486006)(76116006)(476003)(74316002)(66946007)(55016002)(6306002)(33656002)(9686003); DIR:OUT; SFP:1102; SCL:1; SRVR:MN2PR13MB2670; H:MN2PR13MB3582.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: H+QZ7CAzpjAesJajIU4BKHuxCSKcXVskLT/hgy2K6a80ifsMI3V8ZnlJ7Y74nYbzr61rIW++/iw5z2bWz6bPEC07Y/dFtRhorVgO7UAt1UnemgT4LTV+HU6CyyPnrPVFH9dCvRaw/6ntZRROya+x0R22IIP+yxgZF5aax15CMpw6cOee50Pk6Ewe5jaaTwFjQ1uIMz7ihHMmGKVUr+ubDWtWhwaR+enzxB7+GSpeNghIJFWqJgjq3PkumI0uGF+c2XidxQT+PcWL/4gHKE8RpEIMzn2FlNgMTEJ/E9r0HUC5juaqJwTALgyyuRIEAfVWilYwJFCXW8wokXoCCtaHywCojhHtG7n7afsZvb2oKJlT3e1A6HqTuQGaye6BO4FBcHyKa4qk1DkTTzzWu1xsAF32vq0QLq2X9efX8xiAv7g=
x-ms-exchange-transport-forked: True
Content-Type: multipart/related; boundary="_005_MN2PR13MB3582A1E1FE3441CDD54A101985950MN2PR13MB3582namp_"; type="multipart/alternative"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 84109d65-e083-450c-879d-08d74cf6e4d2
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Oct 2019 20:25:57.9843 (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: Fsk4uwKU4I5iR/dyIF72faQzg+T89Y2Hal+repJml3whIA+Vh4ZXi206mcC8v1+Ush5piok/i8qnb/TCYzNQqQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR13MB2670
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/GI7T3CYlVaF0__E6FLnTOZnW1Go>
Subject: [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: Wed, 09 Oct 2019 20:26:04 -0000

Dear authors:
draft-ietf-idr-tunnel-encaps specifies the The Tunnel Encapsulation attribute as an optional transitive BGP Path
attribute, with code point 23.
Does it mean Tunnel Encapsulation Attribute is listed at the same level as MP_REACH_NLRI (Code Point 14) in the Path Attributes lists shown in the following captured packets from Wireshark? If a Destination address is already listed in the MP_RACH_NLRI, is it listed again in the Tunnel Encap subTLV (if it can be reached via some tunnel, such as VxLAN/GRE/?


[cid:image002.png@01D57EB5.CC6C7D20]


Does the Tunnel Encapsulation Attributes have the same fields as MP_REACH_NLRI (RFC4760)?
Or the Tunnel Encapsulation Attributes is the "Network Layer Reachability Information" field of MP_REACH_NLRI?

[cid:image005.png@01D57EB5.CC6C7D20]


Thank you very much,

Linda Dunbar