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] 2015-03 New Policy Proposal (Assessment Criteria for IPv6 Initial Allocation Size)
- Previous message (by thread): [address-policy-wg] 2015-03 New Policy Proposal (Assessment Criteria for IPv6 Initial Allocation Size)
- Next message (by thread): [address-policy-wg] 2015-03 New Policy Proposal (Assessment Criteria for IPv6 Initial Allocation Size)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sascha Luck [ml]
apwg at c4inet.net
Tue May 12 14:34:22 CEST 2015
On Tue, May 12, 2015 at 01:28:39PM +0200, Jan Ingvoldstad wrote: >Apparently, my point was not very reader friendly, so I'll try again: >Routing-wise, someone with 64 billion billion billion addresses, have about >16 billion billion ways to route the entire IPv4 internet, within the >address space constraints of a /32 allocation. In theory, yes. But the policy currently contradicts itself to an extent. Section 3.8 of ripe-641 clearly states: "In IPv6 address policy, the goal of aggregation is considered to be the most important." ss3.4 and 3.5 bear that out also. Yet, s5.1.2 seems to exclude aggregation as a valid reason for an allocation. The Proposal merely attempts to remove this contradiction. rgds, Sascha Luck
- Previous message (by thread): [address-policy-wg] 2015-03 New Policy Proposal (Assessment Criteria for IPv6 Initial Allocation Size)
- Next message (by thread): [address-policy-wg] 2015-03 New Policy Proposal (Assessment Criteria for IPv6 Initial Allocation Size)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]