Re: [Smart] draft-mcfadden-smart-rfc3552-research-methodology
Benjamin Kaduk <kaduk@mit.edu> Fri, 28 June 2019 03:34 UTC
Return-Path: <kaduk@mit.edu>
X-Original-To: smart@ietfa.amsl.com
Delivered-To: smart@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9588F1201B7 for <smart@ietfa.amsl.com>; Thu, 27 Jun 2019 20:34:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 dZgWpQ1H8N6T for <smart@ietfa.amsl.com>; Thu, 27 Jun 2019 20:34:22 -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 ABF51120094 for <smart@irtf.org>; Thu, 27 Jun 2019 20:34:22 -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 x5S3YG4t023881 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 27 Jun 2019 23:34:19 -0400
Date: Thu, 27 Jun 2019 22:34:16 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: mark@internetpolicyadvisors.com
Cc: smart@irtf.org
Message-ID: <20190628033415.GY18345@kduck.mit.edu>
References: <009d01d52cf8$bc6b2e30$35418a90$@internetpolicyadvisors.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <009d01d52cf8$bc6b2e30$35418a90$@internetpolicyadvisors.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/smart/_C7phTC2HKc3y0bbYlL8eJ4-Phk>
Subject: Re: [Smart] draft-mcfadden-smart-rfc3552-research-methodology
X-BeenThere: smart@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Stopping Malware And Researching Threats <smart.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/smart>, <mailto:smart-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/smart/>
List-Post: <mailto:smart@irtf.org>
List-Help: <mailto:smart-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/smart>, <mailto:smart-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jun 2019 03:34:25 -0000
Hi Mark, You are not the only one who has noticed that revisiting RFC 3552 might be timely -- I know of some thoughts in this space in both the IETF and the IAB. So it would be interesting to have results to look at; I do not have any particular comment on the proposed methodoloy, though. -Ben On Thu, Jun 27, 2019 at 09:58:08AM -0500, mark@internetpolicyadvisors.com wrote: > All: > > > > I've posted an I-D that proposes a piece of research to be done in support > of a possible revision to RFC 3552. The general idea is to do an > examination of Security Considerations sections from published RFCs. Doing > that examination might help guide the revision of the fifteen-year-old > guidance on writing a Security Considerations section by providing both > quantitative and qualitative information about existing considerations > sections. That research might (or, might not) be published in its own right > and then used as input to drafting a RFC3552bis. > > > > I propose the methodology as a place to start - rather than dive right in > and tackle the revision of RFC3552 immediately it seems prudent to learn > from what we can of recent published RFCs. I'm not only proposing the > methodology for comment and discussion, but I'm also interested in helping > conduct the research once there is an agreed methodology. > > > > Comments and suggestions welcome as are suggestions of where else to try to > gain input, > > > > mark > > > > Mark McFadden > > Principal Consultantsea > > mark@internetpolicyadvisors.co.uk <mailto:mark@internetpolicyadvisors.co.uk> > > > > > > > > > > > > > > > -- > Smart mailing list > Smart@irtf.org > https://www.irtf.org/mailman/listinfo/smart