RFC 3102: Realm Specific IP: Framework
In plain English — editorial summary, not part of the RFC
This document examines the general framework of Realm Specific IP (RSIP). RSIP is intended as a alternative to NAT in which the end-to- end integrity of packets is maintained. We focus on implementation issues, deployment scenarios, and interaction with other layer-three protocols. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC3102
- Published
- October 2001
- Authors
- M. Borella; J. Lo; D. Grabelsky; G. Montenegro
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- tsv
- Pages
- 30
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3104RSIP Support for End-to-end IPsecCurrent
October 2001
- RFC 3105Finding an RSIP Server with SLPCurrent
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 2998A Framework for Integrated Services Operation over Diffserv NetworksCurrent
November 2000
- RFC 2914Congestion Control PrinciplesUpdated
September 2000
- RFC 3304Middlebox Communications (midcom) Protocol RequirementsCurrent
August 2002
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?