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/[email protected]/

[ipv6-wg] additional IPv6 allocation (ripe-512 issues)

Previous message (by thread): [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
Next message (by thread): [ipv6-wg] additional IPv6 allocation (ripe-512 issues)

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Sander Steffann sander at steffann.nl
Tue Jul 19 11:32:39 CEST 2011

Hi Gunter,

> GV> An issue I see with this policy is that it does not support
> pro-active address planning for the longer term and may end up in
> fragmented non-summarizable address space within an organization. Mainly
> because the newly required address space will be different block and
> will as result require new address planning policy within the
> organization itself.

I don't understand your comment. The idea of the policy proposal is to automatically grow the existing /32 to a /29. That results in a single /29 for an ISP.

- Sander

Previous message (by thread): [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
Next message (by thread): [ipv6-wg] additional IPv6 allocation (ripe-512 issues)

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ ipv6-wg Archives ]