[arin-ppml] Deleting unnecessary NRPM 4 text
Jose R. de la Cruz III
jrdelacruz at acm.org
Fri Oct 9 09:03:09 EDT 2015
Good idea. But maybe the whole NPRM needs to be looked, and not just
removing sections. One way to go might be to inspect each section header
and decide if the policies included in it are relevant or should be joined
with other sections (maybe sections 4 & 6 should be only one).
On Thu, Oct 8, 2015 at 5:12 PM, Scott Leibrand <scottleibrand at gmail.com>
> In light of this afternoon's discussion about simplification of the NPRM,
> I thought I'd dust off a post-exhaustion NRPM 4 simplification proposal I
> wrote a couple years ago. There are a lot of parts that need updating in
> light of more recent modifications (expect another email later), but there
> are a few that seem rather simple and uncontroversial. Can anyone think of
> any reason not to submit a proposal with all four of these? Anyone
> interested in (co-)authoring it?
> 1. Delete from 4.1.6 Aggregation the text that reads “ARIN may reserve
> space to maximize aggregation possibilities until the implementation of
> section 10.4.2.2, at which time”
> Rationale: remove inoperative text
> 2. Delete section 188.8.131.52 Annual Renewal.
> Rationale: Remove operational details (already covered by the RSA and ARIN
> procedures) from NRPM.
> 3. Delete section 184.108.40.206.1. Use of /24
> Rationale: After exhaustion, many organizations can no longer get a /24
> from their upstream ISP, and need to be able to get their initial
> allocation from ARIN.
> 4. Delete section 220.127.116.11. VLSM
> Rationale: VLSM and CIDR are now standard practice, and don’t need to be
> called out in NRPM.
> 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:
> Please contact info at arin.net if you experience any issues.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ARIN-PPML