[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [dhcwg] RFC 3633 Question
Sir Bernie,
Thank you very much for answering my question. It's enough
for me to know that prefix delegation is design for routers. I really appreciate
it.
Sincerely Yours,
Archimedes S. Gaviola
Network Engineer
InfoWeapons Corporation
In IPv6, routers communicate the routing information via
Routing Advertisements (see RFCs 2461 and 2462). There is no need for
DHCPv6 to do this. (And if you don't have a router, why do you need any routing
information.) This type of functionality (Routing Advertisements) doesn't really
exist in IPv4, hence DHCPv4 needed to communicate this
information.
Prefix delegation is primarily design for use by routers,
not hosts (unless a host is also serving as a router).
- Bernie
Hi!
Based
on RFC 3633 - IPv6 Prefix Options for DHCPv6, the specified nodes
involved in the operation are routers such as the requesting router - the router
that acts as a DHCP client that is requesting for prefix(es) and
a delegating router that acts as the DHCP server. My question are, thus the
option (IA_PD) mentioned here is only intended when DHCP is running on
a router ( a packet forwarding node) and not on a host ( non-forwarding packet
node)? Is there a DHCPv6 option for specifying gateway or router just like
in IPv4 when a DHCPv6 is running on a non-forwarding packet node, in
which it will provide options for routers?
Thank you very
much.
Archimedes S.
Gaviola
Network
Engineer
InfoWeapons
Corporation
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
dhcwg mailing list
dhcwg at ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg