RFC 3620:The TUNNEL Profile
RFC-Ref

routing


Click on the red underlined text to get to the source

... element, stripping off the outer element and routing <tunnel profile="http://xml.resource/org/profiles ...
... element, stripping off the outer element and routing <tunnel endpoint="operator console"> ...


... proxy processing this element is responsible for determining the appropriate routing to reach a peer serving the BEEP profile indicated by the URI ...
... BEEP profile indicated by the URI in the attribute's value. Rather than source routing, this provides a hop-by-hop routing ...
... routing, this provides a hop-by-hop routing mechanism to a desired service. ...
... proxy processing this element is responsible for determining the appropriate routing to reach a peer indicated by the value of the "endpoint" attribute. Rather than ...
... peer indicated by the value of the "endpoint" attribute. Rather than source routing, this provides a hop-by-hop routing mechanism to a ...
... source routing, this provides a hop-by-hop routing mechanism to a desired machine. There are no restrictions on how machines are identified. ...


... firewall in unencrypted messages on the other side of that firewall. In this case, source routing (using the "fqdn", "ip4", "ip6", "port" and "srv" attributes) can route ...
... FQDNs or IP addresses via source routing and use the error messages as an indication of whether the queried machine exists. For this attack ...



Google
Web
RFC-Ref