Total of 21 messages in the last 7 days.
script run at: Fri Jul 26 00:53:04 EDT 2019
Messages | Bytes| Who
+--++--+
28.57% |6 | 20.24% |62945 | i...@arin.net
14.29% |3 | 24.17% |75170 | arin-ppml@arin.net
On Fri, Jul 26, 2019 at 1:19 AM Martin Hannigan wrote:
> The folks buying up large swaths of previously
> un or underused IPv4 are not using CGNAT.
This is exactly why we need IPv6: to ease the setup of new networks
and to eliminate the financial barrier to entry.
--
Töma
___
On Thu, Jul 25, 2019 at 5:46 PM Töma Gavrichenkov wrote:
> On Fri, Jul 26, 2019 at 12:25 AM Martin Hannigan
> wrote:
> > From my perspective, there is no IPv4 exhaustion or
> > shortage. Anyone can get almost anything they need
> > on the transfer market.
>
> That depends on the size of your net
On Fri, Jul 26, 2019 at 12:25 AM Martin Hannigan wrote:
> From my perspective, there is no IPv4 exhaustion or
> shortage. Anyone can get almost anything they need
> on the transfer market.
That depends on the size of your network. Through an abuse-proof
pile-up of resource-exhausting CGNATs, alwa
On Thu, Jul 25, 2019 at 5:07 PM Fernando Frediani
wrote:
> Hello all.
>
> Recently I have been reading some content about IPv4 exhaustion in order
> to understand better the problematic
>
[ clip ]
>From my perspective, there is no IPv4 exhaustion or shortage. Anyone can
get almost anything they
Hello all.
Recently I have been reading some content about IPv4 exhaustion in order
to understand better the problematic and I am also working on some
policy proposal drafts and wanted to do a consultation to the community
that perhaps have knowledge about some of the points I would like to
a
I found the wording of the Problem Statement on this one a bit
confusing. However, after deciphering the effect of the actual
policy change I support it.
Essentially, all returned IPv4 space will no longer go to the waiting
list but will supplement the 4.10 reserved pool used to enhance IPv6
The AC has abandoned the following Draft Policy:
* ARIN-2019-6: Longer Hold Time Requirements for 4.1.8 Recipients
Regarding Draft Policy ARIN-2019-6, the AC provided the following statement:
"At its regular monthly meeting on July 18th, the ARIN Advisory Council voted
unanimously to abandon AR
On 18 July 2019 the ARIN Advisory Council (AC) advanced the following
Draft Policy to Recommended Draft Policy status:
Recommended Draft Policy ARIN-2019-1: Clarify Section 4 IPv4 Request
Requirements
The text of the Recommended Draft Policy is below, and may also be found at:
https://www.ar