This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[routing-wg] Large BGP Communities beacon in the wild
- Previous message (by thread): [routing-wg] Large BGP Communities beacon in the wild
- Next message (by thread): [routing-wg] Large BGP Communities beacon in the wild
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Maximilian Wilhelm
max at rfc2324.org
Wed Nov 2 13:03:57 CET 2016
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 -- "First they ignore you, then they laugh at you, then they fight you, then you win." -- Mahatma Gandhi
- Previous message (by thread): [routing-wg] Large BGP Communities beacon in the wild
- Next message (by thread): [routing-wg] Large BGP Communities beacon in the wild
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]