IETF Logo Mail Archive

Re: [Pce] I-D Action: draft-ietf-pce-stateful-hpce-10.txt

"Adrian Farrel" <adrian@olddog.co.uk> Tue, 18 June 2019 21:03 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 4350012019C for <pce@ietfa.amsl.com>; Tue, 18 Jun 2019 14:03:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 0t-OieCf0Z2X for <pce@ietfa.amsl.com>; Tue, 18 Jun 2019 14:03:25 -0700 (PDT)
Received: from mta8.iomartmail.com (mta8.iomartmail.com [62.128.193.158]) (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 920FC120089 for <pce@ietf.org>; Tue, 18 Jun 2019 14:03:25 -0700 (PDT)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id x5IL3Kmm013815; Tue, 18 Jun 2019 22:03:20 +0100
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 37AEF2204E; Tue, 18 Jun 2019 22:03:20 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs2.iomartmail.com (Postfix) with ESMTPS id 225D02204C; Tue, 18 Jun 2019 22:03:20 +0100 (BST)
Received: from LAPTOPK7AS653V (25.129.51.84.dyn.plus.net [84.51.129.25] (may be forged)) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id x5IL3ImW014450 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 18 Jun 2019 22:03:19 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: daniel@olddog.co.uk, "'BRUNGARD, DEBORAH A'" <db3546@att.com>
Cc: pce@ietf.org
References: <156080870226.22474.8459005932219518482@ietfa.amsl.com> <00b301d52558$6870f280$3952d780$@olddog.co.uk>
In-Reply-To: <00b301d52558$6870f280$3952d780$@olddog.co.uk>
Date: Tue, 18 Jun 2019 22:03:17 +0100
Organization: Old Dog Consulting
Message-ID: <000b01d52619$418809d0$c4981d70$@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: AQG5oAjrbLCEWHE0VKrgEM/efwJ2GQMviNEOpr90ZRA=
Content-Language: en-gb
X-Originating-IP: 84.51.129.25
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-24690.001
X-TM-AS-Result: No--16.913-10.0-31-10
X-imss-scan-details: No--16.913-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24690.001
X-TMASE-Result: 10--16.913300-10.000000
X-TMASE-MatchedRID: ZFzIhWOuIztor4mPA3EMtnFPUrVDm6jt1WwSQLxOvlWuc/Mjt14r212t vsxNXD/lNJkT98oMu7vcixbwa0CYj2MFwILfD7YgJ+mFatzELCNKRaXN2yYjHlhs8uimgHNCqrL pOlGDhqG9g7sDXG03MLcm8EfQO7P0IpKkb60iUL9Q+S0N05fR+yFq4bKNOR/1CMYe+fB56eyPW5 BMg95FVp9NxqRbsrdJpt3L5VFqVttSHosnxqKdcLCa4m727IUPdU2gXPGZpudpsnGGIgWMmUUxx rup1O97qCWODjq9KQN8NIfCaHntLE+DqffUqJJufVRlI+8Oy1kd+GV/0bmoXU9EvF53ySNIHDPv bMPO+Q4Pyq8FufPqH9OzF0V710z471NoDlsmZ4kzxdO2BTO208wx7VbZgGmKzMYDusg1SHABSGj tiD7f+2G+Z4EwKHdwV6PudFmEjPgeWdHNBdxmTYicBKfMHlV8mHAp2UJ8+TwM74Nf6tTB9sGTZR Xft8EsWlXhppSEYxiQEDDnH1cOqo+Xyy5YdK5UngIgpj8eDcC063Wh9WVqgqbyPFGTn+O4XEYHd B0elaV0HSe131POnuJGF26G8SWy5yM0c1ktj9M=
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/_aVZo1LBVRXid7HUYHMzVlr_UpQ>
Subject: Re: [Pce] I-D Action: draft-ietf-pce-stateful-hpce-10.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: Tue, 18 Jun 2019 21:03:28 -0000

Thanks Dan.

Deborah, good to go.

Adrian

-----Original Message-----
From: Pce <pce-bounces@ietf.org> On Behalf Of daniel@olddog.co.uk
Sent: 17 June 2019 23:03
To: pce@ietf.org
Subject: Re: [Pce] I-D Action: draft-ietf-pce-stateful-hpce-10.txt

Hi All, 

This revision of the I-D adjusts the number of document authors, from six to
five. 

BR, Dan. 

-----Original Message-----
From: Pce <pce-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org
Sent: 17 June 2019 22:58
To: i-d-announce@ietf.org
Cc: pce@ietf.org
Subject: [Pce] I-D Action: draft-ietf-pce-stateful-hpce-10.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           : Hierarchical Stateful Path Computation Element
(PCE).
        Authors         : Dhruv Dhody
                          Young Lee
                          Daniele Ceccarelli
                          Jongyoon Shin
                          Daniel King
	Filename        : draft-ietf-pce-stateful-hpce-10.txt
	Pages           : 21
	Date            : 2019-06-17

Abstract:
   A Stateful Path Computation Element (PCE) maintains information on
   the current network state, including: computed Label Switched Path
   (LSPs), reserved resources within the network, and pending path
   computation requests. This information may then be considered when
   computing new traffic engineered LSPs, and for associated and
   dependent LSPs, received from Path Computation Clients (PCCs). The
   Path computation response from a PCE is helpful for the PCC to
   gracefully establish the computed LSP.

   The Hierarchical Path Computation Element (H-PCE) architecture,
   provides an architecture to allow the optimum sequence of
   inter-connected domains to be selected, and network policy to be
   applied if applicable, via the use of a hierarchical relationship
   between PCEs.

   Combining the capabilities of Stateful PCE and the Hierarchical PCE
   would be advantageous. This document describes general considerations
   and use cases for the deployment of Stateful, and not Stateless, PCEs
   using the Hierarchical PCE architecture.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-hpce/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-pce-stateful-hpce-10
https://datatracker.ietf.org/doc/html/draft-ietf-pce-stateful-hpce-10

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-stateful-hpce-10


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

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

v2.23.0 | Report a Bug | By Email