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

[Stewart Bryant <[e-mail]>]

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]
> 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