RFC 8159: Keyed IPv6 Tunnel
In plain English — editorial summary, not part of the RFC
This document describes a tunnel encapsulation for Ethernet over IPv6 with a mandatory 64-bit cookie for connecting Layer 2 (L2) Ethernet attachment circuits identified by IPv6 addresses. The encapsulation is based on the Layer 2 Tunneling Protocol Version 3 (L2TPv3) over IP and does not use the L2TPv3 control plane.
Document record
- Document ID
- RFC8159
- Published
- May 2017
- Authors
- M. Konstantynowicz; G. Heron; R. Schatzmayr; W. Henderickx
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4667Layer 2 Virtual Private Network (L2VPN) Extensions for Layer 2 Tunneling Protocol (L2TP)Current
September 2006
- RFC 8104Pseudowire (PW) Endpoint Fast Failure ProtectionCurrent
March 2017
- RFC 7893Pseudowire Congestion ConsiderationsCurrent
June 2016
- RFC 7885Seamless Bidirectional Forwarding Detection (S-BFD) for Virtual Circuit Connectivity Verification (VCCV)Current
July 2016
- RFC 8469Recommendation to Use the Ethernet Control WordCurrent
November 2018
- RFC 7392Explicit Path Routing for Dynamic Multi-Segment PseudowiresCurrent
December 2014
- RFC 7026Retiring TLVs from the Associated Channel Header of the MPLS Generic Associated ChannelCurrent
September 2013
- RFC 6310Pseudowire (PW) Operations, Administration, and Maintenance (OAM) Message MappingCurrent
July 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?