[rfc-i] ABNF Core Rule extensions

dhc at dcrocker.net (Dave Crocker) Fri, 30 January 2015 20:37 UTC

From: "dhc at dcrocker.net"
Date: Fri, 30 Jan 2015 12:37:28 -0800
Subject: [rfc-i] ABNF Core Rule extensions
In-Reply-To: <54CBB82F.2050007@alum.mit.edu>
References: <54C29891.6040101@alum.mit.edu> <54C3576A.9030206@greenbytes.de> <54C3BE06.8010707@alum.mit.edu> <54C3C6A3.6080003@seantek.com> <54C3CF7F.6090901@seantek.com> <54C4AFF1.6030608@gmx.de> <54C7FAD7.7040500@alum.mit.edu> <54C870B5.7000205@seantek.com> <20150128173229.GC3110@localhost> <54C9632A.2040204@seantek.com> <20150128230227.GG3110@localhost> <54CB6B9A.1080801@seantek.com> <54CBB82F.2050007@alum.mit.edu>
Message-ID: <54CBEB88.4020608@dcrocker.net>

On 1/30/2015 8:58 AM, Paul Kyzivat wrote:
> 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.


This might suggest defining basic ABNF to include a registry for
enhancements.

I'd guess that setting that the effort to put that into place would not
be much work.  I'm glad to work on that partitioning effort.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net