Iljitsch van Beijnum wrote:
On 19 nov 2007, at 14:16, Richard Pruss wrote:

http://www.ietf.org/internet-drafts/draft-pruss-dhcp-auth-dsl-02.txt

Doesn't seem to address IPv6. This makes it useless in my book.

Ahh, you have written a book on authentication in DSL architectures... ;-)

No. I'm guessing that would be a short book. Especially the IPv6 part, as doing IPv6 over PPP isn't workable in practice.
Why not? AFAIK, the earlier cited SP that has provided IPv6 since 2001 (NTT) delivers it over PPP, so I'm really puzzled now.

If you point me to the IPv6 deployment architecture from the DSLForum I can send you a draft on how to do the authentication in it. Putting EAP into DHCP v6 is no big trick, the real trick is what does the rest of the IPv6 architecture look like.

Most hosts running IPv6 today don't run DHCPv6. If I'm not going to run DHCPv6 to learn IPv6 nameserver addresses, I'm also not going to do it just because my DSL provider wants me to.
But your provider-spec'd CPE might run DHCPv6 PD, and then of course your host doesn't have to.

In any case, these are exactly the things that the DSLF, and more importantly the DSL industry, needs to nail down. It has barely broached the topic thus far for IP sessions.

There are a ton of questions like:

[...]

It is simply premature to guess at what authentication is appropriate

Does it make sense to go forward with something that requires an update for ALL (new?) customers only to redo much of the same for IPv6, probably less than two years later?

Figuring out how we want to do IPv6 over DSL (and cable) and then making all the changes in one go seems like a much more sensical approach to me.
However sensical, I don't think gating incremental developments in IPv4 service on IPv6 is a very realistic option in practice - not to mention hoping that the DSL and Cable industries will work harmoniously with one another ;-)

- 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