RFC 3365: Strong Security Requirements for Internet Engineering Task Force Standard Protocols

It is the consensus of the IETF that IETF standard protocols MUST make use of appropriate strong security mechanisms. This document describes the…

Read RFC 3365 on the RFC Editor

Outgoing relationships (6 related RFCs)

Informative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Informative reference — RFC 2246: The TLS Protocol Version 1.0
Informative reference — RFC 2743: Generic Security Service Application Program Interface Version 2, Update 1
Informative reference — RFC 2411: IP Security Document Roadmap
Informative reference — RFC 2222: Simple Authentication and Security Layer (SASL)
Informative reference — RFC 2828: Internet Security Glossary

Incoming relationships (12 related RFCs)

Normatively referenced by — RFC 6587: Transmission of Syslog Messages over TCP
Informatively referenced by — RFC 7201: Options for Securing RTP Sessions
Informatively referenced by — RFC 7202: Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution
Informatively referenced by — RFC 7624: Confidentiality in the Face of Pervasive Surveillance: A Threat Model and Problem Statement
Informatively referenced by — RFC 7696: Guidelines for Cryptographic Algorithm Agility and Selecting Mandatory-to-Implement Algorithms
Informatively referenced by — RFC 6726: FLUTE - File Delivery over Unidirectional Transport
Informatively referenced by — RFC 6271: Requirements for SIP-Based Session Peering
Informatively referenced by — RFC 7574: Peer-to-Peer Streaming Peer Protocol (PPSPP)
Informatively referenced by — RFC 7687: Report from the Strengthening the Internet (STRINT) Workshop
Informatively referenced by — RFC 8280: Research into Human Rights Protocol Considerations
Informatively referenced by — RFC 9887: Terminal Access Controller Access-Control System Plus (TACACS+) over TLS 1.3
Informatively referenced by — RFC 6968: FCAST: Object Delivery for the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable Multicast (NORM) Protocols