RFC 3489:STUN - Simple Traversal of User Datagram ...
RFC-Ref

public Internet


Click on the red underlined text to get to the source

... NATs in tandem between the application entity and the public Internet. ...


... STUN responses. STUN servers are generally attached to the public Internet. ...


... \-----/ +--------------+ Public Internet ................| NAT 2 |....................... ...
... private network 2 through NAT 1. Private network 2 connects to the public Internet through NAT 2. The STUN server resides on the public Internet ...
... public Internet through NAT 2. The STUN server resides on the public Internet. STUN ...
... STUN response are public, and can be used by any host on the public Internet to send packets to the application that sent the STUN request. An ...
... the STUN request was sent. Any packets sent by a host on the public Internet to the public address and port learned by STUN will be ...
... to obtain a publicly routable address, that the server reside on the public Internet. ...


... address cannot be arbitrary. If the attacker is on the public Internet (that is, there are no NATs between it and the STUN ...
... router directs them there. If the attacker is on the public Internet, but they can modify the STUN request, they can insert a RESPONSE-ADDRESS ...


... NATs between it and a server run by a service provider on the public Internet. The purpose of such detection is to determine additional steps that might be necessary in order to receive service ...
... reachable from the first, but it is not known whether the second client resides on the public Internet. o Provide a means for a client ...
... o Provide a means for a client to obtain an address on the public Internet from a non-symmetric NAT, for the express purpose of receiving ...
... IPv6; if a user detects a NAT between themselves and the public Internet, they can call up their access provider and complain about it. ...
... validate that there are no additional middleboxes on the path from the public Internet to the client. If this is the case, the application can continue operation using the address bindings ...
... o STUN assumes that the server exists on the public Internet. If the server is located in another private address realm, the user ...
... NAT in front of their entire network, connecting it to the public Internet. If the STUN server used by A is in A's cable operator's network ...
... STUN server must be in the network which is a common ancestor to both - in this case, the public Internet. - The STUN ...
... NAT connecting their network to the public Internet, and the STUN server was on the public Internet, the address ...
... to the public Internet, and the STUN server was on the public Internet, the address obtained by A would not be usable by B. That is because some NATs ...



Google
Web
RFC-Ref