Send ARIN-PPML mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.arin.net/mailman/listinfo/arin-ppml
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of ARIN-PPML digest..."
Today's Topics:
1. Re: Against 2013-4 (Steven Ryerse)
2. Re: Against 2013-4 (John Curran)
3. Re: Against 2013-4 (Owen DeLong)
----------------------------------------------------------------------
Message: 1
Date: Tue, 4 Jun 2013 22:18:56 +0000
From: Steven Ryerse <[email protected]>
To: John Curran <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [arin-ppml] Against 2013-4
Message-ID:
<5b9e90747fa2974d91a54fcfa1b8ad120135e74...@eni-mail.eclipse-networks.com>
Content-Type: text/plain; charset="us-ascii"
John, you are right but when high level RFC changes are contemplated maybe
polling all of the organizations listed in the ARIN database for comments is
the proper thing to do. After all Legacy Holder allocations were made under
those RFCs et al.
From: John Curran [mailto:[email protected]]
Sent: Tuesday, June 04, 2013 12:53 PM
To: Steven Ryerse
Cc: Blake Dunlap; Kevin Kargel; [email protected]
Subject: Re: [arin-ppml] Against 2013-4
On Jun 4, 2013, at 10:52 AM, Steven Ryerse
<[email protected]<mailto:[email protected]>> wrote:
Of course we could ask everyone in the ARIN community to comment.
And before anyone says that they could comment if they wish, I don't see
anywhere in my Legacy paperwork that says I(they) have to participate in this
community to be a stakeholder. This community needs to be open minded and not
closed minded - and it needs to take into consideration all ARIN stakeholders
and not just the ones that decide to comment.
Steven -
The "ARIN community" is actually very, very large; it could be considered all
potentially affected parties, which transcends simply number resource
holders
in this region, and by definition it is impossible to proactively poll all
of them
for their views.
All welcome to participate, and we have done extensive outreach at
conferences
(such Interop, CES, Usenix, Comdex, Gartner, etc.) and via hundreds of
articles
and interviews in trade publications over the years.
While we are very open, there is indeed a threshold for having ones views
heard,
and that is actual participation in the policy process. Each time draft
policy is
published, that _is_ an invitation for all interested parties to comment; no
party
or interest has a unique privilege of being polled for their views on a
given draft
policy.
FYI,
/John
John Curran
President and CEO
ARIN
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.arin.net/pipermail/arin-ppml/attachments/20130604/fcf5b656/attachment-0001.html>
------------------------------
Message: 2
Date: Tue, 4 Jun 2013 22:34:43 +0000
From: John Curran <[email protected]>
To: Steven Ryerse <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [arin-ppml] Against 2013-4
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
On Jun 4, 2013, at 5:18 PM, Steven Ryerse
<[email protected]<mailto:[email protected]>> wrote:
John, you are right but when high level RFC changes are contemplated maybe
polling all of the organizations listed in the ARIN database for comments is
the proper thing to do. After all Legacy Holder allocations were made under
those RFCs et al.
Steven -
Polling any subset of the community runs a very real risk of bias in the
resulting input,
and since affected parties are more than those who were issued resources,
it is best
if those with an interest in number resource policy make their view known.
Note that many resource holders simply wish to use their IP number
resources; i.e.
they requested and received their resources and wish to be unmolested but
simply
use those resources in peace, and ARIN contacting all resource holders for
each new
draft policy would quickly rise to the level of being perceived as
"spam"...
Thanks,
/John
John Curran
President and CEO
ARIN
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.arin.net/pipermail/arin-ppml/attachments/20130604/13b5dc26/attachment-0001.html>
------------------------------
Message: 3
Date: Tue, 4 Jun 2013 16:32:12 -0700
From: Owen DeLong <[email protected]>
To: John Curran <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [arin-ppml] Against 2013-4
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
On an additional note, Steven, ARIN does not change RFCs...That is done by the
RFC-Editor and usually through the IETF process.
Owen
On Jun 4, 2013, at 15:34 , John Curran <[email protected]> wrote:
> On Jun 4, 2013, at 5:18 PM, Steven Ryerse <[email protected]>
> wrote:
>
>> John, you are right but when high level RFC changes are contemplated maybe
>> polling all of the organizations listed in the ARIN database for comments is
>> the proper thing to do. After all Legacy Holder allocations were made under
>> those RFCs et al.
>
> Steven -
>
> Polling any subset of the community runs a very real risk of bias in the
> resulting input,
> and since affected parties are more than those who were issued
> resources, it is best
> if those with an interest in number resource policy make their view
> known.
>
> Note that many resource holders simply wish to use their IP number
> resources; i.e.
> they requested and received their resources and wish to be unmolested
> but simply
> use those resources in peace, and ARIN contacting all resource holders
> for each new
> draft policy would quickly rise to the level of being perceived as
> "spam"...
>
> Thanks,
> /John
>
> John Curran
> President and CEO
> 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:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact [email protected] if you experience any issues.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.arin.net/pipermail/arin-ppml/attachments/20130604/a1fc6241/attachment.html>
------------------------------
_______________________________________________
ARIN-PPML mailing list
[email protected]
http://lists.arin.net/mailman/listinfo/arin-ppml
End of ARIN-PPML Digest, Vol 96, Issue 17
*****************************************
