RFC 3365 · BEST CURRENT PRACTICE · 2002
SUN · 14 JUN 2026
Strong Security Requirements for Internet Engineering Task Force Standard Protocols
Overview
RFC 3365, “Strong Security Requirements for Internet Engineering Task Force Standard Protocols”, is a Best Current Practice document published in August 2002 by J. Schiller. The canonical text is published by the RFC Editor.
Abstract
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.
What “Best Current Practice” means
Documents the IETF community's recommended operational or procedural practice rather than a protocol specification.
Read this RFC
The canonical text of RFC 3365 is hosted at rfc-editor.org. Available in TXT,HTML.
Other RFCs from 2002
- RFC 3364 Tradeoffs in Domain Name System Support for Internet Protocol version 6
- RFC 3366 Advice to link designers on link Automatic Repeat reQuest
- RFC 3363 Representing Internet Protocol version 6 Addresses in the Domain Name System
- RFC 3367 Common Name Resolution Protocol
- RFC 3362 Real-time Facsimile - image/t38 MIME Sub-type Registration
- RFC 3368 The 'go' URI Scheme for the Common Name Resolution Protocol
- RFC 3361 Dynamic Host Configuration Protocol Option for Session Initiation Protocol Servers
- RFC 3369 Cryptographic Message Syntax