Re: Citation bug in RFC 2425

Paul Hoffman / IMC <phoffman@IMC.ORG> Fri, 29 October 1999 23:20 UTC

Received: by ietf.org (8.9.1a/8.9.1a) id TAA26652 for ietf-outbound.10@ietf.org; Fri, 29 Oct 1999 19:20:02 -0400 (EDT)
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25291 for <ietf@ietf.org>; Fri, 29 Oct 1999 19:14:21 -0400 (EDT)
Received: from Default (ip12.proper.com [165.227.249.12]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id QAA23545; Fri, 29 Oct 1999 16:11:00 -0700 (PDT)
Message-Id: <4.2.1.19991029161005.00b94ad0@mail.imc.org>
X-Sender: phoffman@mail.imc.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.1
Date: Fri, 29 Oct 1999 16:14:16 -0700
To: braden@ISI.EDU, ietf@ietf.org, tlilley@perspex.com
From: Paul Hoffman / IMC <phoffman@IMC.ORG>
Subject: Re: Citation bug in RFC 2425
In-Reply-To: <199910292216.AA06502@gra.isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"

At 03:16 PM 10/29/99 -0700, braden@ISI.EDU wrote:
>Using a URL in a citation in an RFC seems like a bad idea.  There may
>be exceptions, e.g., an IETF.org or RFC-Editor.org URL might be less
>risky.  But expecting a URL in general to stay invariant for 25 years
>seems dubious.

Not to worry in this case: it wasn't a normative reference. In fact, that 
reference wasn't mentioned at all in the body of the RFC. :-) They did 
manage to get the URL correct in RFC2426, where it is also a non-normative 
reference.

--Paul Hoffman, Director
--Internet Mail Consortium