Realm Specific IP (RSIP) Parameters

Created

  • 2001-04-20

Last Updated

  • 2009-07-29

Available Formats

RSIP Parameters

Expert(s)

  • Unassigned

Reference

  • RFC 3103: Realm Specific IP: Protocol Specification

Note

RSIP Parameters was defined in Section 8 of RFC 3103, unless otherwise stated.

Available Formats

Range Registration Procedures
0 Reserved
1-240 Specification Required
241-255 Private Use
Value Parameter Reference
0 Reserved RFC 3103
1 Address RFC 3103
2 Ports RFC 3103
3 Lease Time RFC 3103
4 Client ID RFC 3103
5 Bind ID RFC 3103
6 Tunnel Type RFC 3103
7 RSIP Method RFC 3103
8 Error RFC 3103
9 Flow Policy RFC 3103
10 Indicator RFC 3103
11 Message Counter RFC 3103
12 Vendor Specific Parameter RFC 3103
13-21 Unassigned
22 SPI RFC 3104
23-240 Unassigned
241-255 Reserved for Private Use RFC 3103

RSIP Address Types

Expert(s)

  • Unassigned

Reference

  • RFC 3103: Realm Specific IP: Protocol Specification

Available Formats

Range Registration Procedures
0 Reserved
1-240 Specification Required
241-255 Private Use
Value Addrtype Length of value field (in bytes) Reference
0 Reserved 0 RFC 3103
1 IPv4 4 RFC 3103
2 IPv4 netmask 4 RFC 3103
3 IPv6 16 RFC 3103
4 FQDN varies RFC 3103
5-240 Unassigned - RFC 3103
241-255 Reserved for Private Use - RFC 3103

RSIP Tunnel Types

Expert(s)

  • Unassigned

Reference

  • RFC 3103: Realm Specific IP: Protocol Specification

Available Formats

Range Registration Procedures
0 Reserved
1-240 Specification Required
241-255 Private Use
Value Tunnel Type Reference
0 Reserved RFC 3103
1 IP-IP RFC 3103
2 GRE RFC 3103
3 L2TP RFC 3103
4-240 Unassigned RFC 3103
241-255 Reserved for Private Use RFC 3103

RSIP Methods

Expert(s)

  • Unassigned

Reference

  • RFC 3103: Realm Specific IP: Protocol Specification

Available Formats

Range Registration Procedures
0 Reserved
1-240 Specification Required
241-255 Private Use
Value RSIP method Reference
0 Reserved RFC 3103
1 RSA-IP RFC 3103
2 RSAP-IP RFC 3103
3 RSIP with IPsec (RSIPSEC) RFC 3104
4-240 Unassigned RFC 3103
241-255 Reserved for Private Use RFC 3103

RSIP Local Flow Policies

Expert(s)

  • Unassigned

Reference

  • RFC 3103: Realm Specific IP: Protocol Specification

Available Formats

Range Registration Procedures
0 Reserved
1-240 Specification Required
241-255 Private Use
Value Local Flow Policy Reference
0 Reserved RFC 3103
1 Macro flows RFC 3103
2 Micro flows RFC 3103
3-240 Unassigned RFC 3103
241-255 Reserved for Private Use RFC 3103

RSIP Remote Flow Policies

Expert(s)

  • Unassigned

Reference

  • RFC 3103: Realm Specific IP: Protocol Specification

Available Formats

Range Registration Procedures
0 Reserved
1-240 Specification Required
241-255 Private Use
Value Remote Flow Policy Reference
0 Reserved RFC 3103
1 Macro flows RFC 3103
2 Micro flows RFC 3103
3 No policy RFC 3103
4-240 Unassigned RFC 3103
241-255 Reserved for Private Use RFC 3103

RSIP Vendor IDs

Expert(s)

  • Unassigned

Reference

  • RFC 3103: Realm Specific IP: Protocol Specification

Available Formats

Range Registration Procedures
0 Reserved
1-240 Specification Required
241-255 Private Use
Value Vendor ID Reference
0 Reserved RFC 3103
1-240 Unassigned RFC 3103
241-255 Reserved for Private Use RFC 3103

RSIP Message Types

Expert(s)

  • Unassigned

Reference

  • RFC 3103: Realm Specific IP: Protocol Specification

Available Formats

Range Registration Procedures
0 Reserved
1-240 Specification Required
241-255 Private Use
Value Message Implementation Status Reference
0 Reserved
1 ERROR_RESPONSE gateway mandatory RFC 3103
2 REGISTER_REQUEST host mandatory RFC 3103
3 REGISTER_RESPONSE gateway mandatory RFC 3103
4 DE-REGISTER_REQUEST host mandatory RFC 3103
5 DE-REGISTER_RESPONSE gateway mandatory RFC 3103
6 ASSIGN_REQUEST_RSA-IP host optional RFC 3103
7 ASSIGN_RESPONSE_RSA-IP gateway optional RFC 3103
8 ASSIGN_REQUEST_RSAP-IP host mandatory RFC 3103
9 ASSIGN_RESPONSE_RSAP-IP gateway mandatory RFC 3103
10 EXTEND_REQUEST host mandatory RFC 3103
11 EXTEND_RESPONSE gateway mandatory RFC 3103
12 FREE_REQUEST host mandatory RFC 3103
13 FREE_RESPONSE gateway mandatory RFC 3103
14 QUERY_REQUEST host optional RFC 3103
15 QUERY_RESPONSE gateway mandatory RFC 3103
16 LISTEN_REQUEST host optional RFC 3103
17 LISTEN_RESPONSE gateway optional RFC 3103
18-21 Unassigned
22 ASSIGN_REQUEST_RSIPSEC host optional RFC 3104
23 ASSIGN_RESPONSE_RSIPSEC gateway optional RFC 3104
24-240 Unassigned
241-255 Reserved for Private Use

RSIP Error Codes

Registration Procedure(s)

  • Specification Required

Expert(s)

  • Unassigned

Reference

  • RFC 3103: Realm Specific IP: Protocol Specification

Note

100s  General errors
200s  Parameter and message errors.  The gateway uses these errors
      when it detects that a parameter or message is malformed, as
      well as when it does not understand a parameter or message.
300s  Permission, resource, and policy errors.  The gateway uses these
      errors when a host has attempted to do something that it is
      not permitted to do, or something that violated gateway policy.
400s  IPsec errors.  All errors specific to RSIP / IPsec operation.

Available Formats

Code Description Reference
101 UNKNOWN_ERROR. An error that cannot be identified has occurred. This error should be used when all other error messages are inappropriate. RFC 3103
102 USE_TCP. A host has attempted to use UDP on a server that only supports TCP. RFC 3103
103 FLOW_POLICY_VIOLATION: A host has not specified address or port information in enough detail for its assigned flow policy. RFC 3103
104 INTERNAL_SERVER_ERROR: An RSIP server application has detected an unrecoverable error within itself or the RSIP gateway. RFC 3103
105 MESSAGE_COUNTER_REQUIRED: An RSIP host did not use a message counter parameter in a situation in which it should have. RFC 3103
106 UNSUPPORTED_RSIP_VERSION: An RSIP host sent a message with a version number that is not supported by the RSIP gateway. RFC 3103
201 MISSING_PARAM. The request does not contain a required parameter. RFC 3103
202 DUPLICATE_PARAM. The request contains an illegal duplicate parameter. RFC 3103
203 EXTRA_PARAM. The request contains a parameter that it should not. RFC 3103
204 ILLEGAL_PARAM. The gateway does not understand a parameter type. RFC 3103
205 BAD_PARAM. A parameter is malformed. RFC 3103
206 ILLEGAL_MESSAGE. The gateway does not understand the message type. The message type is neither mandatory nor optional. RFC 3103
207 BAD_MESSAGE. A message is malformed and gateway parsing failed. RFC 3103
208 UNSUPPORTED_MESSAGE: The host has transmitted an optional message that the gateway does not support. RFC 3103
301 REGISTER_FIRST. The RSIP host has attempted to request or use resources without registering. RFC 3103
302 ALREADY_REGISTERED. The host has attempted to register again without first de-registering. RFC 3103
303 ALREADY_UNREGISTERED. The host has attempted to de-register but it is already in the unregistered state. RFC 3103
304 REGISTRATION_DENIED. The gateway will not allow the host to register. RFC 3103
305 BAD_CLIENT_ID. The host has referred to itself with the wrong client ID. RFC 3103
306 BAD_BIND_ID. The request refers to a bind ID that is not valid for the host. RFC 3103
307 BAD_TUNNEL_TYPE. The request refers to a tunnel type that is not valid for the host. RFC 3103
308 LOCAL_ADDR_UNAVAILABLE. The gateway is currently not able to allocate ANY local address, but the host may try again later. RFC 3103
309 LOCAL_ADDRPORT_UNAVAILABLE. The gateway is currently not able to allocate ANY local IP address / port tuple of the requested magnitude (i.e., number of ports), but the host may try again later. RFC 3103
310 LOCAL_ADDR_INUSE. The gateway was not able to allocate the requested local address because it is currently used by another entity. RFC 3103
311 LOCAL_ADDRPORT_INUSE. The gateway was not able to allocate the requested local address / port tuple because it is currently used by another entity. RFC 3103
312 LOCAL_ADDR_UNALLOWED. The gateway will not let the host use the specified local IP address due to policy. RFC 3103
313 LOCAL_ADDRPORT_UNALLOWED. The gateway will not let the host use the specified local address / port pair due to policy. RFC 3103
314 REMOTE_ADDR_UNALLOWED. The gateway will not allow the host to establish a session to the specified remote address. RFC 3103
315 REMOTE_ADDRPORT_UNALLOWED. The gateway will not allow the host to establish a session to the specified remote address / port tuple. RFC 3103
401 IPSEC_UNALLOWED. The server will not allow the client to use end-to-end IPsec. RFC 3104
402 IPSEC_SPI_UNAVAILABLE. The server does not have an SPI available for client use. RFC 3104
403 IPSEC_SPI_INUSE. The client has requested an SPI that another client is currently using. RFC 3104