Re: [Idr] BGP routes with color, Question 1: How does route resolution work with your feature?

Natrajan Venkataraman <natv@juniper.net> Mon, 21 March 2022 18:41 UTC

Return-Path: <natv@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 D1F0D3A1AB3; Mon, 21 Mar 2022 11:41:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 header.b=QlkFDL7V; dkim=pass (1024-bit key) header.d=juniper.net header.b=PBifScJl
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 gjGyAoS8397u; Mon, 21 Mar 2022 11:41:24 -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 9243A3A14D3; Mon, 21 Mar 2022 11:41:24 -0700 (PDT)
Received: from pps.filterd (m0108157.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.1.2/8.16.1.2) with ESMTP id 22LFNT98000685; Mon, 21 Mar 2022 11:41:23 -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=x/i5jgHuhr1/dHd2mQFxjUS+8+VMGlnwemHNHVn5/HQ=; b=QlkFDL7Vr+iuGwCKgZ9LeX9bhUsHF8qvQBzlX/FGMhoxi2Ik7EAbpHKE+r9KDcgBvDKO VTplOyCK9FExSPI9LRaJYVXyuPtz2CQkmHWQ/bEc7Vxjp5SkAlL5n/fsujl+ccxfNeFU 5DGnGRkvL/gw3NuVT041Ta8TgQWFbR/tL4IxxWnUnguO0H6SymppOWV87wQ3zBFCRGAg +erNBJXVsBm+VIJJkzArN+h0TcsD+U+e3qR93OAsKIELIsbFPfxZr1HZT+O8HI0FWWhi XF3VFdDidp+rFuCx1rcXFxia6GzNrfs9XSWJ9JDkd5G2wYHssu7izY9SWanJIuhSjwxC iQ==
Received: from nam12-bn8-obe.outbound.protection.outlook.com (mail-bn8nam12lp2172.outbound.protection.outlook.com [104.47.55.172]) by mx0a-00273201.pphosted.com (PPS) with ESMTPS id 3exuyage90-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 21 Mar 2022 11:41:23 -0700
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=SdDE0XVOgGSFxrxUheQTAhEeBd3xwWPqF9zlMgqLGv2JwDsKXYmDMqph1kL+h4ZhYAXCMPx6ILJn0xIMvJM+iPMSU+klVZ5N6rfs44TBvQ6/EhCh/KUR4QKyeYGt1BlRI1ez1D6+H0TIcfYHxO121GxEZGQVNql9MxGW6Icrfi9pMLZOFJbRQIQCekQlPC2kGBDvI2wfb3Sc5V/hdTRDtI1VWPta9uM3M5jrrgeLT1V+X7FALk3WHcoSpz/BBDtIu3TlRVn2imbPw34dZ5jYo8IDVuOQCVaUF/XUuuTHja8jFASDk4JckYGyHk5ssBzL2mFD0fBXBc1CqUeK6N7GLQ==
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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=x/i5jgHuhr1/dHd2mQFxjUS+8+VMGlnwemHNHVn5/HQ=; b=kyLCRTXpWqu14Qtlf3Wczvkd1Hjdu4r1+zpu9p4L9V+qd6agcfc5mimHE7G6ptxVUtyCohxeVKAn778PCXwccoKq9lSwZUxsqLpG3qJj5aTa6USsvgIIYgP5PvH6vDQ67M2QY8enFM54KsDQrRz9uuzvvCzDwUsw6SXQGKnWxAMH1BDQuEZN8Uc2SkHzmtEnmllnaTYEeLyJg3EPJ2UwmA9VkaNNK+lnfie375ZPV9rFLbQYXRP9ALr6NzmIipDd1lRqNwYs4hhTsXgdktewKBPAVUGQbUb2kwhsq1WO6VBLm+YgrKQrz9py0gr29NQqGBI0sDbjgohDQC6OgA44dQ==
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
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=x/i5jgHuhr1/dHd2mQFxjUS+8+VMGlnwemHNHVn5/HQ=; b=PBifScJlE0p4o4m9PqMdpBZe7l5mC00FORyi1ybBSx0gMtdD8TeIXS1JfBo8fLfeBhKasGYc3lNyBfYcFT5sod/6o+tOEwn4NraQbYIQiQzhb1An9YtqqbggTIx5zKKA0w9lrLTETwRt332L7GzIPiZcsGraCmVyL7rVjqLfUQA=
Received: from BY3PR05MB8050.namprd05.prod.outlook.com (2603:10b6:a03:36c::17) by SN6PR05MB5949.namprd05.prod.outlook.com (2603:10b6:805:fe::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5102.15; Mon, 21 Mar 2022 18:41:20 +0000
Received: from BY3PR05MB8050.namprd05.prod.outlook.com ([fe80::90e6:c392:f05a:ba51]) by BY3PR05MB8050.namprd05.prod.outlook.com ([fe80::90e6:c392:f05a:ba51%5]) with mapi id 15.20.5102.008; Mon, 21 Mar 2022 18:41:19 +0000
From: Natrajan Venkataraman <natv@juniper.net>
To: "Dhananjaya Rao (dhrao)" <dhrao=40cisco.com@dmarc.ietf.org>, Jeffrey Haas <jhaas@pfrc.org>
CC: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] BGP routes with color, Question 1: How does route resolution work with your feature?
Thread-Index: AQHYO9UmbzahQEIgVkyNvmJqwZWRrqzJpxEAgAAqYoCAAAbXAIAATENM
Date: Mon, 21 Mar 2022 18:41:19 +0000
Message-ID: <BY3PR05MB8050AEB2BBD3FEA44575A044D9169@BY3PR05MB8050.namprd05.prod.outlook.com>
References: <20220218154223.GU15589@pfrc.org> <6EBC5D65-B529-4699-AD27-25337812EEF0@cisco.com> <20220319210606.GE4905@pfrc.org> <C0D43AE4-A25B-4AFD-B1B2-4D44C0387F59@cisco.com> <20220321130703.GR4905@pfrc.org> <524DAC47-AFDB-443D-8CCA-A7518461FE35@cisco.com>
In-Reply-To: <524DAC47-AFDB-443D-8CCA-A7518461FE35@cisco.com>
Accept-Language: en-IN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Enabled=True; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SiteId=bea78b3c-4cdb-4130-854a-1d193232e5f4; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SetDate=2022-03-21T18:04:28.6166364Z; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ContentBits=0; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Method=Standard
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b7af5284-a87d-4015-310d-08da0b6a63fe
x-ms-traffictypediagnostic: SN6PR05MB5949:EE_
x-ms-exchange-atpmessageproperties: SA|SL
x-microsoft-antispam-prvs: <SN6PR05MB59496194A2B7D06F4A8C4524D9169@SN6PR05MB5949.namprd05.prod.outlook.com>
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: BtJlchqEtNAyQLwvoYUT8B9FReQFqL59UJbEwqOphs7X8Oiui7JNxaAEaMknDh0MyCnKwlT+AuDFmPnyo16EpBIySSLwp2EvIwzFOeALYXScq4zJ3KX7uV+4Lh167wf6w7iqvkhBR8sGlYodWvMNYCNYQYcxlLfbNQ6bcfCB3nI5D5Qo7H5gidAEuzAQuvYKbx0MjDRkZ8oox96I4NRopqD43i3wPdagghMfNGNI8l1rNM1HUlXaqNnSUyWnAkfepaUboMR1ITjNXVR8EY8fr0lS9x3sCQZ6h3gRuGzdvYqS6eXHdW82BnIyx2a3M1lzxBC+ej2BGXRfwY2H3Wgg+bC62PNLdduZKLqHo2lbfhwv+7JYILybjnR1m/uFsCD18lWKdQyQrIaUEcl96Ct3k2EjZkAFmzAHl8nxhFOiZ+j3LI3Snf2g+U51Pf+qApXywx7o+EQc5RC4FessFRjwWscixxf/xUJi0Q+a0iLyyDqTRIpXEm3IurvpnRb8rMDjRo2ioavz914vLVKzAyf0wGP+DRVd73RBpNtPbfR/YdTi2IebRs7D+PNfhj1tjTP4gcpEXXyKSpe5/HpNUtJFobW2NK/Ngp4XCX6K6s4xdzI2QYJ3WsCu12Ko6SpmvrtmrwhCIFmdVbe9tRUSo70lWz3i28ZqEeEksdUYow17NgN8IU8e7mUPRRljJrfSaFcioYQDlC79qu3eJUnAFbuMdZ4O5KkxjhUA78peZpZTRp2m+lt7ptbzHSqcNxBfXCkNSNGYd3HX41UBpV+yBR4GHcVECx0rC6bJo+zRS6Sb7rQ=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BY3PR05MB8050.namprd05.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230001)(4636009)(366004)(91956017)(2906002)(83380400001)(76116006)(6506007)(71200400001)(66476007)(8676002)(66556008)(66446008)(64756008)(4326008)(53546011)(122000001)(7696005)(5660300002)(966005)(38070700005)(508600001)(66946007)(26005)(9326002)(33656002)(8936002)(52536014)(86362001)(38100700002)(55016003)(316002)(186003)(9686003)(110136005)(166002); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: kUCErINVofLdxKVFZa2A/cb8LoNMZ0At6ptFKIaygeTgyJMKgeWq52ylKnQD42PE4TVMjSKaHAQHGRKc9izGqy6Lpj/lPTIBavjV3iOnDDOyZNTmoZOFsZb91yiIGwxyWod485czYTyrMilE4YsB7A2akXIeYm23/kGYeWWZBKILyg8P6sl+kGb6yeH5e874qXWkC1B16O6KHmms07xOvYFS4IuTKxsYGBI/z3F/SopTqw4CxyiuKhpxvgIYk6Vudl+W4+6K9BjqNhr6LVuMKeBKgRPkAg0umIcQ7ZBQAe81c3Sp0D2jqrlyTTtqJF78fDrRr2NyFWsABkvdELn2QcKVHhIzUwauSsar+qtmLtDWYtOpVb0vbtG4bctxOiQyOlbYZcVw/mjUI0+EgotDKc0MJPve3Kg6GdzPOlVxL03B62QO0eVLRnxQjZbHLVfioMqwmsH+QobgX1FV6CGnY8Gj6PBYVqIhJsxi+ewjfSIyd/eDAp4bMq6pXYAGqLVDt5JnAHiRsa6h+eoh1rD6ebvMUScT8YVpKj7tJ57mhkdYpnT9ItdE8NJu6cYztTLilpeos9ClL0X0Tau0iZyxDLbuUd4ZafDjmyeV6Aj4QSy/YpgQIA4fujF0J2WaY9cLSz3VwtlJyRjQcc6vBq0JR2A8m5MECNmsXcvcp3b3qbBR0LiejrTwFcEQFlDxQSfIGQbnx9eeeycjHDknfG8RB1Az/98HE7ey+bOHajc6nAmDlxWWyEPZ8md2zjbmIHRKSdbZ0pbrHUUZMhWLtLWwlzWRvKhG3rfcTfoZrfWQxyk4JZbHiEqUPvIH3xOvAC94NOFDlKBeCGicO4yIFJfb9FvOIJmChBzBTrXMMdUClktY8u0ycBCW5egrTuhoANy+XA36wrzSmZGcSpnFRE22pwQ/8Ai7bpL3Us14s78LPit3Ix1Hk6mQVHOcmpS5s4/peyphyrOIXdiu/fg/Fi0dzFHcXLozsAAcDgPvW8gXoqIWErqD/EGHru3O2aVxjyrAhK6wm0T/Dibx+65aYaK0HLVOcBVc+naNNFrs8vGx8NyDpY1p86G+k5QwNqzEjntDom2j8ULbqv6D2UiQiKdptIVcAIRm9oahUF+cbtaCExTwzNY9dhPeffjXAXObwwRUaH5ff50wYArPmODIJZBuqLcx/UvoiIOVq0pJnCE4seTXk/DuIk6v40hrDJ8ZCReepGMQIjQUaiKLw3LdRJh4auxQZnbZgW/FTMQ4WW+F7JGbeYtLpq208DpnBhUIUmaV7jQxwDS9TnNtQK6kPKG+npMJ4tVmQb73ho8r/nXu3xjwOVPD0OeY2fUVX5r50Q8grUBov6bIT+Hr8BzQUcfacMcVRRa/bCu36ITisJ9ug802u2eOIW8UqhoHBfPG7ixvhkxzaiU5NwpGg0/1E+VOg4yMC/SYmNqLvqbWyxelv3LL/LLXaZ0jiicWCMmY3gLk
Content-Type: multipart/alternative; boundary="_000_BY3PR05MB8050AEB2BBD3FEA44575A044D9169BY3PR05MB8050namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BY3PR05MB8050.namprd05.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: b7af5284-a87d-4015-310d-08da0b6a63fe
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Mar 2022 18:41:19.7607 (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: 40cw3ZIStVYcuy7axd/uhki/Ht1O3aTMhoWA86tBWDZz7M5kiorwwcvTbe5nC+GkBZ0SIBL9O6zUZGctTIZE4A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR05MB5949
X-Proofpoint-GUID: KBStVohd81w6ARiMw6MlGk2FOaQhtD4a
X-Proofpoint-ORIG-GUID: KBStVohd81w6ARiMw6MlGk2FOaQhtD4a
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.850,Hydra:6.0.425,FMLib:17.11.64.514 definitions=2022-03-21_07,2022-03-21_01,2022-02-23_01
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 lowpriorityscore=0 suspectscore=0 clxscore=1011 malwarescore=0 phishscore=0 spamscore=0 adultscore=0 mlxlogscore=999 bulkscore=0 impostorscore=0 mlxscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2202240000 definitions=main-2203210118
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/gwy2jQlg2ZPWYFcSIx6_XRlJ6kY>
Subject: Re: [Idr] BGP routes with color, Question 1: How does route resolution work with your feature?
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: Mon, 21 Mar 2022 18:41:30 -0000

Hi Dhananjaya,

This is Nats (One of the co-authors of the BGP-CT draft). I have questions on the following (NV)

    > >     Can there be more than one LCM present on a BGP CAR route?  If so, how does
    > >     that interact with resolution?

    I don't believe this question received an answer?

DR>> My bad. There can only be a single LCM present on a BGP CAR route.

    > >     > BGP CAR route resolution follows the same recursive resolution model that has been used in IP routing and MPLS networks for the past 20+ years (E via N). The only difference is that the route and next-hop are color-aware - (E, C) and (N, C).
    >
    > >     It's important to note that a property of this historical recursive model
    > >     for existing technologies is that it is longest prefix match.
    >
    > DR## Yes, and CAR does not attempt to change it.
    > DR## However, it is also worth noting that for technologies such as MPLS transport used historically for VPNs and other services, the recursive resolution ultimately has been a match on the host route for the PE/ASBR that’s the BGP service route’s next-hop. There is no aggregation. So, this point to some extent appears academic.

    The motivation for the above points is to illustrate that service route
    resolution is not solely (E,C) as received as the NLRI key.  The resolution
    key is (E, effective color).

DR>> Okay.

NV>> From the above,

I see that having the LCM attribute alone in the CAR NLRI universally solves the problem of communicating the color across different border nodes and towards the ingress PE nodes. All receivers of CAR NLRI need to make this local decision as to use the NLRI Key fully or to throw away the color in the key and use the LCM attribute as it creates an ambiguity where the NLRI key may be the same or different from the Resolution key. Are there any strong reasons for having color in the NLRI against having LCM as a sole representation of color?

Regards,
-Nats-


From: Idr <idr-bounces@ietf.org> on behalf of Dhananjaya Rao (dhrao) <dhrao=40cisco.com@dmarc.ietf.org>
Date: Monday, March 21, 2022 at 6:32 AM
To: Jeffrey Haas <jhaas@pfrc.org>
Cc: idr@ietf.org <idr@ietf.org>
Subject: Re: [Idr] BGP routes with color, Question 1: How does route resolution work with your feature?
[External Email. Be cautious of content]


Jeff,

Please see inline (DR>>)

On 3/21/22, 6:37 PM, "Jeffrey Haas" <jhaas@pfrc.org> wrote:

    Dhananjaya,

    On Mon, Mar 21, 2022 at 10:35:22AM +0000, Dhananjaya Rao (dhrao) wrote:
    > On 3/20/22, 2:36 AM, "Jeffrey Haas" <jhaas@pfrc.org> wrote:
    > >     "via (E,C)".
    >
    > >     When a Local-Color-Mapping Extended Community is present on the BGP CAR
    > >     route, does this mean that this CAR route contributes to resolution as
    > >     (E,LCM) rather than (E,C) where C is the original color present in the NLRI
    > >     key?
    >
    > DR## As you phrased it, LCM color is used when the route is used for resolution. Just to restate, there is no rewrite of the BGP NLRI color as it traverses hops.

    Thanks.  The property I'm trying to ensure we're clear on is that the RIB
    key, (E,C) is not necessarily the resolution key (E, effective color).  The
    effective color will be the C from the NLRI unless an LCM is present.

DR>> Yes. Section 2.8 of the BGP CAR draft states this along with the rationale.

    > >     If so, does that mean that when LCM is in use, the original (E,C) is not
    > >     permitted to contribute to resolution?
    >
    > DR## I did not understand the meaning of this comment. Can you elaborate ?

    The detail I'm trying to confirm is that if a BGP Speaker implementing -CAR
    has received a BGP route (E,C) with LCM C1 that it contributes to resolution
    solely as (E,C1) and not (E,C).

DR>> Okay. Hope the above reference clarifies the behavior.

    > >     Can there be more than one LCM present on a BGP CAR route?  If so, how does
    > >     that interact with resolution?

    I don't believe this question received an answer?

DR>> My bad. There can only be a single LCM present on a BGP CAR route.

    > >     > BGP CAR route resolution follows the same recursive resolution model that has been used in IP routing and MPLS networks for the past 20+ years (E via N). The only difference is that the route and next-hop are color-aware - (E, C) and (N, C).
    >
    > >     It's important to note that a property of this historical recursive model
    > >     for existing technologies is that it is longest prefix match.
    >
    > DR## Yes, and CAR does not attempt to change it.
    > DR## However, it is also worth noting that for technologies such as MPLS transport used historically for VPNs and other services, the recursive resolution ultimately has been a match on the host route for the PE/ASBR that’s the BGP service route’s next-hop. There is no aggregation. So, this point to some extent appears academic.

    The motivation for the above points is to illustrate that service route
    resolution is not solely (E,C) as received as the NLRI key.  The resolution
    key is (E, effective color).

DR>> Okay.

    > >     For cases where the only CAR prefixes in the system are of host length,
    > >     fall-back schemes for color seem fairly clear.  You would search on (N,C1)
    > >     and (N,C2) is permitted to match.
    > >
    > >     When the CAR routes are not host routes and there are perhaps overlapping
    > >     color fallback intents, e.g. if not found in C1 try C2, how should the
    > >     lookup functionally occur?  Would this be a longest prefix match vs. N for
    > >     C1 first and then fallback to a longest prefix match vs. N for C2?
    >
    > DR## That would be the functional behavior by default.
    > DR## I’m a bit unclear on whether you’re looking for anything specific in terms of behaviors or differences.

    The motivations for the two questions from the interim come from attempting
    to understand comparability between the two proposals.

    Thanks for helping to clarify this item.

    Once we have the missing answer for multiple LCM, I think we've closed the
    questions from the interim.  FWIW, Kaliraj indicates in -CT that it is a
    misconfiguration.  If the same holds for -CAR, that clarifies the intended
    behavior and perhaps suggests need for a section on the topic in each
    proposal's Error Handling section.

DR>> Ack, thanks for the perseverance.

Regards,
-Dhananjaya

    -- Jeff

_______________________________________________
Idr mailing list
Idr@ietf.org
https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/idr__;!!NEt6yMaO-gk!WY_ovfrLsfg2jcynx1JXcb7GKZ9PPEYNnY1F3ZJqc9V5P9d9wfyXSMIg4fMPVA$<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/idr__;!!NEt6yMaO-gk!WY_ovfrLsfg2jcynx1JXcb7GKZ9PPEYNnY1F3ZJqc9V5P9d9wfyXSMIg4fMPVA$>


Juniper Business Use Only