Re: [address-policy-wg] 2015-05 Discussion Period extended until 13 May 2016 (Last /8 Allocation Criteria Revision)
you may find reading the actual last /8 policy informative.
Last /8 is not really get affected by this policy. - Additional /22 IPv4 allocations can be only provided from address space outside 185/8
this is misleading or just sadly misinformed last /8 is not an address range, it is a state reached once the ncc had only that address range and continues on irrespective of additions or subtractions of space to the ncc's pool. randy
Thanks Randy, below is what you wrote on Apri 15:
i do not support pigs at the last /8 trough the purpose of the single last /8 allocation was to allow NEW ENTRY. pigs coming back to the trough every 18 months is not new anything.
randy
can you please tell me what you meant from "last /8 allocation" there? Cheers, Arash Naderpour P.S my understanding from 2015-05 is that it divides the current pool into 2 separate parts, last allocation of /8 and additional free IP pool received from IANA. -----Original Message----- From: Randy Bush [mailto:randy@psg.com] Sent: Tuesday, 10 May 2016 11:44 AM To: Arash Naderpour <arash_mpc@parsun.com> Cc: RIPE address policy WG <address-policy-wg@ripe.net> Subject: Re: [address-policy-wg] 2015-05 Discussion Period extended until 13 May 2016 (Last /8 Allocation Criteria Revision) you may find reading the actual last /8 policy informative.
Last /8 is not really get affected by this policy. - Additional /22 IPv4 allocations can be only provided from address space outside 185/8
this is misleading or just sadly misinformed last /8 is not an address range, it is a state reached once the ncc had only that address range and continues on irrespective of additions or subtractions of space to the ncc's pool. randy
P.S my understanding from 2015-05 is that it divides the current pool into 2 separate parts, last allocation of /8 and additional free IP pool received from IANA.
that's nice. as i said a bit ago, you may want to read the last /8 policy and not start trying to redifine terms.
On Tue, May 10, 2016 at 3:44 AM, Randy Bush <randy@psg.com> wrote:
you may find reading the actual last /8 policy informative.
Last /8 is not really get affected by this policy. - Additional /22 IPv4 allocations can be only provided from address space outside 185/8
this is misleading or just sadly misinformed
last /8 is not an address range, it is a state reached once the ncc had only that address range and continues on irrespective of additions or subtractions of space to the ncc's pool.
minor correction, it is a state that was reached once IANA allocated the last /8 to all the RIR's, and it affect _all_ address space after that point. -- Roger Jorgensen | ROJO9-RIPE rogerj@gmail.com | - IPv6 is The Key! http://www.jorgensen.no | roger@jorgensen.no
Il 11/05/2016 09:02, Roger Jørgensen ha scritto:
On Tue, May 10, 2016 at 3:44 AM, Randy Bush <randy@psg.com> wrote:
you may find reading the actual last /8 policy informative.
Last /8 is not really get affected by this policy. - Additional /22 IPv4 allocations can be only provided from address space outside 185/8 this is misleading or just sadly misinformed
last /8 is not an address range, it is a state reached once the ncc had only that address range and continues on irrespective of additions or subtractions of space to the ncc's pool. minor correction, it is a state that was reached once IANA allocated the last /8 to all the RIR's, and it affect _all_ address space after that point.
If I am not wrong standing on the information collected on this list the new allocation criteria was triggered when first allocation from 185/8 has been made. Please see Ingrid Wijte email 20/04/2016 to the list [...] The RIPE NCC started to allocate from 185/8 on 14 September 2012, when we could no longer satisfy a request for address space without touching 185/8. That moment triggered section 5.1 that states that RIPE NCC members can request a one time /22 allocation (1,024 IPv4 addresses). [...] My understanding is that the policy was already there but the community (we) at that date considered fair end up the good part of cake before triggering the new rule Rumors says that there are a lot of suspicius allocation done just one or two weeks before triggering the "last /8" regards Riccardo -- Ing. Riccardo Gori e-mail: rgori@wirem.net Mobile: +39 339 8925947 Mobile: +34 602 009 437 Profile: https://it.linkedin.com/in/riccardo-gori-74201943 WIREM Fiber Revolution Net-IT s.r.l. Via Cesare Montanari, 2 47521 Cesena (FC) Tel +39 0547 1955485 Fax +39 0547 1950285 -------------------------------------------------------------------- CONFIDENTIALITY NOTICE This message and its attachments are addressed solely to the persons above and may contain confidential information. If you have received the message in error, be informed that any use of the content hereof is prohibited. Please return it immediately to the sender and delete the message. Should you have any questions, please contact us by re- plying to info@wirem.net Thank you WIREM - Net-IT s.r.l.Via Cesare Montanari, 2 - 47521 Cesena (FC) --------------------------------------------------------------------
On Wed, May 11, 2016 at 9:22 AM, Riccardo Gori <rgori@wirem.net> wrote:
Il 11/05/2016 09:02, Roger Jørgensen ha scritto:
<snip>
minor correction, it is a state that was reached once IANA allocated the last /8 to all the RIR's, and it affect _all_ address space after that point.
If I am not wrong standing on the information collected on this list the new allocation criteria was triggered when first allocation from 185/8 has been made.
Please see Ingrid Wijte email 20/04/2016 to the list [...] The RIPE NCC started to allocate from 185/8 on 14 September 2012, when we could no longer satisfy a request for address space without touching 185/8. That moment triggered section 5.1 that states that RIPE NCC members can request a one time /22 allocation (1,024 IPv4 addresses). [...]
... too early in the morning, you're right. My point was that it affect all IPv4 addresses after that point in time, not just 185. -- Roger Jorgensen | ROJO9-RIPE rogerj@gmail.com | - IPv6 is The Key! http://www.jorgensen.no | roger@jorgensen.no
participants (4)
-
Arash Naderpour -
Randy Bush -
Riccardo Gori -
Roger Jørgensen