Specify a potential TLS-replacing protocol for future use in Tor.

We should wrap up the design stuff on v0 of "tentp", and rename it.

changed milestone to %Tor: unspecified

added SponsorZ component::core tor/tor milestone::Tor: unspecified needs-proposal points::large priority::medium severity::normal spec sponsor3-maybe status::new type::defect version::tor 0.2.7 labels

Worth looking at during 0.2.7 triage IMO

Trac:
Milestone: Tor: unspecified to Tor: 0.2.7.x-final

Trac:
Status: new to assigned

Marking more tickets as triaged-in for 0.2.7

Trac:
Keywords: N/A deleted, 027-triaged-1-in added

Trac:
Version: N/A to Tor: 0.2.7
Points: N/A to large

Trac:
Milestone: Tor: 0.2.7.x-final to Tor: 0.2.8.x-final

These

Trac:
Milestone: Tor: 0.2.8.x-final to Tor: 0.2.???

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

Trac:
Milestone: Tor: 0.3.??? to Tor: unspecified
Keywords: N/A deleted, tor-03-unspecified-201612 added

Remove an old triaging keyword.

Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added

Trac:
Keywords: N/A deleted, 027-triaged-in added

Trac:
Keywords: 027-triaged-in deleted, N/A added

Trac:
Keywords: 027-triaged-1-in deleted, N/A added

Change the status of all assigned/accepted Tor tickets with owner="" to "new".

Trac:
Status: assigned to new

Trac:
Keywords: spec deleted, spec sponsor3-maybe added
Reviewer: N/A to N/A
Sponsor: N/A to N/A
Severity: N/A to Normal

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