RFC 3104: RSIP Support for End-to-end IPsec
In plain English — editorial summary, not part of the RFC
This document proposes mechanisms that enable Realm Specific IP (RSIP) to handle end-to-end IPsec (IP Security). This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC3104
- Published
- October 2001
- Authors
- G. Montenegro; M. Borella
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- tsv
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3105Finding an RSIP Server with SLPCurrent
October 2001
- RFC 3102Realm Specific IP: FrameworkCurrent
October 2001
- RFC 3103Realm Specific IP: Protocol SpecificationCurrent
October 2001
- RFC 4097Middlebox Communications (MIDCOM) Protocol EvaluationUpdated
June 2005
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
- RFC 3304Middlebox Communications (midcom) Protocol RequirementsCurrent
August 2002
- RFC 3989Middlebox Communications (MIDCOM) Protocol SemanticsObsoleted
February 2005
- RFC 4787Network Address Translation (NAT) Behavioral Requirements for Unicast UDPUpdated
January 2007
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?