RE: RFC 6234 code
"Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com> Mon, 01 July 2013 11:14 UTC
Return-Path: <chris.dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 112B021F9B17 for <ietf@ietfa.amsl.com>; Mon, 1 Jul 2013 04:14:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ouh5fAZjqNf for <ietf@ietfa.amsl.com>; Mon, 1 Jul 2013 04:14:38 -0700 (PDT)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id 6637C21F901A for <ietf@ietf.org>; Mon, 1 Jul 2013 04:14:38 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,973,1363132800"; d="scan'208";a="296745758"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by Baemasodc001ir.sharelnk.net with ESMTP; 01 Jul 2013 12:14:33 +0100
X-IronPort-AV: E=Sophos;i="4.87,973,1363132800"; d="scan'208";a="20658772"
Received: from glkxh0002v.greenlnk.net ([10.109.2.33]) by baemasodc005.greenlnk.net with ESMTP; 01 Jul 2013 12:14:33 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.180]) by GLKXH0002V.GREENLNK.net ([10.109.2.33]) with mapi id 14.02.0328.009; Mon, 1 Jul 2013 12:14:33 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Joe Abley <jabley@hopcount.ca>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: RE: RFC 6234 code
Thread-Topic: RFC 6234 code
Thread-Index: AQHOdD/gHirQWo7qWku6uA/H1V6pk5lPr6Uw
Date: Mon, 01 Jul 2013 11:14:33 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25099133@GLKXM0002V.GREENLNK.net>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097AA4@GLKXM0002V.GREENLNK.net> <51CC67D0.8050600@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097B24@GLKXM0002V.GREENLNK.net> <51CC94B2.2060507@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25097CC1@GLKXM0002V.GREENLNK.net> <51CD9987.8010401@att.com> <BEFC413A958E9B25913F2FE9@JcK-HP8200.jck.com> <D3A3A63A-0CB1-4254-A087-655F9BDA6CEC@vpnc.org> <DB3A3E49-13C6-4CE3-87D5-8F86B37DFC57@hopcount.ca>
In-Reply-To: <DB3A3E49-13C6-4CE3-87D5-8F86B37DFC57@hopcount.ca>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: John C Klensin <john-ietf@jck.com>, RFC Interest <rfc-interest@rfc-editor.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jul 2013 11:14:43 -0000
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@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@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Joe Abley Sent: 28 June 2013 21:41 To: Paul Hoffman Cc: John C Klensin; RFC Interest; ietf@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@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". Joe ******************************************************************** 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. ********************************************************************
- RFC 6234 code Dearlove, Christopher (UK)
- Re: RFC 6234 code Hector Santos
- RE: RFC 6234 code Dearlove, Christopher (UK)
- Re: RFC 6234 code Eggert, Lars
- Re: RFC 6234 code Joe Abley
- Re: RFC 6234 code Joe Abley
- Re: RFC 6234 code Hector Santos
- Re: RFC 6234 code Joe Abley
- RE: RFC 6234 code Dearlove, Christopher (UK)
- Re: RFC 6234 code Eggert, Lars
- RE: RFC 6234 code Dearlove, Christopher (UK)
- Re: RFC 6234 code Tony Hansen
- Re: RFC 6234 code Riccardo Bernardini
- Re: RFC 6234 code Paul Hoffman
- Part of Improving IETF Electronic Diversity [was:… Hector Santos
- Re: RFC 6234 code John C Klensin
- Re: RFC 6234 code Paul Hoffman
- Re: RFC 6234 code Joe Abley
- Re: Part of Improving IETF Electronic Diversity [… Donald Eastlake
- Re: RFC 6234 code Martin Rex
- Re: RFC 6234 code Martin Rex
- Re: RFC 6234 code John C Klensin
- Re: RFC 6234 code Tony Finch
- RE: RFC 6234 code Dearlove, Christopher (UK)