On 7 nov 2007, at 15:45, Mark Townsley wrote:
[...]
However, to suggest that new work on IPv4 be halted because the
authors did not start out with IPv6 in the forefront of their minds
is rather unrealistic.
I certainly don't have a problem with people starting with IPv4 -
after all, that's still what brings in the money.
The problem here is that the suggested work isn't something that's
limited to IPv4, in the same way that work on OSPFv2 is limited to
IPv4. What we're talking about is authentication, something that needs
to happen before people get access to the network. By doing this over
IPv4 we are likely to create two problems:
1. Running IPv6-only -> no authentication -> no access
2. Running dual stack isn't addressed so it probably requires
additional "stuff" that's left out of the spec -> bad interoperability
Back to the issue at hand, I see no technical reason why EAP in
DHCPv6 would not work in largely the same fashion as the proposed
EAP in DHCPv4. I doubt the authors have any aversion at all to
specifying this in detail, with the help of the IETF to ensure that
it is done correctly.
Well, at least that would be something. The practical problem with
that is that the boxes involved now have to snoop two different
protocols, which probably means that this isn't going to be
implemented in practice any time soon. On a more fundamental level,
this makes implementation of DHCPv6 a de facto requirement for IPv6
hosts, something I REALLY don't like.
In my opinion, if doing something is creates so many problems that
usually means the approach is wrong.
Also, when you need to make changes at both ends, that's an
opportunity to get stuff right, because you don't get to do that all
that often.
As for IPv6 deployment for DSL, I will be raising this at the
architecture group session and plenary during the next quarterly DSL
Forum meeting in the hopes of spurring more active development and
deployment.
Great.
_______________________________________________
Int-area mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/int-area
