nanog mailing list archives

control characters in BGP shutdown communication(RFC 9003) messages and NETCONF


From: Martin Tonusoo via NANOG <nanog () lists nanog org>
Date: Sun, 7 Sep 2025 13:25:34 +0300

Hi.

Meta(AS 32934) recently sent a cease NOTIFICATION message to its
neighbors on AMS-IX and Piter-IX which had a "<0b>maintenance" string
on the RFC 9003 "Shutdown Communication" field. In other words, the
"Shutdown Communication" field contained "0b 6d 61 69 6e 74 65 6e 61
6e 63 65". At least on Junos(tested with versions 21.4R3-S3.4,
23.2R2-S4.5 and 25.2R1.9), calling the "get-bgp-summary-information"
or "get-bgp-neighbor-information" RPCs using NETCONF returns the
string containing the control character and this in turn means that
libraries parsing the XML fail as 0x0b(vertical tab) is not in the
allowed character range of XML 1.0:
https://www.w3.org/TR/xml/#charsets

Who is to blame here? Junos, for returning invalid characters in its
NETCONF response?


Martin
_______________________________________________
NANOG mailing list 
https://lists.nanog.org/archives/list/nanog () lists nanog org/message/CS25Q74D72EUV3MVHOMT3GNZ5HGRZWGV/


Current thread: