Re: ISSN for RFC Series under Consideration

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 21 May 2008 21:38 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 7A13D3A6905; Wed, 21 May 2008 14:38:58 -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 F2E983A6958 for <ietf@core3.amsl.com>; Wed, 21 May 2008 14:38:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.414
X-Spam-Level:
X-Spam-Status: No, score=-2.414 tagged_above=-999 required=5 tests=[AWL=0.185, 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 CkQg4+BO-ig9 for <ietf@core3.amsl.com>; Wed, 21 May 2008 14:38:56 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.229]) by core3.amsl.com (Postfix) with ESMTP id 409563A68FA for <ietf@ietf.org>; Wed, 21 May 2008 14:38:56 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so2441369rvf.49 for <ietf@ietf.org>; Wed, 21 May 2008 14:39:00 -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=JKxrHh6Mf8iSZ8jX64U0j9HdutoKEQOX/Qk571XPvsQ=; b=cM3I0V8G9GRdAmxuyH1UbVA8UyDWUspp/ESFlhrkmvTkvcJNDGMVmchT8qcOmSL7tWcZDkzcnYE4W80OwXl7SciNpQ6ykO5GpyvsgMgb7v3y0DztBfRTavkf+Hoc5R9ysazDQobQyULJc10kACr8fP4OOI5I3kHdOtrBVPYKzcU=
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=jH65ZT1n0z9PRjnznXJDMxarVXluk58oMFp6baAsPVAHG9sorwTMHrDWa8KhoZuffhAl+50hxAysZ7inr6/u5BhP6uGd965aRY21V2HzU+KpAqOoVZc1B6aYhx75phCxe0Bvel1qGyndiaq0TFk4/gUR0AMse5Gs9Zvqiv/Vgco=
Received: by 10.140.193.15 with SMTP id q15mr807000rvf.191.1211405940687; Wed, 21 May 2008 14:39:00 -0700 (PDT)
Received: from ?130.216.38.124? ( [130.216.38.124]) by mx.google.com with ESMTPS id k41sm2881260rvb.3.2008.05.21.14.38.58 (version=SSLv3 cipher=RC4-MD5); Wed, 21 May 2008 14:39:00 -0700 (PDT)
Message-ID: <48349682.6040803@gmail.com>
Date: Thu, 22 May 2008 09:39:14 +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: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: ISSN for RFC Series under Consideration
References: <48346149.8040603@isoc.org> <483475E6.7050107@gmx.de>
In-Reply-To: <483475E6.7050107@gmx.de>
Cc: Working Group Chairs <wgchairs@ietf.org>, IAB <iab@ietf.org>, IETF Discussion <ietf@ietf.org>, IAOC <iaoc@ietf.org>, The IESG <iesg@ietf.org>, 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

On 2008-05-22 07:20, Julian Reschke wrote:
> Ray Pelletier wrote:
>> ...
>> The Trust believes there are advantages to indentifying the RFC Series 
>> with an ISSN.  Among them,
>> 1. Make reference to the series compact and globally unique;
>> ...
> 
> More compact than <urn:ietf:rfc:nnnn>?

Possibly not, but there is still a crusty old world of academic
publications with traditional reference styles out there, and an ISSN
will make it much more straightforward to cite RFCs in peer-reviewed
publications. +1 that it's a no-brainer.

Regards
   Brian Carpenter
   University of Auckland


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