In the same way that there is a difference between a bricklayer and an
architect there is a difference between an engineer and a network admin.
If I am going to be a labourer I'd prefer to bring along my jointer and table
saw and pitch in with the hotel rennovations.
The idea of having a whole week without IPv4 is an invitation for half the
membership to decide its the IETF to miss. And its the wrong strategy. The
connection between the laptop and the WiFi access point isn't the problem, its
the connection between the access point and the Internet where we are comming
under pressure.
Run a split network:
IPv4 behind a honking great NAT
IPv6 with external routable IP address
Then attendees have a choice of challenges:
1) Make the applications you need all work from behind an IPv4 NAT
2) Get your platform to run IPv6
I don't see much real value in finding out that a bunch of Internet experts can
manage the second and I see a real downside to discovering that many cannot.
The split network situation is what I expect to see appearing as the IPv4
address pool shrinks. Actually thats the best case scenario, wost case is that
all you can find is just IPv4 NAT.
My transition strategy would be
1) Demonstrate that everyone can get work done in the split network scenario
2) Develop a specification for a T-Box (Transition Box) which is essentially an
extension of current access point, cable, DSL modem etc. NAT capabilities. A
T-Box can plug into an IPv4 or IPv6 connection and provides a transparent
gateway to IPv4 or IPv6 devices - including devices on a mixed v4/v6 network.
3) Persuade the ISPs that they should buy equipment that is T-Box capable as it
is their best chance of being future proof.
4) Write a new architecture document for writing applications that are T-box
friendly. This can also incorporate other goodies we would like to deploy like
security.
________________________________
From: Jari Arkko [mailto:jari(_dot_)arkko(_at_)piuha(_dot_)net]
Sent: Tue 18/12/2007 2:41 PM
To: John C Klensin
Cc: iaoc(_at_)ietf(_dot_)org; ietf(_at_)ietf(_dot_)org; iesg(_at_)ietf(_dot_)org
Subject: Re: IPv4 Outage Planned for IETF 71 Plenary
John,
While I agree with many of your comments, I wanted to touch on this:
Now we also know that skilled engineers and network operators
are capable of configuring their way around those problems.
... Inviting the rest of the community to try to
sort things out in real-time in the plenary is silly at best.
I hope you are not suggesting that there is some significant part of the
IETF community that consists of non-skilled engineers?! ;-)
Jari
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf