[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: DNSEXT WGLC: IPv6 Name Auto Registration
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "jinmei" == jinmei <Tatuya / ~~~~ <jinmei@isl.rdc.toshiba.co.jp>> writes:
>> I see two individual problems:
>> 1. The device (according to the draft) has a problem knowing its FQDN.
>> DHCP will happily supply that information.
jinmei> Okay, then are you also assuming the DHCPv6 server assigns the
jinmei> IPv6 address(es) of the client? Or are you thinking of some
jinmei> registration mechanism from the client (that configures its
jinmei> address(es) in a stateless manner) to the server?
I would think that the address of the DHCPv6 servers should simply
be returned by one (or all) of the routers in the router advertisements.
(As an option)
As a fallback, the DHCPv6 server could have a well known link local
address. RS/RA gets you on the network. RFC2462 says:
stateful autoconfiguration complement each other. For example, a host
can use stateless autoconfiguration to configure its own addresses,
but use stateful autoconfiguration to obtain other information.
Stateful autoconfiguration for IPv6 is the subject of future work
[DHCPv6].
The key thing to realize is that DHCP{v4} does not just do address
configuration - it establishes some level of trust between the end node and
the infrastructure. In particular, a random v6 node is just NOT going to have
any trust relationship with the DNS server such that it can update the
reverse map. A DHCP server can have that.
The DHC WG is working on ways of making that trust stronger.
SEND is also doing similar things. This is not a DNSext issue.
] ON HUMILITY: to err is human. To moo, bovine. | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Finger me for keys
iQCVAwUBPkRTf4qHRg3pndX9AQGwYgP/TdfnlN9lPHjiXqx5RI/DeAPmKEfR4vkW
qJh2R/xL5hygEhFly9FUxAkJzkdMcxP8mtU2x2LHdHzQ0ZI26oanMMgjfQ0p6GUJ
nK9NrYg4NF2qLAM2L8NuV0C+WwCHVo8lGNV4IL5gMV9KYpbE0hITn/ZCageyxjn6
qgXFxdSkoY8=
=0/DK
-----END PGP SIGNATURE-----
--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>