wg-irr - [WG-IRR] RFC 2622 Interpretation
Subject: Registry Working Group
List archive
- From: Michael H Lambert <>
- To:
- Subject: [WG-IRR] RFC 2622 Interpretation
- Date: Wed, 28 Aug 2019 14:45:27 -0400
Here's a question. Based on my reading of section 5.3 of RFC 2622, ASNs or
as-sets can be members of route-sets, as in
route-set: AS5050:RS-INTERNET2
descr: Routes sourced to Internet2 by AS5050
members: AS5050:AS-ABILENE-ONLY, AS5050:AS-I1-ABILENE
members: AS5050:RS-3ROX-CORE-I2-ELIGIBLE
tech-c: PN-ORG-ARIN
mnt-by: MAINT-AS5050
changed: 20120502
changed: 20120523
changed: 20150223
source: RADB
However, when I evaluate this object with bgpq3, peval or even Level3's
filtergen or "whois -m -- \!ias5050:rs-internet2,1", only the route-set
member is being expanded. Am I misinterpreting the RFC, or are the tools not
correctly implementing it? I suspect the former, but the RFC seems pretty
explicit.
Michael
- [WG-IRR] RFC 2622 Interpretation, Michael H Lambert, 08/28/2019
- Re: [WG-IRR] RFC 2622 Interpretation, Larry Blunk, 08/28/2019
- Re: [WG-IRR] RFC 2622 Interpretation, Kuch/Mitchell/D., 08/29/2019
- Re: [WG-IRR] RFC 2622 Interpretation, Michael H Lambert, 08/29/2019
- Re: [WG-IRR] RFC 2622 Interpretation, Kuch/Mitchell/D., 08/29/2019
- Re: [WG-IRR] RFC 2622 Interpretation, Larry Blunk, 08/28/2019
Archive powered by MHonArc 2.6.19.