RFC1395 on BOOTP Extensions

"Joyce K. Reynolds" <jkrey@isi.edu> Mon, 11 January 1993 23:23 UTC

Message-Id: <199301112321.AA16754@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC1395 on BOOTP Extensions
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 11 Jan 1993 15:22:05 -0800
Sender: List Manager <Postmaster@CNRI.Reston.VA.US>
From: "Joyce K. Reynolds" <jkrey@isi.edu>

A new Request for Comments is now available in online RFC libraries.


        RFC 1395:

        Title:      BOOTP Vendor Information Extensions
        Author:     J. Reynolds
        Mailbox:    jkrey@isi.edu
        Pages:      8
        Characters: 16,314
        Updates:    RFC 951
        Obsoletes:  RFCs 1084, 1048


This RFC is a slight revision and extension of RFC 1048 by Philip
Prindeville, who should be credited with the original work in this
memo.  This memo will be updated as additional tags are are defined.
This edition introduces Tag 14 for Merit Dump File, Tag 15 for Domain
Name, Tag 16 for Swap Server and Tag 17 for Root Path.

This memo is a status report on the vendor information extensions used
in the Bootstrap Protocol (BOOTP).  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@CNRI.RESTON.VA.US.  Requests to be added
to or deleted from the RFC-DIST distribution list should be sent to
RFC-REQUEST@NIC.DDN.MIL.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to "rfc-info@ISI.EDU" with the message body 
"help: ways_to_get_rfcs".  For example:

	To: rfc-info@ISI.EDU
	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 NIC@NIC.DDN.MIL.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1111, "Instructions to RFC
Authors", for further information.


Joyce K. Reynolds
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retreive the ASCII version
of the RFCs.

ftp://nic.ddn.mil/rfc/rfc1395.txt"><ftp://nic.ddn.mil/rfc/rfc1395.txt>

RFC1395 on BOOTP Extensions Joyce K. Reynolds