Realm Specific IP: Framework
draft-ietf-nat-rsip-framework-05

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 3102.
Authors Jeffrey Lo , Michael Borella , Gabriel Montenegro , David Grabelsky
Last updated 2013-03-02 (Latest revision 2000-07-14)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Experimental
Formats
txt htmlized pdf bibtex bibxml
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Became RFC 3102 (Experimental)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)
Email authors Email WG IPR References Referenced by Nits Search email archive
draft-ietf-nat-rsip-framework-05 
A new Request for Comments is now available in online RFC libraries.

        RFC 3102

        Title:      Realm Specific IP: Framework
        Author(s):  M. Borella, J. Lo, D. Grabelsky, G. Montenegro
        Status:     Experimental
        Date:       October 2001
        Mailbox:    mike_borella@commworks.com, yidarlo@yahoo.com,
                    david_grabelsky@commworks.com, gab@sun.com
        Pages:      30
        Characters: 73856
        SeeAlso/Updates/Obsoletes:    None

        I-D Tag:    draft-ietf-nat-rsip-framework-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3102.txt

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 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.