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

Document Type Active Internet-Draft (individual)
Last updated 2019-06-27
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Independent Submission                                      M. McFadden
Internet Draft                             internet policy advisors ltd
Intended status: Informational                            June 27, 2019
Expires: December 2019

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

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on October 27, 2019.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors. All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document. Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document. Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

McFadden               Expires October 27, 2019                [Page 1]
Internet-Draft       RFC3552 Research Methodology             June 2019

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.

Table of Contents

   1. Introduction...................................................2
   2. Conventions used in this document..............................3
   3. Motivation.....................................................3
      3.1. Non-goals and scoping.....................................4
      3.2. Research Group............................................4
   4. Goals for Surveying Existing Security Considerations Sections..4
   5. Methodology....................................................5
      5.1. Methodology Overview......................................5
      5.2. Quantitative Methodology..................................6
      5.3. Qualitative Methodology...................................6
      5.4. Implications of the Size of n-set.........................7
   6. Security Considerations........................................7
   7. IANA Considerations............................................8
   8. References.....................................................8
      8.1. Normative References......................................8
      8.2. Informative References....................................8
   9. Acknowledgments................................................8
   Appendix A. Document History......................................9

1. Introduction

   RFC 2223 requires that all RFCs have a Security Consideration
   section.  The motivation of the section is both to encourage RFC
   authors to consider security in protocol design and to inform readers
   of relevant security issues.  RFC 3552 was published in July of 2003
   to give guidance to RFC authors on how to write a good Security
   Considerations section.  It is structured in three parts: a tutorial
   and definitional section, then a series of guidelines, and finally a
   series of examples.

McFadden              Expires December 27, 2019                [Page 2]
Internet-Draft       RFC3552 Research Methodology             June 2019

   It is possible to observe that the Internet security landscape has
   changed significantly since the publication of RFC 3552. Rather than
Show full document text