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] 2006-05 New Draft Document Published (PI Assignment Size)
- Previous message (by thread): [address-policy-wg] 2006-05 New Draft Document Published (PI Assignment Size)
- Next message (by thread): [address-policy-wg] 2006-05 New Draft Document Published (PI Assignment Size)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Richard Hartmann
richih.mailinglist at gmail.com
Thu Oct 21 23:48:07 CEST 2010
On Thu, Oct 21, 2010 at 14:10, Gert Doering <gert at space.net> wrote: > If that's not sufficiently clear, we might need to reword. The wording is clear once you know the intended meaning. Yet, after reading it twice, I was not certain that I understood the intent and all consequences of this rule before I read your explanantion. IMO, the main problem is that "additional" is ambivalent even though it's used in the first sentence, as well. Thus, I would suggest: The RIPE NCC will assign additional IPv4 addresses to an End User in order to pad the assignment size to a multiple of a /24 if an End User demonstrates: [...] Cumulatively, no more than 248 padding IPv4 addresses may be assigned to any particular End User for the purposes outlined in section 6.10. Richard
- Previous message (by thread): [address-policy-wg] 2006-05 New Draft Document Published (PI Assignment Size)
- Next message (by thread): [address-policy-wg] 2006-05 New Draft Document Published (PI Assignment Size)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]