v3 Onion Services: Put IPv6 and unrecognised link specifiers in onion service EXTEND cells

Prop224 says:

The hidden service SHOULD NOT reject any LSTYPE fields which it
doesn't recognize; instead, it should use them verbatim in its EXTEND
request to the rendezvous point.

https://gitweb.torproject.org/torspec.git/tree/proposals/224-rend-spec-ng.txt#n1689

We should either remove this from the spec, or we should:

• add a similar sentence for client descriptor lspecs
• put unrecognised lspecs in descriptors in client intro EXTEND requests
• put unrecognised lspecs in INTRODUCE cells in service rend EXTEND requests

changed milestone to %Tor: unspecified

added 034-removed-20180328 034-triage-20180328 component::core tor/tor ipv6 milestone::Tor: unspecified parent::24403 points::3 priority::medium prop224 severity::normal single-onion status::new tor-hs type::defect version::tor 0.3.2.1-alpha labels

We should also put IPv6 addresses in EXTEND cell link specifiers, even if current relays won't use them.

Do we need to do this for CREATE cells as well? I don't think so, because we're the ones connecting.

This needs to be done in the same release as #24451 (moved), to avoid introducing a v3 onion service distinguisher.

Trac:
Summary: Put unrecognised link specifiers in onion service EXTEND cells to Put IPv6 and unrecognised link specifiers in onion service EXTEND cells

Trac:
Status: new to accepted
Owner: N/A to dgoulet

Move 033 ticket I own to 034

Trac:
Milestone: Tor: 0.3.3.x-final to Tor: 0.3.4.x-final

Trac:
Keywords: N/A deleted, 034-triage-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

Trac:
Keywords: N/A deleted, 034-removed-20180328 added

These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.

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

Replying to teor:

Prop224 says: {{{ The hidden service SHOULD NOT reject any LSTYPE fields which it doesn't recognize; instead, it should use them verbatim in its EXTEND request to the rendezvous point. }}} https://gitweb.torproject.org/torspec.git/tree/proposals/224-rend-spec-ng.txt#n1689

The latest reference is:

https://gitweb.torproject.org/torspec.git/tree/rend-spec-v3.txt#n1714

... we should:

• add a similar sentence for client descriptor lspecs

I did this spec update in #26925 (moved). It's at:

https://gitweb.torproject.org/torspec.git/tree/rend-spec-v3.txt#n1346

Trac:
Keywords: tor-spec deleted, N/A added

Replying to teor:

Do we need to do this for CREATE cells as well? I don't think so, because we're the ones connecting. I don't see this necessary in this direction.

dgoulet will assign himself to the ones he is working on right now.

Trac:
Owner: dgoulet to N/A
Status: accepted to assigned

Trac:
Summary: Put IPv6 and unrecognised link specifiers in onion service EXTEND cells to v3 Onion Services: Put IPv6 and unrecognised link specifiers in onion service EXTEND cells
Parent: #23493 (moved) to #24403 (moved)

Change tickets that are assigned to nobody to "new".

Trac:
Status: assigned to new

changed time estimate to 24h

mentioned in issue #24451 (moved)

mentioned in issue #26925 (moved)

mentioned in issue #26971 (moved)

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

mentioned in issue tpo/core/tor#24451 (closed)

mentioned in issue tpo/core/tor#26971 (closed)