Works too: Unrecognized Attributes: 15 bytes Attr flags e0 code 20: 00 00 3c ca 00 00 00 01 00 00 00 01 On 11/02/16 15:03, Maximilian Wilhelm wrote:
Anno domini 2016 Job Snijders scripsit:
Dear Job,
Through this beacon it was discovered that a vendor was squatting on BGP Path Attribute value 30. And another vendor sat on 31.
So, a twisted turn of events, the Large BGP Communities effort has ended up with BGP Path Attribute value 32 - very befitting if you look at the very problem we're trying to solve :-)
The beacon has been updated to use the new IANA assigned value, nothing else was changed. Hopefully we are in the clear this time around!
Please verify if you can see 192.147.168.0/24 and 2001:67c:208c::/48 There it is:
BGP.20 [t]: 00 00 3c ca 00 00 00 01 00 00 00 01
Best Max
-- Kind regards, CTO at *Foton Telecom CJSC* Tel.: +7 (499) 679-99-99 AS42861 on PeeringDB <http://as42861.peeringdb.com/>, Qrator <https://radar.qrator.net/as42861>, BGP.HE.NET <http://bgp.he.net/AS42861> http://ipv6actnow.org/ <%0Ahttp://ipv6actnow.org/>