Dynamic No-Entry Zone Dissemination in IPv6 Vehicular Networks
draft-jun-chen-ipwave-dynamic-no-entry-zone-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jun Chen | ||
| Last updated | 2026-05-25 (Latest revision 2025-11-21) | ||
| 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
This document defines the Dynamic No-Entry Zone (DNEZ) information element and its dissemination mechanism using IPv6-based vehicular networks. A DNEZ is a temporary lane-level polygonal area generated by a stopped or faulty vehicle to indicate a region that surrounding vehicles may need to avoid. The primary use case is to provide redundancy when roadside perception systems fail due to occlusion, weather, or infrastructure limitations. The DNEZ is disseminated using geographically-scoped IPv6 multicast (GeoBroadcast) as defined in RFC 9366. Receiving vehicles or Road Side Units (RSUs) may rebroadcast the message to extend coverage. Local interpretation and usage of the DNEZ is implementation-specific and outside the scope of this document.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)