I agree with this Draft policy.
This is clearly a legacy IPv4 policy. These reallocation requirements
were put in place to document use of IPv4 resources so that you could ask
for more. Without a free pool, this should not be required.
As we move to the future of IPv6, this appears to be an unneeded act, as
nearly everyone who has applied for IPv6 resources has received a block
that will last for a very long time, and from what I understand during
discussion of another proposal last year, no one has had to come back to
expand their IPv6 block. Thus, there is no need to publically document
usage in order to apply for more space. Thus, the requirement for this
should be dropped from the NRPM.
Albert Erdmann
Network Administrator
Paradise On Line Inc.
On Thu, 26 Jul 2018, Hunter, Kathleen wrote:
+1 to Owens thoughts on this. I know we will continue to do this even after the
policy is cleaned.
Kat Hunter
Comcast LIR
-----Original Message-----
From: ARIN-PPML <arin-ppml-boun...@arin.net> On Behalf Of Owen DeLong
Sent: Thursday, July 26, 2018 6:45 AM
To: Azinger, Marla <marla.azin...@ftr.com>
Cc: arin-ppml@arin.net
Subject: Re: [arin-ppml] Recommended Draft Policy ARIN-2018-3: Remove
Reallocation Requirements for Residential Market Assignments
I will point out that removing the requirement does not prevent anyone from
continuing to provide the information. It merely makes it optional instead of
mandatory.
In many cases, the reporting in question is an artifact of policy that was
specially crafted to aid CMTS-based providers in being able to obtain
sufficient IP space to actually provision networks while attempting to avoid
widespread and massive abuse through a gaping policy loophole. Given the
absence of an IPv4 free pool, that policy is no longer particularly applicable
and I believe some of it has already been eliminated. As such, this is, IMHO,
just some additional cleanup of the NRPM to further adapt to a post-IPv4 world.
Owen
On Jul 25, 2018, at 15:27 , Azinger, Marla <marla.azin...@ftr.com> wrote:
If I read this correct, you would be removing the requirement of public records
that display not just static re-allocations for a general geographic area, but
it would also remove Dynamic pool re-allocations.
If I saw what requirement is being removed correctly, in either respect should
anyone stop doing those type of Re-allocations, they will receive an increase
of abuse calls from law enforcement given one layer of useful data is being
halted. It also might increase geographic route issues because I have come
across some companies that sell geo filter software based off ARIN records.
Food for thought
Marla
-----Original Message-----
From: ARIN-PPML <arin-ppml-boun...@arin.net> On Behalf Of ARIN
Sent: Tuesday, July 24, 2018 11:06 AM
To: arin-ppml@arin.net
Subject: [arin-ppml] Recommended Draft Policy ARIN-2018-3: Remove
Reallocation Requirements for Residential Market Assignments
________________________________
WARNING: External email. Please verify sender before opening attachments or
clicking on links.
________________________________
On 19 July 2018, the ARIN Advisory Council (AC) advanced the following Draft
Policy to Recommended Draft Policy status:
ARIN-2018-3: Remove Reallocation Requirements for Residential Market
Assignments
The text of the Recommended Draft Policy is below, and may also be found at:
https://www.arin.net/policy/proposals/2018_3.html
You are encouraged to discuss all Recommended Draft Policies on PPML prior to
their presentation at the next ARIN Public Policy Consultation (PPC). PPML and
PPC discussions are invaluable to the AC when determining community consensus.
The PDP can be found at:
https://www.arin.net/policy/pdp.html
Draft Policies and Proposals under discussion can be found at:
https://www.arin.net/policy/proposals/index.html
Regards,
Sean Hopkins
Policy Analyst
American Registry for Internet Numbers (ARIN)
Recommended Draft Policy ARIN-2018-3: Remove Reallocation Requirements
for Residential Market Assignments
Advisory Council Statement of Conformance with Principles of Internet Number
Resource Policy:
This recommended draft policy is technically sound, creating a fair and
impartial number policy. The draft policy removes the Residential Market Area
record keeping and publication requirement placed upon one segment of the ISP
population for ARIN IPv4 allocations. Since this requirement does not apply to
IPv4 transfers it is a legacy element of policy sustaining administrative
overhead for a subset of the community. No concerns have been raised by the
community and there has been demonstrable support since its initial proposal.
Problem Statement:
Current number policy requires some organizations to create reallocations or
reassignments for residential subscribers. This requirement complicates record
keeping for ISPs. There is limited value today for requiring these records be
put into the ARIN database.
ARIN number policy for a long time has required ISPs to add a reallocation or
reassignment record for each of their subscriber address blocks. This policy
dates from the original cable allocations as a method to publicly show that a
portion of a larger block has been put into use.
Since ARIN no longer has a free pool of IPv4 addresses and requirements for
transfer are demonstrated without these records, this requirement is no longer
needed.
Furthermore, this requirement complicates reallocation & reassignment entry
into the ARIN database.3 Removing this requirement could reduce the complexity
required for accurately maintaining reallocation and/or reassignment records.
Policy statement:
Remove Section 4.2.3.7.3.1 (Residential Market Area) from the NRPM
Comments:
Timetable for Implementation: Immediate
_______________________________________________
ARIN-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:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact i...@arin.net if you experience any issues.
________________________________
This communication is confidential. Frontier only sends and receives email on
the basis of the terms set out at http://www.frontier.com/email_disclaimer.
_______________________________________________
ARIN-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:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact i...@arin.net if you experience any issues.
_______________________________________________
ARIN-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:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact i...@arin.net if you experience any issues.
_______________________________________________
ARIN-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:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact i...@arin.net if you experience any issues.
_______________________________________________
ARIN-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:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact i...@arin.net if you experience any issues.
