Subject: [spring] FW: New Version Notification for draft-dong-spring-sr-for-enhanced-vpn-00.txt

From: "Dongjie (Jimmy)" <[email-masked]>
Date: Tue, 6 Mar 2018 01:50:37 +0000

Dear all, 

We have submitted a new spring draft draft-dong-spring-sr-for-enhanced-vpn, which describes a segment routing based mechanism to provide enhanced VPN service.

Comments are appreciated. 

Best regards,
Jie

-----Original Message-----

A new version of I-D, draft-dong-spring-sr-for-enhanced-vpn-00.txt
has been successfully submitted by Jie Dong and posted to the IETF repository.

Name:		draft-dong-spring-sr-for-enhanced-vpn
Revision:	00
Title:		Segment Routing for Enhanced VPN Service
Document date:	2018-03-05
Group:		Individual Submission
Pages:		10
URL:            https://www.ietf.org/internet-drafts/draft-dong-spring-sr-for-enhanced-vpn-00.txt
Status:         https://datatracker.ietf.org/doc/draft-dong-spring-sr-for-enhanced-vpn/
Htmlized:       https://tools.ietf.org/html/draft-dong-spring-sr-for-enhanced-vpn-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-dong-spring-sr-for-enhanced-vpn-00

Abstract:
   Enhanced VPN (VPN+) is an enhancement to VPN technology to enable it
   to support the needs of new applications, particularly applications
   that are associated with 5G services.  These applications require
   better isolation and have more stringent performance requirements
   than can be provided with overlay VPNs.  The characteristics of an
   enhanced VPN as perceived by its tenant needs to be comparable to
   those of a dedicated private network.  This requires tight
   integration between the overlay VPN and the underlay network
   resources in a scalable manner.  An enhanced VPN may form the
   underpin of 5G network slicing, but will also be of use in its own
   right.  This document describes the use of segment routing based
   mechanisms to provide the enhanced VPN service with dedicated
   underlay network resources.

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat