IETF Logo Mail Archive

Re: Status of RFC 20

Nico Williams <nico@cryptonector.com> Tue, 09 December 2014 05:09 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E92251A1BF5 for <ietf@ietfa.amsl.com>; Mon, 8 Dec 2014 21:09:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.666
X-Spam-Level:
X-Spam-Status: No, score=-1.666 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RP8Eyfym3SHd for <ietf@ietfa.amsl.com>; Mon, 8 Dec 2014 21:09:26 -0800 (PST)
Received: from homiemail-a96.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 679571A1BA3 for <ietf@ietf.org>; Mon, 8 Dec 2014 21:09:26 -0800 (PST)
Received: from homiemail-a96.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a96.g.dreamhost.com (Postfix) with ESMTP id 2C8413B8069; Mon, 8 Dec 2014 21:09:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=wioCYiajczp6uU SbwyL9RhqA5AU=; b=n1J96jKFDNt/i3w6lrgmQa1XrLmDDI6MDm6Ed5nrzsaPG0 RsIYJ4MvlRBc932/ZEDjoXx0aQ4sbuXid27s8+R87slF6kGunJC+JwZxQHAo4NWA oFk3IRsFWUrPBHq5scEYsdhuKkO52aqS7fSEzWxnx9JzrHNGaaKHRZEnB9Csk=
Received: from localhost (108-207-244-174.lightspeed.austtx.sbcglobal.net [108.207.244.174]) (Authenticated sender: nico@cryptonector.com) by homiemail-a96.g.dreamhost.com (Postfix) with ESMTPA id 9CE9E3B8062; Mon, 8 Dec 2014 21:09:25 -0800 (PST)
Date: Mon, 08 Dec 2014 23:09:25 -0600
From: Nico Williams <nico@cryptonector.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Status of RFC 20
Message-ID: <20141209050920.GJ11221@localhost>
References: <CE03DB3D7B45C245BCA0D24327794936289DC7@MX104CL02.corp.emc.com> <CAC4RtVA10gUzmug4+H5SW2JL4Q7-Yh_ntiqPTswYSUUgXMoczA@mail.gmail.com> <BB4CB3D8CA03EB4A03FEA99B@JcK-HP8200.jck.com> <5484CAFC.7090909@bogus.com> <0F31F56DA06E076BFA0E2EA9@JcK-HP8200.jck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <0F31F56DA06E076BFA0E2EA9@JcK-HP8200.jck.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ESkytBF4p6ficOZVlPO0aTyaYFA
Cc: "Black, David" <david.black@emc.com>, Barry Leiba <barryleiba@computer.org>, rse@rfc-editor.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 09 Dec 2014 05:09:28 -0000

On Sun, Dec 07, 2014 at 05:13:57PM -0500, John C Klensin wrote:
> --On Sunday, December 07, 2014 13:47 -0800 joel jaeggli
> <joelja@bogus.com> wrote:
> > Anyone raising downref issues with rfc 20 is out of their mind.
> 
> There we agree, [...]

+1, and +1 to moving RFC20 to Standard.

> > that said you'll note a rather large gap in citations, given
> > that for something like 29 of the last 45 years there wasn't
> > an online copy in the rfc repository.
> 
> (I added Heather to the distribute because of the above)
> 
> To the best of my knowledge, there has _never_ been a
> requirement that cited documents be available online, and
> especially that authoritative copies be available online.

But perhaps there should be one as to new RFCs.  We mind (or should) our
copyright business nowadays so as to ensure such availability.  That
isn't enough to ensure the existence of an online archive, but then the
IETF and the RFC-Editor seem to strive to provide one (I should, but
don't, know whether and which RFC provides for that function, but if
there is none, that seems like a rather funny omission).

> Certainly it is preferred for many reasons, but never has it
> been a rule, nor is there a rule that makes RFCs special in that
> regard.  If the IESG asked the community for permission to

This is certainly true.  We can't really require that external documents
referenced from RFCs be archived online.

> impose such a rule, it certainly was not within my memory.  As
> to the "last 45 years", there simply has not been an online
> repository for that long, so that criticism would apply to any
> older RFC.

> If we want to start inventing new rules about citations to block
> progress, I think there are any number of members of the
> community who would be happy to contribute to the effort.  More
> constructively, April 1 will be here soon.  :-(

We shouldn't invent new rules, no, but this seems like a nice place to
segway into proposing a new rule as to online availability of new RFCs.

Nico
--

v2.23.0 | Report a Bug | By Email