#6: Lifetime field length should be 16bit for ND compatibility
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.
--
-------------------------+-------------------------------------------------
Reporter: | Owner: draft-ietf-mif-dhcpv6-route-
alexandru.petrescu@… | option@…
Type: enhancement | Status: new
Priority: minor | Milestone: milestone1
Component: dhcpv6 | Version:
-route-option | Keywords:
Severity: In WG Last |
Call |
-------------------------+-------------------------------------------------
Ticket URL: <http://trac.tools.ietf.org/wg/mif/trac/ticket/6>
mif <http://tools.ietf.org/mif/>
_______________________________________________
mif mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/mif
