Dear Colleagues, I have a simple question about route-set objects. <--RFC2622--> ... 5.2 route-set Class The attributes of the route-set class are shown in Figure 12. The route-set attribute defines the name of the set. It is an RPSL name that starts with "rs-". The members attribute lists the members of the set. The members attribute is a list of address prefixes or other route-set names. Note that, the route-set class is a set of route prefixes, not of RPSL route objects. ... </--RFC2622--> 1/ What is the reason that a route-set member can not be an aut-num or as-set object ? Because some registries allow this: route-set: RS-AS101-TO-ABILENE descr: routes that Abilene should accept from AS101 members: AS73, AS11808, AS7774, AS3807, AS13476, AS11995, AS14077, AS13476, AS11964, AS11827, 131.107.151.0/24, 131.252.0.0/16, 134.39.60.0/24, 161.55.0.0/16, 168.156.80.0/20, 168.156.96.0/19, 192.35.180.0/24, 192.46.80.0/24, 198.107.144.0/21, 198.32.40.0/24 admin-c: UW-NOC tech-c: UW-NOC mnt-by: MAINT-AS73 changed: aracine@cac.washington.edu 20010426 source: RADB 2/ Means the last phrase that there are no necessary is to existence of a related route object ? cheers frank
Dear Frank, Frank Bohnsack wrote:
Dear Colleagues,
I have a simple question about route-set objects.
<--RFC2622--> ... 5.2 route-set Class
The attributes of the route-set class are shown in Figure 12. The route-set attribute defines the name of the set. It is an RPSL name that starts with "rs-". The members attribute lists the members of the set. The members attribute is a list of address prefixes or other route-set names. Note that, the route-set class is a set of route prefixes, not of RPSL route objects. ... </--RFC2622-->
1/ What is the reason that a route-set member can not be an aut-num or as-set object ?
Indeed, though RFC2622 allows only address prefixes, several registries, including the RIPE Database, allow aut-num and as-set to be part of the "members:" attribute. RAToolset uses this information to expand such members into route objects (=> prefixes), whose origins are presented by aut-num's and as-set's.
Because some registries allow this:
route-set: RS-AS101-TO-ABILENE descr: routes that Abilene should accept from AS101 members: AS73, AS11808, AS7774, AS3807, AS13476, AS11995, AS14077, AS13476, AS11964, AS11827, 131.107.151.0/24, 131.252.0.0/16, 134.39.60.0/24, 161.55.0.0/16, 168.156.80.0/20, 168.156.96.0/19, 192.35.180.0/24, 192.46.80.0/24, 198.107.144.0/21, 198.32.40.0/24 admin-c: UW-NOC tech-c: UW-NOC mnt-by: MAINT-AS73 changed: aracine@cac.washington.edu 20010426 source: RADB
2/ Means the last phrase that there are no necessary is to existence of a related route object ?
Yes, "members:" attribute lists prefixes that may not correspond to the existing rote objects. To make a route object a member of a set there is another mechanism - to include them by reference ("mbrs-by-ref:" attribute).
cheers frank
Regards, Andrei -- Andrei Robachevsky DB Group Manager RIPE NCC
Hi Frank, I got this question before. Hence I believe we need to clarify this in the RFC, perhaps put it inside the text you quoted. In the next section in RFC, you fill find: 5.3 Predefined Set Objects In a context that expects a route set (e.g. members attribute of the route-set class), an AS number ASx defines the set of routes that are originated by ASx; and an as-set AS-X defines the set of routes that are originated by the ASes in AS-X. A route p is said to be originated by ASx if there is a route object for p with ASx as the value of the origin attribute. For example, in Figure 15, the route set rs-special contains 128.9.0.0/16, routes of AS1 and AS2, and routes of the ASes in AS set AS-FOO. route-set: rs-special members: 128.9.0.0/16, AS1, AS2, AS-FOO Figure 15: Use of AS numbers and AS sets in route sets. The set rs-any contains all routes registered in IRR. The set as-any contains all ASes registered in IRR. On 17 May 2001 12:05:06 +0200, Frank Bohnsack wrote:
Dear Colleagues,
I have a simple question about route-set objects.
<--RFC2622--> ... 5.2 route-set Class
The attributes of the route-set class are shown in Figure 12. The route-set attribute defines the name of the set. It is an RPSL name that starts with "rs-". The members attribute lists the members of the set. The members attribute is a list of address prefixes or other route-set names. Note that, the route-set class is a set of route prefixes, not of RPSL route objects. ... </--RFC2622-->
1/ What is the reason that a route-set member can not be an aut-num or as-set object ?
Because some registries allow this:
route-set: RS-AS101-TO-ABILENE descr: routes that Abilene should accept from AS101 members: AS73, AS11808, AS7774, AS3807, AS13476, AS11995, AS14077, AS13476, AS11964, AS11827, 131.107.151.0/24, 131.252.0.0/16, 134.39.60.0/24, 161.55.0.0/16, 168.156.80.0/20, 168.156.96.0/19, 192.35.180.0/24, 192.46.80.0/24, 198.107.144.0/21, 198.32.40.0/24 admin-c: UW-NOC tech-c: UW-NOC mnt-by: MAINT-AS73 changed: aracine@cac.washington.edu 20010426 source: RADB
2/ Means the last phrase that there are no necessary is to existence of a related route object ?
cheers frank
participants (3)
-
Andrei Robachevsky -
Cengiz Alaettinoglu -
Frank Bohnsack