- rpslng - mailman.ripe.net

Hi, i need information
by Juan Felipe Botero Vega 08 Nov '07

08 Nov '07

Hi, I am working in a common project between the UPC (University Polithecnic of Catalonia, Spain) and Heanet (Ireland's National Education and Research Network). I know this is not a RPSL forum, but i need to know something about this language. In the RFC 2622 RPSL is well defined, but i don't have clear if it is possible to use RPSL for internal routing. My question is: is it possible to use RPSL to perform the following actions: 1. Configure a router announcing it's the networks it has connected to. 2. Configure the routing protocols in each router (this question depends directly of the previous one) 3. Configure the *routing policies *inside the network (i am not referring to BGP policies but policies of access control in each router inside a network). This could be applied also to OSPF areas?? Thanks for your attention.

2 3

Fwd: Re: RPSL support for 32 bit ASN
by Henk Uijterwaal 15 Sep '06

15 Sep '06

>Date: Wed, 23 Aug 2006 11:20:53 +0200 >To: Mark Prior <mrp(a)mrp.net> >From: Henk Uijterwaal <henk(a)ripe.net> >Subject: Re: RPSL support for 32 bit ASN >Cc: rpslnp(a)ripe.net, asn32(a)ripe.net, ggm(a)apnic.net > >At 15:08 18/08/2006, Mark Prior wrote: > >>Is it worth doing another update to RPSL to include this > >This would certainly help us a lot (we can point to a document when >we update our tools), so ... > >... I spent a morning writing essentially a 1 page document just to >update this and submitted it as an individual submission ID, >draft-uijterwaal-rpsl-4byteas-ext-00.txt. To appear in the ID >repository soon. > >Henk > >------------------------------------------------------------------------------ >Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net >RIPE Network Coordination Centre http://www.amsterdamned.org/~henk >P.O.Box 10096 Singel 258 Phone: +31.20.5354414 >1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 >The Netherlands The Netherlands Mobile: +31.6.55861746 >------------------------------------------------------------------------------ > >1160438400 + 381600 = 1160820000. ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ 1160438400 + 381600 = 1160820000.

6 14

Re: [asn32] Re: RPSL support for 32 bit ASN
by Denis Walker 18 Aug '06

18 Aug '06

Mark Prior wrote: > Henk Uijterwaal (RIPE NCC) wrote: > >> Question: How to adapt RPSL for this? >> >> Solutions: >> >> 1) Change the definition in RFC2622 to >> >> <as-number> An AS number x is represented as the string "AS[0-9]+ >> or AS[0-9]+.[0-9]+. (In other words, follow the Michealson draft). >> >> 2) Other? If so, what? > > > It would seem sensible to follow the draft rather than create > confusion by trying something different. Of course some implements may > not have a bounds check on the max size of an AS number. But they may consider it to be an integer and the new syntax will be x.y. cheers denis > > Is it worth doing another update to RPSL to include this and some > other low hanging fruit? > > Mark.

2 1

RPSL support for 32 bit ASN
by Henk Uijterwaal (RIPE NCC) 18 Aug '06

18 Aug '06

RPSL list, RFC2622 and 4012 say: <as-number> An AS number x is represented as the string "ASx". That is, the AS 226 is represented as AS226. This was written assuming 16 bit (0-65536) AS numbers (ASN16). There is now a draft to expand the AS number space to 32 bits (ASN32, see draft-ietf-idr-as4bytes-12.txt) as well as proposals in the various regions to start deploying those (RIPE2005-08, ARIN 2005-9, APNIC 032-v2 and others) as of January 2007. Draft draft-michaelson-4byte-as-representation-01.txt suggests that ASN are written as: <16 msb in decimal>.<16 lsb in decimal> with the first part dropped for values <65536. (In other words, the AS are labelled 0, 1, 2, .... 65534, 65535, 1.0, 1.1, 1.2 ... 1.65535, 2.0). I can imagine that people will want to use 32 bit ASN in RPSL starting 1/2007. Question: How to adapt RPSL for this? Solutions: 1) Change the definition in RFC2622 to <as-number> An AS number x is represented as the string "AS[0-9]+ or AS[0-9]+.[0-9]+. (In other words, follow the Michealson draft). 2) Other? If so, what? I guess in all cases, implementors will have to check that their implementations can deal with ASN >65535. Is there a WG where we can submit a draft with these extensions? Henk ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------

1 0

[Question] BGP update messages
by Shih Ming Tseng 19 May '05

19 May '05

Hi all, I have some questions regarding to BGP update messages. Please take a look at attached data. These are part of the update messages that Route Views received from peer router "81.209.156.1" related to prefix "152.211.164.0/23" for a 3-minute time period. My long-term observation is that 81.209.156.1 dropped all paths to 152.211.164.0/23. My questions are: 1. Why there were so many update messages with "INCOMPLETE" tag and router 81.209.156.1 kept sending exactly the same path to Route Views. ? 2 Assuming that router 81.209.156.1 sent an update to Route Views if and only if the best route was changed. From the data, it looks that the path was exactly the same. If the assumption were correct, why 81.209.156.1 kept sending update ? 3. Damping on router 81.209.156.1 should have dropped the path. It looks like the damping had nothing to do with those update messages. Any comment is appreciated. Thank you, Ming BGP4MP|1065917214|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917214|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917242|W|81.209.156.1|13237|152.211.164.0/23 BGP4MP|1065917362|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917362|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917362|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917362|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917362|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917362|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917362|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917362|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917362|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917362|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917362|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917362|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917362|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917362|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917362|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917362|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917362|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917362|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917362|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917362|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917363|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917363|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917364|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917364|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917364|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917364|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917364|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917365|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917365|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917365|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917366|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917366|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917367|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917367|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917367|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917368|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917368|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917368|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917369|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917369|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917370|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917370|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917370|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917370|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917371|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917371|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917372|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917372|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917372|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917373|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917373|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917373|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917373|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917374|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917374|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917374|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917374|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917385|A|81.209.156.1|13237|152.211.164.0/23|13237 1239 701 816|INCOMPLETE|81.209.156.1|0|0|13237:44295|NAG|| BGP4MP|1065917385|W|81.209.156.1|13237|152.211.164.0/23

1 0

RFC 4012 is now out
by Larry J. Blunk 18 Mar '05

18 Mar '05

I tidied up a few last bits with the RFC-Editor at the IETF meeting and RFC 4012 is now official. Thanks to everyone who contributed and commented on this document! -Larry http://www.ietf.org/rfc/rfc4012.txt

1 0

[Fwd: authors 48 hours: RFC 4012 <draft-blunk-rpslng-08.txt> NOW AVAILABLE]
by Larry Blunk 17 Feb '05

17 Feb '05

RFC4012 is about to be published. I believe Joao and Florent wanted their email addresses updated. Any other corrections? Speak now or forever hold your peace! -Larry

1 0

IRRtoolset 4.8.2 and RPSLng
by Dimitrios Kalogeras 15 Feb '05

15 Feb '05

Hi to all of you, I apologize for the cross posting but I believe this is of interest to all of you. We have noticed some problems with the IRRtoolset regarding the interpretation of RPSLng from RtConfig. The command used for Rtconfig is : RtConfig -h whois.ripe.net -p 43 -protocol ripe -cisco_use_prefix_lists A small template used for RtConfig was : @RtConfig set cisco_map_first_no = 10 @RtConfig set cisco_map_increment_by = 10 @RtConfig set cisco_max_preference = 220 ! Parameters @RtConfig set cisco_prefix_acl_no = 130 @RtConfig set cisco_aspath_acl_no = 130 @RtConfig set cisco_pktfilter_acl_no = 130 @RtConfig set cisco_community_acl_no = 130 @RtConfig set cisco_access_list_no = 130 ! ***** Specify each peer's incoming filter **** ! GEANT @RtConfig set cisco_map_name = "bgp-geant-%d-%d-in" @RtConfig import AS5408 195.251.27.255 AS20965 62.40.103.57 @RtConfig set cisco_map_name = "bgp-geant-%d-%d-out" @RtConfig export AS5408 195.251.27.255 AS20965 62.40.103.57 @RtConfig set cisco_map_name = "bgp-geant-bkp-%d-%d-in" @RtConfig import AS5408 195.251.27.255 AS20965 62.40.103.201 @RtConfig set cisco_map_name = "bgp-geant-bkp-%d-%d-out" @RtConfig export AS5408 195.251.27.255 AS20965 62.40.103.201 Problems: a) In lines with mp-import and afi ipv4.unicast there is error generation although the RIPE RPSLng accepts the object !!! In some cases if we download the object and execute the RtConfig -h whois.ripe.net -p 43 -protocol ripe -cisco_use_prefix_lists -f < saved object there is no problem !!! b) When we use the switch -cisco_eliminate_dup_map_parts the result is wrong when the policy has multiple address_families defined. c) It is not possible to generate route-maps when the template have IPv6 address like " @RtConfig export AS5408 2001:648:2FFF:1:: AS20965 2001:798:2017:10AA::1 if in the RIPE as object we have defined our on IPv6 attachment point. Instead to in order to generate IPv6 route maps we define @RtConfig export AS5408 195.251.27.255 AS20965 2001:798:2017:10AA::1 int the RtConfig templates !!! This results in Ipv6 route-maps generated !! d) The RPSLng robot of RIPE is broken. We intentionally provide a wrong object and the RIPE robot passed it without a problem !!! In our definition .... mp-import: # GRNET Clients ------------------------------------------- # Import Policy: # Accept all routes that: # (a) has the appropriate AS path and # (b) originates from the client (or someone behind the client) # For these routes, according to the advertised communities: # (i) set the appropriate local preference and # (ii) prepend #--------------------------------------------------------------------- afi any from prng-as5408-grnet-clients accept (PeerAS OR PeerAS:AS-TO-GRNET) AND <^PeerAS+PeerAS:AS-TO-GRNET*$>; REFINE { from AS-ANY action pref=100; accept community.contains(5408:120); from AS-ANY action pref=110; accept community.contains(5408:110); from AS-ANY action pref=111; accept community.contains(5408:109); from AS-ANY action pref=100; accept ANY; } REFINE { from AS-ANY action aspath.prepend(AS5408,AS5408,AS5408,AS5408,AS5408); accept community.contains(5408:2005); from AS-ANY action aspath.prepend(AS5408,AS5408,AS5408); accept community.contains(5408:2003); from AS-ANY accept ANY; } When we provided .... mp-import: # GRNET Clients ------------------------------------------- # Import Policy: # Accept all routes that: # (a) has the appropriate AS path and # (b) originates from the client (or someone behind the client) # For these routes, according to the advertised communities: # (i) set the appropriate local preference and # (ii) prepend #--------------------------------------------------------------------- afi any from prng-as5408-grnet-clients accept (PeerAS OR PeerAS:AS-TO-GRNET) AND REFINE { from AS-ANY action pref=100; accept community.contains(5408:120); from AS-ANY action pref=110; accept community.contains(5408:110); from AS-ANY action pref=111; accept community.contains(5408:109); from AS-ANY action pref=100; accept ANY; } REFINE { from AS-ANY action aspath.prepend(AS5408,AS5408,AS5408,AS5408,AS5408); accept community.contains(5408:2005); from AS-ANY action aspath.prepend(AS5408,AS5408,AS5408); accept community.contains(5408:2003); from AS-ANY accept ANY; } responded in the webupdates with no errors !!! Regards, Dimitrios .PS Our current policy is in the RIPE database is : aut-num: AS5408 as-name: GR-NET descr: Greek Research and Technology Network remarks: ############################################################## +# ROUTING POLICY FOR GRNET # +###################################################################### + + + =================================== + BGP Communities supported by GRNET: + =================================== + + + List of all BGP communites used by GRNET: + ----------------------------------------- + NO_EXPORT + NO_ADVERTISE + 5480:666 Blackhole this route (for /32 only) + 5408:120 Primary connection, choose first + 5408:110 Secondary connection, choose second + 5408:109 Trinary connection, choose third + 5408:2005 Prepend 5 times + 5408:4001 Do not announce to AIX + 5408:4005 Do not announce to GEANT + 5408:4010 Seeren Routes (export to RoEdunet) + + + + BGP communities appended/removed automatically by GRNET: + -------------------------------------------------------- + 5408:4001 is appended to all routes received by GEANT + 5408:4005 is appended to all routes received by AIX Peers + 5408:4010 is appended to all routes received by SEEREN Peers + 5408:4010 is removed from all non-Seeren routes received by GRNET + + + BGP communities available to GRNET clients: + ------------------------------------------- + 5408:120 Primary connection, choose first + 5408:110 Secondary connection, choose second + 5408:109 Trinary connection, choose third + 5480:666 Blackhole this route (for /32 only) + 5408:2005 Prepend 5 times + 5408:4001 Do not announce to AIX + 5408:4005 Do not announce to GEANT + !!! NO OTHER 5408:* SHOULD BE USED BY GRNET CLIENTS !!! + + + BGP communities available to SEEREN Peers: + ------------------------------------------ + 5480:666 Blackhole this route (for /32 only) + 5408:2005 Prepend 5 times + 5408:4001 Do not announce to AIX + 5408:4005 Do not announce to GEANT + !!! NO OTHER 5408:* SHOULD BE USED BY SEEREN Peers !!! + + + BGP communities available to AIX Peers: + ------------------------------------------ + 5408:2005 Prepend 5 times + !!! NO OTHER 5408:* SHOULD BE USED BY AIX Peers !!! + + + + +###################################################################### + remarks: === IMPORT POLICY ============================================ + mp-import: # iBGP (AS5408) ------------------------------------------- # accept all routes # (Note: Although this is not described here, # the border router with SEEREN clears 5408:4010 from iBGP) #--------------------------------------------------------------------- afi any from prng-as5408-ibgp accept ANY; mp-import: # GEANT AS20965 ------------------------------------------- # GEANT is the Internet Upstream for GRNET # Import Policy: # Accept all routes # Set Local Preference 100 for primary, 90 for backup # Append community for not announcement to AIX #--------------------------------------------------------------------- # IPv4 unicast and multicast afi ipv4 from AS20965 62.40.103.57 action pref=120; community.append(5408:4001); from AS20965 62.40.103.201 action pref=130; community.append(5408:4001); accept ANY; mp-import: # IPv6 unicast afi ipv6.unicast from AS20965 2001:798:2017:10AA::1 action pref=120; community.append(5408:4001); from AS20965 2001:798:2017:10AA::9 action pref=130; community.append(5408:4001); accept ANY; mp-import: # RoEdunet (AS2614) --------------------------------------- # RoEdunet is the Backup Upstream for SEEREN peers only! # Import Policy: # Accept all ipv4 unicast routes # Set Local Preference of RoEdunet routes to 50 #--------------------------------------------------------------------- afi ipv4.unicast from AS2614 action pref=170; accept ANY; mp-import: # OteGlobe (AS12713) -------------------------------------- # Peering for Seeren SCS VPN purposes only # Import Policy: # Only allow connection networks (62.75.33.228/27), # PE loopbacks (62.75.26.216/29) and CE loopbacks #--------------------------------------------------------------------- afi ipv4.unicast from AS12713 action pref=70; # High preference; community.append(NO_ADVERTISE); accept {62.75.33.228/27^+, 62.75.26.216/29^+, 147.91.0.112/32, 193.254.1.242/32, 194.141.252.13/32, 194.149.130.249/32}; mp-import: # Blackhole Routing for GRNET & SEEREN Clients ------------ # this command is not supported by RPSL and the RIPE database :-( # we are implementing it, though #--------------------------------------------------------------------- afi any.unicast from AS-ANY action community.append(NO_EXPORT); # next-hop = x.x.x.x; accept community.contains(5408:666) AND (PeerAS OR PeerAS:AS-TO-GRNET) AND {0.0.0.0/0^32} AND <^PeerAS+PeerAS:AS-TO-GRNET*$>; REFINE { from prng-as5408-grnet-clients accept ANY; from prng-as5408-seeren accept ANY; } mp-import: # GRNET Clients ------------------------------------------- # Import Policy: # Accept all routes that: # (a) has the appropriate AS path and # (b) originates from the client (or someone behind the client) # For these routes, according to the advertised communities: # (i) set the appropriate local preference and # (ii) prepend #--------------------------------------------------------------------- afi any from prng-as5408-grnet-clients accept (PeerAS OR PeerAS:AS-TO-GRNET) AND <^PeerAS+PeerAS:AS-TO-GRNET*$>; REFINE { from AS-ANY action pref=100; accept community.contains(5408:120); from AS-ANY action pref=110; accept community.contains(5408:110); from AS-ANY action pref=111; accept community.contains(5408:109); from AS-ANY action pref=100; accept ANY; } REFINE { from AS-ANY action aspath.prepend(AS5408,AS5408,AS5408,AS5408,AS5408); accept community.contains(5408:2005); from AS-ANY action aspath.prepend(AS5408,AS5408,AS5408); accept community.contains(5408:2003); from AS-ANY accept ANY; } mp-import: # SEEREN Peers --------------------------------------------- # Import Policy: # Accept all ipv4 unicast and ipv6 unicast routes that # (a) has the appropriate AS path and # (b) originates from the peer (or someone behind that peer) # For these routes, according to the advertised communities: # (i) set the appropriate local preference # (ii) append the community for announcement to RoEdunet and # (ii) prepend #--------------------------------------------------------------------- afi any.unicast from prng-as5408-seeren action pref=100; community.append(5408:4010); accept (PeerAS OR PeerAS:AS-TO-GRNET) AND <^PeerAS+PeerAS:AS-TO-GRNET*$>; REFINE { from AS-ANY action aspath.prepend(AS5408,AS5408,AS5408,AS5408,AS5408); accept community.contains(5408:2005); from AS-ANY action aspath.prepend(AS5408,AS5408,AS5408); accept community.contains(5408:2003); from AS-ANY accept ANY; } mp-import: # AIX Peers ------------------------------------------------ # Import Policy: # Accept all routes that # (a) has the appropriate AS path and # (b) originates from the peer (or someone behind that peer) # For these routes, according to the advertised communities: # (i) set the appropriate local preference # (ii) append the community for not announcement to Geant and # (ii) prepend #--------------------------------------------------------------------- afi ipv4 from prng-as5408-aix action pref=100; community.append(5408:4005); accept (PeerAS OR PeerAS:AS-TO-AIX) AND <^PeerAS+PeerAS:AS-TO-AIX*$>; REFINE { from AS-ANY action aspath.prepend(AS5408,AS5408,AS5408,AS5408,AS5408); accept community.contains(5408:2005); from AS-ANY action aspath.prepend(AS5408,AS5408,AS5408); accept community.contains(5408:2003); from AS-ANY accept ANY; } mp-import: # K-ROOT mirror @ AIX -------------------------------------- # Import Policy: # Accept K-Root routes and # append the community for not announcement to GEANT #--------------------------------------------------------------------- afi ipv4.unicast from AS25152 action pref=100; community.append(5408:4005); accept {193.0.14.0/24, 195.251.59.0/28} + remarks: === EXPORT POLICY ============================================ + mp-export: # iBGP (AS5408) -------------------------------------------- # Export Policy: # Do not propagate RoEdunet routes via iBGP #--------------------------------------------------------------------- afi any to prng-as5408-ibgp announce (NOT <^AS2614>); EXCEPT { to prng-as5408-ibgp-part announce NOT community.contains(5408:4001); } mp-export: # GEANT (AS20965) ------------------------------------------ # Export Policy: # Announce all routes except from those with community (5408:4005) #--------------------------------------------------------------------- afi any to AS20965 announce NOT community.contains(5408:4005); mp-export: # RoEdunet (AS2614) ---------------------------------------- # RoEdunet is the Backup Upstream for SEEREN peers only! # Export Policy: # Announce only IPv4 unicast routes with 5408:4010 community #--------------------------------------------------------------------- afi ipv4.unicast to AS2614 announce community.contains(5408:4010); mp-export: # OteGlobe (AS12713) Peering for Seeren VPN purposes ------- # Export Policy: # Only announce CE loopback #--------------------------------------------------------------------- afi ipv4.unicast to AS12713 announce {194.177.210.40/32}; mp-export: # AIX Peers ------------------------------------------------ # Export Policy: # Announce all routes except from those with community (5408:4001) #--------------------------------------------------------------------- afi ipv4.unicast to prng-as5408-aix announce NOT community.contains(5408:4001); mp-export: # GRNET Clients & Seeren Peers ----------------------------- # Export Policy: # Announce either all routes or a partial routing table #--------------------------------------------------------------------- afi any to prng-as5408-grnet-firt announce ANY; EXCEPT { to prng-as5408-grnet-part announce NOT community.contains(5408:4001); } + remarks: ############################################################## +# END OF ROUTING POLICY FOR GRNET # +###################################################################### + admin-c: GN28-RIPE tech-c: GN28-RIPE mnt-by: GRNET-NOC changed: D.Kalogeras(a)noc.ntua.gr 19990622 changed: D.Kalogeras(a)noc.ntua.gr 20031120 changed: D.Kalogeras(a)noc.ntua.gr 20031128 changed: D.Kalogeras(a)noc.ntua.gr 20031201 changed: A.Polyrakis(a)noc.ntua.gr 20031218 changed: A.Polyrakis(a)noc.ntua.gr 20041202 changed: A.Polyrakis(a)noc.ntua.gr 20050203 changed: D.Kalogeras(a)noc.ntua.gr 20050215 source: RIPE -- -- Dimitrios K. Kalogeras Electrical Engineer Ph.D. Network Manager NTUA/GR-Net Network Management Center _____________________________________ icq: 11887484 voice: +30-210-772 1863 fax: +30-210-772 1866 e-mail: D.Kalogeras(a)noc.ntua.gr pub 1024D/F2A69A72 2002-12-13 Dimitrios Kalogeras <D.Kalogeras(a)noc.ntua.gr> Key fingerprint = 64C5 646D 8D33 A3FF 14D1 66C6 5127 54CC F2A6 9A72

1 0

The release of RPSLng IRRToolSet
by Katie Petrusha 03 Aug '04

03 Aug '04

[ Apologies for multiple messages ] Dear Colleagues, The RIPE NCC is pleased to announce version 4.8.2 release of IRRToolSet. RPSLng is an effort to extend RPSL language, enabling the language to document routing policies for the IPv6 and multicast address families currently used on the Internet. IRRToolSet implements the Internet Draft Document draft-blunk-rpslng-07 (ftp://ftp.ietf.org/internet-drafts/draft-blunk-rpslng-07.txt) The release contains peval, rpslcheck and RtConfig that support RPSLng. The software can be compiled using GCC-3.x, and also includes numerous contributed patches, bug fixes and changes related to the new draft. Please note that this will be the last release of IRRToolSet made by the RIPE NCC. Further IRRToolSet will be maintained by ISC (Internet Systems Consortium). More details regarding the migration will follow soon. The source code release and binary packages can be downloaded from: ftp://ftp.ripe.net/tools/IRRToolSet You can also check the IRRToolSet project page: http://www.ripe.net/db/irrtoolset Thanks to everyone who contributed the patches and bug fixes. Please contact <irrtoolset(a)ripe.net> for any comments. -- Best regards, Katie Petrusha RIPE NCC

1 0

Re:
by Jhaas 20 Jul '04

20 Jul '04

1 0