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] 200 customer requirements for IPv6
- Previous message (by thread): [address-policy-wg] Re: 200 customer requirements for IPv6
- Next message (by thread): [address-policy-wg] 200 customer requirements for IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jørgen Hovland
jorgen at hovland.cx
Thu Nov 17 20:03:30 CET 2005
----- Original Message ----- From: "Tim Streater" <tim.streater at dante.org.uk> > We are an LIR and we already have a /32 for the European NREN transit > network that we also manage (GEANT). You don't use customer address space > to address your transit network. What happens if that customer goes > bankrupt or wants the space back or takes their custom elsewhere? And it's > intended to be a couple of years, not 10. > >>> I was able to get v4 PI space for >>> this from RIPE, but the 200 rule appears to rule out these guys using >>v6. Oh well. >> Hi Tim, The 200 rule is for PA. You want/need PI so lets start/continue The PI discussion, not the "I am so special that I need a special PI policy just for my organisation" discussion if anybody is thinking in that direction. Joergen Hovland
- Previous message (by thread): [address-policy-wg] Re: 200 customer requirements for IPv6
- Next message (by thread): [address-policy-wg] 200 customer requirements for IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]