[rfc-i] ABNF Core Rule extensions

Changing the subject because the discussion no longer has anything to do 
with fragment tagging.

First, it's questionable whether extending the ABNF Core Rules is in 
scope for rfc-interest. If we are talking about extending RFC5234 then 
abnf-interest would be a better place.

OTOH, it might make sense to decouple the Core Rules from RFC5234 into 
their own RFC. In that case it *might* make sense to do it here.

Decoupling them (and then updating RFC5234 to remove them and instead 
reference the separate draft) would eliminate one obvious case where 
there are two distinct ABNF modules in the same draft.

	Thanks,
	Paul

On 1/30/15 6:31 AM, Sean Leonard wrote:
> On 1/28/2015 3:02 PM, Nico Williams wrote:
>>> As a broader useful point (not directed specifically to
>>> draft-ietf-json-text-sequence-13), I think it would be nice if
>>> future RFC ABNF can assume that the symbols in RFC 20 for %x00-20 /
>>> %x7F are rules that can be used as-is. Hence NUL = %x00, SUB = %x1A,
>>> DEL = %x7F, etc.
>> I agree.  These should be added to RFC5234 (i.e., we should publish an
>> update RFC listing them).
>
> I would be willing to write up/work on a concise RFC (Internet-Draft)
> that does this, prior to IETF 92. I would not mind adding a few
> additional rules to the Core Rules if there is near-unanimous support
> for such rules. (Hard to think of any in particular, except maybe some
> generic UTF8 character rules. Last I checked, ABNF is still
> octet-oriented and US-ASCII focused.)
>
> While I would not say "precondition", it is reasonable to require that
> RFCs after the publication of such an RFC follow it, much like RFCs past
> 5234 use RFC 5234 as the basis.
>
> Sean
>
> _______________________________________________
> rfc-interest mailing list
> rfc-interest at rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
>