[ppml] IPv6 flawed?
marla.azinger at frontiercorp.com
Mon Sep 17 11:26:00 EDT 2007
Hmmm...Now...what was that long drawn out conversation....that addressed private space in a good way.....oh yeah! ULA-C!
From: ppml-bounces at arin.net [mailto:ppml-bounces at arin.net]On Behalf Of
Sent: Monday, September 17, 2007 7:00 AM
To: Ted Mittelstaedt; Kevin Kargel; ppml at arin.net
Subject: Re: [ppml] IPv6 flawed?
> You don't understand it because you are large enough to have your
> own allocation.
> For the orgs too small to meet justification requirements to get
> a direct allocation of IPv6 from an RIR, it is a big problem.
> They do not want to get IPv6 from an ISP AKA "local internet registry"
> and put time and money into numbering all their servers and suchlike -
> because if they find a better deal down the street from the ISP's
> (I mean local internet registry's) competitor, they want to be free
> to dump the existing ISP and go to the competitor without having to
> renumber internally.
> This IMHO is the single largest reason so many orgs adopted NAT.
I agree with Ted that there is a noticeable benefit to having NAT
capability, but not that it is the "single largest reason so many orgs
adopted NAT." It does act as a pseudo-security feature, and it does make
a network "portable".
I would have no problem with a say a /32 of IPv6 being set aside as
"private space." This will only increase the longevity of IPv6 when used
by companies who only need limited IP addresses and want to use private
space and NAT. What arguments are there against this?
You are receiving this message because you are subscribed to the ARIN Public Policy
Mailing List (PPML at arin.net).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/ppml Please contact the ARIN Member Services
Help Desk at info at arin.net if you experience any issues.
More information about the ARIN-PPML