Re: [secdir] secdir review of draft-ietf-netconf-monitoring

"Bert Wijnen \(IETF\)" <bertietf@bwijnen.net> Fri, 11 June 2010 14:59 UTC

Return-Path: <bertietf@bwijnen.net>
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 C84333A6921; Fri, 11 Jun 2010 07:59:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.157
X-Spam-Level: **
X-Spam-Status: No, score=2.157 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_50=0.001, HELO_MISMATCH_NET=0.611, HOST_EQ_NL=1.545]
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 ETYBODfuKbl3; Fri, 11 Jun 2010 07:59:54 -0700 (PDT)
Received: from relay.versatel.net (relay60.tele2.vuurwerk.nl [62.250.3.60]) by core3.amsl.com (Postfix) with ESMTP id 8DA073A6918; Fri, 11 Jun 2010 07:59:53 -0700 (PDT)
Received: from [87.215.199.34] (helo=BertLaptop) by relay.versatel.net with smtp (Exim 4.69) (envelope-from <bertietf@bwijnen.net>) id 1ON5i4-0002rc-VK; Fri, 11 Jun 2010 16:59:53 +0200
Message-ID: <211423AAAF024289A47B1713400BD4A3@BertLaptop>
From: "Bert Wijnen \(IETF\)" <bertietf@bwijnen.net>
To: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>, "Martin Bjorklund" <mbj@tail-f.com>
References: <4C11ED2B.1070707@deployingradius.com> <20100611080956.GA5257@elstar.local> <20100611.101949.192441308.mbj@tail-f.com> <20100611085506.GE5257@elstar.local>
In-Reply-To: <20100611085506.GE5257@elstar.local>
Date: Fri, 11 Jun 2010 16:49:50 +0200
Organization: Consultant
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6002.18197
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18197
Cc: "Ersue, Mehmet \(NSN - DE/Munich\)" <mehmet.ersue@nsn.com>, draft-ietf-netconf-monitoring@tools.ietf.org, secdir@ietf.org, iesg@ietf.org
Subject: Re: [secdir] secdir review of draft-ietf-netconf-monitoring
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: Fri, 11 Jun 2010 14:59:55 -0000

Juergen, I will add your text to the template.

I am assuming that Dan will check this further with the securioty ADs.
The status (as far as I know) is that the security ADs are/were
evaluating our latest template (modulo one typio and your new  text).

Bert
----- Original Message ----- 
From: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>;
To: "Martin Bjorklund" <mbj@tail-f.com>;
Cc: <aland@deployingradius.com>;; <secdir@ietf.org>;; <iesg@ietf.org>;; 
<draft-ietf-netconf-monitoring@tools.ietf.org>;; "Bert Wijnen" 
<bertietf@bwijnen.net>;
Sent: Friday, June 11, 2010 10:55 AM
Subject: Re: [secdir] secdir review of draft-ietf-netconf-monitoring


On Fri, Jun 11, 2010 at 10:19:49AM +0200, Martin Bjorklund wrote:

> Actually, this document follows the latest security considerations
> template.

I guess I have to dig out the latest guidelines now... OK, I stand
corrected - the template is indeed pretty short for a read-only
module.

> However, the template does not mention that NETCONF runs over a secure
> transport.  Maybe the template (and this document) should be updated
> to make this clear?

Yes, it seems some introductionary text in the security considerations
about NETCONF might be useful, especially since not all people are
familiar with NETCONF yet. Here is a first draft:

   The YANG module defined in this memo is designed to be accessed
   via the NETCONF protocol [RFC4741]. The lowest NETCONF layer is
   the secure transport layer and the mandatory to implement secure
   transport is SSH [RFC4742].

I am CCing Bert Wijnen since he drove the development of the security
considerations template.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>