The IPv6 Virtual Private Network (VPN) Context Information Option
draft-bonica-6man-vpn-dest-opt-01
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2018-12-10
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
6man R. Bonica
Internet-Draft Juniper Networks
Intended status: Standards Track C. Lenart
Expires: June 13, 2019 Verizon
G. Presbury
Hughes Network Systems
December 10, 2018
The IPv6 Virtual Private Network (VPN) Context Information Option
draft-bonica-6man-vpn-dest-opt-01
Abstract
This document defines a new IPv6 Destination Option that can be used
to encode Virtual Private Network (VPN) context information. It is
applicable when VPN payload is transported over IPv6.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 13, 2019.
Copyright Notice
Copyright (c) 2018 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
(https://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
Bonica, et al. Expires June 13, 2019 [Page 1]
Internet-Draft VPN Dest Opt December 2018
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4
3. VPN Context Information . . . . . . . . . . . . . . . . . . . 4
4. The VPN Context Information Option . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
Virtual Private Network (VPN) technologies allow network providers to
emulate private networks with shared infrastructure. For example,
assume that a red sites and blue sites connect to a provider network.
The provider network facilitates communication among red sites and
facilitates communication among blue sites. However, it prevents
communication between red sites and blue sites.
The IETF has standardized many VPN technologies, including:
o Layer 2 VPN (L2VPN) [RFC6624].
o Layer 3 VPN (L3VPN) [RFC4364].
o Virtual Private LAN Service (VPLS) [RFC4761][RFC4762].
o Ethernet VPN (EVPN) [RFC7432].
o Pseudowires [RFC8077].
The above-mentioned technologies include the following components:
o Customer Edge (CE) devices.
o Provider Edge (PE) devices.
o Routing Instances.
o VPN context information.
Bonica, et al. Expires June 13, 2019 [Page 2]
Internet-Draft VPN Dest Opt December 2018
o Transport tunnels.
CE devices participate in closed communities called VPNs. CEs that
participate in one VPN can communicate with one another but cannot
communicate with CEs that participate in another VPN.
CE devices connect to provider networks through PE devices. Each PE
maintains one Routing Instance for each VPN that it supports. A
Routing Instance is a VPN specific Forwarding Information Base (FIB).
In EVPN, Routing Instances are called Ethernet Virtual Instances
(EVI).
Assume that one CE sends a packet through a provider network to
another CE. The packet enters the provider network through an
ingress PE and leaves the provider network through an egress PE. The
Show full document text