[168827] in North American Network Operators' Group
Re: Route Server Filters at IXPs and 4-byte ASNs
daemon@ATHENA.MIT.EDU (Jared Mauch)
Wed Feb 5 11:07:43 2014
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <20140205142159.GB594@pfrc>
Date: Wed, 5 Feb 2014 11:04:26 -0500
To: Jeff Haas <jhaas@pfrc.org>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Feb 5, 2014, at 9:21 AM, Jeffrey Haas <jhaas@pfrc.org> wrote:
> The wide comms draft (and flex comms, where some of the ideas were =
pulled in
> from) was intended to address the messier case where the meaning of a
> community was already structured. To pick on one of the items in the =
list:
> http://www.onesc.net/communities/as209/
>=20
> Coding these using regexes is a PITA, both as an implementor of the
> underlying policy and as a sender who has to remember what the magic =
value
> means. Ideally the operator should end up with something simple:=20
> Tell AS209, Do not announce to AS foo. Prepend N times to PST peers. =
Etc.
> Right now, these things are magic values.
When possible (e.g.: here at AS2914) we have used things like this:
65500:nnn do not announce to peer
where the NNN is the peer ASN. Using such literal numbering is easier =
for
the humans involved. The ability to see what route is learned from =
specific ASN
is also helpful, as things like AS_PATH are just a bit-string that can =
be arbitrarily
set and sent by a peer.
I will try to keep my eye open for the draft.
(perhaps see you in Atlanta or London).
- Jared=
