Methodology for Researching Security Considerations Sections
draft-mcfadden-rfc3552-research-methodology-00

Document Type Expired Internet-Draft (individual)
Authors Mark McFadden  , Alan Mills 
Last updated 2020-09-05 (latest revision 2020-03-04)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-mcfadden-rfc3552-research-methodology-00.txt

Abstract

RFC3552 provides guidance to authors in crafting RFC text on Security Considerations. The RFC is more than fifteen years old. With the threat landscape and security ecosystem significantly changed since the RFC was published, RFC3552 is a candidate for update. This draft proposes that, prior to drafting an update to RFC3553, an examination of recent, published Security Considerations sections be carried out as a baseline for how to improve RFC3553. It suggests a methodology for examining Security Considerations sections in published RFCs and the extraction of both quantitative and qualitative information that could inform a revision of the older guidance. It also reports on a recent experiment on textual analysis of sixteen years of RFC Security Consideration sections.

Authors

Mark McFadden (Mark@internetpolicyadvisors.com)
Alan Mills (alan2.mills@live.uwe.ac.uk)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)