That would take too long to get organized. Just suspend fees and policy
requirements and give one to each of the first 400 requestors. Overall it
would reduce costs related to evaluating "need", so the lack of fee income
would not be a major loss.
(just kidding)
I am not ... It is long past time to move on, so getting rid of the
distraction might help with those still holding out hope.
Tony
Owen
>
> If you have been keeping an eye on the ARIN IPV4 countdown, they
allocated their last /23 yesterday. There are only 400 /24s in the pool
Owen DeLong wrote:
> I vote for a /24 lotto to get rid of the rest!
That would take too long to get organized. Just suspend fees and policy
requirements and give one to each of the first 400 requestors. Overall it
would reduce costs related to evaluating "need", so the lack of fee income
would not be a major loss.
>
> (just kidding)
I am not ... It is long past time to move on, so getting rid of the
distraction might help with those still holding out hope.
It won't be long, ARIN has been processing over 350 IPv4 requests each
of the last few months.
Who is the layman in this story? Almost every system I work with at home and in the datacenter has IPv6 turned on by default. If someone wandered through those networks, and started turning on IPv6 infrastructure so that they started getting IPv6 addresses, my bet is that most of the java-based applications would already be bound to the stacks in such a way that they would just start sending traffic over IPv6. I base this on the fact that any number of developers have been confused by “::” being somewhere in their world now. Those people don’t care about the network, or IPv4 vs IPv6. It would just work.
Now, if layman == Network Operators, and Networking people at Corporations, well, there you might be right.
Since IPV6 does not have NAT, it's going to be difficult for the layman to understand their firewall. deployment of ipv4 is pretty simple. ipv6 on the otherhand is pretty difficult at the network level. yes, all the clients get everything automatically except for the router/firewall.
Absolute garbage. CPE already ship with basically the same controls
for IPv6 as for IPv4. Default block in except reply traffic +
specified holes for services you want to open up to the world. The
is same paradigm that has been in use in IPv4 for a years now.
Since IPV6 does not have NAT, it's going to be difficult for the layman to
understand their firewall. deployment of ipv4 is pretty simple. ipv6 on
the otherhand is pretty difficult at the network level. yes, all the
clients get everything automatically except for the router/firewall.
Enabling IPv6 on my CPE was extremely difficult, yes. It took three
extra clicks to enable connection sharing and then subsequently enable
incoming connections.
> I am not ... It is long past time to move on, so getting rid of the
> distraction might help with those still holding out hope.
i think that is unfair to the ipv6 fanboys (and girls). ipv6 use is
increasing
slowly. i bet it hits 10% by the time we retire.
Are you planning to retire this year? Select a logistic curve for 1800 days
forward at:
While the base curve it runs on is running ahead of the measured traffic
curve, the measure of IPv6 enabled browsers is a reasonable indicator for
what is happening.
While the base curve it runs on is running ahead of the measured traffic
curve, the measure of IPv6 enabled browsers is a reasonable indicator for
what is happening.
we're an isp, with ipv6 enabled since 1997. we measure real traffic,
not wishes of what could be.
Wait… You’re trying to convince me that it’s easier to understand “You have this box in the way. It blocks many of the packets you want and some of the packets you don’t want. It also does weird things to the header in the process.” than it is to understand “You have this box. By default it only allows outbound connections and blocks all incoming connections. You can tell it what you want to permit inbound. Your packet headers are the same on both sides of the box.”
You have a different definition of “easy to understand” than I do.