Re: [mpls] draft-fang-mpls-label-forwarding-no-swap - how much does it really save?

[Robert Raszuk <[e-mail]>]

Hi Shahram,

This is first time I see that we judge what should the RFC contain by using
sniffer on the wire ... but as I pointed out this is besides the point.

Control plane is different and what currently defined primitives require
control plane to provide workarounds for the missing forwarding action.

Moreover think further ... look at I2RS and MPLS YANG models. Would it
contain something which is not in the MPLS architecture RFC .. I doubt as
by procedural requirements consulting normative reference section it will
be blocked.

As a consequence it is no longer just local RP/RE to data plane trick .. we
are not for new architectures impacting remote controllers which will need
to use concepts of incoming/outgoing labels when setting data plane using
global/path labels.

Is this sound design by any means ?

Cheers,
R.










On Fri, Jul 24, 2015 at 12:06 AM, Shahram Davari <[e-mail]>
wrote:

> Andrew,
>
> Focusing on just the data-plane, do you agree that externally observable
> behavior of a router that does "no-swap" is same as "swap" to the same
> label.
> If so why do you think a standards RFC for data-plane is required? since
> standards RFC should be something that is externally visible outside of a
> box.
>
>
> Thanks
> Shahram
>
> -----Original Message-----
> From: mpls [mailto:[e-mail]] On Behalf Of Andrew Qu
> Sent: Thursday, July 23, 2015 2:55 PM
> To: Loa Andersson; Alexander Vainshtein; Stewart Bryant; Andrew G. Malis;
> S. Davari
> Cc: [e-mail]
> Subject: Re: [mpls] draft-fang-mpls-label-forwarding-no-swap - how much
> does it really save?
>
> It seems I mislead folks from my previous mail.
>
> Please let me rephrase my points. :-)
>
> >From a ASIC design engineer point of view,  I wanted to say swap and
> no-swap is
> Very different meaning.
>
> As long as there is a defined swap operation, I have to design the "swap"
> completely
> In ASIC logic.
>
> If there is a "no-swap" operation defined, then my ASIC engineer will
> implement it differently
> than swap.
>
> I used "TTL" and EXP handling as example.  Since the label is to be
> "swap"ed with a new LABEL stack,
> then the design of SWAPING need to consider TTL handling such as
> 1) just decrement of original TTL or 2) using a brand new TTL, such as
> using local new register stored value to
>   Fill the sawp'ed new label stack.
>
> And in reality,  the ASIC may chose a HW adjacency storage which has
> complete label stack space,  SW is resonspile
> To file them up to fulfill so called "swap" operation.
>
> When standard defines a "no-swap" operation,  ASIC engineer would
> implement such operation completely differently in
> Real RTL design with regarding how to handling TTL or EXP.
>
> If I am putting NETWORK meaning aside for the moment,  the wording in RFC
> about "swap" and "no-swap" is already making difference
> to inplementor already.  So that is what I meant that as RFC writer, we
> should be as clear as possible.
>
>
>
> That is first of my points.
>
> My next point is that:
>
> As matter of fact,  "no-swap" operation has huge difference in the
> following implementation than "swap".
>
> For example:
>
> When without "no-swap" operation defined, in order to achieve "no-swap"
> result, as you suggested,
> I would simply copy "in-label" and write it back to "out-label", but to
> HW, it means that
> for different in-label, I must use different HW adjacency to support
> "no-swap" result.
> So it will be 1-1 mapping of using adjacencies of HW resource even they
> share the rest of rewrite
> Information such out going port and DMAC/SMAC etc.
>
>
> However if we do have a "no-swap" operation defined,  then I can share no
> matter of how many in-coming
> Label with just "ONE" HW adjacence to rewrite the in-coming packets.
>
> The adjacency instruction would simply just be "no operation on label
> value, decrement TTL" and using
> "out_port, DMAC, SMAC"  for all the incoming packet with different labels.
>
> This is huge saving in terms of implementation when "no-swap" is defiend
> as a MPLS opearation option for
> a ASIC design engineer..
>
> Lastly, I still personally believe,  the network meaning of "swap" and
> "no-swap" can't be treated the same.
> As Robert pointed out,  SR also has "CONTINUE" operation as well,  why SR
> keep that operation if we thing
> SWAP is good to cover all cases including "CONTINUE" ?
>
> The local implementation may use the "same" way to meet two different
> requirements does NOT mean they
> Are the same, so from standard RFC point of view, we should not leave it
> as it is,  I feel when use
> Case arises, we should add the clarification such as this draft to clarify.
>
> Thanks,
>
> Andrew
>
>
>
>
>
>
>
>
>
>
> -----Original Message-----
> From: Loa Andersson [mailto:[e-mail]]
> Sent: Thursday, July 23, 2015 6:59 PM
> To: Andrew Qu; Alexander Vainshtein; Stewart Bryant; Andrew G. Malis; S.
> Davari
> Cc: [e-mail]
> Subject: Re: [mpls] draft-fang-mpls-label-forwarding-no-swap - how much
> does it really save?
>
> Andrew,
>
> On 2015-07-23 16:01, Andrew Qu wrote:
> > I don't agree no-swap is the same as "swap with same value".
> >
> > I think if standard adds a no-swap operation, that would be great for
> > people to implement
> >
> > Either SW or HW.
> >
> > Once the label is defined as swap, I need to consider
> >
> > 1)TTL
> >
> > Copy payload TTL ? or using const_value
> >
> > 2)QoS (pipe mode or not)
> >
> > If pipe mode => then I need to do something
> >
> > If not=> then I need to do something else.
> >
> > However if it is really a "no-swap",  then it is very clear for HW/SW
> > to implement such operation.
> >
> > I don't need to consider any part of above cases.
>
> I've a little bit ambivalent (mostly thought this is a no go) about this
> draft, bur if we say that no-swap and not considering TTL and QOS, then
> this definitely a no go!
>
> /Loa
> >
> > I don't think swaping a same value label is NOT the same as "no-swap"
> > at all.
> >
> >  From Standard point of view, we should NOT leave ambiguity here at all.
> >
> > Thanks,
> >
> > Andrew
> >
> > *From:*mpls [mailto:[e-mail]] *On Behalf Of *Alexander
> > Vainshtein
> > *Sent:* Tuesday, July 21, 2015 5:05 PM
> > *To:* Stewart Bryant; Andrew G. Malis; S. Davari
> > *Cc:* [e-mail]
> > *Subject:* Re: [mpls] draft-fang-mpls-label-forwarding-no-swap - how
> > much does it really save?
> >
> > +1.
> >
> > Thumb typed on my LG,
> > Sasha
> >
> > ------ Original message ------
> > *From: *Stewart Bryant
> > *Date: *21/07/2015 17:58
> > *To: *Andrew G. Malis;S. Davari;
> > *Cc: *[e-mail] <mailto:[e-mail]>;
> > *Subject:*Re: [mpls] draft-fang-mpls-label-forwarding-no-swap - how
> > much does it really save?
> >
> > This draft proposes architectural changes, and as we can show that
> > these changes are not needed, in my view, this draft should not go
> > forward.
> >
> > - Stewart
> >
> >
> > On 21/07/2015 09:02, Andrew G. Malis wrote:
> >
> >     As there are no architectural or protocol changes or IANA
> >     considerations, this draft should be informational if it goes
> >     forward (it currently says "standards track").
> >
> >     Cheers,
> >
> >     Andy
> >
> >     On Mon, Jul 20, 2015 at 8:52 PM, S. Davari  <[e-mail]
> >     <mailto:[e-mail]>> wrote:
> >
> >     Eric
> >
> >     I agree no standard change is required since this is a local
> >     optimization issue.
> >
> >     Regards,
> >     Shahram
> >
> >
> >     > On Jul 20, 2015, at 11:43 AM, Eric C Rosen <[e-mail]
> <mailto:[e-mail]>> wrote:
> >     >
> >     >> On 7/20/2015 2:07 PM, Shahram Davari wrote:
> >     >> The new swapped labels (The outgoing  label that replaces the
> >     >> incoming label) need to be stored in a table. Using this draft
> >     >> reduces the number of swapped labels that needs to be stored,
> >     >> regardless of  implementation. Don't you agree?
> >     >
> >     > No.  If you notice that the incoming label needs to be 'replaced'
> by an outgoing label of the same value, you could just make the rewrite
> string shorter, so it won't overwrite the top label on the stack.  This
> seems to be what the draft suggests, but it could  be done as an
> optimization for the particular case where the
> >     incoming and outgoing labels have the same value.  You could do this
> >     today, as a local implementation optimization. There doesn't seem to
> >     be any interop issue or any change to the data plane semantics.
> >     >
> >     >> It also reduces the configuration and management of the new
> swapped labels.
> >     >
> >     > We're not discussing whether there are any advantages to the use
> of domain-wide labels.  We're discussing whether the use of domain-wide
> labels requires a change in the forwarding plane architecture.  I just
> don't see that it does.
> >     >
> >     > _______________________________________________
> >     > mpls mailing list
> >     >[e-mail] <mailto:[e-mail]>
> >     >https://www.ietf.org/mailman/listinfo/mpls
> >
> >
> >     _______________________________________________
> >     mpls mailing list
> >     [e-mail] <mailto:[e-mail]>
> >     https://www.ietf.org/mailman/listinfo/mpls
> >
> >
> >     _______________________________________________
> >
> >     mpls mailing list
> >
> >     [e-mail]  <mailto:[e-mail]>
> >
> >     https://www.ietf.org/mailman/listinfo/mpls
> >
> >
> >
> >
> > --
> >
> > For corporate legal information go to:
> >
> >
> >
> > http://www.cisco.com/web/about/doing_business/legal/cri/index.html
> >
> >
> >
> > ************* Email Confidentiality Notice ******************** The
> > information contained in this e-mail message (including any
> > attachments) may be confidential, proprietary, privileged, or
> > otherwise exempt from disclosure under applicable laws. It is intended
> > to be conveyed only to the designated recipient(s). Any use,
> > dissemination, distribution, printing, retaining or copying of this
> > e-mail (including its
> > attachments) by unintended recipient(s) is strictly prohibited and may
> > be unlawful. If you are not an intended recipient of this e-mail, or
> > believe that you have received this e-mail in error, please notify the
> > sender immediately (by replying to this e-mail), delete any and all
> > copies of this e-mail (including any attachments) from your system,
> > and do not disclose the content of this e-mail to any other person.
> Thank you!
> >
> >
> >
> > _______________________________________________
> > mpls mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/mpls
> >
> ************* Email Confidentiality Notice ********************
> The information contained in this e-mail message (including any
> attachments) may be confidential, proprietary, privileged, or otherwise
> exempt from disclosure under applicable laws. It is intended to be
> conveyed only to the designated recipient(s). Any use, dissemination,
> distribution, printing, retaining or copying of this e-mail (including its
> attachments) by unintended recipient(s) is strictly prohibited and may
> be unlawful. If you are not an intended recipient of this e-mail, or
> believe
> that you have received this e-mail in error, please notify the sender
> immediately (by replying to this e-mail), delete any and all copies of
> this e-mail (including any attachments) from your system, and do not
> disclose the content of this e-mail to any other person. Thank you!
>
> _______________________________________________
> mpls mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/mpls
>
> _______________________________________________
> mpls mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/mpls
>