[arin-ppml] Policy Proposal: Reduce all Minimum Allocation/Assignment units to /24
Sweeting, John
john.sweeting at twcable.com
Tue Apr 29 19:44:32 EDT 2014
Yes I meant 61, sorry
Sent from my iPhone
> On Apr 29, 2014, at 7:07 PM, "Michael Peddemors" <michael at linuxmagic.com> wrote:
>
> Derek,
>
> Just FYI, this is something that you might consider being 'fast tracked'
> by the supporters..
>
> "NANOG 61 is traveling to Bellevue, Washington for the second time!
> ,,,,,
> NANOG 61 takes place on June 2-4, 2014 and will offer a great
> opportunity to network with colleagues, freshen-up skills, learn
> advanced networking techniques, and discover new network applications.
> NANOG 61 will be hosted by our Premium Sponsor"
>
> So, this could happen very soon..
>
>
>> On 14-04-29 03:30 PM, Sweeting, John wrote:
>> Hi Derek,
>>
>> In a nutshell the shepherds assigned to this proposal have been asked to
>> worked this to have it available and present it as a “Recommended Draft
>> Policy” at the PPC at NANOG 60. If it continues to receive the
>> overwhelming support that it has enjoyed today then it could go to “Last
>> Call” following NANOG. There are a lot of moving pieces but it is
>> definitely doable. You can contact me off list if you would like more
>> specific information.
>>
>> Thanks,
>> John
>>
>> On 4/29/14, 6:17 PM, "Derek Calanchini" <derekc at cnets.net
>> <mailto:derekc at cnets.net>> wrote:
>>
>> So it appears this is highly supported so far, what needs to happen
>> to move it forward?
>>
>>
>> Best regards,
>>
>> Derek Calanchini
>> Owner
>> Creative Network Solutions
>> Phone: 916-852-2890
>> Fax: 916-852-2899
>>
>> "Adopt the metric system!"
>>
>> CNS LOGO
>>> On 4/29/2014 3:14 PM, Michael Peddemors wrote:
>>> And I support.. if it wasn't clear..
>>> I mentioned to the author that if this is tough to swallow, we
>>> should at least go down to a /22 everywhere..
>>>
>>> (We have an application going in as well for space, and we would
>>> be returning 3 /24's back upstream on acceptance as well, it would
>>> be nicer if we didn't have to pay the expense of a second upstream
>>> provider. So I also 'support' getting the board involved to
>>> expedite this)
>>>
>>>> On 14-04-29 02:57 PM, Randy Carpenter wrote:
>>>>
>>>> I support.
>>>>
>>>> I would want to make sure that someone who needs more than a /24,
>>>> could still get what they need immediately rather than only
>>>> getting a /24 (as long as what they need is available). I have
>>>> worked with several entities that are single-homed, and are using
>>>> a /22, but need a /21, or are using a /23 and need a /22. They
>>>> are all unable to get additional space form their upstream.
>>>> Allowing them to get what they need from ARIN would allow them to
>>>> return the old space to their upstream. It would benefit all.
>>>>
>>>>
>>>> thanks,
>>>> -Randy
>>>>
>>>>
>>>> ----- Original Message -----
>>>>> Template: ARIN-POLICY-PROPOSAL-TEMPLATE-3.0
>>>>>
>>>>> 1. Policy Proposal Name: Reduce all Minimum
>>>>> Allocation/Assignment units to
>>>>> /24
>>>>> 2. Proposal Originator
>>>>> a. name: Owen DeLong
>>>>> b. email: owen at delong.com c. telephone: 408-890-7992
>>>>> d. organization: Hurricane Electric
>>>>> 3. Date: 29 April, 2014
>>>>> 4. Problem Statement:
>>>>> As we approach runout, more and more end users and smaller ISPs
>>>>> will be
>>>>> unable to obtain space from their upstreams and will be seeking
>>>>> space from
>>>>> ARIN. In order to meet these needs to the extent possible and to
>>>>> make policy
>>>>> more fair to a broader range of the ARIN constituency, we should
>>>>> reduce the
>>>>> minimum assignment and allocation units to /24 across the board.
>>>>> 5. Policy statement:
>>>>> Change the minimum allocation and assignment unit for all IPv4
>>>>> single and
>>>>> multi homed instances to /20. This would include:
>>>>>
>>>>> 4.2.1.5 Change all occurrences of /20 and /22 to /24
>>>>> 4.2.2.1.1 Change all occurrences of /20 to /24, and change 16
>>>>> /24s to 1 /24.
>>>>> Remove the example about 12 /24s.
>>>>> 4.3.2.1 Change both occurrences of /20 to /24
>>>>> 4.9 Change /22 to /24
>>>>> 4.9.1 Change all instances of /22 to /24. Remove the reference
>>>>> to 4 /24s.
>>>>>
>>>>> 6. Comments:
>>>>> a. Timetable for implementation: Immediate, possibly
>>>>> through board action.
>>>>> b. Anything else
>>>>>
>>>>> END OF TEMPLATE
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> PPML
>>>>> You are receiving this message because you are subscribed to
>>>>> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
>>>>> Unsubscribe or manage your mailing list subscription at:
>>>>> http://lists.arin.net/mailman/listinfo/arin-ppml
>>>>> Please contact info at arin.net if you experience any issues.
>>>> _______________________________________________
>>>> PPML
>>>> You are receiving this message because you are subscribed to
>>>> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
>>>> Unsubscribe or manage your mailing list subscription at:
>>>> http://lists.arin.net/mailman/listinfo/arin-ppml
>>>> Please contact info at arin.net if you experience any issues.
>>
>>
>>
>> ------------------------------------------------------------------------
>> <http://www.avast.com/>
>>
>> This email is free from viruses and malware because avast! Antivirus
>> <http://www.avast.com/> protection is active.
>>
>>
>>
>> ------------------------------------------------------------------------
>> This E-mail and any of its attachments may contain Time Warner Cable
>> proprietary information, which is privileged, confidential, or subject
>> to copyright belonging to Time Warner Cable. This E-mail is intended
>> solely for the use of the individual or entity to which it is addressed.
>> If you are not the intended recipient of this E-mail, you are hereby
>> notified that any dissemination, distribution, copying, or action taken
>> in relation to the contents of and attachments to this E-mail is
>> strictly prohibited and may be unlawful. If you have received this
>> E-mail in error, please notify the sender immediately and permanently
>> delete the original and any copy of this E-mail and any printout.
>>
>>
>> _______________________________________________
>> PPML
>> You are receiving this message because you are subscribed to
>> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
>> Unsubscribe or manage your mailing list subscription at:
>> http://lists.arin.net/mailman/listinfo/arin-ppml
>> Please contact info at arin.net if you experience any issues.
>
>
>
> --
> "Catch the Magic of Linux..."
> ------------------------------------------------------------------------
> Michael Peddemors, President/CEO LinuxMagic Inc.
> Visit us at http://www.linuxmagic.com @linuxmagic
> ------------------------------------------------------------------------
> A Wizard IT Company - For More Info http://www.wizard.ca
> "LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd.
> ------------------------------------------------------------------------
> 604-682-0300 Beautiful British Columbia, Canada
>
> This email and any electronic data contained are confidential and intended
> solely for the use of the individual or entity to which they are addressed.
> Please note that any views or opinions presented in this email are solely
> those of the author and are not intended to represent those of the company.
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
More information about the ARIN-PPML
mailing list