Keyed IPv6 Tunnel
RFC 8159

Document Type RFC - Proposed Standard (May 2017; No errata)
Last updated 2017-05-05
Replaces draft-mkonstan-l2tpext-keyed-ipv6-tunnel
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd Carlos Pignataro
Shepherd write-up Show (last changed 2015-07-01)
IESG IESG state RFC 8159 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Deborah Brungard
Send notices to draft-ietf-l2tpext-keyed-ipv6-tunnel.all@ietf.org
IANA IANA review state IANA OK - No Actions Needed
IANA action state No IC
Internet Engineering Task Force (IETF)           M. Konstantynowicz, Ed.
Request for Comments: 8159                                 G. Heron, Ed.
Category: Standards Track                                  Cisco Systems
ISSN: 2070-1721                                            R. Schatzmayr
                                                     Deutsche Telekom AG
                                                           W. Henderickx
                                                    Alcatel-Lucent, Inc.
                                                                May 2017

                           Keyed IPv6 Tunnel

Abstract

   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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc8159.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Konstantynowicz, et al.      Standards Track                    [Page 1]
RFC 8159                    Keyed IPv6 Tunnel                   May 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Static 1:1 Mapping without a Control Plane  . . . . . . . . .   3
   3.  64-Bit Cookie . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Encapsulation . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Fragmentation and Reassembly  . . . . . . . . . . . . . . . .   7
   6.  OAM Considerations  . . . . . . . . . . . . . . . . . . . . .   7
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  11
   Contributors  . . . . . . . . . . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   L2TPv3, as defined in [RFC3931], provides a mechanism for tunneling
   Layer 2 (L2) "circuits" across a packet-oriented data network (e.g.,
   over IP), with multiple attachment circuits multiplexed over a single
   pair of IP address endpoints (i.e., a tunnel) using the L2TPv3
   Session ID as a circuit discriminator.

   Implementing L2TPv3 over IPv6 [RFC2460] provides the opportunity to
   utilize unique IPv6 addresses to identify Ethernet attachment
   circuits directly, leveraging the key property that IPv6 offers -- a
   vast number of unique IP addresses.  In this case, processing of the
   L2TPv3 Session ID may be bypassed upon receipt, as each tunnel has
   one and only one associated session.  This local optimization does
   not hinder the ability to continue supporting the multiplexing of
   circuits via the Session ID on the same router for other L2TPv3
   tunnels.

   There are various advantages to this approach when compared to the
   "traditional" L2TPv3 approach of using a loopback address to
   terminate the tunnel and then carrying multiple sessions over the
   tunnel.  These include better ECMP load balancing (since each tunnel
   has a unique source/destination IPv6 address pair) and finer-grained
   control when advertising tunnel endpoints using a routing protocol.
Show full document text