This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/
[ipv6-wg] IPv6 Deployment Panel at ICANN, Lisbon
- Previous message (by thread): [ipv6-wg] IPv6 Deployment Panel at ICANN, Lisbon
- Next message (by thread): [ipv6-wg] IPv6 Deployment Panel at ICANN, Lisbon
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Pekka Savola
pekkas at netcore.fi
Mon Mar 26 14:40:47 CEST 2007
Hi, On Mon, 26 Mar 2007, Dimitrios Kalogeras wrote: > I am trying to figure out the reason for that. Well It is not my > surprise that ISPs have not yet adopted the RPSLng for documenting their > new IPv6 routing policies. So we are stuck by hardwired policies which > are not be propagated in routing filters. Just as a data-point: many networks received their allocation before the RIPE DB supported route6 objects (thus couldn't add them, and have forgotten to do so after the support was added) or simply haven't known route6 objects should be added too. I believe in many cases the operators would be willing to add the objects if approached with a gentle reminder. Maybe someone should send such reminders? It'd maybe be best if RIPE NCC could do this, but I'm not sure if such operational checks are within their current toolbox.. -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
- Previous message (by thread): [ipv6-wg] IPv6 Deployment Panel at ICANN, Lisbon
- Next message (by thread): [ipv6-wg] IPv6 Deployment Panel at ICANN, Lisbon
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]