julian at mehnle
Aug 17, 2008, 5:36 AM
Post #1 of 2
(319 views)
Permalink
|
|
RFC 4408 test-suite 2008.08 released
|
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
A new release, 2008.08, of the RFC 4408 test-suite has been finalized:
http://www.openspf.org/Test_Suite
It is recommended that you verify that your implementations still conform
to the updated test-suite, and update them if necessary.
A quote from the changelog (changes since the 2007.05 release):
# Legend:
# --- = A new release
# ! = Added a test case or otherwise tightened a requirement, possibly
# causing implementations to become incompliant with the current
# test-suite release
# - = Removed a test case or otherwise relaxed a requirement
# * = Fixed a bug, or made a minor improvement
- --- 2008.08 (2008-08-17 16:00)
! "invalid-domain-empty-label", "invalid-domain-long",
"invalid-domain-long-via-macro" test cases:
A <target-name> that is a valid domain-spec per RFC 4408 but an invalid
domain name per RFC 1035 (two successive dots or labels longer than 63
characters) must be treated either as a "PermError" or as non-existent and
thus a no-match. (In particular, those cases can never cause a TempError
because the error is guaranteed to reoccur given the same input data.
This applies likewise to RFC-1035-invalid <target-name>s that are the
result of macro expansion.) Refined descriptions and comments to that
end.
The no-match behavior can be inferred by analogy from 4.3/1 and 5/10/3.
The spec reference to 8.1/2 is bogus because the formal grammar does not
preclude such invalid domain names.
! The "exp= without domain-spec" controversy has been resolved; it must be a
syntax error. Tightened "exp-empty-domain" test case accordingly.
! Added test cases:
! "a-dash-in-toplabel":
<toplabel> may contain dashes. Implementations matching <toplabel>
non-greedily may get that wrong.
! "a-only-toplabel", "a-only-toplabel-trailing-dot":
Both "a:museum" and "a:museum." are invalid syntax. A bare top-label is
insufficient, with or without a trailing dot.
! "exp-no-txt", "exp-dns-error":
Clearly, "exp=" referring to a non-existent TXT RR, or the look-up
resulting in a DNS error, must cause the "exp=" modifier to be ignored per
6.2/4.
! "macro-mania-in-domain":
Test macro-encoded percents (%%), spaces (%_), and URL-percent-encoded
spaces (%20) in <domain-spec>.
! "macro-reverse-split-on-dash":
Test transformation of macro expansion results: splitting on non-dot
separator characters, reversal, number of right-hand parts to use.
- Removed "a-valid-syntax-but-unqueryable" test case. It is redundant to
the "invalid-domain-empty-label" test case.
- Relaxed "multispf1" test case:
If performed via live DNS (yes, some people do that!), this test may be
ineffective as DNS resolvers may combine multiple identical RRs. Thus,
tolerate the test failing in this manner.
* Adjusted "multispf2" test case:
Avoid combination of multiple identical RRs by using different
capitalization in intentionally duplicate RRs.
* Renamed test cases:
a-numeric-top-label -> a-numeric-toplabel
a-bad-toplab -> a-bad-toplabel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkioG2UACgkQwL7PKlBZWjsH7QCeKgchvwAFYQYpgyCKnXNojqhI
x5UAn0K7qpRJbZ4CAHINF7/4p5wy4b+0
=auCa
-----END PGP SIGNATURE-----
-------------------------------------------
Sender Policy Framework: http://www.openspf.org
Modify Your Subscription: http://www.listbox.com/member/
Archives: https://www.listbox.com/member/archive/1007/=now
RSS Feed: https://www.listbox.com/member/archive/rss/1007/
Powered by Listbox: http://www.listbox.com
|
