Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Clarifications and Extensions for the Bootstrap Protocol (RFC1542)

IP.com Disclosure Number: IPCOM000002374D
Original Publication Date: 1993-Oct-01
Included in the Prior Art Database: 2000-Sep-12
Document File: 19 page(s) / 49K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

W. Wimer: AUTHOR

Abstract

Some aspects of the BOOTP protocol were rather loosely defined in its original specification. In particular, only a general description was provided for the behavior of "BOOTP relay agents" (originally called BOOTP forwarding agents"). The client behavior description also suffered in certain ways. This memo attempts to clarify and strengthen the specification in these areas. Due to some errors introduced into RFC 1532 in the editorial process, this memo is reissued as RFC 1542.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 6% of the total text.

Network Working Group W. Wimer

Request for Comments: 1542 Carnegie Mellon University

Updates: 951 October 1993

Obsoletes: 1532

Category: Standards Track

Clarifications and Extensions for the Bootstrap Protocol

Status of this Memo

This RFC 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" for the standardization state and status

of this protocol. Distribution of this memo is unlimited.

Abstract

Some aspects of the BOOTP protocol were rather loosely defined in its

original specification. In particular, only a general description

was provided for the behavior of "BOOTP relay agents" (originally

called BOOTP forwarding agents"). The client behavior description

also suffered in certain ways. This memo attempts to clarify and

strengthen the specification in these areas. Due to some errors

introduced into RFC 1532 in the editorial process, this memo is

reissued as RFC 1542.

In addition, new issues have arisen since the original specification

was written. This memo also attempts to address some of these.

Table of Contents

1. Introduction................................................. 2

1.1 Requirements................................................ 3

1.2 Terminology................................................. 3

1.3 Data Transmission Order..................................... 4

2. General Issues............................................... 5

2.1 General BOOTP Processing.................................... 5

2.2 Definition of the 'flags' Field............................. 5

2.3 Bit Ordering of Hardware Addresses.......................... 7

2.4 BOOTP Over IEEE 802.5 Token Ring Networks................... 8

3. BOOTP Client Behavior........................................ 9

3.1 Client use of the 'flags' field............................. 9

3.1.1 The BROADCAST flag........................................ 9

3.1.2 The remainder of the 'flags' field........................ 9

3.2 Definition of the 'secs' field.............................. 10

3.3 Use of the 'ciaddr' and 'yiaddr' fields..................... 10

3.4 Interpretation of the 'giaddr' field........................ 11

3.5 Vendor information "magic cookie"........................... 12

4. BOOTP Relay Agents........................................... 13

4.1 General BOOTP Processing for Relay Agents......................