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. Consultation on ARIN IRR Roadmap Extended through 25 April
      2018 (ARIN)
   2. Comment on IRR Consultation (Osterweil, Eric)
   3. Re: Comment on IRR Consultation (John Curran)
   4. ASO Review Consultation 2018 (ARIN)
   5. Re: ASO Review Consultation 2018 (ARIN)
   6. Re: Consultation on ARIN IRR Roadmap Extended through 25
      April 2018 (Brian Jones)


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

Message: 1
Date: Wed, 31 Jan 2018 11:22:52 -0500
From: ARIN <i...@arin.net>
To: arin-consult@arin.net
Subject: [ARIN-consult] Consultation on ARIN IRR Roadmap Extended
        through 25 April 2018
Message-ID: <d8a5106b-00c9-0dd2-36f3-c69d5a4a0...@arin.net>
Content-Type: text/plain; charset=utf-8; format=flowed

Based on the level of community interest and the significance of the
work involved in improving the ARIN Internet Routing Registry (IRR), we
are extending the discussion period on the current consultation through
25 April 2018. The consultation text is available at:
https://www.arin.net/participate/acsp/community_consult/01-09-2018_irr.html

This extension will allow time for ARIN staff to present on this topic
at both the North American Network Operators Group (NANOG) meeting,
19-21 February in Atlanta, GA and at the upcoming ARIN 41 Public Policy
and Members Meeting, 15-18 April in Miami, Fl.

For details on both events, including remote participation options, visit:

NANOG 72:
https://www.nanog.org/
Presentation on 20 February at 10:00 AM EDT

ARIN 41:
https://www.arin.net/ARIN41

We encourage all interested individuals to provide comments to
arin-consult@arin.net. You can subscribe to this mailing list at:
http://lists.arin.net/mailman/listinfo/arin-consult.

Regards,

John Curran
President and CEO
American Registry for Internet Numbers (ARIN)





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

Message: 2
Date: Thu, 1 Feb 2018 18:03:40 +0000
From: "Osterweil, Eric" <eosterw...@verisign.com>
To: "arin-consult@arin.net" <arin-consult@arin.net>
Subject: [ARIN-consult] Comment on IRR Consultation
Message-ID: <d6e57c75-048c-4ba8-825c-b1ba6918d...@verisign.com>
Content-Type: text/plain; charset="utf-8"

To whom it may concern,

ARIN?s newly opened Community Consultation that solicits feedback on ARIN?s IRR 
Roadmap (posted on 09, January 2018) is an encouraging development.  We, at 
Verisign, are supportive of this initiative.  We believe it aligns well with 
our long-standing interests in Internet Security, Stability, and Resiliency and 
the community?s existing security-related needs to ensure the veracity of IRR 
objects (described in [RFC-7682).

Eric Osterweil

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.arin.net/pipermail/arin-consult/attachments/20180201/b6c29e2c/attachment-0001.html>

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

Message: 3
Date: Thu, 1 Feb 2018 18:27:23 +0000
From: John Curran <jcur...@arin.net>
To: "Osterweil, Eric" <eosterw...@verisign.com>
Cc: "arin-consult@arin.net" <arin-consult@arin.net>
Subject: Re: [ARIN-consult] Comment on IRR Consultation
Message-ID: <ca55680a-fd5f-4cff-bab5-d109ba859...@arin.net>
Content-Type: text/plain; charset="us-ascii"

On Feb 1, 2018, at 12:04 PM, Osterweil, Eric 
<eosterw...@verisign.com<mailto:eosterw...@verisign.com>> wrote:
...
ARIN's newly opened Community Consultation that solicits feedback on ARIN's IRR 
Roadmap (posted on 09, January 2018) is an encouraging development.  We, at 
Verisign, are supportive of this initiative.  We believe it aligns well with 
our long-standing interests in Internet Security, Stability, and Resiliency and 
the community's existing security-related needs to ensure the veracity of IRR 
objects (described in [RFC-7682).

Eric -

That's very clear and helpful feedback on this consultation.

Thanks!
/John

John Curran
President and CEO
ARIN

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.arin.net/pipermail/arin-consult/attachments/20180201/4253edae/attachment-0001.html>

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

Message: 4
Date: Fri, 2 Feb 2018 08:59:35 -0500
From: ARIN <i...@arin.net>
To: arin-consult@arin.net
Subject: [ARIN-consult] ASO Review Consultation 2018
Message-ID: <add605bc-1f11-b364-d954-9184f03bb...@arin.net>
Content-Type: text/plain; charset=utf-8; format=flowed

As a part of the Number Resource Organization (NRO), ARIN is seeking
community input on the NRO community consultation on the ASO review.

"The most recent ASO Review concluded with 18 recommendations, which the
NRO has resolved to accept. The first 17 recommendations are well
defined and practical, and can be implemented by actions of the NRO
Secretariat, or of the ASO Address Council, with respect to
administrative procedures, documentation, or in some cases adjustments
to agreements which are expected to be non-controversial.

The 18th recommendation of the Report is that "The NRO should initiate a
public consultation, involving the five RIR communities, to determine
the future structure of the ASO". The NRO EC has concluded to accept
that recommendation and is hereby launching a consultation on the issues
identified in the ASO Review Report."

The full Consultation is available for review at:

https://www.nro.net/aso-review-consultation-2018/

Issues to Address:

The scope of this consultation includes the structural implications of
issues identified by the ASO Review, including but not limited to:

      * Any updates and adjustments identified as required for
ASO-related documents
      * Any procedural clarifications and adjustments identified
      * Reported confusion of roles between ASO and NRO, and their 
components
      * Perceived complexity of relationships among NRO, ASO and ICANN
      * Relevance and cost to the RIRs of various ICANN engagement 
activities

Out of the Scope of this consultation are the following aspects:

      * Global Policy Development Process (GPDP)
      * ASO AC role with GPDP

Specific Questions:

The NRO EC is looking to specific answer to the following questions:

      * What adjustments, if any, should be made in order to address the
issues described above?
      * Should adjustments be limited to NRO MoU, ASO MoU, and/or ICANN
Bylaws
      * Over what timeframes should these adjustments be developed and
implemented
      * What strategic aspects should we pay attention to when
considering these adjustments?

Please provide comments to arin-consult@arin.net. All ARIN community
feedback will be forwarded on to the NRO. You can subscribe to this
mailing list at: http://lists.arin.net/mailman/listinfo/arin-consult.

This consultation will remain open through 5:00 PM EST on Wednesday, 28
February 2018.

Regards,

John Curran
President and CEO
American Registry for Internet Numbers (ARIN)





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

Message: 5
Date: Fri, 9 Feb 2018 10:29:42 -0500
From: ARIN <i...@arin.net>
To: arin-consult@arin.net
Subject: Re: [ARIN-consult] ASO Review Consultation 2018
Message-ID: <50943a0a-8707-5544-282c-5d5a1b668...@arin.net>
Content-Type: text/plain; charset=utf-8; format=flowed

The NRO EC and ASO AC Joint Response to the 2017 Independent ASO Review 
Recommendations has been published on the NRO website for community 
consideration.

https://www.nro.net/nro-ec-and-aso-ac-joint-response-to-the-2017-independent-aso-review-recommendations/

Regards,

Communications and Member Services
American Registry for Internet Numbers (ARIN)


On 2/2/18 8:59 AM, ARIN wrote:
> As a part of the Number Resource Organization (NRO), ARIN is seeking
> community input on the NRO community consultation on the ASO review.
>
> "The most recent ASO Review concluded with 18 recommendations, which the
> NRO has resolved to accept. The first 17 recommendations are well
> defined and practical, and can be implemented by actions of the NRO
> Secretariat, or of the ASO Address Council, with respect to
> administrative procedures, documentation, or in some cases adjustments
> to agreements which are expected to be non-controversial.
>
> The 18th recommendation of the Report is that "The NRO should initiate a
> public consultation, involving the five RIR communities, to determine
> the future structure of the ASO". The NRO EC has concluded to accept
> that recommendation and is hereby launching a consultation on the issues
> identified in the ASO Review Report."
>
> The full Consultation is available for review at:
>
> https://www.nro.net/aso-review-consultation-2018/
>
> Issues to Address:
>
> The scope of this consultation includes the structural implications of
> issues identified by the ASO Review, including but not limited to:
>
>      * Any updates and adjustments identified as required for
> ASO-related documents
>      * Any procedural clarifications and adjustments identified
>      * Reported confusion of roles between ASO and NRO, and their 
> components
>      * Perceived complexity of relationships among NRO, ASO and ICANN
>      * Relevance and cost to the RIRs of various ICANN engagement 
> activities
>
> Out of the Scope of this consultation are the following aspects:
>
>      * Global Policy Development Process (GPDP)
>      * ASO AC role with GPDP
>
> Specific Questions:
>
> The NRO EC is looking to specific answer to the following questions:
>
>      * What adjustments, if any, should be made in order to address the
> issues described above?
>      * Should adjustments be limited to NRO MoU, ASO MoU, and/or ICANN
> Bylaws
>      * Over what timeframes should these adjustments be developed and
> implemented
>      * What strategic aspects should we pay attention to when
> considering these adjustments?
>
> Please provide comments to arin-consult@arin.net. All ARIN community
> feedback will be forwarded on to the NRO. You can subscribe to this
> mailing list at: http://lists.arin.net/mailman/listinfo/arin-consult.
>
> This consultation will remain open through 5:00 PM EST on Wednesday, 28
> February 2018.
>
> Regards,
>
> John Curran
> President and CEO
> American Registry for Internet Numbers (ARIN)
>
>
>



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

Message: 6
Date: Tue, 13 Feb 2018 19:05:36 +0000
From: Brian Jones <bjo...@vt.edu>
To: "<arin-consult@arin.net>" <arin-consult@arin.net>
Subject: Re: [ARIN-consult] Consultation on ARIN IRR Roadmap Extended
        through 25 April 2018
Message-ID:
        <CANyqO+F0LJi+8N5kt8eKhcndo-OZv5hq9ZAykuodzDxm6=h...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

I agree that this is an effort worth pursuing. I do have security concerns
about how authentication and authorization occurs.

I would recommend focusing efforts around a set of agreed upon standards
and remove any mention of ? best practices? from the language. That is an
overloaded term that can mean anything to anyone, whereas a set of agreed
upon standards should allow for clearer and more efficient operation.  (See
last bullet that includes ?best practices?.)

fwiw
?
Brian

On Wed, Jan 31, 2018 at 11:22 AM ARIN <i...@arin.net> wrote:

> Based on the level of community interest and the significance of the
> work involved in improving the ARIN Internet Routing Registry (IRR), we
> are extending the discussion period on the current consultation through
> 25 April 2018. The consultation text is available at:
> https://www.arin.net/participate/acsp/community_consult/01-09-2018_irr.html
>
> This extension will allow time for ARIN staff to present on this topic
> at both the North American Network Operators Group (NANOG) meeting,
> 19-21 February in Atlanta, GA and at the upcoming ARIN 41 Public Policy
> and Members Meeting, 15-18 April in Miami, Fl.
>
> For details on both events, including remote participation options, visit:
>
> NANOG 72:
> https://www.nanog.org/
> Presentation on 20 February at 10:00 AM EDT
>
> ARIN 41:
> https://www.arin.net/ARIN41
>
> We encourage all interested individuals to provide comments to
> arin-consult@arin.net. You can subscribe to this mailing list at:
> http://lists.arin.net/mailman/listinfo/arin-consult.
>
> Regards,
>
> John Curran
> President and CEO
> American Registry for Internet Numbers (ARIN)
>
>
>
> _______________________________________________
> 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/20180213/a92ce22a/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 65, Issue 1
*******************************************

Reply via email to