Here are some simplified text and a update the title. I think using an "at
least one" standard creates an appropriate burden for organizations
submitting reallocation or detailed reassignment requests while ensuring
POCs are notified and there is minimal validity based on the standard in
section 3
I like this approach. However, I have a question, do all the POC objects
need to be valid or does at least one of the POC objects need to be valid?
If we care we might want to be more specific on that point, I think it is
possible to read the current text either way right now.
I think I like at l
This seems completely reasonable to me.
--
Brian E Jones, CSP-SM, CSP-PO
NI&S Virginia Tech
bjo...@vt.edu
> On Oct 20, 2018, at 2:14 PM, Andrew Dul wrote:
>
> I'd like to propose to the community a rewrite of 2017-12 that would
> hopefully bring it in line with the Implementation B option of t
It reads well to me.
Mike Arbrouet, CISSP
From: ARIN-PPML on behalf of Owen DeLong
Sent: Wednesday, October 24, 2018 4:01:21 PM
To: Andrew Dul
Cc: ARIN-PPML List
Subject: Re: [arin-ppml] Board of Trustees Remands Recommended Draft Policy
ARIN-2017-12
Works
Works for me.
Owen
> On Oct 20, 2018, at 11:14 , Andrew Dul wrote:
>
> I'd like to propose to the community a rewrite of 2017-12 that would
> hopefully bring it in line with the Implementation B option of the Staff
> Implementation memo.
>
> What do others think of this approach?
>
> Andre
I'd like to propose to the community a rewrite of 2017-12 that would
hopefully bring it in line with the Implementation B option of the Staff
Implementation memo.
What do others think of this approach?
Andrew
===
Policy statement:
Insert one new section into NRPM 3:
3.7 POC Validation Upon R
On 31 July 2018, the ARIN Board of Trustees remanded Recommended Draft
Policy ARIN-2017-12: Require New POC Validation Upon Reassignment to the
Advisory Council, noting:
"The ARIN Board of Trustees remands ARIN Recommended Draft Policy
2017-12: Require New POC Validation Upon Reassignment to t
