Iljitsch van Beijnum wrote:

Irritation is irrelevant. What's relevant is that the IETF is a slow moving standards organization. Unless a lot of people are very wrong, any work started today will be relevant during the period in time where we run out of IPv4 addresses. The way I see it, that makes it necessary for any and all technologies that the IETF works on, and especially the ones that it starts new work on, must be able to work with both IPv4 and IPv6. Maybe the IPv6 part isn't going to be implemented immediately. That's a decision that each vendor / service provider has to make for themselves. But the IETF can't ignore IPv6, which, so far, pretty much all participants in this discussion have been doing.
This would not be the first proposal to enter the IETF with its primary focus on IPv4. Indeed, during my tenure on the IESG I have reviewed a number of documents which either did not have IPv6 basics included at all, or did in passing with a number of associated errors and omissions. It is for this that I asked Margaret Wasserman to give a tutorial presentation at the int-area meeting a year or so ago to identify common problems that she had seen with documents which do not correctly consider IPv6. I think she did a great job.

So, while you certainly are solving problems with IPv6 in the forefront of your mind, not all of the IETF, or industry at large, is. It is clearly our job as shepherds of IPv6 to make sure that anything developed for IPv4 works with IPv6, and as well to design new and improved capabilities into IPv6 that do not exist in IPv4. 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.

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.

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.

- Mark


_______________________________________________
Int-area mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/int-area



_______________________________________________
Int-area mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/int-area

Reply via email to