RFC 2855 on DHCP for IEEE 1394
RFC Editor <rfc-ed@ISI.EDU> Tue, 13 June 2000 19:04 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19182; Tue, 13 Jun 2000 15:04:48 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id OAA28627 for ietf-123-outbound.10@ietf.org; Tue, 13 Jun 2000 14:55:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id OAA28592 for <all-ietf@loki.ietf.org>; Tue, 13 Jun 2000 14:49:05 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18831 for <all-ietf@ietf.org>; Tue, 13 Jun 2000 14:49:03 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id LAA14978; Tue, 13 Jun 2000 11:49:03 -0700 (PDT)
Message-Id: <200006131849.LAA14978@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2855 on DHCP for IEEE 1394
Cc: rfc-ed@ISI.EDU, ip1394@mailbag.cps.intel.com
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 13 Jun 2000 11:49:03 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2855 Title: DHCP for IEEE 1394 Author(s): K. Fujisawa Status: Standards Track Date: June 2000 Mailbox: fujisawa@sm.sony.co.jp Pages: 5 Characters: 8070 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ip1394-dhcp-04.txt URL: ftp://ftp.isi.edu/in-notes/rfc2855.txt IEEE Std 1394-1995 is a standard for a High Performance Serial Bus. Since 1394 uses a different link-layer addressing method than conventional IEEE802/Ethernet, the usage of some fields must be clarified to achieve interoperability. This memo describes the 1394 specific usage of some fields of DHCP messages. This document is a product of the IP Over IEEE 1394 Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
- RFC 2855 on DHCP for IEEE 1394 RFC Editor