IETF Logo Mail Archive

Re: [secdir] Secdir review of draft-ietf-isis-trill

Donald Eastlake <d3e3e3@gmail.com> Mon, 20 December 2010 18:41 UTC

Return-Path: <d3e3e3@gmail.com>
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 C14333A69B2; Mon, 20 Dec 2010 10:41:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.175
X-Spam-Level:
X-Spam-Status: No, score=-103.175 tagged_above=-999 required=5 tests=[AWL=0.424, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 7zs0+CgOe9iL; Mon, 20 Dec 2010 10:41:31 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 8D2983A6866; Mon, 20 Dec 2010 10:41:30 -0800 (PST)
Received: by wyf23 with SMTP id 23so3149111wyf.31 for <multiple recipients>; Mon, 20 Dec 2010 10:43:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=YDpZMdDPYeB74CedfD5uWe6qtrlgeCd0QrW6oQnHFE8=; b=jCIoEIAzW/R86DYQZXTzNvctGdwPPq03SW2l6d+hvtNSm65A/XDGircKWExpefkYPS EO3ykgkvqbq45xMPQ6B8mkgihkU0ZjY1PON4ewrqKVnf16xH7fLNaqfVLr5KButgIcfK ji4i8HjshxIAHueyGTWCFh4y3YJhUVUlKbXuU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=vvahxom6GKCw6nqAi1RQ/Js9xYBjibNA5qA1eAzUbNeV0pehrijitZMzegPxh1ndQ4 ctEP0zB4EfR0STtgEFm/kS6DDhyUbl9eN4WAEqQmtff/PJasYwn0CUNwSyIwkHcwNftt 58tKClrTc74TlhCx5j4Ga9uTmQ6uxyzGflF3E=
Received: by 10.227.183.71 with SMTP id cf7mr2877594wbb.195.1292870604020; Mon, 20 Dec 2010 10:43:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.143.196 with HTTP; Mon, 20 Dec 2010 10:43:03 -0800 (PST)
In-Reply-To: <tsltyi8xuo7.fsf@mit.edu>
References: <tslipywbakv.fsf@mit.edu> <tsl4oac15m0.fsf@mit.edu> <4D0BDDC0.6060201@acm.org> <tsl7hf7zqtp.fsf@mit.edu> <AANLkTim-RGc1mnaVVjLP=8Y_7OV+tmT=OTXUmZ6q=Ddm@mail.gmail.com> <AANLkTi=LMZB8HTRXXEd+gKx+haAvn_vywkF6PUzVsr=p@mail.gmail.com> <tsltyi8xuo7.fsf@mit.edu>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 20 Dec 2010 13:43:03 -0500
Message-ID: <AANLkTi=ES=zgq3e0mGN7er4guZ4czaLWxcjRDOEapzuv@mail.gmail.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: Erik Nordmark <nordmark@acm.org>, secdir@ietf.org, draft-ietf-isis-trill@tools.ietf.org, ietf@ietf.org
Subject: Re: [secdir] Secdir review of draft-ietf-isis-trill
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: Mon, 20 Dec 2010 18:41:31 -0000

Hi,

On Mon, Dec 20, 2010 at 11:42 AM, Sam Hartman <hartmans-ietf@mit.edu> wrote:
>>>>>> "Radia" == Radia Perlman <radiaperlman@gmail.com> writes:
>
>    Radia> No objections.  Radia
>
>
> Can I get someone to confirm that the text in the proposed sentences is
> substantially true?
> I think so but I'm not an IS-IS expert.

LSPs have sequences number, etc., and are idempotent. I think only
Hellos have the potential replay Denial of Service problem. So I would
suggest changing to:

"Even when the IS-IS
authentication is used, replays of Hello packets can create
denial-of-service conditaions; see RFC 6039 for details. These issues
are similar in scope to those discussed in section 6.2 of
draft-ietf-trill-rbridge-protocol, and the same mitigations may apply."

Thanks,
Donald

v2.23.0 | Report a Bug | By Email