ObsoletedPROPOSED STANDARDIETF stream

RFC 3825: Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6225.

Current version: RFC 6225Dynamic Host Configuration Protocol Options for Coordinate-Based Location Configuration Information

In plain English — editorial summary, not part of the RFC

This document specifies a Dynamic Host Configuration Protocol Option for the coordinate-based geographic location of the client. The Location Configuration Information (LCI) includes latitude, longitude, and altitude, with resolution indicators for each. The reference datum for these values is also included. [STANDARDS-TRACK]

Document record

Document ID
RFC3825
Published
July 2004
Authors
J. Polk; J. Schnizlein; M. Linsner
Status
PROPOSED STANDARD
Stream
IETF
Area
rai
Pages
15
Also known as
Obsoleted by:
RFC 6225

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.

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?

canonical URL: /rfc/3825-dynamic-host-configuration-protocol-option-for-coordinate-based-location-configu