RFC 5580: Carrying Location Objects in RADIUS and Diameter
In plain English — editorial summary, not part of the RFC
This document describes procedures for conveying access-network ownership and location information based on civic and geospatial location formats in Remote Authentication Dial-In User Service (RADIUS) and Diameter. The distribution of location information is a privacy-sensitive task. Dealing with mechanisms to preserve the user's privacy is important and is addressed in this document. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5580
- Published
- August 2009
- Authors
- H. Tschofenig; F. Adrangi; M. Jones; A. Lior; B. Aboba
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 53
- Also known as
- —
- Updated by:
- RFC 8559
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 5687GEOPRIV Layer 7 Location Configuration Protocol: Problem Statement and RequirementsCurrent
March 2010
- RFC 5090RADIUS Extension for Digest AuthenticationCurrent
February 2008
- RFC 5030Mobile IPv4 RADIUS RequirementsCurrent
October 2007
- RFC 4675RADIUS Attributes for Virtual LAN and Priority SupportCurrent
September 2006
- RFC 4673RADIUS Dynamic Authorization Server MIBCurrent
September 2006
- RFC 4672RADIUS Dynamic Authorization Client MIBCurrent
September 2006
- RFC 4590RADIUS Extension for Digest AuthenticationObsoleted
July 2006
- RFC 4372Chargeable User IdentityCurrent
January 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?