port
Click on the red underlined text to get to the source
... element looks like this:
<tunnel fqdn='proxy2.example.com' port='604'>
<tunnel fqdn='final.example.com' port ...
... element looks like this:
<tunnel fqdn='proxy2.example.com' port='604'>
<tunnel fqdn='final.example.com' srv='_telnet ...
... element looks like this:
<tunnel fqdn='proxy2.example.com' port='604'>
<tunnel fqdn='final.example.com' svc='_telnet ...
... [2] Proxy1 maps this to
<tunnel fqdn="proxy2.example.com" port="604">
<tunnel profile="http://xml.resource/org/profiles ...
... Proxy2 then strips the outermost element, looking up the
appropriate address and port, and forwards the <tunnel/>
element ...
... [2] Proxy1 maps this to
<tunnel fqdn="proxy2.example.com" port="604">
<tunnel endpoint="operator console">
...
... Proxy2 then strips the outermost element, looking up the
appropriate address and port, and forwards the <tunnel/>
element ...
... RFC2373(-> 3513(-> 4291draft)) [4]. The format of the "port" attribute is a decimal number
between one and 65535, inclusive. The format of the "srv" attribute
is a pair of identifiers ...
... The only allowable combinations of attributes are as follows:
o fqdn + port;
o fqdn + srv;
...
...
If the outermost element has a "port" attribute and an "fqdn"
attribute but no "srv" attribute, then "fqdn" is looked up as an A
record via DNS ...
... 6], and the appropriate server is contacted; if
that lookup fails and a "port" attribute is present, the connection
is attempted as if the "srv" attribute were not specified.
...
... firewall. In this case, source routing (using the
"fqdn", "ip4", "ip6", "port" and "srv" attributes) can route a
connection ...