Transcript ZEROCONF

ZEROCONF
Zero Configuration Networking
3:30pm - 5:30pm
[email protected]
Stuart Cheshire <[email protected]>
Erik Guttman <[email protected]>
Agenda
3:30
3:45
3:35
4:15
4:45
4:55
5 min
30min
10min
30min
10min
15min
5:10
15min Plug for networked appliances BOF
5:25
Agenda Bashing
IP linklocal draft 01 discussion
End result of requirements draft
MC address allocation protocol
Report on DNSEXT work on mDNS
ZC security draft
5min Going forward - Schedule and Goals
ZEROCONF IETF 49 Dec. 2000
Stuart & Erik
Stuart
Erik
Steve Hanna
Bernard Aboba
Aidan Williams &
Steve Hanna
Simon Tsang &
Stan Moyer
Erik & Stuart
2
IPv4 Link Local Addresses
• Changes in -01
–
–
–
–
–
–
Changed “random” to “pseudo-random”
Only one host has to reconfigure on collision
Explicit mention of NAT
Explains why no subnetting of 169.254 (ARP)
Local-only and global-only hosts on same wire
DHCP server SHOULD NOT assign 169.254
ZEROCONF IETF 49 Dec. 2000
3
DHCP and 169.254?
• Why DHCP server SHOULD NOT assign
169.254
– Host could end up with two 169.254 addresses?
– Old clients may not play by the 169.254 rules
– May be useful for implementers to know
semantics of special address ranges
(e.g. ARP replies from 169.254 are broadcast)
ZEROCONF IETF 49 Dec. 2000
4
DHCP and 169.254?
• Why DHCP server MAY assign 169.254
– Pseudo-random number generator is
implementation-specific
– Remote pseudo-random number generator
accessed via network is valid implementation?
– … using DHCP packets?
ZEROCONF IETF 49 Dec. 2000
5