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 08:08 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 7881A120838; Thu, 17 Oct 2019 01:08:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 ezNiJHpjZAqO; Thu, 17 Oct 2019 01:08:17 -0700 (PDT)
Received: from mx0a-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 5203F120115; Thu, 17 Oct 2019 01:08:17 -0700 (PDT)
Received: from pps.filterd (m0108156.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id x9H81Off011869; Thu, 17 Oct 2019 01:08:14 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=dY207gADGizbd48V0aJAPJiBvnNS+Km6W/S9cpj2cbM=; b=oas1P3aLn1G2pOd//UiBBNvnQvCB6ryC4B/Q62QgAjBJf3rlU8STCDVRTw18YzZXIUNh HUHpmgdz1x3uQjXKEpINjpfn2WqP3ORbE5qxdqr186MnBF8TpaACnqh4y+02X7/PFxC7 zD6j/DZroFZl6i13O6KQpAsRbct9EWw8O1xQ3kncuSGdxwGDXwoyPq4Pc9jKiFaqgzo7 5blClFKEbV+m5UeH5sCN8pU9bRxpAEfjKMkesybdLqFxp5XcA9eVDdvNeiSBoWPdOXjW HFw7FHeKGdS8j6Q87JvSi2TWKLMnhcNzQt1aviEzHzrp9KwHc+WL9wjklB0wAS7fPTRO KQ==
Received: from nam03-dm3-obe.outbound.protection.outlook.com (mail-dm3nam03lp2052.outbound.protection.outlook.com [104.47.41.52]) by mx0a-00273201.pphosted.com with ESMTP id 2vnukstehb-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 17 Oct 2019 01:08:14 -0700
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Dlz+gZQOitf3dxtIcDGC35pzoioQn/+EvRQTREyY6G13naZBitfmCUb0mT+z+XEKEcp6sJFOZNGvID95M6GK3VqoT5tnZJ+2JU1pjFrsttc4q1nWNRFoi0jaTn2jSC5vS8wCwhOrabM2VsRI3FbN8yEx2XT9BtG8lz6hUiD0PdNA8LSyc+B7fECpwuZttGE4Vdm7biUmPcBqN4JRNmqJwuU7RePhh00YcfFaOSl/Dlmy96BNmrmjiCokzau2yTHVAXPs6xqW6s0aqscjV97vGvEXytwrmqwYZuP0ImQQmhSnAsAU78bExtxMRGZPklEIZEPuiXDeZ+FuUEwK/j6osg==
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=dY207gADGizbd48V0aJAPJiBvnNS+Km6W/S9cpj2cbM=; b=NDMUSkf3VyvUhsULU2uSoyrGUuvOSJAy471ODyxc+Y4eKJCkPZqMDJmtvWzdOiSuzWuYBcCV8W3PbOZlG6cD3+KoHmgQLgsQyQ3k960PaXZ/NLkgcDyCwkZngyxvd7UmwfPfJhALnSYYmmVAoShAtcfqfUuGQ/1CuzDv1Xjm+qur5GBHHzyljdXc0x2xYsrZWG3lyCxJ01ECgtXNv5wwkCdOI201BL6mc2rfy90eY+oEwQx+ZhhQkYSfcuQ/QGh9s27pz7xtQpfJXtdpd5kdBCpqZBkRGwIIRE6V5WJlqoV20xaQG8EqTamVGo6N5xP2vyZOAqeI6KAQRqHwIXLBpQ==
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 BYAPR05MB4231.namprd05.prod.outlook.com (52.135.194.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.14; Thu, 17 Oct 2019 08:08:12 +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 08:08:12 +0000
From: Srihari Sangli <ssangli@juniper.net>
To: Robert Raszuk <robert@raszuk.net>, Srihari Sangli <ssangli=40juniper.net@dmarc.ietf.org>
CC: 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: [Idr] Can one Destination Address appear in both Tunnel Encap Attribute and in MP_REACH_NLRI ?
Thread-Index: AQHVhL8mkuVMKDZJs0OlvyicMVffvKde1rmA
Date: Thu, 17 Oct 2019 08:08:11 +0000
Message-ID: <0B48E5E7-3A1F-45C0-ACF9-B9A0FA323ED4@juniper.net>
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>
In-Reply-To: <CAOj+MMGqKj=zKbws92ni1fL2O-So=dbcW-mb02uRnQ+G55xm_w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-GB
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;
x-originating-ip: [116.197.184.10]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 2027527a-dcd8-401d-c276-08d752d927a7
x-ms-office365-filtering-ht: Tenant
x-ms-traffictypediagnostic: BYAPR05MB4231:
x-microsoft-antispam-prvs: <BYAPR05MB4231595DC7FB73088F039C13B96D0@BYAPR05MB4231.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 01930B2BA8
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(376002)(346002)(396003)(39860400002)(136003)(189003)(199004)(129404003)(446003)(14444005)(486006)(33656002)(5660300002)(256004)(7736002)(4744005)(11346002)(6116002)(3846002)(316002)(2616005)(476003)(2906002)(66066001)(36756003)(110136005)(54906003)(25786009)(186003)(86362001)(71190400001)(71200400001)(6246003)(229853002)(6436002)(26005)(4326008)(6486002)(14454004)(76116006)(91956017)(6506007)(478600001)(6306002)(76176011)(6512007)(54896002)(8936002)(9326002)(81166006)(81156014)(66446008)(64756008)(66556008)(66476007)(66946007)(8676002)(102836004)(99286004); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB4231; 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: EwJr3fZ5fqNuPYFFSRn4j/tvTxVTJ+p0KB3PcZxIyHnuDEIUCZUuH2tKS/Le5OkPBPXFJxYg6FNCVrpCHhy7PuPMO1lhSNJCWzfCwUIpLPGWEgzwL253jFIcZ00q3U0+sIta2rwSvSxuPFiXmQqZ5O8uOQPt9I2ni8HfhJqj0CWeog9Mk8Er8cUuXEDliLbrNuHnof4vVTj8Kfl/xKjgyUe5hLHtGilzxsCOyj1pYJXAurAeZcHYCHV8ErmghM0ALsajZibj+5+Dn48SmlVYp5tVg3+czIizbFvNwOQCve/iBybGL1udop5c8wWV+dpoNx/bRQz8YAl+3wauagYQMh5IUFjeX0Ej1rHzEexWUboy06YnB0MMpOKFq96xqVgcrymaR/oZ5DbK0/Rfw99vyIrQBY420cFzg5wthbMewh8=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_0B48E5E73A1F45C0ACF9B9A0FA323ED4junipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 2027527a-dcd8-401d-c276-08d752d927a7
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Oct 2019 08:08:12.1661 (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: +YvnpQx+glRuo3GDgRtAneBbbqgqh43Is4SkOFTEz/k1iFmZhUlRTzsQcqGHHy2Br6IPZiqhuUeRuHhnGy1aYg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB4231
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,1.0.8 definitions=2019-10-17_03:2019-10-17,2019-10-17 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 bulkscore=0 mlxscore=0 adultscore=0 mlxlogscore=777 priorityscore=1501 lowpriorityscore=0 spamscore=0 clxscore=1011 impostorscore=0 suspectscore=0 phishscore=0 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1908290000 definitions=main-1910170071
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/QXEZXuzk0TzDCFyJiapJw66lCDI>
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 08:08:19 -0000

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ā€¦