RFC 2563: DHCP Option to Disable Stateless Auto-Configuration in IPv4 Clients
In plain English — editorial summary, not part of the RFC
This document describes a mechanism by which DHCP servers are able to tell clients that they do not have an IP address to offer, and that the client should not generate an IP address it's own. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2563
- Published
- May 1999
- Authors
- R. Troll
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 9
- Also known as
- —
- Updated by:
- RFC 8925
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1971IPv6 Stateless Address AutoconfigurationObsoleted
August 1996
- RFC 2610DHCP Options for Service Location ProtocolCurrent
June 1999
- RFC 2485DHCP Option for The Open Group's User Authentication ProtocolCurrent
January 1999
- RFC 2855DHCP for IEEE 1394Current
June 2000
- RFC 2269Using the MARS Model in non-ATM NBMA NetworksCurrent
January 1998
- RFC 2242NetWare/IP Domain Name and InformationCurrent
November 1997
- RFC 2225Classical IP and ARP over ATMUpdated
April 1998
- RFC 2937The Name Service Search Option for DHCPCurrent
September 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?