Hi Alvaro, Support the adoption of this draft.
Bruno, I agree — it’d be good to capture (as we go forward) the additional MPLS requirements. We are currently iterating on a draft relating to the entropy label requirements, but it’d be good to give more general guidance for implementors going forward on these things. This draft seems like the natural home for such commentary. Kind regards, r. On 24 Sep 2014, at 14:49, [email protected] wrote: > Hi, > > (as a co-author) I support working group adoption. > > This document defines how the SPRING architecture can be applied to MPLS with > existing hardware & networks and quite limited impact to MPLS sub-part (e.g. > OAM & loadbalancing). IMO this is a very applicable declination of the SPRING > architecture. > > More specific comments: > - Eventually, the doc could list such “additional” MPLS requirements (e.g. > hardware/software ability to push more labels on the ingress, load-balancing > considerations in transit, OAM extensions…). Eventually in the section 8 > “Manageability considerations” which is currently empty. > - Last sentence of section 6 “Segment List History” is eventually historic > and need to be removed/updated. > - Security consideration needs to be written. A priori, as the MPLS principle > are unchanged, MPLS SPRING probably does not change much the security > consideration of MPLS networks therefore IMO this is not blocking for WG > adoption. Existing doc on security may need to be referenced, e.g. RFC 5920 > “Security Framework for MPLS and GMPLS Networks”, may be saying that as LDP > sessions are removed, LDP security aspects (as discussed in RFC 5036 and RFC > 6952) no longer need to be considered. > > Thanks, > Regards, > Bruno > > > From: Alvaro Retana (aretana) [mailto:[email protected]] > Sent: Wednesday, September 24, 2014 3:08 PM > To: [email protected] > Cc: [email protected] > Subject: WG Adoption Call for draft-filsfils-spring-segment-routing-mpls > > Hi! > > This message officially starts the call for adoption for > draft-filsfils-spring-segment-routing-mpls. > > Please indicate your position about adopting this draft by end-of-day on > October 8, 2014. > > Some additional background: This draft describes the instantiation of > Segment Routing on the MPLS data plane. The Segment Routing Architecture is > presented in draft-filsfils-spring-segment-routing (for which there is a > separate call for adoption) > > http://tools.ietf.org/html/draft-filsfils-spring-segment-routing-mpls > > Thanks! > > Alvaro. > _________________________________________________________________________________________________________________________ > > 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. > _______________________________________________ > spring mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/spring
_______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
