Session Traversal Utilities for NAT (STUN) is a standardized set of methods, including a . The STUN protocol and method were updated in RFC , retaining many of the original specifications as a subset of methods, but removing others. 21 Oct STUN was first defined in RFC (standards) back in , and then revised two times once in RFC (standards) in and again in. Session Traversal Utilities for NAT (STUN). This RFC was published in Abstract. Session Traversal Utilities for NAT (STUN) is a protocol that serves.
|Published (Last):||9 April 2010|
|PDF File Size:||16.33 Mb|
|ePub File Size:||20.33 Mb|
|Price:||Free* [*Free Regsitration Required]|
Session Traversal Utilities for NAT (STUN)
Assuming the Identity of a Client The message type field is decomposed further into rfc 5389 following structure: However, experience since the publication of RFC has found that classic STUN simply does not work sufficiently well to be rfd deployable solution. Forming a Request or an Indication The on-the-wire protocol described rfc 5389 is changed only slightly from classic STUN.
The method and class are orthogonal, so that for each method, a request, success response, error rfc 5389, and indication are possible for that method. Classic STUN provided no way to discover whether it would, in fact, work or rfc 5389, and it provided no remedy in cases rfc 5389 it did not. Same meaning as reflexive address. A username and associated password that represent a shared secret between rfc 5389 and 53889. This page was last edited on 2 Aprilat Although there are four message classes, there are only two types of transactions rrfc STUN: Overview of Operation This section is descriptive only.
Attacks against the Protocol Application layer protocols Network address translation Voice frc IP. Processing a Success Response The client side is implemented in the user’s communications rfc 5389, such as a Voice over Internet Protocol VoIP phone or an instant messaging client.
Resends of the same request reuse the same transaction ID, but the client MUST choose a new transaction ID for new transactions unless the new request is bit-wise identical to the previous request and rfc 5389 from the same transport address to the same IP address. A short-term credential has an rfc 5389 temporal scope, which may be based on a specific amount of time such as 5 minutes or on an event such as termination of a SIP dialog.
The details of the encoding, and of the attributes themselves are given in Section The lower agent in the figure is the client, and is rfc 5389 to private network 1. An entity that implements the STUN protocol. In this specification, the terms STUN server and server are synonymous. The server also uses the transaction ID as a key to identify each transaction uniquely across all clients.
STUN agents can safely ignore comprehension-optional attributes they don’t understand, but cannot successfully process a message if it contains comprehension-required attributes that are not understood.
The password from a long-term credential. Sending the Request or Indication In some usages, Rfc 5389 must be multiplexed rfc 5389 other protocols e. Wing, The Internet Society October Retrieved from ” https: STUN is a tool for communications protocols to detect and traverse network address translators that are located in the path between two endpoints of communication.
In RFC [ RFC ], this rfc 5389 was part of the transaction ID; placing the magic cookie in this location allows a server to detect if the client will understand certain attributes rfc 5389 were added in this revised specification.
It is implemented as a light-weight client-server protocol, requiring only simple query and response components with a third-party server located on the common, easily accessible network, typically rfc 5389 Internet. Rosenberg Request for Comments: These mechanisms include DNS discovery, a redirection technique to an alternate server, a fingerprint attribute for demultiplexing, and two authentication and message-integrity exchanges.
The Interactive Connectivity Establishment ICE rfc 5389 provides a structured mechanism to determine the optimal communication path between two peers. STUN agents can safely ignore comprehension-optional attributes they don’t understand, rfc 5389 cannot successfully process a message if it contains comprehension-required attributes that are not understood.
Views Read Edit View history. The algorithm consists of a series of tests to be performed by an application.
stunclient: RFC Session Traversal Utilities for NAT (STUN) client
A short-term credential has an explicit temporal scope, which rfc 5389 be based on a specific amount of time such as 5 minutes or on an event such as termination of a SIP dialog. Typically, a usage indicates when STUN messages get sent, which optional attributes to include, what server is used, and rfc 5389 authentication mechanism is to be used. Same 5839 as reflexive address.
This network connects to private network 2 through NAT 1.