IETF Logo Mail Archive

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

Radia Perlman <radiaperlman@gmail.com> Sun, 19 December 2010 19:55 UTC

Return-Path: <radiaperlman@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 B80D03A68BC; Sun, 19 Dec 2010 11:55:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level:
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 R5k3rvbgX8KR; Sun, 19 Dec 2010 11:55:46 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id BC1293A68BB; Sun, 19 Dec 2010 11:55:46 -0800 (PST)
Received: by iwn40 with SMTP id 40so2694092iwn.31 for <multiple recipients>; Sun, 19 Dec 2010 11:57:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=+ZEGy+OgJCGKXblBvElHIhNYeABHXgHyQKtzAcSN/wY=; b=v6stuT8Ly3jMpBT2FMiF7kbmRKuaPPvxYZh9Nk/WODM6k3wYwWF2nQ+V0bRADcwtlY nNpJXvkXdcfA34cCyE3aGk7hjOg87YX25ncHlZOSl6kSWZttjPg5x5+OZFz+HeTc80I9 jTG/NbXonfvLnAkTLy4THOGc3gs0EWQfz3ed4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=fByNJUOWRewKtgwFPFrORnNvtFI25kC1z/7tJK3FdYn4+RuykrL7U+oR+tBguPayPa c1e4Ld0WgYdyRUe1XHTHj2cAkil/N2puOnQ61V+wpUJ5AoRXP2j8ucB+6RnkwIJa7iuI XdPiyDdnsSPre6/XmgmzPRJApM2IvHjDqU+s0=
MIME-Version: 1.0
Received: by 10.42.175.70 with SMTP id az6mr3284518icb.428.1292788658545; Sun, 19 Dec 2010 11:57:38 -0800 (PST)
Received: by 10.42.220.199 with HTTP; Sun, 19 Dec 2010 11:57:38 -0800 (PST)
In-Reply-To: <AANLkTim-RGc1mnaVVjLP=8Y_7OV+tmT=OTXUmZ6q=Ddm@mail.gmail.com>
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>
Date: Sun, 19 Dec 2010 11:57:38 -0800
Message-ID: <AANLkTi=LMZB8HTRXXEd+gKx+haAvn_vywkF6PUzVsr=p@mail.gmail.com>
From: Radia Perlman <radiaperlman@gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: Erik Nordmark <nordmark@acm.org>, secdir@ietf.org, Sam Hartman <hartmans-ietf@mit.edu>, 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: Sun, 19 Dec 2010 19:55:47 -0000

No objections.

Radia

On Sun, Dec 19, 2010 at 10:16 AM, Donald Eastlake <d3e3e3@gmail.com> wrote:
> My apologies for responding slowly, I was traveling.
>
> If it is tolerable to people, I do not mind adding the two sentences
> requested by Sam to the isis-trill draft.
>
> Thanks,
> Donald
>
> PS: It appears to me that the same considerations apply to
> draft-ietf-isis-ieee-aq.
>
> On Fri, Dec 17, 2010 at 10:45 PM, Sam Hartman <hartmans-ietf@mit.edu> wrote:
>>>>>>> "Erik" == Erik Nordmark <nordmark@acm.org> writes:
>>
>>
>>    Erik> Adding just this sentence to draft-ietf-isis-trill (the code
>>    Erik> point document) seems odd. Your comment is really a comment on
>>    Erik> the security of IS-IS, and not specific to TRILL and unrelated
>>    Erik> to the code points.
>>
>> I don't care much where the text goes.  I'm happy if you provide an rfc
>> editor note for draft-ietf-trill-rbridge-protocol if you like that
>> approach better.  However, as I read draft-ietf-isis-trill, it defines
>> the interface between TRILL and IS-IS.  In my mind, that's where the
>> security consideration appears.  You're re-using a component that isn't
>> up to our current standards--we know that; we're working on it in
>> KARP. However in doing that, you need to document the security
>> considerations for your protocol.  Since you have a document that
>> specifically is the interface between your protocol and the component
>> you are re-using,that seems like the best place to do the documentation
>> work.
>>
>> however, in decreasing order of priority, I want to call out my concern
>> that we need to be far more careful about what we expect in terms of
>> security from future work we charter and that we should document the
>> specific interactions between IS-IS and TRILL.  While I have expressed
>> an opinion above on where I think that documentation should go, feel
>> free to put it where you think is most correct.
> _______________________________________________
> secdir mailing list
> secdir@ietf.org
> https://www.ietf.org/mailman/listinfo/secdir
>

v2.26.15 | Report a Bug | By Email | System Status