I am assuming that the change to correct the typo where I said /20 instead of 
/24 will still have the support of the community. This has been mentioned 
elsewhere during the discussion, but otherwise, yes, I agree with you and David.

Owen

On Apr 30, 2014, at 11:22 AM, John Springer <sprin...@inlandnet.com> wrote:

> The analysis by David is, in my opinion, correct. This policy proposal is 
> receiving what in my experience is an unprecedented amount of community 
> support, _AS_WRITTEN_. Changes to the text require support be reiterated, 
> which might be unwanted and harmful to the text speed of the process. Further 
> desired changes should be submitted separately to avoid interfering with the 
> momentum that has been generated.
> 
> The community is speaking and the AC is listening. What I am hearing is get 
> busy and get 'er done. If the policy proposal can be supported as written, it 
> should be. Any changes to the text as written will have to be listened to and 
> responded to and cannot speed things up.
> 
> I am _NOT_ saying do not dissent, only that the conversation that ensues will 
> take time.
> 
> Not to put words in Marty's mouth, but that is how I interpret what he is 
> saying.
> 
> John Springer
> 
> On Wed, 30 Apr 2014, David Huberman wrote:
> 
>> Derek,
>>  
>> Marty can be a bit gruff - it's part of his charm :)  He's actually trying 
>> very hard to help you achieve your goals.  His observation you quoted is 
>> borne of wisdom of
>> dealing with the policy process for many years.   Some may agree, or may not 
>> agree.  I happened to agree strongly with him.
>>  
>> Owen's proposal, without modifications (or at least, not the one proposed so 
>> far), has the best chance of succeeding, and doing so quickly.
>>  
>> Just my opinion.
>>  
>> /david
>> David R Huberman
>> Microsoft Corporation
>> Senior IT/OPS Program Manager (GFS)
>> _______________________________________________________________________________________________________________________________________________________________________
>> From: arin-ppml-boun...@arin.net <arin-ppml-boun...@arin.net> on behalf of 
>> Derek Calanchini <der...@cnets.net>
>> Sent: Tuesday, April 29, 2014 6:13 PM
>> To: arin-ppml@arin.net
>> Subject: Re: [arin-ppml] Policy Proposal: Reduce all Minimum 
>> Allocation/Assignment units to /24  
>> Martin,
>> You seem very negative about this, disagreeing for the sake of disagreeing 
>> is counter productive.  Perhaps you could explain your concerns giving 
>> actual reasons,
>> potential fallout, issues, etc in the hopes of making it better....
>>  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 5:15 PM, Martin Hannigan wrote:
>> Owens change is simple and fast. Meddling beyond that is asking for trouble. 
>>  It's a no op. Leave it alone. 
>> Bring that to the PPC at NANOG and this is dead. 
>> On Tuesday, April 29, 2014, Jimmy Hess <mysi...@gmail.com> wrote:
>>      On Tue, Apr 29, 2014 at 12:58 PM, Owen DeLong <o...@delong.com> wrote:
>> 
>>      I support the proposed change as written.
>> 
>>      In addition,  since Multihomed ISPs no longer have a different minimum
>>      allocation, I suggest    removing the distinction between Multihomed
>>      and non-Multihomed ISPs:
>> 
>>         o 4.2.1.5     Delete the sentence that says "For multihomed ISPs...."
>>         Remove multi-homed distinction and requirements for initial
>>      allocations to ISPs.
>>            o Delete section  4.2.2.1  Standard or non-multihomed  and 
>> subsections.
>> 
>>            o Rename section 4.2.2.2 to  remove references to Multihomed
>> 
>>      Prepend     "When requesting a  /24,  demonstrate the efficient
>>      utilization of a minimum contiguous or non-contiguous  /27  (two /28s)
>>      from an upstream."
>> 
>>      [Regardless if multihomed or not]
>> 
>>      > 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: o...@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@arin.net).
>>      > Unsubscribe or manage your mailing list subscription at:
>>      > http://lists.arin.net/mailman/listinfo/arin-ppml
>>      > Please contact i...@arin.net if you experience any issues.
>> 
>>      --
>>      -JH
>>      _______________________________________________
>>      PPML
>>      You are receiving this message because you are subscribed to
>>      the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).
>>      Unsubscribe or manage your mailing list subscription at:
>>      http://lists.arin.net/mailman/listinfo/arin-ppml
>>      Please contact i...@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@arin.net).
>> Unsubscribe or manage your mailing list subscription at:
>> http://lists.arin.net/mailman/listinfo/arin-ppml
>> Please contact i...@arin.net if you experience any issues.
>> _______________________________________________________________________________________________________________________________________________________________________
>> [avast-mail-stamp.png]
>> This email is free from viruses and malware because avast! Antivirus 
>> protection is active.
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact i...@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@arin.net).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-ppml
Please contact i...@arin.net if you experience any issues.

Reply via email to