[secdir] draft-ietf-pce-flexible-grid-16 ietf last call Secdir review

Yoav Nir via Datatracker <noreply@ietf.org> Sat, 29 August 2026 19:32 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: secdir@ietf.org
Delivered-To: secdir@mail2.ietf.org
Received: from [10.244.9.115] (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 57F5A13194739; Sat, 29 Aug 2026 12:32:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1788031933; bh=HK85IR3pyLKnwS/1Xgh/tv85Y6JBuQEZ4Z+tUUwPrQs=; h=From:To:Cc:Subject:Reply-To:Date; b=ND99P4ht7Ax7176LEqQ0YRHPeOHe83lcxwfDOJoFmuyNqFd3C2BdvY/YmjnEm40Wa zjzJVfD2KNcSSVDtCawnNGwS8yyDkekNFjR2zo4hkQZBYUiEZAy+fp18t3sns1v/A9 xemNSlTpBTpIptdB7reYemT/lgLAZ8FoFI9mcz9Q=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Yoav Nir via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.73.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <178803193320.130837.2060982551659975574@dt-datatracker-6669c7b496-4m6kd>
Date: Sat, 29 Aug 2026 12:32:13 -0700
Message-ID-Hash: YWLYKX6JGJP65EJE76ZISAZBI5EBOHMQ
X-Message-ID-Hash: YWLYKX6JGJP65EJE76ZISAZBI5EBOHMQ
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-secdir.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-pce-flexible-grid.all@ietf.org, last-call@ietf.org, pce@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Yoav Nir <ynir.ietf@gmail.com>
Subject: [secdir] draft-ietf-pce-flexible-grid-16 ietf last call Secdir review
List-Id: Security Area Directorate <secdir.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/9HA4MFHnv1ZdYENPmBMIWYpUNI8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Owner: <mailto:secdir-owner@ietf.org>
List-Post: <mailto:secdir@ietf.org>
List-Subscribe: <mailto:secdir-join@ietf.org>
List-Unsubscribe: <mailto:secdir-leave@ietf.org>

Document: draft-ietf-pce-flexible-grid
Title: PCEP Extension for Flexible Grid Networks
Reviewer: Yoav Nir
Review result: Has Nits

This review is limited by my lack of knowledge about PCEP.

I'll start with a Gen-Art comment, that the document references RFC 8253 (TLS
for PCEP), but that document has been updated by RFC 9916 (using TLS 1.3 for
PCEP), so this document should reference that as well. In any case, TLS is only
mentioned once, in the security considerations section.

The Security Considerations section is quite short, and mostly by-reference,
stating that it "has no requirement for a change to the security models within
PCEP" and that "the security considerations described in [RFC5440] and the use
of TLS to provide a secure transport for PCEP as described in [RFC8253] apply
to the extensions defined in this document". Fair enough, but RFC 5440 (PCEP)
is from 2009, and contains such advice as that "TCP-MD5 [RFC2385] is the only
available security mechanism for securing the TCP connections", and nowhere in
this document is the use of TLS mandated.

The Security Considerations section goes on to say that the "additional
information distributed in order to address the RSA problem represents a
disclosure of network capabilities that an operator might wish to keep private.
Operators are encouraged to secure this information"  I don't know what
"encouraged" means here. Either the information in this extension is more
sensitive than general PCEP information, and TLS is a MUST or a SHOULD, or it's
similar to other information, and so using TLS remains optional. I think the
document (though probably not the Security Considerations section) should say
one way or the other. Nowhere else in the document is security, privacy, or
disclosure mentioned.