RFC 3620:The TUNNEL Profile
RFC-Ref

address


Click on the red underlined text to get to the source

... BEEP connection, in much the way a NAT translates IP addresses. However, detailed discussion of such uses is beyond the scope of this ...


... Proxy2 then strips the outermost element, looking up the appropriate address and port, and forwards the <tunnel/> element ...
... Proxy2 then strips the outermost element, looking up the appropriate address and port, and forwards the <tunnel/> element ...


... DNS for translation to an IP number. An "ip4" attribute is interpreted as the dotted-quad representation of an IPv4 address. An "ip6" attribute is interpreted as a text representation of an IPv6 address. In each of these cases, a transport connection ...
... is interpreted as the dotted-quad representation of an IPv4 address. An "ip6" attribute is interpreted as a text representation of an IPv6 address. In each of these cases, a transport connection is established to the so-identified server. If the outermost element ...


... profile. Hence, the "srv" attribute "_tunnel._tcp" MAY be used as a default for finding the appropriate address for tunneling into a particular domain ...


... Attackers sniffing packets on one side of the firewall cannot see IP addresses or FQDNs of machines on the other side of the firewall ...
... Attackers cannot exhaustively attempt to connect to many FQDNs or IP addresses via source routing and use the error messages as an ...


... semantics: See Section 4 of this document. Contact information: See the Author's Address appendix of this document. ...
... tunnel Contact Information: See the "Authors' Addresses" section of this memo ...


... Author's Address ...



Google
Web
RFC-Ref