Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a IRR as-set/route-set field resp. irr_as_set6 for IPv6 #605

arnoldnipper opened this issue Dec 3, 2019 · 2 comments


Copy link

@arnoldnipper arnoldnipper commented Dec 3, 2019

Although IPv6 is around for two decades some networks still have different routing policies for IPv4 and IPv6. To support this a new field "IRR as-set/route-set IPv6" resp. irr_as_set6 would be needed. This would also allow for a clear structure as this field only can have a single value then.

Relates to #26 #151 and #260

@arnoldnipper arnoldnipper added this to the Decide milestone Dec 3, 2019
@arnoldnipper arnoldnipper self-assigned this Dec 3, 2019

This comment has been minimized.

Copy link

@shane-kerr shane-kerr commented Dec 4, 2019

In RPSL you can declare as many AS-SET objects as you want, which allows networks with different routing policies to have an AS-SET for IPv4 and an AS-SET for IPv6, if that matches their deployment. Is this not possible with the PeeringDB mapping?


This comment has been minimized.

Copy link

@job job commented Dec 4, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.