Internet-Draft Kenji Fujisawa Sony Corporation Expires: November, 1998 DHCP on IEEE 1394 Status of this memo This document is an Internet-Draft. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as ``work in progress.'' To view the entire list of current Internet-Drafts, please check the "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). Abstract IEEE Std 1394-1995 is a standard for a High Performance Serial Bus. Since 1394 uses different link-layer addressing method than conventional IEEE802/Ethernet, the usage of some fields must be clarified to achieve interoperability. This memo proposes the 1394 specific usage of some fields of DHCP messages. K. Fujisawa Expires November 1998 [Page 1] Internet Draft draft-fujisawa-ip1394-dhcp-00.txt May 1998 1. Introduction IEEE Std 1394-1995 is a standard for a High Performance Serial Bus. IETF IP1394 Working Group is standardizing the method to carry IPv4 datagrams and ARP packets over IEEE1394 subnetwork [1394]. The Dynamic Host Configuration Protocol (DHCP) [RFC2131] provides a framework for passing configuration information to hosts on a TCP/IP network. Since 1394 uses different link-layer addressing method than conventional IEEE802/Ethernet, the usage of some fields must be clarified to achieve interoperability. This memo proposes the 1394 specific usage of some fields of DHCP. See [RFC2131] for the mechanism of DHCP and the explanations of each fields. 2. 1394 specific usage of DHCP message fields Following rules should be used when the DHCP client is connected to IEEE1394 subnetwork. 'htype' (hardware address type) should be 0x18. 'hlen' (hardware address length) should be 16. The format of the 'chaddr' (client hardware address) is specified as follows, 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | node_ID | unicast_FIFO_hi | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | unicast_FIFO_lo | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | max_rec | spd | reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The value of 'node_ID', 'unicast_FIFO', 'max_rec' and 'spd' sub-fields should be the same value used by ARP specified in [1394]. Note that, since 'node_ID' may be reassigned on 1394 bus-reset, 'chaddr' can not be used for the client identification, 'client identifier' option MUST be used in DHCP messages from the client to the server. 'chaddr' will be used only to return a message from the server (or DHCP relay-agent) to the client. K. Fujisawa Expires November 1998 [Page 2] Internet Draft draft-fujisawa-ip1394-dhcp-00.txt May 1998 'client identifier' option may consist of any data, but when using node unique ID (EUI-64) for the 'client identifier', the format is illustrated as follows. Code Len Type Client-Identifier +-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+ | 61 | 9 | 0x18| node unique ID | +-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+ For more details, see "9.14. Client-identifier" in [RFC2132]. Security Considerations Security issues are not discussed in this document. References [1394] IP1394 Working Group, "IPv4 over IEEE 1394", draft-ietf-ip1394-ipv4-08.txt, work in progress [RFC2131] R. Droms, "Dynamic Host Configuration Protocol", RFC2131, March 1997 [RFC2132] S. Alexander, and R. Droms, "DHCP Options and BOOTP Vendor Extensions", RFC2132, March 1997 Author's address Kenji Fujisawa Sony Corporation IT Laboratories, Computer Systems Laboratory 6-7-35, Kitashinagawa, Shinagawa-ku, Tokyo, 141-0001 Japan Phone: +81-3-5448-4602 E-mail: fujisawa@sm.sony.co.jp K. Fujisawa Expires November 1998 [Page 3]