[address-policy-wg] 2010-06 New Policy Proposal (Registration Requirements for IPv6 End User Assignments): discussion in the IPv6-WG mailing list
- Previous message (by thread): [address-policy-wg] 2010-06 New Policy Proposal (Registration Requirements for IPv6 End User Assignments): discussion in the IPv6-WG mailing list
- Next message (by thread): [address-policy-wg] 2010-06 New Policy Proposal (Registration Requirements for IPv6 End User Assignments): discussion in the IPv6-WG mailing list
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at inex.ie
Fri Sep 3 17:56:18 CEST 2010
On 03/09/2010 16:43, Remco van Mook wrote: > I guess it really depends on what you'd want to consider as more > important; ease of administration or aggregation. The policy makes the > assumption of large amounts of end user assignments being made - if you > want out both /48 and /56 from a single PoP and you're going to do both > in any significant quantity, I'd personally choose to use separate > blocks for the /56 and the /48 assignments to allow for easier > recycling. Then those blocks can have their own separate entry in the > database, each with a single assignment size. If you need to re-hash > block sizes at a later point, you can always change to a larger number > of smaller blocks in the database. Database entries are (relatively) > cheap. So the "assignment-size:" really means maximum assignment size rather than exact assignment size? Yes, certainly if you're large enough, you would go for separate blocks for /48 and /56 anyway. However, smaller operations may carve them from the same block for whatever reasons. Nick
- Previous message (by thread): [address-policy-wg] 2010-06 New Policy Proposal (Registration Requirements for IPv6 End User Assignments): discussion in the IPv6-WG mailing list
- Next message (by thread): [address-policy-wg] 2010-06 New Policy Proposal (Registration Requirements for IPv6 End User Assignments): discussion in the IPv6-WG mailing list
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]