You’re making little sense here.
If we refer to ARIN issued, then we’re literally excluding addresses not issued
by ARIN from the policy, which I believe is not the intent.
Owen
> On Nov 3, 2022, at 15:06, Fernando Frediani wrote:
>
> In the case where ARIN issued then let's keep calling it
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
No, I think the end result would be “6.5.8: End-user Allocations”.
Owen
> On Nov 3, 2022, at 10:47, Brian Jones wrote:
>
>
>
>
>> On Nov 3, 2022, at 11:46 AM, ARIN mailto:i...@arin.net>>
>> wrote:
>>
>> Section 6.5.8: change “Direct Assignments from ARIN to End-user
>> Organizations” to
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
> On Nov 3, 2022, at 11:46 AM, ARIN wrote:
>
> Section 6.5.8: change “Direct Assignments from ARIN to End-user
> Organizations” to “End-user Allocations”
>
So the end result would be “End-user Allocations to End-user Organizations” in
section 6.5.8? Not sure that Header reads well. If it
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
