HIP-based Virtual Private LAN Service (HIPLS)
draft-henderson-hip-vpls-11
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Thomas R. Henderson , Steven C. Venema , David Mattes | ||
| Last updated | 2017-02-04 (Latest revision 2016-08-03) | ||
| 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
The Host Identity Protocol (HIP) and architecture adds a cryptographic name space to name Internet hosts. This draft describes a use case of the HIP architecture, which is to provide a HIP-enabled virtual private LAN service (VPLS) over an untrusted network. In this case, HIP is used to secure tunnels between the provider edge (PE) equipment.
Authors
Thomas R. Henderson
Steven C. Venema
David Mattes
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)