Requirements for a Zero-Configuration IPv6 CPE
draft-baker-v6ops-cpe-autoconfigure-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Fred Baker | ||
| Last updated | 2017-12-19 (latest revision 2017-06-17) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-baker-v6ops-cpe-autoconfigure-00.txt
https://www.ietf.org/archive/id/draft-baker-v6ops-cpe-autoconfigure-00.txt
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
Fred Baker (fredbaker.ietf@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)