Browse Prior Art Database

A method for Realm Specific IP signaling using DHCP

IP.com Disclosure Number: IPCOM000028926D
Original Publication Date: 2004-Jun-08
Included in the Prior Art Database: 2004-Jun-08

Publishing Venue

IBM

Abstract

Disclosed in this paper is a new method of using existing DHCP implementations as signaling vehicle for RSIP. Current specification for RSIP defines operations on the flow of packets and also signaling that has to happen between RSIP clients and server. The packet flow consists of a) Client preparing the packet with RSIP global address and port and tunneling it with its own address up to RSIP server b) RSIP server stripping the tunnel header and forwarding it to the destination machine c) RSIP server receiving the response packets and tunneling them back to the Client Signaling part consists of a) Client discovering RSIP server b) Client registering with RSIP server c) Client requesting global address, port pair(s). d) Optionally client querying RSIP server to find out whether a particular address to which one of its applications trying to connect is local or remote (outside) of the RSIP server (essentially means whether translation is required or not) Implementing this level of extensive signaling between each client and the RSIP server would be costly in terms of a) Server performance b) Implementation complexity of the signaling vehicle for RSIP resource management