1 - 3 - 4 - 6 - 8 - A - B - C - D - E - F - G - H - I - K - L - M - N - O - P - R - S - T - U - V - W
version
Click on the red underlined text to get to the source
... term SIMCO refers to SIMCO version 3.0. The term "prefix-length" is
used as described in [RFC4291 ...
... 0x20 : request not applicable
0x21 : lack of resources
0x22 : protocol version mismatch
0x23 : authentication failed
...
... 0x4E : NAT mode not supported
0x4F : IP version mismatch
0x50 : conflict with existing rule
0x51 : not authorized to change lifetime ...
... ----------------------------------------------------
0x0001 : SIMCO protocol version 32 bits
0x0002 : authentication ...
... SIMCO Protocol Version Attribute ...
...
The SIMCO protocol version attribute has a length of four octets.
The first two octets contain the version number, one the major
...
... SIMCO protocol version attribute has a length of four octets.
The first two octets contain the version number, one the major
version number and the other the minor version number ...
... The first two octets contain the version number, one the major
version number and the other the minor version number. Two remaining
octets are reserved.
...
... version number, one the major
version number and the other the minor version number. Two remaining
octets are reserved.
...
... | 0x0001 | 0x0004 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|major version #|minor version #| reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
...
... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|major version #|minor version #| reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
...
... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: Protocol version attribute
The SIMCO protocol ...
...
The SIMCO protocol specified within this document is version 3.0.
The version numbers carried in the protocol version ...
... SIMCO protocol specified within this document is version 3.0.
The version numbers carried in the protocol version attribute are 3
for major version number ...
... version 3.0.
The version numbers carried in the protocol version attribute are 3
for major version number and 0 for minor version number ...
... version numbers carried in the protocol version attribute are 3
for major version number and 0 for minor version number.
...
... S : persistent storage of policy rules
The supported IP version for the internal and external network are
coded into the IIV (Internal IP version ...
... IP version for the internal and external network are
coded into the IIV (Internal IP version) and EIV (external IP
version) parameter fields. They both have a size of two bits.
...
... network are
coded into the IIV (Internal IP version) and EIV (external IP
version) parameter fields. They both have a size of two bits.
Allowed values are 0x1 for IP version ...
... IP
version) parameter fields. They both have a size of two bits.
Allowed values are 0x1 for IP version 4 (IPv4), 0x2 for IP version 6
...
... Allowed values are 0x1 for IP version 4 (IPv4), 0x2 for IP version 6
(IPv6), and the combination of both (0x3) for IPv4 and IPv6 ...
... The second parameter field also has a length of 4 bits. It specifies
the IP version number. Defined values for this field are:
0x1 : IPv4 ...
... respectively. Both have a length of 2 bits. They specify the
requested version of the IP protocol at the inside (IPi) or outside
(IPo) of the middlebox ...
... 0x0320 : negative reply: request not applicable
0x0321 : negative reply: lack of resources
0x0322 : negative reply: protocol version mismatch
0x0323 : negative reply: authentication failed
...
... request message contains one or two attributes: a mandatory SIMCO
version number attribute and an optional authentication challenge
attribute requesting that the middlebox ...
... +--------------------------+
| SIMCO protocol version |
+--------------------------+
| authentication ...
...
The remaining six negative replies are specific to session
establishment. One of them, the 'protocol version mismatch' negative
reply (0x0322), contains a single attribute: the protocol version
...
... session
establishment. One of them, the 'protocol version mismatch' negative
reply (0x0322), contains a single attribute: the protocol version
attribute.
...
... +--------------------------+
| SIMCO protocol version |
+--------------------------+
...
... 0x034E : negative reply: NAT mode not supported
0x034F : negative reply: IP version mismatch
0x0350 : negative reply: conflict with existing rule
0x0351 : negative reply: not authorized to change lifetime ...
... request message starts with checking the major
and minor protocol version number in the protocol version attribute.
If the middlebox ...
... starts with checking the major
and minor protocol version number in the protocol version attribute.
If the middlebox does not support the specified version number ...
... version attribute.
If the middlebox does not support the specified version number, then
the middlebox returns a negative reply message ...
... middlebox returns a negative reply message of type 'protocol
version mismatch' (0x0322) with the protocol version attribute
indicating a version number ...
... reply message of type 'protocol
version mismatch' (0x0322) with the protocol version attribute
indicating a version number that is supported by the middlebox ...
... version mismatch' (0x0322) with the protocol version attribute
indicating a version number that is supported by the middlebox.
After sending this reply, the middlebox ...
... middlebox may then check the PRR parameter set. A negative reply
of type 'IP version mismatch' (0x034F) is returned if the IPi field
does not match the inside IP version of the address ...
... of type 'IP version mismatch' (0x034F) is returned if the IPi field
does not match the inside IP version of the address at the middlebox.
...
... address at the middlebox.
A negative reply of type 'IP version mismatch' (0x034F) is returned
if the IPo field does not match the outside IP version of the address ...
... A negative reply of type 'IP version mismatch' (0x034F) is returned
if the IPo field does not match the outside IP version of the address
at the middlebox ...
... parameter field is set to 'protocols only' (0x1). Consequently, the
attribute has a length of 32 bits. The IP version parameter field is
set according to the IPo parameter field in the PRR parameter set
...
... A NAT binding at the outside (A2) with the requested transport
protocol, external IP version, port range, and port parity is
...
... A NAT binding at the outside (A2) with the requested transport
protocol, external IP version, port range, and port parity is
...
... middlebox reserves an inside (A1) NAT
binding with the requested transport protocol, internal IP
version, port range, and port parity.
...
... parameter field is set to 'full addresses' (0x0). The location
parameter field is set to 'outside' (0x02). The IP version parameter
field is set according to the IPo parameter field in the PRR ...
... to 'full addresses' (0x0). The location parameter field is set to
'inside' (0x01). The IP version parameter field is set according to
the IPi parameter field in the PRR parameter set attribute of the PRR ...
... IP addresses are wildcarding
according to this prefix length. If the IP version number field
indicates IPv6 ...
... parameter field is set to 'full addresses' (0x0). The location
parameter field is set to 'outside' (0x02). The IP version parameter
field is set according to the IP version parameter field in the PER ...
... parameter field is set to 'outside' (0x02). The IP version parameter
field is set according to the IP version parameter field in the PER
parameter set attribute of the PER ...
... addresses' (0x0). The location parameter field is set to 'inside'
(0x01). The IP version parameter field is set according to the IP
version parameter field in the PER parameter set attribute of the PER ...
... addresses' (0x0). The location parameter field is set to 'inside'
(0x01). The IP version parameter field is set according to the IP
version parameter field in the PER parameter set attribute of the PER
...
... IP addresses are wildcarding
according to this prefix length. If the IP version number field
indicates IPv6 ...
... IP addresses are wildcarding
according to this prefix length. If the IP version number field
indicates IPv6 ...
... Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS) Protocol Version 1.1", RFC 4346prop, April 2006. ...
... Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", RFC 2460draft, December 1998. ...
... Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291draft, February 2006. ...