GEOPRIV support for RADIUS
draft-jones-radius-geopriv-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Hannes Tschofenig | ||
Last updated | 2004-02-10 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Network access servers are increasingly capable of providing user and device location information to AAA servers. This enables the AAA server to make additional authorization decisions based on the location of the user or access device. The home or visited network may also use the location information for other purposes (e.g., acting as a location server). This document provides guidelines for the encoding and transport of location information using the RADIUS protocol which are compliant with the Geopriv requirements for security and privacy.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)