Carrying Virtual Transport Network Identifier in IPv6 Extension Header
draft-dong-6man-enhanced-vpn-vtn-id-01

Document Type Active Internet-Draft (individual)
Authors Jie Dong  , Zhenbin Li  , Chongfeng Xie  , Chenhao Ma 
Last updated 2020-07-13
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized 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)
Network Working Group                                            J. Dong
Internet-Draft                                                     Z. Li
Intended status: Standards Track                     Huawei Technologies
Expires: January 14, 2021                                         C. Xie
                                                                   C. Ma
                                                           China Telecom
                                                           July 13, 2020

 Carrying Virtual Transport Network Identifier in IPv6 Extension Header
                 draft-dong-6man-enhanced-vpn-vtn-id-01

Abstract

   This document proposes a new option type to carry virtual transport
   network identifier (VTN ID) in the IPv6 extensions headers to
   identify the Virtual Transport Network (VTN) the packet belongs to.
   The procedure of processing the VTN option is also specified.  This
   provides a scalable solution for data plane encapsulation of enhanced
   VPN (VPN+) as described in I-D.ietf-teas-enhanced-vpn.  One typical
   use case of VPN+ is to provide transport network slicing in 5G, while
   it could also be used in more general cases.

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 January 14, 2021.

Copyright Notice

   Copyright (c) 2020 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

Dong, et al.            Expires January 14, 2021                [Page 1]
Internet-Draft               IPv6 VTN Option                   July 2020

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  New IPv6 Extension Header Option for VTN  . . . . . . . . . .   3
   4.  Procedures  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  VTN Option Insertion  . . . . . . . . . . . . . . . . . .   4
     4.2.  VTN based Packet Forwarding . . . . . . . . . . . . . . .   4
   5.  Operational Considerations  . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   8.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   5
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   6
     10.2.  Informative References . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Virtual private networks (VPNs) have served the industry well as a
   means of providing different groups of users with logically isolated
   connectivity over a common network.  Some customers may request a
   connectivity services with advanced characteristics such as complete
   isolation from other services or guaranteed performance.  These
   services are "enhanced VPNs" (known as VPN+).
   [I-D.ietf-teas-enhanced-vpn] describes the framework and candidate
   component technologies for providing enhanced VPN services.  One
   typical use case of VPN+ is to provide transport network slicing in
   5G, while it could also be used in more general cases.

   The enhanced properties of VPN+ require tighter coordination and
   integration between the underlay network resources and the overlay
   network.  VPN+ service is built on a Virtual Transport Network (VTN)
   which has a customized network topology and a set of dedicated or
   shared network resources allocated from the underlay network.  The
   overlay VPN together with the corresponding VTN in the underlay
   provide the VPN+ service.  In the network, traffic of different VPN+
Show full document text