Re: [mpls] Opsdir last call review of draft-ietf-mpls-spring-entropy-label-11

[<[e-mail]>]

Hi Joe,

>You're still leaving this a MAY, which may be fine.  But is there a
>recommended approach other than using the minimum value?  I haven't read
>the other advertisements drafts, so they may be recommending something
>(in which case a reference link would be nice to add).

The advertisement drafts are using a unique value which is the smallest value.
IMO, this draft should serve as a base to the advertisement drafts and not the opposite. That's why I would like to avoid a reference (at least normative) to the advertisement drafts.

Brgds,


-----Original Message-----
From: Joe Clarke [mailto:[e-mail]] 
Sent: Friday, July 06, 2018 16:55
To: LITKOWSKI Stephane OBS/EM; [e-mail]
Cc: [e-mail]; [e-mail]; [e-mail]
Subject: Re: Opsdir last call review of draft-ietf-mpls-spring-entropy-label-11

On 7/5/18 18:25, [e-mail] wrote:
> I found a couple of MAY requirements in here that I feel should be stronger or
> offer some additional recommendation (mainly to favor operators or help guide
> vendors).  First, section 4 states "For simplicity, an implementation MAY use
> the minimum ERLD between each linecard as the ERLD value for the system."  I
> feel there should be a stronger recommendation on what to do here given that
> ERLD is later described as a key piece of the algorithm for EL placement.  A
> vendor may opt for the simple approach, but should they consider a more robust
> approach to favor operators?
> 
> [SLI] Proposed addition:
> "The drawback of using a single ERLD for a system lower than the capability of one or more specific component is that it may increase the number of ELI/ELs inserted. This leads to an increase of the label stack size."

That sounds reasonable.  Wouldn't it also potentially cause a loss of
load balancing capability along a path?

You're still leaving this a MAY, which may be fine.  But is there a
recommended approach other than using the minimum value?  I haven't read
the other advertisements drafts, so they may be recommending something
(in which case a reference link would be nice to add).

> 
> Second, section 5 states "this node MAY advertise its MSD value or a subset of
> its MSD value to the controller."  It MAY NOT do that, too.  It would be good
> to highlight pros and cons to this.
> 
> [SLI] Here is the proposal:" As the controller does not have
>    the knowledge of the entire label stack to be pushed by the node, the
>    node SHOULD advertise an MSD value which is lower than its actual limit. If the node advertises an MSD values equal to its actual limit, the controller could program an LSP using a number of labels equal to the MSD value. When receiving this label stack from the controller, the ingress node may not be able to add any service (L2VPN, L3VPN, EVPN...) label on top of this label stack.  The consequence could be for the ingress node to drop service packets that should have been forwarded over the LSP."

Works for me.

> 
> 
> 
> Finally, section 7.2 states "In case of a trade-off, an implementation MAY
> provide flexibility to the operator to select the criteria to be considered
> when placing EL/ELIs..."  I can see this being of great value to operators to
> have vendors allow this.  But as with any MAY, the vendor MAY choose NOT to do
> it.  SHOULD seems better here for that reason.
> 
> [SLI] Agree that "SHOULD" better fits here

Thanks!

Joe

_________________________________________________________________________________________________________________________

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.