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] The final /8 policy proposals, part 3.2
- Previous message (by thread): [address-policy-wg] The final /8 policy proposals, part 3.2
- Next message (by thread): [address-policy-wg] The final /8 policy proposals, part 3.2
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Masataka Ohta
mohta at necom830.hpcl.titech.ac.jp
Fri Sep 11 13:31:15 CEST 2009
Sander Steffann wrote: > Jim asked why we should change the policy at all for the final /8. I > hope I have given at least one good reason: new entrants. Michael > proposed to leave (further) decisions about the final /8 until IANA > runs out of IPv4 addresses. Another good reason to change the policy is recent development of NAT technology. Recent NAT even allows for end to end transparency that there is no reason for old entrants not to deploy NAT to reduce address consumption to leave room for new entrants. Masataka Ohta PS If we wisely allocate the final /8s, we will be ready to allocate class E and part of class D for unicast before we run out of classes A, B and C. That is, we don't need IPv6.
- Previous message (by thread): [address-policy-wg] The final /8 policy proposals, part 3.2
- Next message (by thread): [address-policy-wg] The final /8 policy proposals, part 3.2
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]