Source material for RFCs (was: Re: [dnsext] a possible errata to RFC2136)
Alfred Hönes <ah@TR-Sys.de> Tue, 10 November 2009 17:30 UTC
Return-Path: <owner-namedroppers@ops.ietf.org>
X-Original-To: ietfarch-dnsext-archive@core3.amsl.com
Delivered-To: ietfarch-dnsext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 29BBC3A6917; Tue, 10 Nov 2009 09:30:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.888
X-Spam-Level: ***
X-Spam-Status: No, score=3.888 tagged_above=-999 required=5 tests=[AWL=-0.962, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, FH_RELAY_NODNS=1.451, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, J_CHICKENPOX_24=0.6, MIME_8BIT_HEADER=0.3, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h57X5PzHnmDi; Tue, 10 Nov 2009 09:30:34 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 0DACD3A685E; Tue, 10 Nov 2009 09:30:34 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1N7uRN-0002Bu-IV for namedroppers-data0@psg.com; Tue, 10 Nov 2009 17:23:37 +0000
Received: from [213.178.172.147] (helo=TR-Sys.de) by psg.com with esmtp (Exim 4.69 (FreeBSD)) (envelope-from <A.Hoenes@TR-Sys.de>) id 1N7uRJ-0002B8-GZ for namedroppers@ops.ietf.org; Tue, 10 Nov 2009 17:23:34 +0000
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA112083758; Tue, 10 Nov 2009 18:22:38 +0100
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id SAA06630; Tue, 10 Nov 2009 18:22:37 +0100 (MEZ)
From: Alfred Hönes <ah@TR-Sys.de>
Message-Id: <200911101722.SAA06630@TR-Sys.de>
Subject: Source material for RFCs (was: Re: [dnsext] a possible errata to RFC2136)
To: namedroppers@ops.ietf.org
Date: Tue, 10 Nov 2009 18:22:36 +0100
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset="hp-roman8"
Content-Transfer-Encoding: 7bit
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-ID: <namedroppers.ops.ietf.org>
List-Unsubscribe: To unsubscribe send a message to namedroppers-request@ops.ietf.org with
List-Unsubscribe: the word 'unsubscribe' in a single line as the message text body.
List-Archive: <http://ops.ietf.org/lists/namedroppers/>
At Mon, 09 Nov 2009 18:21:57 -0500, Olafur Gudmundsson wrote:
> FWIW, I have a copy of the nroff file that the rfc-editor used
> to generate RFC2136.
>
> Olafur
There's (in general) no need to escape to private copies.
It is an explicit task [*] of the RFC Editor to securely archive the
'source' documents used to generate RFCs as well, and to hand out
copies of these files to interested parties, e.g. for the purpose of
performing follow-up work.
So simply ask the RFC Editor if there's a need!
Kind regards,
Alfred.
[*]
An interesting reading for folks who want to look behind the scenes
of the RFC Editor, how they work and -- collaterally -- how authors
can contribute to {speed up|slow down} their work,
and who also have enough spare time on travelling:
http://IAOC.IETF.ORG/docs/Bidders-Conference-Transcript-6-03-09.txt
or
http://IAOC.IETF.ORG/docs/Bidders-Conference-Transcript-6-03-09.pdf
More related material can be found on
http://IAOC.IETF.ORG/rfced-procurement.html#PositionDes
and
http://IAOC.IETF.ORG/rfced-procurement.html#Bidders
- Source material for RFCs (was: Re: [dnsext] a pos… Alfred Hönes