Re: [Idr] locator length : draft-li-idr-flowspec-srv6

Huaimo Chen <huaimo.chen@futurewei.com> Mon, 15 March 2021 15:00 UTC

Return-Path: <huaimo.chen@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 3BE103A1376 for <idr@ietfa.amsl.com>; Mon, 15 Mar 2021 08:00:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level:
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H2=-0.001, T_REMOTE_IMAGE=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=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 PHo11Ocy18Bd for <idr@ietfa.amsl.com>; Mon, 15 Mar 2021 08:00:34 -0700 (PDT)
Received: from NAM10-DM6-obe.outbound.protection.outlook.com (mail-dm6nam10on2122.outbound.protection.outlook.com [40.107.93.122]) (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 6DF383A137A for <idr@ietf.org>; Mon, 15 Mar 2021 08:00:34 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ANU9oflz7h4aLmWree2K42vLhRuO0Xw69S1gUTeStBrUHUDHZ4iNag3jL3MLVC+fbsHLUKVaqqzalL4jaKu5kVGIRu4uvXQcyg/DByYVXJktWEmbuS6sRd2AcuZRiuQVl7zI3UprZzwHHHCy6iBN3DJtBcqjVGIJ9yuSnAGkQI4Vg8OKBMp0/bdhJ9l9Luhi+0X382iihR99gDcnOO0Q2qGnOx5gGSFsPP/sEQzxgkuPYnP69D7ky0hvpr45uyCK/wgdzG1+54KqNZ+mmLjrfU+g2JAjhCnAMss7tx1R8YICeE/Tu8xyUczyfaPoFJehJoUFTFW/0rooevInbtQLMw==
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=dIR7fN8VRjplnRy82nhmSYnAhm20Osc/C80kw1m9sgg=; b=Z3+G2G+GWFXk6LenyfU3K2WlCtCq+zmrOU5nAF5Acxr/waRLDSwQ5PE654JLIsmE5rZpH7mi1otKdmnYw5oGMfCWc4y0p3x+9LiFNwJuOubYcrLdZrmkGqVKu9dQIGQlTW3fyJEiZO86BpZoWhdmilzgzJ4/zdTuDwk+1U6BZ7S37d6D8IF0I4dEH50QSzG0DUzYCy5Xh+D4MaME2eudNKDSePIwINYGfRzUsoC2lPIEMZNLrD98B0/QbPh+Lg1ChoVK0OurTXbt2Dn3wwlQxRSM3X9sDDTfgMb19IiXVsBRllxo3h+mmHUYYOsg95l5IhtuyFWAqBLEXiqTdUcciw==
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=dIR7fN8VRjplnRy82nhmSYnAhm20Osc/C80kw1m9sgg=; b=fLZL9BgYT/X0pvZgL19ibb+eHAUewsENY/+rgDAkpQ1fcd3xg2ULAUb9OrgQ/QSFPw8fRQZfV/Fh0nrRiJafwSkcIsQY1vcfbre1rOhEUIBDrgAKK/pkHbf7jQu7IEjsRHoMLaXprQdee8vJB/tm0kBGuMbLcKSynSLknAW4UDY=
Received: from MN2PR13MB4087.namprd13.prod.outlook.com (2603:10b6:208:263::16) by BLAPR13MB4739.namprd13.prod.outlook.com (2603:10b6:208:306::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3955.11; Mon, 15 Mar 2021 15:00:30 +0000
Received: from MN2PR13MB4087.namprd13.prod.outlook.com ([fe80::8cbf:200a:c112:a4b3]) by MN2PR13MB4087.namprd13.prod.outlook.com ([fe80::8cbf:200a:c112:a4b3%9]) with mapi id 15.20.3955.013; Mon, 15 Mar 2021 15:00:30 +0000
From: Huaimo Chen <huaimo.chen@futurewei.com>
To: Gyan Mishra <hayabusagsm@gmail.com>, "Joel M. Halpern" <jmh@joelhalpern.com>
CC: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] locator length : draft-li-idr-flowspec-srv6
Thread-Index: AQHXF02tikGQcIMfGU6yjuwVAdoH0KqAcZQAgAAdKIaAAAH1gIAAN6eBgAAFuYCAAKdLgIADswGg
Date: Mon, 15 Mar 2021 15:00:30 +0000
Message-ID: <MN2PR13MB408793C3C9D5398C13BA0DDAF26C9@MN2PR13MB4087.namprd13.prod.outlook.com>
References: <MN2PR13MB40876899246382264C393D06F26F9@MN2PR13MB4087.namprd13.prod.outlook.com> <89430d8e-58c1-7854-27a5-b01a4cf9c43f@joelhalpern.com> <MN2PR13MB4087266ED6ECE72F5F281E86F26F9@MN2PR13MB4087.namprd13.prod.outlook.com> <41feb923-eeba-d7db-a048-1b335bf8f92b@joelhalpern.com> <MN2PR13MB40874FC93A03CCDE2A012ECBF26F9@MN2PR13MB4087.namprd13.prod.outlook.com> <ad81e08a-09ab-ef9a-3295-ab3cf58b740d@joelhalpern.com>, <CABNhwV3PR_u2jG6Eo2uRwK0XRSemZJ006RdeuGG6_jyJnaZoAg@mail.gmail.com>
In-Reply-To: <CABNhwV3PR_u2jG6Eo2uRwK0XRSemZJ006RdeuGG6_jyJnaZoAg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=futurewei.com;
x-originating-ip: [2601:199:4300:8e5a:849d:536b:3f7d:962a]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f0b99ccf-b760-4144-024c-08d8e7c3136f
x-ms-traffictypediagnostic: BLAPR13MB4739:
x-microsoft-antispam-prvs: <BLAPR13MB4739C42ACB02393D9496B940F26C9@BLAPR13MB4739.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7219;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: pPCJR56XXaNiyjIPlxzuM10bmfy486ZdDVHUWqVAtUyqWXUYg02I8fWE5ioRyfbC+FahpSzbYCpSkw9du+BibKTtjyDrETQFLkqKLIQR4KRJSU2Wjtzc0k+Cda9erqpK3G9IEOhR6ZSpkugY87GPLtrlDsFtnZWn92c9940OsIBxBxXUjfkixetephanp9Z/ve2eUgj2QArYuiZkfA1txYGoqwsVxcWGcLMm3EEY1bPCFK9QZ4mo6KtBNe2Ut4XZ4oB77Td+8uTJIrq0zeUDI2ePWsqYzbR+EoXtLPben2R5Krx7qTjEJxr7+eZlX5EzZnhq4ciHQPjzke4pIOECcOdNyF1wMqx4ZdWnHGCpZ5TgVhP1OVNI3Ihzv5voXKUAW4p+a3Asf71UMp0WjWu6pu9uyualvEnBRDEdpAbnSk6VsXzujfZk3It9wOEG1y8sgFYFx0omMvX9y//pd78prhvXXcgT/ST1Iw30nKRCWkMXNhT6NnMe/lX4GkFqI9enTESSVG3dgTgr//bRpaVjR1wI7SFSoCMZu9xZX+Yfb0YdQ2w00gqP8cQb/RBECpSW85dARd6wSMdM/EgAVp6N8NrCyyE4T5RJXsvXbAk6kqHbpyPHr/kT+lf8MQQHVlelgaiTtsagkVP8+JH6JQunng==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MN2PR13MB4087.namprd13.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(376002)(136003)(396003)(366004)(39840400004)(346002)(6506007)(9686003)(66446008)(66476007)(76116006)(478600001)(83380400001)(53546011)(55016002)(66946007)(66556008)(64756008)(33656002)(186003)(52536014)(5660300002)(966005)(86362001)(7696005)(4326008)(316002)(44832011)(71200400001)(19627405001)(2906002)(8936002)(110136005)(166002)(8676002); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: =?Windows-1252?Q?W6ABjbpNr2T8oTkypqKhJeG27C5zZlCXFnpL4b4Ptg96jCKvI0S1N2ap?= =?Windows-1252?Q?44hcLMxGRc74Q3ZDG+d826+03ShseYtUbdmsEfBjHfO0p3YZaptg80vZ?= =?Windows-1252?Q?L0McxBuMx94KvDmfdYY9WBlTQZhlhv9slFuQyEVN+7KTRl9eA8z7xXl5?= =?Windows-1252?Q?mbglXw0Bv8wKgsYK+LfLYiQIbtyMYad/JchsyreuKYTOAJ9JvlHIodHz?= =?Windows-1252?Q?d7Hqthg2qsKZk4AmQRXuhPUtS5tzi/YDivuOU8uOOvEcGbLU/sgDPQg0?= =?Windows-1252?Q?OHIkGcNCh1XSTbJmeXYPPg7KBQyBRNcEHFqBIhJQYdtacL+9FZoI94jW?= =?Windows-1252?Q?TVU2HaVioIw/Fc7fw0WZDLv9I6AZ4SuDobq+TwFKnVyYA33/vU5gmrue?= =?Windows-1252?Q?d9ZcOktBjVVdYt7IaShi2vE0JNhL31KYJyWMYMH1QxaY3bEJvry/Qqco?= =?Windows-1252?Q?FrWoHs1M8pTX1lDi+Y3DAS1e6ZQQqkIa3/LTYC/M9jfarh5g3yXrYZzp?= =?Windows-1252?Q?SLyNtVAyVtNSzi63tpXfvgBgis/LBUTuBL5Q+59nuYtn9GquKNKWjJmg?= =?Windows-1252?Q?/pvqlS2NCdXbo3l+vJowvvdZPv16JpL96vYGBmGGcnwtPwi4xhZO2yPg?= =?Windows-1252?Q?l9u53XZWkUZ4MuMSVOt8PiFf1DMEh+/uXv7e1EYMfKyycEmJ19f8qM4q?= =?Windows-1252?Q?3Ml/lnNdJ06SlKw4MDEQey2518SPPgQ/GBRA1Nxq7q/nOl66cWW2/a5Y?= =?Windows-1252?Q?g8d0Ahw7lASH5dLTtparwGWFC7DvM/3nsmCUyMlzgH4By35XbkbqfMux?= =?Windows-1252?Q?ChvFZEY9GVLKlX+mkthQhyU++yS7eLUOmA0Uno4oIW80FrUQtExDR31C?= =?Windows-1252?Q?73ksr1hs+hEDeCU4ro0j/pzTPFxpat/w6wIM8tSgqkUzCKfi0lmjVzKm?= =?Windows-1252?Q?lybt5dfUO/5u4aFR/XPrvbJ795Vz6qw79r5kRLkzzapB3rkBw3fNnSdz?= =?Windows-1252?Q?3pctdVf6PehIzWIHFcz/IKbMczJ4v/VyzyfA3pYjgy+w0H+L/SXQK1R5?= =?Windows-1252?Q?ZbhU8NzcHnRLTfK3uqDK3Lp46FJvzLu4TfqQ7UPOCezD4h/EiD2gTAQI?= =?Windows-1252?Q?3Brxh/rZzxbvT0SfeTrzcDqvsGCT3Z3uPS++gHcI90agnWeMWKKlXPP8?= =?Windows-1252?Q?XNwFj4N9SvATypMG/fSq1azNZ3UcVg96np+ipdUtatloPsm9vlwPTLt9?= =?Windows-1252?Q?5Dnfzid4SjrotkQa2tPdbsC0jpe1AssBpcluJQxZcJGXfBqiHPdiFg7C?= =?Windows-1252?Q?Rqks0YZohHhtuciFcVDBEJOexEVRNIVnoNqt7oX3wMv87+TWEoJaKdnq?= =?Windows-1252?Q?faFLRjYEbbtWIVE/w5mFhKNalbSw8e2VKAlOxJCtnV/bubpXhehw+oEb?= =?Windows-1252?Q?uh5X1aZQ8l4unlMLPf1ev+nWERnrfizR4xnN3Z288hUJ/4e2fOtPNdSO?= =?Windows-1252?Q?fj0TYAFC?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR13MB408793C3C9D5398C13BA0DDAF26C9MN2PR13MB4087namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MN2PR13MB4087.namprd13.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f0b99ccf-b760-4144-024c-08d8e7c3136f
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Mar 2021 15:00:30.1485 (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: +/ZJdAuk9gXOuUpdOl1oo9qFf68653BoeBVLjE2tZebsJkU84058vAUNUIfeX6Dwoa3bGEA47GuotJMs3jvwIA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLAPR13MB4739
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/BbFbUX_SHwfSdCCxH07bYJ8u8a0>
Subject: Re: [Idr] locator length : draft-li-idr-flowspec-srv6
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, 15 Mar 2021 15:00:37 -0000

Hi Gyan,

    Thank you very much for your comments.

    RFC 8956 defines (Type 13) Flow Label component containing a list of
{numeric_op, value} pairs that are used to match the 20-bit Flow Label.
The operations on the label can be lt (less than) and gt (greater than).

    As you mentioned in your comments, MPLS VPN labels are encoded into
the func/arg of SRv6 SID. In this case, it seems that the operations
lt and gt on func/arg are the operations on label. Applying operations
lt and gt on func/arg (i.e., label) makes sense.

Best Regards,
Huaimo

________________________________
From: Gyan Mishra <hayabusagsm@gmail.com>
Sent: Saturday, March 13, 2021 1:27 AM
To: Joel M. Halpern <jmh@joelhalpern.com>
Cc: Huaimo Chen <huaimo.chen@futurewei.com>om>; idr@ietf.org <idr@ietf.org>
Subject: Re: [Idr] locator length : draft-li-idr-flowspec-srv6

Huaimo

With SRv6 BGP Service overlay the egress PE signals the SRv6 Service SID in SRv6 service TLV encoded in BGP prefix SID attribute with BGP overlay service route for SRv6-BE /no SRH or egress PE colors overlay service route with BGP color community for SRv6-TE w/ SRH.  The SRv6 source node encapsulates the PE-CE customer payload in outer “MPLS topmost transport label like” IPv6 header where the destination address is the SRv6 Service SID provided by the egress PE.

The SRv6 L2 L3 VPN Services TLV is encoded in the BGP prefix SID attribute identical to MPLS VPN service label and thus the VPN label is now encoded into the func/arg SRv6 SID signaled by the egress PE and is fixed throughout the closed SR domain.

SRv6 BGP Service overlay

https://tools.ietf.org/html/draft-ietf-bess-srv6-services-05<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-bess-srv6-services-05&data=04%7C01%7Chuaimo.chen%40futurewei.com%7Cf35805d2e8784e5a795108d8e5e9251a%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637512136823894640%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=cIFl1GwBr%2FkLm7j%2BI5XR8CuCwPkhcZEzsK8B8S8291Q%3D&reserved=0>

As SRv6 is reusing the IPv6 data plane with same L3 VPN overlay RFC 4364, I don’t think any of the processes would change to carry BGP flow spec RFC 8955, as the BGP vpn overlay layer remains unchanged.

We are just swapping the underlay change from MPLS to IPv6 data plane.


Kind Regards

Gyan

On Fri, Mar 12, 2021 at 3:29 PM Joel M. Halpern <jmh@joelhalpern.com<mailto:jmh@joelhalpern.com>> wrote:
I have to disagree with your basic premise.  At least for LOC and FUNC
bits, less than and greater than are NOT meaningful comparisons.

Even for ARG bits, the only defined usage for the bits is such that
comparisons other than equal to / not equal to are meaningless.

Yours,
Joel

On 3/12/2021 3:19 PM, Huaimo Chen wrote:
> Hi Joel,
>
>      Thanks much for your further comment.
>
>      It seems that using loc, func and args in SID is simpler than using
> address prefix of SID for SRv6 flow specification. For matching/filtering
> on an IP destination address prefix, it seems that there is just bitwise
> pattern matching. For matching/filtering on a SID (loc, func and args in
> SID),
> there are a few operators such as eq, lt and gt (and combinations of them).
>
>      For flow specification(s) to match a range of functions such as
> from function value F1 to F1+1, to F1+n (where n > 1) in SID,
> using IP address prefix seems need (n+1) flow specifications, each of
> which is for one function value and would have two (type 1) components:
> one component for matching the locator and the other for matching the
> function value. Using loc and func in SID needs just one flow specification
> having one (type TBD) component with three <op, value> pairs. The first pair
> is for matching the locator and the other two for the range.
>
> Best Regards,
> Huaimo
>
> ------------------------------------------------------------------------
> *From:* Joel Halpern Direct <jmh.direct@joelhalpern.com<mailto:jmh.direct@joelhalpern.com>>
> *Sent:* Friday, March 12, 2021 11:49 AM
> *To:* Huaimo Chen <huaimo.chen@futurewei.com<mailto:huaimo.chen@futurewei.com>>
> *Cc:* idr@ietf.org<mailto:idr@ietf.org> <idr@ietf.org<mailto:idr@ietf.org>>; Lizhenbin <lizhenbin@huawei.com<mailto:lizhenbin@huawei.com>>
> *Subject:* Re: locator length : draft-li-idr-flowspec-srv6
> Given that you have to check loc before func and check loc and func
> before arg, it would seem simpler to just use an address prefix.  Gets
> around all of the knowledge problems.
>
> Note that a UI for creating flowspec filters can allow the user to
> specify it in all sorts of ways.  that does not mean we need to put all
> of them in the protocol when they are equivalent.
>
> Yours,
> Joel
>
> On 3/12/2021 11:44 AM, Huaimo Chen wrote:
>> Hi Joel,
>>
>>      Thanks much for your further comment.
>>
>>      Just checking the FUNC bits should be limited. We will add some
>> text to state that in order to check the FUNC bits, the LOC needs to
>> be examined and matched first.
>>
>> Best Regards,
>> Huaimo
>>
>> ------------------------------------------------------------------------
>> *From:* Joel Halpern Direct <jmh.direct@joelhalpern.com<mailto:jmh.direct@joelhalpern.com>>
>> *Sent:* Friday, March 12, 2021 9:58 AM
>> *To:* Huaimo Chen <huaimo.chen@futurewei.com<mailto:huaimo.chen@futurewei.com>>; Joel M. Halpern
>> <jmh@joelhalpern.com<mailto:jmh@joelhalpern.com>>
>> *Cc:* idr@ietf.org<mailto:idr@ietf.org> <idr@ietf.org<mailto:idr@ietf.org>>; Lizhenbin <lizhenbin@huawei.com<mailto:lizhenbin@huawei.com>>
>> *Subject:* Re: locator length : draft-li-idr-flowspec-srv6
>> An operator can assign B::/48 and C::?46  for Locators.  Sure, it would
>> usually be a single prefix with a single length.  But that is not required.
>>
>> When one is examining the LOC, sure, you can use the value length to
>> handle it.
>> But the way the mechanism is described, one could try to check just the
>> FUNC bits, without matching the LOC.
>> First, that has the problem of needing exogenous information about the
>> LOC length.
>>
>> And it is actually worse than that.  Testing the FUNC bits of the
>> destination field of an IP packet without checking the LOC bits is
>> actually meaningless.  You don't even know if the DA is an SRv6 SID.
>>
>> An yet further, there is no requirement that the encoding of the FUNC in
>> different SIDs uses the same value representation.  The standardized
>> values are for advertising in routing protocols, not for the packets.
>>
>> Net: I don't think having the field identification works.
>>
>> Yours,
>> Joel
>>
>> On 3/12/2021 9:51 AM, Huaimo Chen wrote:
>>> Hi Joel,
>>>
>>>      Thank you very much for your comment during the IETF 110.
>>>
>>>      Regarding to the lengths of locator(LOC)s and function(FUNCT)s in
>>> SIDs,
>>> RFC8986 says that the locator length, is flexible, and an operator is free
>>> to use the locator length of their choice. This seems indicating that the
>>> operator can select the length for the locator. After their selection, the
>>> the locator length is determined/fixed. This is illustrated by examples
>>> in RFC8986.
>>>
>>>      One example in the beginning of section 3.2 is as follows:
>>>         For example, a network operator may:
>>>            Assign block B::/48 to the SR domain
>>>            Assign a unique B:N::/64 block to each SRv6-enabled node in
>>> the domain.
>>> After this assignment, the length of the locators of the SIDs in the domain
>>> is 64 bits.
>>>
>>>      In the end of section 3.2, the text shows the Function fields of SIDs.
>>> The length of function(FUNCT)s is 16 bits.
>>>
>>>      When a SID is used in the domain, its locator length and function
>>> length
>>> should have been determined.
>>>
>>>      When an operator configures a SRv6 flow specification, involving
>>> a SID or a group of SIDs, s/he should have known the locator length and
>>> function length in the SID(s).
>>>
>>> Best Regards,
>>> Huaimo

_______________________________________________
Idr mailing list
Idr@ietf.org<mailto:Idr@ietf.org>
https://www.ietf.org/mailman/listinfo/idr<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fidr&data=04%7C01%7Chuaimo.chen%40futurewei.com%7Cf35805d2e8784e5a795108d8e5e9251a%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637512136823904595%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=308PkYLf8wfcS9h%2BK07PUSuNMZuD%2B%2F877Xxxbo4hSDk%3D&reserved=0>
--

[http://ss7.vzw.com/is/image/VerizonWireless/vz-logo-email]<https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.verizon.com%2F&data=04%7C01%7Chuaimo.chen%40futurewei.com%7Cf35805d2e8784e5a795108d8e5e9251a%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637512136823904595%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Gqfjp5KslpJZe%2FM1vfBPfXeX81XslNzamG5SHfrDogQ%3D&reserved=0>

Gyan Mishra

Network Solutions Architect

M 301 502-1347
13101 Columbia Pike
Silver Spring, MD