Guidelines on the structure of a PPVPN Layer 2 solution document
draft-carugi-ppvpn-l2solution-doc-guidelines-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Marco Carugi | ||
| Last updated | 2003-03-04 | ||
| 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 provides guidelines on how to structure a PPVPN Layer 2 solution document. The intent is to provide a common way of describing the various functional components of a Layer 2 solution, making easier their identification as well as the mechanisms providing those functionalities, and, possibly, facilitating further convergence in the solution space. These guidelines have been discussed internally to the PPVPN Layer 2 design team and agreed as a recommendation, although not mandatory, to authors of PPVPN L2 solution drafts.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)