 |
 |
Context: Hurricane Electric is now doing IRR filtering now. My question isn't specific to HE's filtering, but is more about what the best practices are. I'm looking for clue, on or off list, about whether my AS should have an aut-num object. We already have an as-set object listing our AS as well as those of our transit customers. This as-set's name is listed in PeeringDB. We also already have a route-set object containing route objects for each of our prefixes. I've looked at some other networks and this approach (list an as-set in PeeringDB) seems to be the common case. I am only aware of a couple networks who are using an aut-num object. I'm cool with creating an aut-num object, but how much do I really need to fill in? That is, do I need to have import/export statements for literally every AS I peer with, or can I just use "from ANY accept ANY" and "to ANY announce AS-WIKTEL"? I don't want to create and have to maintain an aut-num that is more complex than necessary. I also don't want to break working traffic with peers who might pick up that aut-num object automatically. If it matters, I use the ARIN IRR. I was previously using email templates but would intend to switch (which I understand is permanent) to the web interface on my next modification. -- Richard