[secdir] secdir review of draft-ietf-pwe3-iccp-13

"Scott G. Kelly" <scott@hyperthought.com> Thu, 13 February 2014 16:53 UTC

Return-Path: <scott@hyperthought.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 4A1EC1A0318 for <secdir@ietfa.amsl.com>; Thu, 13 Feb 2014 08:53:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=unavailable
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id DpIj8gsNafcu for <secdir@ietfa.amsl.com>; Thu, 13 Feb 2014 08:53:51 -0800 (PST)
Received: from smtp66.iad3a.emailsrvr.com (smtp66.iad3a.emailsrvr.com []) by ietfa.amsl.com (Postfix) with ESMTP id 261FC1A0336 for <secdir@ietf.org>; Thu, 13 Feb 2014 08:53:50 -0800 (PST)
Received: from localhost (localhost.localdomain []) by smtp17.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id C1ACA2A04EB; Thu, 13 Feb 2014 11:53:48 -0500 (EST)
X-Virus-Scanned: OK
Received: from app48.wa-webapps.iad3a (relay.iad3a.rsapps.net []) by smtp17.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 1569B2A04F8; Thu, 13 Feb 2014 11:53:33 -0500 (EST)
Received: from hyperthought.com (localhost.localdomain []) by app48.wa-webapps.iad3a (Postfix) with ESMTP id 03332381BBB; Thu, 13 Feb 2014 11:53:33 -0500 (EST)
Received: by apps.rackspace.com (Authenticated sender: scott@hyperthought.com, from: scott@hyperthought.com) with HTTP; Thu, 13 Feb 2014 08:53:33 -0800 (PST)
Date: Thu, 13 Feb 2014 08:53:33 -0800
From: "Scott G. Kelly" <scott@hyperthought.com>
To: "secdir@ietf.org" <secdir@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, draft-ietf-pwe3-iccp.all@tools.ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Importance: Normal
X-Priority: 3 (Normal)
X-Type: plain
Message-ID: <1392310413.011331048@apps.rackspace.com>
X-Mailer: webmail7.0
Subject: [secdir] secdir review of draft-ietf-pwe3-iccp-13
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 13 Feb 2014 16:53:53 -0000

I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG.  These comments were written primarily for the benefit of the security area directors.  Document editors and WG chairs should treat these comments just like any other last call comments.

I'm sorry that this review is a few days late. From the abstract:

   This document specifies an inter-chassis communication protocol
   (ICCP) that enables Provider Edge (PE) device redundancy for Virtual
   Private Wire Service (VPWS) and Virtual Private LAN Service (VPLS)
   applications. The protocol runs within a set of two or more PEs,
   forming a redundancy group, for the purpose of synchronizing data
   amongst the systems. It accommodates multi-chassis attachment circuit
   as well as pseudowire redundancy mechanisms.
So, it's a redundancy protocol between provider edge devices. The document is long (81 pages), and not having been a participant in the wg, I encountered a lot of unfamiliar territory.

The document presents 4 different interconnect scenarios for PEs (provider edge devices), as they are called. The security considerations section says that the security considerations in RFC5036 (LDP) and RFC4447 (Pseudowire Setup and Maintenance Using LDP) apply, and goes on to say that the ICCP protocol (which runs between the PEs) is intended to be restricted to a single administrative domain.

The security considerations section goes on to talk about the need for policy configuration, and recommends that implementations provide control-plane policing to mitigate various attacks.

I have to admit that I only have a limited understanding of this protocol, and this review should be taken accordingly. Zooming up to a 20000` level, I see that there is a group, and that this protocol allows a device to join and participate the group. 

The 4 different interconnect scenarios have different security properties/considerations. The first one (co-located dedicated interconnect) allows assumptions about physical security. The second and fourth have the PEs communicating via shared fabric ("Core Network"). The third has a dedicated interconnect which may allow assumptions about connection security.

So, the questions I think of are these:

- what are the potential consequences of an unauthorized join?

- if any of these are a concern, then how do I prevent unauthorized joins?

- assuming unauthorized joins are prevented, what are the potential consequences of interfering with traffic?

- if any of these are a concern, then how do I detect/prevent these?

In the case relying on physical security and/or a dedicated link (first/third), these can all be addressed by securing the physical link. In the other two cases, we either need protocol mechanisms, or we need assumptions/methods relating to the core network.

Since the security considerations section points at RFCs 5036 and 4447, I went and looked at those. They talk about LDP and MPLS security, but the mechanisms they are using are ip address filtering and MD5 authentication. Under some assumptions for the core network, these may be fine, but under others (e.g. a potentially hostile core network), they are not.

These are the things that occurred to me, as an outside observer who read the draft once.