Civic Location and Geospatial Coordinate Support in IPv6 ND
draft-gundavelli-6man-nd-location-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Sri Gundavelli | ||
| Last updated | 2024-01-13 (Latest revision 2023-07-12) | ||
| 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
The physical location of a network device plays a crucial role in various applications, particularly in emergency calling, where precise caller location information is essential for prompt and effective emergency response. RFC 4676 has standardized DHCP options for delivering the Civic Location of the client, while RFC 6225 has defined DHCP options for delivering the Geospatial coordinates of the client. However, these corresponding options are missing in IPv6 Neighbor Discovery protocols. This proposal aims to address this gap by introducing the necessary options for IPv6 Neighbor Discovery to provide accurate location information.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)