draft-loughney-what-standards-01.txt IETF 59 NEWTRK WG Presented by Spencer Dawkins

Background We are good at generating RFCs. We are not so good at maintaining them. At RFCs, outsiders – groups deploying RFCs – don’t always have a clear view some protocols. The Transport Area has spun up a WG to sort out the various enhancements / to TCP – TCPM WG.

Proposal RFC numbers are not significant in themselves. STD label can ‘lump’ a set of RFCs together – but very few protocols reach STD level. Updating / Obsoleting of RFCs are possible, but there are some implementation bugs in this. The proposal would be to create a label to indicate a set of relating RFCs. We should include Informational, Experimental, Applicability Statements & BCPs inside of label. Probably don’t want to cover individual drafts, unless sponsored by a working group.

Implications Drafts should indicate the label which applies and define more explicitly how the draft relates to existing labels (does it update, replace, obsolete, set requirements, provide best current practices, extends …. ) I assume that one paragraph would be enough. Some problems: Would this be yet another thing that the IESG needs to check? Would this create more work for the Secretariat / RFC Editor? Would we need to appoint experts (as in expert reviewers) to do consistency checks on the labels? Some gains: Provide a cross-referencing tool for people who actually implement & use the stuff we do here. Provide a better tool for maintenance of the RFC series. Provide better scaling for the RFC series.

Example Label: SCTP - Stream Control Transmission Protocol Stable IETF One Mult Deployed Known info change tech recomme impl impl widely harmful doc status RFC 2960 Y Y Y Y N N n/a BASE PROTOCOL RFC 3257 n/a n/a n/a n/a n/a N Yes APP STATEMENT RFC 3286 n/a n/a n/a n/a n/a N Yes INFORMATION RFC 3309 Y Y Y Y N N n/a UPDATES RFC 3436Y YYYNNn/aEXTRA RFC 3554Y YYYNNn/aEXTRA Imp Guide [1]N N Y Y N N n/a EXTENSION Add IP [2] N N Y Y N N n/a EXTENSION PR-SCTP [3] N N Y Y N N n/a EXTENSION SCTP MIB [4] N N Y Y N N n/a MIB SCTPSOCK [5] N N Y Y N N n/a EXTRA [1] draft-ietf-tsvwg-sctpimpguide-10.txt [2] draft-ietf-tsvwg-addip-sctp-08.txt [3] draft-ietf-tsvwg-prsctp-03.txt (approved by IESG) [4]draft-ietf-sigtran-sctp-mib-10.txt [5]draft-ietf-tsvwg-sctpsocket-07.txt RFC 2960 Stream Control Transmission Protocol RFC 3257 Stream Control Transmission Protocol Applicability Statement RFC 3286 An Introduction to the Stream Control Transmission Protocol (SCTP) RFC 3309 Stream Control Transmission Protocol (SCTP) Checksum Change. RFC 3436 Transport Layer Security over Stream Control Transmission Protocol. RFC 3554 On the Use of Stream Control Transmission Protocol (SCTP) with IPsec. Note on the list: Using TCP DSACKs and SCTP Duplicate TSNs to Detect Spurious Retransmissions F-RTO: An Algorithm for Detecting Spurious Retransmission Timeouts with TCP and SCTP

Next Steps Put together a webpage showing examples. Any suggestions for topic / protocol to show?