[Smart] draft-mcfadden-smart-rfc3552-research-methodology

[<[e-mail]>]

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

[e-mail] <mailto:[e-mail]>