[Pce] Benjamin Kaduk's No Objection on draft-ietf-pce-stateful-hpce-14: (with COMMENT)

Benjamin Kaduk via Datatracker <noreply@ietf.org> Sat, 19 October 2019 04:02 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 219D2120052; Fri, 18 Oct 2019 21:02:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-pce-stateful-hpce@ietf.org, Adrian Farrel <adrian@olddog.co.uk>, pce-chairs@ietf.org, adrian@olddog.co.uk, pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.106.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <157145777112.3841.5924102348121639921.idtracker@ietfa.amsl.com>
Date: Fri, 18 Oct 2019 21:02:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/aCkyEfFCj5GaozYiZwY_pqEQevw>
Subject: [Pce] Benjamin Kaduk's No Objection on draft-ietf-pce-stateful-hpce-14: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 19 Oct 2019 04:02:52 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-pce-stateful-hpce-14: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-hpce/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for addressing my Discuss point!

I would consider including the conclusion from our discussion about what
would happen if a PCEP speaker does not support stateful H-PCE but the peer
assumes it does, perhaps in an operational considerations section, but this does
not rise to a Discuss-level point.  For convenience, this was discussed as:

% I further did a mental exercise for PCC -> C-PCE -> P-PCE and assumed
% all support stateful and H-PCE extension but what happens when any
% PCEP speaker does not support stateful H-PCE but the peer assumes that
% it does. On further PCEP message exchange, the messages may not get
% further propagated and thus at worse would not lead to the stateful
% H-PCE based 'parent' control of the LSP. This is something any peer
% should be prepared for anyways.