[secdir] Secdir telechat review of draft-ietf-ospf-link-overload-11

Sean Turner <sean@sn3rd.com> Fri, 05 January 2018 01:44 UTC

Return-Path: <sean@sn3rd.com>
X-Original-To: secdir@ietf.org
Delivered-To: secdir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D256127863; Thu, 4 Jan 2018 17:44:40 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Sean Turner <sean@sn3rd.com>
To: secdir@ietf.org
Cc: ospf@ietf.org, ietf@ietf.org, draft-ietf-ospf-link-overload.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.68.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151511668059.14718.13596043175355413910@ietfa.amsl.com>
Date: Thu, 04 Jan 2018 17:44:40 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/5OLqT2EYCeBm1UPEe9pG6hr2C9s>
Subject: [secdir] Secdir telechat review of draft-ietf-ospf-link-overload-11
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 05 Jan 2018 01:44:41 -0000

Reviewer: Sean Turner
Review result: Ready

In reviewing this draft, I was most concerned that this mechanism could be used
by an attacker to push traffic towards or away from a node.  If the messages
are authenticated then I tend to agree with your assessment that this draft
doesn't introduce any new security considerations beyond those in
[RFC2328]/[RFC5340].  If not, well all bets are off.

I did note a couple of editorial nits, but I sent those directly to the authors.