IETF Logo Mail Archive

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

Srihari Sangli <ssangli@juniper.net> Thu, 17 October 2019 05:31 UTC

Return-Path: <ssangli@juniper.net>
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 060C3120821; Wed, 16 Oct 2019 22:31:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_RATIO_04=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 x_YD8CVI95ID; Wed, 16 Oct 2019 22:31:32 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 966CB120236; Wed, 16 Oct 2019 22:31:32 -0700 (PDT)
Received: from pps.filterd (m0108157.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id x9H5VJWX031412; Wed, 16 Oct 2019 22:31:29 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=4I23QIW1kI5R6q62R/IP6YSiLkvchxFVVdGVP81zhLo=; b=yX0ujVIJJIarsMwlNdrExTbeKTA74SZneK3XuiSWrS3zNu7bPE11+AJE5bI41YWfTSBd z4UKzXWgSWkyh4LzU7ObcnI8runX+ngsSIYS9XS0gc2PIqpujOUGvSpso4+zXd3LYrPM XbYpG2uK/PGrTbboESPNqnWUh7WNoDMugQpTQh8sgmbFaGx4+4SwZnBKU4GkhL5wHhNX PVaeS7pjdYKz31oOskJUFgVJUHfHWr+zX4sFbFMF9+VwpyB9Tn1GcEDbQlIAbnV41CSW 0j3VGlG5l9m/ldUezfir/eJt+Mrt8lor+1CjdL6R2ULuhoZvpHud067iZwFOemjrW5iO zA==
Received: from nam01-bn3-obe.outbound.protection.outlook.com (mail-bn3nam01lp2053.outbound.protection.outlook.com [104.47.33.53]) by mx0a-00273201.pphosted.com with ESMTP id 2vpdfp8cfk-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 16 Oct 2019 22:31:28 -0700
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=EdEDsextuzf1FlN6CAig+psls/ZatF187zfAHz2hpGbOOEH7ufh8WvDZE85tGB2G7e/aQr3feJYc/gul1jB2g4jXm8qbGDQtX0sPsqE0rfSOAR7vsR1VEwr7ky6cXZuHEDp1byAU1Fw2OB6dp0+rGUxOSkRTXM6KP4DOdw/vXI5IDVdPiWvuHszWw2JYBVKQz1M1UIMuH5VOnYZcGjOzRoc8BrJnUYepREoByMAT+lI1m3Z5/J8EvSQZd3I+4y2cMNwSpK53umY7lUtWzy/z7naSYW6fUvk7v2nw8KsJmx6v9TxIytKFheYt5isEu5PYI5W4nz+XcwtK8BuHE6smPQ==
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=4I23QIW1kI5R6q62R/IP6YSiLkvchxFVVdGVP81zhLo=; b=m8hJ/wFNnbFifi1/yeDUQdXriEKUVSDlVk7yoTTk75TItFB9An2P9jx9HvVUikvt2d7cjLHdMSN3jgj0c7pS4J6zl2avbQJePVMVpWVprb5beoyHV5TPCQEvUQ9HdOyifyGhi6VK9FYIQB5i44MdmaRGYtWVGKAWchB6BE0jK0vzbufEI5+mKMa7qk8/IUhmG6FJVD0TZzNUXuXGRbk94Os44osgS4HqiONLQIjSELd9uhpRzDZ0nFuuEEhA++MUS2yDhZae1oosYSgOhEtV7HDixFQUFiciJXTPRDOVUE7i4ztWuFPWPUFHFx7MlzefC3AKQeHTeT6BUz628A9UBQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=juniper.net; dmarc=pass action=none header.from=juniper.net; dkim=pass header.d=juniper.net; arc=none
Received: from BYAPR05MB6230.namprd05.prod.outlook.com (20.178.55.215) by BYAPR05MB4485.namprd05.prod.outlook.com (52.135.203.27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.11; Thu, 17 Oct 2019 05:31:26 +0000
Received: from BYAPR05MB6230.namprd05.prod.outlook.com ([fe80::5874:eda3:f289:dc45]) by BYAPR05MB6230.namprd05.prod.outlook.com ([fe80::5874:eda3:f289:dc45%4]) with mapi id 15.20.2367.014; Thu, 17 Oct 2019 05:31:26 +0000
From: Srihari Sangli <ssangli@juniper.net>
To: Linda Dunbar <linda.dunbar@futurewei.com>, "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/rBgF+t6wA
Date: Thu, 17 Oct 2019 05:31:25 +0000
Message-ID: <78F7A474-6F86-4EA3-93A3-001B4E2C2116@juniper.net>
References: <MN2PR13MB3582A1E1FE3441CDD54A101985950@MN2PR13MB3582.namprd13.prod.outlook.com>
In-Reply-To: <MN2PR13MB3582A1E1FE3441CDD54A101985950@MN2PR13MB3582.namprd13.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: yes
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=2a46ea2f-d43c-4aa2-afe3-0000fbb0c733; MSIP_Label_9784d817-3396-4a4f-b60c-3ef6b345fe55_SetDate=2019-10-17T05:26:31Z;
x-originating-ip: [116.197.184.10]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ef92d864-e8ba-4e3c-007f-08d752c34115
x-ms-office365-filtering-ht: Tenant
x-ms-traffictypediagnostic: BYAPR05MB4485:
x-microsoft-antispam-prvs: <BYAPR05MB4485BC83203FEA38DF1B1DA5B96D0@BYAPR05MB4485.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 01930B2BA8
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(366004)(396003)(376002)(346002)(136003)(189003)(199004)(2906002)(110136005)(8936002)(81156014)(81166006)(8676002)(6436002)(76176011)(5660300002)(2201001)(11346002)(476003)(446003)(2616005)(486006)(99936001)(2501003)(66476007)(6246003)(86362001)(6486002)(478600001)(66576008)(54896002)(229853002)(14454004)(6306002)(236005)(6512007)(33656002)(64756008)(256004)(76116006)(71200400001)(91956017)(71190400001)(66446008)(14444005)(66556008)(66946007)(25786009)(26005)(790700001)(6116002)(66066001)(316002)(7736002)(186003)(99286004)(36756003)(3846002)(733005)(102836004)(6506007); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB4485; H:BYAPR05MB6230.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: FBWgsd7HwBUPKGIRtbhbsnb1zx7Mb+E5X0+L90G6tlptipseALcCVBFUslEUzf6ahHYHyrppXKgwbfxVdq1QZhrUwbjOch/2TEootB4RULjlp+1yKQfEEmO2c0tj2fBjcjQ5BWuYVR419h+czLBO3KFXgWWEsKhP3IvW/wjk9DGYZvYFIkuwCEYonalQxnzLEG48lv3EPV4bceJtwPKKqIUpwiMbpbpFKm+6BqmctdYIbGcA7bz/TQtoketxyzuEGu3gmsULI9KzHPufhcksXuLuN1JI/OWXk195CuBvOgYNJlxJije2uccj9fM0xb1x4hKMntoKYxKF+IYdtbXAzNSGyka8DQWeG3LhTzulqOUO0Ep61j1pZOB1YuWGAFDpD5rymAvbmS4R51yEtkzt1UdcNLBB1pXCSy/tUCkVBvA=
x-ms-exchange-transport-forked: True
Content-Type: multipart/related; boundary="_005_78F7A4746F864EA393A3001B4E2C2116junipernet_"; type="multipart/alternative"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: ef92d864-e8ba-4e3c-007f-08d752c34115
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Oct 2019 05:31:25.6592 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: XJZ+Se0FeiwtVlQi1sWDC1sWQ7/yJSzq3B97cBb9lh+QB12i1xV+eYieGkId467JhB7m4oeMjXlq8lJ2Oo0NqA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB4485
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,1.0.8 definitions=2019-10-17_02:2019-10-17,2019-10-17 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 suspectscore=0 adultscore=0 mlxscore=0 priorityscore=1501 mlxlogscore=863 malwarescore=0 impostorscore=0 lowpriorityscore=0 bulkscore=0 clxscore=1011 spamscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1908290000 definitions=main-1910170043
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/xw4VH6AWj-DSK3Y3KFJrMFquC3E>
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: Thu, 17 Oct 2019 05:31:35 -0000

Linda,

I’m not sure if I understand your question completely. Pls see comments inline.

On 10/10/19, 1:56 AM Linda Dunbar from linda.dunbar@futurewei.com<mailto:linda.dunbar@futurewei.com> said >

Dear authors:
draft-ietf-idr-tunnel-encaps specifies the The Tunnel Encapsulation attribute as an optional transitive BGP Path
attribute, with code point 23.

Yes, that’ right.

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?

Like you mention, the Tunnel Encapsulation Attribute is a Path attribute, so it is a matter to displaying all the path attributes, one can display in the ascending order of the Code Points.

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/?

I’m not clear what you mean here. The MP_REACH provides the reachability information while the Tunnel Encapsulation Attribute provides the Tunnel details (remote-endpoint, encapsulation, etc). The presence of Tunnel Encapsulation attribute in an update that carries MP_REACH attribute indicates the data path destined for prefixes encoded in the NLRI field of MP_REACH.

Thanks.

srihari…


[cid:image001.png@01D584DA.351A7140]


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:image002.png@01D584DA.351A7140]


Thank you very much,

Linda Dunbar

v2.23.0 | Report a Bug | By Email