In the case where ARIN issued then let's keep calling it by its name, so nobody can think otherwise and is always aware that something that was once issued can be revoked if rules surrounding that are circumvented, because it is not uncommon many thing that once issued that becomes a irrevocable property and orgs can do whatever they want with resources regardless of the policies. For other cases where not issued than can call something else like ARIN-registered or something.

Fernando

On 03/11/2022 18:11, Owen DeLong via ARIN-PPML wrote:
Rather than “ARIN-issued”, I suggest either “ARIN-registered” or “ARIN-recorded” or “ARIN-managed”.

ARIN did not issue many of the allocations and assignments currently recorded in the ARIN database.

Otherwise, I support the policy as written. In fact, it is sufficiently non-operable in not changing the way in which ARIN manages the registry that I would even nominate it for consideration as an editorial change.

Owen


On Nov 3, 2022, at 08:46, ARIN <[email protected]> wrote:

The following Draft Policy has been revised:
* ARIN-2022-12: Direct Assignment Language Update
Revised text is below and can be found at:
https://www.arin.net/participate/policy/drafts/2022_12/
You are encouraged to discuss all Draft Policies on PPML. The AC will evaluate the discussion to assess the conformance of this Draft Policy with ARIN's Principles of Internet number resource policy as stated in the Policy Development Process (PDP). Specifically, these principles are:
* Enabling Fair and Impartial Number Resource Administration
* Technically Sound
* Supported by the Community
The PDP can be found at:
https://www.arin.net/participate/policy/pdp/
Draft Policies and Proposals under discussion can be found at:
https://www.arin.net/participate/policy/drafts/
Regards,
Sean Hopkins
Senior Policy Analyst
American Registry for Internet Numbers (ARIN)
Draft Policy ARIN-2022-12: ARIN-2022-12: Direct Assignment Language Update
Problem Statement:
As a result of ARIN’s fee harmonization direct assignments are no longer being utilized within ARIN databases therefore language around that has been deprecated and should be modernized.
Policy Statement:
Section 3.6.3:
Remove “direct assignment” from “This policy applies to every Organization that has a direct assignment, direct allocation, or AS number from ARIN (or one of its predecessor registries) or a reallocation from an upstream ISP.” Section 4.2.2, paragraph 1: change “direct assignments or allocations” to “ARIN-issued IPv4 addresses” Section 4.2.2, paragraph 2: change “direct allocations, direct assignments, re-allocations or reassignments” to “ARIN-issued IPv4 addresses, re-allocations or reassignments” Section 4.3.2: change “direct assignments or allocations” to “ARIN-issued IPv4 addresses” Section 6.5.8: change “Direct Assignments from ARIN to End-user Organizations” to “End-user Allocations” Section 8.5.4: change “direct assignments or allocations” to “ARIN-issued IPv4 addresses” Section 8.5.6: change “direct assignments or allocations” to “ARIN-issued IPv4 addresses”
Timetable for Implementation: Immediate
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please [email protected] you experience any issues.


_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please [email protected]  if you experience any issues.
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.

Reply via email to