On Wed, Mar 23, 2016 at 2:27 PM, Sean Leonard <dev+ietf(_at_)seantek(_dot_)com>
But the terminology needs to be clarified
at some point: a single document (or sentence) is either normative or
not. If something is a "best common practice", it is not normative, the
rules are set somewhere else.
IETF Process issue:
Well, RFC 5646/BCP 47 "Tags for Identifying Languages" is a BCP. However,
it is referred to normatively by a slew of Standards Track documents. I
would propose that this document be seen in a similar light. One would not
expect the Mail Standards to adopt these regular expressions, but other
standards that use regular expressions for e-mail would probably do best to
refer to this document. Examples include CBOR/CDDL
(draft-greevenbosch-appsawg-cbor-cddl), and DNS/NAPTR records (RFCs
3401-3404), when the subject matter is e-mail stuff.
It seems to me RFC2026's definition of BCP would cover what you're trying
to do here.
And if what you're really producing is regular expressions that match
anything that the ABNFs in the mail RFCs will legitimately produce, you
might want to do a standards track document that explicitly updates those
documents where those ABNFs are listed.
Then again, I could see this just as easily going Informational since it's
unlikely (to me, at least) that anyone will point compliance language at
such a document.
How's that for actionable feedback? :-/
ietf-smtp mailing list