RFC 4676: Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4776.
Current version: 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
- RFC4676
- Published
- October 2006
- Authors
- H. Schulzrinne
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 19
- Also known as
- —
- Obsoleted by:
- RFC 4776
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 3825Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration InformationObsoleted
July 2004
- RFC 4666Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA)Current
September 2006
- RFC 4662A Session Initiation Protocol (SIP) Event Notification Extension for Resource ListsCurrent
August 2006
- RFC 4661An Extensible Markup Language (XML)-Based Format for Event Notification FilteringCurrent
September 2006
- RFC 4660Functional Description of Event Notification FilteringUpdated
September 2006
- RFC 4694Number Portability Parameters for the "tel" URICurrent
October 2006
- RFC 4695RTP Payload Format for MIDIObsoleted
November 2006
- RFC 4696An Implementation Guide for RTP MIDICurrent
November 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?