Requirements for a Zero-Configuration IPv6 CPE
draft-baker-v6ops-cpe-autoconfigure-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Fred Baker | ||
Last updated | 2017-12-19 (Latest revision 2017-06-17) | ||
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 note is a breif exploration of what is required for a CPE to be auto-configurable from the perspective on an ISP or other upstream network. It assumes that the CPE may also be IPv4-capable (probably using NAPT), but that the requirements for that are well understood and need no further specification.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)