Thanks for that insight, I guess we are going to have to replace our old as-macro/set with a route-set instead then, I wonder if it would be easier to change the RPSL specification than request all our peers to change there policy configurations! (c: Thanks, Adam

-----Original Message----- From: Andrei Robachevsky [mailto:andrei@ripe.net] Sent: 11 June 2001 11:49 To: Low, Adam Cc: db-wg@ripe.net; ripe-dbm@ripe.net Subject: Re: RPSL route-set/as-set query.

Dear Adam,

"Low, Adam" wrote:

...

Hi Colleagues,

I had a question that I am unable to find an answer for

within the RPSL RFC's, it seems that it is not possible to nest route-set objects within as-set objects, would this be a limitation of the RIPE DBM, RPSL or syntax ?!

...

This is a limitation of RPSL. Members of an as-set are aut-nums and as-sets.

However, a route-set members could be prefixes, other route-sets as well as aut-nums and as-sets. In such cases an aut-num defines the set of routes that are originated by that AS and an as-set defines the set of routes that are originated by the ASes in that as-set.

...

The reason I ask is that we are migrating a customer onto our network and whilst renumbering we will be advertising there assigned blocks from another provider. We currently use as-set's to depict our announcements to peers/providers so would like to add these to our as-set using a route-set object without having to replace our as-set object with a route-set object for our peer/provider announcements.

Thanks, Adam

Regards,

Andrei Robachevsky DB Group Manager RIPE NCC