[arin-ppml] proposal 2013-8
Rudolph Daniel
rudi.daniel at gmail.com
Thu Jan 23 05:32:41 EST 2014
I support the proposal as seen
Rudi Daniel
(information technologist)
784 430 9235
On Jan 22, 2014 6:41 PM, <arin-ppml-request at arin.net> wrote:
> Send ARIN-PPML mailing list submissions to
> arin-ppml at arin.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.arin.net/mailman/listinfo/arin-ppml
> or, via email, send a message with subject or body 'help' to
> arin-ppml-request at arin.net
>
> You can reach the person managing the list at
> arin-ppml-owner at arin.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ARIN-PPML digest..."
>
>
> Today's Topics:
>
> 1. Re: NRPM Policies 4.6 and 4.7 Suspended by ARIN Board
> (John Curran)
> 2. Re: [arin-council] FW: Section 4.4 Micro Allocation
> Conservation Update (prop-200) (Martin Hannigan)
> 3. Policy Proposal 2013-8 Subsequent Allocations for Additional
> Distrete Network Sites (CJ Aronson)
> 4. Re: Policy Proposal 2013-8 Subsequent Allocations for
> Additional Distrete Network Sites (Andrew Dul)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 22 Jan 2014 06:51:38 +0000
> From: John Curran <jcurran at arin.net>
> To: Martin Hannigan <hannigan at gmail.com>
> Cc: "arin-ppml at arin.net" <arin-ppml at arin.net>
> Subject: Re: [arin-ppml] NRPM Policies 4.6 and 4.7 Suspended by ARIN
> Board
> Message-ID: <2E15FDF6-7EFD-43EB-ABFB-95AB7BC55282 at arin.net>
> Content-Type: text/plain; charset="us-ascii"
>
> > On Jan 21, 2014, at 7:19 PM, Martin Hannigan <hannigan at gmail.com> wrote:
> >
> > It should include a reason why policy needed to be suspended
> unilaterally and clear competitive support. ARIN has real anti trust
> concerns I worry about as a member. The AC is %company heavy in some
> respects. We want to make sure this is clean.
>
> I have suggested to the AC that their recommendation take
> the form of a draft policy which would go through the normal
> policy development process (including Public Policy meeting
> deliberation and advancement based on community support.)
>
> FYI,
> /John
>
> John Curran
> President and CEO
> ARIN
>
> ------------------------------
>
> Message: 2
> Date: Tue, 21 Jan 2014 23:27:37 -1000
> From: Martin Hannigan <hannigan at gmail.com>
> To: Andrew Dul <andrew.dul at quark.net>
> Cc: "arin-ppml at arin.net" <arin-ppml at arin.net>
> Subject: Re: [arin-ppml] [arin-council] FW: Section 4.4 Micro
> Allocation Conservation Update (prop-200)
> Message-ID:
> <CAMDXq5NmVDsQdgOBsk5OyqCoDncs=E=
> o8s7Nh3vAi6dqQ+SPBQ at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Andrew,
>
>
> On Thu, Jan 16, 2014 at 5:05 PM, Andrew Dul <andrew.dul at quark.net> wrote:
>
> > Hi Marty,
> >
> > We'll be discussing this at the AC meeting next week. The 2 to 3
> > participants part is pretty straight forward change. The fee schedule
> >
>
> The majority of IXP operators in North America agree.
>
> part, we'll likely have to discuss if that is in scope for the PDP, if
> > not, that part would have to be moved out of the PDP process and
> > probably should be moved to the consultation process.
>
>
>
> I'm surprised at your comment since the existing policy says this:
>
> "ISPs and other organizations receiving these micro-allocations will be
> charged under the ISP fee schedule, while end-users will be charged under
> the fee schedule for end-users. "
>
> Why wasn't that moved out of the process? Regardless, I'm not particularly
> hung up on that as long as there is clarity as to who gets a "extra"
> benefit and who does not. The current language is indiscernible.
>
> Best,
>
> -M<
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.arin.net/pipermail/arin-ppml/attachments/20140121/51e2562f/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Wed, 22 Jan 2014 15:21:14 -0700
> From: CJ Aronson <cja at daydream.com>
> To: "arin-ppml at arin.net" <arin-ppml at arin.net>
> Subject: [arin-ppml] Policy Proposal 2013-8 Subsequent Allocations for
> Additional Distrete Network Sites
> Message-ID:
> <
> CAC6JZKS+BihMENiymuuNr+ocE7bM31MsWvTJ3j2BVGnO3aUeoQ at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi everyone,
>
> If you have feedback on this proposal please send it to this list. We will
> also be discussing the policy proposal at the upcoming PPC.
>
> Thanks!
> ----Cathy
>
>
> *Policy Proposal 2013-8 Subsequent Allocations for Additional Distrete
> Network Sites*
>
> *Problem Statement:*
>
> During the ARIN 32 PPM, ARIN staff noted in the Policy Implementation and
> Experience Report that the current Multiple Discrete Network Policy (MDN)
> does not contain criteria for new sites of an existing MDN customer.
>
> Current ARIN practice is to use the Immediate Need policy (NRPM 4.2.1.6).
>
> This policy proposal seeks to add NRPM text to clarify criteria for new
> sites of existing MDN customers.
>
>
>
> *Policy Statement:*
>
> IPv4:
>
> Add the following statement to section 4.5.4.
>
> Upon verification that the organization has already obtained connectivity
> at its new discrete network site, the new networks shall be allocated the
> minimum allocation size under section 4.2.1.5 unless the organization can
> demonstrate additional need using the immediate need criteria (4.2.1.6).
>
> IPv6:
>
> Add an additional reference to section 6.11.5.b such that it references
> both the initial allocation and subsequent allocation sections of the IPv6
> LIR policy.
>
> "Each network will be judged against the existing utilization criteria
> specified in 6.5.2 and 6.5.3 as if it were a separate organization..."
>
>
>
> *Comments*:
>
> a. Timetable for implementation: immediate
>
> b. This policy is being proposed based upon the Policy Implementation &
> Experience Report from ARIN 32.
>
>
> https://www.arin.net/participate/meetings/reports/ARIN_32/PDF/thursday/nobile-policy.pdf
>
> c: Older versions of the MDN policy did contain new network criteria. This
> criteria appears to have been dropped during subsequent rewrites of the MDN
> policy. "The organization must not allocate a CIDR block larger than the
> current minimum assignment size of the RIR (currently /20 for ARIN) to a
> new network." (https://www.arin.net/policy/archive/nrpm_20041015.pdf)
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.arin.net/pipermail/arin-ppml/attachments/20140122/8bd540e2/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 4
> Date: Wed, 22 Jan 2014 14:29:35 -0800
> From: Andrew Dul <andrew.dul at quark.net>
> To: arin-ppml at arin.net
> Subject: Re: [arin-ppml] Policy Proposal 2013-8 Subsequent Allocations
> for Additional Distrete Network Sites
> Message-ID: <52E0464F.4030504 at quark.net>
> Content-Type: text/plain; charset="iso-8859-1"
>
> As the originator of this policy proposal, I support this draft as written.
>
> Andrew
>
> On 1/22/2014 2:21 PM, CJ Aronson wrote:
> > Hi everyone,
> >
> > If you have feedback on this proposal please send it to this list. We
> > will also be discussing the policy proposal at the upcoming PPC.
> >
> > Thanks!
> > ----Cathy
> >
> > *Policy Proposal 2013-8 Subsequent Allocations for Additional Distrete
> > Network Sites
> > *
> >
> > *Problem Statement:*
> >
> > During the ARIN 32 PPM, ARIN staff noted in the Policy Implementation
> > and Experience Report that the current Multiple Discrete Network
> > Policy (MDN) does not contain criteria for new sites of an existing
> > MDN customer.
> >
> > Current ARIN practice is to use the Immediate Need policy (NRPM 4.2.1.6).
> >
> > This policy proposal seeks to add NRPM text to clarify criteria for
> > new sites of existing MDN customers.
> >
> >
> >
> > *Policy Statement:*
> >
> > IPv4:
> >
> > Add the following statement to section 4.5.4.
> >
> > Upon verification that the organization has already obtained
> > connectivity at its new discrete network site, the new networks shall
> > be allocated the minimum allocation size under section 4.2.1.5 unless
> > the organization can demonstrate additional need using the immediate
> > need criteria (4.2.1.6).
> >
> > IPv6:
> >
> > Add an additional reference to section 6.11.5.b such that it
> > references both the initial allocation and subsequent allocation
> > sections of the IPv6 LIR policy.
> >
> > "Each network will be judged against the existing utilization criteria
> > specified in 6.5.2 and 6.5.3 as if it were a separate organization..."
> >
> >
> >
> > *Comments*:
> >
> > a. Timetable for implementation: immediate
> >
> > b. This policy is being proposed based upon the Policy Implementation
> > & Experience Report from ARIN 32.
> >
> >
> https://www.arin.net/participate/meetings/reports/ARIN_32/PDF/thursday/nobile-policy.pdf
> >
> > c: Older versions of the MDN policy did contain new network criteria.
> > This criteria appears to have been dropped during subsequent rewrites
> > of the MDN policy. "The organization must not allocate a CIDR block
> > larger than the current minimum assignment size of the RIR (currently
> > /20 for ARIN) to a new network."
> > (https://www.arin.net/policy/archive/nrpm_20041015.pdf)
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > 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.
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.arin.net/pipermail/arin-ppml/attachments/20140122/3a50fa17/attachment.html
> >
>
> ------------------------------
>
> _______________________________________________
> ARIN-PPML mailing list
> ARIN-PPML at arin.net
> http://lists.arin.net/mailman/listinfo/arin-ppml
>
> End of ARIN-PPML Digest, Vol 103, Issue 7
> *****************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20140123/9c4e4258/attachment.htm>
More information about the ARIN-PPML
mailing list