aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorIan Jackson <ijackson@chiark.greenend.org.uk>2024-03-05 18:29:49 +0000
committerIan Jackson <ijackson@chiark.greenend.org.uk>2024-03-05 18:31:25 +0000
commita2d4549a8d76bfede8ee093ab446229b69b06229 (patch)
treec6a3b843f2f88caf5c2658cf6ea6bfe2bf413c40
parent285cf93e702b558e95294d9c0276eee8e7e9e616 (diff)
downloadtorspec-a2d4549a8d76bfede8ee093ab446229b69b06229.tar.gz
torspec-a2d4549a8d76bfede8ee093ab446229b69b06229.zip
Remove duplicated statement about unknown extensions
This sentence seems stray in this section. The information is alreayd present with the wording The same rules for multiplicity, ordering, and handling unknown types apply to the extension fields here as described \[EST_INTRO\] above. which appears earlier, for each of the two sections.
-rw-r--r--spec/rend-spec/introduction-protocol.md2
1 files changed, 0 insertions, 2 deletions
diff --git a/spec/rend-spec/introduction-protocol.md b/spec/rend-spec/introduction-protocol.md
index 5016347..9b9c5b0 100644
--- a/spec/rend-spec/introduction-protocol.md
+++ b/spec/rend-spec/introduction-protocol.md
@@ -494,8 +494,6 @@ ntorv3, if the service did not list "2" in the `FlowCtrl` line in the
descriptor. The client SHOULD NOT provide this field if the consensus parameter
'cc_alg' is 0.
-The service MUST ignore any unknown fields.
-
#### Proof-of-Work (PoW) {#INTRO1_POW_EXT}
This extension can be used to optionally attach a proof of work to the introduction request.