Back to matrix

L01-TS: Yes

Rationale

A licensed protocol-definition path is available in the pinned sources, rather than relying on permission to reuse website prose. BSD-3-Clause notices cover tailcfg registration/map schemas, controlclient registration and map exchanges, controlhttp/controlbase transport and handshake definitions, discovery framing, DERP frames and flow, and Tailnet Lock authority updates, signatures, synchronization and RPC schemas in tka and tailcfg/tka.go. These embedded definitions can be used and adapted commercially with the stated notices. The selected WireGuard dependency is pinned by go.mod and provides its message/handshake definitions under MIT; Noise section 16 dedicates its specification to the public domain. IP, UDP, TCP, HTTP, TLS, JSON and CBOR use IETF implementation permissions. Enrollment exposes an AuthURL/follow-up boundary: the external identity provider remains external, rather than requiring reproduction of its private business logic. OpenID Connect separately grants implementation use in Appendix C; it is not asserted to be the only provider supported. This establishes L01 at the documented protocol-interface level using the same source-embedded-definition approach accepted elsewhere in the matrix.

Assessment method

Pinned embedded protocol definitions and applicable grants; documentary inference

Source context

Tailscale BSD definitions, selected WireGuard MIT source, Noise IPR, IETF TLP and OpenID notices

Outstanding qualification

Preserve BSD copyright, conditions and disclaimer; retain MIT notices in covered copies; follow applicable IETF/OpenID attribution and code-component notices. No endorsement or compatibility follows from modification. This finding does not license separately published website prose, disclose the proprietary managed coordinator, grant access to any hosted service or IdP, or establish patent clearance (L02). The selected managed-control/Tailnet-Lock profile is unchanged; Headscale is not substituted. Source definitions establish a rights path, not a completeness/interoperability certification for every managed-product feature. No account, runtime test or service benchmark was used. Documentary classification, not legal clearance.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.