Brian,
Yes I did object, we had the same argument then.
At the time my position was a distinctly minority one. Today I think I have won
that argument and I think that people are looking at NAT as an opportunity, not
merely an annoyance.
NAT is only about 30% of the solution. The other two essential components are
an administration model for the transition and a new layering model that
properly abstracts and separates the applications layer from the layer we are
attempting to change.
At this point I am pretty confident that people are going to do the right thing
on NAT. Certainly there are people who know a lot more than me at that layer of
the stack. I can add most value here by pushing on the other two pieces of the
puzzle where I believe change is necessary and where currently my position is
still a minority one.
IPv6 transition is not going to happen unless it is 100% transparent to
application developers and end users.
________________________________
From: Brian E Carpenter
[mailto:brian(_dot_)e(_dot_)carpenter(_at_)gmail(_dot_)com]
Sent: Thu 03/01/2008 2:42 PM
To: Hallam-Baker, Phillip
Cc: Jeroen Massar; michael(_dot_)dillon(_at_)bt(_dot_)com;
ietf(_at_)ietf(_dot_)org
Subject: Re: Deployment Cases
On 2008-01-04 05:30, Hallam-Baker, Phillip wrote:
Yes, as you point out the generic answer to the problem is NAT-PT which was
recently squashed after a cabal got together.
That's a bizarre statement. Which of the technical arguments
in RFC 4966 are you referring to as being products of a cabal?
Did you raise your objections to those arguments during the
IETF Last Call on draft-ietf-v6ops-natpt-to-historic
(issued 2007-03-08)?
My point here is that the thinking on the transition in the IETF to date has
all been of the form 'well everyone is going to have to become like us, only
they can't possibly expect to so its a bit of a problem but not our problem'.
Have you been contributing to ngtrans and v6ops over the last
ten years to correct this wrong way of thinking?
I received a lot of criticism when I first proposed that the IETF embrace NAT
as a transition tool rather than deprecate it. The idea that we should
actively encourage the NAT-ing of IPv4 was considered as unacceptable as
Brian and others now find my proposals for changing the way that the IETF
operates and the considerations it takes into account.
That comparison is a category mistake. And given that NAT-PT was defined
as a co-existence technique in February 2000 (RFC 2766), I'm not sure
I see your point exactly.
I don't see much dispute on that point today. Pretty much everyone seems to
now accept that we are going to run out of IPv4 addresses before IPv6
deployment is complete and that some form of address sharing is therefore
inevitable. What we have failled to do so far is to act on that.
Well, the original plan was that IPv6 would deploy before sharing
of IPv4 addresses started. That didn't happen and of course it's
unfortunate. It's true that those of us who were aghast at the
negative consequences of address sharing did nothing to make it work
better, and wrote about the negative consequences. I make no apology
for my part in that.
Given today's reality, some of the aghast are thinking actively about
how to define a method that isn't broken in the ways described by
RFC 4966.
Brian
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf