Browse Prior Art Database

Realm Specific IP: Protocol Specification (RFC3103)

IP.com Disclosure Number: IPCOM000005854D
Original Publication Date: 2001-Oct-01
Included in the Prior Art Database: 2001-Nov-13

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Borella: AUTHOR [+4]

Abstract

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 3% of the total text.

Network Working Group                                         M. Borella

Request for Comments: 3103                                  D. Grabelsky

Category: Experimental                                         CommWorks

                                                                   J. Lo

                                                    Candlestick Networks

                                                            K. Taniguchi

                                                                 NEC USA

                                                            October 2001

               Realm Specific IP: Protocol Specification

Status of this Memo

   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.

Copyright Notice

   Copyright (C) The Internet Society (2001).  All Rights Reserved.

IESG Note

   The IESG notes that the set of documents describing the RSIP

   technology imply significant host and gateway changes for a complete

   implementation.  In addition, the floating of port numbers can cause

   problems for some applications, preventing an RSIP-enabled host from

   interoperating transparently with existing applications in some cases

   (e.g., IPsec).  Finally, there may be significant operational

   complexities associated with using RSIP.  Some of these and other

   complications are outlined in section 6 of the RFC 3102, as well as

   in the Appendices of RFC 3104.  Accordingly, the costs and benefits

   of using RSIP should be carefully weighed against other means of

   relieving address shortage.

Abstract

   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.

Borella, et al.               Experimental                      [Page 1]

RFC 3103              RSIP Protocol Specification           October 2001

Table of Contents

   1. Introduction  . . . . . . . . . . . . . . . . . . . . . . . .  3

   2. Specification of Requirements . . . . . . . . . . . . . . . .  4

   3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . .  4

   4. Architecture  . . . . . . . . . . . . . . . . . . . . . . . .  5

   5. Transport Protocol  . . . . . . . . . . . . . . . . . . . . .  7

   6. Host / Gateway Relationships  . . . . . . . . . . . . . . . .  7

   7. Gateway Flow Policy and State . . . . . . . . . . . . . . . .  8

   7.1. Local Flow Policy . . . . . . . . . . . . . . . . . . . . .  9

   7.2. Remote Flow Policy  . . . . . . . . . . . . . . . . . . . .  9

   7.3. Gateway State . . . . . . . . . . . . . . . . . . . . . . . 10

   8. Parameter Specification and Formats . . . . . . . . . . . . . 11

   8.1. Address . . . . . . . . . . . . . . . . . . . . . . . . . . 11

   8.2. Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

   8.3. Lease Time  . . . . . . . . . . . . . . . . . . . . . . . . 13

   8.4. Client ID . . . . . . . . . . . . . . . . . . . . . . . . . 13

   8.5. Bind ID . . . . . . . . . . . . . . . . . . . . . . . . . . 13

   8.6. Tunnel Type . ....