[rfc-i] Fwd: New Version Notification for draft-flanagan-plaintext-00.txt

Dearlove, Christopher (UK) chris.dearlove at baesystems.com
Tue Jun 24 06:11:49 PDT 2014

Most people do not have the spare effort to consider what they assume will be nitpicking details to, for example, efficiently enable production of HTML. They assume that no one will do something that seriously reduces functionality. They trust people who are involved to do the right things. Same as people working on protocol X don't attend every other protocol Y working group to check nothing bad is happening there.

But as you've made it clear nothing is going to change, I'm not sure there's anything more to say.

But I'd be interested if you posted on IETF discuss with a subject line like "Printing RFCs cleanly will no longer be supported" to see how many people realise that's what you are saying. (If it's not what you are saying, which format will allow me to print an RFC without unplanned page breaks in tables or figures, not overly limited to specific tools, and tool settings, to do so?)

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: Julian Reschke [mailto:julian.reschke at gmx.de] 
Sent: 24 June 2014 13:48
To: Dearlove, Christopher (UK); Thomas Clausen
Cc: Paul Kyzivat; rfc-interest at rfc-editor.org
Subject: Re: [rfc-i] Fwd: New Version Notification for draft-flanagan-plaintext-00.txt

----------------------! WARNING ! ---------------------- This message originates from outside our organisation, either from an external partner or from the internet.
Consider carefully whether you should click on any links, open any attachments or reply.
Follow the 'Report Suspicious Emails' link on IT matters for instructions on reporting suspicious email messages.

On 2014-06-24 14:35, Dearlove, Christopher (UK) wrote:
> OK, I admit I completely missed that RFC. I suspect that's true of most other people too.

That can happen if you're not subscribed to ietf-discuss, nor to rfc-interest, and did not attend the IETF plenaries where this was announced, or the prior BOFs where it was discussed.

Best regards, Julian

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