Subject: [mpls] draft-jags-mpls-ext-hdr-entropy-lbl-00

From: <[email-masked]>
Date: Mon, 31 Jan 2022 15:39:15 +0000

Hi all,

1) As previously presented and discussed, section 2 of draft-decraene-mpls-slid-encoded-entropy-label-id [1] proposes to use the unused bits of the Entropy Label TTL field to carry indicators in the stack.
This provides the following benefits:
- Faster deployment with incremental benefit.  (as most/all egress LER already support ELI so won't drop the packet)
- Assuming EL used, no extra labels added in the stack (ECMP is largely used and EL helps, so a chance that EL be already present)
- Save a special purpose label (and related routing extensions to signal its support  in LDP, RSVP-TE, BGP, IS-IS, OSPF, BGP-LS)

2) Indicators are useful for different use cases, yet new uses cases may require additional data.
draft-jags-mpls-ext-hdr-entropy-lbl [2] builds on top of the above indicators to signal the presence of In-Stack (IS) and Bottom of Stack (BOS) MPLS Extension Header (MEH) in an MPLS label stack.
Specifically, it defines MPLS Extension Header encoding formats to carry additional data in the MPLS label stack that can influence forwarding decision and to carry additional data (such as IOAM) after the Bottom of the MPLS label stack.

Comments welcomed.

Thanks,
Bruno (on behalf of the authors)

[1] https://datatracker.ietf.org/doc/html/draft-decraene-mpls-slid-encoded-entropy-label-id#section-2
[2] https://datatracker.ietf.org/doc/html/draft-jags-mpls-ext-hdr-entropy-lbl

-----Original Message-----
From: [email-masked]<mailto:[email-masked]> <[email-masked]<mailto:[email-masked]>>
Sent: Wednesday, January 26, 2022 5:21 PM
To: DECRAENE Bruno INNOV/NET <[email-masked]<mailto:[email-masked]>>; Jaganbabu Rajamanickam <[email-masked]<mailto:[email-masked]>>; Jisu Bhattacharya <[email-masked]<mailto:[email-masked]>>; Rakesh Gandhi <[email-masked]<mailto:[email-masked]>>; Royi Zigler <[email-masked]<mailto:[email-masked]>>
Subject: New Version Notification for draft-jags-mpls-ext-hdr-entropy-lbl-00.txt

A new version of I-D, draft-jags-mpls-ext-hdr-entropy-lbl-00.txt
has been successfully submitted by Jaganbabu Rajamanickam and posted to the
IETF repository.

Name:           draft-jags-mpls-ext-hdr-entropy-lbl
Revision:       00
Title:          MPLS Extension Header Encodings Using Entropy Label
Document date:  2022-01-26
Group:          Individual Submission
Pages:          24
URL:            https://www.ietf.org/archive/id/draft-jags-mpls-ext-hdr-entropy-lbl-00.txt
Status:         https://datatracker.ietf.org/doc/draft-jags-mpls-ext-hdr-entropy-lbl/
Html:           https://www.ietf.org/archive/id/draft-jags-mpls-ext-hdr-entropy-lbl-00.html
Htmlized:       https://datatracker.ietf.org/doc/html/draft-jags-mpls-ext-hdr-entropy-lbl

Abstract:
   This document uses the Multiprotocol Label Switching (MPLS) Entropy
   Label (EL) extensions defined in draft-decraene-mpls-slid-encoded-
   entropy-label-id to indicate the presence of MPLS Extension Header
   (MEH) in an MPLS label stack.  It defines different MPLS Extension
   Header encoding formats to carry additional data in the MPLS label
   stack that can influence forwarding decision and to carry additional
   data after the Bottom of the MPLS label stack.

The IETF Secretariat

_________________________________________________________________________________________________________________________

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.

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.