On Sun, Aug 28, 2005 at 01:22:07AM -0700,
SM <sm(_at_)resistor(_dot_)net> wrote
a message of 32 lines which said:
Although some information in RFC 1032 is dated, it remains useful
and is still widely used as a guide for troubleshooting technical
issues.
You must be kidding.
The reasons for moving RFC 1032 from status UNKNOWN to status
HISTORIC are light.
It is already historic and most information in it is plainly wrong:
Reporting-MTA: dns; mx2.nic.fr
Arrival-Date: Mon, 29 Aug 2005 11:42:56 +0200 (CEST)
Final-Recipient: rfc822; HOSTMASTER(_at_)SRI-NIC(_dot_)ARPA
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Postfix; [sri-nic.arpa]: Name or service not known
The rest, as mentioned by Harald Alverstrand, is just policy
requirments (and bad ones) which are NOT IETF business.
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf