Send arin-suggestions mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.arin.net/mailman/listinfo/arin-suggestions
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-suggestions digest..."


Today's Topics:

   1. Response to Suggestion 2013.8: DEPLOY TWO-FACTOR
      AUTHENTICATION (ARIN)
   2. Response to Suggestion 2013.12: PERSISTENT FIELD FOR PURCHASE
      ORDER NUMBER IN BILLING INFORMATION (ARIN)
   3. New ACSP Suggestion 2013.13: AVAILABILITY OF TICKET
      INFORMATION TO ALL POCS OF AN ORG ID (ARIN)
   4. Response to Suggestion 2013.14: SIGN ARIN'S       FORWARD DNS ZONE
      (ARIN)


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

Message: 1
Date: Wed, 22 May 2013 13:11:17 -0400
From: ARIN <[email protected]>
To: [email protected]
Subject: [ARIN-Suggestions] Response to Suggestion 2013.8: DEPLOY
        TWO-FACTOR      AUTHENTICATION
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"

ARIN has issued its initial response to ACSP Suggestion 2013.8. The 
suggestion and response text are provided below. This suggestion remains 
open and is available at:

https://www.arin.net/participate/acsp/suggestions/2013-8.html

Regards,

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

****
Suggestion: *

I propose that ARIN deploy two factor authentication across as many 
systems as practical. I would suggest giving non-staff multiple options 
including Smartphone support, hardware tokens, and possibly SMS backup. 
The system should be a "one to many" in cases with individuals having 
multiple ORG's.

*Response:*

We agree that enhanced authentication options would be an added benefit 
to security-conscious ARIN members. We will look into various methods 
and will propose a solution at the fall 2013 member meeting that can be 
prioritized accordingly.

This suggestion will remain open.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.arin.net/pipermail/arin-suggestions/attachments/20130522/9575807d/attachment-0001.html>

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

Message: 2
Date: Wed, 22 May 2013 13:12:59 -0400
From: ARIN <[email protected]>
To: [email protected]
Subject: [ARIN-Suggestions] Response to Suggestion 2013.12: PERSISTENT
        FIELD FOR PURCHASE ORDER NUMBER IN BILLING INFORMATION
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"

ARIN has issued its initial response to ACSP Suggestion 2013.12. The 
suggestion and response text are provided below. This suggestion remains 
open and is available at:

https://www.arin.net/participate/acsp/suggestions/2013-12.html

Regards,

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

****
Suggestion: *

Allow ARIN-online Billing information to include a persistent field for 
PO#, that will get printed on the invoice in the PO # filed automatically.

*Response:*

Thank you for your suggestion to include a persistent field for a 
purchase order number that will get printed on the invoice in the 
purchase order # field automatically. During development we will likely 
allow both a persistent (static) as well as a dynamic PO # according to 
each organization's specific needs. We will put this into the 
development queue as soon as possible, noting that we have a couple of 
significant development efforts underway for the next few months. 
Therefore it may be several months before we are able to move this into 
implementation.

This suggestion will remain open.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.arin.net/pipermail/arin-suggestions/attachments/20130522/ee345554/attachment-0001.html>

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

Message: 3
Date: Wed, 22 May 2013 13:15:04 -0400
From: ARIN <[email protected]>
To: [email protected]
Subject: [ARIN-Suggestions] New ACSP Suggestion 2013.13: AVAILABILITY
        OF TICKET INFORMATION TO ALL POCS OF AN ORG ID
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"

A new suggestion was received through the ACSP, and was assigned 
number2013.13 upon receipt of confirmation.

The text of the Suggestion is available at:


https://www.arin.net/participate/acsp/suggestions/2013-13.html

ARIN will issue an initial response within 10 business days.

Regards,

Communications and Member Services

American Registry for Internet Numbers (ARIN)


****
Suggestion: *


Make all ARIN-online tickets available to all contacts of the ORG.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.arin.net/pipermail/arin-suggestions/attachments/20130522/fad57afa/attachment-0001.html>

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

Message: 4
Date: Wed, 22 May 2013 13:17:45 -0400
From: ARIN <[email protected]>
To: [email protected]
Subject: [ARIN-Suggestions] Response to Suggestion 2013.14: SIGN
        ARIN'S  FORWARD DNS ZONE
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"

ARIN has issued its initial response to ACSP Suggestion 2013.14. The 
suggestion and response text are provided below. This suggestion remains 
open and is available at:

https://www.arin.net/participate/acsp/suggestions/2013-14.html

Regards,

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

****
Suggestion: *

The arin.net zone and in particular www.arin.net does not seem to be DNS 
Sec signed. It would be good for ARIN to demonstrate their leadership in 
the Internet technical community and sign their forward DNS zone, 
arin.net. As an example both Lacnic and RIPE have signed their forward 
zones.

If this means changing DNS registrars, then please do so.

Thank you.

*Response:*

We will add this additional feature to a planned upgrade to our existing 
DNSSEC signing services and roll out signed forward zones that ARIN is 
authoritative for by Q2 of 2014. This suggestion will remain open.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.arin.net/pipermail/arin-suggestions/attachments/20130522/4cf4104a/attachment-0001.html>

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

_______________________________________________
arin-suggestions mailing list
[email protected]
http://lists.arin.net/mailman/listinfo/arin-suggestions


End of arin-suggestions Digest, Vol 23, Issue 3
***********************************************

Reply via email to