[arin-ppml] Additional modifications to Section 8.3 related to ASN's and legacy addresses

[Martin Hannigan]

John,

The intention is to place the communities right to know above the
transfer parties right to privacy with respect to legacy number
resources and legacy ASN's. It would also be useful for you in order
to provide all of us with relevant data as to how a market is
operating to the standards we are setting. I know the latter is
probably easily accomplished even with confidentiality restrictions in
place, but the former is much harder without a policy standard. Is
there a better way to do such a thing? In the absence of a needs test
for legacy nr/asn's for example, I don't see a lot of need for
confidentiality requirements.

Thoughts?

Best,

-M<



On Wed, May 23, 2012 at 2:12 AM, John Curran <jcurran at arin.net> wrote:
> On May 23, 2012, at 12:30 AM, Martin Hannigan wrote:
>
> .3.4 Notice of Refusal
>
> ARIN will provide a written and detailed notice that includes the
> specific reasons why when refusing any number resource or ASN transfer.
>  This
> notice will be provided to all parties to a transfer.
>
>
> Martin -
>
>    It is generally the recipient who has difficulty qualifying during a
> transfer,
>    and while the specific reason is often "Recipient can't demonstrate need
>    in accordance with policy", the proposed language suggests that more
>    detailed information should be returned to both the current resource
> holder
>    and intended recipient.  If that is the case, then it is important to
> note that
>    this information may contain technical & business planning information
> of
>    the intended recipient which is only known to ARIN via NDA and therefore
>
>    not readily releasable.
>
>    Of course, this may not be as frequent an issue given the legacy aspects
>    of the proposed policy change, but as written, the notice would appear
>    to apply to transfers of any resources and may run afoul of NDA terms
>    unless this disclosure is very clearly specified in the proposed policy,
>    and specifically authorized in advance by intended recipients when
>    applying to transfer resources.  Supplying this information to only the
>    recipient would not cause this problem (and we presently do provide
>    that information in the request ticket) but that may not meet your goals
>    for the proposed policy change.
>
> FYI,
> /John
>
> John Curran
> President and CEO
> ARIN
>