Skip to main content

Path Computation Element Communication Protocol (PCEP) Extensions for Native IP Networks
draft-ietf-pce-pcep-extension-native-ip-40

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>, dd@dhruvdhody.com, draft-ietf-pce-pcep-extension-native-ip@ietf.org, jgs@juniper.net, pce-chairs@ietf.org, pce@ietf.org, rfc-editor@rfc-editor.org
Subject: Document Action: 'Path Computation Element Communication Protocol (PCEP) Extensions for Native IP Networks' to Experimental RFC (draft-ietf-pce-pcep-extension-native-ip-39.txt)

The IESG has approved the following document:
- 'Path Computation Element Communication Protocol (PCEP) Extensions for
   Native IP Networks'
  (draft-ietf-pce-pcep-extension-native-ip-39.txt) as Experimental RFC

This document is the product of the Path Computation Element 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-pce-pcep-extension-native-ip/


Ballot Text

Technical Summary

   This document defines the Path Computation Element Communication
   Protocol (PCEP) extension for Central Control Dynamic Routing (CCDR)
   based applications in Native IP networks.  It describes the key
   information that is transferred between Path Computation Element
   (PCE) and Path Computation Clients (PCC) to accomplish the End-to-End
   (E2E) traffic assurance in the Native IP network under PCE as a
   central controller (PCECC).

Working Group Summary

   It represents a strong concurrence of a few but that is understandable 
   for a specialized document that is applicable for Native-IP only.

   There was a discussion about the document's status. The authors wanted 
   the proposed standard but after discussions with AD/chairs, the track 
   was changed to Experimental.

Document Quality

There is a planned implementation for one vendor as listed in Section 12.

Personnel

   The Document Shepherd for this document is Dhruv Dhody. The Responsible
   Area Director is John Scudder.

RFC Editor Note