RFC 3620:The TUNNEL Profile
RFC-Ref

firewall


Click on the red underlined text to get to the source

... profile, a BEEP peer implementing the TUNNEL profile is co-resident with a firewall. An initiating machine inside the firewall makes a connection ...
... TUNNEL profile is co-resident with a firewall. An initiating machine inside the firewall makes a connection to the proxy, then ask that proxy ...
... make a connection to an endpoint outside the firewall. Once this connection is established, the proxy ...


... TUNNEL profile is to allow bidirectional contact between two machines normally separated by a firewall. Since TUNNEL allows this connection ...
... In some environments, it is undesirable to expose the names of machines on one side of a firewall in unencrypted messages on the other side of that firewall. In this case, source routing ...
... machines on one side of a firewall in unencrypted messages on the other side of that firewall. In this case, source routing (using the "fqdn", "ip4", "ip6", "port ...
... route a connection to the firewall proxy, with an innermost "profile" or ...
... profile" or "endpoint" attribute which the firewall proxy understands. Local provisioning can allow a proxy ...
... o Attackers sniffing packets on one side of the firewall cannot see IP addresses or FQDNs ...
... IP addresses or FQDNs of machines on the other side of the firewall; and, o Attackers ...



Google
Web
RFC-Ref