IPv6-Mostly Networks: Deployment and Operations Considerations
draft-link-v6ops-6mops-01
| Document | Type |
Replaced Internet-Draft
(v6ops WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jen Linkova , Nick Buraglio | ||
| Last updated | 2024-08-16 (Latest revision 2024-07-07) | ||
| Replaced by | draft-ietf-v6ops-6mops | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-v6ops-6mops | |
| Consensus boilerplate | Unknown | ||
| 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 discusses a deployment scenario called "an IPv6-Mostly network", when IPv6-only and IPv4-enabled endpoints coexist on the same network (network segment, VLAN, SSID etc).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)