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/routing-wg@ripe.net/
[routing-wg] Re: New IPv4 blocks allocated to RIPE NCC
- Previous message (by thread): [routing-wg] New IPv4 blocks allocated to RIPE NCC
- Next message (by thread): [routing-wg] Re: New IPv4 blocks allocated to RIPE NCC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Valdis.Kletnieks at vt.edu
Valdis.Kletnieks at vt.edu
Wed Dec 1 17:27:31 CET 2010
On Wed, 01 Dec 2010 12:36:13 +0100, Andrea Cima said: > Additionally, please note that three "pilot" prefixes will be announced > from each /8. The prefixes are: > > 5.0.0.0/16 > 5.1.0.0/21 > 5.1.24.0/24 > > 37.0.0.0/16 > 37.1.0.0/21 > 37.1.24.0/24 > > They all originate in AS12654. Is there a pingable test address target in these prefixes? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: </ripe/mail/archives/routing-wg/attachments/20101201/05b33f34/attachment.sig>
- Previous message (by thread): [routing-wg] New IPv4 blocks allocated to RIPE NCC
- Next message (by thread): [routing-wg] Re: New IPv4 blocks allocated to RIPE NCC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]