diff options
Diffstat (limited to 'spec/tor-spec')
| -rw-r--r-- | spec/tor-spec/channels.md | 2 | ||||
| -rw-r--r-- | spec/tor-spec/create-created-cells.md | 2 | ||||
| -rw-r--r-- | spec/tor-spec/flow-control.md | 2 | ||||
| -rw-r--r-- | spec/tor-spec/negotiating-channels.md | 4 | ||||
| -rw-r--r-- | spec/tor-spec/subprotocol-versioning.md | 2 |
5 files changed, 6 insertions, 6 deletions
diff --git a/spec/tor-spec/channels.md b/spec/tor-spec/channels.md index 5b0020a..046181b 100644 --- a/spec/tor-spec/channels.md +++ b/spec/tor-spec/channels.md @@ -33,7 +33,7 @@ whereas clients and bridges SHOULD NOT do so. Parties should usually reuse an existing channel rather than opening new a channel to the same relay. There are exceptions here; -we discuss them more [below](#XXXX). +we discuss them more below. <!-- TODO: add anchor link --> To open a channel, a client or relay must know the IP address and port diff --git a/spec/tor-spec/create-created-cells.md b/spec/tor-spec/create-created-cells.md index 1e6281c..965cad1 100644 --- a/spec/tor-spec/create-created-cells.md +++ b/spec/tor-spec/create-created-cells.md @@ -191,7 +191,7 @@ of each type. After checking relay identities, extending ORs generate a CREATE/CREATE2 cell from the contents of the EXTEND/EXTEND2 cell. -See [Creating circuits](./#creating-circuits.md#creating-circuits) +See [Creating circuits](./creating-circuits.md#creating-circuits) for details. The payload of an EXTENDED cell is the same as the payload of a diff --git a/spec/tor-spec/flow-control.md b/spec/tor-spec/flow-control.md index bf1abe2..91c04e3 100644 --- a/spec/tor-spec/flow-control.md +++ b/spec/tor-spec/flow-control.md @@ -33,7 +33,7 @@ information. See proposal 111 for details. Link padding can be created by sending PADDING or VPADDING cells along the connection; relay cells of type "DROP" can be used for long-range padding. The payloads of PADDING, VPADDING, or DROP -cells are filled with padding bytes. See [Cell Packet format](./cell-packet-format#cell-packet-format). +cells are filled with padding bytes. See [Cell Packet format](./cell-packet-format.md#cell-packet-format). If the link protocol is version 5 or higher, link level padding is enabled as per padding-spec.txt. On these connections, clients may diff --git a/spec/tor-spec/negotiating-channels.md b/spec/tor-spec/negotiating-channels.md index 2501d7f..c328e12 100644 --- a/spec/tor-spec/negotiating-channels.md +++ b/spec/tor-spec/negotiating-channels.md @@ -10,7 +10,7 @@ which we describe in [another section](./obsolete-channels.md). In brief: - The initiator starts the handshake by [opening a TLS connection](#tls). - - Both parties send a [VERSIONS](#VERSIONS-cell) + - Both parties send a [VERSIONS](#VERSIONS-cells) to negotiate the protocol version to use. - The responder sends a [CERTS cell](#CERTS-cells) to give the @@ -145,7 +145,7 @@ Relevant certType values are: | 7 | Ed25519 identity, signed with RSA identity. The certificate format for certificate types 1-3 is DER encoded X509. -For others, the format is as documented in [a later section](./cert-spec.md) +For others, the format is as documented in [a later section](../cert-spec.md) Note that type 7 uses a different format from types 4-6. diff --git a/spec/tor-spec/subprotocol-versioning.md b/spec/tor-spec/subprotocol-versioning.md index 97c4409..780a337 100644 --- a/spec/tor-spec/subprotocol-versioning.md +++ b/spec/tor-spec/subprotocol-versioning.md @@ -295,7 +295,7 @@ Describes the communications mechanisms used to bundle circuits together, in order to split traffic across multiple paths. > TODO: This is not yet described here. For details see -> [Proposal 329](../proposals/329). +> [Proposal 329](../proposals/329-traffic-splitting.txt). <a id="tor-spec.txt-9.13"></a> |