RFC 3103: Realm Specific IP: Protocol Specification
In plain English — editorial summary, not part of the RFC
This document presents a protocol with which to implement Realm Specific IP (RSIP). The protocol defined herein allows negotiation of resources between an RSIP host and gateway, so that the host can lease some of the gateway's addressing parameters in order to establish a global network presence. This protocol is designed to operate on the application layer and to use its own TCP or UDP port. In particular, the protocol allows a gateway to allocate addressing and control parameters to a host such that a flow policy can be enforced at the gateway. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC3103
- Published
- October 2001
- Authors
- M. Borella; D. Grabelsky; J. Lo; K. Taniguchi
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- tsv
- Pages
- 54
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3102Realm Specific IP: FrameworkCurrent
October 2001
- RFC 3104RSIP Support for End-to-end IPsecCurrent
October 2001
- RFC 3105Finding an RSIP Server with SLPCurrent
October 2001
- RFC 4097Middlebox Communications (MIDCOM) Protocol EvaluationUpdated
June 2005
- RFC 3304Middlebox Communications (midcom) Protocol RequirementsCurrent
August 2002
- RFC 2730Multicast Address Dynamic Client Allocation Protocol (MADCAP)Current
December 1999
- 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?