aboutsummaryrefslogtreecommitdiff
path: root/spec/rend-spec/introduction-protocol.md
diff options
context:
space:
mode:
Diffstat (limited to 'spec/rend-spec/introduction-protocol.md')
-rw-r--r--spec/rend-spec/introduction-protocol.md15
1 files changed, 13 insertions, 2 deletions
diff --git a/spec/rend-spec/introduction-protocol.md b/spec/rend-spec/introduction-protocol.md
index 02ed828..5016347 100644
--- a/spec/rend-spec/introduction-protocol.md
+++ b/spec/rend-spec/introduction-protocol.md
@@ -463,10 +463,21 @@ will have:
The same rules for multiplicity, ordering, and handling unknown types
apply to the extension fields here as described \[EST_INTRO\] above.
-### INTRODUCE1 Extensions
+### INTRODUCE1/INTRODUCE2 Extensions
The following sections details the currently supported or reserved extensions
-of an `INTRODUCE1` message.
+of an `INTRODUCE1`/`INTRODUCE2` message.
+
+Note that there are two sets of extensions in `INTRODUCE1`/`INTRODUCE2`:
+one in the top-level, unencrypted portion,
+and one within the plaintext of ENCRYPTED.
+
+The sets of extensions allowed in each part of the message are disjoint:
+each extension is valid in only *one* of the two places.
+
+Nevertheless, for historical reasons,
+both kinds of extension are listed in this section,
+and the use nonoverlapping values of `EXT_FIELD_TYPE`.
#### Congestion Control