
Realm Specific IP (RSIP) Parameters

(last updated 2001-10-15)

Registries included below:
- RSIP Parameters
  - Address types
  - Tunnel types
  - RSIP methods
  - Flow policy
  - Vendor ID
- RSIP message type codes
- RSIP error codes


Registry Name: RSIP Parameters
Reference: [RFC3103]
Registration Procedures: Specification required 

Note: 
RSIP Parameters was defined in section 8 of [RFC3103], unless 
otherwise stated.

Registry:
Value     Parameter                       Reference
--------  ------------------------------  ---------
0         Reserved                        [RFC3103]
1         Address                         [RFC3103]
2         Ports                           [RFC3103]
3         Lease Time                      [RFC3103]
4         Client ID                       [RFC3103]
5         Bind ID                         [RFC3103]
6         Tunnel Type                     [RFC3103]
7         RSIP Method                     [RFC3103]
8         Error                           [RFC3103]
9         Flow Policy                     [RFC3103]
10        Indicator                       [RFC3103]
11        Message Counter                 [RFC3103]
12        Vendor Specific Parameter       [RFC3103]
13-21     Unassigned
22        SPI                             [RFC3104]
24-240    Unassigned
241-255   Reserved for private use        [RFC3103]


Registry Name: RSIP address types 
Reference: [RFC3103]
Registration Procedures: Specification required 

Registry:
Value  Addrtype        Length of value field (in bytes)  Reference
-----  --------------  --------------------------------  ---------
0      Reserved        0                                 [RFC3103]
1      IPv4            4                                 [RFC3103]
2      IPv4 netmask    4                                 [RFC3103]
3      IPv6            16                                [RFC3103]
4      FQDN            varies                            [RFC3103]


Registry Name: RSIP Tunnel Types
Reference: [RFC3103]
Registration Procedures: Specification required 

Registry:
Value  Tunnel Type           Reference
-----  --------------------  ---------
0      Reserved              [RFC3103]
1      IP-IP                 [RFC3103]
2      GRE                   [RFC3103]
3      L2TP                  [RFC3103]
 

Registry Name: RSIP Methods
Reference: [RFC3103]
Registration Procedures: Specification required 

Registry:
Value  RSIP method                   Reference
-----  ----------------------------  --------- 
0      Reserved                      [RFC3103]
1      RSA-IP                        [RFC3103] 
2      RSAP-IP                       [RFC3103]
3      RSIP with IPsec (RSIPSEC)     [RFC3104]


Registry Name: RSIP Flow Policies 
Reference: [RFC3103]
Registration Procedures: Specification required 

Registry:
Value  Flow Policy           Reference
-----  --------------------  ---------
0      Reserved              [RFC3103]
1      Macro flows           [RFC3103]
2      Micro flows           [RFC3103]
3      No policy             [RFC3103]


Registry Name: RSIP Vendor ID's 
Reference: [RFC3103]
Registration Procedures: Specification required 

Registry:
Value  Vendor ID             Reference
-----  --------------------  ---------
0      Reserved              [RFC3103]


Registry Name: RSIP Message Types
Reference: [RFC3103]
Registration Procedures: Specification required 

Registry:
Value     Message                     Implementation  Status      Reference
--------  --------------------------  --------------  ----------  ---------
0         Reserved
1         ERROR_RESPONSE              gateway         mandatory   [RFC3103]
2         REGISTER_REQUEST            host            mandatory   [RFC3103]
3         REGISTER_RESPONSE           gateway         mandatory   [RFC3103]  
4         DE-REGISTER_REQUEST         host            mandatory   [RFC3103]
5         DE-REGISTER_RESPONSE        gateway         mandatory   [RFC3103]
6         ASSIGN_REQUEST_RSA-IP       host            optional    [RFC3103]
7         ASSIGN_RESPONSE_RSA-IP      gateway         optional    [RFC3103]
8         ASSIGN_REQUEST_RSAP-IP      host            mandatory   [RFC3103]
9         ASSIGN_RESPONSE_RSAP-IP     gateway         mandatory   [RFC3103]
10        EXTEND_REQUEST              host            mandatory   [RFC3103]
11        EXTEND_RESPONSE             gateway         mandatory   [RFC3103]
12        FREE_REQUEST                host            mandatory   [RFC3103]
13        FREE_RESPONSE               gateway         mandatory   [RFC3103]
14        QUERY_REQUEST               host            optional    [RFC3103]
15        QUERY_RESPONSE              gateway         mandatory   [RFC3103]
16        LISTEN_REQUEST              host            optional    [RFC3103]
17        LISTEN_RESPONSE             gateway         optional    [RFC3103] 
18-21     Unassigned                      
22        ASSIGN_REQUEST_RSIPSEC      host            optional    [RFC3104] 
23        ASSIGN_RESPONSE_RSIPSEC     gateway         optional    [RFC3104]  
24-240    Unassigned
241-255   Reserved for private use


Registry Name: RSIP Error Codes                                               
Reference: [RFC3103]
Registration Procedures: Specification required 

Note:
100's  General errors
200's  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.
300's  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.
400's  IPsec errors.  All errors specific to RSIP / IPsec operation.

Registry:
Code  Description                                                                Reference  
----  -------------------------------------------------------------------------  ---------
101   UNKNOWN_ERROR.  An error that cannot be identified has occurred.           [RFC3103]
      This error should be used when all other error messages are 
      inappropriate.

102   USE_TCP.  A host has attempted to use UDP on a server that                 [RFC3103]
      only supports TCP.

103   FLOW_POLICY_VIOLATION: A host has not specified address or                 [RFC3103]
      port information in enough detail for its assigned flow policy.

104   INTERNAL_SERVER_ERROR: An RSIP server application has detected             [RFC3103]
      an unrecoverable error within itself or the RSIP gateway.

105   MESSAGE_COUNTER_REQUIRED: An RSIP host did not use a message               [RFC3103]
      counter parameter in a situation in which it should have.

201   MISSING_PARAM. The request does not contain a required parameter.          [RFC3103]

202   DUPLICATE_PARAM. The request contains an illegal duplicate parameter.      [RFC3103]

203   EXTRA_PARAM. The request contains a parameter that it should not.          [RFC3103]

204   ILLEGAL_PARAM. The gateway does not understand a parameter type.           [RFC3103]

205   BAD_PARAM. A parameter is malformed.                                       [RFC3103]

206   ILLEGAL_MESSAGE. The gateway does not understand the message               [RFC3103]
      type.  The message type is neither mandatory nor optional.

207   BAD_MESSAGE. A message is malformed and gateway parsing failed.            [RFC3103]

208   UNSUPPORTED_MESSAGE: The host has transmitted an optional message          [RFC3103]
      that the gateway does not support.

301   REGISTER_FIRST. The RSIP host has attempted to request or use              [RFC3103]
      resources without registering.

302   ALREADY_REGISTERED. The host has attempted to register again               [RFC3103]
      without first de-registering.

303   ALREADY_UNREGISTERED. The host has attempted to de-register but it         [RFC3103]
      is already in the unregistered state.

304   REGISTRATION_DENIED. The gateway will not allow the host to register.      [RFC3103]

305   BAD_CLIENT_ID. The host has referred to itself with the wrong client ID.   [RFC3103]

306   BAD_BIND_ID. The request refers to a bind ID that is not valid for         [RFC3103]
      the host.

307   BAD_TUNNEL_TYPE. The request refers to a tunnel type that is               [RFC3103]
      not valid for the host.

308   LOCAL_ADDR_UNAVAILABLE. The gateway is currently not able to               [RFC3103]
      allocate ANY local address, but the host may try again later.

309   LOCAL_ADDRPORT_UNAVAILABLE.  The gateway is currently not able to          [RFC3103]
      allocate ANY local IP address / port tuple of the requested magnitude 
      (i.e., number of ports), but the host may try again later.

310   LOCAL_ADDR_INUSE. The gateway was not able to allocate the requested       [RFC3103]
      local address because it is currently used by another entity.

311   LOCAL_ADDRPORT_INUSE.  The gateway was not able to allocate the            [RFC3103]
      requested local address / port tuple because it is currently used
      by another entity.

312   LOCAL_ADDR_UNALLOWED. The gateway will not let the host use                [RFC3103]
      the specified local IP address due to policy.

313   LOCAL_ADDRPORT_UNALLOWED. The gateway will not let the host                [RFC3103]
      use the specified local address / port pair due to policy.

314   REMOTE_ADDR_UNALLOWED.  The gateway will not allow the host                [RFC3103]
      to establish a session to the specified remote address.

315   REMOTE_ADDRPORT_UNALLOWED.  The gateway will not allow the host to         [RFC3103]
      establish a session to the specified remote address /  port tuple.

401   IPSEC_UNALLOWED.  The server will not allow the client                     [RFC3104]
      to use end-to-end IPsec.

402   IPSEC_SPI_UNAVAILABLE. The server does not have an SPI                     [RFC3104]
      available for client use.

403   IPSEC_SPI_INUSE.  The client has requested an SPI that                     [RFC3104]
      another client is currently using.


References
----------
[RFC3103]  M. Borella, D. Grabelsky, J. Lo, and K. Tuniguchi, "Realm
           Specific IP: Protocol Specification", RFC 3103, 
           October 2001.

[RFC3104]  G. Montenegro and  M. Borella, "RSIP Support for End-to-end
           IPsec", RFC 3104, October 2001.


(created 2001-04-20)

[]



