Re: [secdir] Review of draft-ietf-nsis-ext-06

Elwyn Davies <elwynd@folly.org.uk> Sat, 20 March 2010 15:33 UTC

Return-Path: <elwynd@folly.org.uk>
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 6F9853A6AAA; Sat, 20 Mar 2010 08:33:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.469
X-Spam-Level:
X-Spam-Status: No, score=-1.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 WhGLeOxWJ2f6; Sat, 20 Mar 2010 08:33:50 -0700 (PDT)
Received: from b.painless.aaisp.net.uk (b.painless.aaisp.net.uk [IPv6:2001:8b0:0:30::51bb:1e34]) by core3.amsl.com (Postfix) with ESMTP id 88D2E3A6A7A; Sat, 20 Mar 2010 08:33:47 -0700 (PDT)
Received: from 153.107.2.81.in-addr.arpa ([81.2.107.153] helo=[81.187.254.247]) by b.painless.aaisp.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <elwynd@folly.org.uk>) id 1Nt0gT-0004VN-KM; Sat, 20 Mar 2010 15:33:53 +0000
Message-ID: <4BA4EB7D.3080702@folly.org.uk>
Date: Sat, 20 Mar 2010 15:36:29 +0000
From: Elwyn Davies <elwynd@folly.org.uk>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Shawn M Emery <shawn.emery@sun.com>
References: <4BA48592.8040804@sun.com>
In-Reply-To: <4BA48592.8040804@sun.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sat, 20 Mar 2010 09:35:05 -0700
Cc: draft-ietf-nsis-ext.all@tools.ietf.org, iesg@ietf.org, secdir@ietf.org
Subject: Re: [secdir] Review of draft-ietf-nsis-ext-06
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: elwynd@folly.org.uk
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: Sat, 20 Mar 2010 15:33:51 -0000

Thanks for the review.

The suggestion about RFC 4081 is well taken.

I will take the editorials under advisement!

Regards,
Elwyn

Shawn M Emery wrote:
>
> 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.
>
> This draft describes is an informational document that provides an
> overview of the Next Steps in Signaling (NSIS) set of protocols, how
> to deploy said protocols, and how to extend the set of NSIS protocols.
>
> The security considerations section does exist and gives guidance for
> any extensions to the NSIS protocol set.  It then talks about using
> authentication, integrity checks, and authorization for any NSIS
> supported routers.
>
> The section continues guidance for extensions by making sure they
> leverage NSIS' lower layer transport authentication and that any new
> transport protocols created support NSIS' low layer authentication and
> integrity check capabilities.
>
> I think this section should include a reference to RFC 4081 for the
> possible attack scenarios for NSIS when considering an extension to
> the NSIS protocol set.
>
> General comments:
>
> None.
>
> Editorial comments:
>
> 3. The General Internet Signaling Transport
>
> s/in future/in the future/
>
>
> 8. Extending the Protocols
>
> s/identified in future/identified in the future/
>