Skip to main content

Textual Analysis Methodology for Security Considerations Sections
draft-mcfadden-smart-rfc3552-textual-research-02

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Mark McFadden , Alan Mills
Last updated 2021-03-13 (Latest revision 2020-09-09)
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

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 RFC3552, an examination of recent, published Security Considerations sections be carried out as a baseline for how to improve RFC3552. 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
Alan Mills

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