Phase 4.

[Bryan Socha]

Whats the big deal   If your just arin, dont panic. Akamai and
digitalocean has been the only people aquire fair priced v4 putside
arin.So arin is ending.   It doesnt stop anything. be smart 3 usd
per ip is fair if dirty.  F the auct8ons they are fake and we get the ips
lower than op3ning.

Icann is the mast 8 class as real?Distribute them
,

Re: US patent 5473599

[Donald Eastlake]

Hi,

See below

On Wed, Apr 23, 2014 at 12:47 PM, Henning Brauer  wrote:
> * Paul WALL  [2014-04-22 19:30]:
>> Both CARP and VRRP use virtual router MAC addresses that start with
>> 00:00:5e.  This organizational unique identifier (OUI) is assigned to
>> IANA, not OpenBSD or a related project.  The CARP authors could have
>> gotten their own from IEEE.  OUIs are not free but the cost is quite
>> reasonable (and was even more reasonable years ago when this
>> unfortunate decision was made).
>
> we're an open source project, running on a rather small budget almost
> exclusively from donations, so "quite reasonable" doesn't cut it.

While it is at the discretion of the IEEE Registration Authority,
generally the IEEE RA will grant code point for standards use without
any fee. While this is not all that clear from their web site,
http://standards.ieee.org/develop/regauth/, except for standards use
group (multicast) MAC addresses which are only for standards use and
for which there is no charge, it is their policy.

>> The next two octets for IPv4 VRRP are 00:01.  Highly coincidentally,
>> the CARP folks *also* decided to use 00:01 after they got upset at the
>> IETF for dissing their slide deck.
>
> you're interpreting way too much in here.
> carp has been based on an earlier, never published vrrp implementatoin
> we had before realizing the patent problem.
> i don't remember any discussion about the OUI or, more general, the mac
> address choice. it's 10 years ago now, so i don't remember every
> single detail, changing the mac addr has pbly just been forgotten.
> not at least using sth but 00:01 for the 4th and 5th octet was likely
> a mistake. changing that now - wether just 4th/5th octet or to an
> entirely different, donated OUI - wouldn't be easy, unfortunately.
> acadmic discussion as long as we don't have a suitable OUI anyway.
>
>> If either of these decisions had not been made, we would not be having
>> this discussion today.
>
> we weren't really given a choice.
> as I said before, I'd much prefer we had just been given a multicast
> address etc. we tried. the IEEE/IETF/IANA processes have been an utter
> failure in our (limited) experience, not just in this case. might be
> different if you're $big_vendor with deep pockets, but that doesn't
> help either.

That seems like a very scatter-shot claim. The process for applying
for MAC addresses under the IANA OUI was regularized in RFC 5342,
since updated to and replaced by RFC 7042. See
http://www.rfc-editor.org/rfc/rfc7042.txt. Perhaps you were trying
before RFC 5342?

To get an assignment under IANA it must bet or standard use that is
either an IETF standard or related to an IETF standard but it doesn't
say what the relationship has to be. It must also be documented in an
Internet Draft or an RFC but there is no technical screening for
posting an Internet Draft so that doesn't seem like a barrier. It is
subject to expert review.

Thanks,
Donald
=
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e...@gmail.com

>> ...
> ...
> --
> Henning Brauer, h...@bsws.de, henn...@openbsd.org
> BS Web Services GmbH, AG Hamburg HRB 128289, http://bsws.de
> Full-Service ISP - Secure Hosting, Mail and DNS Services
> Dedicated Servers, Rootservers, Application Hosting

Re: IPv4 Address transfer after company acquisition

[Owen DeLong]

Without interpretation:

Look on the ARIN Website..

Policies->Number Resource Policy Manual

You want to read Section 8, specifically section 8.2

Owen

On Apr 23, 2014, at 10:28 AM, John Jackson  wrote:

> I have a customer who previously didn't have any IPv4 address space.  They
> recently acquired a competitor that has a /24.
> 
> Are there any special ARIN rules for this type of transfer?
> 
> Any pointers, or 'gotchas'?
> 
> Thanks
> John

Re: IPv4 Address transfer after company acquisition

[Justin M. Streiner]

On Wed, 23 Apr 2014, John Jackson wrote:


I have a customer who previously didn't have any IPv4 address space.  They
recently acquired a competitor that has a /24.

Are there any special ARIN rules for this type of transfer?

Any pointers, or 'gotchas'?


I'm pretty sure ARIN has the transfer process documented on their website. 
From what I remember, ARIN will need to see some documentation of the 
acquisition, including a letter of agency/authorization from the company 
that was acquired, on the original company's letterhead.


jms

IPv4 Address transfer after company acquisition

[John Jackson]

I have a customer who previously didn't have any IPv4 address space.  They
recently acquired a competitor that has a /24.

Are there any special ARIN rules for this type of transfer?

Any pointers, or 'gotchas'?

Thanks
John

Re: US patent 5473599

[Henning Brauer]

* TGLASSEY  [2014-04-23 19:13]:
> in fact CARP clearly is an infringement [of the patent].

that's YOUR analysis, and it contradicts ours and the legal advice we
got, so I'll ignore it.

Irrelevant anyway, see subject - expired.

-- 
Henning Brauer, h...@bsws.de, henn...@openbsd.org
BS Web Services GmbH, AG Hamburg HRB 128289, http://bsws.de
Full-Service ISP - Secure Hosting, Mail and DNS Services
Dedicated Servers, Rootservers, Application Hosting

Re: US patent 5473599

[TGLASSEY]

Henning I understand your work is important - and that its open source 
but that is part of the problem with global patent law today. No one 
wants it around when their works are impacted by it. But patent 
publications are binding under the treaties and in fact CARP clearly is 
an infringement. The issue is what to do do about it.


Todd Glassey

On 4/23/2014 9:47 AM, Henning Brauer wrote:

* Paul WALL  [2014-04-22 19:30]:

Both CARP and VRRP use virtual router MAC addresses that start with
00:00:5e.  This organizational unique identifier (OUI) is assigned to
IANA, not OpenBSD or a related project.  The CARP authors could have
gotten their own from IEEE.  OUIs are not free but the cost is quite
reasonable (and was even more reasonable years ago when this
unfortunate decision was made).

we're an open source project, running on a rather small budget almost
exclusively from donations, so "quite reasonable" doesn't cut it.


The next two octets for IPv4 VRRP are 00:01.  Highly coincidentally,
the CARP folks *also* decided to use 00:01 after they got upset at the
IETF for dissing their slide deck.

you're interpreting way too much in here.
carp has been based on an earlier, never published vrrp implementatoin
we had before realizing the patent problem.
i don't remember any discussion about the OUI or, more general, the mac
address choice. it's 10 years ago now, so i don't remember every
single detail, changing the mac addr has pbly just been forgotten.
not at least using sth but 00:01 for the 4th and 5th octet was likely
a mistake. changing that now - wether just 4th/5th octet or to an
entirely different, donated OUI - wouldn't be easy, unfortunately.
acadmic discussion as long as we don't have a suitable OUI anyway.


If either of these decisions had not been made, we would not be having
this discussion today.

we weren't really given a choice.
as I said before, I'd much prefer we had just been given a multicast
address etc. we tried. the IEEE/IETF/IANA processes have been an utter
failure in our (limited) experience, not just in this case. might be
different if you're $big_vendor with deep pockets, but that doesn't
help either.

fortunately this obviously isn't a big problem in practice, based on
the fact that we don't get any complaints/reports in that direction.
still would be way micer if that situation had been created in the
first place, but as said - we weren't given that choice.


Nothing personal Henning (and I like what you did with OpenBGPd and
OpenNTPd) but you'd gain a lot of respect in my eyes, as well as a
bunch of other people's, if you publicly admitted the CARP OUI
decision was a huge mistake.

huge? nah.
mistake? probably.


If your lawyers have advised you not to
apologize because of liability concerns (despite that "no warranty"
bit in the BSD license) it's OK - I completely understand.

you live in a bizarre world apparently.
but then, that's what the US (dunno wether that is your actual
background, sounds that way tho) is when it comes to patents and
liability in the eyes of the rest of the world. neither of us can
change that, so be it.

and just to prevent confusion: I didn't implement most of carp, but was
involved, and I wasn't the one dealing with IANA/IETF/whatever either.
No pun intended if I mixed up IETF, IANA, IEEE somewhere here, it's
not like we create new protocols every other day.



--
-

Personal Email - Disclaimers Apply

Re: US patent 5473599

[Henning Brauer]

* Paul WALL  [2014-04-22 19:30]:
> Both CARP and VRRP use virtual router MAC addresses that start with
> 00:00:5e.  This organizational unique identifier (OUI) is assigned to
> IANA, not OpenBSD or a related project.  The CARP authors could have
> gotten their own from IEEE.  OUIs are not free but the cost is quite
> reasonable (and was even more reasonable years ago when this
> unfortunate decision was made).

we're an open source project, running on a rather small budget almost
exclusively from donations, so "quite reasonable" doesn't cut it.

> The next two octets for IPv4 VRRP are 00:01.  Highly coincidentally,
> the CARP folks *also* decided to use 00:01 after they got upset at the
> IETF for dissing their slide deck.

you're interpreting way too much in here.
carp has been based on an earlier, never published vrrp implementatoin
we had before realizing the patent problem.
i don't remember any discussion about the OUI or, more general, the mac
address choice. it's 10 years ago now, so i don't remember every
single detail, changing the mac addr has pbly just been forgotten.
not at least using sth but 00:01 for the 4th and 5th octet was likely
a mistake. changing that now - wether just 4th/5th octet or to an
entirely different, donated OUI - wouldn't be easy, unfortunately.
acadmic discussion as long as we don't have a suitable OUI anyway.

> If either of these decisions had not been made, we would not be having
> this discussion today.

we weren't really given a choice.
as I said before, I'd much prefer we had just been given a multicast
address etc. we tried. the IEEE/IETF/IANA processes have been an utter
failure in our (limited) experience, not just in this case. might be
different if you're $big_vendor with deep pockets, but that doesn't
help either. 

fortunately this obviously isn't a big problem in practice, based on
the fact that we don't get any complaints/reports in that direction.
still would be way micer if that situation had been created in the
first place, but as said - we weren't given that choice.

> Nothing personal Henning (and I like what you did with OpenBGPd and
> OpenNTPd) but you'd gain a lot of respect in my eyes, as well as a
> bunch of other people's, if you publicly admitted the CARP OUI
> decision was a huge mistake.

huge? nah.
mistake? probably.

> If your lawyers have advised you not to
> apologize because of liability concerns (despite that "no warranty"
> bit in the BSD license) it's OK - I completely understand.

you live in a bizarre world apparently.
but then, that's what the US (dunno wether that is your actual
background, sounds that way tho) is when it comes to patents and
liability in the eyes of the rest of the world. neither of us can
change that, so be it.

and just to prevent confusion: I didn't implement most of carp, but was
involved, and I wasn't the one dealing with IANA/IETF/whatever either.
No pun intended if I mixed up IETF, IANA, IEEE somewhere here, it's
not like we create new protocols every other day.

-- 
Henning Brauer, h...@bsws.de, henn...@openbsd.org
BS Web Services GmbH, AG Hamburg HRB 128289, http://bsws.de
Full-Service ISP - Secure Hosting, Mail and DNS Services
Dedicated Servers, Rootservers, Application Hosting

Re: ARIN Enters Phase Four of the IPv4 Countdown Plan

[John Curran]

On Apr 23, 2014, at 12:13 PM, Bob Evans  wrote:

> Yes, you could have shown up to discuss, present arguments , vote 
> there many. meetings on this as well as ARIN email discussion threads. All
> the hot topics are always presented at nanog/arin meets in an effort to
> create community awareness and gather community interest. 

Bob -

Very well said - also, while it is true that IPv4 address allocation
and assignment policy may become less relevant over time, it is not 
at all clear that will be the case with other policies, such as the 
IPv4 transfer policy.

In any case, if you have views on how address space in the region 
should be administered, please participate in one or more of:

  - The ARIN ppml mailing list
  - The ARIN Public Policy Meeting (in-person or remote)
  - The ARIN Public Policy Consultations held at each NANOG

We have nearly a dozen proposed policy changes being considered 
at the present time, and the time to express support or concern
is _now_ (as opposed to after these policies changes have been
approved, implemented and are in use.)

FYI,
/John

John Curran
President and CEO
ARIN

Re: ARIN Enters Phase Four of the IPv4 Countdown Plan

[Bob Evans]

Yes, you could have shown up to discuss, present arguments , vote 
there many. meetings on this as well as ARIN email discussion threads. All
the hot topics are always presented at nanog/arin meets in an effort to
create community awareness and gather community interest. I attended ARIN
only meetings where the rooms were full - this was a hot topic of ARIN
meetings many times. Your point was brought up many times - that position
was represented.

The process to get a big block is cumbersome...thus verizon went out to
the open market to buy space. A notable verizon person attend an arin
meeting and openly said so. And that was during late phase 2 or beginning
of 3. So it's not that easy for a big company to get a big block.

Bob Evans
CTO

> If you didn't like it, you could have participated in the rule making
> where things like this were discussed at length, and voted on by the
> "community" (which turned out to be a very few people who gave a shit).
>
> --
> TTFN,
> patrick
>
>
> On Apr 23, 2014, at 10:35, "Paul S."  wrote:
>>
>> Am I the only one who thinks this 'clench' is rather absurd especially
>> right after one company pretty much got 1/4th of all remaining address
>> space when there's such an insane crunch looming?
>>
>> Regardless of how large / important they are, that is.
>>
>> If anything, this is just gonna make things more difficult for smaller
>> companies while larger ones roam free.
>>
>>> On 4/23/2014 午後 11:04, John Curran wrote:
>>> NANOGers -
>>>
>>>ARIN's regional IPv4 free pool has reached the equivalent of one /8
>>> of IPv4 space,
>>>which means we are approaching runout of IPv4 space availability in
>>> this region.
>>>(See attached announcement from ARIN regarding occurrence of this
>>> event)
>>>
>>>There are some changes to processing of requests as we enter this
>>> final phase,
>>>and obviously service providers ought to be thinking about
>>> IPv6-based services,
>>>if not already in deployment.
>>>
>>> FYI,
>>> /John
>>>
>>> John Curran
>>> President and CEO
>>> ARIN
>>>
>>> Begin forwarded message:
>>>
>>> From: ARIN mailto:i...@arin.net>>
>>> Subject: [arin-announce] ARIN Enters Phase Four of the IPv4 Countdown
>>> Plan
>>> Date: April 23, 2014 at 10:00:20 AM GMT-3
>>> To: arin-annou...@arin.net
>>>
>>> ARIN is down to its final /8 of available space in its inventory and
>>> has moved into Phase Four of its IPv4 Countdown Plan. All IPv4 requests
>>> are now subject to Countdown Plan processes, so please review the
>>> following details carefully.
>>>
>>> All IPv4 requests will be processed on a "First in, First out" basis,
>>> and all requests of any size will be subject to team review, and
>>> requests for /15 or larger will require department director approval.
>>> ARIN's resource analysts will respond to tickets as they appear
>>> chronologically in the queue. Each ticket response is treated as an
>>> individual transaction, so the completion time of a single request may
>>> vary based on customer response times and the number of requests
>>> waiting in the queue. Because each correspondence will be processed in
>>> sequence, it is possible that response times may exceed our usual
>>> two-day turnaround.
>>>
>>> The hold period for returned, reclaimed, and revoked blocks is now
>>> reduced to 60 days. All returned, revoked, and reclaimed IPv4 address
>>> space will go back into the available pool when the 60 day period has
>>> expired. Staff will continue to check routing/filtering on space being
>>> reissued and will notify recipients if there are issues.
>>>
>>> When a request is approved, the recipient will have 60 days to complete
>>> payment and/or an RSA. On the 61st day, the address space will be
>>> released back to the available pool if payment and RSA are not
>>> completed.
>>>
>>> We encourage you to visit the IPv4 Countdown Phase Four page at:
>>>
>>> https://www.arin.net/resources/request/countdown_phase4.html
>>>
>>> ARIN may experience situations where it can no longer fulfill
>>> qualifying IPv4 requests due to a lack of inventory of the desired
>>> block size. At that time, the requester may opt to accept the largest
>>> available block size or they may ask to be placed on the Waiting List
>>> for Unmet Requests. Full details about this process are available at:
>>>
>>> https://www.arin.net/resources/request/waiting_list.html
>>>
>>> Please contact hostmas...@arin.net or our Help Desk +1.703.227.0660 if
>>> you have questions about these procedural changes.
>>>
>>> Regards,
>>>
>>> Leslie Nobile
>>> Director, Registration Services
>>> American Registry for Internet Numbers (ARIN)
>>> ___
>>> ARIN-Announce
>>> You are receiving this message because you are subscribed to
>>> the ARIN Announce Mailing List (arin-annou...@arin.net).
>>> Unsubscribe or manage your mailing list subscription at:
>>> http://lists.arin.net/mailman/listinfo/arin-announce

Re: ARIN Enters Phase Four of the IPv4 Countdown Plan

[Dale W. Carder]

Thus spake Paul S. (cont...@winterei.se) on Wed, Apr 23, 2014 at 11:35:20PM 
+0900:
> Am I the only one who thinks this 'clench' is rather absurd
> especially right after one company pretty much got 1/4th of all
> remaining address space when there's such an insane crunch looming?

Deck Chairs.

Dale

Re: ARIN Enters Phase Four of the IPv4 Countdown Plan

[Patrick W. Gilmore]

If you didn't like it, you could have participated in the rule making where 
things like this were discussed at length, and voted on by the "community" 
(which turned out to be a very few people who gave a shit).

-- 
TTFN,
patrick


On Apr 23, 2014, at 10:35, "Paul S."  wrote:
> 
> Am I the only one who thinks this 'clench' is rather absurd especially right 
> after one company pretty much got 1/4th of all remaining address space when 
> there's such an insane crunch looming?
> 
> Regardless of how large / important they are, that is.
> 
> If anything, this is just gonna make things more difficult for smaller 
> companies while larger ones roam free.
> 
>> On 4/23/2014 午後 11:04, John Curran wrote:
>> NANOGers -
>> 
>>ARIN's regional IPv4 free pool has reached the equivalent of one /8 of 
>> IPv4 space,
>>which means we are approaching runout of IPv4 space availability in this 
>> region.
>>(See attached announcement from ARIN regarding occurrence of this event)
>> 
>>There are some changes to processing of requests as we enter this final 
>> phase,
>>and obviously service providers ought to be thinking about IPv6-based 
>> services,
>>if not already in deployment.
>> 
>> FYI,
>> /John
>> 
>> John Curran
>> President and CEO
>> ARIN
>> 
>> Begin forwarded message:
>> 
>> From: ARIN mailto:i...@arin.net>>
>> Subject: [arin-announce] ARIN Enters Phase Four of the IPv4 Countdown Plan
>> Date: April 23, 2014 at 10:00:20 AM GMT-3
>> To: arin-annou...@arin.net
>> 
>> ARIN is down to its final /8 of available space in its inventory and has 
>> moved into Phase Four of its IPv4 Countdown Plan. All IPv4 requests are now 
>> subject to Countdown Plan processes, so please review the following details 
>> carefully.
>> 
>> All IPv4 requests will be processed on a "First in, First out" basis, and 
>> all requests of any size will be subject to team review, and requests for 
>> /15 or larger will require department director approval. ARIN's resource 
>> analysts will respond to tickets as they appear chronologically in the 
>> queue. Each ticket response is treated as an individual transaction, so the 
>> completion time of a single request may vary based on customer response 
>> times and the number of requests waiting in the queue. Because each 
>> correspondence will be processed in sequence, it is possible that response 
>> times may exceed our usual two-day turnaround.
>> 
>> The hold period for returned, reclaimed, and revoked blocks is now reduced 
>> to 60 days. All returned, revoked, and reclaimed IPv4 address space will go 
>> back into the available pool when the 60 day period has expired. Staff will 
>> continue to check routing/filtering on space being reissued and will notify 
>> recipients if there are issues.
>> 
>> When a request is approved, the recipient will have 60 days to complete 
>> payment and/or an RSA. On the 61st day, the address space will be released 
>> back to the available pool if payment and RSA are not completed.
>> 
>> We encourage you to visit the IPv4 Countdown Phase Four page at:
>> 
>> https://www.arin.net/resources/request/countdown_phase4.html
>> 
>> ARIN may experience situations where it can no longer fulfill qualifying 
>> IPv4 requests due to a lack of inventory of the desired block size. At that 
>> time, the requester may opt to accept the largest available block size or 
>> they may ask to be placed on the Waiting List for Unmet Requests. Full 
>> details about this process are available at:
>> 
>> https://www.arin.net/resources/request/waiting_list.html
>> 
>> Please contact hostmas...@arin.net or our Help Desk +1.703.227.0660 if you 
>> have questions about these procedural changes.
>> 
>> Regards,
>> 
>> Leslie Nobile
>> Director, Registration Services
>> American Registry for Internet Numbers (ARIN)
>> ___
>> ARIN-Announce
>> You are receiving this message because you are subscribed to
>> the ARIN Announce Mailing List (arin-annou...@arin.net).
>> Unsubscribe or manage your mailing list subscription at:
>> http://lists.arin.net/mailman/listinfo/arin-announce
>> Please contact i...@arin.net if you experience any issues.
>> 
> 

Re: ARIN Enters Phase Four of the IPv4 Countdown Plan

[Paul S.]

Am I the only one who thinks this 'clench' is rather absurd especially 
right after one company pretty much got 1/4th of all remaining address 
space when there's such an insane crunch looming?


Regardless of how large / important they are, that is.

If anything, this is just gonna make things more difficult for smaller 
companies while larger ones roam free.


On 4/23/2014 午後 11:04, John Curran wrote:

NANOGers -

ARIN's regional IPv4 free pool has reached the equivalent of one /8 of IPv4 
space,
which means we are approaching runout of IPv4 space availability in this 
region.
(See attached announcement from ARIN regarding occurrence of this event)

There are some changes to processing of requests as we enter this final 
phase,
and obviously service providers ought to be thinking about IPv6-based 
services,
if not already in deployment.

FYI,
/John

John Curran
President and CEO
ARIN

Begin forwarded message:

From: ARIN mailto:i...@arin.net>>
Subject: [arin-announce] ARIN Enters Phase Four of the IPv4 Countdown Plan
Date: April 23, 2014 at 10:00:20 AM GMT-3
To: arin-annou...@arin.net

ARIN is down to its final /8 of available space in its inventory and has moved 
into Phase Four of its IPv4 Countdown Plan. All IPv4 requests are now subject 
to Countdown Plan processes, so please review the following details carefully.

All IPv4 requests will be processed on a "First in, First out" basis, and all 
requests of any size will be subject to team review, and requests for /15 or larger will 
require department director approval. ARIN's resource analysts will respond to tickets as 
they appear chronologically in the queue. Each ticket response is treated as an 
individual transaction, so the completion time of a single request may vary based on 
customer response times and the number of requests waiting in the queue. Because each 
correspondence will be processed in sequence, it is possible that response times may 
exceed our usual two-day turnaround.

The hold period for returned, reclaimed, and revoked blocks is now reduced to 
60 days. All returned, revoked, and reclaimed IPv4 address space will go back 
into the available pool when the 60 day period has expired. Staff will continue 
to check routing/filtering on space being reissued and will notify recipients 
if there are issues.

When a request is approved, the recipient will have 60 days to complete payment 
and/or an RSA. On the 61st day, the address space will be released back to the 
available pool if payment and RSA are not completed.

We encourage you to visit the IPv4 Countdown Phase Four page at:

https://www.arin.net/resources/request/countdown_phase4.html

ARIN may experience situations where it can no longer fulfill qualifying IPv4 
requests due to a lack of inventory of the desired block size. At that time, 
the requester may opt to accept the largest available block size or they may 
ask to be placed on the Waiting List for Unmet Requests. Full details about 
this process are available at:

https://www.arin.net/resources/request/waiting_list.html

Please contact hostmas...@arin.net or our Help Desk +1.703.227.0660 if you have 
questions about these procedural changes.

Regards,

Leslie Nobile
Director, Registration Services
American Registry for Internet Numbers (ARIN)
___
ARIN-Announce
You are receiving this message because you are subscribed to
the ARIN Announce Mailing List (arin-annou...@arin.net).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-announce
Please contact i...@arin.net if you experience any issues.

ARIN Enters Phase Four of the IPv4 Countdown Plan

[John Curran]

NANOGers -

   ARIN's regional IPv4 free pool has reached the equivalent of one /8 of IPv4 
space,
   which means we are approaching runout of IPv4 space availability in this 
region.
   (See attached announcement from ARIN regarding occurrence of this event)

   There are some changes to processing of requests as we enter this final 
phase,
   and obviously service providers ought to be thinking about IPv6-based 
services,
   if not already in deployment.

FYI,
/John

John Curran
President and CEO
ARIN

Begin forwarded message:

From: ARIN mailto:i...@arin.net>>
Subject: [arin-announce] ARIN Enters Phase Four of the IPv4 Countdown Plan
Date: April 23, 2014 at 10:00:20 AM GMT-3
To: arin-annou...@arin.net

ARIN is down to its final /8 of available space in its inventory and has moved 
into Phase Four of its IPv4 Countdown Plan. All IPv4 requests are now subject 
to Countdown Plan processes, so please review the following details carefully.

All IPv4 requests will be processed on a "First in, First out" basis, and all 
requests of any size will be subject to team review, and requests for /15 or 
larger will require department director approval. ARIN's resource analysts will 
respond to tickets as they appear chronologically in the queue. Each ticket 
response is treated as an individual transaction, so the completion time of a 
single request may vary based on customer response times and the number of 
requests waiting in the queue. Because each correspondence will be processed in 
sequence, it is possible that response times may exceed our usual two-day 
turnaround.

The hold period for returned, reclaimed, and revoked blocks is now reduced to 
60 days. All returned, revoked, and reclaimed IPv4 address space will go back 
into the available pool when the 60 day period has expired. Staff will continue 
to check routing/filtering on space being reissued and will notify recipients 
if there are issues.

When a request is approved, the recipient will have 60 days to complete payment 
and/or an RSA. On the 61st day, the address space will be released back to the 
available pool if payment and RSA are not completed.

We encourage you to visit the IPv4 Countdown Phase Four page at:

https://www.arin.net/resources/request/countdown_phase4.html

ARIN may experience situations where it can no longer fulfill qualifying IPv4 
requests due to a lack of inventory of the desired block size. At that time, 
the requester may opt to accept the largest available block size or they may 
ask to be placed on the Waiting List for Unmet Requests. Full details about 
this process are available at:

https://www.arin.net/resources/request/waiting_list.html

Please contact hostmas...@arin.net or our Help Desk +1.703.227.0660 if you have 
questions about these procedural changes.

Regards,

Leslie Nobile
Director, Registration Services
American Registry for Internet Numbers (ARIN)
___
ARIN-Announce
You are receiving this message because you are subscribed to
the ARIN Announce Mailing List (arin-annou...@arin.net).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-announce
Please contact i...@arin.net if you experience any issues.