RFC 4833: Timezone Options for DHCP
In plain English — editorial summary, not part of the RFC
Two common ways to communicate timezone information are POSIX 1003.1 timezone strings and timezone database names. This memo specifies DHCP options for each of those methods. The DHCPv4 time offset option is deprecated. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4833
- Published
- April 2007
- Authors
- E. Lear; P. Eggert
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 10
- Also known as
- —
- Updates:
- RFC 2132
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4832Security Threats to Network-Based Localized Mobility Management (NETLMM)Current
April 2007
- RFC 4831Goals for Network-Based Localized Mobility Management (NETLMM)Current
April 2007
- RFC 4830Problem Statement for Network-Based Localized Mobility Management (NETLMM)Current
April 2007
- RFC 4857Mobile IPv4 Regional RegistrationCurrent
June 2007
- RFC 4861Neighbor Discovery for IP version 6 (IPv6)Updated
September 2007
- RFC 4862IPv6 Stateless Address AutoconfigurationUpdated
September 2007
- RFC 4866Enhanced Route Optimization for Mobile IPv6Current
May 2007
- RFC 4795Link-local Multicast Name Resolution (LLMNR)Current
January 2007
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?