Re: [Pce] Implementation option of draft-ietf-pce-stateful-interdomain-01.txt

Dhruv Dhody <dhruv.ietf@gmail.com> Mon, 29 March 2021 14:05 UTC

Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 360123A155D for <pce@ietfa.amsl.com>; Mon, 29 Mar 2021 07:05:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, 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=gmail.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 c0WxsQjDTFux for <pce@ietfa.amsl.com>; Mon, 29 Mar 2021 07:04:58 -0700 (PDT)
Received: from mail-io1-xd30.google.com (mail-io1-xd30.google.com [IPv6:2607:f8b0:4864:20::d30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04DB73A155F for <pce@ietf.org>; Mon, 29 Mar 2021 07:04:57 -0700 (PDT)
Received: by mail-io1-xd30.google.com with SMTP id v26so12859545iox.11 for <pce@ietf.org>; Mon, 29 Mar 2021 07:04:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=uzpwhU81kY8IzIddi169WgSA3neLYn7k4AXKLClmcQo=; b=esv2DjGF0nlGCZN1webTm46yFWErAF6ogfsEn/uC0NGTo7JyTzMH9Ngk9psIpI5Giu ssh7ALRbJmR/4sXMO/pu6sOibx0Uh3Q1xV0dF2ue6IdMYJ5hDJRAC9Q8OaOQUaE700rI 455rr/44tmsvgA0Ort+F7s8sInfvkTzqBRp2Dqw7u/j5/iz+DlYaiLKuBDPfnqGSJ/3H GbHN4qQTUq04M6rZYEF1eew258yMvt5mUdcWhXoUa/h+/mX0xu6NcQdlJhpYwan8Y3sf Zqu0RTWQJpO7dgGdt516StnrolJ1uulZHh+kCQzbWLkg0uuhUD2phhnWXWaiKwf7QW6L 4F0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=uzpwhU81kY8IzIddi169WgSA3neLYn7k4AXKLClmcQo=; b=jPMk45UeB+A2E3OfCM4V292CxfF9Iw/XhpUk4ru+7f/piGZbHyvs5SoQAezVZX7W+K jJ3379UWtaPq2vC13cs7PeeFMSM/ZWUPO1/5mu37pv17EKAL14xFIw/ulVqdUdjY5UXw LojmjoPOdiOU1DWi3swS385//P4Ua6LW6Txhd4n592cesxVKrsWHmp5x/B+U7JGNlPxL nEZBErrOpfrN3Y0ZSIe04lZgoj2PKnkNQuJUfLADRYNBBfYLGayeXRqNCi4E3GO+xI83 n+fjHdISezjw3jIQSVCdwyPTY1wmELGDlN+qFdKl7FyJSj6d8hGvaIMqSlD/4trgF6WL +ekg==
X-Gm-Message-State: AOAM532N4IdXwweIlv343DY+rNtSwgW4kR7y85XHAgA3UZIqh468uZG8 wbUiFw1yAG1Kvs5Mjod3v8YhHU5PKVAfS2cJz6I=
X-Google-Smtp-Source: ABdhPJxI2OgDhYeaz/kcYuZHBiXyNtXdfctnKEf+G/lE77nBnk/ZknuwwDakxOSLk7J+683EaTOszszbr9ooIMqzIrA=
X-Received: by 2002:a02:a606:: with SMTP id c6mr24774537jam.108.1617026696074; Mon, 29 Mar 2021 07:04:56 -0700 (PDT)
MIME-Version: 1.0
References: <32373_1614018923_6033F96B_32373_329_1_aa05da94-089a-fc73-ca40-8bead8f6a013@orange.com> <CAB75xn41ERs9dcyzkOMADsRHED55mXNxgoBt_fH175wbhsMYug@mail.gmail.com> <30638_1615457838_6049EE2E_30638_39_1_da681320-9738-e520-daf3-196fe0dd1a9a@orange.com> <E9B7E0F9-C92A-4771-8D3A-0124A708AB60@nokia.com> <DM6PR11MB3802CADBA0D4B8EB5071F1A1D3659@DM6PR11MB3802.namprd11.prod.outlook.com> <21914_1616523090_605A2F52_21914_150_1_220c2811-d325-72f5-78a6-fef5939a394f@orange.com> <DM6PR11MB38023B1321B1F4D564F40645D37E9@DM6PR11MB3802.namprd11.prod.outlook.com>
In-Reply-To: <DM6PR11MB38023B1321B1F4D564F40645D37E9@DM6PR11MB3802.namprd11.prod.outlook.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Mon, 29 Mar 2021 19:34:19 +0530
Message-ID: <CAB75xn4iZ2qGq=jGZ+dS=4M=5Dx4Zz4OS79WEb_tAvPsLHMn4g@mail.gmail.com>
To: "Mike Koldychev (mkoldych)" <mkoldych@cisco.com>
Cc: "olivier.dugeon@orange.com" <olivier.dugeon@orange.com>, "Stone, Andrew (Nokia - CA/Ottawa)" <andrew.stone@nokia.com>, "pce@ietf.org" <pce@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/UDb9O-PXNjMWbSXOAdOJFH6QEx8>
Subject: Re: [Pce] Implementation option of draft-ietf-pce-stateful-interdomain-01.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Mar 2021 14:05:03 -0000

Hi Mike, Olivier,

Speaking as a WG member...

On Mon, Mar 29, 2021 at 2:42 PM Mike Koldychev (mkoldych)
<mkoldych@cisco.com> wrote:
>
> Hi Olivier,
>
>
>
> I would not recommend using the BSID TLV for #2 (Signal the presence of a Stitching Label in the path of a Tunnel/Policy). ERO/SR-ERO is the object that encodes the label-stack/path, and the SL is part of the label-stack/path of the previous Policy/Tunnel that uses it, so it belongs to the ERO/SR-ERO.

I agree.

> BTW I don’t believe there is currently a way in PCEP to represent a BSID ERO sub-object, it would be useful to define it in some common way with the Stitching Label.
>

For SR we can use the existing SR-ERO subobject itself as per the
binding label/SID draft, and we also have a Label subobject that can
be made to use for non-SR cases.


>
>
> I agree about using flag(s) instead of allocating a new PST to represent the SL in the BSID TLV.
>
>

We should describe a clear relationship between binding and stitching
labels. Then, TE-PATH-BINDING TLV could be used to report/request a
stitching label with a flag set in this TLV.

Thanks!
Dhruv

>
> *IF* RSVP-TE RECORD_ROUTE is used, then RRO object is appropriate.
>
>
>
> Thanks,
>
> Mike.
>
>
>
> From: olivier.dugeon@orange.com <olivier.dugeon@orange.com>
> Sent: Tuesday, March 23, 2021 2:11 PM
> To: Mike Koldychev (mkoldych) <mkoldych@cisco.com>om>; Stone, Andrew (Nokia - CA/Ottawa) <andrew.stone@nokia.com>om>; Dhruv Dhody <dhruv.ietf@gmail.com>
> Cc: pce@ietf.org
> Subject: Re: [Pce] Implementation option of draft-ietf-pce-stateful-interdomain-01.txt
>
>
>
> Hi Mike,
>
> Le 22/03/2021 à 21:03, Mike Koldychev (mkoldych) a écrit :
>
> Hi Olivier,
>
>
>
> I believe what you are trying to achieve is:
>
> Attach a Stitching Label to a Tunnel/Policy, similar to how a Binding Label points to a Tunnel/Policy.
>
> [OD] Yes. Exactly
>
>
> Signal the presence of a Stitching Label in the path of a Tunnel/Policy.
>
> [OD] Yes by using PCE to PCE exchange through PCEP to convey this information
>
>
>
>
>
> I believe that #1 can be achieved using the Binding Label TLV, by perhaps defining another Binding Type. And #2 can be achieved by adding another ERO/SR-ERO sub-object.
>
> [OD] I think that both #1 & #2 could be achieved using the TE-PATH-BINDING TLV minus the addition of new flag to mention that the TE-PATH-BINDING TLV transport a Stitching Label. I would not define a new Binding Type as we could re-use which have been already define in the pce-binding-sid draft and we would not go back to the same problem as with the multiple PST code point. So, a dedicated flag to mention that it is a Binding Label for inter-domain would be better.
>
>
>
> I do not think it’s a good idea to use the RRO unless there is an actual RSVP RECORD_ROUTE being used.
>
> [OD] I tend to be agree after analysis all potential inconvenient, in particular in term of management. But, in another hand, the Stitching label is part of the Tunnel path reported by the Record Route Object.
>
> Regards
>
> Olivier
>
>
>
> Thanks,
>
> Mike.
>
>
>
> From: Pce <pce-bounces@ietf.org> On Behalf Of Stone, Andrew (Nokia - CA/Ottawa)
> Sent: Thursday, March 11, 2021 11:11 AM
> To: olivier.dugeon@orange.com; Dhruv Dhody <dhruv.ietf@gmail.com>
> Cc: pce@ietf.org
> Subject: Re: [Pce] Implementation option of draft-ietf-pce-stateful-interdomain-01.txt
>
>
>
> Hi Olivier,
>
>
>
> Thanks for pointing this out. I think the presentation slide wording might have been a bit stronger than what is currently written in the posted draft, as the text does not prohibit the use of RRO but rather acknowledge and document that there are implementations which skip inclusion of SR-RRO (Nokia implementation does send SR-RRO), so it documents how to handle this scenario on the PCE. The text indicates that SR-RRO may or may not be included, and if omitted the PCE is to fallback to treating the ERO “like” it was an RRO.
>
>
>
> https://datatracker.ietf.org/doc/html/draft-koldychev-pce-operational-03#section-6
>
>
>
>    A PCC MUST send an (possibly empty) ERO/SR-ERO/SRv6-ERO in the PCRpt
>
>    message for every LSP.  A PCC MAY send an SR-RRO/SRv6-RRO for an SR-
>
>    TE/SRv6-TE LSP (respectively).  A PCE SHOULD interpret the RRO/SR-
>
>    RRO/SRv6-RRO as the actual path the LSP is taking but MAY interpret
>
>    only the ERO/SR-ERO/SRv6-ERO as the actual path.  In the absence of
>
>    an RRO/SR-RRO/SRv6-RRO a PCE SHOULD interpret the ERO/SR-ERO/SRv6-ERO
>
>    (respectively) as the actual path for the LSP.
>
>
>
>
>
> I think the potential interdomain stitching label case you point out and the S-Flag defined in RFC8664 mentioned by Dhruv during the meeting seem to be valid use cases where an SR-RRO would need to be included.
>
>
>
> Thanks!
>
> Andrew
>
>
>
> From: Pce <pce-bounces@ietf.org> on behalf of "olivier.dugeon@orange.com" <olivier.dugeon@orange.com>
> Organization: Orange Labs
> Date: Thursday, March 11, 2021 at 5:17 AM
> To: Dhruv Dhody <dhruv.ietf@gmail.com>
> Cc: "pce@ietf.org" <pce@ietf.org>
> Subject: Re: [Pce] Implementation option of draft-ietf-pce-stateful-interdomain-01.txt
>
>
>
> Hello Dhruv, all,
>
> Following the presentation done during the IETF meeting, please find the link to the presentation: https://datatracker.ietf.org/meeting/110/materials/slides-110-pce-32-inter-domain-00
>
> I also not a major point to take into account following the presentation of draft PCEP Operational Clarification (draft-koldychev-pce-operational) see https://datatracker.ietf.org/doc/draft-koldychev-pce-operational/ and https://datatracker.ietf.org/meeting/110/materials/slides-110-pce-34-operational-clarification-00:
>
>  => In this draft, authors propose to use SR-ERO/SRv6-ERO and to NOT use SR-RRO/SR-v6-RRO for Segment Routing.
>
> As a consequence for the stateful inter-domain draft, proposed option d1, d2 and d3 become invalid as it uses the RRO to convey the Stiching Label. Thus, only option d4 with a specific new sub-Object to convey the Stitching Label remains valid.
>
> As usual, comments are welcome.
>
> Regards
>
> Olivier
>
> Le 26/02/2021 à 05:35, Dhruv Dhody a écrit :
>
> Hi Olivier,
>
> Thanks for starting this thread.
>
> As a WG participant...
>
>
>
> On Tue, Feb 23, 2021 at 12:05 AM <olivier.dugeon@orange.com> wrote:
>
> Dear all,
>
> According to the remark about implementation we got during the WG call
> for adoption, we would start a new thread to discuss this point.
> The goal isto prepare the discussion for next IETF meeting and reach a
> consensusin order to edit revision 2 of the draft.
>
> The stitching label principle requires at least a certain number of
> modifications in the current PCEP version:
>
>  a) A new PCE Capability to announce the inter-domain behaviour
>  b) A new PCE Association Group to associate the local paths identifier
>     to the inter-domain identifier
>  c) new PCEP Errors to manage the Stitching Label exchange
>  d) A mechanism to convey the Stitching Label
>
> If there is no other choice than to reuse existing PCEP Objects by
> allocating new code points for modifications a-c,there is several
> options for point d, which we have tried to list below:
>
>  d1) Use ERO and RRO in conjunction to new Path Setup code points as
>      described in version 01 of the draft. It is the simplest
>      implementation but as mention by Dhruv, each time a new path
>      enforcement appear, a new PST code point must be allocated.
>      For example, when Segment Routing v6 will be standardized, we must
>      allocate a new Stitching label PST code point for SRv6.
>  d2) Use ERO and ERO in conjunction to a new flag in LSP. Simple as for d1,
>      but need to use the LSP Extended Flag draft as all LSP flags have been
>      already allocated.
>  d3) Same as d2 but find another place for the flag e.g. SRP or LSPA Object.
>  d4) Define a new PCEP sub-Objet TLV within the LSP Object to convey the
>      stitching label. This is more independent but need extra parsing from
>      an implementation point of view.
>
>
> My preference would for d2 or d3 (in that order).
> LSP Extended Flag is adopted by the WG and is ready for prime-time use -- let's use it :)
> Authors of LSP Extended Flag are waiting for the draft blockade to be lifted to post the -00 WG I-D.
>
> Thanks!
> Dhruv
>
>
>
> Please, give us your opinion about these different options and don't hesitate
> to propose others.
>
> Regards
>
> Olivier on be-half of co-author's
>
>
>
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
>
> --
>
>
>
> Olivier Dugeon
> Orange Expert, Future Networks
> Open Source Referent
> Orange/IMT/OLN/WTC/IEE/iTeQ
>
>
>
> fixe : +33 2 96 07 28 80
> mobile : +33 6 82 90 37 85
> olivier.dugeon@orange.com
>
> _________________________________________________________________________________________________________________________
>
>
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
>
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
>
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
>
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
>
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
>
> they should not be distributed, used or copied without authorisation.
>
> If you have received this email in error, please notify the sender and delete this message and its attachments.
>
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
>
> Thank you.
>
> --
>
>
>
> Olivier Dugeon
> Orange Expert, Future Networks
> Open Source Referent
> Orange/IMT/OLN/WTC/IEE/iTeQ
>
>
>
> fixe : +33 2 96 07 28 80
> mobile : +33 6 82 90 37 85
> olivier.dugeon@orange.com
>
> _________________________________________________________________________________________________________________________
>
>
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
>
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
>
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
>
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
>
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
>
> they should not be distributed, used or copied without authorisation.
>
> If you have received this email in error, please notify the sender and delete this message and its attachments.
>
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
>
> Thank you.