Response to one specific comment; ignoring/not taking any stand on the rest of the DHCP/RA discussion...
On 4/5/12 1:27 PM, "jouni korhonen" <jouni.nos...@gmail.com> wrote: > > RADEXT is working on > http://tools.ietf.org/html/draft-ietf-radext-ipv6-access-06 > which adds attributes for RFC4191 use, for example. That is then also > implicitly > available for Diameter. > > Assuming unicast RA would be doable using just RFC6085, then there should not > be much, if anything, to do protocol wise. The router that gets provisioned > per > host via AAA knows the l2-l3 mapping already.. and the AAA server also learns > it. For dynamic changes of routes, AAA server can use e.g. l2 or l3 addresses > for a session identification when it sends a change of authorization.. > Yes. The router can learn the L2 to L3 mapping based on the Router Solicitations/Attach Triggers of the host. It can also learn this mapping by being in the Authentication path (supporting Proxy RADIUS), or by means of handling RADIUS triggers. Now, with respect to unicast RA transmission, the clarified L3 multicast/L2 unicast semantic defined in 6085 does allow unicast RA transmission. Sri _______________________________________________ mif mailing list mif@ietf.org https://www.ietf.org/mailman/listinfo/mif
