> > One comment, not directly related to the 6lowpan-nd draft: There are > > countries where service providers are required to know which customer > > is using a particular (global) address at a particular time - we need > > to be able to supply this information to the police on request. This > > is one of the reasons why the control of (stateful) DHCP is useful, > > and where "random processes that run on routers or other equipment" > > make life harder. > > > > I don't think this is an issue. RADIUS Accounting can be used (and is) > to report dynamically assigned IPv6 addressing information, just as it > was with IPv4. > > The relevant IETF RADIUS attributes are - > > Framed-Interface-Id > > Framed-IPv6-Prefix > > Delegated-IPv6-Prefix
That's fine, *if* your infrastructure is Radius based. On the other hand, if your infrastructure is DHCP based, it is definitely an issue - and another stumbling block to the introduction of IPv6. Steinar Haug, Nethelp consulting, [email protected] -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
