The following errata report has been submitted for RFC8402, "Segment Routing Architecture".
-------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7671 -------------------------------------- Type: Editorial Reported by: Alvaro Retana <aretana.i...@gmail.com> Section: 4.1 Original Text ------------- A likely use case for the BGP-Prefix segment is an IGP-free hyper- scale spine-leaf topology where connectivity is learned solely via BGP [RFC7938] Corrected Text -------------- A likely use case for the BGP-Prefix segment is an IGP-free hyper- scale spine-leaf topology where connectivity is learned solely via BGP [RFC7938]. Notes ----- The period is missing at the end of the sentence. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC8402 (draft-ietf-spring-segment-routing-15) -------------------------------------- Title : Segment Routing Architecture Publication Date : July 2018 Author(s) : C. Filsfils, Ed., S. Previdi, Ed., L. Ginsberg, B. Decraene, S. Litkowski, R. Shakir Category : PROPOSED STANDARD Source : Source Packet Routing in Networking Area : Routing Stream : IETF Verifying Party : IESG _______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
