CPE Default Route Detection
draft-vandevelde-v6ops-cpe-default-route-detection-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Gunter Van de Velde , John Jason Brzozowski , Shin Miyakawa | ||
| Last updated | 2008-02-13 | ||
| 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
When the CPE (Customer Premisses Equipment) device is a routed IPv6 device, then detection automation of the upstream connectivity (i.e. the default-route) has not been uniformly described. There are many CPE vendors, and they may have many technologies to achieve this goal. This document provides an overview of the problem space, while identifying various options within the solution space.
Authors
Gunter Van de Velde
John Jason Brzozowski
Shin Miyakawa
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)