RFC 2401 on Security Architecture for IP

RFC Editor <rfc-ed@ISI.EDU> Wed, 25 November 1998 20:25 UTC

Received: (from adm@localhost) by ietf.org (8.8.5/8.8.7a) id PAA23670 for ietf-123-outbound.10@ietf.org; Wed, 25 Nov 1998 15:25:03 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.8.5/8.8.7a) with ESMTP id PAA23494 for <all-ietf@ietf.org>; Wed, 25 Nov 1998 15:23:13 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id MAA28396; Wed, 25 Nov 1998 12:23:15 -0800 (PST)
Message-Id: <199811252023.MAA28396@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2401 on Security Architecture for IP
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 25 Nov 1998 12:23:15 -0800
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        RFC 2401:

        Title:	    Security Architecture for the Internet Protocol
	Author(s):  S. Kent, R. Atkinson
	Status:     Proposed Standard
	Date:       November 1998
        Mailbox:    kent@bbn.com, rja@corp.home.net
	Pages:      66
        Characters: 168162
        Obsoletes:  1825
        I-D Tag:    draft-ietf-ipsec-arch-sec-07.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2401.txt


This memo specifies the base architecture for IPsec compliant
systems.  The goal of the architecture is to provide various security
services for traffic at the IP layer, in both the IPv4 and IPv6
environments.  This document describes the goals of such systems,
their components and how they fit together with each other and into
the IP environment.  It also describes the security services offered
by the IPsec protocols, and how these services can be employed in the
IP environment.

This document is a product of the IP Security Protocol Working Group
of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  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 Alegre Ramos
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.
ftp://ftp.isi.edu/in-notes/rfc2401.txt"><ftp://ftp.isi.edu/in-notes/rfc2401.txt>