[rfc-i] v3imp #8 Fragment tagging on sourcecode

Paul Kyzivat pkyzivat at alum.mit.edu
Fri Jan 23 10:37:48 PST 2015

On 1/23/15 1:16 PM, Nico Williams wrote:
> On Fri, Jan 23, 2015 at 01:09:03PM -0500, Paul Kyzivat wrote:
>> On 1/23/15 12:55 PM, Nico Williams wrote:
>>> Keeping the canonical module scattered is not an answer.
>> Different strokes for different folks. This *can* work. It would
> Yes, it *can* work.  But when you make large changes you have to scatter
> them all over your I-D.  That's double-plus-unfun.
>> work much better if you could automatically extract the collection
>> of fragments when you want to process it.
> That's easy enough if you're willing to do what RFC5403 does.

Sure, but without a standard way to do it you need a custom extractor 
for every draft. In the case of ABNF, which is widely used in drafts, it 
would be highly desirable to have a single tool that could verify the 
ABNF in any draft.

Also, the tagging in 5403 diminishes the readability of the draft. 
Consider how much less readable RFC5234 would be if you did that.


More information about the rfc-interest mailing list