On Tue, 2004-04-27 at 10:51 -0400, Meng Weng Wong wrote:
Here are the changes since Sunday.
* "c" macro introduced; provides human-readable IPv6 notation
* "t" macro limited to use in "exp" text only.
* "r" macro added to indicate receiver domain.
Any objections? Speak now or forever hold your peace...
To §4.5 "mx" consider adding something like:
"If a result of an MX lookup is a string which in violation of RFC1035
appears to be a numeric IPv4 dotted-quad address or IPv6 address rather
than an existent fully qualified domain name, then the mechanism MUST
NOT match that address, even if the erroneously specified IP address
matches the IP address from which the connection originates."
That is, if you get a connection from 1.2.3.4 for 'domain.com' and
'domain.com' has the following erroneous records:
MX 10 1.2.3.4
TXT "v=spf1 mx ?all"
... then the SPF lookup must not match the 'mx' mechanism, but must call
through to result in 'unknown'. MX records must point at _names_ not
numbers, and to accept numbers is wrong.
Also, should you be writing 'an A or AAAA lookup' in place of 'an A
lookup'?
--
dwmw2