pion/dtls: README-based editorial guide

pion/dtls describes itself in the README as "DTLS 1.2 implementation for Go (DTLS 1.3 in progress)". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "README", the README says: Native [DTLS 1.2][rfc6347] implementation in the Go programming language.. That establishes the project's stated boundary, not a production test.

The README's "Implemented" section gives a useful starting point for deciding whether the project fits: RFC 5705: [Keying Material Exporters for Transport Layer Security (TLS)][rfc5705]. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: RFC 6347: [Datagram Transport Layer Security Version 1.2][rfc6347]. It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "README". The source evidence includes: > [!WARNING] > This branch is currently frozen from tagging while DTLS 1.3 work is underway. > > DTLS 1.3 and breaking changes should target the main branch.. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.

Start installation from the README's documented entry point. A command that can be checked in the source is: go run examples/listen/selfsign/main.go When the README contains no runnable command, this article does not invent one. Open its "Implemented" section and confirm system dependencies, default ports, and first-run initialization before using a public server.