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/
[address-policy-wg] /24 in Europe, AP and North America?
- Previous message (by thread): [address-policy-wg] /24 in Europe, AP and North America?
- Next message (by thread): [address-policy-wg] /24 in Europe, AP and North America?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andy Davidson
andy at nosignal.org
Wed Nov 28 13:14:40 CET 2007
On 27 Nov 2007, at 11:35, Hank Nussbacher wrote: > This may have been covered before but I'm not sure. I have a > client that needs a /24 in Europe, a /24 in AP and a /24 in North > America - all for multihoming purposes (in each area). If he > becomes a RIPE member, can he get the 3 /24s and 3 ASNs of which > only one set will be used in Europe? Or just get the /19 like > everyone else, and carve it into 3 chunks and route them each from > a different area? It's normally a /21, which is enough for eight /24 networks - with a caveat. Some networks, to reduce the effects of deaggregation on their routing table size, will filter on the cidr boundaries that RIPE use as minimum allocation size. If you went down the PA route, the addresses would come from a range which some people filter to a /21 smallest subnet size. If you go down the PI route, you will be burning through less IP space and additionally will get your addresses from a range that people are less likely to filter /24s in. Andy
- Previous message (by thread): [address-policy-wg] /24 in Europe, AP and North America?
- Next message (by thread): [address-policy-wg] /24 in Europe, AP and North America?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]