ZEROCONF

1
ZEROCONF

• Zero Configuration Networking
• 330pm - 530pm
• zeroconf-request_at_merit.edu
• Stuart Cheshire ltcheshire_at_apple.comgt
• Erik Guttman ltErik.Guttman_at_sun.comgt

2
Agenda

• 330 5 min Agenda Bashing Stuart Erik
• 345 30min IP linklocal draft 01
  discussion Stuart
• 335 10min End result of requirements draft Erik
• 415 30min MC address allocation protocol Steve
  Hanna
• 445 10min Report on DNSEXT work on mDNS Bernard
  Aboba
• 455 15min ZC security draft Aidan Williams
• Steve Hanna
• 510 15min Plug for networked appliances
  BOF Simon Tsang
• Stan Moyer
• 525 5min Going forward - Schedule and Goals Erik
  Stuart

3
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

4
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)

5
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?