RE: [IAOC] ISSN for RFC Series under Consideration

"Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com> Tue, 27 May 2008 14:56 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 83FF53A68A2; Tue, 27 May 2008 07:56:23 -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 91AF43A6890; Tue, 27 May 2008 07:56:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.547
X-Spam-Level:
X-Spam-Status: No, score=-5.547 tagged_above=-999 required=5 tests=[AWL=1.051, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 1ARJvmV6zXrU; Tue, 27 May 2008 07:56:21 -0700 (PDT)
Received: from mail128.messagelabs.com (mail128.messagelabs.com [216.82.250.131]) by core3.amsl.com (Postfix) with SMTP id 7E5DF3A68A2; Tue, 27 May 2008 07:56:21 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: Donald.Eastlake@motorola.com
X-Msg-Ref: server-13.tower-128.messagelabs.com!1211900186!7324861!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 6396 invoked from network); 27 May 2008 14:56:26 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-13.tower-128.messagelabs.com with SMTP; 27 May 2008 14:56:26 -0000
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id m4REuKQL023252; Tue, 27 May 2008 07:56:25 -0700 (MST)
Received: from il06vts01.mot.com (il06vts01.mot.com [129.188.137.141]) by il06exr02.mot.com (8.13.1/Vontu) with SMTP id m4REuJha003073; Tue, 27 May 2008 09:56:19 -0500 (CDT)
Received: from de01exm64.ds.mot.com (de01exm64.am.mot.com [10.176.8.15]) by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id m4REuIBj003061; Tue, 27 May 2008 09:56:19 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [IAOC] ISSN for RFC Series under Consideration
Date: Tue, 27 May 2008 10:56:17 -0400
Message-ID: <3870C46029D1F945B1472F170D2D979003D50213@de01exm64.ds.mot.com>
In-Reply-To: <5D1A7985295922448D5550C94DE2918001F64020@DEEXC1U01.de.lucent.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [IAOC] ISSN for RFC Series under Consideration
thread-index: Aci7cZYO0+1fIPReQHa3pUpy1VNzNwEcsM3wAAjDeDA=
References: <48346149.8040603@isoc.org><p06250105c45a15074413@[75.145.176.242]><48346B97.8090804@isoc.org> <5D1A7985295922448D5550C94DE2918001F64020@DEEXC1U01.de.lucent.com>
From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
To: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
X-CFilter-Loop: Reflected
Cc: IAOC <iaoc@ietf.org>, IETF Discussion <ietf@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: multipart/mixed; boundary="===============0289024108=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

It's not "rather than". The issues are orthogonal. The reasons for
getting an ISSN have been posted. ISBNs for individual RFCs is a
separate issue that would not be affected by getting an ISSN for the
series.
 
Donald

________________________________

From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
Behalf Of DRAGE, Keith (Keith)
Sent: Tuesday, May 27, 2008 9:17 AM
To: Ray Pelletier; Pete Resnick
Cc: Working Group Chairs; RFC Editor; IAB; IETF Discussion; IAOC
Subject: RE: [IAOC] ISSN for RFC Series under Consideration


Can you explain why you are suggesting using an ISSN for the whole
series, rather than ISBN for individual RFCs.
 
regards
 
Keith


________________________________

	From: wgchairs-bounces@ietf.org
[mailto:wgchairs-bounces@ietf.org] On Behalf Of Ray Pelletier
	Sent: Wednesday, May 21, 2008 7:36 PM
	To: Pete Resnick
	Cc: Working Group Chairs; IAB; IETF Discussion; IAOC; RFC Editor
	Subject: Re: [IAOC] ISSN for RFC Series under Consideration
	
	


	Pete Resnick wrote:
	

		On 5/21/08 at 1:52 PM -0400, Ray Pelletier wrote:
		
		  

			The Trust believes there are advantages to
indentifying the RFC 
			Series with an ISSN.
			    

		
		OK, maybe I'm getting suspicious in my (still slowly)
advancing years:
		  

		Nowhere in the message did I see words like, "The Trust
has consulted 
		with lawyers/doctors/priests/old-crusty-IETFers and have
found no 
		disadvantages to identifying the RFC Series with an
ISSN."

	The Trust did consult with lawyers, old-crusty-IETFers, RFC
Editor, and found no disadvantages to indentifying the RFC Series with
an ISSN.  
	

		 Did the 
		Trust actually find no potential problems (in which case
it would be 
		nice to hear that), have they not looked into it yet, or
did they 
		find problems and you're not saying because you don't
want to have a 
		big public discussion (in which case you're being dopey,
because it's 
		gonna happen anyway)?
		  

	That we know!
	

		(For the record, had you said that the Trust did in fact
consult the 
		tea leaves and everything looked on the up-and-up and
they were 
		simply confirming this with the community, I would have
immediately 
		said, "Fine with me." I'm happy to have people to whom
such things 
		can be delegated, but I do want to hear the words "We've
done our due 
		diligence.")
		  

	We've done our due diligence, but we respect the community and
the process, and seek its guidance.
	
	Ray
	

		pr
		  

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