The following errata report has been submitted for RFC8327, "Mitigating the Negative Impact of Maintenance through BGP Session Culling".
-------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid5280 -------------------------------------- Type: Editorial Reported by: Job Snijders <[email protected]> Section: 1 Original Text ------------- BGP Session Culling is the practice of ensuring BGP sessions are forcefully torn down before maintenance activities on a lower-layer network commence -- activities that otherwise would affect the flow of data between the BGP speakers. BGP Session Culling is the practice of ensuring BGP sessions are forcefully torn down before commencing maintenance activities (that otherwise would affect the flow of data between the BGP speakers) on a lower-layer network. Corrected Text -------------- BGP Session Culling is the practice of ensuring BGP sessions are forcefully torn down before maintenance activities on a lower-layer network commence -- activities that otherwise would affect the flow of data between the BGP speakers. Notes ----- The original version of a corrected sentence was left in the document in the editing phase 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. -------------------------------------- RFC8327 (draft-ietf-grow-bgp-session-culling-05) -------------------------------------- Title : Mitigating the Negative Impact of Maintenance through BGP Session Culling Publication Date : March 2018 Author(s) : W. Hargrave, M. Griswold, J. Snijders, N. Hilliard Category : BEST CURRENT PRACTICE Source : Global Routing Operations Area : Operations and Management Stream : IETF Verifying Party : IESG _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
