Re: [secdir] review of draft-ietf-isis-bfd-tlv-02

Sam Hartman <hartmans-ietf@mit.edu> Sun, 25 July 2010 11:18 UTC

Return-Path: <hartmans@mit.edu>
X-Original-To: secdir@core3.amsl.com
Delivered-To: secdir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C91D3A68B3 for <secdir@core3.amsl.com>; Sun, 25 Jul 2010 04:18:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level:
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RC0FstJxoPru for <secdir@core3.amsl.com>; Sun, 25 Jul 2010 04:18:25 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by core3.amsl.com (Postfix) with ESMTP id 055843A682E for <secdir@ietf.org>; Sun, 25 Jul 2010 04:18:24 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (dhcp-23f1.meeting.ietf.org [130.129.35.241]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id B5AE320120; Sun, 25 Jul 2010 07:18:42 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 0640A4133; Sun, 25 Jul 2010 07:18:40 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Stephen Kent <kent@bbn.com>
References: <p06240803c870ffec1816@[10.242.10.151]>
Date: Sun, 25 Jul 2010 07:18:39 -0400
In-Reply-To: <p06240803c870ffec1816@[10.242.10.151]> (Stephen Kent's message of "Sat\, 24 Jul 2010 16\:44\:40 -0400")
Message-ID: <tslsk37ajxs.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: stbryant@cisco.com, ginsberg@cisco.com, chopps@cisco.com, dward@juniper.com, secdir@ietf.org
Subject: Re: [secdir] review of draft-ietf-isis-bfd-tlv-02
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 25 Jul 2010 11:18:26 -0000

>>>>> "Stephen" == Stephen Kent <kent@bbn.com>; writes:

    Stephen> The Security Considerations section is just one paragraph,
    Stephen> which states that the addition of this feature does not
    Stephen> adversely affect the security mechanism (sic) of IS-IS. I'm
    Stephen> not questioning this assertion, based on reading this
    Stephen> document, but I think a couple of additional sentences are
    Stephen> needed here, to justify the assertion.


How about something like: This TLV does not adversely affect the
security of IS-Is. The primary consequence of using the BFD mechanism in
a case where it is not supported is incorrectly detecting a false
failure of bidirectional forwarding.  The primary consequence of not
using BFD when BFD is supported is failure to detect situations in which
bidirectional forwarding is not happening on a link. At worst, this
leads to a denial of service condition. However, a party who can
manipulate the contents of this TLV is already in a position to create
such a denial of service by disrupting IS-IS routing.

If the above paragraph is correct, I think it may go some distance to
addressing Stephen's concern.

However, I wonder how the authentication mechanisms of BFD interact with
the authentication mechanisms of IS-IS? Is it possible to get into a
situation where IS-IS is authenticated but BFD is not?  If so, that
should be discussed in the security considerations section.

--Sam