Security Mechanisms for the Internet
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 20
- Abstract
- Security must be built into Internet Protocols for those protocols to offer their services securely. Many security problems can be traced to improper implementations. However, even a proper implementation will have security problems if the fundamental protocol is itself exploitable. Exactly how security should be implemented in a protocol will vary, because of the structure of the protocol itself. However, there are many protocols for which standard Internet security mechanisms, already developed, may be applicable. The precise one that is appropriate in any given situation can vary. We review a number of different choices, explaining the properties of each.
- Publication Date
- 2003-12-01
- Status Note
- Informational
- DOI
10.17487/RFC3631- Link
- https://doi.org/10.17487/RFC3631
- Author(s)
- Steven M. BellovinJeffrey I. SchillerCharlie Kaufman
- Keyword(s)
- Protocol, DoS
Latest version of IETF RFC 3631
Document Versions — IETF RFC 3631
-
▶ IETF RFC 3631 (2003-12-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- NIST.FIPS.186 — DSS EXTERNAL
- "Misplaced trust: Kerberos 4 session keys". Proceedings of the Internet Society Network and Distributed Systems Security Symposium, March 1997. EXTERNAL
- Rivest, R., Shamir, A. and L. Adleman, "A Method for Obtaining Digital Signatures and Public-Key Cryptosystems", Communications of the ACM, February 1978. EXTERNAL
- "Foiling the Cracker: A Survey of, and Implications to, Password Security". D. Klein. Usenix UNIX Security Workshop, August 1990. EXTERNAL
- "Cryptography and the Internet", S.M. Bellovin, in Proceedings of CRYPTO '98, August 1998. EXTERNAL
- Kivinen, T., et al., "Negotiation of NAT-Traversal in the IKE", Work in Progress, June 2002. EXTERNAL
- "Limitations of the Kerberos Authentication System". Proceedings of the 1991 Winter USENIX Conference, 1991. EXTERNAL
- "A Real-World Analysis of Kerberos Password Security". T. Wu. Network and Distributed System Security Symposium (NDSS '99). January 1999. EXTERNAL
- "UNIX Password Security", R.H. Morris and K. Thompson, Communications of the ACM. November 1979. EXTERNAL
- "Using the Domain Name System for System Break-Ins". Proc. Fifth Usenix Security Conference, 1995. EXTERNAL
- IETF RFC 1321 [Active*]
- IETF RFC 1510 [Superseded*]
- IETF RFC 1750 [Superseded*]
- IETF RFC 1847 [Active*]
- IETF RFC 2104 [Active, Amended*]
- IETF RFC 2222 [Superseded*]
- IETF RFC 2246 [Superseded*]
- IETF RFC 2289 [Active*]
- IETF RFC 2316 [Active*]
- IETF RFC 2385 [Superseded*]
- IETF RFC 2401 [Superseded*]
- IETF RFC 2402 [Superseded*]
- IETF RFC 2406 [Superseded*]
- IETF RFC 2407 [Superseded*]
- IETF RFC 2411 [Superseded*]
- IETF RFC 2535 [Superseded*]
- IETF RFC 2744 [Active*]
- IETF RFC 2993 [Active*]
- IETF RFC 3174 [Active, Amended*]
- IETF RFC 3261 [Active*]
- IETF RFC 3445 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC3631.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 3631, Security Mechanisms for the Internet. Available at https://doi.org/10.17487/RFC3631
Snippet:
IETF RFC 3631, Security Mechanisms for the Internet. Available at https://doi.org/10.17487/RFC3631
HTML (ISO 690 compliant)
Preview:
IETF RFC 3631, Security Mechanisms for the Internet. Available at https://doi.org/10.17487/RFC3631
Snippet:
<span class="citation"><cite>IETF RFC 3631</cite>, Security Mechanisms for the Internet. Available at <a href="https://doi.org/10.17487/RFC3631" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3631</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 3631, Security Mechanisms for the Internet
doi: 10.17487/RFC3631
url: https://doi.org/10.17487/RFC3631
doi: 10.17487/RFC3631
url: https://doi.org/10.17487/RFC3631
Snippet:
<li> <cite id="bib-rfc3631">IETF RFC 3631</cite>, Security Mechanisms for the Internet <span class="doi">10.17487/RFC3631</span> </li>
Referenced By
- IETF RFC 3862 [Active*]
- IETF RFC 3871 [Active*]
- IETF RFC 4111 [Active*]