Hi folks,
Per my action item from today's IPP WG Telecon, there is
an excellent new I-D from the IETF Zero Configuration WG
(addressing small office, home networks, ad-hoc networks,
etc.) in the directory ftp://ftp.ietf.org/internet-drafts/
<draft-ietf-zeroconf-reqts-02.txt>
- Zeroconf Requirements (10 Jan 2000)
The Abstract and Table of Contents follow:
Abstract
Zero Configuration (Zeroconf) Networks are a particular class of
TCP/IP networks that may be established in the home, in small
offices or even for an adhoc purpose. Zeroconf networks do not
have and should not be expected to have user configurable network
infrastructure such as DHCP, DNS and other administered services.
This is because typical Zeroconf network users neither have the
skill nor desire to configure, administer, or manage a network.
This document presents Zeroconf protocol requirements for four
areas: IP host configuration, domain name to IP address
resolution, IP multicast address allocation, and service
discovery. Security issues and the transitions between a Zeroconf
protocol and a non-Zeroconf protocol are also discussed within
each protocol area.
Table of Contents
1 Overview....................................................2
2 Introduction................................................3
2.1 Reading This Document.....................................3
2.2 Zeroconf Protocols........................................4
2.3 Zeroconf Networks........................................10
3 Scenarios..................................................16
3.1 IP Host Configuration Scenarios..........................16
3.2 Domain Name to IP Address Resolution Scenarios...........18
3.3 IP Multicast Address Allocation Scenarios................19
3.4 Service Discovery Scenarios..............................19
3.5 Additional Scenarios.....................................25
4 Security Requirements......................................25
4.1 ZeroConf Security Threat Analysis........................25
4.2 Security Requirements....................................26
5 Additional Considerations..................................28
5.1 IANA Considerations......................................28
5.2 Internationalization Considerations......................28
5.3 Security Considerations..................................28
6 Full Copyright Statement...................................28
7 Acknowledgements...........................................29
8 References.................................................30
The identified candidates for Service Discovery are IETF SLP v2
(RFC 2608) and (work-in-progress) Microsoft SSDP (Simple Service
Discovery Protocol). Note that the IETF has *not* accepted SSDP
for standards track work and the current SSDP draft is expired.
The scenarios for discovery address printers and file services.
This requirements spec is definitely WELL worth reading.
Cheers,
- Ira McDonald (consulting architect at Sharp Labs America)
(co-editor of SLP 'printer:' template)
High North Inc