[rfc-i] RFC 6234 code

Dearlove, Christopher (UK) chris.dearlove at baesystems.com
Mon Jul 1 04:14:33 PDT 2013

That's 20 minutes per person of course.

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: ietf-bounces at ietf.org [mailto:ietf-bounces at ietf.org] On Behalf Of Joe Abley
Sent: 28 June 2013 21:41
To: Paul Hoffman
Cc: John C Klensin; RFC Interest; ietf at ietf.org list
Subject: Re: RFC 6234 code

----------------------! 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 2013-06-28, at 15:19, Paul Hoffman <paul.hoffman at vpnc.org> wrote:

> The RFC Editor is publishing code in a text file that is formatted like an RFC. The proposal is for the RFC Editor to publish *the exact same code* in a file without the RFC wrapping.
> If you really think you see a legal difference in doing the second, fine; I propose that you are just searching for problems that do not exist.

Quite possibly they don't, and I'm not presuming to talk for John. But the vague thoughts that crossed my mine were the issues that allowed Phil Zimmerman to publish PGP source code in book form and avoid conviction for munitions export without a licence.

Perhaps this is no longer an issue in the US following Bernstein vs. United States and Junger vs. Daley.

Just thinking aloud, really.

I will observe that far more than 20 minutes of combined person-minutes have been consumed by this thread already, and the approach of minimum collective effort is still "scrape the code from the RFC yourself and compile it".

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