G02-TS: Yes
Rationale
A changed endpoint locator is reported to the coordinator and distributed in peer-map updates to relevant authorized peers. It need not be announced to every Tailscale participant or as an individual endpoint route in the global Internet.
Assessment method
Primary documentation and pinned source; explicit architectural inference
Source context
Tailscale addressing, control plane, magicsock and tailcfg
Outstanding qualification
Source witness: MapRequest endpoint reporting and MapResponse PeerChange.Endpoints. Scope includes the tailnet control service, relevant peer maps and relay state. Authorized peer sets can be large; this does not establish a small worst-case update fanout or global capacity.
Public sources
- https://tailscale.com/docs/concepts/control-data-planes
- https://tailscale.com/docs/concepts/control-data-planes
- https://tailscale.com/docs/concepts/tailscale-ip-addresses
- https://raw.githubusercontent.com/tailscale/tailscale/566f89e0fb2aa4b2f1ebf98761e45e62aa5ef225/wgengine/magicsock/endpoint.go
- https://raw.githubusercontent.com/tailscale/tailscale/566f89e0fb2aa4b2f1ebf98761e45e62aa5ef225/tailcfg/tailcfg.go
- https://tailscale.com/blog/sqlite-wal-reset-bug
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round591.html
- round591-sources.json