[prev in list] [next in list] [prev in thread] [next in thread]
List: mpls
Subject: Re: [mpls] on MIAD ADI requirement draft RE: Agenda for the MPLS Open DT 2021-10-14
From: Stewart Bryant <stewart.bryant () gmail ! com>
Date: 2021-10-21 15:24:44
Message-ID: ACE3E7B4-4F84-4D5A-A60A-074A9B2AE6E7 () gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
> On 21 Oct 2021, at 15:42, Kireeti Kompella <kireeti.ietf@gmail.com> wrote:
>
> Hi Matthew,
>
> On Oct 18, 2021, at 01:55, Bocci, Matthew (Nokia - GB) <matthew.bocci@nokia.com \
> <mailto:matthew.bocci@nokia.com>> wrote:
> > "The mechanism to indicate thatAncillary Data is present MUST operate in the \
> > context of the top of stack LSE."
>
> I'm not sure what this means, except possibly, the ADI MUST NOT be the top of stack \
> LSE. There were some suggestions that the FAI could be at the top of stack, \
> accompanied by some label gymnastics to get the forwarding label. This rules that \
> option out (which I'm happy about).
> Here's some alternate text:
>
> "The mechanism to indicate that Ancillary Data is present MUST allow for simple \
> forwarding of MPLS packets based on the top of stack LSE. A node MAY (SHOULD?) go \
> further, though, to find the ADI within the label stack and act upon it."
MPLS always operates in the context of the top of stack.
Sure when the FEC is IP it does some rummaging around for other information but when \
the FEC is not IP I don't think it does that. It certainly should not.
By binding the operation of these new features to the ToS we avoid painting ourselves \
into any corners and get the option to revise or exclude the operation in the light \
of experience.
- Stewart
[Attachment #5 (unknown)]
<html><head><meta http-equiv="Content-Type" content="text/html; \
charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; \
line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote \
type="cite" class=""><div class="">On 21 Oct 2021, at 15:42, Kireeti Kompella <<a \
href="mailto:kireeti.ietf@gmail.com" class="">kireeti.ietf@gmail.com</a>> \
wrote:</div><br class="Apple-interchange-newline"><div class=""><meta \
http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div \
style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: \
after-white-space;" class="">Hi Matthew,<br class=""><div class=""><br \
class=""></div><div class="">On Oct 18, 2021, at 01:55, Bocci, Matthew (Nokia - GB) \
<<a href="mailto:matthew.bocci@nokia.com" class="">matthew.bocci@nokia.com</a>> \
wrote:<br class=""><br class=""><blockquote type="cite" class=""><div class=""><span \
style="font-family: Calibri, sans-serif; font-size: 11pt; caret-color: rgb(0, 0, 0);" \
class="">"The mechanism to indicate that</span><font face="Calibri, sans-serif" \
class=""><span style="caret-color: rgb(0, 0, 0); font-size: 14.666666984558105px;" \
class="">Ancillary</span></font><span style="caret-color: rgb(0, 0, 0); font-family: \
Calibri, sans-serif; font-size: 11pt;" class=""> Data is present MUST operate in \
the context of the top of stack LSE."</span></div></blockquote><div class=""><br \
class=""></div>I'm not sure what this means, except possibly, the ADI MUST NOT be the \
top of stack LSE. There were some suggestions that the FAI could be at the top \
of stack, accompanied by some label gymnastics to get the forwarding label. \
This rules that option out (which I'm happy about).</div><div class=""><br \
class=""></div><div class="">Here's some alternate text:</div><div class=""><br \
class=""></div><div class="">"The mechanism to indicate that Ancillary Data is \
present MUST allow for simple forwarding of MPLS packets based on the top of stack \
LSE. A node MAY (SHOULD?) go further, though, to find the ADI within the label \
stack and act upon it."</div><div class=""><br \
class=""></div></div></div></blockquote><br class=""></div><div>MPLS always operates \
in the context of the top of stack.</div><div><br class=""></div><div>Sure when the \
FEC is IP it does some rummaging around for other information but when the FEC is not \
IP I don't think it does that. It certainly should not.</div><div><br \
class=""></div><div>By binding the operation of these new features to the ToS we \
avoid painting ourselves into any corners and get the option to revise or exclude the \
operation in the light of experience.</div><div><br class=""></div><div>- \
Stewart</div><div><br class=""></div><div><br class=""></div><br \
class=""></body></html>
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic