Proxy TUNNEL item configuration.

Each item provided allow to configure a particular value conforming a next hop BEEP proxy to be traversed to reach the destination.

See vortex_tunnel_new for more details about using this enumerations.

Enumerator:

TUNNEL_END_CONF	Beacon used by the vortex_tunnel_settings_add_hop function to signal that no more configuration items are expected.
TUNNEL_FQDN	Full qualified domain name to be configured a particular hop.
TUNNEL_PORT	Tcp end point port for the hop configuration.
TUNNEL_IP4	IP version 4 address for the hop configuration.
TUNNEL_IP6	IP version 6 address for the hop configuration.
TUNNEL_SRV	DNS service record configuration.
TUNNEL_URI	An URI value to be proxied. Under normal operations a connection created through a BEEP proxy is configured with TUNNEL_IP4 and TUNNEL_PORT values. However, TUNNEL profile also allows requesting to proxy a particular profile, letting the decision to map that "profile" to a particular host location to the BEEP proxy. How is mapped the "profile" request to a particular host location is a matter of provisioning for each BEEP TUNNEL server. This value is only allowed to define the remote endpoint to connect to.
TUNNEL_ENDPOINT	An endpoint configuration, a user defined string configured by the provision of each BEEP proxy traversed. This value provides an alternative hop configuration to create tunnels. It allows to configure a final destination providing a string description like: "application server", "console operator", etc. How is mapped the "profile" request to a particular host location is a matter of provisioning for each BEEP TUNNEL server. This value is only allowed to define the remote endpoint to connect to.