Realm Specific IP: Protocol Specification
The information below is for an old version of the document that is already published as an RFC.
This is an older version of an Internet-Draft that was ultimately published as RFC 3103.
|Authors||Michael Borella , David Grabelsky , Jeffrey Lo|
|Last updated||2013-03-02 (Latest revision 2000-07-11)|
|RFC stream||Internet Engineering Task Force (IETF)|
|Additional resources||Mailing list discussion|
|Stream||WG state||WG Document|
|IESG||IESG state||RFC 3103 (Experimental)|
|Send notices to||(None)|
A new Request for Comments is now available in online RFC libraries. RFC 3103 Title: Realm Specific IP: Protocol Specification Author(s): M. Borella, D. Grabelsky, J. Lo, K. Taniguchi Status: Experimental Date: October 2001 Mailbox: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com Pages: 54 Characters: 115855 SeeAlso/Updates/Obsoletes: None I-D Tag: draft-ietf-nat-rsip-protocol-07.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3103.txt 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 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.