[secdir] Secdir review of draft-ietf-trill-loss-delay-05

"Joseph Salowey (jsalowey)" <jsalowey@cisco.com> Mon, 04 August 2014 02:51 UTC

Return-Path: <jsalowey@cisco.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCF071B281E; Sun, 3 Aug 2014 19:51:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cDhgDo5CCXUK; Sun, 3 Aug 2014 19:51:24 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FA291B281C; Sun, 3 Aug 2014 19:51:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=498; q=dns/txt; s=iport; t=1407120684; x=1408330284; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=4yH2we5nCDXBEVWEoWoHNl1AwrvpptYt33fqjvBj028=; b=FHiGfx3Ax+S5Y351Fcef8/PQgXh+V54sbAivJ3uYx0poP+Z/GQDDM9jg 0abAz0dp3x+YH5YihJXQV2Ua0xKQiiIEbW8qJyzPXDXL9D649YkIgLsBc qu+XiMUfW1wyT2/03gBRdDcfmj/HLPwxBzp/dJJa3dOpjz+nb90b/U2m4 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAOX03lOtJA2J/2dsb2JhbABbgw2BLdR6FneECjpRAT5CJwQBiFTFeheTAoEcBZwGlF+DTYIy
X-IronPort-AV: E=Sophos;i="5.01,795,1400025600"; d="scan'208";a="344842416"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-3.cisco.com with ESMTP; 04 Aug 2014 02:51:20 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s742pKTV021681 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 4 Aug 2014 02:51:20 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.143]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0123.003; Sun, 3 Aug 2014 21:51:20 -0500
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "<secdir@ietf.org>" <secdir@ietf.org>, IESG <iesg@ietf.org>, "draft-ietf-trill-loss-delay-05.all@tools.ietf.org" <draft-ietf-trill-loss-delay-05.all@tools.ietf.org>
Thread-Topic: Secdir review of draft-ietf-trill-loss-delay-05
Thread-Index: AQHPr474bgzZWUCee0itdMp1CjayKw==
Date: Mon, 4 Aug 2014 02:51:19 +0000
Message-ID: <729629AB-CA13-4B00-82AF-8392A5D6454F@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.33.248.134]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9B2CDDB2DBAEEE49AE0A2C08240877F4@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/secdir/D5VIvEjCxU-b6_125cLuK0EC1W8
Subject: [secdir] Secdir review of draft-ietf-trill-loss-delay-05
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: Mon, 04 Aug 2014 02:51:26 -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.

The document is ready. 

The document has a security considerations section that covers the issues that I can think of.  

Cheers,

Joe