Make sure RSOS is documented in specifications

We merged the rend-spec implementation, but we haven't marked the proposal closed. What does it add that isn't documented in rend-spec / dir-spec now? We should make sure to document that, to keep our specs up to date, and mark proposal 260 as closed.

changed milestone to %Tor: 0.3.1.x-final

added component::core tor/tor milestone::Tor: 0.3.1.x-final parent::21554 priority::high prop224 resolution::implemented severity::normal single-onion status::closed type::defect labels

Trac:
Milestone: Tor: 0.3.0.x-final to Tor: 0.3.1.x-final

Trac:
Owner: N/A to teor
Status: new to assigned

Teor is pretty sure that there aren't any undocumented changes from prop260. All that's left to do is scan through the proposal and confirm, then mark the proposal closed.

Trac:
Owner: teor to N/A

There are no dir-spec changes for single onion services.

prop#224 contains an onion service descriptor entry for single onion services in the encrypted section, that belongs in rend-spec. Let's explain single onion services there when we merge prop#224 into rend-spec:

Single onion services connect directly to introduction and rendezvous points. They use a 3-hop path to connect to HSDirs, to avoid malicious HSDirs rejecting descriptors by service IP address.

We could even add this to rend-spec now if we wanted to, but that would duplicate the info once prop224 merges.

Trac:
Keywords: N/A deleted, single-onion, rsos, prop224 added

Trac:
Status: assigned to merge_ready

Now there's only one kind of single onion service, remove all references to old rsos tag

Trac:
Keywords: rsos deleted, N/A added

Trac:
Status: merge_ready to closed
Resolution: N/A to implemented

closed

moved to tpo/core/tor#22277 (closed)