> From: Brian E Carpenter <brian.e.carpenter@xxxxxxxxx>
> The problem is that the creation of disjoint addressing realms (due to
> NAT and to IPv4/IPv6 coexistence) has made distributed application
> design almost impossible without kludges.
See, this is the kind of thing I was talking about in my early post in the
recent incarnation of this thread. Complaining about the existence of
disjoint naming realms, and how it has complicated our lives, is like a
rocket scientist complaining about gravity, and how hard it makes their job.
(OK, it's not quite a perfect analogy, since gravity is fundamental, but I
think my point is clear.)
They were inevitable, end of story. This is the architectural reality we live
in, and we need to accept that, and fully align IETF work around that reality
- and not act like it's a red-headed step-child that will sit in a corner and
be quiet if we don't deign to pay attention to it.
Yes, it does make our lives as engineers a lot harder. Trying to do
fundamental architectural upgrade an enormous, in-service communication
system is hard too - much, much harder than a clean sheet design, and filled
with all sorts of kludges on the edges where you have to interface to
existing stuff. However, if you just accept that that's what you have to do,
and get on with it, you can make non-trivial progress.
Noel
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf