Definition of a Common Management Interface Format
draft-liu-ipsec-vpn-management-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Quentin Liu | ||
| Last updated | 1997-12-30 | ||
| 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 defines a common interface format for describing the configuration of a Virtual Private Network (VPN) in the context of IPSec and equipment from different vendors. The configuration format would be both importable and exportable by various vendors of VPN equipment and software that is IPSec compliant, facilitating an uniform and perhaps automated method of interoperability (creating a VPN) between VPN products from different vendors. This document will only discuss the proposed configuration format. The mechanism by which the file is propagated is beyond the scope of this document and will not be discussed. A security association is not mandatory between two management stations from different vendors wishing to employ this method of VPN configuration, as this configuration format can easily be packaged in a file and propagated out of band.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)