RSIP Support for End-to-end IPsec
draft-ietf-nat-rsip-ipsec-04
The information below is for an old version of the document that is already published as an RFC.
Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 3104.
|
|
---|---|---|---|
Authors | Michael Borella , Gabriel Montenegro | ||
Last updated | 2020-01-21 (Latest revision 2000-07-20) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | Experimental | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Became RFC 3104 (Experimental) | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
draft-ietf-nat-rsip-ipsec-04
A new Request for Comments is now available in online RFC libraries. RFC 3104 Title: RSIP Support for End-to-end IPsec Author(s): G. Montenegro, M. Borella Status: Experimental Date: October 2001 Mailbox: gab@sun.com, mike_borella@commworks.com Pages: 19 Characters: 38719 SeeAlso/Updates/Obsoletes: None I-D Tag: draft-ietf-nat-rsip-ipsec-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3104.txt This document proposes mechanisms that enable Realm Specific IP (RSIP) to handle end-to-end IPsec (IP Security). This document is a product of the Network Address Translator Working Group of the IETF. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. 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.