Dear participants in MIF WG, Currently draft-ietf-mif-dhcpv6-route-option-04 specifies that the lifetime of a route (and implicitely of a default route) is to be 32bit length field.
On another hand, the currently implemented default routes are implemented according to ND Neighbor Discovery, which uses route_r_ lifetime on 16bit (RFC 4861 search "Router Lifetime"). I think this is an issue. It generates additional work to the implementer. If one agrees that it is good to store the DHCP default route in the existing ND data structures, then one notices a conversion is needed. If these lifetime fields were expressed in the same number of bits (preferably 16bit, because that exists already) then the implementer would be relieved from conversion work. I wanted to ask the oppinion of the WG about this issue. Yours, Alex _______________________________________________ mif mailing list mif@ietf.org https://www.ietf.org/mailman/listinfo/mif
