Re: Last erratum last call

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

First, I apologize for having been AWOL for several months and having
dropped the ball on the test-suite release.  I got overrun by a move and a
new job.

Frank Ellermann wrote:
> Okay, if Julian, Terry, or somebody else doesn't scream I'll try the
> "both okay, and certainly not TempError" approach.
>
> We clearly have consensus for "no TempError", and it is not only rough.

Frank, thanks for writing up the erratum proposal:

  http://www.openspf.org/RFC_4408/Errata?action=browse&diff=1&revision=58&diffrevision=53

I think all of us are mostly on the same page now with regard to the issue
matter.  I do have one concern about the erratum wording, though.  Your
proposal puts all the stuff in the "PermError" definition in section
2.5.7.  I don't think that's appropriate.  How about the attached diff
instead?

In any case I have adjusted the test suite to allow both the "PermError"
and no-match behaviors:

  http://www.openspf.org/source/project/test-suite/rfc4408-tests.yml?rev=98&view=markup
  http://www.openspf.org/source/project/test-suite/rfc4408-tests.CHANGES?rev=98&view=auto

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkimGeIACgkQwL7PKlBZWjtWiACfd/uDjVrt3DhIgqIxYrErLbHv
u2AAn0c//HMjhknhvnY9wBufVS5uyn0w
=5DFP
-----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

--- rfc4408.txt.org	2008-08-15 22:17:01.423767657 +0000
+++ rfc4408.txt	2008-08-15 22:46:25.471808361 +0000
@@ -489,9 +489,9 @@
    A "PermError" result means that the domain's published records could
    not be correctly interpreted.  This signals an error condition that
    requires manual intervention to be resolved, as opposed to the
-   TempError result.  Be aware that if the domain owner uses macros
-   (Section 8), it is possible that this result is due to the checked
-   identities having an unexpected format.
+   TempError result.  Be aware that it is also possible that this result
+   is generated by certain SPF clients due to the input arguments
+   having an unexpected format; see Section 4.8.
 
 3.  SPF Records
 
@@ -877,6 +877,16 @@
    For several mechanisms, the <domain-spec> is optional.  If it is not
    provided, the <domain> is used as the <target-name>.
 
+   Note: Historically, this document has made no provisions for how to
+   handle <domain-spec>s, or macro-expansions thereof, that are
+   syntactically invalid per [RFC1035], such as names with empty labels
+   (e.g., "foo..example.com") or overlong labels (more than 63
+   characters).  Some implementations choose to treat as a no-match
+   mechanisms, and ignore modifiers, with such names, whereas others
+   throw a "PermError" exception.  The outcome for an unexpected
+   <domain-spec> without macros might even differ from that for an
+   unexpected <target-name> after macro expansion.
+
 5.  Mechanism Definitions
 
    This section defines two types of mechanisms.