--On Tuesday, March 29, 2016 11:45 -0400 "Dale R. Worley"
Here's another ugly little bit of processing: On some
systems, library routines that convert dotted-number IP
address strings into four-octet format treat a component that
starts with "0" as being written in octal. E.g.,
"010.010.010.010" is equivalent to "18.104.22.168". (Try executing
"dig ietf.org @010.010.010.010" on a Linux system.) As far as
I know, this isn't *specified* anywhere in the RFCs, and some
RFCs (e.g., RFC 997) have leading zeros on numbers that
contain "9". So it's worth warning people not to use leading
zeros in IPv4 addresses.
And that comment identifies another ugly little issue. An email
address of email@example.com implies that
"010.010.010.010" is a domain name and "010" (the rightmost
label) is a TLD. Because there is no such TLD (nor is there
one for "8."), such an address is an error, so, if a
mail-related regular expression document pursues that question
at all, it would allow something that violated 5321 no matter
whether 010 is interpreted as "2", "8", "10", "16", STX,
Backspace, DLE, or something else.
I'm not suggesting Sean would do that, only emphasizing (again)
the dangers of developing a second spec (or two specs more
generally) that is inadvertently not quite consistent with the
ietf-smtp mailing list