RFC 3365: Strong Security Requirements for Internet Engineering Task Force Standard Protocols
In plain English — editorial summary, not part of the RFC
It is the consensus of the IETF that IETF standard protocols MUST make use of appropriate strong security mechanisms. This document describes the history and rationale for this doctrine and establishes this doctrine as a best current practice.
Document record
- Document ID
- RFC3365
- Published
- August 2002
- Authors
- J. Schiller
- Status
- BEST CURRENT PRACTICE
- Stream
- Legacy
- Area
- —
- Pages
- 8
- Also known as
- BCP61
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1822A Grant of Rights to Use a Specific IBM patent with PhoturisCurrent
August 1995
- RFC 1640The Process for Organization of Internet Standards Working Group (POISED)Current
June 1994
- RFC 1601Charter of the Internet Architecture Board (IAB)Obsoleted
March 1994
- RFC 1358Charter of the Internet Architecture Board (IAB)Obsoleted
August 1992
- RFC 3677IETF ISOC Board of Trustee Appointment ProceduresCurrent
December 2003
- RFC 3774IETF Problem StatementCurrent
May 2004
- RFC 3797Publicly Verifiable Nominations Committee (NomCom) Random SelectionCurrent
June 2004
- RFC 3844IETF Problem Resolution ProcessCurrent
August 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?