Re: ISSN for RFC Series under Consideration

John C Klensin <> Thu, 22 May 2008 15:19 UTC

Return-Path: <>
Received: from [] (localhost []) by (Postfix) with ESMTP id 8F1FE3A6B19; Thu, 22 May 2008 08:19:08 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 940D03A6B23 for <>; Thu, 22 May 2008 08:19:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id lWAmDDTnuRIb for <>; Thu, 22 May 2008 08:19:06 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 98E973A6B16 for <>; Thu, 22 May 2008 08:19:06 -0700 (PDT)
Received: from [] (helo=localhost) by with esmtp (Exim 4.34) id 1JzCZR-00076a-Ok; Thu, 22 May 2008 11:19:10 -0400
Date: Thu, 22 May 2008 11:19:06 -0400
From: John C Klensin <>
To: Marshall Eubanks <>
Subject: Re: ISSN for RFC Series under Consideration
Message-ID: <AA06F31A614ADD97F28596F7@[]>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Disposition: inline
Cc: Steve Crocker <>, IETF Discussion <>
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

--On Thursday, 22 May, 2008 11:00 -0400 Marshall Eubanks
<> wrote:

> Here is a concrete suggestion.
> We (for some definition of we) have the Internet Journal,
> which is   paper.
> Publish a "Supplement of the Internet Journal," in paper, or
> on line,   which is
> - physically published 3 times a year
> - has all of the RFC's published since then
> - includes the level 1 RFC errata as available
> - includes other notes like RFC's that have been made
> obsolete, etc. - charge it to cover costs at least (say, $ 500
> / year for a   subscription).
> This would be picked up by at least some libraries, and would
> solve   the "on-line is ephemera" problem.


I think this is an interesting idea.   It is, however, one that
would require some staffing, budget, working with ISOC on
arrangements, etc.  I don't see any of those things as a big
deal, but I could be wrong.   And they are certainly a bigger
deal than assigning an ISSN number and, if necessary, simply
running a printer and stuffing an envelope (as Bill suggested,
we've actually done that in the more or less distant past).

So my constructive suggestions are

(i) Let's not make this hard for ourselves.

(ii) Assigning an ISSN to the series would not interfere, in any
way, with what you suggest should the demand be there, either
for library subscriptions, as an added symbolic benefit for some
level of ISOC membership, or both.   And, for some of the
purposes for which an ISSN for the RFC series would be a good
idea, assigning that number to a compendium that includes
non-RFC materials would be self-defeating.

(iii) As someone suggested earlier in this thread, the IETF
Journal should probably have an ISSN of its own, but that is a
quite separate issue.

IETF mailing list