Hi Bruno, From: Bruno Decraene <bruno.decra...@orange.com<mailto:bruno.decra...@orange.com>> Date: Monday, June 12, 2017 at 9:37 AM To: Acee Lindem <a...@cisco.com<mailto:a...@cisco.com>>, "draft-ietf-ospf-segment-routing-extensi...@ietf.org<mailto:draft-ietf-ospf-segment-routing-extensi...@ietf.org>" <draft-ietf-ospf-segment-routing-extensi...@ietf.org<mailto:draft-ietf-ospf-segment-routing-extensi...@ietf.org>>, "draft-ietf-isis-segment-routing-extensi...@ietf.org<mailto:draft-ietf-isis-segment-routing-extensi...@ietf.org>" <draft-ietf-isis-segment-routing-extensi...@ietf.org<mailto:draft-ietf-isis-segment-routing-extensi...@ietf.org>> Cc: "spring@ietf.org<mailto:spring@ietf.org>" <spring@ietf.org<mailto:spring@ietf.org>>, "isis...@ietf.org<mailto:isis...@ietf.org>" <isis...@ietf.org<mailto:isis...@ietf.org>>, OSPF WG List <o...@ietf.org<mailto:o...@ietf.org>> Subject: RE: [OSPF] OSPFv2 Segment Routing Extensions ERO Extensions (would also effect OSPFv3 and IS-IS) - REPLY TO THIS ONE
Hi Acee, authors 2 clarification questions inline [Bruno] From: OSPF [mailto:ospf-boun...@ietf.org] On Behalf Of Acee Lindem (acee) Sent: Friday, June 09, 2017 4:46 PM To: OSPF WG List; spring@ietf.org<mailto:spring@ietf.org>; isis...@ietf.org<mailto:isis...@ietf.org> Cc: draft-ietf-ospf-segment-routing-extensi...@ietf.org<mailto:draft-ietf-ospf-segment-routing-extensi...@ietf.org> Subject: Re: [OSPF] OSPFv2 Segment Routing Extensions ERO Extensions (would also effect OSPFv3 and IS-IS) - REPLY TO THIS ONE Corrected IS-IS WG alias – Please reply to this one. Thanks, Acee From: Acee Lindem <a...@cisco.com<mailto:a...@cisco.com>> Date: Friday, June 9, 2017 at 10:42 AM To: OSPF WG List <o...@ietf.org<mailto:o...@ietf.org>>, "spring@ietf.org<mailto:spring@ietf.org>" <spring@ietf.org<mailto:spring@ietf.org>>, "i...@ietf.org<mailto:i...@ietf.org>" <i...@ietf.org<mailto:i...@ietf.org>> Cc: "draft-ietf-ospf-segment-routing-extensi...@ietf.org<mailto:draft-ietf-ospf-segment-routing-extensi...@ietf.org>" <draft-ietf-ospf-segment-routing-extensi...@ietf.org<mailto:draft-ietf-ospf-segment-routing-extensi...@ietf.org>> Subject: OSPFv2 Segment Routing Extensions ERO Extensions (would also effect OSPFv3 and IS-IS) Hi OSPF, ISIS, and SPRING WGs, As part of the Alia’s AD review, she uncovered the fact that the ERO extensions in 6.1 and 6.2 are specified as far as encoding but are not specified as far as usage in any IGP or SPRING document. As document shepherd, my proposal is that they simply be removed since they were incorporated as part of a draft merge and it appears that no one has implemented them (other than parsing). [Bruno] Is the option to move those Binding SID IGP extensions in a different (WG) document opened/considered? Any opinion on this? If there is the energy to fully specify usage, than a separate document would make sense. I think there is a enough description of the binding SID in existing SPRING documents. However, it the ERO that is not specified. We could also deprecate types (4-8) in the OSPFv2 Extended Prefix LSA Sub-TLV registry to delay usage of these code points for some time (or indefinitely ;^). [Bruno] Are there reasons to make actions to delay/against such usage? Since these are fully specified in the IGP Extensions, there are probably implementations that parse and validate the sub-TLVs. Thanks, Acee Thanks Regards, --Bruno Thanks, Acee _________________________________________________________________________________________________________________________ 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 spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
