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]/

[address-policy-wg] RE: [ipv6-wg] additional IPv6 allocation (ripe-512 issues)

• Previous message (by thread): [address-policy-wg] Re: [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
• Next message (by thread): [address-policy-wg] RE: [ipv6-wg] additional IPv6 allocation (ripe-512 issues)

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

Sander Steffann sander at steffann.nl
Tue Jul 19 13:29:09 CEST 2011

Hi,

> GV> That would be perfect.. I was just reading the comments
> sequentially... and just assumed that when an ISP gets through the HD
> ratio stuff on his first /32, that he will gets the neighbor /32. In
> that case the ISP needs to make a new address plan policy, which would
> not be as clean as if he would have had a /31 to start off with. With
> the /29 there would be no issue at all on this matter.

That is what is happening now. A proposal for changing this is on the way :)
Sander

• Previous message (by thread): [address-policy-wg] Re: [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
• Next message (by thread): [address-policy-wg] RE: [ipv6-wg] additional IPv6 allocation (ripe-512 issues)

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

[ ipv6-wg Archives ]