[Pce] Fw: Time for a liaison to the ITU

"Adrian Farrel" <adrian@olddog.co.uk> Fri, 09 November 2007 22:32 UTC

Return-path: <pce-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqcPH-0008J9-SD; Fri, 09 Nov 2007 17:32:56 -0500
Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1IqcPG-0008J4-NM for pce-confirm+ok@megatron.ietf.org; Fri, 09 Nov 2007 17:32:54 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqcPG-0008Iv-Cc for pce@ietf.org; Fri, 09 Nov 2007 17:32:54 -0500
Received: from pythagoras.zen.co.uk ([212.23.3.140]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IqcPF-00088Q-Pq for pce@ietf.org; Fri, 09 Nov 2007 17:32:54 -0500
Received: from [88.96.235.142] (helo=aria-networks.com) by pythagoras.zen.co.uk with esmtp (Exim 4.50) id 1IqcPC-00068f-Eo; Fri, 09 Nov 2007 22:32:50 +0000
Received: from your029b8cecfe ([81.140.15.32]) by aria-networks.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 9 Nov 2007 22:31:48 +0000
Message-ID: <10ea01c82320$71970f30$5aa92f40@your029b8cecfe>
From: Adrian Farrel <adrian@olddog.co.uk>
To: pce@ietf.org
Date: Fri, 09 Nov 2007 22:32:09 -0000
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-OriginalArrivalTime: 09 Nov 2007 22:31:48.0965 (UTC) FILETIME=[5147E150:01C82320]
X-Originating-Pythagoras-IP: [88.96.235.142]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: Ross Callon <rcallon@juniper.net>, Scott Bradner <sob@harvard.edu>
Subject: [Pce] Fw: Time for a liaison to the ITU
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Path Computation Element <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@lists.ietf.org?subject=subscribe>
Errors-To: pce-bounces@lists.ietf.org

Hi working group,

In recent months there has been a resurgence of interest in the inter-layer 
characteristics of the ASON architecture defined in the ITU-T. This has 
included discussions in Study Group 15 Questions 12 and 14 about how to 
provide routing in a layered network.

As you may recall, Study Group 15 recently recognized PCE as an option for 
handling their multi-level routing requirements , and published G.7715.2 
describing how a separate path computation component could be used.

So we think that draft-ietf-pce-inter-layer-frwk-05.txt and 
draft-ietf-pce-inter-layer-req-05.txt may be of interest to them and propose 
to send the short liaison below.

Your comments are welcomed.

 Regards,
Adrian and JP

 ===

 To: ITU-T Q12/15 and Q14/15
Cc: Stephen Trowbridge, Kam Lam, Malcolm Betts, Ross Callon, Dave Ward, 
Scott Bradner
Subject: Application of PCE to Inter-Layer Networks
For: Information

 The Path Computation Element (PCE) working group of the IETF is aware that 
your Questions have recently been discussing the inter-layer aspects of the 
ASON architecture and particularly how to select routes across a multi-layer 
network, and how to represent within a higher layer network the potential or 
real connectivity across a lower layer network.

In the light of G.7715.2 we believe that you may be interested in some work 
being discussed in the PCE working group. "Framework for PCE-Based 
Inter-Layer MPLS and GMPLS Traffic Engineering" may be found at 
http://www.ietf.org/internet-drafts/draft-ietf-pce-inter-layer-frwk-05.txt. 
This document should be read in the context of the general PCE architecture 
described in "A Path Computation Element (PCE)-Based Architecture" 
http://www.ietf.org/rfc/rfc4655.txt

Although not specifically targeted at the ASON architecture, we would 
welcome any comments that you have on 
draft-ietf-pce-inter-layer-frwk-05.txt, and invite interested parties to 
contribute either through the liaison process or via the PCE working group 
mailing list details of which can be found at the PCE working group charter 
page http://www.ietf.org/html.charters/pce-charter.html

We are also looking at the requirements driven by inter-layer routing for 
extensions to the PCE Protocol (PCEP) used for communication between Path 
Computation Clients (PCCs) and PCEs. These can be found in "PCC-PCE 
Communication and PCE Discovery Requirements for Inter-Layer Traffic 
Engineering " 
http://www.ietf.org/internet-drafts/draft-ietf-pce-inter-layer-req-05.txt

Best regards,
JP Vasseur and Adrian Farrel
IETF PCE working group co-chairs 




_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce