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/address-policy-wg@ripe.net/
Antwort: Re: [address-policy-wg] RIPE Access Policy Change Request to allow allocations to critical infrastructure
- Previous message (by thread): [address-policy-wg] RIPE Access Policy Change Request to allow allocations to critical infrastructure
- Next message (by thread): Antwort: Re: [address-policy-wg] RIPE Access Policy Change Request to allow allocations to critical infrastructure
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andreas Bäß/Denic
baess at denic.de
Sat Jan 10 14:33:08 CET 2004
Gert, you have not been right when assuming that DENIC is only looking for an IPv4 solution. All of our nameservers should have full and native V4 _and_ V6 connectivity which includes the anycast servers as well. > > Do you mean one (1) /32 that can be cut up into smaller > > allocations (/48) which then should appear in the global > > routing table, allowing the services that reside in those > > blocks to be anycast? Or do you mean multiple /32's as the > > case is for the moment*? > > For the routing table size, it doesn't really matter. Neither for the > global address usage. > > For filtering reasons, /32s would be more convenient. > > (But we're not talking v6 yet :-) - DENIC aims at a v4 policy change) > > Gert Doering > -- NetMaster Regards Andreas Baess -- DENIC eG Wiesenhüttenplatz 26 D-60329 Frankfurt
- Previous message (by thread): [address-policy-wg] RIPE Access Policy Change Request to allow allocations to critical infrastructure
- Next message (by thread): Antwort: Re: [address-policy-wg] RIPE Access Policy Change Request to allow allocations to critical infrastructure
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]