tus: UNKNOWN) (DOI: 10.17487/RFC0027)
0028 Time Standards. W.K. English. January 1970. (Format: TXT, HTML)
... DOI:
10.17487/RFC0230)
0231 Service center standards for remote usage: A user's view. J.F.
Heafne... er based message systems. National Bureau
of Standards. September 1981. (Format: TXT, HTML) (Obsoleted b... er Based Message Systems.
National Bureau of Standards. January 1983. (Format: TXT, HTML)
(Obsolete
/rfc27>.
RFC0028 | | English, W., "Time Standards", RFC 28, DOI 10.17487/RFC0028, January 1970, <ht... | Heafner, J. and E. Harslem, "Service center standards for remote usage: A user's view", RFC 231, DOI 10... rfc805>.
RFC0806 | RFC0841 | National Bureau of Standards, "Proposed Federal Information Processing Standar... rfc840>.
RFC0841 | | National Bureau of Standards, "Specification for message format for Computer B
nfo/bcp8>.
BCP9 | Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October ... S., and S. Turner, "Characterization of Proposed Standards", BCP 9, RFC 7127, January 2014.
Duss... ey, R., Crocker, D., and E. Burger, "Reducing the Standards Track to Two Maturity Levels", BCP 9, RFC 6410, O... ., "Retirement of the "Internet Official Protocol Standards" Summary Document", BCP 9, RFC 7100, December 201
(Also RFC####)
For example:
0009 The Internet Standards Process -- Revision 3. S. Bradner. October
... 07 HTML= bytes) (Also RFC2014)
0009 The Internet Standards Process. S. Bradner, L. Dusseault, R.
Sparks... 713, RFC9389)
0011 Entities Involved in the IETF Standards Process. R. Salz. June
2022. (Obsoletes RFC2... tes)
(Also RFC2350)
0022 Guide for Internet Standards Writers. G. Scott. June 1998.
(Format: TXT =
(Also RFC####)
For example:
0009 The Internet Standards Process -- Revision 3. S. Bradner. October
... 07 HTML= bytes) (Also RFC2014)
0009 The Internet Standards Process. S. Bradner, L. Dusseault, R.
Sparks... 713, RFC9389)
0011 Entities Involved in the IETF Standards Process. R. Salz. June
2022. (Obsoletes RFC2... tes)
(Also RFC2350)
0022 Guide for Internet Standards Writers. G. Scott. June 1998.
(Format: TXT =
rname/password systems are not acceptable in IETF standards.
4.1.2. Challenge Response and One Time Password... d be
defended against.
Authors of internet standards MUST describe which denial of service
attacks ... .
Note: In general, the IESG will not approve standards track protocols
which do not provide for stron... nore
the broader threat environment. All IETF standards-track protocols
are considered likely to have