AS-SET should be able to reference AS-SET in other sources.

[troy2914]

Attempted in 4.0.2

Modify FAILED: [as-set] AS2914:AS-EUROPE-V6
ERROR: Object AS-1AND1 referenced in field members not found in database NTTCOM - must reference one of aut-num, as-set.
ERROR: Object AS-3W-INFRA referenced in field members not found in database NTTCOM - must reference one of aut-num, as-set.

Actually for that matter, I do not think any checks beyond valid content (ascii and of the form as-set name or asn ) of as-set/asn names, should be checked for the as-set members. E.g. it may refer to as-set's/ASNs that do not currently exist.

[mxsasha]

I'll pick this up and validate only on valid ASN or valid as-set name. I take it the same principle should apply to rtr-set and route-set? Those also have the same strong validation now.

[job]

Correct, please also extend to those object types.

…

On Fri, Jun 28, 2019 at 18:51 Sasha Romijn ***@***.***> wrote: I'll pick this up and validate only on valid ASN or valid as-set name. I take it the same principle should apply to rtr-set and route-set? Those also have the same strong validation now. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#240>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABFRWCQZ3L4QIFE3THDAL3P4Y6PVANCNFSM4H346AZQ> .