A Framework for Network Resource Partition (NRP) based Enhanced Virtual Private Networks
draft-ietf-teas-enhanced-vpn-20

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-teas-enhanced-vpn@ietf.org, james.n.guichard@futurewei.com, lberger@labn.net, rfc-editor@rfc-editor.org, teas-chairs@ietf.org, teas@ietf.org
Subject: Document Action: 'A Framework for Network Resource Partition (NRP) based Enhanced Virtual Private Networks' to Informational RFC (draft-ietf-teas-enhanced-vpn-19.txt)

The IESG has approved the following document:
- 'A Framework for Network Resource Partition (NRP) based Enhanced
   Virtual Private Networks'
  (draft-ietf-teas-enhanced-vpn-19.txt) as Informational RFC

This document is the product of the Traffic Engineering Architecture and
Signaling Working Group.

The IESG contact persons are Gunter Van de Velde, Jim Guichard and John
Scudder.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-teas-enhanced-vpn/

Ballot Text

Technical Summary

   This document describes the framework for NRP-based Enhanced Virtual
   Private Networks (VPNs) to support the needs of applications with
   specific traffic performance requirements (e.g., low latency, bounded
   jitter).  NRP-based Enhanced VPNs leverage the VPN and Traffic
   Engineering (TE) technologies and adds characteristics that specific
   services require beyond those provided by conventional VPNs.
   Typically, an NRP-based enhanced VPN will be used to underpin network
   slicing, but could also be of use in its own right providing enhanced
   connectivity services between customer sites.  This document also
   provides an overview of relevant technologies in different network
   layers, and identifies some areas for potential new work.

Working Group Summary

   The working group had a lot of discussion on terminology and concepts but reached broad consensus on the final version. 

Document Quality

   This is an informational document without protocol implementation. It has undergone multiple reviews including OPSDIR and SECDIR.

Personnel

   The Document Shepherd for this document is Lou Berger. The Responsible
   Area Director is Jim Guichard.

RFC Editor Note