Skip to content

Direct Client-to-Client

Direct Client-to-Client (DCC) (originally Direct Client Connection ) is an IRC-related sub-protocol enabling peers to interconnect using an IRC server for handshaking in order to exchange files or perform non-relayed chats.

Version
v1 · 2026-09-28 · History
Domain-specific #
8994
Domain group
Applied Sciences & Engineering
Origin domain
Computer Science & Software Engineering
Subdomains
Network Protocols, Internet Relay Chat → Computer Science & Software Engineering

Core Idea

Direct Client-to-Client is treated here as the recurring computerscienceandinformation identity summarized by this source-grounded definition: Direct Client-to-Client (DCC) (originally Direct Client Connection ) is an IRC-related sub-protocol enabling peers to interconnect using an IRC server for handshaking in order to exchange files or perform non-relayed chats. Direct Client-to-Client (DCC) (originally Direct Client Connection ) is an IRC-related sub-protocol enabling peers to interconnect using an IRC server for handshaking in order to exchange files or perform non-relayed chats. Once established, a typical DCC session runs independently from the IRC server.

How would you explain it like I'm…

Meet, Then Talk Directly

Imagine a big chat room where everyone talks through a helper in the middle. Two people can use the chat room just to say "let's connect," and then they send files or talk straight to each other without the helper passing every message. That's Direct Client-to-Client.

Chat Room Handshake Link

Direct Client-to-Client, or DCC, is part of IRC, an old system for online chat where messages normally go through a server. DCC lets two users use the IRC server only to set up a connection, like a quick handshake. After that, their computers connect directly to each other to send files or chat privately, without the server passing along their messages. The direct connection keeps working on its own even without the server's help. It started with a program called ircII and is now supported by many chat programs.

IRC Direct Peer Connection

Direct Client-to-Client (DCC), originally called Direct Client Connection, is a sub-protocol related to IRC (Internet Relay Chat). In normal IRC, every message is relayed through a server. With DCC, two clients use the IRC server only for handshaking, exchanging the information needed to connect, and then open a direct peer-to-peer connection to transfer files or chat without relaying. Once set up, the DCC session runs independently of the IRC server. It was first designed for the ircII client and is now supported by many IRC clients, and even some clients on napster-protocol networks. A variant called SDCC (Secure DCC), or DCC SCHAT, adds encryption. Unusually, there is no RFC specification describing DCC.

 

Direct Client-to-Client (DCC; originally Direct Client Connection) is an IRC-related sub-protocol in which two peers use the IRC server solely for handshaking and then establish a direct connection for file exchange or non-relayed chat. After setup, a typical DCC session runs independently of the IRC server, so data no longer passes through the relay. Originating with the ircII client, it is now widely supported by IRC clients, and some napster-protocol peer-to-peer clients (TekNap, SunshineUN, Lopster) also implement DCC send/get. The SDCC (Secure DCC) variant, also called DCC SCHAT, supports encrypted connections. No RFC specifies DCC.

Scope of Application

  • DCC Relay. This method can be used by XDCC channels to fill their XDCC bots from other XDCC channels.

  • Common DCC applicationsDCC CHAT. The CHAT service enables users to chat with each other over a DCC connection.

  • Common DCC applicationsDCC CHAT. Once a connection is established, the protocol used for DCC CHAT is very simple: users exchange CRLF-terminated messages.

  • DCC SEND. It is common practice to add the file size as a last argument: DCC SEND.

  • DCC XMIT. The XMIT service is a modified version of DCC SEND that allows for resuming files and cuts down on wasteful traffic from the ACK longs.

Clarity

A clear use of Direct Client-to-Client names the carrier, the operative relation, and the conditions under which the source treats the identity as present. The minimal definition is Direct Client-to-Client (DCC) (originally Direct Client Connection ) is an IRC-related sub-protocol enabling peers to interconnect using an IRC server for handshaking in order to exchange files or perform non-relayed chats.

Manages Complexity

Direct Client-to-Client compresses multiple computerscienceandinformation details into a stable diagnostic relation. The source shows both the central mechanism—when compared to sending messages normally, this reduces IRC network load, allows sending of larger amounts of text at once, due to the lack of flood control, and makes the communication more secure by not exposing the message to the IRC servers (however, the message is still in plaintext).—and the practical.

Abstract Reasoning

  1. Type the carrier. Identify the computerscienceandinformation entities to which the claim applies.
  2. State the relation. Use the source-grounded identity: Direct Client-to-Client (DCC) (originally Direct Client Connection ) is an IRC-related sub-protocol enabling peers to interconnect using an IRC server for handshaking in order to exchange files or perform non-relayed chats.
  3. Check operation and conditions. The CTCP protocol was implemented by Michael Sandrof in 1990 for ircII version 2.1.
  4. Demand recognition evidence.

Knowledge Transfer

Within the home domain. Knowledge about Direct Client-to-Client transfers literally when a new case preserves the same carrier type, relation, and recognition test. This method can be used by XDCC channels to fill their XDCC bots from other XDCC channels. The CHAT service enables users to chat with each other over a DCC connection. Beyond the home domain. No canonical parent is asserted for Direct Client-to-Client. An outside case receives the specialist name only when the same typed roles and rejection conditions can be filled literally; otherwise the comparison remains an analogy pending later graph densification.

Neighborhood in Abstraction Space

Direct Client-to-Client sits in a sparse region of the domain-specific corpus (85th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Unclustered & Miscellaneous (2551 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-08