From 2cad4d69b899ebcf7391ddcd5a21cd2115baee67 Mon Sep 17 00:00:00 2001 From: Nick Mathewson Date: Thu, 14 Dec 2023 13:17:32 -0500 Subject: Rephrase OtherAddr/own-addr text --- spec/tor-spec/negotiating-channels.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/spec/tor-spec/negotiating-channels.md b/spec/tor-spec/negotiating-channels.md index 01a22d1..e503ece 100644 --- a/spec/tor-spec/negotiating-channels.md +++ b/spec/tor-spec/negotiating-channels.md @@ -469,20 +469,22 @@ and 16 when ATYPE is 0x06 (IPv6). If the ALEN value is wrong for the given ATYPE value, then the provided address should be ignored. -When sending `OTHERADDR`, -implementations SHOULD use the actual IP address -they have observed for the other party. +The `OTHERADDR` field SHOULD be set to the actual IP address +observed for the other party. > (This is typically the address passed to `connect()` > when acting as the channel initiator, > or the address received from `accept()` > when acting as the channel responder.) -When sending the party's own addresses, +When sending the party's own addresses +in the `ATYPE`/`ALEN`/`AVAL` fields, relays SHOULD send the addresses that they have advertised in their router descriptors. Bridges and clients SHOULD send none of their own addresses. +> The OTHERADDR and + For the `TIME` field, relays send a (big-endian) integer holding the number of seconds since the Unix epoch. -- cgit v1.2.3-54-g00ecf