Technology and engineering · 2002
RFC 3365: Strong Security Requirements for Internet Engineering Task Force Standard Protocols
by J. Schiller
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.
Anyone can see what's on the shelves. Open a book with a free account, and stay in touch with its book club.
- First published
- 2002
- Status
- Best Current Practice
- Pages
- 8
- Also known as
- BCP 61
- Copyright
- ✓ Free to read · Copied in full, as published
Where it comes from
RFC Editor · IETF Datatracker · IETF Trust Legal Provisions
Copied in full and unchanged from the RFC Editor, with the RFC's own notices. © IETF Trust and the persons identified as the document authors. The IETF Trust allows copying and distributing an RFC in full and without modification, so Micwyn shows it exactly as published and makes no study guide, audio or other version of it.
Discuss a passage
Select any passage in the reader and press Discuss to talk about it in public.