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] IPv6 access to K-root
- Previous message (by thread): [address-policy-wg] IPv6 access to K-root
- Next message (by thread): [address-policy-wg] IPv6 policy of making 200 /48 assignments
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Iljitsch van Beijnum
iljitsch at muada.com
Tue Mar 1 20:58:55 CET 2005
On 1-mrt-05, at 18:31, Tim Streater wrote: > 3) plan to provide IPv6 connectivity to organisations - yes, we will > certainly do that - to which it will assign /48s etc etc - no, we will > never do that as all our customers are LIRs. > 4) have a plan for making at least 200 /48 assignments to other > organisations etc etc - no, we will never assign such space as all our > customers have their own already. So what do you need IPv6 address space for apart from your own stuff? Seems to me that from an address allocation point of view, you are and endsite. > In short, I would advocate relaxing the rules about PI space. The trouble is that in IPv4 there is at least _some_ backpressure on PI because people need to qualify for a /24. In IPv6, we don't count addresses anymore, so all else being equal, MORE people would be able to get PI space. If that were to happen, we'd be in a lot of trouble. Iljitsch
- Previous message (by thread): [address-policy-wg] IPv6 access to K-root
- Next message (by thread): [address-policy-wg] IPv6 policy of making 200 /48 assignments
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]