Colleagues,
K-root server has now IPv6 transport enabled.
k.root-servers.net. AAAA 2001:7fd::1
A 193.0.14.129
This information is also available from www.root-servers.org webiste.
Regards,
Andrei Robachevsky
RIPE NCC
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(a)ripe.net
- if you are not subscribed to ripe-list(a)ripe.net yet, go to
http://www.ripe.net/mailman/listinfo/ripe-list#subscribers
- for any questions, don't hesitate to contact chair(a)ripe.net
As always, apologies for receiving multiple copies of this announcement.
Best regards,
Rob Blokzijl
RIPE Chairman
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
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:
<https://www.ripe.net/ripe/docs/smallest-alloc-sizes.html>
Regards,
--
leo vegoda
Registration Services Manager
RIPE NCC
