Hi, Young and authors,
Thank you for putting forward such a draft. This reminds me to check if
draft-ietf-pce-questions touches upon this issue and I find the following
description (in Section 3):
＂
It has also been proposed that the PCE Communication Protocol (PCEP)
[RFC5440] could be extended to serve as an information collection
protocol to supply information from network devices to a PCE. The
logic is that the network devices may already speak PCEP and so the
protocol could easily be used to report details about the resources
and state in the network, including the LSP state discussed in
Sections 14 and 15.
＂
So, indeed this draft discusses something interesting. Would be good to hear
how other PCErs think about this.
BTW, by browsing through the content, it seems that there are no extensions
included so far. Since the document type is standard track, I wonder if the
intention is to include PCEP extensions in the future or the draft actually
meant to be informational only?
Regards,
Xian
-----Original Message-----
From: Pce [mailto:[email protected]] On Behalf Of Leeyoung
Sent: 2014年7月3日 5:51
To: [email protected]
Cc: Greg Bernstein; Zhenghaomian
Subject: [Pce] FW: New Version Notification for
draft-lee-pce-transporting-te-data-00.txt
Hi,
We have just published a new PCE draft concerning alternative ways of
transporting TE data that may not depend on IGP-TE or BGP-LS.
The motivation for this work is a timely update of TE data directly from nodes
to PCE(s) to support scenarios like:
(i) networks that do not support IGP-TE or BGP-LS but want to implement PCE.
(ii) applications that require accurate and timely TE data that current
convergence time associated with flooding is not justified.
(iii) reduction of node OH processing of flooding mechanisms (esp. optical
transport networks where there are large amounts of traffic data and
constraints due to OTN/WSON/Flexi-grid, etc. Note that also BGP-LS is not
supported in optical transport networks today)
Your comment will always be appreciated.
Thanks,
Young (on behalf of other co-authors)
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Wednesday, July 02, 2014 4:32 PM
To: Greg Bernstein; Dhruv Dhody; Greg Bernstein; Zhenghaomian; Dhruv Dhody;
Leeyoung; Leeyoung; Zhenghaomian
Subject: New Version Notification for draft-lee-pce-transporting-te-data-00.txt
A new version of I-D, draft-lee-pce-transporting-te-data-00.txt
has been successfully submitted by Young Lee and posted to the IETF repository.
Name: draft-lee-pce-transporting-te-data
Revision: 00
Title: PCEP Extensions in Support of Transporting Traffic Engineering
Data
Document date: 2014-07-02
Group: Individual Submission
Pages: 20
URL:
http://www.ietf.org/internet-drafts/draft-lee-pce-transporting-te-data-00.txt
Status:
https://datatracker.ietf.org/doc/draft-lee-pce-transporting-te-data/
Htmlized: http://tools.ietf.org/html/draft-lee-pce-transporting-te-data-00
Abstract:
In order to compute and provide optimal paths, Path Computation
Elements (PCEs) require an accurate and timely Traffic Engineering
Database (TED). Traditionally this TED has been obtained from a link
state routing protocol supporting traffic engineering extensions.
This document discusses possible alternatives to TED creation. This
document gives architectural alternatives for these enhancements and
their potential impacts on network nodes, routing protocols, and
PCE.
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
_______________________________________________
Pce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/pce
_______________________________________________
Pce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/pce
