From shane at ripe.net Wed Dec 15 18:01:25 2004 From: shane at ripe.net (Shane Kerr) Date: Wed, 15 Dec 2004 18:01:25 +0100 Subject: [ipv6-wg@ripe.net] RPSLng in the RIPE Whois Database Message-ID: <41C06DE5.1090104@ripe.net> Dear Colleagues, Beginning Wednesday 29 December 2004, the RIPE Database will support RPSLng. RPSLng extends the Routing Policy Specification Language (RPSL) allowing description of IPv6 and multicast routing policies. It includes a new object type, ROUTE6, and new attributes, such as "mp-import:" and "mp-export:". RPSLng was submitted to the IETF to become an RFC. You can read the most recent draft at: http://www.radb.net/rpslng-08.html This change will not affect the current contents of the database. It is optional for any objects you maintain. The main differences for query users are as follows: - Currently a query for an IPv4 address or network may return INETNUM, ROUTE, and INET-RTR objects. A query for an IPv6 address or network can only return an INET6NUM object. After we put RPSLng into production, IPv6 queries will start to also return ROUTE6 and INET-RTR objects, if they are in the database. - Currently an inverse query (using the "-i" flag) for AUT-NUM objects may return ROUTE objects. After we put RPSLng into production, a query will return both ROUTE and ROUTE6 objects. If you want to limit your query, you can use the "-T" flag. For example, if you only want ROUTE objects returned to an inverse query, you can type: whois -h whois.ripe.net -T route -i origin AS3333 Please change your scripts if necessary. We will not move the contents of the RPSLng prototype Whois server to the RIPE Whois Database. You will have to create any objects that define your routing policy in the production RIPE Whois Database. You can update the RPSLng prototype Whois server until the start of January 2005. The query interface will be available until the end of January 2005. -- Shane Kerr Software Manager RIPE NCC From berni at birkenwald.de Wed Dec 15 19:31:22 2004 From: berni at birkenwald.de (Bernhard Schmidt) Date: Wed, 15 Dec 2004 19:31:22 +0100 Subject: [ipv6-wg@ripe.net] RPSLng in the RIPE Whois Database In-Reply-To: <41C06DE5.1090104@ripe.net> References: <41C06DE5.1090104@ripe.net> Message-ID: <1103135482.10580.5.camel@cholera> Hi, > Beginning Wednesday 29 December 2004, the RIPE Database will support > RPSLng. This is great, I really appreciate that. Now, any comments about registering route6-objects for 6to4 prefix (2002::/16)? I would suggest a solution like it is already done for the IPv4 part (192.88.99.0/24), perhaps even use the same maintainer. 2002::/16 isn't RFC3068 per se, but since 3068 and the appropriate parts in 3056 are strictly tied and 6to4 relays are mostly bidirectional (announcing IPv4 and IPv6 prefix) it wouldn't hurt to use RFC3068-MNT here, too. The initial object would need to be created by RIPE NCC though, due to missing mnt-routes in ::0/0. Bernhard From leo at ripe.net Thu Dec 16 14:56:47 2004 From: leo at ripe.net (leo vegoda) Date: Thu, 16 Dec 2004 14:56:47 +0100 Subject: [ipv6-wg@ripe.net] New IPv6 Address Block Allocated to RIPE NCC Message-ID: <5384E2AA-4F6A-11D9-9302-000A95DAB530@ripe.net> Dear Colleagues, The RIPE NCC received the IPv6 address range 2001:4C00::/23 from the IANA in December 2004. You may wish to adjust any filters you have in place accordingly. More information on the IP space administered by the RIPE NCC can be found on our web site at: Regards, -- leo vegoda Registration Services Manager RIPE NCC From engin at ripe.net Tue Dec 21 14:07:58 2004 From: engin at ripe.net (Engin Gunduz) Date: Tue, 21 Dec 2004 14:07:58 +0100 Subject: [ipv6-wg@ripe.net] Re: RPSLng in the RIPE Whois Database In-Reply-To: <1103135482.10580.5.camel@cholera> References: <41C06DE5.1090104@ripe.net> <1103135482.10580.5.camel@cholera> Message-ID: <20041221130758.GC10976@x47.ripe.net> Hi Bernhard, On 2004-12-15 19:31:22 +0100, Bernhard Schmidt wrote: > Hi, > > > Beginning Wednesday 29 December 2004, the RIPE Database will support > > RPSLng. > > This is great, I really appreciate that. > > Now, any comments about registering route6-objects for 6to4 prefix > (2002::/16)? I would suggest a solution like it is already done for the > IPv4 part (192.88.99.0/24), perhaps even use the same maintainer. > 2002::/16 isn't RFC3068 per se, but since 3068 and the appropriate parts > in 3056 are strictly tied and 6to4 relays are mostly bidirectional > (announcing IPv4 and IPv6 prefix) it wouldn't hurt to use RFC3068-MNT > here, too. > > The initial object would need to be created by RIPE NCC though, due to > missing mnt-routes in ::0/0. OK, we will add "mnt-routes: RIPE-NCC-RPSL-MNT" to the 0::/0 inet6num object during the transition. Regards, > > Bernhard -- Engin Gunduz RIPE NCC Software Engineering Department From k13 at nikhef.nl Tue Dec 21 14:44:13 2004 From: k13 at nikhef.nl (Rob Blokzijl) Date: Tue, 21 Dec 2004 14:44:13 +0100 (MET) Subject: [ipv6-wg@ripe.net] Announcement: Policy Development Process in RIPE Message-ID: To the RIPE Community, later today I will publish a draft document that describes the policy making process in RIPE. It is draft, so your input is requested in order to come to a generally accepted final document. Logistics: - deadline for comments on the first draft: 1 Februari 2005 - discussion takes place on ripe-list at ripe.net - if you are not subscribed to ripe-list at ripe.net yet, go to http://www.ripe.net/mailman/listinfo/ripe-list#subscribers - for any questions, don't hesitate to contact chair at ripe.net As always, apologies for receiving multiple copies of this announcement. Best regards, Rob Blokzijl RIPE Chairman From randy at psg.com Tue Dec 21 18:05:57 2004 From: randy at psg.com (Randy Bush) Date: Tue, 21 Dec 2004 12:05:57 -0500 Subject: [ipv6-wg@ripe.net] Re: [eix-wg] Announcement: Policy Development Process in RIPE References: Message-ID: <16840.22517.647024.632059@roam.psg.com> > later today I will publish a draft document that describes the policy > making process in RIPE. this is the product of the small working group on the subject? randy From leo at ripe.net Thu Dec 16 14:56:47 2004 From: leo at ripe.net (leo vegoda) Date: Thu, 16 Dec 2004 14:56:47 +0100 Subject: [ipv6-wg@ripe.net] [afnog] New IPv6 Address Block Allocated to RIPE NCC Message-ID: <5384E2AA-4F6A-11D9-9302-000A95DAB530@ripe.net> Dear Colleagues, The RIPE NCC received the IPv6 address range 2001:4C00::/23 from the IANA in December 2004. You may wish to adjust any filters you have in place accordingly. More information on the IP space administered by the RIPE NCC can be found on our web site at: Regards, -- leo vegoda Registration Services Manager RIPE NCC _______________________________________________ afnog mailing list afnog at afnog.org http://listserv2.cfi.co.ug/mailman/listinfo/afnog