Re: [secdir] Secdir telechat review of draft-ietf-core-resource-directory-25
Benjamin Kaduk <kaduk@mit.edu> Thu, 13 August 2020 18:02 UTC
Return-Path: <kaduk@mit.edu>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C947C3A102D for <secdir@ietfa.amsl.com>; Thu, 13 Aug 2020 11:02:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 XlLWgpPQisJT for <secdir@ietfa.amsl.com>; Thu, 13 Aug 2020 11:02:47 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D4213A102A for <secdir@ietf.org>; Thu, 13 Aug 2020 11:02:47 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 07DI2hMn026808 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 13 Aug 2020 14:02:45 -0400
Date: Thu, 13 Aug 2020 11:02:42 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Valery Smyslov <valery@smyslov.net>
Cc: secdir@ietf.org
Message-ID: <20200813180242.GZ92412@kduck.mit.edu>
References: <159704204394.11310.18005109400419971010@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <159704204394.11310.18005109400419971010@ietfa.amsl.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/BZh3Wt8OcoLfzJFexhKG5COx778>
Subject: Re: [secdir] Secdir telechat review of draft-ietf-core-resource-directory-25
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 13 Aug 2020 18:02:50 -0000
Thanks for the reviews, Valery and Adam! Like Roman, I filed a Discuss ballot with questions about the authorization model, including whether transport security such as (D)TLS can/should be assumed, as you pointed out. (I also mentioned that the discussion of NTP DDoS seems out of place...) -Ben On Sun, Aug 09, 2020 at 11:47:23PM -0700, Valery Smyslov via Datatracker wrote: > Reviewer: Valery Smyslov > Review result: Ready > > 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 -24 version of this draft was reviewed by Adam Montville. I looked over his > review and I think that the issue he raised about possible mitigation of DDoS > amplification attacks has been addressed in this version. I personally think > that sentences describing how DNS and NTP are vulnerable to amplification > attacks are redundant in this document, but that's a matter of taste and > doesn't hurt. > > It is my impression, that Security Considerations were mostly written having in > mind that (D)TLS is always used, however it is only "SHOULD" in this draft (or > even "MAY" if we look at RFC6690 which Security Considerations this draft > refers to). I think that adding a few words describing which consequences for > security not using (D)TLS would have and in which cases it is allowed will make > the Security Considerations more consistent. > > > > _______________________________________________ > secdir mailing list > secdir@ietf.org > https://www.ietf.org/mailman/listinfo/secdir > wiki: http://tools.ietf.org/area/sec/trac/wiki/SecDirReview
- [secdir] Secdir telechat review of draft-ietf-cor… Valery Smyslov via Datatracker
- Re: [secdir] Secdir telechat review of draft-ietf… Roman Danyliw
- Re: [secdir] Secdir telechat review of draft-ietf… Benjamin Kaduk
- Re: [secdir] [core] Secdir telechat review of dra… Christian Amsüss