HIP-based Virtual Private LAN Service (HIPLS)

Document Type Expired Internet-Draft (individual)
Authors Thomas Henderson  , Steven Venema  , David Mattes 
Last updated 2017-02-04 (latest revision 2016-08-03)
Stream (None)
Intended RFC status (None)
Expired & archived
plain text htmlized pdfized 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


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.


Thomas Henderson (tomhend@u.washington.edu)
Steven Venema (steve@polyverse.io)
David Mattes (d.mattes@temperednetworks.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)