Send ARIN-consult mailing list submissions to
        arin-consult@arin.net

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.arin.net/mailman/listinfo/arin-consult
or, via email, send a message with subject or body 'help' to
        arin-consult-requ...@arin.net

You can reach the person managing the list at
        arin-consult-ow...@arin.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of ARIN-consult digest..."


Today's Topics:

   1. Re: Amended ACSP Consultation: Expanding the Size of the ARIN
      Board of Trustees (Brian Jones)
   2. Re: Consultation on Open ACSP Suggestions (Owen DeLong)


----------------------------------------------------------------------

Message: 1
Date: Wed, 11 Apr 2018 13:26:32 -0400
From: Brian Jones <bjo...@vt.edu>
To: David Farmer <far...@umn.edu>
Cc: "<arin-consult@arin.net>" <arin-consult@arin.net>
Subject: Re: [ARIN-consult] Amended ACSP Consultation: Expanding the
        Size of the ARIN Board of Trustees
Message-ID:
        <canyqo+fvza2_yysrric7se7ymal2lyk-krccravtc8p0ot8...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

See inline



On Tue, Apr 10, 2018 at 2:13 PM, David Farmer <far...@umn.edu> wrote:

> I am not opposed to the idea of expanding the board, a change from six to
> nine elected board members with the CEO as an ex officio member seems
> reasonable to me. However, I cannot support the current proposal as
> written.  The primary flaw I see in the current proposal is that it simply
> expands the board without modifying how the board is selected. I believe
> the issue at hand is as much about how the board is selected as much as it
> is about the size of the board.
>
> Currently, a combined slate of candidates is proposed by the nominating
> committee for the two board positions up for election each year, and the
> two candidates with the most votes from the combined slate are selected.
> This sometimes degrades into a popularity contest.  Name recognition plays
> as big a role as the qualifications of a candidate in determining who
> prevails, potentially leaving the board without necessary expertise even
> though the slate may have included candidates with the necessary
> expertise.  Just adding another position selected by this same process, 
> selecting
> the three candidates with the most votes from the combined slate, I fear
> will only have a nominal effect on the composition of the board, and simply
> result in a larger board with many of the same issues.
>
> In addition to expanding the board, I suggest each of the three board
> positions up for election have a separate slate of two or more candidates
> each year, instead of the current process with it's combined slate.
> This allows the nominating committee, with advice from the board, to select
> candidates with the expertise needed by the board to compete for a single
> position and ensure a candidate with the necessary expertise will prevail
> in the election. I don't think criteria for each position should be
> enshrined in the bylaws, as the needs of the board will change and evolve
> over time, but many of the issues discussed recently should be considered;
> sector representation, organization types, etc...
>

?+1 David's comments. I believe this is the way forward if the board needs
expanding in size. There should also be more specific instructions from the
board to the nomination committee about specific needs or skill sets
expected for the positions.?

--
Brian


>
> Thanks.
>
> On Tue, Apr 10, 2018 at 10:00 AM, ARIN <memb...@arin.net> wrote:
>
>> (You are only receiving this final version.)
>>
>> In May 2017, the ARIN Board of Trustees proposed expansion of the size of
>> the Board of Trustees in order to increase opportunities for diversity in
>> the background of Board members, including geographical and gender
>> representation. This proposal was the topic of an energetic community
>> consultation with mixed outcome indicating both support and concerns with
>> such a change. The ARIN Board considered the outcome of the consultation,
>> but ultimately the measure did not achieve the four-fifths approval
>> threshold necessary for changing ARIN's Bylaws.
>>
>> In February of this year, the ARIN Board discussed an additional issue
>> related to the present size of the Board: specifically, the challenge that
>> a smaller Board poses when engaging in strategic discussions, for example
>> in regard to long-term direction or relationships with other Internet
>> organizations. While many of these topics are discussed with the community
>> prior to decision (e.g. formation of the NRO, support for the IANA
>> Stewardship Transition), it is often up to the ARIN Board of Trustees to
>> decide whether to explore these initiatives when they are at an early
>> stage. There is a very wide diversity of the Internet ecosystem that can be
>> affected by ARIN's strategic direction and this includes Internet service
>> providers of all sizes and types (transit, access, etc.), Internet online
>> and content industries, data center and cloud operators, educational and
>> government networks, commercial firms, and civil society. While the
>> Trustees elected by the community often have a bro
>>  ad knowledge of the Internet ecosystem, seven Trustees is a relatively
>> small group to evaluate impacts across the entire Internet ecosystem.
>>
>> As a result of this discussion, the ARIN Board agreed to initiate a new
>> community consultation to expand the number of elected Board members from
>> six to nine, in order to allow for wider representation of the Internet
>> community during Board discussions.
>> Board proposal:
>>
>> ARIN should add three more elected voting seats to the Board of Trustees,
>> raising the current six (two elected per year) to nine (three elected per
>> year). New Board seats are to be added to the Board in a phased manner -
>> one per year in the 2018 thru 2020 elections as noted below
>> *       October 2018: 3 Board members will be elected for 2019; 8 Trustee
>> board (9 if the appointed seat is used)
>> *       October 2019: 3 Board members will be elected for 2020; 9 Trustee
>> board (10 if the appointed seat is used)
>> *       October 2020: 3 Board members will be elected for 2021; 10
>> Trustee board (11 if the appointed seat is used)
>>
>> The link to the proposed Bylaws amendment necessary to effect such a
>> change can be viewed at: https://www.arin.net/about_us/
>> bot/20180216/exhibit_e.pdf
>>
>> We are seeking community feedback on this proposed change to the size of
>> the ARIN Board of Trustees. This consultation will remain open for at least
>> 30 days.
>>
>> Please provide comments to arin-consult@arin.net. You can subscribe to
>> this mailing list at: http://lists.arin.net/mailman/listinfo/arin-consult
>> .
>>
>> Discussion on arin-consult@arin.net will close on 14 May 2018.
>>
>> If you have any questions, please contact us at i...@arin.net.
>>
>> Regards,
>>
>> John Curran
>> President and CEO
>> American Registry for Internet Numbers (ARIN)
>>
>>
>
>
> --
> ===============================================
> David Farmer               Email:far...@umn.edu
> Networking & Telecommunication Services
> Office of Information Technology
> University of Minnesota
> 2218 University Ave SE        Phone: 612-626-0815
> Minneapolis, MN 55414-3029   Cell: 612-812-9952
> ===============================================
>
> _______________________________________________
> ARIN-Consult
> You are receiving this message because you are subscribed to the ARIN
> Consult Mailing
> List (ARIN-consult@arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-consult Please contact the
> ARIN Member Services
> Help Desk at i...@arin.net if you experience any issues.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.arin.net/pipermail/arin-consult/attachments/20180411/8e43a39a/attachment-0001.html>

------------------------------

Message: 2
Date: Wed, 11 Apr 2018 10:34:42 -0700
From: Owen DeLong <o...@delong.com>
To: John Curran <jcur...@arin.net>
Cc: "<arin-consult@arin.net>" <arin-consult@arin.net>
Subject: Re: [ARIN-consult] Consultation on Open ACSP Suggestions
Message-ID: <ea5105c3-b570-42e3-b86e-5cbf1cea9...@delong.com>
Content-Type: text/plain; charset="utf-8"

John,

The first question in the survey is an utter failure from my perspective as I 
don?t see priorities in terms of categories.

There are some things in each category which I consider relatively higher 
priority vs. other things in those same categories.

For example, I would consider the following to be relatively high priority (In 
email order. not necessarily priority order):

        2017.16
        2017.21
        2015.20
        2016.8
        2013.28
        2017.28
        2017.22
        2017.8

You?ll notice that those are spread all over the categories.

Owen


> On Apr 11, 2018, at 09:48 , John Curran <jcur...@arin.net> wrote:
> 
> Owen - 
>  
> It would be most helpful if you (and others) could complete the referenced 
> survey <https://www.surveymonkey.com/r/OpenACSP2018 
> <https://www.surveymonkey.com/r/OpenACSP2018>>, as that allows for relative 
> prioritization (e.g. please set higher those items you support) and allow us 
> to develop a work plan for 2019 that accomplishes what the community most 
> desires. 
> 
> Thanks!
> /John
> 
> John Curran
> President and CEO
> ARIN
> 
>> On 11 Apr 2018, at 12:40 PM, Owen DeLong <o...@delong.com 
>> <mailto:o...@delong.com>> wrote:
>> 
>> 
>> 
>>> On Apr 11, 2018, at 08:54 , ARIN <i...@arin.net <mailto:i...@arin.net>> 
>>> wrote:
>>> 
>>> Through 11 May, we will be collecting feedback from the community on
>>> many of the open ACSP Suggestions that are not currently on the ARIN
>>> 2018 Work Plan.
>>> 
>>> There is a survey available at
>>> https://www.surveymonkey.com/r/OpenACSP2018 
>>> <https://www.surveymonkey.com/r/OpenACSP2018> where you can rank
>>> suggestions by category (type of improvement), and you also have the
>>> option to rate the value of each open suggestion.
>>> 
>>> The information gleaned from the survey will be one of the inputs used
>>> to help determine which suggestions will be included ARIN's 2019 Work
>>> Plan. For your reference, the suggestions included in the survey have
>>> been grouped as follows:
>>> 
>>> New Account Management Functionality:
>>> 
>>>    * 2017.16 - Allow registered brokers to be added to transfer tickets
>> 
>> Support
>> 
>>>    * 2017.21 - Display Account Type of Org IDs
>> 
>> Support
>> 
>>>    * 2017.24 - Allow NET objects of Simple Reassignments to hold POC objects
>> 
>> Neutral, slightly opposed. Don?t see the benefit and therefore question the 
>> value
>> of doing so.
>> 
>>>    * 2017.25 - Allow Changes to Org Handle in a Detailed Reassignment 
>>> Without Requiring Deletion
>> 
>> Support
>> 
>>> Account Management Improvements:
>>> 
>>>    * 2013.16 - Association of Multiple Networks With A Customer
>> 
>> Not entirely clear on the problem being solved or the benefit.
>> 
>>>    * 2017.3 - Allow Multiple Primary Billing Contacts
>> 
>> Confused. Multiple billing contacts makes sense to me. By definition, 
>> primary implies a singular value.
>> 
>>> New ARIN Online Features:
>>> 
>>>    * 2015.20 - Marking ARIN Online Messages as Read
>> 
>> Support
>> 
>>>    * 2016.8 - List All Related Unvalidated POCs
>> 
>> Support
>> 
>>>    * 2017.13 - Sorting of Allocations / Assignments by org-id in ARIN Online
>> 
>> Support
>> 
>>> ARIN Online Improvements:
>>> 
>>>    * 2013.28 - POC Validation Message Removal Upon Validation
>> 
>> Support
>> 
>>>    * 2017.28 - Improvements to POC Searches Within ARIN Online
>> 
>> Support
>> 
>>> Billing Functionality Improvements:
>>> 
>>>    * 2012.5 - Bulk Billing Management
>> 
>> Support
>> 
>>>    * 2016.06 - Add PO Field to Invoices in ARIN Online
>> 
>> Neutral
>> 
>>>    * 2016.12 - Interactive Fee Calculator
>> 
>> Neutral, but opposed to a fee increase to enable it.
>> 
>>> Reporting Improvements:
>>> 
>>>    * 2018.2 - Improvements to Whois Inaccuracy Reporting
>> 
>> Support
>> 
>>> RESTful Web Services (RWS) Improvements:
>>> 
>>>    * 2011.17 - Define access restrictions for APIs
>> 
>> Neutral to slightly opposed. Do not see sufficient benefit for expense.
>> 
>>>    * 2012.20 - Remove result limit for Whois-RWS child network queries
>> 
>> Support
>> 
>>>    * 2015.18 - Sort Order For Utilization reports from RESTful Whois
>> 
>> Support
>> 
>>>    * 2016.11 - Improvements to RESTful Web Services
>> 
>> Support
>> 
>>>    * 2017.22 - Disable OT&E API keys (RegRWS) in Production Systems
>> 
>> Support
>> 
>>>    * 2017.23 - Changes To RegRWS Access With API Key Authentication
>> 
>> Neutral
>> 
>>> Security Improvements:
>>> 
>>>    * 2017.1 - Two-factor functionality improvement
>> 
>> Neutral
>> 
>>> Website Improvements:
>>> 
>>>    * 2017.9 - Changes to IP Address Widget
>> 
>> Neutral
>> 
>>>    * 2017.8 - Chat button for ARIN.NET <http://arin.net/> website
>> 
>> Support
>> 
>>>    * 2016.03 - Provide Web UI for RDAP
>> 
>> Neutral to slightly opposed. Don?t see sufficient benefit vs. cost unless it
>> essentially comes automatically with RDAP. In reality, there will be plenty 
>> of
>> external RDAP Web-UIs created by third parties, so I don?t see much point 
>> here
>> unless it replaces Whois-RWS and/or Reg-RWS and those products are EOLd as a
>> result.
>> 
>> Owen
>> 
>> 
>> _______________________________________________
>> ARIN-Consult
>> You are receiving this message because you are subscribed to the ARIN 
>> Consult Mailing
>> List (ARIN-consult@arin.net <mailto:ARIN-consult@arin.net>).
>> Unsubscribe or manage your mailing list subscription at:
>> http://lists.arin.net/mailman/listinfo/arin-consult 
>> <http://lists.arin.net/mailman/listinfo/arin-consult> Please contact the 
>> ARIN Member Services
>> Help Desk at i...@arin.net <mailto:i...@arin.net> if you experience any 
>> issues.
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.arin.net/pipermail/arin-consult/attachments/20180411/3c237702/attachment.html>

------------------------------

Subject: Digest Footer

_______________________________________________
ARIN-consult mailing list
ARIN-consult@arin.net
http://lists.arin.net/mailman/listinfo/arin-consult


------------------------------

End of ARIN-consult Digest, Vol 67, Issue 23
********************************************

Reply via email to