Re: [Netconf] WGLC for draft-ietf-netconf-tls-04.txt

badra@isima.fr Tue, 30 September 2008 16:23 UTC

Return-Path: <netconf-bounces@ietf.org>
X-Original-To: netconf-archive@lists.ietf.org
Delivered-To: ietfarch-netconf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6BFFC3A6BD8; Tue, 30 Sep 2008 09:23:43 -0700 (PDT)
X-Original-To: netconf@core3.amsl.com
Delivered-To: netconf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B06D93A6BD8 for <netconf@core3.amsl.com>; Tue, 30 Sep 2008 09:23:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.46
X-Spam-Level:
X-Spam-Status: No, score=-1.46 tagged_above=-999 required=5 tests=[AWL=0.337, BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3, SARE_SUB_ENC_UTF8=0.152]
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 7GyIpwXtd4me for <netconf@core3.amsl.com>; Tue, 30 Sep 2008 09:23:41 -0700 (PDT)
Received: from sp.isima.fr (sp.isima.fr [193.55.95.1]) by core3.amsl.com (Postfix) with ESMTP id 9D3E63A6BD0 for <netconf@ietf.org>; Tue, 30 Sep 2008 09:23:40 -0700 (PDT)
Received: from www.isima.fr (www-data@www.isima.fr [193.55.95.79]) by sp.isima.fr (8.13.8/8.13.8) with SMTP id m8UHNvVI503892; Tue, 30 Sep 2008 18:23:57 +0100
Received: from 88.164.98.77 (SquirrelMail authenticated user badra) by www.isima.fr with HTTP; Tue, 30 Sep 2008 18:22:49 +0200 (CEST)
Message-ID: <54288.88.164.98.77.1222791769.squirrel@www.isima.fr>
In-Reply-To: <001301c9230c$7ed77940$0601a8c0@allison>
References: <50947.88.164.98.77.1222460713.squirrel@www.isima.fr><00bb01c92265$a9c7ba90$0600a8c0@china.huawei.com> <61043.88.164.98.77.1222722436.squirrel@www.isima.fr> <001301c9230c$7ed77940$0601a8c0@allison>
Date: Tue, 30 Sep 2008 18:22:49 +0200
From: badra@isima.fr
To: "tom.petch�" <cfinss@dial.pipex.com>
User-Agent: SquirrelMail/1.4.2
MIME-Version: 1.0
X-Priority: 3
Importance: Normal
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (sp.isima.fr [193.55.95.1]); Tue, 30 Sep 2008 18:23:57 +0100 (WEST)
Cc: � <netconf@ietf.org>
Subject: Re: [Netconf] WGLC for draft-ietf-netconf-tls-04.txt
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/netconf>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: netconf-bounces@ietf.org
Errors-To: netconf-bounces@ietf.org

>> 4. Cipher Suite Requirements
>>
>>      Implementation of the protocol specified in this document MAY
>>      implement any TLS cipher suite that provides mutual authentication.
>>
>>      Implementations MUST support TLS 1.2 [RFC5246] and are REQUIRED to
>>      support the mandatory to implement cipher suite, which is
>>      TLS_RSA_WITH_AES_128_CBC_SHA.  This document is assumed to apply to
>>      future versions of TLS, in which case the mandatory to implement
>>      cipher suite for the implemented version MUST be supported.
>>
>>      In the case of the pre-shared key authentication (described in
>>      Section 3.3), implementations are REQUIRED to support the cipher
>>      suite TLS_DHE_PSK_WITH_AES_128_CBC_SHA RFC4279].
>>
>> Comments?
>> Best regards,
>> Badra
>>
>
> I think that you need more than this, somewhere in the document, giving
> the
> applicability of the two very different suites, when is one appropriate,
> when
> the other.  As it stands, I get the feeling that I am being told that you
> really
> should be using PSK but that someone, perhaps that nasty old security
> directorate, has insisted we conform to BCP0061 and so have had to include
> the
> other as well:-)


I think the "applicability" or the benefits of using pre-shared key based
authentication have been explained in the Introduction of [RFC4279]. To
recall of them, would be sufficient to insert the following text at the
end of the first paragraph of Section 3? (The use of PSK is a MAY, not a
SHOULD)

"The benefits of pre-shared symmetric-key vs. public-/private-key pair
based authentication for the key exchange in TLS have been explained in
the Introduction of [RFC4279]".

Best regards
Badra
_______________________________________________
Netconf mailing list
Netconf@ietf.org
https://www.ietf.org/mailman/listinfo/netconf