<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I am be wrong, but sometimes I feel that some people either don't
understand the issue of IPv4 exhaustion and keep believing
everything will always be sorted out. Even worst, some seem to
believe that if they have a noble justification ARIN will keep
issuing them with more IPv4 and all that's necessary for that is a
policy in place.</p>
<p>Other seems to go in the direction of "I support it because my
supplier (or customer) needs it in order that I can keep doing
business with him" - forgetting that policies are not made to
fulfill individual or fewer business needs among the totality of
members that use those limited resources.</p>
<p>I do understand the reasoning of some that mentioned that point
about being removed from the list, however that was not done on
propose against those individual institutions but given the
circumstances and in order to benefit the majority of existing and
new members in a more fair possible way.</p>
<p>Regards<br>
Fernando<br>
</p>
<div class="moz-cite-prefix">On 15/01/2021 15:56,
<a class="moz-txt-link-abbreviated" href="mailto:hostmaster@uneedus.com">hostmaster@uneedus.com</a> wrote:<br>
</div>
<blockquote type="cite"
cite="mid:alpine.LRH.2.21.2101151254001.5385@bigone.uneedus.com">All
major operating systems and major brands of networking gear have
IPv6 enabled. In fact, the latest windows server networking
requires IPv6, and features will fail if you were to turn IPv6
off.
<br>
<br>
I understand good designs can be done with IPv4 with little or no
configuration. In fact the CPE of most major ISP's today have
BOTH IPv4 dhcp blocks preconfigured, as well as assignment of IPv6
to all attached network devices by SLAAC and/or DHCPv6, leaving
nearly no configuration to set up a single node network.
<br>
<br>
Thus, if setting up a new network, it actually takes MORE work to
get rid of IPv6 to form an IPv4 only network, rather than simply
using the preconfigured setup which is dual stack.
<br>
<br>
There are already nodes on the internet that are IPv6 ONLY. This
will become more common as time goes on. Not going with the
default dual stack setup will cut your users from access to these
services. Eventually we will reach a tipping point, after which
IPv4 services will start to disappear. Also, the devices do not
have to do NAT for IPv6, reducing the load on routers. In todays
world, turning on IPv6 will result in more than half of the
traffic routing via IPv6 bypassing the NAT. It also future proofs
your network.
<br>
<br>
Albert Erdmann
<br>
Network Administrator
<br>
Paradise On Line Inc.
<br>
<br>
On Fri, 15 Jan 2021, Mark Kiwiet wrote:
<br>
<br>
<blockquote type="cite">Inside/Private network space will probably
always be IPv4. I don't understand why you would deal with
IPv6 on the inside - you have the entire freaking
<br>
class A of 10.0.0.0/8 to design around - and make beautiful
designs as well.
<br>
<br>
Unless you're running a NOC or a Web Server Farm - you really
don't need more than 1 Public IP address for even 500+ private
surfing endpoints. Outside of
<br>
standard ports like TCP/25 - you can overload a single IP
address with hundreds of high random ports.
<br>
<br>
Right now - the biggest public IPv4 issue is waste. There are
tons of public IPv4's that are not used because they are part of
an overallocated customer
<br>
block.
<br>
<br>
On Fri, Jan 15, 2021 at 10:51 AM <a class="moz-txt-link-rfc2396E" href="mailto:hostmaster@uneedus.com"><hostmaster@uneedus.com></a>
wrote:
<br>
What expensive technology are you talking about? Windows
has had IPv6
<br>
since Windows 2000. Ditto with Apple or Chromebooks or
any other tech
<br>
that is commonly used in schools.
<br>
<br>
Use of RFC1918 Ipv4 addresses is quite common in every
school I have ever
<br>
dealt with. Even at the university level, it is very
uncommon to assign
<br>
workstations to public IPv4 addresses, and some form of
NAT is used for
<br>
IPv4 access via common public addresses with or without a
proxy.
<br>
<br>
Albert Erdmann
<br>
Network Administrator
<br>
Paradise On Line Inc.
<br>
<br>
On Fri, 15 Jan 2021, Jay Wendelin wrote:
<br>
<br>
>
<br>
> You would have to ask the ISP’s themselves. My
Schools will not want to be involved at all nor will we want to
implement new and expensive
<br>
technologies for
<br>
> ip6.
<br>
>
<br>
>
<br>
>
<br>
>
<br>
>
<br>
> <a class="moz-txt-link-abbreviated" href="mailto:cidimage001.png@01D698CE.05CAF3C0">cidimage001.png@01D698CE.05CAF3C0</a>
<br>
>
<br>
> Jay Wendelin
<br>
>
<br>
> Chief Information Officer
<br>
>
<br>
> Cell: 309-657-5303
<br>
>
<br>
> <a class="moz-txt-link-abbreviated" href="mailto:jmw@poweredbystl.com">jmw@poweredbystl.com</a>
<br>
>
<br>
> <a class="moz-txt-link-abbreviated" href="mailto:cidimage002.png@01D698CE.05CAF3C0">cidimage002.png@01D698CE.05CAF3C0</a>
<a class="moz-txt-link-abbreviated" href="mailto:cidimage003.png@01D698CE.05CAF3C0">cidimage003.png@01D698CE.05CAF3C0</a>
<a class="moz-txt-link-abbreviated" href="mailto:cidimage004.png@01D698CE.05CAF3C0">cidimage004.png@01D698CE.05CAF3C0</a>
<br>
>
<br>
>
<br>
>
<br>
>
<br>
>
<br>
> From: Fernando Frediani <a class="moz-txt-link-rfc2396E" href="mailto:fhfrediani@gmail.com"><fhfrediani@gmail.com></a>
<br>
> Date: Friday, January 15, 2021 at 10:36 AM
<br>
> To: Jay Wendelin <a class="moz-txt-link-rfc2396E" href="mailto:jmw@poweredbystl.com"><jmw@poweredbystl.com></a>
<br>
> Cc: arin-ppml <a class="moz-txt-link-rfc2396E" href="mailto:arin-ppml@arin.net"><arin-ppml@arin.net></a>
<br>
> Subject: Re: [arin-ppml] Draft Policy ARIN-2020-2:
Grandfathering of Organizations Removed from Waitlist by
Implementation of ARIN-2019-16
<br>
>
<br>
> WARNING: This message originated from outside of the
organization. Please do not click links or open attachments
unless you recognize the
<br>
source of this
<br>
> email and can ensure the content is safe.
<br>
>
<br>
>
<br>
>
<br>
> Didn't these ISPs in 2021 not invest IPv6 deployment
and good CGNAT techniques and they rely only on keep getting
more addresses from ARIN ?
<br>
>
<br>
>
<br>
>
<br>
> Fernando
<br>
>
<br>
> On Fri, 15 Jan 2021, 13:29 Jay Wendelin,
<a class="moz-txt-link-rfc2396E" href="mailto:jmw@poweredbystl.com"><jmw@poweredbystl.com></a> wrote:
<br>
>
<br>
> I support this petition, I have many Public
School Clients that rely on their ISP’s to manage and offer IP
address.
<br>
>
<br>
>
<br>
>
<br>
> Jay Wendelin
<br>
>
<br>
> CIO
<br>
>
<br>
> STL/BTS
<br>
>
<br>
>
<br>
>
<br>
> <a class="moz-txt-link-abbreviated" href="mailto:cidimage001.png@01D698CE.05CAF3C0">cidimage001.png@01D698CE.05CAF3C0</a>
<br>
>
<br>
> Jay Wendelin
<br>
>
<br>
> Chief Information Officer
<br>
>
<br>
> Cell: 309-657-5303
<br>
>
<br>
> <a class="moz-txt-link-abbreviated" href="mailto:jmw@poweredbystl.com">jmw@poweredbystl.com</a>
<br>
>
<br>
> <a class="moz-txt-link-abbreviated" href="mailto:cidimage002.png@01D698CE.05CAF3C0">cidimage002.png@01D698CE.05CAF3C0</a>
<a class="moz-txt-link-abbreviated" href="mailto:cidimage003.png@01D698CE.05CAF3C0">cidimage003.png@01D698CE.05CAF3C0</a>
<a class="moz-txt-link-abbreviated" href="mailto:cidimage004.png@01D698CE.05CAF3C0">cidimage004.png@01D698CE.05CAF3C0</a>
<br>
>
<br>
>
<br>
>
<br>
> _______________________________________________
<br>
> ARIN-PPML
<br>
> You are receiving this message because you are
subscribed to
<br>
> the ARIN Public Policy Mailing List
(<a class="moz-txt-link-abbreviated" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).
<br>
> Unsubscribe or manage your mailing list subscription
at:
<br>
> <a class="moz-txt-link-freetext" href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a>
<br>
> Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any
issues.
<br>
>
<br>
>
<br>
>_______________________________________________
<br>
ARIN-PPML
<br>
You are receiving this message because you are subscribed
to
<br>
the ARIN Public Policy Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).
<br>
Unsubscribe or manage your mailing list subscription at:
<br>
<a class="moz-txt-link-freetext" href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a>
<br>
Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.
<br>
<br>
<br>
<br>
--
<br>
<br>
[uc?export=download&id=1rw0rA0GcTMgcl44DG58wdI5ADThV4qbh&revid=0B3CYAKYY2jq7RXgwVlV4QWZyaFFkbXdiUE9GeVMyQjdmRW9VPQ]
<br>
<br>
<br>
<br>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a class="moz-txt-link-freetext" href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a>
Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.
</pre>
</blockquote>
</body>
</html>