IETF Logo Mail Archive

Re: [Pce] I-D Action: draft-ietf-pce-pcep-extension-for-pce-controller-07.txt

Adrian Farrel <adrian@olddog.co.uk> Wed, 02 September 2020 15:11 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF1F23A0B15 for <pce@ietfa.amsl.com>; Wed, 2 Sep 2020 08:11:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aEBp6HZeVf4R for <pce@ietfa.amsl.com>; Wed, 2 Sep 2020 08:11:14 -0700 (PDT)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 005743A0DED for <pce@ietf.org>; Wed, 2 Sep 2020 08:11:13 -0700 (PDT)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta6.iomartmail.com (8.14.4/8.14.4) with ESMTP id 082FBBon010282 for <pce@ietf.org>; Wed, 2 Sep 2020 16:11:11 +0100
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id E47E72203D for <pce@ietf.org>; Wed, 2 Sep 2020 16:11:10 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs1.iomartmail.com (Postfix) with ESMTPS id CFC8C2203A for <pce@ietf.org>; Wed, 2 Sep 2020 16:11:10 +0100 (BST)
Received: from LAPTOPK7AS653V ([84.93.102.82]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id 082FB9Pq021382 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <pce@ietf.org>; Wed, 2 Sep 2020 16:11:10 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: pce@ietf.org
References: <159901420163.20335.5164743044438591499@ietfa.amsl.com>
In-Reply-To: <159901420163.20335.5164743044438591499@ietfa.amsl.com>
Date: Wed, 02 Sep 2020 16:11:09 +0100
Organization: Old Dog Consulting
Message-ID: <01fe01d6813b$4ab3cfc0$e01b6f40$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJHneM3TbY5A4Qe9wdu4FQ7qEWLx6hzOciw
Content-Language: en-gb
X-Originating-IP: 84.93.102.82
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-25640.005
X-TM-AS-Result: No--21.813-10.0-31-10
X-imss-scan-details: No--21.813-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25640.005
X-TMASE-Result: 10--21.812700-10.000000
X-TMASE-MatchedRID: oCj5caaCQylor4mPA3EMtnFPUrVDm6jttb3wUEoASahPvOpmjDN2klVa zIZBiETD9HKQnl/CQstfMrorr76P9vOb/ssg0phATh4VSQfkIVwYOnQDwWp0xC62hjZS0WoY6Zh ZJfDWK5/Bz9YdtuEgTG53M7Tz7E6rrZPIorUNC92cxB01DrjF91F5adRR2Ej1neWzvt1s9ohbaD avYsjybbciZK6fRJYTe9jndC0U8UlMG/zUuTYivU7yqWc5cVLPzxauQOoKfWugDWpkqTKvoWgbs S7BAlaWxEzxH1OhRhJCGD9jIcc0V+g1Yi0AsApPbWgRGvgWOREKF0jiwuWuOAv1OPvvDLzslwV4 oAe+9zbM+bAACwR/n6sbL17QvabEPy1vOUgRZKJ0+657dxGJGKm9/6ObPjnDC22/l58BLy4y5PB tqoQlk4T+IirX4K90TY524cbCSAVyuwcaughq/RT656LDV3kUlhpPdwv1Z0qTU3CLdU2O7z7FnC rEJ7NNKGASuvDJuD1UAbEDylQzMfWUZFWpEklt4h8r8l3l4eb+NefZIdSZXNE4PeXguBzl6uIqc KPp5BPm2Ag8sBtZ9hVCpTodm0dLfDDFL+oKuV48FYXQ7T7bc7kjcmSnmog+pjtcfbwefVGjxYyR Ba/qJX3mXSdV7KK4uPItwmogb15TptoDfp6JrMRB0bsfrpPIqxB32o9eGclVaBFytIQUtw==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/iZxXf9acT0jIOkLLNroQ9tczqoo>
Subject: Re: [Pce] I-D Action: draft-ietf-pce-pcep-extension-for-pce-controller-07.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Sep 2020 15:11:16 -0000

Just to repeat what I said when Shuping proposed the changes...
This revision addresses all the points in my review.
Cheers,
Adrian

-----Original Message-----
From: Pce <pce-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org
Sent: 02 September 2020 03:37
To: i-d-announce@ietf.org
Cc: pce@ietf.org
Subject: [Pce] I-D Action:
draft-ietf-pce-pcep-extension-for-pce-controller-07.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Path Computation Element WG of the IETF.

        Title           : PCEP Procedures and Protocol Extensions for Using
PCE as a Central Controller (PCECC) of LSPs
        Authors         : Zhenbin Li
                          Shuping Peng
                          Mahendra Singh Negi
                          Quintin Zhao
                          Chao Zhou
	Filename        :
draft-ietf-pce-pcep-extension-for-pce-controller-07.txt
	Pages           : 35
	Date            : 2020-09-01

Abstract:
   The Path Computation Element (PCE) is a core component of Software-
   Defined Networking (SDN) systems.  It can compute optimal paths for
   traffic across a network and can also update the paths to reflect
   changes in the network or traffic demands.

   PCE was developed to derive paths for MPLS Label Switched Paths
   (LSPs), which are supplied to the head end of the LSP using the Path
   Computation Element Communication Protocol (PCEP).  But SDN has a
   broader applicability than signaled MPLS and GMPLS traffic-engineered
   (TE) networks, and the PCE may be used to determine paths in a range
   of use cases.  PCEP has been proposed as a control protocol for use
   in these environments to allow the PCE to be fully enabled as a
   central controller.

   A PCE-based central controller (PCECC) can simplify the processing of
   a distributed control plane by blending it with elements of SDN and
   without necessarily completely replacing it.  Thus, the LSP can be
   calculated/setup/initiated and the label forwarding entries can also
   be downloaded through a centralized PCE server to each network
   devices along the path while leveraging the existing PCE technologies
   as much as possible.

   This document specifies the procedures and PCEP extensions for using
   the PCE as the central controller.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-extension-for-pce-contr
oller/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-pce-pcep-extension-for-pce-controller
-07
https://datatracker.ietf.org/doc/html/draft-ietf-pce-pcep-extension-for-pce-
controller-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-pcep-extension-for-pce-cont
roller-07


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


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

v2.23.0 | Report a Bug | By Email