Case-sensitive status
"Murray S. Kucherawy" <[email protected]>
| Newsgroups | gmane.mail.spam.spf.discuss |
|---|---|
| Message-ID | <F5833273385BB34F99288B3648C4F06F13512DF65B@EXCH-C2.corp.cloudmark.com> |
Hello all, first-time writer, long-time knower-of-SPF. I'm aware that Scott has started the work of putting together a push to move SPF from an Experimental to Standards Track document within the IETF. I'll be helping out where I can. One change I'd like to suggest has to do with the SPF results strings. RFC4408 presents these status strings in a specific case. RFC5451 presents them in all-lowercase. Neither one explicitly says anything about whether or not consumers of the results need to test them in a case-sensitive manner, although in a roundabout way they're case-insensitive because ABNF (RFC5234) says so when case-sensitivity isn't expressly stated. Would it break any known implementations to change them to all-lowercase in the new RFC, just to be consistent with other things? -MSK ------------------------------------------- Sender Policy Framework: http://www.openspf.org [http://www.openspf.org] Modify Your Subscription: http://www.listbox.com/member/ [http://www.listbox.com/member/] Archives: https://www.listbox.com/member/archive/735/=now RSS Feed: https://www.listbox.com/member/archive/rss/735/6959934-50ec8f89 Modify Your Subscription: https://www.listbox.com/member/?member_id=6959934&id_secret=6959934-b7c4528d Unsubscribe Now: https://www.listbox.com/unsubscribe/?member_id=6959934&id_secret=6959934-edadf31a&post_id=20110809154131:941E5732-C2BF-11E0-B039-F8BA90E3FC08 Powered by Listbox: http://www.listbox.com