Re: [Idr] [draft-ietf-idr-segment-routing-te-policy] Error handling for Explicit NULL Label Policy Sub-TLV

"Kausik Majumdar (kmajumda)" <kmajumda@cisco.com> Mon, 08 July 2019 05:05 UTC

Return-Path: <kmajumda@cisco.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 99E2412010D; Sun, 7 Jul 2019 22:05:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.498
X-Spam-Level:
X-Spam-Status: No, score=-14.498 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=gCmHDVhe; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=SHaLxTMV
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 IapTabULPqJD; Sun, 7 Jul 2019 22:05:47 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D46C8120099; Sun, 7 Jul 2019 22:05:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=25360; q=dns/txt; s=iport; t=1562562346; x=1563771946; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=mczOaxJWvuYY4Wxty/YAA8Uv3uairaXgTuLjL3ZcLI4=; b=gCmHDVheAtp7vv2DkSz+XZKZNkVOfSnN3AsYpEa15KZHyuKzf2JUuZpZ WmsWNWJEDu+fWzCI9jVFj4jT0LEsi5fXXP8xaoj19B8vsmVhNMS/GXkQz VSOMuiq2mOn4npAU82CxvYIceqsyRoHxMEmYZUnlIiT7zb2eIthaeKb5V o=;
IronPort-PHdr: =?us-ascii?q?9a23=3AHeMYFBI8B7MRQou089mcpTVXNCE6p7X5OBIU4Z?= =?us-ascii?q?M7irVIN76u5InmIFeBvKd2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUg?= =?us-ascii?q?Mdz8AfngguGsmAXE7+Jfz3aiAzNM9DT1RiuXq8NBsdFQ=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AIAACpziJd/5RdJa1lGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBUwUBAQEBCwGBFC8pJwNqVSAECyiEHINHA4RSiXaCW5dGgS6?= =?us-ascii?q?BJANUCQEBAQwBASUIAgEBhEACF4IXIzQJDgEDAQEEAQECAQVtijcMhUoBAQE?= =?us-ascii?q?EEhEKEwEBNwEPAgEIEQQBASQEAwICAjAUCQgCBAENBQgagwGBHU0DHQECDJs?= =?us-ascii?q?0AoE4iGBxgTKCeQEBBYR6GIISAwaBNAGLXheBQD+BEAFGgkw+gmEBAQIBgWA?= =?us-ascii?q?VDwcJglQygiaOcIR9lmkJAoIXhlaNSYIshyGOMY0wh0CPfQIEAgQFAg4BAQW?= =?us-ascii?q?BUDg3gSFwFYMngkE3bwEHgkOFFIU/cgEBgSeNUQEB?=
X-IronPort-AV: E=Sophos;i="5.63,465,1557187200"; d="scan'208,217";a="588924891"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 08 Jul 2019 05:05:45 +0000
Received: from XCH-RCD-007.cisco.com (xch-rcd-007.cisco.com [173.37.102.17]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id x6855jwP003919 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 8 Jul 2019 05:05:45 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-RCD-007.cisco.com (173.37.102.17) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 8 Jul 2019 00:05:44 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 8 Jul 2019 00:05:43 -0500
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 8 Jul 2019 01:05:43 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=mczOaxJWvuYY4Wxty/YAA8Uv3uairaXgTuLjL3ZcLI4=; b=SHaLxTMVXZFdw78MGcT4cCGUD37uAfLa8Uqw7g3lX6jVy4N/oPHkgWX8vHJUMV6In20D0vXaVOwMs4iycHvHkW0JRZLOvpmPeYXKsHjuCEi1X9aYiDxi+3KCJeaQs+uv2c3mbtCFSqESseG3O8NB+Enp7XCRoU9OctcQVAA05BU=
Received: from BYAPR11MB3544.namprd11.prod.outlook.com (20.178.206.17) by BYAPR11MB3302.namprd11.prod.outlook.com (20.177.185.91) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2052.17; Mon, 8 Jul 2019 05:05:41 +0000
Received: from BYAPR11MB3544.namprd11.prod.outlook.com ([fe80::16c:6e5d:15ef:b7a7]) by BYAPR11MB3544.namprd11.prod.outlook.com ([fe80::16c:6e5d:15ef:b7a7%6]) with mapi id 15.20.2052.020; Mon, 8 Jul 2019 05:05:41 +0000
From: "Kausik Majumdar (kmajumda)" <kmajumda@cisco.com>
To: "Ketan Talaulikar (ketant)" <ketant@cisco.com>, Przemyslaw Krol <pkrol@google.com>, Manoharan Sundaramoorthy <manoharan@arista.com>
CC: Paul Mattes <pamattes@microsoft.com>, "draft-ietf-idr-segment-routing-te-policy@ietf.org" <draft-ietf-idr-segment-routing-te-policy@ietf.org>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [draft-ietf-idr-segment-routing-te-policy] Error handling for Explicit NULL Label Policy Sub-TLV
Thread-Index: AQHVMZs42SxhAEYJek650hZrRQQyaKbAMa6A
Date: Mon, 8 Jul 2019 05:05:41 +0000
Message-ID: <BYAPR11MB3544555FC236B836B4D6D0BED0F60@BYAPR11MB3544.namprd11.prod.outlook.com>
References: <CAE+itjfH=EHN=Fm-in0v0r5r1wHKOz+Kd0mGBJfm6cLjVKNTNg@mail.gmail.com> <CACH2EkVGD3ZX3ZdX9dS9tPoPrDtqTvHnQD4VezrOED3fmVj4jA@mail.gmail.com> <CA+W7bqevhivu0KBbjwcRirxpL2HyZ0Hc7hfapOzisQvqf0jK6w@mail.gmail.com> <CACH2EkXwAbx-1ZZFbxBr=TN2j07WpAG2Krsq8ojhrKANdOZ-dQ@mail.gmail.com> <DM5PR11MB2027AA578DF4B998E671CEB9C1FB0@DM5PR11MB2027.namprd11.prod.outlook.com>
In-Reply-To: <DM5PR11MB2027AA578DF4B998E671CEB9C1FB0@DM5PR11MB2027.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=kmajumda@cisco.com;
x-originating-ip: [2001:420:c0c8:1005::a6]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d803379c-c097-4d25-7727-08d70361ed04
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BYAPR11MB3302;
x-ms-traffictypediagnostic: BYAPR11MB3302:
x-ms-exchange-purlcount: 4
x-microsoft-antispam-prvs: <BYAPR11MB330285B2D3047AB1FFFAE272D0F60@BYAPR11MB3302.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 00922518D8
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(396003)(376002)(346002)(39860400002)(366004)(199004)(189003)(478600001)(229853002)(316002)(53936002)(236005)(52536014)(9686003)(8676002)(102836004)(790700001)(6116002)(8936002)(46003)(45080400002)(966005)(54896002)(81166006)(6306002)(73956011)(55016002)(66446008)(64756008)(66556008)(66476007)(81156014)(76116006)(66946007)(6436002)(186003)(5660300002)(86362001)(2906002)(33656002)(68736007)(6246003)(14454004)(486006)(76176011)(71200400001)(6506007)(53546011)(71190400001)(561944003)(99286004)(7696005)(25786009)(74316002)(11346002)(446003)(606006)(4326008)(14444005)(110136005)(476003)(256004)(54906003)(7736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3302; H:BYAPR11MB3544.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 7KLCXxmgGvQ3p6MbDrHYuTtRrQ/OvSVkV+g6ViP4Nlbqcxzch7jY+QHn5/e1yG/D/dC9ZSfSP0JX/G2NkzLE3Ejyu1XqL8aFrZikeF4p25P4u4w5sjzQHbSUYN1K+HK0FPbleieZLmkh74ZzWmV1tTfmjLsfYHQsuxvqJa/PbeHZoyEAJ+n9HHrwYmarXipC0jZ7iThUpaigZySNHdRNLLXFk3jOiHFayEAChhNsL/pFIPDqb3RcLVbsj8F3biCdccGL+OBMSNPOQ1CuFntvmOvY7QhLvFZt0qNQebBV6Xj3EN8bo4leIX/ZxtZCBmSAQhs+3R2mIXz/EAVaXB0rQC+bSLpxcivGTKjodCn5N3mj5Qa/ZGGzVbxDU8oTQ0+N8TwnOzdX+Oi9OwEsajdrxbJ9Ex47aDyp7Ju2UbPQk6w=
Content-Type: multipart/alternative; boundary="_000_BYAPR11MB3544555FC236B836B4D6D0BED0F60BYAPR11MB3544namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d803379c-c097-4d25-7727-08d70361ed04
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Jul 2019 05:05:41.7139 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: kmajumda@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3302
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.17, xch-rcd-007.cisco.com
X-Outbound-Node: rcdn-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Fh7uTLtBg5_tcsCo-_tK7phVM6I>
Subject: Re: [Idr] [draft-ietf-idr-segment-routing-te-policy] Error handling for Explicit NULL Label Policy Sub-TLV
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, 08 Jul 2019 05:05:49 -0000

Hi Mano, PK,

The SR-TE Policy version 07 draft updated to capture the Error handling for Explicit NULL Label Policy Sub-TLV.

Please let us know if you have any other suggestions/improvement in the draft.

Thanks,
Kausik

From: Idr <idr-bounces@ietf.org> On Behalf Of Ketan Talaulikar (ketant)
Sent: Wednesday, July 3, 2019 5:29 AM
To: Przemyslaw Krol <pkrol@google.com>om>; Manoharan Sundaramoorthy <manoharan@arista.com>
Cc: Paul Mattes <pamattes@microsoft.com>om>; draft-ietf-idr-segment-routing-te-policy@ietf.org; idr@ietf.org
Subject: Re: [Idr] [draft-ietf-idr-segment-routing-te-policy] Error handling for Explicit NULL Label Policy Sub-TLV

Hi Mano/PK,

I also agree with your proposal for (1).

Regarding (2), I also agree that it is better to treat the values 0 and >  4 as reserved and if these values are used then the headend can ignore the TLV (which would actually be falling back to local config, if any).

I would request the authors to please consider updating the draft with the same if they agree.

Thanks,
Ketan

From: Przemyslaw Krol <pkrol@google.com<mailto:pkrol@google.com>>
Sent: 18 May 2019 07:29
To: Manoharan Sundaramoorthy <manoharan@arista.com<mailto:manoharan@arista.com>>
Cc: Nandan Saha <nandan@arista.com<mailto:nandan@arista.com>>; draft-ietf-idr-segment-routing-te-policy@ietf.org<mailto:draft-ietf-idr-segment-routing-te-policy@ietf.org>; Ketan Talaulikar (ketant) <ketant@cisco.com<mailto:ketant@cisco.com>>; Paul Mattes <pamattes@microsoft.com<mailto:pamattes@microsoft.com>>; idr@ietf.org<mailto:idr@ietf.org>
Subject: Re: [draft-ietf-idr-segment-routing-te-policy] Error handling for Explicit NULL Label Policy Sub-TLV

Hi Mano,

Oh, I see. Thanks for clarification and apologies for my irrelevant comment then.
FWIW, I support your proposal to consider these values as reserved and fallback to local poli..., erm, behavior defined by config :-)

pk



On Fri, May 17, 2019, 17:09 Manoharan Sundaramoorthy <manoharan@arista.com<mailto:manoharan@arista.com>> wrote:
Hi Pk,

In 2(b) we meant, "For values 0 and 5-255, treat as if the Sub-TLV was not received and take default ENLP action that is configured locally" (or) "if these values are to be treated as illegal, then do TAW".

Thanks,
Mano

On Fri, May 17, 2019 at 11:20 PM Przemyslaw Krol <pkrol@google.com<mailto:pkrol@google.com>> wrote:
Hi Nandan,

I personally agree with your proposal for handling multiple ENLP sub-TLV (1). It's clear and consistent with other similar cases

In terms of ENLP = 0 || >=5 (2), my concern regarding 2b (fallback to static) is that there may be multiple instances of BGP policy (different advertisers) with the same or lower preference and valid ENLP values. Failing back to static would basically skip those BGP policies and "bypass" policy selection. I suspect it's undesirable. For this reason, treating it as reserved (2a) sounds to me like a better option. Unless you really meant ignoring offending policy and moving to the next one (which can be static or BGP, depending on the selection algo), but regardless, 2a) seems safer and less disruptive in the future (if/when we need ENLP >=5 ).


thanks,
pk

On Thu, May 16, 2019 at 12:42 AM Nandan Saha <nandan@arista.com<mailto:nandan@arista.com>> wrote:
Hi folks,
 There error handling for the ENLP sub-TLV isn't defined in
draft-ietf-idr-segment-routing-te-policy-05 [1].

There are 2 things that need to be clarified:-

1. The behavior when ENLP sub-TLV occurs more than once:
  For this, my preference is to add text like we have for policy
priority sub-TLV [2] (and some other sub-TLVs), mandating only one
occurrence and treat-as-withdraw when present more than once.

2. Behavior when ENLP value is either 0 or >= 5.
  The only meaningful/legal values defined now are 1-4. My preference is to
2a: mark other values as reserved for future use. (We could mark them
illegal but that'll rule out trying to extended them if ever needed)
and
2.b: Upon receipt ENLP = 0 || >=5 the headend call fall back to local
policy. (If we go down the route of marking 0 || >= 5 as illegal, we
can do TAW)

Please let me know what you think, and if this seems reasonable.

[1] - https://tools.ietf.org/html/draft-ietf-idr-segment-routing-te-policy-05#section-2.4.4
[2] - https://tools.ietf.org/html/draft-ietf-idr-segment-routing-te-policy-05#section-2.4.5

Thanks,
Nandan


--
Przemyslaw "PK" Krol |
 Strategic Network Engineer
ing | pkrol@google.com<mailto:pkrol@google.com>


--
Thanks,
Manoharan