IETF Logo Mail Archive

Re: ISSN for RFC Series under Consideration

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 22 May 2008 01:06 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A986E28C0F3; Wed, 21 May 2008 18:06:30 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F1D5C28C10C for <ietf@core3.amsl.com>; Wed, 21 May 2008 18:06:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.507
X-Spam-Level:
X-Spam-Status: No, score=-2.507 tagged_above=-999 required=5 tests=[AWL=0.092, BAYES_00=-2.599]
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 s3JdmF5uPLhF for <ietf@core3.amsl.com>; Wed, 21 May 2008 18:06:27 -0700 (PDT)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by core3.amsl.com (Postfix) with ESMTP id C55C53A6897 for <ietf@ietf.org>; Wed, 21 May 2008 18:06:26 -0700 (PDT)
Received: by wa-out-1112.google.com with SMTP id k34so3580551wah.25 for <ietf@ietf.org>; Wed, 21 May 2008 18:06:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:organization:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=GAyk0yRaxiUqv0d08TOGTra3ESl+e/qFxX7Dl5OR+MY=; b=G8jCD6Fr2QhAgIdawjtEsppo4UUneC/v/zOeoL8yEd6RTyOni3iOaYvxipn3jpt5CisB/BxMJ/a8a53GHwceq0atH1SFINbBMevk53VuHMvQV3KhfiQ/BOHm1TJ0MXhxkYaRGCScMO8k2hLWZY81SXvNIQkoKGq/yIwFBKNzRp0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=wth2wOzDDJlit5LJW2ixF/JcCgbi/viARxPtZXdpIlwmEJxdIMlCSVe3RWKLZEhcmR1tGzC/U3siI45kjmlO/BxcsWviwcel0zxZDfwgNiT/WDxkSPweL4QL0L12M/QgNuBSoGU80IvIgZEDxDueYIDnZZESCPKPkvhaIzZ/7Lg=
Received: by 10.114.132.5 with SMTP id f5mr11334395wad.201.1211418390005; Wed, 21 May 2008 18:06:30 -0700 (PDT)
Received: from ?130.216.38.124? ( [130.216.38.124]) by mx.google.com with ESMTPS id n32sm6777302wag.47.2008.05.21.18.06.26 (version=SSLv3 cipher=RC4-MD5); Wed, 21 May 2008 18:06:29 -0700 (PDT)
Message-ID: <4834C728.1060804@gmail.com>
Date: Thu, 22 May 2008 13:06:48 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Eric Rescorla <ekr@networkresonance.com>
Subject: Re: ISSN for RFC Series under Consideration
References: <48349682.6040803@gmail.com> <C45A11F7.38960%mshore@cisco.com> <20080521230951.EB8C85081A@romeo.rtfm.com>
In-Reply-To: <20080521230951.EB8C85081A@romeo.rtfm.com>
Cc: Working Group Chairs <wgchairs@ietf.org>, IAB <iab@ietf.org>, IETF Discussion <ietf@ietf.org>, Melinda Shore <mshore@cisco.com>, IAOC <iaoc@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

> 
> I agree with Melinda here. I can't remember ever seeing anything
> like an ISBN or an ISSN used as a citation in an academic paper.

Correct, but I have seen a wide variety of ways to cite RFCs
and tying them all back to an ISSN number would be a step forward
IMHO. In any case: at worst, harmless.

   Brian
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email