From andrew.dul at quark.net Fri Apr 1 11:59:46 2016 From: andrew.dul at quark.net (Andrew Dul) Date: Fri, 1 Apr 2016 08:59:46 -0700 Subject: [ARIN-consult] Fw: [ARIN-Suggestions] New Suggestion - ACSP 2016.4 - Waiting List for 2 Byte ASNs In-Reply-To: References: <56FC3708.1090103@arin.net> Message-ID: <56FE9AF2.80409@quark.net> This suggestion would seem to be about who gets which number resources when, and thus perhaps should be handled by a policy change to the PDP. Do others feel the same way? I'm happy to write a policy proposal to start that process if others believe that would be beneficial to the community. Andrew On 3/30/2016 5:17 PM, Scott Leibrand wrote: > There are valid technical reasons, pertaining to communities, why ISP > networks with multihomed downstream BGP customers would be better > served by ASNs that can be represented by a two-byte number, with the > other two bytes all zeros. Those technical reasons do not apply, > AFAIK, to edge networks, only to transit providers with BGP-speaking > customers who want to use communities to control route announcements. > > -Scott > > On Wed, Mar 30, 2016 at 5:13 PM, David Huberman > > wrote: > > Apologies, but I have this data analysis done, and I dont want to > lose it. I can resend when the consultation officially opens. > > > I just did a quick data analysis of the DFZ found on one of my > routers. > > There are 601,729 unique routes originating from and transiting > through 53,511 ASNs. > > 71,170 routes (11.8%) originate from or propagate through a 4-byte > ASN. > There are 10,244 (19.1%) unique 4-byte ASNs in my copy of the table. > > Given this data, I'm unclear why the registry should be treating > 4-byte ASNs as anything but a single contiguous pool, as policy > currently states. > > ________________________________________ > From: arin-suggestions-bounces at arin.net > > > on behalf of ARIN > > > Sent: Wednesday, March 30, 2016 4:28 PM > To: arin-suggestions at arin.net > Subject: [ARIN-Suggestions] New Suggestion - ACSP 2016.4 - Waiting > List for 2 Byte ASNs > > We received the following suggestion on 18 March: > > Suggestion Details: > > Description: Waiting list for 2 Byte ASNs > > Value to Community: One member said to me: > > Ticket from ARIN "We have noted your request for a 2-byte ASN. ARIN is > out of 2-byte ASN's in its inventory. We get them returned voluntarily > from time to time. If we have one at the time of issuance, we will > issue > it to your organization. If we do not have a 2-byte in inventory > at that > time, your organization will receive the standard 4-byte ASN. " > > Member comment "if they are really out - a waitinglist would be > nice...." > > On 30 March, we sent the following response to the submitter: > > Thank you for your suggestion numbered 2016.04 - Waiting List for > 2 Byte > ASNs. > > Background > > The NRPM included instructions in the past for ARIN staff to > remove any > distinction between 2-byte and 4-byte in the issuance of AS numbers. > This particular policy language has since been retired in the NRPM. > > Staff has followed policy regarding issuance of AS numbers, but has > often had lower numbered, classic 2-byte, AS numbers available over > time. We would either receive them in our new delegations from the > IANA, > obtain them from customer returns of AS numbers, or through > revocations > of AS numbers due to non-payment of registration fees. Although ARIN > expects to no longer receive AS numbers from the IANA inside the > classic > 2-byte range, we do expect to continue reclaiming them through returns > and revocations going forward. > > Some AS number requests today continue to specifically ask for an AS > number from the classic 2-byte range. In those situations we relay to > the customer that we have noted their special request and that we will > accommodate it at the issuance phase of the ticket process if one is > available at the time. > > The Suggestion > > We understand your suggestion is to establish a waiting list for AS > numbers from the classic 2-byte range for those customers who > specifically request one when ARIN does not have them available. This > waiting list would be similar to the IPv4 waiting list for unmet > requests, but managed separately for AS numbers. Organizations > would be > placed on this AS number waiting list, and when one became available > through reclamation at ARIN, it would be slated for the organization > first on the waiting list. > > Staff Action > > ARIN staff can create a waiting list for 2-byte AS numbers if there is > favor from the community to establish one. ARIN staff will open a > consultation on the topic to gather feedback and take appropriate > action > based on information received through that process. > > Thank you for participating in the ARIN Consultation and Suggestion > Process. We will leave this suggestion open until a consultation has > been completed on this topic and an implementation plan has been > established. > > Regards, > > Communications and Member Services > American Registry for Internet Numbers (ARIN) > > > _______________________________________________ > arin-suggestions mailing list > arin-suggestions at arin.net > http://lists.arin.net/mailman/listinfo/arin-suggestions > _______________________________________________ > ARIN-Consult > You are receiving this message because you are subscribed to the > ARIN Consult Mailing > List (ARIN-consult at 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 info at arin.net if you > experience any issues. > > > > > _______________________________________________ > ARIN-Consult > You are receiving this message because you are subscribed to the ARIN Consult Mailing > List (ARIN-consult at 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 info at arin.net if you experience any issues. -------------- next part -------------- An HTML attachment was scrubbed... URL: From owen at delong.com Fri Apr 1 15:44:43 2016 From: owen at delong.com (Owen DeLong) Date: Fri, 1 Apr 2016 12:44:43 -0700 Subject: [ARIN-consult] [ARIN-Suggestions] New Suggestion - ACSP 2016.4 - Waiting List for 2 Byte ASNs In-Reply-To: <56FE9AF2.80409@quark.net> References: <56FC3708.1090103@arin.net> <56FE9AF2.80409@quark.net> Message-ID: If it happens at all, it should happen through the PDP. Personally, I think that this is yet another excuse for further delays in 32-bit ASN integration and we shouldn?t be supporting it. Owen > On Apr 1, 2016, at 08:59 , Andrew Dul wrote: > > This suggestion would seem to be about who gets which number resources when, and thus perhaps should be handled by a policy change to the PDP. Do others feel the same way? > > I'm happy to write a policy proposal to start that process if others believe that would be beneficial to the community. > > Andrew > > On 3/30/2016 5:17 PM, Scott Leibrand wrote: >> There are valid technical reasons, pertaining to communities, why ISP networks with multihomed downstream BGP customers would be better served by ASNs that can be represented by a two-byte number, with the other two bytes all zeros. Those technical reasons do not apply, AFAIK, to edge networks, only to transit providers with BGP-speaking customers who want to use communities to control route announcements. >> >> -Scott >> >> On Wed, Mar 30, 2016 at 5:13 PM, David Huberman > wrote: >> Apologies, but I have this data analysis done, and I dont want to lose it. I can resend when the consultation officially opens. >> >> >> I just did a quick data analysis of the DFZ found on one of my routers. >> >> There are 601,729 unique routes originating from and transiting through 53,511 ASNs. >> >> 71,170 routes (11.8%) originate from or propagate through a 4-byte ASN. >> There are 10,244 (19.1%) unique 4-byte ASNs in my copy of the table. >> >> Given this data, I'm unclear why the registry should be treating 4-byte ASNs as anything but a single contiguous pool, as policy currently states. >> >> ________________________________________ >> From: arin-suggestions-bounces at arin.net > on behalf of ARIN > >> Sent: Wednesday, March 30, 2016 4:28 PM >> To: arin-suggestions at arin.net >> Subject: [ARIN-Suggestions] New Suggestion - ACSP 2016.4 - Waiting List for 2 Byte ASNs >> >> We received the following suggestion on 18 March: >> >> Suggestion Details: >> >> Description: Waiting list for 2 Byte ASNs >> >> Value to Community: One member said to me: >> >> Ticket from ARIN "We have noted your request for a 2-byte ASN. ARIN is >> out of 2-byte ASN's in its inventory. We get them returned voluntarily >> from time to time. If we have one at the time of issuance, we will issue >> it to your organization. If we do not have a 2-byte in inventory at that >> time, your organization will receive the standard 4-byte ASN. " >> >> Member comment "if they are really out - a waitinglist would be nice...." >> >> On 30 March, we sent the following response to the submitter: >> >> Thank you for your suggestion numbered 2016.04 - Waiting List for 2 Byte >> ASNs. >> >> Background >> >> The NRPM included instructions in the past for ARIN staff to remove any >> distinction between 2-byte and 4-byte in the issuance of AS numbers. >> This particular policy language has since been retired in the NRPM. >> >> Staff has followed policy regarding issuance of AS numbers, but has >> often had lower numbered, classic 2-byte, AS numbers available over >> time. We would either receive them in our new delegations from the IANA, >> obtain them from customer returns of AS numbers, or through revocations >> of AS numbers due to non-payment of registration fees. Although ARIN >> expects to no longer receive AS numbers from the IANA inside the classic >> 2-byte range, we do expect to continue reclaiming them through returns >> and revocations going forward. >> >> Some AS number requests today continue to specifically ask for an AS >> number from the classic 2-byte range. In those situations we relay to >> the customer that we have noted their special request and that we will >> accommodate it at the issuance phase of the ticket process if one is >> available at the time. >> >> The Suggestion >> >> We understand your suggestion is to establish a waiting list for AS >> numbers from the classic 2-byte range for those customers who >> specifically request one when ARIN does not have them available. This >> waiting list would be similar to the IPv4 waiting list for unmet >> requests, but managed separately for AS numbers. Organizations would be >> placed on this AS number waiting list, and when one became available >> through reclamation at ARIN, it would be slated for the organization >> first on the waiting list. >> >> Staff Action >> >> ARIN staff can create a waiting list for 2-byte AS numbers if there is >> favor from the community to establish one. ARIN staff will open a >> consultation on the topic to gather feedback and take appropriate action >> based on information received through that process. >> >> Thank you for participating in the ARIN Consultation and Suggestion >> Process. We will leave this suggestion open until a consultation has >> been completed on this topic and an implementation plan has been >> established. >> >> Regards, >> >> Communications and Member Services >> American Registry for Internet Numbers (ARIN) >> >> >> _______________________________________________ >> arin-suggestions mailing list >> arin-suggestions at arin.net >> http://lists.arin.net/mailman/listinfo/arin-suggestions >> _______________________________________________ >> ARIN-Consult >> You are receiving this message because you are subscribed to the ARIN Consult Mailing >> List (ARIN-consult at 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 info at arin.net if you experience any issues. >> >> >> >> _______________________________________________ >> ARIN-Consult >> You are receiving this message because you are subscribed to the ARIN Consult Mailing >> List (ARIN-consult at 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 info at arin.net if you experience any issues. > > _______________________________________________ > ARIN-Consult > You are receiving this message because you are subscribed to the ARIN Consult Mailing > List (ARIN-consult at 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 info at arin.net if you experience any issues. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rs at seastrom.com Fri Apr 1 16:35:02 2016 From: rs at seastrom.com (Robert Seastrom) Date: Fri, 1 Apr 2016 16:35:02 -0400 Subject: [ARIN-consult] [ARIN-Suggestions] New Suggestion - ACSP 2016.4 - Waiting List for 2 Byte ASNs In-Reply-To: <56FE9AF2.80409@quark.net> References: <56FC3708.1090103@arin.net> <56FE9AF2.80409@quark.net> Message-ID: <1E8D2726-51F8-4847-90DA-5DCB11015815@seastrom.com> > On Apr 1, 2016, at 11:59 AM, Andrew Dul wrote: > > I'm happy to write a policy proposal to start that process if others believe that would be beneficial to the community. Could we start with a problem statement that describes what problem we would be solving that isn't already adequately addressed by having ASNs be 8.3-transferable number resources? -r From scottleibrand at gmail.com Fri Apr 1 20:50:29 2016 From: scottleibrand at gmail.com (Scott Leibrand) Date: Fri, 1 Apr 2016 17:50:29 -0700 Subject: [ARIN-consult] [ARIN-Suggestions] New Suggestion - ACSP 2016.4 - Waiting List for 2 Byte ASNs In-Reply-To: <1E8D2726-51F8-4847-90DA-5DCB11015815@seastrom.com> References: <56FC3708.1090103@arin.net> <56FE9AF2.80409@quark.net> <1E8D2726-51F8-4847-90DA-5DCB11015815@seastrom.com> Message-ID: If the demand for 2-byte ASNs is lower than the recovery rate of unused ones, then it would seem more efficient to just have ARIN hand them out (via waiting list) to people who claim a technical need for 2-byte instead of 4-byte ASN. If the demand exceeds the zero-effort supply, then 8.3 transfers will fill the gap, but if ARIN just hands out its recovered 2-byte ASNs to organizations who'd be fine with 4-byte, then we're artificially constraining the supply of 2-byte ASNs, and forcing up the price to the point where it is worth the time of buyers to contact people who would otherwise give their 2-byte ASNs back to ARIN and try to get them to transfer them instead. I would like to see an estimate of the number of 2-byte and 4-byte ASNs recovered and assigned in the last year, the number of organizations requesting 2-byte ASNs vs. those happy with 4-byte, and the number of 2-byte and 4-byte ASNs transferred under 8.3. Depending on those numbers, I could either support a policy proposal to set up a 2-byte ASN request process and waiting list, or I might decide it's not worth the trouble. With regard to the policy vs. operational practice question: If we need technical criteria for requesting 2-byte ASNs, then I think policy is appropriate. But if we can't agree on what those should be, or the numbers are such that it doesn't look like we need to restrict who can get on the 2-byte waiting list, then I would say that letting ARIN staff run the waiting list as an operational matter based on community consultation would be a much quicker and lower-overhead way to do the right thing. -Scott On Fri, Apr 1, 2016 at 1:35 PM, Robert Seastrom wrote: > > > On Apr 1, 2016, at 11:59 AM, Andrew Dul wrote: > > > > I'm happy to write a policy proposal to start that process if others > believe that would be beneficial to the community. > > Could we start with a problem statement that describes what problem we > would be solving that isn't already adequately addressed by having ASNs be > 8.3-transferable number resources? > > -r > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.dul at quark.net Sat Apr 2 14:02:21 2016 From: andrew.dul at quark.net (Andrew Dul) Date: Sat, 2 Apr 2016 11:02:21 -0700 Subject: [ARIN-consult] [ARIN-Suggestions] New Suggestion - ACSP 2016.4 - Waiting List for 2 Byte ASNs In-Reply-To: <1E8D2726-51F8-4847-90DA-5DCB11015815@seastrom.com> References: <56FC3708.1090103@arin.net> <56FE9AF2.80409@quark.net> <1E8D2726-51F8-4847-90DA-5DCB11015815@seastrom.com> Message-ID: <5700092D.2080208@quark.net> On 4/1/2016 1:35 PM, Robert Seastrom wrote: >> On Apr 1, 2016, at 11:59 AM, Andrew Dul wrote: >> >> I'm happy to write a policy proposal to start that process if others believe that would be beneficial to the community. > Could we start with a problem statement that describes what problem we would be solving that isn't already adequately addressed by having ASNs be 8.3-transferable number resources? > The problem as I understand it is that ARIN will receive 2-byte ASNs as returns over time, and these ASNs have perceived or additional value to organizations compared to 4-byte ASNs. Will 8.3 ASNs transfers meet the needs of some organizations, yes. The question is what to do with the 2-byte ASNs that will end up in ARIN's inventory for various reasons. How should ARIN allocate these 2-byte ASNs? Should they be given to the next requester, regardless of technical need for a 2-byte ASN? (What are the technical qualifications we should use if there is a specific technical need? e.g. provides transit to more than 1 ASN?) Should they be held in reserve? Should ARIN hold them for some period of time before reallocating them? Should they be put up for auction to qualified organizations? Should they be given to the 1st organization on a wait-list for 2-byte ASNs? Andrew From David_Huberman at outlook.com Sat Apr 2 14:30:45 2016 From: David_Huberman at outlook.com (David Huberman) Date: Sat, 2 Apr 2016 18:30:45 +0000 Subject: [ARIN-consult] [ARIN-Suggestions] New Suggestion - ACSP 2016.4 - Waiting List for 2 Byte ASNs In-Reply-To: <5700092D.2080208@quark.net> References: <56FC3708.1090103@arin.net> <56FE9AF2.80409@quark.net> <1E8D2726-51F8-4847-90DA-5DCB11015815@seastrom.com>, <5700092D.2080208@quark.net> Message-ID: I think everything Andrew wrote cries out for the PDP not the ACSP :) > On Apr 2, 2016, at 2:02 PM, Andrew Dul wrote: > > > On 4/1/2016 1:35 PM, Robert Seastrom wrote: >>> On Apr 1, 2016, at 11:59 AM, Andrew Dul wrote: >>> >>> I'm happy to write a policy proposal to start that process if others believe that would be beneficial to the community. >> Could we start with a problem statement that describes what problem we would be solving that isn't already adequately addressed by having ASNs be 8.3-transferable number resources? > The problem as I understand it is that ARIN will receive 2-byte ASNs as returns over time, and these ASNs have perceived or additional value to organizations compared to 4-byte ASNs. > > Will 8.3 ASNs transfers meet the needs of some organizations, yes. The question is what to do with the 2-byte ASNs that will end up in ARIN's inventory for various reasons. > > How should ARIN allocate these 2-byte ASNs? Should they be given to the next requester, regardless of technical need for a 2-byte ASN? (What are the technical qualifications we should use if there is a specific technical need? e.g. provides transit to more than 1 ASN?) Should they be held in reserve? Should ARIN hold them for some period of time before reallocating them? Should they be put up for auction to qualified organizations? Should they be given to the 1st organization on a wait-list for 2-byte ASNs? > > Andrew From jcurran at arin.net Sat Apr 2 15:01:42 2016 From: jcurran at arin.net (John Curran) Date: Sat, 2 Apr 2016 19:01:42 +0000 Subject: [ARIN-consult] [ARIN-Suggestions] New Suggestion - ACSP 2016.4 - Waiting List for 2 Byte ASNs In-Reply-To: References: <56FC3708.1090103@arin.net> <56FE9AF2.80409@quark.net> <1E8D2726-51F8-4847-90DA-5DCB11015815@seastrom.com>, <5700092D.2080208@quark.net>, Message-ID: <86B95862-0F55-4BF4-A74B-D8C77729CA4E@arin.net> > On Apr 2, 2016, at 2:30 PM, David Huberman wrote: > > I think everything Andrew wrote cries out for the PDP not the ACSP :) Indeed. Perhaps (based upon discussion here) the Advisory Council could ponder what changes, if any, to number resource policy are needed? /John John Curran President and CEO ARIN >> On Apr 2, 2016, at 2:02 PM, Andrew Dul wrote: >> >> >> On 4/1/2016 1:35 PM, Robert Seastrom wrote: >>>> On Apr 1, 2016, at 11:59 AM, Andrew Dul wrote: >>>> >>>> I'm happy to write a policy proposal to start that process if others believe that would be beneficial to the community. >>> Could we start with a problem statement that describes what problem we would be solving that isn't already adequately addressed by having ASNs be 8.3-transferable number resources? >> The problem as I understand it is that ARIN will receive 2-byte ASNs as returns over time, and these ASNs have perceived or additional value to organizations compared to 4-byte ASNs. >> >> Will 8.3 ASNs transfers meet the needs of some organizations, yes. The question is what to do with the 2-byte ASNs that will end up in ARIN's inventory for various reasons. >> >> How should ARIN allocate these 2-byte ASNs? Should they be given to the next requester, regardless of technical need for a 2-byte ASN? (What are the technical qualifications we should use if there is a specific technical need? e.g. provides transit to more than 1 ASN?) Should they be held in reserve? Should ARIN hold them for some period of time before reallocating them? Should they be put up for auction to qualified organizations? Should they be given to the 1st organization on a wait-list for 2-byte ASNs? >> >> Andrew > _______________________________________________ > ARIN-Consult > You are receiving this message because you are subscribed to the ARIN Consult Mailing > List (ARIN-consult at 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 info at arin.net if you experience any issues. From farmer at umn.edu Sat Apr 2 16:42:26 2016 From: farmer at umn.edu (David Farmer) Date: Sat, 2 Apr 2016 15:42:26 -0500 Subject: [ARIN-consult] [ARIN-Suggestions] New Suggestion - ACSP 2016.4 - Waiting List for 2 Byte ASNs In-Reply-To: <5700092D.2080208@quark.net> References: <56FC3708.1090103@arin.net> <56FE9AF2.80409@quark.net> <1E8D2726-51F8-4847-90DA-5DCB11015815@seastrom.com> <5700092D.2080208@quark.net> Message-ID: <135EFF60-8A86-498D-8121-2E6764244A54@umn.edu> > On Apr 2, 2016, at 13:02, Andrew Dul wrote: > > On 4/1/2016 1:35 PM, Robert Seastrom wrote: >>> On Apr 1, 2016, at 11:59 AM, Andrew Dul wrote: >>> >>> I'm happy to write a policy proposal to start that process if others believe that would be beneficial to the community. >> Could we start with a problem statement that describes what problem we would be solving that isn't already adequately addressed by having ASNs be 8.3-transferable number resources? > The problem as I understand it is that ARIN will receive 2-byte ASNs as returns over time, and these ASNs have perceived or additional value to organizations compared to 4-byte ASNs. > > Will 8.3 ASNs transfers meet the needs of some organizations, yes. The question is what to do with the 2-byte ASNs that will end up in ARIN's inventory for various reasons. > > How should ARIN allocate these 2-byte ASNs? Should they be given to the next requester, regardless of technical need for a 2-byte ASN? (What are the technical qualifications we should use if there is a specific technical need? e.g. provides transit to more than 1 ASN?) Should they be held in reserve? Should ARIN hold them for some period of time before reallocating them? Should they be put up for auction to qualified organizations? Should they be given to the 1st organization on a wait-list for 2-byte ASNs? > > Andrew A few other related issues; Would an organization looking for a 2-byte ASN have the option to receive a 4-byte ASN in the interim? If they did would they have to return it? Should the waiting list be closed to organizations that already have a 2-byte ASNs? If there is really a technical need for 2-byte ASNs, shouldn't we attempt to build an inventory of 2-byte ASNs? One option could be some kind of incentive or amnesty program allowing organization to trade-in 2-byte ASNs and receive 4-byte ASNs in exchange, no questions asked, no justification required, or receive a wavier on fees in exchange for unused 2-byte ASNs. Several organizations have excess ASNs that may not be used on a full-time basis, such as for test labs or temporary transitions or other projects. But, returning temporarily unused ASNs and getting new ones when they are needed again represents an unnecessary financial burden on organizations, compared to keeping a small inventory of ASNs for such temporary uses. However, it would seem likely that at least some 2-byte ASNs could be made available by allowing organizations to obtain new 4-byte ASNs in exchange for these ASNs used on a temporary basis. Overall I think these issues are better handled within the Policy Development Process, as I believe technical criteria should be defined for who is eligible to receive 2-byte ASNs. Furthermore, if we can't agree on such technical criteria, then there probably isn't a good enough reason to create a waiting list for 2-byte ASNs or otherwise treat 2-byte ASNs separately from 4-byte ASNs, and the already available option to transfer ASNs (both 2-byte and 4-byte) should be sufficient to handle the problem. Thanks. -- =============================================== David Farmer Email: farmer at umn.edu Office of Information Technology University of Minnesota 2218 University Ave SE Phone: +1-612-626-0815 Minneapolis, MN 55414-3029 Cell: +1-612-812-9952 =============================================== From jrhett at netconsonance.com Sat Apr 2 16:44:54 2016 From: jrhett at netconsonance.com (Jo Rhett) Date: Sat, 2 Apr 2016 13:44:54 -0700 Subject: [ARIN-consult] [ARIN-Suggestions] New Suggestion - ACSP 2016.4 - Waiting List for 2 Byte ASNs In-Reply-To: <135EFF60-8A86-498D-8121-2E6764244A54@umn.edu> References: <56FC3708.1090103@arin.net> <56FE9AF2.80409@quark.net> <1E8D2726-51F8-4847-90DA-5DCB11015815@seastrom.com> <5700092D.2080208@quark.net> <135EFF60-8A86-498D-8121-2E6764244A54@umn.edu> Message-ID: > Overall I think these issues are better handled within the Policy Development Process, as I believe technical criteria should be defined for who is eligible to receive 2-byte ASNs. Furthermore, if we can't agree on such technical criteria, then there probably isn't a good enough reason to create a waiting list for 2-byte ASNs or otherwise treat 2-byte ASNs separately from 4-byte ASNs, and the already available option to transfer ASNs (both 2-byte and 4-byte) should be sufficient to handle the problem. I agree with every word David said above. -- Jo Rhett Net Consonance : net philanthropy to improve open source and internet projects. From info at arin.net Mon Apr 4 09:31:07 2016 From: info at arin.net (ARIN) Date: Mon, 4 Apr 2016 09:31:07 -0400 Subject: [ARIN-consult] Consultation Closed: Proposed Bylaws Changes Message-ID: <57026C9B.20407@arin.net> On 2 April 2016, ARIN concluded its community consultation regarding proposed election-related changes to the ARIN bylaws: https://www.arin.net/participate/acsp/community_consult/03-03-2016_bylaws.html ARIN thanks those that provided feedback during the consultation. Community consultation feedback will be provided to the ARIN Board in their consideration of the next steps. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From richardj at arin.net Mon Apr 4 11:23:15 2016 From: richardj at arin.net (Richard Jimmerson) Date: Mon, 4 Apr 2016 15:23:15 +0000 Subject: [ARIN-consult] [ARIN-Suggestions] New Suggestion - ACSP 2016.4 - Waiting List for 2 Byte ASNs In-Reply-To: <0CF3A3B3-920F-4BCD-98BD-B0DE6E2306FF@seastrom.com> References: <56FC3708.1090103@arin.net> <180AD551-F4D1-4168-928B-86B7710A3194@delong.com> <20160331114529.GE901@22.rev.meerval.net> <0CF3A3B3-920F-4BCD-98BD-B0DE6E2306FF@seastrom.com> Message-ID: <8C22882A-4709-4C30-9D1D-41B72369CD36@arin.net> Hello Rob, From: Robert Seastrom > I would be curious to hear from ARIN staff how many ASNs have been transfered under 8.3 to date. A total of 8 AS numbers have been transferred via the 8.3 transfer process, to date. Richard Jimmerson CIO & Acting Director of Registration Services American Registry or Internet Numbers -------------- next part -------------- An HTML attachment was scrubbed... URL: From richardj at arin.net Mon Apr 4 11:38:08 2016 From: richardj at arin.net (Richard Jimmerson) Date: Mon, 4 Apr 2016 15:38:08 +0000 Subject: [ARIN-consult] [ARIN-Suggestions] New Suggestion - ACSP 2016.4 - Waiting List for 2 Byte ASNs In-Reply-To: <8C22882A-4709-4C30-9D1D-41B72369CD36@arin.net> References: <56FC3708.1090103@arin.net> <180AD551-F4D1-4168-928B-86B7710A3194@delong.com> <20160331114529.GE901@22.rev.meerval.net> <0CF3A3B3-920F-4BCD-98BD-B0DE6E2306FF@seastrom.com> <8C22882A-4709-4C30-9D1D-41B72369CD36@arin.net> Message-ID: Hello Rob, I am updating this figure to include the AS number count transferred via 8.3 before that service was added to ARIN Online. There have been a total of 8 AS numbers transferred via 8.3 since that service was incorporated into ARIN Online. Before that time, there were another 15 transferred via the 8.3 process. There have been a grand total of 23 AS numbers transferred via the 8.3 transfer process dating back to the beginning of the implementation of that policy. Richard Jimmerson CIO & Acting Director of Registration Services American Registry for Internet Numbers From: > on behalf of Richard Jimmerson > Date: Monday, April 4, 2016 at 11:23 AM To: Robert Seastrom >, Job Snijders > Cc: "arin-consult at arin.net" > Subject: Re: [ARIN-consult] [ARIN-Suggestions] New Suggestion - ACSP 2016.4 - Waiting List for 2 Byte ASNs Hello Rob, From: Robert Seastrom > I would be curious to hear from ARIN staff how many ASNs have been transfered under 8.3 to date. A total of 8 AS numbers have been transferred via the 8.3 transfer process, to date. Richard Jimmerson CIO & Acting Director of Registration Services American Registry or Internet Numbers -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Mon Apr 25 13:17:20 2016 From: info at arin.net (ARIN) Date: Mon, 25 Apr 2016 13:17:20 -0400 Subject: [ARIN-consult] Consultation Closed: Retirement of IPv4 Countdown Plan Message-ID: <571E5120.8010704@arin.net> On 22 April 2016, ARIN concluded its community consultation regarding retirement of the IPv4 Countdown Plan. https://www.arin.net/participate/acsp/community_consult/03-21-2016_countdown.html ARIN thanks those that provided feedback during the consultation. Based on community feedback, ARIN staff will retire the IPv4 Countdown Plan effective 1 June 2016. As outlined in the consultation, retiring the IPv4 Countdown Plan involves the cessation of Phase 4 processing procedures in our future review of IPv4 assignment/allocation requests. These requests are destined for the waiting list for unmet IPv4 requests, and going forward they will be handled via normal processes and no longer be serialized via team review of IPv4 request tickets. Removing these procedures would allow the recovered staff time to be redirected to other registration related work activities inside the ARIN Registration Services Department, such as handling the increasing number of IPv4 transfers. Please contact info at arin.net should you have any questions. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN)