RFC 4776: Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information
In plain English — editorial summary, not part of the RFC
This document specifies a Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) option containing the civic location of the client or the DHCP server. The Location Configuration Information (LCI) includes information about the country, administrative units such as states, provinces, and cities, as well as street addresses, postal community names, and building information. The option allows multiple renditions of the same address in different scripts and languages. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4776
- Published
- November 2006
- Authors
- H. Schulzrinne
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 19
- Also known as
- —
- Obsoletes:
- RFC 4676
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3825Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration InformationObsoleted
July 2004
- RFC 4780Management Information Base for the Session Initiation Protocol (SIP)Current
April 2007
- RFC 4769IANA Registration for an Enumservice Containing Public Switched Telephone Network (PSTN) Signaling InformationUpdated
November 2006
- RFC 4788Enhancements to RTP Payload Formats for EVRC Family CodecsUpdated
January 2007
- RFC 4759The ENUM Dip Indicator Parameter for the "tel" URICurrent
December 2006
- RFC 4749RTP Payload Format for the G.729.1 Audio CodecUpdated
October 2006
- RFC 4745Common Policy: A Document Format for Expressing Privacy PreferencesCurrent
February 2007
- RFC 4734Definition of Events for Modem, Fax, and Text Telephony SignalsCurrent
December 2006
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?