Re: [RTG-DIR] RtgDir review: draft-ietf-mpls-spring-entropy-label

[Daniele Ceccarelli <[e-mail]>]

Great.
After sorting out the draft status no more pending issues from my side.

BR
Daniele

From: [e-mail] [mailto:[e-mail]]
Sent: venerdì 27 aprile 2018 16:59
To: Daniele Ceccarelli <[e-mail]>; <[e-mail]> ([e-mail]) <[e-mail]>
Cc: [e-mail]; [e-mail]; [e-mail]
Subject: RE: RtgDir review: draft-ietf-mpls-spring-entropy-label

Make sense, I will correct it.


From: Daniele Ceccarelli [mailto:[e-mail]]
Sent: Friday, April 27, 2018 16:56
To: LITKOWSKI Stephane OBS/OINIS; <[e-mail]<mailto:[e-mail]>> ([e-mail]<mailto:[e-mail]>)
Cc: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Subject: RE: RtgDir review: draft-ietf-mpls-spring-entropy-label

Hi Stephane,

it’s a terminology issue. I don’t think there has to be a 1:1 mapping between domain and AS.  The term domain can refer to various administrative boundaries, in this case signaling domains.
If you want you can say: “propagate between the signalling domains”. The info is not exchanged between the protocols.

BR
Daniele

From: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]]
Sent: venerdì 27 aprile 2018 15:18
To: Daniele Ceccarelli <[e-mail]<mailto:[e-mail]>>; <[e-mail]<mailto:[e-mail]>> ([e-mail]<mailto:[e-mail]>) <[e-mail]<mailto:[e-mail]>>
Cc: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Subject: RE: RtgDir review: draft-ietf-mpls-spring-entropy-label

Hi Daniele,

There are two cases for stitching, you can stitch at a domain boundary (when using domain, I mean AS), but you can also stitch within the domain between some kind of subdomains that may run different protocols. For example, within a single area, you may have LDP and SR running in different islands, and you may need to propagate the ELC from the SR egress to the LDP ingress.

Brgds,

From: Daniele Ceccarelli [mailto:[e-mail]]
Sent: Friday, April 27, 2018 13:33
To: LITKOWSKI Stephane OBS/OINIS; <[e-mail]<mailto:[e-mail]>> ([e-mail]<mailto:[e-mail]>)
Cc: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Subject: RE: RtgDir review: draft-ietf-mpls-spring-entropy-label

Hi Stephane,

please see below (BOTH replies).

Cheers,
Daniele


From: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]]
Sent: venerdì 27 aprile 2018 10:02
To: LITKOWSKI Stephane OBS/OINIS <[e-mail]<mailto:[e-mail]>>; Daniele Ceccarelli <[e-mail]<mailto:[e-mail]>>; <[e-mail]<mailto:[e-mail]>> ([e-mail]<mailto:[e-mail]>) <[e-mail]<mailto:[e-mail]>>
Cc: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Subject: RE: RtgDir review: draft-ietf-mpls-spring-entropy-label

Sorry, there is one comment I have missed to reply:

“- Section 6: “   To accomodate the mix of signalling protocols involved during the

   stitching, the entropy label capability SHOULD be propagated between the signalling protocols.” Not clear what this means, maybe it should be propagated between the two domains, not the signaling protocols?”



The text talks about the entropy label capability, not the entropy label itself. The idea is upon stitching to enable transitivity across signaling protocols (as the ELC is carried in signaling protocols).



[>DC] yes, understood and since I believe the signaling protocols will be running in separate domains IMHO it’s more appropriate to speak about propagation between the domains and not between the signaling protocols (you don’t propagate and info between two protocols, and if you do that It’s and implementation issue).

From: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]]
Sent: Thursday, April 26, 2018 15:50
To: Daniele Ceccarelli; <[e-mail]<mailto:[e-mail]>> ([e-mail]<mailto:[e-mail]>)
Cc: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Subject: RE: RtgDir review: draft-ietf-mpls-spring-entropy-label

Hi Daniele,

Thanks for your review, I have addressed most of your comments as part of the -09 that I have just submitted. Let me know if it fits your comments.
The not addressed comment is :

  *   “Section 1.1 – Is this needed? The abstract says “This document examines and describes how ELs are to be applied to Segment Routing” and the status is informational. I’m not sure RFC2119 language is needed. E.g. in section 4 “A router capable of reading N labels but not using an EL located within those N labels MUST consider its ERLD to be 0”.  Further reading the document I see constraint against e.g. the ERLD are defined. Maybe it is more appropriate to say that the document also describes the requirements for the usage of EL in SPRING MPLS ? Moreover in section 6 it seems to describe procedures, so it’s even more than applicability and requirements.

Yes, the current intended status is Informational as per a very old discussion but I think it may re-require a discussion. As you pointed, we are now defining some requirements, we are giving some new concepts (ERLD). So I’m open to a debate on the status of the document if it should go to STD track or let it informational. I would like to hear other opinions on this.
[>DC] Agree. This probably needs to be discussed with the WG and the chairs. If you want to keep the informal status there are some things to be changed. To me it’s simpler to go for standard track and modify the scope of the document, but this is just my opinion.

Brgds,


_________________________________________________________________________________________________________________________



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.

_________________________________________________________________________________________________________________________



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.