Re: [Detnet] [mpls] draft-decraene-mpls-slid-encoded-entropy-label-id (was RE: Please review the PALS/MPLS/DetNet Joint Session minutes)

I like Bruno’s idea of reusing the entropy label as indicator of MEH in the
label stack and is backwards compatibility for devices not supporting can
continue to use for ECMP load balancing.

I think this is a solid interim solution to get the ball rolling with
minimal software updates and being able to support ancillary data in the
label stack and as other solutions are progressed that may take longer or
implement and deploy at least in the near term we have a quick solution
that could be promising for operators.

I think we do have to vett out the backwards compatibility and scenario I
can think of is if you want to be able to use the entropy label for ECMP
load balancing and simultaneously want to also use as ancillary data
indicator I am guessing won’t work and that is something we would have to
be cognizant of if deployed.

Kind Regards

Gyan

On Wed, Mar 30, 2022 at 4:04 PM John E Drake <jdrake=
[email protected]> wrote:

> Wim,
>
>
>
> I think I would term it a thought experiment.  An RFC 6790 compliant node
> will take the value in the EL label field and use it to select an outgoing
> interface.  If the value in the EL field is a slice ID, such an node will
> select an outgoing interface which is not necessarily part of the slice in
> question and that outgoing interface will be to a node which is not
> necessarily part of the slice in question.
>
>
>
> Yours Irrespectively,
>
>
>
> John
>
>
>
>
>
> Juniper Business Use Only
>
> *From:* Henderickx, Wim (Nokia - BE/Antwerp) <[email protected]>
> *Sent:* Wednesday, March 30, 2022 3:21 PM
> *To:* John E Drake <[email protected]>; [email protected]
> *Cc:* mpls <[email protected]>; detnet WG <[email protected]>; [email protected]
> *Subject:* Re: [mpls] [Pals]
> draft-decraene-mpls-slid-encoded-entropy-label-id (was RE: Please review
> the PALS/MPLS/DetNet Joint Session minutes)
>
>
>
> *[External Email. Be cautious of content]*
>
>
>
> John, do you have evidence of this or is this a theoretical claim ?
>
>
>
> *From: *mpls <[email protected]> on behalf of John E Drake <
> [email protected]>
> *Date: *Wednesday, 30 March 2022 at 19:13
> *To: *[email protected] <[email protected]>
> *Cc: *mpls <[email protected]>, detnet WG <[email protected]>, [email protected] <
> [email protected]>
> *Subject: *Re: [mpls] [Pals]
> draft-decraene-mpls-slid-encoded-entropy-label-id (was RE: Please review
> the PALS/MPLS/DetNet Joint Session minutes)
>
> Except that putting a slice ID in the Entropy Label field will break
> existing  ELI/EL Implementations because their hashing of the slice ID
> won’t necessarily place a packet on the correct outgoing I/F
>
> Sent from my iPhone
>
>
>
> On Mar 30, 2022, at 1:00 PM, [email protected] wrote:
>
> 
>
> *[External Email. Be cautious of content]*
>
>
>
>
>
>
>
> *From:* Tony Li <[email protected]> *On Behalf Of *Tony Li
> *Sent:* Wednesday, March 30, 2022 4:08 PM
>
> > [Kireeti]: suggest attending talk by Tony on danger of reusing ELI
> before making any decision.
>
> https://notes.ietf.org/notes-ietf-113-pals
> <https://urldefense.com/v3/__https:/notes.ietf.org/notes-ietf-113-pals__;!!NEt6yMaO-gk!Sw9ofU9AyD7Z-JKwyAqMlHk5xhNLxZNMSu31Yt6-K7yh-6JehvlSPLDcqrP3gOo$>
>
>
>
> Done. The talk raised no “danger of reusing ELI” for draft
> draft-decraene-mpls-slid-encoded-entropy-label-id; quite the contrary.
>
> I quote: “claims of backward compatibility apply to
> draft-decraene-mpls-slid-encoded-entropy-label-id-03”. With more details on
> slide 18
>
>
> https://datatracker.ietf.org/meeting/113/materials/slides-113-mpls-05-policy-on-mpls-special-purpose-labels-reuse-00
> <https://urldefense.com/v3/__https:/datatracker.ietf.org/meeting/113/materials/slides-113-mpls-05-policy-on-mpls-special-purpose-labels-reuse-00__;!!NEt6yMaO-gk!Sw9ofU9AyD7Z-JKwyAqMlHk5xhNLxZNMSu31Yt6-K7yh-6JehvlSPLDcNEC7QKk$>
>
>
>
>
>
> Yes, the issue with this proposal is that it has no space for in-stack
> data and not enough space for possible expansion of additional actions.
>
>
>
> [Bruno] There are two steps:
>
> - This proposal allows for carrying 8 Indicators and a slice ID while been
> backward compatible with egress LER hance providing faster deployment with
> incremental benefit.
>
> - If more in-stack data is required the proposal is extensible (e.g.
> draft-jags-mpls-ext-hdr) but at the cost of losing the above benefits for
> the ASes & uses-cases requiring more than 8 Indicators per AS or In-Stack
> Data.
>
> So we can have both worlds: simple first step and extensibility for those
> who need it.
>
>
>
> Independently, we also/already have the post stack data option to carry
> ancillary data, which may limit the need for In-Stack data extension.
>
>
>
> --Bruno
>
>
>
> Tony
>
>
>
>
>
>
>
> Orange Restricted
>
> _________________________________________________________________________________________________________________________
>
>
>
> 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.
>
> _______________________________________________
> Pals mailing list
> [email protected]
>
> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/pals__;!!NEt6yMaO-gk!Sw9ofU9AyD7Z-JKwyAqMlHk5xhNLxZNMSu31Yt6-K7yh-6JehvlSPLDcSqI60Zo$
> <https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/pals__;!!NEt6yMaO-gk!Sw9ofU9AyD7Z-JKwyAqMlHk5xhNLxZNMSu31Yt6-K7yh-6JehvlSPLDcSqI60Zo$>
>
> _______________________________________________
> detnet mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/detnet
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email [email protected] <[email protected]>*



*M 301 502-1347*

_______________________________________________
Pals mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/pals