Re: [Pce] Updates RE: I-D Action: draft-ietf-pce-hierarchy-extensions-09.txt

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 06 February 2019 19:50 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 9A855130F29 for <pce@ietfa.amsl.com>; Wed, 6 Feb 2019 11:50:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 XVOFEHbcpR3N for <pce@ietfa.amsl.com>; Wed, 6 Feb 2019 11:50:29 -0800 (PST)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (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 92C39130E9A for <pce@ietf.org>; Wed, 6 Feb 2019 11:50:28 -0800 (PST)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta7.iomartmail.com (8.14.4/8.14.4) with ESMTP id x16JoQmC014558; Wed, 6 Feb 2019 19:50:26 GMT
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id E9DA02203D; Wed, 6 Feb 2019 19:50:25 +0000 (GMT)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs3.iomartmail.com (Postfix) with ESMTPS id D3C732203C; Wed, 6 Feb 2019 19:50:25 +0000 (GMT)
Received: from LAPTOPK7AS653V ([87.112.189.92]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id x16JoOw4004708 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 6 Feb 2019 19:50:25 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: daniel@olddog.co.uk, pce@ietf.org
References: <002301d4be4b$6be4d310$43ae7930$@olddog.co.uk>
In-Reply-To: <002301d4be4b$6be4d310$43ae7930$@olddog.co.uk>
Date: Wed, 06 Feb 2019 19:50:24 -0000
Organization: Old Dog Consulting
Message-ID: <022f01d4be55$34158470$9c408d50$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AQEzHcruDv6CIMcAT5TQCWYU/nckwKcWbTsg
X-Originating-IP: 87.112.189.92
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-24414.002
X-TM-AS-Result: No--15.895-10.0-31-10
X-imss-scan-details: No--15.895-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24414.002
X-TMASE-Result: 10--15.894800-10.000000
X-TMASE-MatchedRID: TmlY9+XBoTnxIbpQ8BhdbOYAh37ZsBDC9mnDjfUPq55n5cZ5y8SBOsHc NLntsxmN1di5kB0M8FanayRux2acwjmkvVO2eNn+zNY33yIEF4bs8rI+Arq54bV5fSMRD1zqv3I 3EnO7EZx6pO9c4J2+KqFydf3AIiqZL0W1btd8e56mput5KKcJ0zoSfZud5+GgSO2IbIklM8xptM 6nEjcyPqfzZVr02jANfb1p2EyLnCD9+rKlRf1WaMNrWpY804TGMVx/3ZYby79rE1c4mB5UmtGuw 4Lwp4hl48CHU6S1ISHOCRsgJ4DzkYWDz7mPxd0pWGVA57gn78c9sp6v4GhlP4zZ6FNX6KaLKSyM l4Bp7a5yjB8rtLiqOJ6AzGUG6rEJhdUss4Ved7O1PiMh4ZF39UCrr/LkAQ46PILl10bYlyBncpG Qs7S9GTRzIRIo4G/0Bc5l05FO6qtEXwnTCGfm3dwM5s/IbFmyUVruDsLy3YSbKItl61J/ycnjLT A/UDoAnL8I93Xanoma0k2he5NwuCs3zPQeiEbe+gtHj7OwNO2FR9Hau8GO7gP90fJP9eHt
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/nHgH5YcX2wRtwXRiL6ykeI_6BcE>
Subject: Re: [Pce] Updates RE: I-D Action: draft-ietf-pce-hierarchy-extensions-09.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, 06 Feb 2019 19:50:37 -0000

Thanks Dan/co-authors,

This revision addressed my concerns.

I told Dhruv, and he seems to have pushed the draft forward.

Cheers,
Adrian

-----Original Message-----
From: Pce <pce-bounces@ietf.org> On Behalf Of daniel@olddog.co.uk
Sent: 06 February 2019 18:40
To: pce@ietf.org
Subject: [Pce] Updates RE: I-D Action:
draft-ietf-pce-hierarchy-extensions-09.txt

Dear PCE'rs, 

Happy Chinese New Year! 

Please find attached an update to draft-ietf-pce-hierarchy-extensions
addressing a few important comments from Adrian. Updates to the I-D include:

- Additional clarifying text for Parent PCE Capability Advertisement
- New sub-section highlighting applicability of procedures and encodings in
the I-D to PCC-PCE Communications
- Further discussion of the Backwards Compatibility behavior
- Reintroducing an appendix that provides details on implementations, this
section will be removed before publication
- Addressing various grammar NITs

BR, Dan (and the co-authors)

-----Original Message-----
From: I-D-Announce <i-d-announce-bounces@ietf.org> On Behalf Of
internet-drafts@ietf.org
Sent: 06 February 2019 17:18
To: i-d-announce@ietf.org
Cc: pce@ietf.org
Subject: I-D Action: draft-ietf-pce-hierarchy-extensions-09.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           : Extensions to Path Computation Element
Communication Protocol (PCEP) for Hierarchical Path Computation Elements
(PCE)
        Authors         : Fatai Zhang
                          Quintin Zhao
                          Oscar Gonzalez de Dios
                          R. Casellas
                          Daniel King
	Filename        : draft-ietf-pce-hierarchy-extensions-09.txt
	Pages           : 31
	Date            : 2019-02-06

Abstract:
   The Hierarchical Path Computation Element (H-PCE) architecture is
   defined in RFC 6805.  It provides a mechanism to derive an optimum
   end-to-end path in a multi-domain environment by using a hierarchical
   relationship between domains to select the optimum sequence of
   domains and optimum paths across those domains.

   This document defines extensions to the Path Computation Element
   Protocol (PCEP) to support Hierarchical PCE procedures.



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

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-pce-hierarchy-extensions-09
https://datatracker.ietf.org/doc/html/draft-ietf-pce-hierarchy-extensions-09

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-hierarchy-extensions-09


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/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html or
ftp://ftp.ietf.org/ietf/1shadow-sites.txt

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