Skip to main content

Path Computation Element Communication Protocol (PCEP) Extensions for Establishing Relationships between Sets of Label Switched Paths and Virtual Networks
draft-ietf-pce-vn-association-11

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-pce-vn-association@ietf.org, hari@netflix.com, jgs@juniper.net, pce-chairs@ietf.org, pce@ietf.org, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Path Computation Element Communication Protocol (PCEP) extensions for establishing relationships between sets of Label Switched Paths and Virtual Networks' to Proposed Standard (draft-ietf-pce-vn-association-11.txt)

The IESG has approved the following document:
- 'Path Computation Element Communication Protocol (PCEP) extensions for
   establishing relationships between sets of Label Switched Paths and
   Virtual Networks'
  (draft-ietf-pce-vn-association-11.txt) as Proposed Standard

This document is the product of the Path Computation Element Working Group.

The IESG contact persons are Alvaro Retana, Andrew Alston and John Scudder.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-vn-association/


Ballot Text

Technical Summary

   This document describes how to extend the Path Computation Element
   (PCE) Communication Protocol (PCEP) association mechanism introduced
   by the PCEP Association Group specification, to further associate
   sets of Label Switched Paths (LSPs) with a higher-level structure
   such as a Virtual Network (VN) requested by a customer or
   application.  This extended association mechanism can be used to
   facilitate control of virtual network using the PCE architecture.

Working Group Summary

   We have broad agreement for this working group document.

Document Quality

   Existing implementation specified in the document.

   Currently all strings in PCEP are ASCII instead of BCP 18, BCP 166. This was
   discussed briefly in the WG. The authors decided to keep ASCII with the idea
   that all string processing would be better to be handled together.

Personnel

   Document Shepherd: Hariharan Ananthakrishnan  
   Responsible Area Director: John Scudder

RFC Editor Note