SOCKS Protocol Version 6

Versions 4 and 5 of the SOCKS protocol were developed two decades ago and are in widespread use for circuit level gateways or as circumvention tools, and enjoy wide support and usage from various software, such as web browsers, SSH clients, and proxifiers. However, their design needs an update in order to take advantage of the new features of transport protocols, such as TCP Fast Open , or to better assist newer transport protocols, such as MPTCP . One of the main issues faced by SOCKS version 5 is that, when taking into account the TCP handshake, method negotiation, authentication, connection request and grant, it may take up to 5 RTTs for a data exchange to take place at the application layer. This is especially costly in networks with a large delay at the access layer, such as 3G, 4G, or satelite. The desire to reduce the number of RTTs manifests itself in the design of newer security protocols. TLS version 1.3 defines a zero round trip (0-RTT) handshake mode for connections if the client and server had previously communicated. TCP Fast Open is a TCP option that allows TCP to send data in the SYN and receive a response in the first ACK, and aims at obtaining a data response in one RTT. The SOCKS protocol needs to concern itself with at least two TFO deployment scenarios: First, when TFO is available end-to-end (at the client, at the proxy, and at the server); second, when TFO is active between the client and the proxy, but not at the server. This document describes the SOCKS protocol version 6. The key improvements over SOCKS version 5 are: The client sends as much information upfront as possible, and does not wait for the authentication process to conclude before requesting the creation of a socket. The connection request also mimics the semantics of TCP Fast Open . As part of the connection request, the client can supply the potential payload for the initial SYN that is sent out to the server. The protocol can be extended via options without breaking backward-compatibility. The protocol can leverage the aforementioned options to support 0-RTT authentication schemes.

Typos and minor clarifications are not listed. draft-08 Removed Address Resolution options Happy Eyeballs options DNS provided by SOCKS draft-07 All fields are now alignned. Eliminated version minors Lots of changes to options 2-byte option kinds Flattened option kinds/types/reply codes; also renamed some options Socket options Proxies MUST always answer them (Clients can probe for support) MPTCP Options: expanded functionality (“please do/don’t do MPTCP on my behalf”) MPTCP Scheduler options removed Listen Backlog options: code changed to 0x03 Revamped Idempotence options Auth data options limited to one per method Authentication Reply: all authentication-related information is now in the options Authentication replies no longer have a field indicating the chosen auth. method Method that must proceed (or whereby authentication succeeded) indicated in options Username/password authentication: proxy now sends reply in option Removed requirements w.r.t. caching authentication methods by multihomed clients UDP: 8-byte association IDs Sessions The proxy is now free to terminate ongoing connections along with the session. The session-terminating request is not part of the session that it terminated. Address Resolution options draft-06 Session options Options now have a 2-byte length field. Stack options Stack options can no longer contain duplicate information. TFO: Better payload size semantics TOS: Added missing code field. MPTCP Scheduler options: Removed support for round-robin “Default” renamed to “Lowest latency first” Listen Backlog options: now tied to sessions, instead of an authenticated user Idempotence options Now used in the context of a session (no longer tied to an authenticated user) Idempotence options have a different codepoint: 0x05. (Was 0x04.) Clarified that implementations that support Idempotence Options must support all Idempotence Option Types. Shifted Idempotence Option Types by 1. (Makes implementation easier.) Shrunk vendor-specific option range to 32 (down from 64). Removed reference to dropping initial data. (It could no longer be done as of -05.) Initial data size capped at 16KB. Application data is never encrypted by SOCKS 6. (It can still be encrypted by the TLS layer under SOCKS.) Messages now carry the total length of the options, rather than the number of options. Limited options length to 16KB. Security Considerations Updated the section to reflect the smaller maximum message size. Added a subsection on resource exhaustion. draft-05 Limited the “slow” authentication negociations to one (and Authentication Replies to 2) Revamped the handling of the first bytes in the application data stream False starts are now recommended. (Added the “False Start” section.) Initial data is only available to clients willing to do “slow” authentication. Moved the “Initial data size” field from Requests to Authentication Method options. Initial data size capped at 2^13. Initial data can no longer be dropped by the proxy. The TFO option can hint at the desired SYN payload size. Request: clarified the meaning of the Address and Port fields. Better reverse TCP proxy support: optional listen backlog for TCP BIND TFO options can no longer be placed inside Operation Replies. IP TOS stack option Suggested a range for vendor-specific options. Revamped UDP functionality Now using fixed UDP ports DTLS support Stack options: renamed Proxy-Server leg to Proxy-Remote leg draft-04 Moved Token Expenditure Replies to the Authentication Reply. Shifted the Initial Data Size field in the Request, in order to make it easier to parse. draft-03 Shifted some fields in the Operation Reply to make it easier to parse. Added connection attempt timeout response code to Operation Replies. Proxies send an additional Authentication Reply after the authentication phase. (Useful for token window advertisements.) Renamed the section “Connection Requests” to “Requests” Clarified the fact that proxies don’t need to support any command in particular. Added the section “TCP Fast Open on the Client-Proxy Leg” Options: Added constants for option kinds Salt options removed, along with the relevant section from Security Considerations. (TLS 1.3 Makes AEAD mandatory.) Limited Authentication Data options to one per method. Relaxed proxy requirements with regard to handling multiple Authentication Data options. (When the client violates the above bullet point.) Removed interdependence between Authentication Method and Authentication Data options. Clients SHOULD omit advertising the “No authentication required” option. (Was MAY.) Idempotence options: Token Window Advertisements are now part of successful Authentication Replies (so that the proxy-server RTT has no impact on their timeliness). Proxies can’t advetise token windows of size 0. Tweaked token expenditure response codes. Support no longer mandatory on the proxy side. Revamped Socket options Renamed Socket options to Stack options. Banned contradictory socket options. Added socket level for generic IP. Removed the “socket” socket level. Stack options no longer use option codes from setsockopt(). Changed MPTCP Scheduler constants. draft-02 Made support for Idempotence options mandatory for proxies. Clarified what happens when proxies can not or will not issue tokens. Limited token windows to 2^31 - 1. Fixed definition of “less than” for tokens. NOOP commands now trigger Operation Replies. Renamed Authentication options to Authentication Data options. Authentication Data options are no longer mandatory. Authentication methods are now advertised via options. Shifted some Request fields. Option range for vendor-specific options. Socket options. Password authentication. Salt options. draft-01 Added this section. Support for idempotent commands. Removed version numbers from operation replies. Request port number for SOCKS over TLS. Deprecate encryption/encapsulation within SOCKS. Added Version Mismatch Replies. Renamed the AUTH command to NOOP. Shifted some fields to make requests and operation replies easier to parse.

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in .

Command code +------------------------------> | Address | | Port | | Options | +------------------------+ +------------------------+ --------> Initial data +------------------------------> +------------------------+ +-----------------------+ Authentication Reply | Type | <----------------------------------+ Options <----- +-----------------------+ <-------------------(Authentication protocol)------------------> +-----------------------+ Authentication Reply | Type = Success | <----------------------------------+ Options <----- +-----------------------+ +-----------------------+ Operation Reply | Reply code | <--------------------+ Bind address <------------------ | Bind port | | Options | +-----------------------+ ]]> When a TCP-based client wishes to establish a connection to a server, it must open a TCP connection to the appropriate SOCKS port on the SOCKS proxy. The client then enters a negotiation phase, by sending the request in , that contains, in addition to fields present in SOCKS 5 , fields that facilitate low RTT usage and faster authentication negotiation. Next, the server sends an authentication reply. If the request did not contain the necessary authentication information, the proxy indicates an authentication method that must proceed. This may trigger a longer authentication sequence that could include tokens for ulterior faster authentications. The part labeled “Authentication protocol” is specific to the authentication method employed and is not expected to be employed for every connection between a client and its proxy server. The authentication protocol typically takes up 1 RTT or more. If the authentication is successful, an operation reply is generated by the proxy. It indicates whether the proxy was successful in creating the requested socket or not. In the fast case, when authentication is properly set up, the proxy attempts to create the socket immediately after the receipt of the request, thus achieving an operational conection in one RTT (provided TFO functionality is available at the client, proxy, and server).

The client starts by sending a request to the proxy.

Version: 6 Command Code: 0x00 NOOP: does nothing. 0x01 CONNECT: requests the establishment of a TCP connection. TFO MUST NOT be used unless explicitly requested. 0x02 BIND: requests the establishment of a TCP port binding. 0x03 UDP ASSOCIATE: requests a UDP port association. Address Type: 0x01: IPv4 0x03: Domain Name 0x04: IPv6 Address: this field’s format depends on the address type: IPv4: a 4-byte IPv4 address Domain Name: one byte that contains the length of the FQDN, followed by the FQDN itself. The string is not NUL-terminated, but padded by NUL characters, if needed. IPv6: a 16-byte IPv6 address Port: the port in network byte order. Padding: set to 0 Options Length: the total size of the SOCKS options that appear in the Options field. MUST NOT exceed 16KB. Options: see . The Address and Port fields have different meanings based on the Command Code: NOOP: The fields have no meaning. The Address Type field MUST be either 0x01 (IPv4) or 0x04 (IPv6). The Address and Port fields MUST be 0. CONNECT: The fields signify the address and port to which the client wishes to connect. BIND, UDP ASSOCIATE: The fields indicate the desired bind address and port. If the client does not require a certain address, it can set the Address Type field to 0x01 (IPv4) or 0x04 (IPv6), and the Address field to 0. Likewise, if the client does not require a certain port, it can set the Port field to 0. Clients can advertise their supported authentication methods by including an Authentication Method Advertisement option (see ).

Upon receipt of a request starting with a version number other than 6, the proxy sends the following response:

Version: 6 A client MUST close the connection after receiving such a reply.

Upon receipt of a valid request, the proxy sends an Authentication Reply:

Version: 6 Type: 0x00: authentication successful. 0x01: authentication failed. Options Length: the total size of the SOCKS options that appear in the Options field. MUST NOT exceed 16KB. Options: see . If the server signals that the authentication has failed and does not signal that any authentication negotiation can continue (via an Authentication Method Selection option), the client MUST close the connection. The client and proxy begin a method-specific negotiation. During such negotiations, the proxy MAY supply information that allows the client to authenticate a future request using an Authentication Data option. Application data is not subject to any encryption negotiated during this phase. Descriptions of such negotiations are beyond the scope of this memo. When the negotiation is complete (either successfully or unsuccessfully), the proxy sends a second Authentication Reply. The second Authentication Reply MUST NOT allow for further negotiations.

After the authentication negotiations are complete, the proxy sends an Operation Reply:

Version: 6 Reply Code: 0x00: Succes 0x01: General SOCKS server failure 0x02: Connection not allowed by ruleset 0x03: Network unreachable 0x04: Host unreachable 0x05: Connection refused 0x06: TTL expired 0x07: Command not supported 0x08: Address type not supported 0x09: Connection attempt timed out Bind Port: the proxy bound port in network byte order. Padding: set to 0 Address Type: 0x01: IPv4 0x03: Domain Name 0x04: IPv6 Bind Address: the proxy bound address in the following format: IPv4: a 4-byte IPv4 address Domain Name: one byte that contains the length of the FQDN, followed by the FQDN itself. The string is not NUL-terminated, but padded by NUL characters, if needed. IPv6: a 16-byte IPv6 address Options Length: the total size of the SOCKS options that appear in the Options field. MUST NOT exceed 16KB. Options: see . Proxy implementations MAY support any subset of the client commands listed in . If the proxy returns a reply code other than “Success”, the client MUST close the connection. If the client issued an NOOP command, the client MUST close the connection after receiving the Operation Reply.

In case the client has issued a CONNECT request, data can now pass.

In case the client has issued a BIND request, it must wait for a second Operation reply from the proxy, which signifies that a host has connected to the bound port. The Bind Address and Bind Port fields contain the address and port of the connecting host. Afterwards, application data may pass.

Proxies offering UDP functionality must be configured with a UDP port used for relaying UDP datagrams to and from the client, and/or a port used for relaying datagrams over DTLS. Following a successful Operation Reply, the proxy sends a UDP Association Initialization message:

Association ID: the identifier of the UDP association Proxy implementations SHOULD generate Association IDs randomly or pseudo-randomly. Clients may start sending UDP datagrams to the proxy either in plaintext, or over an established DTLS session, using the proxy’s configured UDP ports. A client’s datagrams are prefixed by a SOCKS Datagram Header, indicating the remote host’s address and port:

Version: 0x06 Association ID: the identifier of the UDP association Address Type: 0x01: IPv4 0x03: Domain Name 0x04: IPv6 Address: this field’s format depends on the address type: IPv4: a 4-byte IPv4 address Domain Name: one byte that contains the length of the FQDN, followed by the FQDN itself. The string is not NUL-terminated. IPv6: a 16-byte IPv6 address Port: the port in network byte order. Following the receipt of the first datagram from the client, the proxy makes a one-way mapping between the Association ID and: the 5-tuple of the UDP conversation, if the datagram was received over plain UDP, or the DTLS connection, if the datagram was received over DTLS. The DTLS connection is identified either by its 5-tuple, or some other mechanism, like . Further datagrams carrying the same Association ID, but not matching the established mapping, are silently dropped. The proxy then sends an UDP Association Confirmation message over the TCP connection with the client:

Status: MUST be 0x00 Following the confirmation message, UDP packets bound for the proxy’s bind address and port are relayed to the client, also prefixed by a Datagram Header. The UDP association remains active for as long as the TCP connection between the client and the proxy is kept open.

Under some circumstances (e.g. when hosting a server), the SOCKS client expects the remote host to send UDP datagrams first. As such, the SOCKS client must trigger a UDP Association Confirmation without having the proxy relay any datagrams on its behalf. To that end, it sends an empty datagram prefixed by a Datagram Header with an IP address and port consisting of zeroes. The client SHOULD resend the empty datagram if an UDP Association Confirmation is not received after a timeout.

The use of multicast addessses is permitted for UDP traffic only.

SOCKS options have the following format:

Kind: Allocated by IANA. (See .) Length: The total length of the option. MUST be a multiple of 4. Option Data: The contents are specific to each option kind. Unless otherwise noted, client and proxy implementations MAY omit supporting any of the options described in this document. Upon encountering an unsupported option, a SOCKS endpoint MUST silently ignore it.

Stack options can be used by clients to alter the behavior of the protocols on top of which SOCKS is running, as well the protcols used by the proxy to communicate with the remote host (i.e. IP, TCP, UDP). A Stack option can affect either the proxy’s protocol on the client-proxy leg or on the proxy-remote leg. Clients can only place Stack options inside SOCKS Requests. Proxies MAY choose not to honor any Stack options sent by the client. Proxies include Stack options in their Operation Replies to signal their behavior, and MUST do so for every supported Stack option sent by the client. Said options MAY also be unsolicited, i. e. the proxy MAY send them to signal behaviour that was not explicitly requested by the client. If a particular Stack option is unsupported, the proxy MUST silently ignore it. In case of UDP ASSOCIATE, the stack options refer to the UDP traffic relayed by the proxy. Stack options that are part of the same message MUST NOT contradict one another or contain duplicate information.

Leg: 1: Client-Proxy Leg 2: Proxy-Remote Leg 3: Both Legs Level: 1: IP: options that apply to either IPv4 or IPv6 2: IPv4 3: IPv6 4: TCP 5: UDP Code: Option code Option Data: Option-specific data

TOS: The IP TOS code The client can use IP TOS options to request that the proxy use a certain value for the IP TOS field. Likewise, the proxy can use IP TOS options to advertise the TOS values being used.

This memo provides enough features for clients to implement a mechanism analogous to Happy Eyeballs over SOCKS. However, when the delay between the client and the proxy, or the proxy’s vantage point, is high, doing so can become impractical or inefficient. In such cases, the client can instruct the proxy to employ the Happy Eyeballs technique on its behalf when connecting to a remote host. The client MUST supply a Domain Name as part of its Request. Otherwise, the proxy MUST silently ignore the option. TODO: Figure out which knobs to include.

Payload Size: The desired payload size of the TFO SYN. Ignored in case of a BIND command. If a SOCKS Request contains a TFO option, the proxy SHOULD attempt to use TFO in case of a CONNECT command, or accept TFO in case of a BIND command. Otherwise, the proxy MUST NOT attempt to use TFO in case of a CONNECT command, or accept TFO in case of a BIND command. In case of a CONNECT command, the client can indicate the desired payload size of the SYN. If the field is 0, the proxy can use an arbitrary payload size. If the field is non-zero, the proxy MUST NOT use a payload size larger than the one indicated. The proxy MAY use a smaller payload size than the one indicated.

In case of a CONNECT or BIND command, the client can inform the proxy whether MPTCP is desired on the proxy-remote leg by sending a Multipath option. Conversely, the proxy can use a Multipath option to convey the following information: * whether or not the connection uses MPTCP or not, when replying to a CONNECT command, or in the second Operation reply to a BIND command, or * whether an MPTCP connection will be accepted, when first replying to a BIND command.

Availability: 0x01: MPTCP is not desired or available 0x02: MPTCP is desired or available In the absence of such an option, the proxy SHOULD NOT enable MPTCP.

Backlog: The length of the listen backlog. The default behavior of the BIND does not allow a client to simultaneously handle multiple connections to the same bind address. A client can alter BIND’s behavior by adding a TCP Listen Backlog Option to a BIND Request, provided that the Request is part of a Session. In response, the proxy sends a TCP Listen Backlog Option as part of the Operation Reply, with the Backlog field signalling the actual backlog used. The proxy SHOULD NOT use a backlog longer than requested. Following the successful negotiation of a backlog, the proxy listens for incoming connections for as long as the initial connection stays open. The initial connection is not used to relay data between the client and a remote host. To accept connections, the client issues further BIND Requests using the bind address and port supplied by the proxy in the initial Operation Reply. Said BIND requests must belong to the same Session as the original Request. If no backlog is issued, the proxy signals a backlog length of 0, and BIND’s behavior remains unaffected.

A client that is willing to go through the authentication phase MUST include an Authentication Method Advertisement option in its Request. In case of a CONNECT Request, the option is also used to specify the amount of initial data supplied before any method-specific authentication negotiations take place.

Initial Data Size: A two-byte number in network byte order. In case of CONNECT, this is the number of bytes of initial data that are supplied by the client immediately following the Request. This number MUST NOT be larger than 2^14. Methods: One byte per advertised method. Method numbers are assigned by IANA. Padding: A minimally-sized sequence of zeroes, such that the option length is a multiple of 4. Note that 0 coincides with the value for “No Authentication Required”. Clients MUST support the “No authentication required” method. Clients SHOULD omit advertising the “No authentication required” option. The proxy indicates which authentication method must proceed by sending an Authentication Method Selection option in the corresponding Authentication Reply:

Method: The selected method. If the proxy selects “No Acceptable Methods”, the client MUST close the connection. If authentication is successful via some other means, or not required at all, the proxy silently ignores the Authentication Method Advertisement option.

Authentication Data options carry method-specific authentication data. They can be part of SOCKS Requests and Authentication Replies. Authentication Data options have the following format:

Method: The number of the authentication method. These numbers are assigned by IANA. Authentication Data: The contents are specific to each method. Clients MUST only place one Authentication Data option per authentication method.

Clients and proxies can establish SOCKS sessions, which span one or more Requests. All session-related negotiations are done via Session Options, which are placed in Requests and Authentication Replies by the client and, respectively, by the proxy. Client and proxy implementations MUST either support all Session Option Types, or none.

A client can initiate a session by sending a Session Request Option:

The proxy then replies with a Session ID Option in the successful Operation Reply:

Session ID: An opaque sequence of bytes specific to the session. The size MUST be a multiple of 4. MUST NOT be empty. The Session ID serves to identify the session and is opaque to the client. The credentials, or lack thereof, used to initiate the session are tied to the session. If authentication is to be performed for further Requests, the session is deemed “untrusted”, and the proxy also places a Session Untrusted option in the Authentication Reply:

The SOCKS Request that initiated the session is considered part of the session. A client MUST NOT attempt to initiate a session from within a different session. If the proxy can not or will not honor the Session Request, it does so silently.

Any further SOCKS Requests that are part of the session MUST include a Session ID Option (as seen in ). The authentication procedure is altered based on the Session ID’s validity and whether or not the Session is untrusted. For valid Session IDs: If the session is untrusted, the proxy MUST reject clients that do not authenticate using the same method and credentials that were used to initiate the session. Otherwise, the proxy MUST silently ignore any authentication attempt in the Request, and MUST NOT require any authentication. The proxy then replies by placing a Session OK option in the successful Authentication Reply:

If the ticket is invalid, the first Authentication Reply MUST signal that authentication failed and can not continue (by setting the Type field to 0x01). Further, it SHALL contain a Session Invalid option:

Proxies can, at their discretion, tear down a session and free all associated state. Proxy implementations SHOULD feature a timeout mechanism that destroys sessions after a period of inactivity. When a session is terminated, the proxy MAY close all connections associated with said session. Clients can signal that a session is no longer needed, and can be torn down, by sending a Session Teardown option in addition to the Session ID option:

After sending such an option, the client MUST assume that the session is no longer valid. The proxy MUST treat the connection-terminating request as if it were not part of any session.

To protect against duplicate SOCKS Requests, clients can request, and then spend, idempotence tokens. A token can only be spent on a single SOCKS request. Tokens are 4-byte unsigned integers in a modular 4-byte space. Therefore, if x and y are tokens, x is less than y if 0 < (y - x) < 2^31 in unsigned 32-bit arithmetic. Proxies grant contiguous ranges of tokens called token windows. Token windows are defined by their base (the first token in the range) and size. All token-related operations are done via Idempotence options. Idempotence options are only valid in the context of a SOCKS Session. If a SOCKS Request is not part of a Session (either by supplying a valid Session ID or successfully initiating one via a Session Request), the proxy MUST silently ignore any Idempotence options. Token windows are tracked by the proxy on a per-session basis. There can be at most one token window for every session and its tokens can only be spent from within said session. Client and proxy implementations MUST either support all Idempotence Option Types, or none.

A client can obtain a window of tokens by sending an Idempotence Request option as part of a SOCKS Request:

Window Size: The requested window size. Once a token window is issued, the proxy MUST include an Idempotence Window option in all subsequent successful Authentication Replies:

Window Base: The first token in the window. Window Size: The window size. This value MAY differ from the requested window size. Window sizes MUST be less than 2^31. Window sizes MUST NOT be 0. If no token window is issued, the proxy MUST silently ignore the Token Request. If there is already a token window associated with the session, the proxy MUST NOT issue a new window.

The client can attempt to spend a token by including a Idempotence Expenditure option in its SOCKS request:

Kind: 13 (Idempotence Expenditure option) Length: 8 Token: The token being spent. Clients SHOULD prioritize spending the smaller tokens. The proxy responds by sending either an Idempotence Accepted or Rejected option as part of the Authentication Reply:

If eligible, the token is spent before attempting to honor the Request. If the token is not eligible for spending, the Authentication Reply MUST indicate failure.

Windows can be shifted (i. e. have their base increased, while retaining their size) unilaterally by the proxy. Proxy implementations SHOULD shift the window: * as soon as the lowest-order token in the window is spent and * when a sufficiently high-order token is spent. Proxy implementations SHOULD NOT shift the window’s base beyond the highest unspent token.

Even though the proxy increases the window’s base monotonically, there is no mechanism whereby a SOCKS client can receive the Token Window Advertisements in order. As such, clients SHOULD disregard Token Window Advertisements with a Window Base less than the previously known value.

Username/Password authentication is carried out as in . Clients can also attempt to authenticate by placing the Username/Password request in an Authentication Data Option.

Username/Password Request: The Username/Password Request, as described in . Proxies reply by including a Authentication Data Option in the next Authentication Reply which contains the Username/Password reply:

Username/Password Reply: The Username/Password Reply, as described in .

TFO breaks TCP semantics, causing replays of the data in the SYN’s payload under certain rare circumstances . A replayed SOCKS Request could itself result in a replayed connection on behalf of the client. As such, client implementations SHOULD NOT use TFO on the client-proxy leg unless: The protocol running on top of SOCKS tolerates the risks of TFO, or The SYN’s payload does not contain any application data (so that no data is replayed to the server, even though duplicate connections are still possible), or The client uses Idempotence Options, making replays very unlikely, or SOCKS is running on top of TLS and Early Data is not used.

In case of CONNECT Requests, the client MAY start sending application data as soon as possible, as long as doing so does not incur the risk of breaking the SOCKS protocol. Clients must work around the authentication phase by doing any of the following: If the Request does not contain an Authentication Method Advertisement option, the authentication phase is guaranteed not to happen. In this case, application data MAY be sent immediately after the Request. Application data MAY be sent immediately after receiving an Authentication Reply indicating success. When performing a method-specific authentication sequence, application data MAY be sent immediately after the last client message.

Clients may require information typically obtained from DNS servers, albeit from the proxy’s vantage point. While the CONNECT command can work with domain names, some clients’ workflows require that addresses be resolved as a separate step prior to connecting. Moreover, the SOCKS Datagram Header, as described in , can be reduced in size by providing the resolved destination IP address, rather than the FQDN. Emerging techniques may also make use of DNS to deliver server-specific information to clients. For example, Encrypted SNI relies on DNS to publish encryption keys. Proxy implementations MAY provide a default plaintext DNS service. A client looking to make use of it issues a CONNECT Request to IP address 0.0.0.0 or 0:0:0:0:0:0:0:0 on port 53. Following successful authentication, the Operation Reply indicates an unspecified bind address (0.0.0.0 or ::) and port (0). The client and proxy then behave as per . The service itself can be provided directly by the proxy daemon, or by proxying the client’s request to a pre-configured DNS server. If the proxy does not implement such functionality, it MAY return an error code signalling “Connection refused”.

Given the format of the request message, a malicious client could craft a request that is in excess of 16 KB and proxies could be prone to DDoS attacks. To mitigate such attacks, proxy implementations SHOULD be able to incrementally parse the requests. Proxies MAY close the connection to the client if: the request is not fully received after a certain timeout, or the number of options or their size exceeds an imposed hard cap.

In TLS 1.3, early data (which is likely to contain a full SOCKS request) is prone to replay attacks. While Token Expenditure options can be used to mitigate replay attacks, anything prior to the initial Token Request is still vulnerable. As such, client implementations SHOULD NOT make use of TLS early data unless the Request attempts to spend a token.

Malicious clients can issue a large number of Session Requests, forcing the proxy to keep large amounts of state. To mitigate this, the proxy MAY implement policies restricting the number of concurrent sessions on a per-IP or per-user basis, or barring unauthenticated clients from establishing sessions.

This document requests that IANA allocate 2-byte option kinds for SOCKS 6 options. Further, this document requests the following option kinds: Unassigned: 0 Stack: 1 Authentication Method Advertisement: 2 Authentication Method Selection: 3 Authentication Data: 4 Session Request: 5 Session ID: 6 Session Untrusted: 7 Session OK: 8 Session Invalid: 9 Session Teardown: 10 Idempotence Request: 11 Idempotence Window: 12 Idempotence Expenditure: 13 Idempotence Accepted: 14 Idempotence Rejected: 15 Resolution Request: 16 IPv4 Resolution: 17 IPv6 Resolution: 18 Vendor-specific: 64512-0xFFFF This document also requests that IANA allocate a TCP and UDP port for SOCKS over TLS and DTLS, respectively.

The protocol described in this draft builds upon and is a direct continuation of SOCKS 5 .