[rfc-dist] RFC 3631 on Security Mechanisms for the Internet
rfc-editor@rfc-editor.org (rfc-editor@rfc-editor.org) Fri, 19 December 2003 00:26 UTC
From: rfc-editor@rfc-editor.org
Date: Thu, 18 Dec 2003 16:26:59 -0800
Subject: [rfc-dist] RFC 3631 on Security Mechanisms for the Internet
Message-ID: <200312190026.hBJ0Qxs19684@gamma.isi.edu>
--NextPart A new Request for Comments is now available in online RFC libraries. RFC 3631 Title: Security Mechanisms for the Internet Author(s): S. Bellovin, J. Schiller, C. Kaufman, Eds. Status: Informational Date: December 2003 Mailbox: bellovin@acm.org, jis@mit.edu, charliek@microsoft.com Pages: 20 Characters: 47064 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-iab-secmech-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3631.txt 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. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <031218162557.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3631 --OtherAccess Content-Type: Message/External-body; name="rfc3631.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <031218162557.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart--
- [rfc-dist] RFC 3631 on Security Mechanisms for th… rfc-editor@rfc-editor.org