On Mon 2019-01-14 22:29:50 -0500, John Levine wrote: > When the ABNF about extended-domain was written with the comment about > info derived from the TCP connection, the TCP connection was > synonymous with the transport. Now the transport is TCP plus STARTTLS > in various versions plus SNI, none of which was contemplated back in > 2001. I think it's reasonable to use extended-domain for info about > the underlying transport, even if the details are not strictly about > TCP. After all, the rDNS name in the FROM extended-domain comes from > a DNS PTR lookup of the IP address which uses IP over UDP so it's > never been strictly about TCP.
I agree with this reasoning -- the TCP-info ABNF doesn't even
contemplate a way to indicate source port, which it would if it was
trying to accurately describe a TCP session in detail specific to TCP.
It's about transport and routing ("how did the inbound MTA get here?"),
so it seems fair game for SNI.
--dkg
signature.asc
Description: PGP signature
_______________________________________________ Uta mailing list [email protected] https://www.ietf.org/mailman/listinfo/uta
