nanog mailing list archives
Re: AS 3356 (Level 3) -- Community 3356:666
From: Niels Bakker <niels=nanog () bakker net>
Date: Wed, 4 Aug 2021 18:15:17 +0200
* Martijn Schmidt [Wed 04 Aug 2021, 18:01 CEST]:
And it's also nice not to yank the old community in case your customers still depend on it, even if you do also support the RFC version as an alias of that one.
Note that 3356:666 is applied on ingress to routes received from peers. They could easily rewrite their import policy to translate any 3356:666 to 3356:9999 before passing it on to their RTBH systems, without impacting previous consumers of 3356:666 among their BGP customers.
-- Niels.
Current thread:
- AS 3356 (Level 3) -- Community 3356:666 Sriram, Kotikalapudi (Fed) via NANOG (Aug 04)
- Re: AS 3356 (Level 3) -- Community 3356:666 Patrick Schultz (Aug 04)
- Re: AS 3356 (Level 3) -- Community 3356:666 Sriram, Kotikalapudi (Fed) via NANOG (Aug 04)
- Re: AS 3356 (Level 3) -- Community 3356:666 Daniel Suchy via NANOG (Aug 04)
- Re: AS 3356 (Level 3) -- Community 3356:666 Steve Meuse (Aug 04)
- Re: AS 3356 (Level 3) -- Community 3356:666 Martijn Schmidt via NANOG (Aug 04)
- Re: AS 3356 (Level 3) -- Community 3356:666 Niels Bakker (Aug 04)
- Re: AS 3356 (Level 3) -- Community 3356:666 Steve Meuse (Aug 04)
- Re: AS 3356 (Level 3) -- Community 3356:666 Patrick Schultz (Aug 04)