Set of RFC Documents SRDs

1
Set of RFC DocumentsSRDs

• Trend Micro NSSG
• Douglas Otis
• doug_otis_at_trendmicro.com
• Toward better RFC presentation and management

2
SRD Overview

• Establish reference anchors for endeavours
• Classify RFC relationships
• Couple anchors with a Status database
• SRDs submitted with I-D IESG action
• IESG reviews IETF Notes from WGs
• IESG creates IESG Notes
• IESG assigns forums
• IESG reviews security alerts, interoperation
  reports, and implementer and administrator
  guidance as made available

3
SRD goals

• Establish stable references for IETF product
• Create comprehensive classifications of RFCs as
  related to distinct endeavours
• Minimize repetition of information
• Minimize maintenance
• Improve document tracking from inception to
  obsolescence
• Improve communications

4
The Present RFC Situation

• The flat RFC structure is difficult to use, as
  the number of RFCs grow
• Indexes do not provide comprehensive sets of RFCs
• Categories of RFCs are difficult to maintain
• Open issues are difficult to track
• Consolidation of information should be reviewed

5
Minimal process change but tools needed for SRDs

• Process change requires an evolutionary, rather
  than revolutionary approach
• People should see benefits with the least amount
  of effort possible, but this requires automation
• Automated generation of HTML, RSS, and event
  notification with current link support
• Links to a Status database

6
SRD Classifications

• core
• extensions
• guidance
• obsoletes
• experimental
• definitions
• companion (other SRDs)

7
Status Partitions

• IESG Notes
• IETF Notes
• Security Alerts
• Developer Considerations
• Administrator Considerations
• Interoperation (Versioning and report URIs)
• Forum URI (mailing list)

8
Steps along the way

• Agree to RFC classification
• Agree to Status Partitions
• Agree to SRD document format
• Use scripts to generate first rough cut
• Find assistance for RFC classification
• Present work product to related WG
• Present to the community via web pages
• Incorporate feedback on error or omissions
• Require SRD for I-D submission
• Define process for Status publishing