From 285cf93e702b558e95294d9c0276eee8e7e9e616 Mon Sep 17 00:00:00 2001 From: Ian Jackson Date: Tue, 5 Mar 2024 18:27:57 +0000 Subject: Discuss the weirdness with two lots of INTRODUCE extensions --- spec/rend-spec/introduction-protocol.md | 15 +++++++++++++-- 1 file 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 -- cgit v1.2.3-54-g00ecf