[rfc-i] Embedding stuff (code, etc.) in RFCs

Dearlove, Christopher (UK) chris.dearlove at baesystems.com
Fri Jul 12 11:49:52 PDT 2013

It is definitive now. And based on where every discussion I've seen on the subject goes, not changing soon. So that's what any approach has to be built on.

And I never suggested every line. Distinctive text can be between markers.

Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194 |  Fax: +44 1245 242124
chris.dearlove at baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687

-----Original Message-----
From: Paul Kyzivat [mailto:pkyzivat at alum.mit.edu] 
Sent: 12 July 2013 17:46
To: Dearlove, Christopher (UK)
Cc: rfc-interest at rfc-editor.org
Subject: Re: [rfc-i] Embedding stuff (code, etc.) in RFCs

----------------------! WARNING ! ----------------------
This message originates from outside our organisation,
either from an external partner or from the internet.
Keep this in mind if you answer this message.
Follow the 'Report Suspicious Emails' link on IT matters
for instructions on reporting suspicious email messages.

On 7/12/13 12:39 PM, Dearlove, Christopher (UK) wrote:
> The .txt is the definitive RFC, so extracting from that has its advantages.

It is definitive *now*. But the limitations of that are also clear.
This is one of them.

> Perhaps we should have a <code> or whatever in the XML, and then xml2rfc to map that to something distinctive, plus a tool to pull the distinctive text out of the .txt, while extracting the code from <code> ... </code> in the XML would be trivial.

I don't want the support for code extraction to impact the readability 
of the draft. Having to put special punctuation into the draft, 
especially on every line of code, does, IMO, detract from readability.


This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.

More information about the rfc-interest mailing list