Re: [secdir] [Last-Call] Secdir last call review of draft-ietf-pce-pcep-extension-for-pce-controller-10
Benjamin Kaduk <kaduk@mit.edu> Thu, 11 February 2021 23:48 UTC
Return-Path: <kaduk@mit.edu>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37D7A3A0E4F for <secdir@ietfa.amsl.com>; Thu, 11 Feb 2021 15:48:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-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 NO4JwT1XI_YE for <secdir@ietfa.amsl.com>; Thu, 11 Feb 2021 15:48:29 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 483403A0E4C for <secdir@ietf.org>; Thu, 11 Feb 2021 15:48:28 -0800 (PST)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 11BNmM4S010933 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 11 Feb 2021 18:48:26 -0500
Date: Thu, 11 Feb 2021 15:48:22 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Cc: secdir@ietf.org
Message-ID: <20210211234822.GL21@kduck.mit.edu>
References: <161264008418.17090.9500210699717988432@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <161264008418.17090.9500210699717988432@ietfa.amsl.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/wLJq8Wypt6j5H-98rxmp8Wnwqkw>
Subject: Re: [secdir] [Last-Call] Secdir last call review of draft-ietf-pce-pcep-extension-for-pce-controller-10
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2021 23:48:31 -0000
Thanks for this review, Yaron! In particular... On Sat, Feb 06, 2021 at 11:34:44AM -0800, Yaron Sheffer via Datatracker wrote: > Reviewer: Yaron Sheffer > Review result: Not Ready > [...] > > - RFC 8283 which defines the architecture that is implemented by this draft > says: > > [The] security implications of SDN have not been fully discussed or described. > Therefore, protocol and applicability work-around solutions for this > architecture must take proper account of these concerns. > > It is expected that each new document that is produced for a specific use case > will also include considerations of the security impacts of the use of a > PCE-based central controller on the network type and services being managed. > > I don't think that the current document addresses this challenge. ... this point is something that I am *very* happy is being raised as soon as possible. Like you, I am not very satisfied with the initial email response (though I did not open up the attached diff), so I hope that we will see more on this front before the document advances to the IESG. Thanks again, Ben > In general, this looks like a very monolithic architecture, where everybody > trusts everybody else once they've been authenticated. Although Sec. 9.1 > discusses the case of a malicious PCE (which would be rather catastrophic), I > would encourage the authors to consider whether a malicious PCC can also > disrupt the PCE's operations and cause "major impact to the network". > > > -- > last-call mailing list > last-call@ietf.org > https://www.ietf.org/mailman/listinfo/last-call
- [secdir] Secdir last call review of draft-ietf-pc… Yaron Sheffer via Datatracker
- Re: [secdir] Secdir last call review of draft-iet… Pengshuping (Peng Shuping)
- Re: [secdir] Secdir last call review of draft-iet… Yaron Sheffer
- Re: [secdir] [Last-Call] Secdir last call review … Benjamin Kaduk