On Friday 25 July 2008 19:43, Russell Coker wrote: > Package: postfix-policyd-spf-perl > Version: 2.005-2 > Severity: normal > > http://www.rfc.net/rfc2606.txt > > RFC 2606 describes the use of example.com and similar domains. Instead of > using some.domain.tld in the man page it should use official example > domains. > > The example in the man pages uses three domains, they could be replaced > with example.com, example.net, and example.org to give a result that will > never cause unexpected results if used on the net and which I believe will > more clearly convey the intent of the example.
SInce .tld (the tld used in the documentation) does not actually exist, there is no potential for harm. RFC 2606 is an IETF BCP and not an actual standard of any kind. The example in the man page is from the original upstream documentation and has been distributed this way for years, including being shipped with the Postfix source for several releases. I don't think changing these would provide any meaningful benifit and would create divergence from upstream. This topic recently came up on the IETF main list in a slightly different context: http://www.ietf.org/mail-archive/web/ietf/current/msg51960.html If I were writing documenation from scratch, I might use such domains, but I think that they are, if anything less clear than the current examples. > http://www.rfc.net/rfc3330.html > > Also the IP address 1.2.3.4 should not be used. I suggest using one of > the private address ranges from RFC 3330 (10.0.0.0/8 is the most popular). RFC 3330 is informational and not a standard of any kind. Since the IP addess used in the example does not and can not cause any network traffic related to the IP number, I don't see any point in changing it. Using a private address actually has potential for confusion here because people new to SPF sometimes put their private addresses in their SPF records thinking they need to do so. Using it in the example would re-inforce that belief. At this point, I'm inclined to won't fix this bug, but I'll wait and see if you have any more compelling points to make. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
