RSIP lets a host borrow one or more IP addresses (and UDP/TCP port) from one or more RSIP gateways, by leasing (usually public) IP addresses and ports to RSIP hosts located in other (usually private) addressing realms.
The RSIP client requests registration with an RSIP gateway. The gateway in turn delivers either a unique IP address or a shared IP address and a unique set of TCP/UDP ports and associates the RSIP host address to this address. The RSIP host uses this address to send packets to destinations in the other realm. The tunnelled packets between RSIP host and gateway contain both addresses, and the RSIP gateway strips off the host address header and sends the packet to the destination.
RSIP can also be used to relay traffic between several different privately addressed networks by leasing several different addresses to reach different destination networks.
As of November 2004[update], the protocol was in the experimental stage and not yet in widespread use.
- Interactive Connectivity Establishment (ICE)
- Middlebox Middlebox Communications (MIDCOM)
- Simple Traversal of UDP over NATs (STUN)
- Traversal Using Relay NAT (TURN)
- Universal Plug and Play (UPnP)
- RFC 3102 - Realm Specific IP: Framework
- RFC 3103 - Realm Specific IP: Protocol Specification
- RFC 3104 - RSIP Support for End-to-end IPsec