Re: ISSN for RFC Series under Consideration

"TS Glassey" <tglassey@earthlink.net> Wed, 21 May 2008 19:43 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 5D0FC28C243; Wed, 21 May 2008 12:43:15 -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 4C9F028C21E; Wed, 21 May 2008 12:43:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
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 sKzJvPfd2FgC; Wed, 21 May 2008 12:43:13 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) by core3.amsl.com (Postfix) with ESMTP id 2B9EE3A6810; Wed, 21 May 2008 12:43:13 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=ZMbaMVyeluY7+TSkMgiIkH95i64PBokaV6Nj7mAgT3WQjqnLEtM0D7zShlGOj+yf; h=Received:Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [64.125.79.23] (helo=tsg1) by elasmtp-galgo.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1JyuDT-0004xT-HY; Wed, 21 May 2008 15:43:15 -0400
Message-ID: <012301c8bb7b$31689c50$0200a8c0@tsg1>
From: "TS Glassey" <tglassey@earthlink.net>
To: "Steve Crocker" <steve@shinkuro.com>, "IETF Discussion" <ietf@ietf.org>
References: <48346149.8040603@isoc.org><p06240813c45a240358e7@[165.227.249.200]> <2C63EC2C-E28F-4EB0-AE86-BF80ADF28D67@shinkuro.com>
Subject: Re: ISSN for RFC Series under Consideration
Date: Wed, 21 May 2008 12:44:57 -0700
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79a538f1ef6d089928b13ec098faa0dfdb350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 64.125.79.23
Cc: IAOC <iaoc@ietf.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 think there is a bigger issue with encumbering the people of the US for 
paying for creating an indexing system for the IETF to prevent the 
Chair/Trust from doing its job.

I suggest that this is another stupid idea from the Trust to keep them from 
actually answering the question as to what they are going to do to
    1)    Protect IETF IP's
    2)    Market those IP's

Todd Glassey

----- Original Message ----- 
From: "Steve Crocker" <steve@shinkuro.com>
To: "IETF Discussion" <ietf@ietf.org>
Cc: "IAOC" <iaoc@ietf.org>
Sent: Wednesday, May 21, 2008 12:17 PM
Subject: Re: ISSN for RFC Series under Consideration


> Naw.  The ISSN has to be on the document itself.  As you point out,
> this isn't something to be done with Internet Drafts, so it falls
> naturally to the RFC Editor, not to the individual authors.
>
> Steve
>
>
> On May 22, 2008, at 3:14 AM, Paul Hoffman wrote:
>
>> Mostly sounds fine, with one small glitch.
>>
>> At 1:52 PM -0400 5/21/08, Ray Pelletier wrote:
>>> According to the Library of Congress, www.loc.gov/issn/, for serials
>>> available only in online versions, the ISSN should appear on the
>>> title
>>> screen or home page and/or in the masthead or other areas where
>>> information about publisher, frequency, subscribing, copyright,
>>> etc. is
>>> given.
>>
>> The value of adding "ISSN: 12345678" to each RFC seems small,
>> particularly relative to the cost of everyone having to update their
>> tools and so on. Also, we would have to tell people *not* to put the
>> ISSN designation in their Internet Drafts (which are not part of the
>> RFC series), but then switch it on for the RFC, and so on.
>>
>> The cost of putting "ISSN: 12345678" on a few pages at rfc-editor.org
>> and ietf.org is tiny and hopefully sufficient for the statement above.
>>
>> --Paul Hoffman
>> _______________________________________________
>> IETF mailing list
>> IETF@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>
> _______________________________________________
> IETF mailing list
> IETF@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf 

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