
From touch@isi.edu  Thu May  2 16:36:55 2013
Return-Path: <touch@isi.edu>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F88D21F8F3C for <irtf-discuss@ietfa.amsl.com>; Thu,  2 May 2013 16:36:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.2
X-Spam-Level: 
X-Spam-Status: No, score=-105.2 tagged_above=-999 required=5 tests=[AWL=0.600,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c1DvKrC59iqe for <irtf-discuss@ietfa.amsl.com>; Thu,  2 May 2013 16:36:50 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 568E421F8EC2 for <irtf-discuss@irtf.org>; Thu,  2 May 2013 16:36:50 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r42NZvsr028563 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 2 May 2013 16:35:57 -0700 (PDT)
Message-ID: <5182F84F.8000402@isi.edu>
Date: Thu, 02 May 2013 16:35:43 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: bmanning@vacation.karoshi.com
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.>
In-Reply-To: <20130425140830.GA21669@vacation.karoshi.com.>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: Re: [irtf-discuss] RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2013 23:36:55 -0000

IETF-stream and IRTF-streams are often considered peer-reviewed.

Other streams may or may not be considered peer-reviewed (I would not 
consider IAB documents as such), but independent submissions are 
generally not (they only purpose of the one review they get is to make 
sure they're on-topic and not bogus).

Joe

On 4/25/2013 7:08 AM, bmanning@vacation.karoshi.com wrote:
>
>   at least a few university communities consider RFCs as peer reviewed papers.
>
> /bill
>
>
> On Thu, Apr 25, 2013 at 12:42:54PM +0000, Yaakov Stein wrote:
>> I just checked and my request is marked "under consideration" with no-one else voting for it.
>>
>> See https://feedback.researchgate.net/responses/please-allow-enter-ietf-rfcs-as-peer-reviewed-papers
>>
>> Perhaps if some other ResearchGate members vote for it the RG staff will take notice.
>>
>> Y(J)S
>>
>>
>> -----Original Message-----
>> From: irtf-discuss-bounces@irtf.org [mailto:irtf-discuss-bounces@irtf.org] On Behalf Of Yaakov Stein
>> Sent: 25 April, 2013 15:33
>> To: marcelo bagnulo braun; SM
>> Cc: irtf-discuss@irtf.org; rfc-interest@rfc-editor.org
>> Subject: Re: [irtf-discuss] RFCs accepted journal articles
>>
>>
>> I submitted a request to ResearchGate to accept RFCs as a valid publication type.
>>
>> However, I never received any feedback from them.
>>
>> Y(J)S
>>
>>
>> -----Original Message-----
>> From: irtf-discuss-bounces@irtf.org [mailto:irtf-discuss-bounces@irtf.org] On Behalf Of marcelo bagnulo braun
>> Sent: 25 April, 2013 15:19
>> To: SM
>> Cc: irtf-discuss@irtf.org; rfc-interest@rfc-editor.org
>> Subject: Re: [irtf-discuss] RFCs accepted journal articles
>>
>> I already did quite a while ago. No reply so far.
>>
>> El 25/04/13 11:00, SM escribis:
>>> Hi Marcelo,
>>> At 01:32 25-04-2013, marcelo bagnulo braun wrote:
>>>> What would be really useful would be that the RFC series are included
>>>> in the Journal Citation Report. I have asked this to the RFC editor a
>>>> while ago, but i didnt received any reply.
>>>>
>>>> This would go a very long way (at least in this part of the world) to
>>>> make them valid as a an merit for the academics.
>>>
>>> I suggest asking the RSE about the above.
>>>
>>> Regards,
>>> -sm
>>>
>>

From jari.arkko@piuha.net  Thu May  2 17:11:45 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB98021F8FC4 for <irtf-discuss@ietfa.amsl.com>; Thu,  2 May 2013 17:11:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.14
X-Spam-Level: 
X-Spam-Status: No, score=-102.14 tagged_above=-999 required=5 tests=[AWL=-0.340, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QDV+Ws0IN8iP for <irtf-discuss@ietfa.amsl.com>; Thu,  2 May 2013 17:11:40 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 6DCB721F86B9 for <irtf-discuss@irtf.org>; Thu,  2 May 2013 17:11:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 637A12CC56; Fri,  3 May 2013 03:11:39 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id duL4QCa05Yn5; Fri,  3 May 2013 03:11:38 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id E38A12CC48; Fri,  3 May 2013 03:11:37 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <5182F84F.8000402@isi.edu>
Date: Thu, 2 May 2013 20:11:35 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2EF12BD5-908C-4D8C-81F2-C88B8AF52BA2@piuha.net>
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.> <5182F84F.8000402@isi.edu>
To: Joe Touch <touch@ISI.EDU>
X-Mailer: Apple Mail (2.1503)
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, bmanning@vacation.karoshi.com, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: Re: [irtf-discuss] [rfc-i]  RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 00:11:45 -0000

> IETF-stream and IRTF-streams are often considered peer-reviewed.
>=20
> Other streams may or may not be considered peer-reviewed (I would not =
consider IAB documents as such), but independent submissions are =
generally not (they only purpose of the one review they get is to make =
sure they're on-topic and not bogus).

There are two review steps for the independent submissions, the ISR and =
the IESG review. I was under the impression that while the latter is =
just about non-conflict with the IETF process, the former would  have =
looked at content and worthwhileness to publish. But I've never been a =
part of the review board, so I don't really know=85

Anyway, not trying to deflect your main point but just wondering about =
this one detail.

Also, IAB does publish documents with a comment period, but it is true =
that they are not obliged to take feedback into account, so in theory =
they are not peer reviewed while in practice they often are.

Jari


From touch@isi.edu  Thu May  2 17:32:13 2013
Return-Path: <touch@isi.edu>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA9D921F8FDC for <irtf-discuss@ietfa.amsl.com>; Thu,  2 May 2013 17:32:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.4
X-Spam-Level: 
X-Spam-Status: No, score=-105.4 tagged_above=-999 required=5 tests=[AWL=0.400,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C4CW-5YHSizh for <irtf-discuss@ietfa.amsl.com>; Thu,  2 May 2013 17:32:06 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id B9ABA21F8ED3 for <irtf-discuss@irtf.org>; Thu,  2 May 2013 17:32:06 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r430VUdO008508 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 2 May 2013 17:31:31 -0700 (PDT)
Message-ID: <51830554.6040604@isi.edu>
Date: Thu, 02 May 2013 17:31:16 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.> <5182F84F.8000402@isi.edu> <2EF12BD5-908C-4D8C-81F2-C88B8AF52BA2@piuha.net>
In-Reply-To: <2EF12BD5-908C-4D8C-81F2-C88B8AF52BA2@piuha.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, bmanning@vacation.karoshi.com, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: Re: [irtf-discuss] [rfc-i]  RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 00:32:13 -0000

On 5/2/2013 5:11 PM, Jari Arkko wrote:
>
>
>> IETF-stream and IRTF-streams are often considered peer-reviewed.
>>
>> Other streams may or may not be considered peer-reviewed (I would not consider IAB documents as such), but independent submissions are generally not (they only purpose of the one review they get is to make sure they're on-topic and not bogus).
>
> There are two review steps for the independent submissions, the ISR
> and the IESG review. I was under the impression that while the latter is
> just about non-conflict with the IETF process, the former would have
> looked at content and worthwhileness to publish. But I've never been a
> part of the review board, so I don't really know…

The information is here: http://www.rfc-editor.org/indsubs.html

ISR checks to make sure a doc is non-bogus and relevant to be an RFC.

IESG is a check on whether the doc should be part of the IETF process, 
or is somehow dangerous to the Internet in content.

But neither is a true content quality review as would be expected of a 
peer-review process.

> Anyway, not trying to deflect your main point but just wondering about this one detail.
>
> Also, IAB does publish documents with a comment period, but it is
> true that they are not obliged to take feedback into account, so in
> theory they are not peer reviewed while in practice they often are.

Any of us can solicit feedback and use that to make our documents better.

The IAB as a group decides what to publish and whether to incorporate 
comments, according to RFC 4845. That's self-publication, not peer review.

Joe

From touch@isi.edu  Thu May  2 21:03:27 2013
Return-Path: <touch@isi.edu>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA97921F9027 for <irtf-discuss@ietfa.amsl.com>; Thu,  2 May 2013 21:03:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.404
X-Spam-Level: 
X-Spam-Status: No, score=-104.404 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4,  SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HycUGSTBvjn9 for <irtf-discuss@ietfa.amsl.com>; Thu,  2 May 2013 21:03:23 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 8968E21F9026 for <irtf-discuss@irtf.org>; Thu,  2 May 2013 21:03:23 -0700 (PDT)
Received: from [192.168.1.97] (pool-71-105-87-221.lsanca.dsl-w.verizon.net [71.105.87.221]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r4342Ysb012401 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 2 May 2013 21:02:43 -0700 (PDT)
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.> <5182F84F.8000402@isi.edu> <2EF12BD5-908C-4D8C-81F2-C88B8AF52BA2@piuha.net> <51830554.6040604@isi.edu> <51832E10.9010101@gmail.com>
In-Reply-To: <51832E10.9010101@gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf-8
Message-Id: <1A457452-F465-4D07-9373-0061CC5EF81D@isi.edu>
X-Mailer: iPhone Mail (10B350)
From: Joe Touch <touch@isi.edu>
Date: Thu, 2 May 2013 21:02:33 -0700
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "bmanning@vacation.karoshi.com" <bmanning@vacation.karoshi.com>, Jari Arkko <jari.arkko@piuha.net>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: Re: [irtf-discuss] [rfc-i]  RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 04:03:27 -0000

On May 2, 2013, at 8:25 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> w=
rote:

> On 03/05/2013 12:31, Joe Touch wrote:
>>=20
>>=20
>> On 5/2/2013 5:11 PM, Jari Arkko wrote:
>>>=20
>>>=20
>>>> IETF-stream and IRTF-streams are often considered peer-reviewed.
>>>>=20
>>>> Other streams may or may not be considered peer-reviewed (I would not
>>>> consider IAB documents as such), but independent submissions are
>>>> generally not (they only purpose of the one review they get is to
>>>> make sure they're on-topic and not bogus).
>>>=20
>>> There are two review steps for the independent submissions, the ISR
>>> and the IESG review. I was under the impression that while the latter is=

>>> just about non-conflict with the IETF process, the former would have
>>> looked at content and worthwhileness to publish. But I've never been a
>>> part of the review board, so I don't really know=E2=80=A6
>>=20
>> The information is here: http://www.rfc-editor.org/indsubs.html
>>=20
>> ISR checks to make sure a doc is non-bogus and relevant to be an RFC.
>>=20
>> IESG is a check on whether the doc should be part of the IETF process,
>> or is somehow dangerous to the Internet in content.
>>=20
>> But neither is a true content quality review as would be expected of a
>> peer-review process.
>=20
> Joe, I don't know where you get that from.

I gave the URL.=20

> The ISE review is a peer review
> with the option of anonymity for the reviewer and feedback to the authors
> or to the RSE only.
>=20
> This is covered in the CCR article, and anyone trying to justify the
> academic credentials of the RFC series is welcome to cite the CCR
> article; that's why we wrote it.
> http://www.sigcomm.org/sites/default/files/ccr/papers/2010/January/1672308=
-1672315.pdf
>=20
>   Brian

RFC Editor website vs CCR article. =20

Joe

From brian.e.carpenter@gmail.com  Thu May  2 20:25:02 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9F3321F90F3 for <irtf-discuss@ietfa.amsl.com>; Thu,  2 May 2013 20:25:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.157
X-Spam-Level: 
X-Spam-Status: No, score=-102.157 tagged_above=-999 required=5 tests=[AWL=-0.357, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x5QL6pFmTwxW for <irtf-discuss@ietfa.amsl.com>; Thu,  2 May 2013 20:25:02 -0700 (PDT)
Received: from mail-da0-x231.google.com (mail-da0-x231.google.com [IPv6:2607:f8b0:400e:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 7701921F905B for <irtf-discuss@irtf.org>; Thu,  2 May 2013 20:24:59 -0700 (PDT)
Received: by mail-da0-f49.google.com with SMTP id p5so593447dak.8 for <irtf-discuss@irtf.org>; Thu, 02 May 2013 20:24:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ZuMTwBb+RfzHwv1Ak/aqpSRWvIqXAcIisWiz4bZagrs=; b=PgWV6PU7/kavjvSzGTFC7sr3w+zuZI8ugRBIaWcc8vSVy79ZlIORpES+bzQt6wSZPJ kRpryUwsqV3TnA/kCZ2MU1pek/KpKiwlJwPzDkE02/Xlvmrqu4pT1TSupfe8KwvIIYVG +VtZ1ri8fRZZZH7KoZHY6smB6NNocBZEwepaYEn1yEKxc/VE3bwYTFbTwjRWHURJXQxJ A5B9yELhrRg1HmaCV+rHwwFaTWQj2T5aKRuwqigtbJNnR/yAhase96spj+lrHf+T1jGh zN4GWj4JEgMSio52IH89krQqzGMoQdyEHFSybVhWsofL/vHHEuQ4ix/YVQSlT0E5y03J Oa3Q==
X-Received: by 10.66.235.3 with SMTP id ui3mr12804497pac.200.1367551499203; Thu, 02 May 2013 20:24:59 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id al2sm9749860pbc.25.2013.05.02.20.24.55 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 May 2013 20:24:57 -0700 (PDT)
Message-ID: <51832E10.9010101@gmail.com>
Date: Fri, 03 May 2013 15:25:04 +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: Joe Touch <touch@isi.edu>
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net>	<09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com>	<5177C089.1000904@cs.helsinki.fi>	<C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com>	<5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es>	<6.2.5.6.2.20130425015837.0b9aece0@resistor.net>	<51791F3E.6040707@it.uc3m.es>	<07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il>	<07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il>	<20130425140830.GA21669@vacation.karoshi.com.>	<5182F84F.8000402@isi.edu>	<2EF12BD5-908C-4D8C-81F2-C88B8AF52BA2@piuha.net> <51830554.6040604@isi.edu>
In-Reply-To: <51830554.6040604@isi.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 02 May 2013 22:33:43 -0700
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, bmanning@vacation.karoshi.com, Jari Arkko <jari.arkko@piuha.net>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: Re: [irtf-discuss] [rfc-i]  RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 03:25:03 -0000

On 03/05/2013 12:31, Joe Touch wrote:
>=20
>=20
> On 5/2/2013 5:11 PM, Jari Arkko wrote:
>>
>>
>>> IETF-stream and IRTF-streams are often considered peer-reviewed.
>>>
>>> Other streams may or may not be considered peer-reviewed (I would not=

>>> consider IAB documents as such), but independent submissions are
>>> generally not (they only purpose of the one review they get is to
>>> make sure they're on-topic and not bogus).
>>
>> There are two review steps for the independent submissions, the ISR
>> and the IESG review. I was under the impression that while the latter =
is
>> just about non-conflict with the IETF process, the former would have
>> looked at content and worthwhileness to publish. But I've never been a=

>> part of the review board, so I don't really know=E2=80=A6
>=20
> The information is here: http://www.rfc-editor.org/indsubs.html
>=20
> ISR checks to make sure a doc is non-bogus and relevant to be an RFC.
>=20
> IESG is a check on whether the doc should be part of the IETF process,
> or is somehow dangerous to the Internet in content.
>=20
> But neither is a true content quality review as would be expected of a
> peer-review process.

Joe, I don't know where you get that from. The ISE review is a peer revie=
w
with the option of anonymity for the reviewer and feedback to the authors=

or to the RSE only.

This is covered in the CCR article, and anyone trying to justify the
academic credentials of the RFC series is welcome to cite the CCR
article; that's why we wrote it.
http://www.sigcomm.org/sites/default/files/ccr/papers/2010/January/167230=
8-1672315.pdf

   Brian


From brian.e.carpenter@gmail.com  Thu May  2 22:35:23 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D64A21F8733 for <irtf-discuss@ietfa.amsl.com>; Thu,  2 May 2013 22:35:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.112
X-Spam-Level: 
X-Spam-Status: No, score=-102.112 tagged_above=-999 required=5 tests=[AWL=-0.312, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0TJUc2OyJ04K for <irtf-discuss@ietfa.amsl.com>; Thu,  2 May 2013 22:35:18 -0700 (PDT)
Received: from mail-pd0-f175.google.com (mail-pd0-f175.google.com [209.85.192.175]) by ietfa.amsl.com (Postfix) with ESMTP id D320421F85C3 for <irtf-discuss@irtf.org>; Thu,  2 May 2013 22:35:18 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id y14so737255pdi.20 for <irtf-discuss@irtf.org>; Thu, 02 May 2013 22:35:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=FFbGfkzMQitM7ZP3ZigGdbPX6X3jfZPYDblbeHHnVyA=; b=jIS6SaNrZzmUvm6EIPs4+KclHe1D2svfDvQRQYNUUOHQnlGO6MOrTVPd15ybm24YYo 8PWoZQnrMQRj7zJO4d7zYtb4ubmiDiRqAdFr7EyH0Nb3Ud3jKQgnGi09pqIKiOPEiKFY 67B5Ez/01fBoHfpLOLZo1kwbLhhrP+2Q49UDkgK52uqVJvPkqpuKHCPf0QW14sBg74sm KNMnny+Y3waZ6YuKaLsq6A3QCiRXRvphcHjVcX8i4Ye0PZgFciZIeBjQIrVR5cV9yspZ pfTxs622Lhxj6UnZ3kJ1ERWNIuBx8jsCERyUYaADMsxSLUYjKzi0IBMn2WByAEYLsv1o /xkA==
X-Received: by 10.68.224.65 with SMTP id ra1mr12185161pbc.103.1367559318591; Thu, 02 May 2013 22:35:18 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id uf2sm10191609pbc.41.2013.05.02.22.35.14 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 May 2013 22:35:17 -0700 (PDT)
Message-ID: <51834C97.1040209@gmail.com>
Date: Fri, 03 May 2013 17:35:19 +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: Joe Touch <touch@isi.edu>
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.> <5182F84F.8000402@isi.edu> <2EF12BD5-908C-4D8C-81F2-C88B8AF52BA2@piuha.net> <51830554.6040604@isi.edu> <51832E10.9010101@gmail.com> <1A457452-F465-4D07-9373-0061CC5EF81D@isi.edu>
In-Reply-To: <1A457452-F465-4D07-9373-0061CC5EF81D@isi.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "bmanning@vacation.karoshi.com" <bmanning@vacation.karoshi.com>, Jari Arkko <jari.arkko@piuha.net>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: Re: [irtf-discuss] [rfc-i]  RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 05:35:23 -0000

On 03/05/2013 16:02, Joe Touch wrote:
>=20
> On May 2, 2013, at 8:25 PM, Brian E Carpenter <brian.e.carpenter@gmail.=
com> wrote:
>=20
>> On 03/05/2013 12:31, Joe Touch wrote:
>>>
>>> On 5/2/2013 5:11 PM, Jari Arkko wrote:
>>>>
>>>>> IETF-stream and IRTF-streams are often considered peer-reviewed.
>>>>>
>>>>> Other streams may or may not be considered peer-reviewed (I would n=
ot
>>>>> consider IAB documents as such), but independent submissions are
>>>>> generally not (they only purpose of the one review they get is to
>>>>> make sure they're on-topic and not bogus).
>>>> There are two review steps for the independent submissions, the ISR
>>>> and the IESG review. I was under the impression that while the latte=
r is
>>>> just about non-conflict with the IETF process, the former would have=

>>>> looked at content and worthwhileness to publish. But I've never been=
 a
>>>> part of the review board, so I don't really know=E2=80=A6
>>> The information is here: http://www.rfc-editor.org/indsubs.html
>>>
>>> ISR checks to make sure a doc is non-bogus and relevant to be an RFC.=

>>>
>>> IESG is a check on whether the doc should be part of the IETF process=
,
>>> or is somehow dangerous to the Internet in content.
>>>
>>> But neither is a true content quality review as would be expected of =
a
>>> peer-review process.
>> Joe, I don't know where you get that from.
>=20
> I gave the URL.=20
>=20
>> The ISE review is a peer review
>> with the option of anonymity for the reviewer and feedback to the auth=
ors
>> or to the RSE only.
>>
>> This is covered in the CCR article, and anyone trying to justify the
>> academic credentials of the RFC series is welcome to cite the CCR
>> article; that's why we wrote it.
>> http://www.sigcomm.org/sites/default/files/ccr/papers/2010/January/167=
2308-1672315.pdf
>>
>>   Brian
>=20
> RFC Editor website vs CCR article. =20

I'm afraid I don't see the inconsistency.

    Brian


From touch@isi.edu  Thu May  2 23:03:37 2013
Return-Path: <touch@isi.edu>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A595521F9058 for <irtf-discuss@ietfa.amsl.com>; Thu,  2 May 2013 23:03:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.404
X-Spam-Level: 
X-Spam-Status: No, score=-104.404 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4,  SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FB4+99Qcfimh for <irtf-discuss@ietfa.amsl.com>; Thu,  2 May 2013 23:03:33 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 61EFB21F92EF for <irtf-discuss@irtf.org>; Thu,  2 May 2013 23:03:33 -0700 (PDT)
Received: from [192.168.1.97] (pool-71-105-87-221.lsanca.dsl-w.verizon.net [71.105.87.221]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r4362RxZ000093 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 2 May 2013 23:02:37 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.> <5182F84F.8000402@isi.edu> <2EF12BD5-908C-4D8C-81F2-C88B8AF52BA2@piuha.net> <51830554.6040604@isi.edu> <51832E10.9010101@gmail.com> <1A457452-F465-4D07-9373-0061CC5EF81D@isi.edu> <51834C97.1040209@gmail.com>
In-Reply-To: <51834C97.1040209@gmail.com>
Mime-Version: 1.0 (1.0)
Message-Id: <C8BA4BA7-8F0E-4093-B196-0774C855E0B2@isi.edu>
From: Joe Touch <touch@isi.edu>
Date: Thu, 2 May 2013 22:52:38 -0700
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: iPhone Mail (10B350)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "bmanning@vacation.karoshi.com" <bmanning@vacation.karoshi.com>, Jari Arkko <jari.arkko@piuha.net>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: Re: [irtf-discuss] [rfc-i]  RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 06:03:37 -0000

On May 2, 2013, at 10:35 PM, Brian E Carpenter <brian.e.carpenter@gmail.com>=
 wrote:

> On 03/05/2013 16:02, Joe Touch wrote:
>>=20
>> On May 2, 2013, at 8:25 PM, Brian E Carpenter <brian.e.carpenter@gmail.co=
m> wrote:
>>=20
>>> On 03/05/2013 12:31, Joe Touch wrote:
>>>>=20
>>>> On 5/2/2013 5:11 PM, Jari Arkko wrote:
>>>>>=20
>>>>>> IETF-stream and IRTF-streams are often considered peer-reviewed.
>>>>>>=20
>>>>>> Other streams may or may not be considered peer-reviewed (I would not=

>>>>>> consider IAB documents as such), but independent submissions are
>>>>>> generally not (they only purpose of the one review they get is to
>>>>>> make sure they're on-topic and not bogus).
>>>>> There are two review steps for the independent submissions, the ISR
>>>>> and the IESG review. I was under the impression that while the latter i=
s
>>>>> just about non-conflict with the IETF process, the former would have
>>>>> looked at content and worthwhileness to publish. But I've never been a=

>>>>> part of the review board, so I don't really know=E2=80=A6
>>>> The information is here: http://www.rfc-editor.org/indsubs.html
>>>>=20
>>>> ISR checks to make sure a doc is non-bogus and relevant to be an RFC.
>>>>=20
>>>> IESG is a check on whether the doc should be part of the IETF process,
>>>> or is somehow dangerous to the Internet in content.
>>>>=20
>>>> But neither is a true content quality review as would be expected of a
>>>> peer-review process.
>>> Joe, I don't know where you get that from.
>>=20
>> I gave the URL.=20
>>=20
>>> The ISE review is a peer review
>>> with the option of anonymity for the reviewer and feedback to the author=
s
>>> or to the RSE only.
>>>=20
>>> This is covered in the CCR article, and anyone trying to justify the
>>> academic credentials of the RFC series is welcome to cite the CCR
>>> article; that's why we wrote it.
>>> http://www.sigcomm.org/sites/default/files/ccr/papers/2010/January/16723=
08-1672315.pdf
>>>=20
>>>  Brian
>>=20
>> RFC Editor website vs CCR article. =20
>=20
> I'm afraid I don't see the inconsistency.
>=20
>    Brian

The web pages imply that everything in scope will be published, albeit if re=
vised. Peer review would include peer rejection for quality too.=20

Joe=

From hannes.tschofenig@nsn.com  Thu May  2 23:53:23 2013
Return-Path: <hannes.tschofenig@nsn.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA43921F93FE for <irtf-discuss@ietfa.amsl.com>; Thu,  2 May 2013 23:53:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.8
X-Spam-Level: 
X-Spam-Status: No, score=-105.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zLF8SLdkTd9I for <irtf-discuss@ietfa.amsl.com>; Thu,  2 May 2013 23:53:18 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 5EBED21F93F9 for <irtf-discuss@irtf.org>; Thu,  2 May 2013 23:53:18 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id r436rE7V006373 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 3 May 2013 08:53:14 +0200
Received: from USCHHTC002.nsn-intra.net ([10.159.161.15]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id r436r6Ma009100 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 3 May 2013 08:53:11 +0200
Received: from USCHHTC003.nsn-intra.net (10.159.161.16) by USCHHTC002.nsn-intra.net (10.159.161.15) with Microsoft SMTP Server (TLS) id 14.3.123.3; Fri, 3 May 2013 01:53:06 -0500
Received: from USCHMBX001.nsn-intra.net ([169.254.1.6]) by USCHHTC003.nsn-intra.net ([10.159.161.16]) with mapi id 14.03.0123.003; Fri, 3 May 2013 01:53:06 -0500
From: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
To: ext Joe Touch <touch@isi.edu>, "bmanning@vacation.karoshi.com" <bmanning@vacation.karoshi.com>
Thread-Topic: [irtf-discuss] RFCs accepted journal articles
Thread-Index: AQHOQQewU5dLBAzLAkej7xuo87WyRZjm8JOAgAAHvgCAADefAIAAA8aAgAAC2wCAABfrAIALnsyAgAAl03A=
Date: Fri, 3 May 2013 06:53:05 +0000
Message-ID: <1373E8CE237FCC43BCA36C6558612D2A9DFFC3@USCHMBX001.nsn-intra.net>
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.> <5182F84F.8000402@isi.edu>
In-Reply-To: <5182F84F.8000402@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.159.161.122]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 496
X-purgate-ID: 151667::1367563994-000076D0-FD0E3C1F/0-0/0-0
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: Re: [irtf-discuss] RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 06:53:24 -0000

> Other streams may or may not be considered peer-reviewed (I would not
> consider IAB documents as such), but independent submissions are
> generally not (they only purpose of the one review they get is to make
> sure they're on-topic and not bogus).

FWIW: There is a lot of review happening for IAB documents from the IAB its=
elf, from members in IAB programs (if the document belongs to a program) an=
d also from the IETF community since the documents are typically last calle=
d.

From touch@isi.edu  Fri May  3 10:26:37 2013
Return-Path: <touch@isi.edu>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CBEE21F973A for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 10:26:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.201
X-Spam-Level: 
X-Spam-Status: No, score=-99.201 tagged_above=-999 required=5 tests=[SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l7LVwA5FIcxX for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 10:26:31 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id AD0CA21F86F4 for <irtf-discuss@irtf.org>; Fri,  3 May 2013 09:46:10 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r43GjJKb005847 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 3 May 2013 09:45:19 -0700 (PDT)
Message-ID: <5183E990.6090208@isi.edu>
Date: Fri, 03 May 2013 09:45:04 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.> <5182F84F.8000402@isi.edu> <1373E8CE237FCC43BCA36C6558612D2A9DFFC3@USCHMBX001.nsn-intra.net> <5183E283.3080400@isi.edu> <CAMm+Lwj5nCyjULi=-t8hpwUetRf+VeK1FfaANvnm6A4u5QZV8g@mail.gmail.com>
In-Reply-To: <CAMm+Lwj5nCyjULi=-t8hpwUetRf+VeK1FfaANvnm6A4u5QZV8g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "bmanning@vacation.karoshi.com" <bmanning@vacation.karoshi.com>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: Re: [irtf-discuss] [rfc-i]  RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 17:26:37 -0000

On 5/3/2013 9:40 AM, Phillip Hallam-Baker wrote:
> Peer review is just another name for community feedback.

http://en.wikipedia.org/wiki/Peer_review

A key component is the significant potential for rejection.

> Yes I know they dress it up as something different but seriously, I 
> don't think I am the only person who has done peer review for academic 
> journals here. the only reason I have stopped doing peer review for 
> journals is that my policy is that if someone else is going to profit 
> from my work product then they have to pay me for it.

And yet you participate in the IETF?

> We all know where the literature is going. The UK has already 
> established the principle that all work that is supported by public 
> funds has to be available to the public without cost. That model is 
> going to win. The UK is more than big enough to establish critical 
> mass even if the for-profit publishers manage to stave off that type 
> of policy being imposed in the US by lobbying (i.e. bribing) congress.

I completely agree that the UK is big enough to drive global issues. 
That's why the US drives on the left.

Joe


From touch@isi.edu  Fri May  3 10:29:17 2013
Return-Path: <touch@isi.edu>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EE3A21F9748 for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 10:29:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.201
X-Spam-Level: 
X-Spam-Status: No, score=-99.201 tagged_above=-999 required=5 tests=[SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XQDsGc6Q6dXv for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 10:29:11 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id BB23221F8F43 for <irtf-discuss@irtf.org>; Fri,  3 May 2013 09:15:47 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r43GFCd9025523 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 3 May 2013 09:15:12 -0700 (PDT)
Message-ID: <5183E283.3080400@isi.edu>
Date: Fri, 03 May 2013 09:14:59 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.> <5182F84F.8000402@isi.edu> <1373E8CE237FCC43BCA36C6558612D2A9DFFC3@USCHMBX001.nsn-intra.net>
In-Reply-To: <1373E8CE237FCC43BCA36C6558612D2A9DFFC3@USCHMBX001.nsn-intra.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "bmanning@vacation.karoshi.com" <bmanning@vacation.karoshi.com>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: Re: [irtf-discuss] RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 17:29:17 -0000

On 5/2/2013 11:53 PM, Tschofenig, Hannes (NSN - FI/Espoo) wrote:
>> Other streams may or may not be considered peer-reviewed (I would not
>> consider IAB documents as such), but independent submissions are
>> generally not (they only purpose of the one review they get is to make
>> sure they're on-topic and not bogus).
>
> FWIW: There is a lot of review happening for IAB documents from the
> IAB itself, from members in IAB programs (if the document belongs to a
> program) and also from the IETF community since the documents are
> typically last called.

That's community feedback, not peer review.

Peer review includes a recommendation not to publish, and non-junk 
venues have rejection rates >50% (typically around 30% or less).

Joe

From yding@cs.helsinki.fi  Fri May  3 10:42:35 2013
Return-Path: <yding@cs.helsinki.fi>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B11421F8FED for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 10:42:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.201
X-Spam-Level: 
X-Spam-Status: No, score=-3.201 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YvHOvXUGTbcR for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 10:42:30 -0700 (PDT)
Received: from mail.cs.helsinki.fi (courier.cs.helsinki.fi [128.214.9.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FD7821F96FA for <irtf-discuss@irtf.org>; Fri,  3 May 2013 10:37:39 -0700 (PDT)
Received: from [192.168.93.127] (host-94-101-2-100.igua.fi [94.101.2.100]) (AUTH: PLAIN yding, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by mail.cs.helsinki.fi with esmtp; Fri, 03 May 2013 20:37:22 +0300 id 00068A78.5183F5D2.00001A2D
Message-ID: <5183F5D9.9020307@cs.helsinki.fi>
Date: Fri, 03 May 2013 20:37:29 +0300
From: Aaron Yi DING <yding@cs.helsinki.fi>
Organization: Helsinki Uni.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.> <5182F84F.8000402@isi.edu> <1373E8CE237FCC43BCA36C6558612D2A9DFFC3@USCHMBX001.nsn-intra.net> <5183E283.3080400@isi.edu>
In-Reply-To: <5183E283.3080400@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "bmanning@vacation.karoshi.com" <bmanning@vacation.karoshi.com>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: Re: [irtf-discuss] RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 17:42:35 -0000

On 03/05/2013 19:14, Joe Touch wrote:
> On 5/2/2013 11:53 PM, Tschofenig, Hannes (NSN - FI/Espoo) wrote:
>>> Other streams may or may not be considered peer-reviewed (I would not
>>> consider IAB documents as such), but independent submissions are
>>> generally not (they only purpose of the one review they get is to make
>>> sure they're on-topic and not bogus).
>>
>> FWIW: There is a lot of review happening for IAB documents from the
>> IAB itself, from members in IAB programs (if the document belongs to a
>> program) and also from the IETF community since the documents are
>> typically last called.
>
> That's community feedback, not peer review.
>
> Peer review includes a recommendation not to publish, and non-junk 
> venues have rejection rates >50% (typically around 30% or less).
>
> Joe


Reference here for instance

SIGCOMM
http://www.cs.ucsb.edu/~almeroth/conf/stats/#sigcomm 
<http://www.cs.ucsb.edu/%7Ealmeroth/conf/stats/#sigcomm>
MobiCom
http://www.cs.ucsb.edu/~almeroth/conf/stats/#mobicom 
<http://www.cs.ucsb.edu/%7Ealmeroth/conf/stats/#mobicom>
NSDI
http://www.cs.ucsb.edu/~almeroth/conf/stats/#nsdi 
<http://www.cs.ucsb.edu/%7Ealmeroth/conf/stats/#nsdi>

-- Aaron

From touch@isi.edu  Fri May  3 10:43:29 2013
Return-Path: <touch@isi.edu>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EC5521F842B for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 10:43:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.201
X-Spam-Level: 
X-Spam-Status: No, score=-99.201 tagged_above=-999 required=5 tests=[AWL=-0.000, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DTBz+qV5gY64 for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 10:43:23 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 6040A21F81FF for <irtf-discuss@irtf.org>; Fri,  3 May 2013 10:39:04 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r43HcKgp024078 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 3 May 2013 10:38:20 -0700 (PDT)
Message-ID: <5183F5FD.20806@isi.edu>
Date: Fri, 03 May 2013 10:38:05 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.> <5182F84F.8000402@isi.edu> <1373E8CE237FCC43BCA36C6558612D2A9DFFC3@USCHMBX001.nsn-intra.net> <5183E283.3080400@isi.edu> <CAMm+Lwj5nCyjULi=-t8hpwUetRf+VeK1FfaANvnm6A4u5QZV8g@mail.gmail.com> <5183E990.6090208@isi.edu> <CAMm+Lwi=vhe1=o__=q04FuMUU9PX816g2JpEVyNpOKf8O1rQ_Q@mail.gmail.com>
In-Reply-To: <CAMm+Lwi=vhe1=o__=q04FuMUU9PX816g2JpEVyNpOKf8O1rQ_Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "bmanning@vacation.karoshi.com" <bmanning@vacation.karoshi.com>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: Re: [irtf-discuss] [rfc-i]  RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 17:43:29 -0000

On 5/3/2013 9:58 AM, Phillip Hallam-Baker wrote:
> I am not a 'free software' zealot. I have never had a problem with 
> someone taking my designs and implementing them.
>
> What sticks in my craw is when people propose that they take my work, 
> make it their exclusive property and limit access to it. That does not 
> add any value to me.

So how do you feel when you provide advice or feedback to corporate IETF 
participants and they later reveal they own IPR on that protocol?

Joe

From hallam@gmail.com  Fri May  3 10:19:55 2013
Return-Path: <hallam@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4057821F9745 for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 10:19:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.4
X-Spam-Level: 
X-Spam-Status: No, score=0.4 tagged_above=-999 required=5 tests=[AWL=-0.400, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CmQWtn6+NsJ9 for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 10:19:54 -0700 (PDT)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 2F2A121F997F for <irtf-discuss@irtf.org>; Fri,  3 May 2013 09:40:25 -0700 (PDT)
Received: by mail-we0-f174.google.com with SMTP id z2so1458377wey.5 for <irtf-discuss@irtf.org>; Fri, 03 May 2013 09:40:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=BMsztvArNudqSb43FJY5lBQ3Bb166Z1PkPKtw6KID4Y=; b=m31GNfwLFSi4+XmTUraBfzdEnb4aNfR3rB1SjA6SsFx3oFioWpyeDsiaDF3cpVLMh2 EoaEzm/1Nmk/nv4vloiFIpeXbwJ3B+AzapuMRJZ5ZytBS45E0ps8STETHDsw3a53WKfr zjvdNGVmtMls70r0vqz+YYpUAOHdnMzD2XIaFzP3HrNWDrzdwXOdtMBSztEuFDhtR8vR 4YArRVpmCfrbV4OAnQSMvf7/G+Dy9wG16ZcvMFZbgsHHl1DzWwGql3bjfdR34bQ3vlPi RyzsYCAF0cgDnoNDCrADaJowlYea8OVWzZQsckb4gbK3g/dlQOU2egwPNEEyupvc6nef C8YQ==
MIME-Version: 1.0
X-Received: by 10.194.62.174 with SMTP id z14mr15016921wjr.20.1367599224242; Fri, 03 May 2013 09:40:24 -0700 (PDT)
Received: by 10.194.121.161 with HTTP; Fri, 3 May 2013 09:40:24 -0700 (PDT)
In-Reply-To: <5183E283.3080400@isi.edu>
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.> <5182F84F.8000402@isi.edu> <1373E8CE237FCC43BCA36C6558612D2A9DFFC3@USCHMBX001.nsn-intra.net> <5183E283.3080400@isi.edu>
Date: Fri, 3 May 2013 12:40:24 -0400
Message-ID: <CAMm+Lwj5nCyjULi=-t8hpwUetRf+VeK1FfaANvnm6A4u5QZV8g@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Joe Touch <touch@isi.edu>
Content-Type: multipart/alternative; boundary=047d7b86d6d8f4cb8304dbd30144
X-Mailman-Approved-At: Fri, 03 May 2013 10:53:49 -0700
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "bmanning@vacation.karoshi.com" <bmanning@vacation.karoshi.com>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: Re: [irtf-discuss] [rfc-i]  RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 17:19:55 -0000

--047d7b86d6d8f4cb8304dbd30144
Content-Type: text/plain; charset=ISO-8859-1

Peer review is just another name for community feedback.

Yes I know they dress it up as something different but seriously, I don't
think I am the only person who has done peer review for academic journals
here. the only reason I have stopped doing peer review for journals is that
my policy is that if someone else is going to profit from my work product
then they have to pay me for it.


We all know where the literature is going. The UK has already established
the principle that all work that is supported by public funds has to be
available to the public without cost. That model is going to win. The UK is
more than big enough to establish critical mass even if the for-profit
publishers manage to stave off that type of policy being imposed in the US
by lobbying (i.e. bribing) congress.

There will be an interesting transition process but the reputation of a
journal is only as good as the people who write for it. A lot of for-profit
journals will disappear and a lot of not-for-profit institutions that fund
themselves through publishing overpriced journals to academic libraries are
going to be in doo-doo even deeper than the newspapers are right now. The
paper journals that die will be quickly replaced by online journals
supported by open source workflow tools, many of which have the same
editorial boards as the ones that are pushed under.

The journal publishers are intermediaries that do not add value. They are
facing a disruptive change in their business model and they have absolutely
no chance of survival. None.

[And remember that I am not an open source zealot by any means]


So while I think it is good that we support the academics here, I don't
think we should worry too much about the extent to which it is going to
help them. Any tenure committee that is deciding a position in computer
networking that is not capable of evaluating the worth of a technical paper
on its own merits has no business being a tenure committee. They should
resign and take emeritus immediately.

When I looked at various frauds being perpetrated in the reputation systems
for online auctions and the like, my starting point was my experience of
the well known and long practiced frauds in 'peer-review'. Almost no peer
review is anonymous in a meaningful sense. Everyone who is established in
their field has a pretty good idea of what everyone else works on and what
their pet ideas are. The link spamming schemes designed to foil search
engine rankings were anticipated by decades by the citation cartels that
infest most of the literature.


I don't think we should worry unduly about the old system. Do whatever is
necessary to at least have the information being tracked. The review we
give is at least as good as 'academic' peer review. The people who are
trying to insist on a distinction are the legacy journal publishers who are
about to lose their entire market.

--047d7b86d6d8f4cb8304dbd30144
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Peer review is just another name for community feedback.<d=
iv><br></div><div style>Yes I know they dress it up as something different =
but seriously, I don&#39;t think I am the only person who has done peer rev=
iew for academic journals here. the only reason I have stopped doing peer r=
eview for journals is that my policy is that if someone else is going to pr=
ofit from my work product then they have to pay me for it.</div>
<div style><br></div><div style><br></div><div style>We all know where the =
literature is going. The UK has already established the principle that all =
work that is supported by public funds has to be available to the public wi=
thout cost. That model is going to win. The UK is more than big enough to e=
stablish critical mass even if the for-profit publishers manage to stave of=
f that type of policy being imposed in the US by lobbying (i.e. bribing) co=
ngress.=A0</div>
<div style><br></div><div style>There will be an interesting transition pro=
cess but the reputation of a journal is only as good as the people who writ=
e for it. A lot of for-profit journals will disappear and a lot of not-for-=
profit institutions that fund themselves through publishing overpriced jour=
nals to academic libraries are going to be in doo-doo even deeper than the =
newspapers are right now. The paper journals that die will be quickly repla=
ced by online journals supported by open source workflow tools, many of whi=
ch have the same editorial boards as the ones that are pushed under.</div>
<div style><br></div><div style>The journal publishers are intermediaries t=
hat do not add value. They are facing a disruptive change in their business=
 model and they have absolutely no chance of survival. None.</div><div styl=
e>
<br></div><div style>[And remember that I am not an open source zealot by a=
ny means]</div><div style><br></div><div style><br></div><div style>So whil=
e I think it is good that we support the academics here, I don&#39;t think =
we should worry too much about the extent to which it is going to help them=
. Any tenure committee that is deciding a position in computer networking t=
hat is not capable of evaluating the worth of a technical paper on its own =
merits has no business being a tenure committee. They should resign and tak=
e emeritus immediately.</div>
<div style><br></div><div style>When I looked at various frauds being perpe=
trated in the reputation systems for online auctions and the like, my start=
ing point was my experience of the well known and long practiced frauds in =
&#39;peer-review&#39;. Almost no peer review is anonymous in a meaningful s=
ense. Everyone who is established in their field has a pretty good idea of =
what everyone else works on and what their pet ideas are. The link spamming=
 schemes designed to foil search engine rankings were anticipated by decade=
s by the citation cartels that infest most of the literature.</div>
<div style><br></div><div style><br></div><div style>I don&#39;t think we s=
hould worry unduly about the old system. Do whatever is necessary to at lea=
st have the information being tracked. The review we give is at least as go=
od as &#39;academic&#39; peer review. The people who are trying to insist o=
n a distinction are the legacy journal publishers who are about to lose the=
ir entire market.</div>
<div style><br></div><div style><br></div></div>

--047d7b86d6d8f4cb8304dbd30144--

From hallam@gmail.com  Fri May  3 10:29:47 2013
Return-Path: <hallam@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2B2721F964C for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 10:29:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.533
X-Spam-Level: 
X-Spam-Status: No, score=0.533 tagged_above=-999 required=5 tests=[AWL=-0.266,  HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cGIMCn3yGN9Q for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 10:29:46 -0700 (PDT)
Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) by ietfa.amsl.com (Postfix) with ESMTP id 5F1E621F8201 for <irtf-discuss@irtf.org>; Fri,  3 May 2013 09:58:47 -0700 (PDT)
Received: by mail-wg0-f50.google.com with SMTP id m15so1826749wgh.5 for <irtf-discuss@irtf.org>; Fri, 03 May 2013 09:58:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=UeQwIFgfevwIha/9/CIQwCubivht09MOtFG9xH7tKFE=; b=SV56nDpFpgid9Vo/6Octn/7EZOtaqH1hpMuIujsEDNO3AcpoRTTzHPpNyEAKSItcWP U78YqTZ6QVAoRE12ZKsZ10Rr+ZU0sgyRHWnWDQ8xaJuQNzDZmVOKxLzI0a/ibaribyEe yUeZVAEoqbD0mkADDWs+Sx6bCgWTDcDtmOlTqolWOHGm1Ma4x3cAewZtVuAXNHTJRQiz DGpUvxpRjluI5WEySRkR3fZ8f2jkaGamYmB99M1M6hE+HkhdX25u96bxbhAWluUu7xCD tutfoWb8cpZIQ+tA+ovCLkybwKqzyrZbiyeeC5uk90uausDPTaR+7slj1Skg9O2bIKHy ctnQ==
MIME-Version: 1.0
X-Received: by 10.194.62.174 with SMTP id z14mr15100125wjr.20.1367600314849; Fri, 03 May 2013 09:58:34 -0700 (PDT)
Received: by 10.194.121.161 with HTTP; Fri, 3 May 2013 09:58:34 -0700 (PDT)
In-Reply-To: <5183E990.6090208@isi.edu>
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.> <5182F84F.8000402@isi.edu> <1373E8CE237FCC43BCA36C6558612D2A9DFFC3@USCHMBX001.nsn-intra.net> <5183E283.3080400@isi.edu> <CAMm+Lwj5nCyjULi=-t8hpwUetRf+VeK1FfaANvnm6A4u5QZV8g@mail.gmail.com> <5183E990.6090208@isi.edu>
Date: Fri, 3 May 2013 12:58:34 -0400
Message-ID: <CAMm+Lwi=vhe1=o__=q04FuMUU9PX816g2JpEVyNpOKf8O1rQ_Q@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Joe Touch <touch@isi.edu>
Content-Type: multipart/alternative; boundary=047d7b86d6d8f6500e04dbd34207
X-Mailman-Approved-At: Fri, 03 May 2013 10:53:50 -0700
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "bmanning@vacation.karoshi.com" <bmanning@vacation.karoshi.com>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: Re: [irtf-discuss] [rfc-i]  RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 17:29:47 -0000

--047d7b86d6d8f6500e04dbd34207
Content-Type: text/plain; charset=ISO-8859-1

Well first off I am actually paid to participate in IETF, so it isn't an
issue.

I did participate in IETF while I was retired but that was because:

* IETF did not charge me to participate
* IETF makes my immediate work product (specifications) available at no
charge
* I couldn't spend all my time making daleks even if I wanted to


I am not a 'free software' zealot. I have never had a problem with someone
taking my designs and implementing them.

What sticks in my craw is when people propose that they take my work, make
it their exclusive property and limit access to it. That does not add any
value to me.



On Fri, May 3, 2013 at 12:45 PM, Joe Touch <touch@isi.edu> wrote:

>
> On 5/3/2013 9:40 AM, Phillip Hallam-Baker wrote:
>
>> Peer review is just another name for community feedback.
>>
>
> http://en.wikipedia.org/wiki/**Peer_review<http://en.wikipedia.org/wiki/Peer_review>
>
> A key component is the significant potential for rejection.
>
>
>  Yes I know they dress it up as something different but seriously, I don't
>> think I am the only person who has done peer review for academic journals
>> here. the only reason I have stopped doing peer review for journals is that
>> my policy is that if someone else is going to profit from my work product
>> then they have to pay me for it.
>>
>
> And yet you participate in the IETF?
>
>
>  We all know where the literature is going. The UK has already established
>> the principle that all work that is supported by public funds has to be
>> available to the public without cost. That model is going to win. The UK is
>> more than big enough to establish critical mass even if the for-profit
>> publishers manage to stave off that type of policy being imposed in the US
>> by lobbying (i.e. bribing) congress.
>>
>
> I completely agree that the UK is big enough to drive global issues.
> That's why the US drives on the left.
>
> Joe
>
>


-- 
Website: http://hallambaker.com/

--047d7b86d6d8f6500e04dbd34207
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Well first off I am actually paid to participate in IETF, =
so it isn&#39;t an issue.<div><br></div><div style>I did participate in IET=
F while I was retired but that was because:</div><div style><br></div><div =
style>
* IETF did not charge me to participate</div><div style>* IETF makes my imm=
ediate work product (specifications) available at no charge</div><div style=
>* I couldn&#39;t spend all my time making daleks even if I wanted to</div>
<div style><br></div><div style><br></div><div style>I am not a &#39;free s=
oftware&#39; zealot. I have never had a problem with someone taking my desi=
gns and implementing them.</div><div style><br></div><div style>What sticks=
 in my craw is when people propose that they take my work, make it their ex=
clusive property and limit access to it. That does not add any value to me.=
=A0</div>
<div style><br></div></div><div class=3D"gmail_extra"><br><br><div class=3D=
"gmail_quote">On Fri, May 3, 2013 at 12:45 PM, Joe Touch <span dir=3D"ltr">=
&lt;<a href=3D"mailto:touch@isi.edu" target=3D"_blank">touch@isi.edu</a>&gt=
;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><br>
On 5/3/2013 9:40 AM, Phillip Hallam-Baker wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Peer review is just another name for community feedback.<br>
</blockquote>
<br>
</div><a href=3D"http://en.wikipedia.org/wiki/Peer_review" target=3D"_blank=
">http://en.wikipedia.org/wiki/<u></u>Peer_review</a><br>
<br>
A key component is the significant potential for rejection.<div class=3D"im=
"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Yes I know they dress it up as something different but seriously, I don&#39=
;t think I am the only person who has done peer review for academic journal=
s here. the only reason I have stopped doing peer review for journals is th=
at my policy is that if someone else is going to profit from my work produc=
t then they have to pay me for it.<br>

</blockquote>
<br></div>
And yet you participate in the IETF?<div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
We all know where the literature is going. The UK has already established t=
he principle that all work that is supported by public funds has to be avai=
lable to the public without cost. That model is going to win. The UK is mor=
e than big enough to establish critical mass even if the for-profit publish=
ers manage to stave off that type of policy being imposed in the US by lobb=
ying (i.e. bribing) congress.<br>

</blockquote>
<br></div>
I completely agree that the UK is big enough to drive global issues. That&#=
39;s why the US drives on the left.<span class=3D"HOEnZb"><font color=3D"#8=
88888"><br>
<br>
Joe<br>
<br>
</font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b=
r>Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><=
br>
</div>

--047d7b86d6d8f6500e04dbd34207--

From hallam@gmail.com  Fri May  3 11:24:18 2013
Return-Path: <hallam@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A8F021F9679 for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 11:24:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.7
X-Spam-Level: 
X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[AWL=1.100, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZHyQU0EhJU4a for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 11:24:05 -0700 (PDT)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 16C3621F9668 for <irtf-discuss@irtf.org>; Fri,  3 May 2013 11:23:40 -0700 (PDT)
Received: by mail-we0-f174.google.com with SMTP id z2so1528217wey.19 for <irtf-discuss@irtf.org>; Fri, 03 May 2013 11:23:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ZoQM5NtQ0FgxxkDuJCVLiAuDmwCA7o3L4pq2SRcqtzY=; b=043oPKTjZBbmXOt/OVICvU7OYbzk1GAFPDVMBfKN/6xxgifyqn/dLILF46RMSlfRAe XwwhHiGj4oOPMlK5Fws6QY4xmy+SE9T1LTtnaDNgIwof8GeYazdsKvLYaEDD5JpVrR32 MusOqfvxk6OXkZpctlxgS4uGNKYkDtP0wul7Fhv7Tp9dcpDvtOMqfx7nS0IBnkhKC+GY 3IarmU5lxBHQQv9jfhzEYMCMrJjZTGdcqmIM1gINP8GcgZb+sumoSAM3LIjZSbFqv8B0 /DHxIfnErqRrIi8z0mSpYAXGzNJ89CDSsYZQyQ3v1r+2CTaUFEtkadZOBbRWlCrVpOxc vBhw==
MIME-Version: 1.0
X-Received: by 10.194.62.174 with SMTP id z14mr15497411wjr.20.1367605418663; Fri, 03 May 2013 11:23:38 -0700 (PDT)
Received: by 10.194.121.161 with HTTP; Fri, 3 May 2013 11:23:38 -0700 (PDT)
In-Reply-To: <5183F5FD.20806@isi.edu>
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.> <5182F84F.8000402@isi.edu> <1373E8CE237FCC43BCA36C6558612D2A9DFFC3@USCHMBX001.nsn-intra.net> <5183E283.3080400@isi.edu> <CAMm+Lwj5nCyjULi=-t8hpwUetRf+VeK1FfaANvnm6A4u5QZV8g@mail.gmail.com> <5183E990.6090208@isi.edu> <CAMm+Lwi=vhe1=o__=q04FuMUU9PX816g2JpEVyNpOKf8O1rQ_Q@mail.gmail.com> <5183F5FD.20806@isi.edu>
Date: Fri, 3 May 2013 14:23:38 -0400
Message-ID: <CAMm+Lwj5AyM6+gOj+jPqpc1x6Qj5f7GSa5UzYxbydZTGW22ALQ@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Joe Touch <touch@isi.edu>
Content-Type: multipart/alternative; boundary=047d7b86d6d82c261504dbd47370
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "bmanning@vacation.karoshi.com" <bmanning@vacation.karoshi.com>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: Re: [irtf-discuss] [rfc-i]  RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 18:24:18 -0000

--047d7b86d6d82c261504dbd47370
Content-Type: text/plain; charset=ISO-8859-1

On Fri, May 3, 2013 at 1:38 PM, Joe Touch <touch@isi.edu> wrote:

>
> On 5/3/2013 9:58 AM, Phillip Hallam-Baker wrote:
>
>> I am not a 'free software' zealot. I have never had a problem with
>> someone taking my designs and implementing them.
>>
>> What sticks in my craw is when people propose that they take my work,
>> make it their exclusive property and limit access to it. That does not add
>> any value to me.
>>
>
> So how do you feel when you provide advice or feedback to corporate IETF
> participants and they later reveal they own IPR on that protocol?
>

That is the reason that I think WGs should specify their IPR policy for
contributions when they are formed. I find it completely unacceptable.

I do have pending patent applications that might eventually appear in IETF
as proposed standards but if I submit them I will certainly be telling
people that I have the claims or else how are they going to know to pay me?
If someone has a patent though, they should probably write the specs at
their own expense and submit as individual submissions so the documents can
be recorded and tracked. IETF process is not really suited to a case where
one party has essential controlling patent claims and would be useless if
there were conflicting claims.


Unfortunately, that is the problem that the IETF IPR policy attempts to
address which is not the same as the principal IPR problems we face. And
the cost of policy compliance is still very high.

Intentional abuse of IETF process by actual IETF participants is a very
rare event if it has happened at all. Much more common problems are:

* Participant files 'defensive' patents, goes bust or otherwise loses
control of the IPR which is bought by a troll.

* Participant has IPR that is relevant but not critical to a proposal but
their legal department is unwilling to consider reasonable commercial terms
for making it available.

* A patent applicant reads traffic on IETF mailing lists and either files a
new patent with claims covering the ideas or adds claims to a continuation
in part of an existing patent application.

* An IPR holder files a bad faith patent suit knowing that it is going to
be much less expensive for the targets to settle than to defend the suit.

* Some participants in a WG have obtained a license for certain IPR and
they attempt to forestall competition that have not obtained licenses by
making it essential to the specification.


I have encountered all the above numerous times.

-- 
Website: http://hallambaker.com/

--047d7b86d6d82c261504dbd47370
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Fri, May 3, 2013 at 1:38 PM, Joe Touch <span dir=3D"ltr=
">&lt;<a href=3D"mailto:touch@isi.edu" target=3D"_blank">touch@isi.edu</a>&=
gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div class=3D"im"><br>
On 5/3/2013 9:58 AM, Phillip Hallam-Baker wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I am not a &#39;free software&#39; zealot. I have never had a problem with =
someone taking my designs and implementing them.<br>
<br>
What sticks in my craw is when people propose that they take my work, make =
it their exclusive property and limit access to it. That does not add any v=
alue to me.<br>
</blockquote>
<br></div>
So how do you feel when you provide advice or feedback to corporate IETF pa=
rticipants and they later reveal they own IPR on that protocol?<span class=
=3D"HOEnZb"><font color=3D"#888888"><br></font></span></blockquote></div><d=
iv>
<br></div><div style>That is the reason that I think WGs should specify the=
ir IPR policy for contributions when they are formed. I find it completely =
unacceptable.</div><div style><br></div><div style>I do have pending patent=
 applications that might eventually appear in IETF as proposed standards bu=
t if I submit them I will certainly be telling people that I have the claim=
s or else how are they going to know to pay me? If someone has a patent tho=
ugh, they should probably write the specs at their own expense and submit a=
s individual submissions so the documents can be recorded and tracked. IETF=
 process is not really suited to a case where one party has essential contr=
olling patent claims and would be useless if there were conflicting claims.=
</div>
<div style><br></div><div style><br></div><div style>Unfortunately, that is=
 the problem that the IETF IPR policy attempts to address which is not the =
same as the principal IPR problems we face. And the cost of policy complian=
ce is still very high.</div>
<div style><br></div><div style>Intentional abuse of IETF process by actual=
 IETF participants is a very rare event if it has happened at all. Much mor=
e common problems are:</div><div style><br></div><div style>* Participant f=
iles &#39;defensive&#39; patents, goes bust or otherwise loses control of t=
he IPR which is bought by a troll.</div>
<div style><br></div><div style>* Participant has IPR that is relevant but =
not critical to a proposal but their legal department is unwilling to consi=
der reasonable commercial terms for making it available.</div><div style>
<br></div><div style>* A patent applicant reads traffic on IETF mailing lis=
ts and either files a new patent with claims covering the ideas or adds cla=
ims to a continuation in part of an existing patent application.=A0</div>
<div style><br></div><div style>* An IPR holder files a bad faith patent su=
it knowing that it is going to be much less expensive for the targets to se=
ttle than to defend the suit.</div><div style><br></div><div style>* Some p=
articipants in a WG have obtained a license for certain IPR and they attemp=
t to forestall competition that have not obtained licenses by making it ess=
ential to the specification.</div>
<div style><br></div><div style><br></div><div style>I have encountered all=
 the above numerous times.</div><div><br></div>-- <br>Website: <a href=3D"h=
ttp://hallambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--047d7b86d6d82c261504dbd47370--

From brian.e.carpenter@gmail.com  Fri May  3 13:09:04 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4E2821F88D8 for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 13:09:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.8
X-Spam-Level: 
X-Spam-Status: No, score=-102.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oHr1Ga13yfh0 for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 13:09:00 -0700 (PDT)
Received: from mail-pa0-f41.google.com (mail-pa0-f41.google.com [209.85.220.41]) by ietfa.amsl.com (Postfix) with ESMTP id 0E58E21F894E for <irtf-discuss@irtf.org>; Fri,  3 May 2013 13:09:00 -0700 (PDT)
Received: by mail-pa0-f41.google.com with SMTP id rl6so1107490pac.28 for <irtf-discuss@irtf.org>; Fri, 03 May 2013 13:08:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=218nMGZtbkEUX0T/fC7YGqWkfzH2rxnyJN3HZwTWmtY=; b=XLXA4JKRvqLL+Mj/ziChPMy/gHqbu1rHmJnrccYRdqhWUEN2bT7PxuuxtWOEszGKSH l7K9RzXp8UtAqVGLHW4hdrtjAqMpvMqyNukpGsHEiNP8xWFtc5NrHI3C4/sKaY4xCjyf 06nrUoCf3IQ4+Df3xYRaxaYDhgD7KbZGOG4wkqapbaGiyNFhQqTawSqBcQGZZ3yAuFAo s80OORzb3Q0f6kDv/TiBiS6Ma/dHPKu3WbhAdtLAul3uK2WeF57Bc7b2rHNGABHooeaD Mpoa/3rmV3paxOVO9H512G5FCR9J1YnjDvHf1raz1t8/IJnf13GyNYQJLcundethxdEE Hi8g==
X-Received: by 10.66.232.230 with SMTP id tr6mr16724616pac.83.1367611739743; Fri, 03 May 2013 13:08:59 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id wz9sm12857604pbc.5.2013.05.03.13.08.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 May 2013 13:08:57 -0700 (PDT)
Message-ID: <5184195D.8050809@gmail.com>
Date: Sat, 04 May 2013 08:09:01 +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: Joe Touch <touch@isi.edu>
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.> <5182F84F.8000402@isi.edu> <2EF12BD5-908C-4D8C-81F2-C88B8AF52BA2@piuha.net> <51830554.6040604@isi.edu> <51832E10.9010101@gmail.com> <1A457452-F465-4D07-9373-0061CC5EF81D@isi.edu> <51834C97.1040209@gmail.com> <C8BA4BA7-8F0E-4093-B196-0774C855E0B2@isi.edu>
In-Reply-To: <C8BA4BA7-8F0E-4093-B196-0774C855E0B2@isi.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "bmanning@vacation.karoshi.com" <bmanning@vacation.karoshi.com>, Jari Arkko <jari.arkko@piuha.net>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: Re: [irtf-discuss] [rfc-i]  RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 20:09:04 -0000

One final comment at the end...

On 03/05/2013 17:52, Joe Touch wrote:
>=20
> On May 2, 2013, at 10:35 PM, Brian E Carpenter <brian.e.carpenter@gmail=
=2Ecom> wrote:
>=20
>> On 03/05/2013 16:02, Joe Touch wrote:
>>> On May 2, 2013, at 8:25 PM, Brian E Carpenter <brian.e.carpenter@gmai=
l.com> wrote:
>>>
>>>> On 03/05/2013 12:31, Joe Touch wrote:
>>>>> On 5/2/2013 5:11 PM, Jari Arkko wrote:
>>>>>>> IETF-stream and IRTF-streams are often considered peer-reviewed.
>>>>>>>
>>>>>>> Other streams may or may not be considered peer-reviewed (I would=
 not
>>>>>>> consider IAB documents as such), but independent submissions are
>>>>>>> generally not (they only purpose of the one review they get is to=

>>>>>>> make sure they're on-topic and not bogus).
>>>>>> There are two review steps for the independent submissions, the IS=
R
>>>>>> and the IESG review. I was under the impression that while the lat=
ter is
>>>>>> just about non-conflict with the IETF process, the former would ha=
ve
>>>>>> looked at content and worthwhileness to publish. But I've never be=
en a
>>>>>> part of the review board, so I don't really know=E2=80=A6
>>>>> The information is here: http://www.rfc-editor.org/indsubs.html
>>>>>
>>>>> ISR checks to make sure a doc is non-bogus and relevant to be an RF=
C.
>>>>>
>>>>> IESG is a check on whether the doc should be part of the IETF proce=
ss,
>>>>> or is somehow dangerous to the Internet in content.
>>>>>
>>>>> But neither is a true content quality review as would be expected o=
f a
>>>>> peer-review process.
>>>> Joe, I don't know where you get that from.
>>> I gave the URL.=20
>>>
>>>> The ISE review is a peer review
>>>> with the option of anonymity for the reviewer and feedback to the au=
thors
>>>> or to the RSE only.
>>>>
>>>> This is covered in the CCR article, and anyone trying to justify the=

>>>> academic credentials of the RFC series is welcome to cite the CCR
>>>> article; that's why we wrote it.
>>>> http://www.sigcomm.org/sites/default/files/ccr/papers/2010/January/1=
672308-1672315.pdf
>>>>
>>>>  Brian
>>> RFC Editor website vs CCR article. =20
>> I'm afraid I don't see the inconsistency.
>>
>>    Brian
>=20
> The web pages imply that everything in scope will be published, albeit =
if revised. Peer review would include peer rejection for quality too.=20

In that case the web pages miss out an important fact: the ISE sometimes =
says "No".

    Brian


From touch@isi.edu  Fri May  3 13:29:48 2013
Return-Path: <touch@isi.edu>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6B4721F9298 for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 13:29:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.501
X-Spam-Level: 
X-Spam-Status: No, score=-100.501 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bHMAnVAZIafC for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 13:29:43 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 346A121F9080 for <irtf-discuss@irtf.org>; Fri,  3 May 2013 13:29:43 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r43KTWXU003225 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 3 May 2013 13:29:32 -0700 (PDT)
Message-ID: <51841E1D.8040703@isi.edu>
Date: Fri, 03 May 2013 13:29:17 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Nico Williams <nico@cryptonector.com>
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.> <5182F84F.8000402@isi.edu> <2EF12BD5-908C-4D8C-81F2-C88B8AF52BA2@piuha.net> <51830554.6040604@isi.edu> <51832E10.9010101@gmail.com> <1A457452-F465-4D07-9373-0061CC5EF81D@isi.edu> <51834C97.1040209@gmail.com> <C8BA4BA7-8F0E-4093-B196-0774C855E0B2@isi.edu> <5184195D.8050809@gmail.com> <CAK3OfOg1h-QNRVXYsgvJwQAsOeejNE_HD00L3DMLTsHchsLSEA@mail.gmail.com>
In-Reply-To: <CAK3OfOg1h-QNRVXYsgvJwQAsOeejNE_HD00L3DMLTsHchsLSEA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "bmanning@vacation.karoshi.com" <bmanning@vacation.karoshi.com>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [irtf-discuss] [rfc-i]  RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 20:29:49 -0000

On 5/3/2013 1:14 PM, Nico Williams wrote:
> And the IESG can request that the RFC-Editor not publish.

Only for dangerous or end-run around IETF process. Not for mere quality 
issues.

Joe

From hallam@gmail.com  Fri May  3 14:01:30 2013
Return-Path: <hallam@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C6C221F91B0 for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 14:01:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.087
X-Spam-Level: 
X-Spam-Status: No, score=-0.087 tagged_above=-999 required=5 tests=[AWL=0.047,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_HTML_USL_OBFU=1.666, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OFMEEDvdlMpJ for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 14:01:29 -0700 (PDT)
Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id E125221F9113 for <irtf-discuss@irtf.org>; Fri,  3 May 2013 14:01:28 -0700 (PDT)
Received: by mail-we0-f177.google.com with SMTP id u3so1626079wey.22 for <irtf-discuss@irtf.org>; Fri, 03 May 2013 14:01:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=uMCbYX07GPMl/Q9fH0x/SkFLQaHG/szkKTZ+xRvUyd0=; b=aFttZF1YbvALziKEGXldtMYeTfHPHikFMl37+xzGrWQJqt3dMy4wOhXV36mgXu5QVy u/Q0RfLqTY8aEEFZR7KvRIdDE5plJ358nbmMQkcj+TW+KctIDVpdlCJ2FBUu6OzIFglc sxUGddBIB36uNGel5zNQLynxv6oXjJjvIAuNkojQmAXZKRr8o89IgzQc17v4ntvQaET1 bSANWF/5ZxCEzidSwR1wgKIJLFxH0BREMVUAfM7g6nVLnEB5DpeFmuEM0JBYleoxndV/ ssTINvKXsCbesZgTWMLLhOyzwK7q8EhNzSzhwXB6y4keQpl7zXtfcaUPr/bAU0LAZfiF MkHQ==
MIME-Version: 1.0
X-Received: by 10.194.58.163 with SMTP id s3mr16130499wjq.6.1367614887794; Fri, 03 May 2013 14:01:27 -0700 (PDT)
Received: by 10.194.121.161 with HTTP; Fri, 3 May 2013 14:01:27 -0700 (PDT)
In-Reply-To: <51841E1D.8040703@isi.edu>
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.> <5182F84F.8000402@isi.edu> <2EF12BD5-908C-4D8C-81F2-C88B8AF52BA2@piuha.net> <51830554.6040604@isi.edu> <51832E10.9010101@gmail.com> <1A457452-F465-4D07-9373-0061CC5EF81D@isi.edu> <51834C97.1040209@gmail.com> <C8BA4BA7-8F0E-4093-B196-0774C855E0B2@isi.edu> <5184195D.8050809@gmail.com> <CAK3OfOg1h-QNRVXYsgvJwQAsOeejNE_HD00L3DMLTsHchsLSEA@mail.gmail.com> <51841E1D.8040703@isi.edu>
Date: Fri, 3 May 2013 17:01:27 -0400
Message-ID: <CAMm+LwiDmihVUPTW0r_wNjdJjX9UXPyASkvPN+5s+T9sYrjhmw@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Joe Touch <touch@isi.edu>
Content-Type: multipart/alternative; boundary=047d7ba9751493a03604dbd6a7fe
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, Nico Williams <nico@cryptonector.com>, "bmanning@vacation.karoshi.com" <bmanning@vacation.karoshi.com>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: Re: [irtf-discuss] [rfc-i]  RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 21:01:30 -0000

--047d7ba9751493a03604dbd6a7fe
Content-Type: text/plain; charset=ISO-8859-1

Tim Berners-Lee submitted a paper on the WWW to Hypertext '92, it was
rejected.
In 1993 they asked him to give the keynote.

I don't think getting papers published in the lit is a valid or useful
criteria for career progression. Any tenure committee that is relying on
peer review to decide is stupid.

I am happy for the IETF to do whatever is necessary to for academics to
gain checklist compliance. Debugging a stupid process is not our problem.




On Fri, May 3, 2013 at 4:29 PM, Joe Touch <touch@isi.edu> wrote:

>
> On 5/3/2013 1:14 PM, Nico Williams wrote:
>
>> And the IESG can request that the RFC-Editor not publish.
>>
>
> Only for dangerous or end-run around IETF process. Not for mere quality
> issues.
>
> Joe
>
> ______________________________**_________________
> rfc-interest mailing list
> rfc-interest@rfc-editor.org
> https://www.rfc-editor.org/**mailman/listinfo/rfc-interest<https://www.rfc-editor.org/mailman/listinfo/rfc-interest>
>



-- 
Website: http://hallambaker.com/

--047d7ba9751493a03604dbd6a7fe
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Tim Berners-Lee submitted a paper on the WWW to Hypertext =
&#39;92, it was rejected.<div style>In 1993 they asked him to give the keyn=
ote.</div><div style><br></div><div style>I don&#39;t think getting papers =
published in the lit is a valid or useful criteria for career progression. =
Any tenure committee that is relying on peer review to decide is stupid.</d=
iv>
<div style><br></div><div style>I am happy for the IETF to do whatever is n=
ecessary to for academics to gain checklist compliance. Debugging a stupid =
process is not our problem.</div><div style><br></div><div style><br></div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri,=
 May 3, 2013 at 4:29 PM, Joe Touch <span dir=3D"ltr">&lt;<a href=3D"mailto:=
touch@isi.edu" target=3D"_blank">touch@isi.edu</a>&gt;</span> wrote:<br><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">
<div class=3D"im"><br>
On 5/3/2013 1:14 PM, Nico Williams wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
And the IESG can request that the RFC-Editor not publish.<br>
</blockquote>
<br></div>
Only for dangerous or end-run around IETF process. Not for mere quality iss=
ues.<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
Joe</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
______________________________<u></u>_________________<br>
rfc-interest mailing list<br>
<a href=3D"mailto:rfc-interest@rfc-editor.org" target=3D"_blank">rfc-intere=
st@rfc-editor.org</a><br>
<a href=3D"https://www.rfc-editor.org/mailman/listinfo/rfc-interest" target=
=3D"_blank">https://www.rfc-editor.org/<u></u>mailman/listinfo/rfc-interest=
</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br=
>
</div>

--047d7ba9751493a03604dbd6a7fe--

From touch@isi.edu  Fri May  3 14:35:30 2013
Return-Path: <touch@isi.edu>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BD8E21F9058 for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 14:35:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.825
X-Spam-Level: 
X-Spam-Status: No, score=-102.825 tagged_above=-999 required=5 tests=[AWL=2.975, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vpcIWs6u7DFG for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 14:35:24 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id B6E9421F9052 for <irtf-discuss@irtf.org>; Fri,  3 May 2013 14:35:24 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r43LYKCj028938 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 3 May 2013 14:34:20 -0700 (PDT)
Message-ID: <51842D4D.3060708@isi.edu>
Date: Fri, 03 May 2013 14:34:05 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Nico Williams <nico@cryptonector.com>
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.> <5182F84F.8000402@isi.edu> <2EF12BD5-908C-4D8C-81F2-C88B8AF52BA2@piuha.net> <51830554.6040604@isi.edu> <51832E10.9010101@gmail.com> <1A457452-F465-4D07-9373-0061CC5EF81D@isi.edu> <51834C97.1040209@gmail.com> <C8BA4BA7-8F0E-4093-B196-0774C855E0B2@isi.edu> <5184195D.8050809@gmail.com> <CAK3OfOg1h-QNRVXYsgvJwQAsOeejNE_HD00L3DMLTsHchsLSEA@mail.gmail.com> <51841E1D.8040703@isi.edu> <CAK3OfOhswEzzHS9BTBcRZZ0J_k+edUV9YQhJWP39Zyqdd_6hzQ@mail.gmail.com>
In-Reply-To: <CAK3OfOhswEzzHS9BTBcRZZ0J_k+edUV9YQhJWP39Zyqdd_6hzQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "bmanning@vacation.karoshi.com" <bmanning@vacation.karoshi.com>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [irtf-discuss] [rfc-i]  RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 21:35:30 -0000

On 5/3/2013 1:50 PM, Nico Williams wrote:
> On Fri, May 3, 2013 at 3:29 PM, Joe Touch <touch@isi.edu> wrote:
>> On 5/3/2013 1:14 PM, Nico Williams wrote:
>>> And the IESG can request that the RFC-Editor not publish.
>>
>> Only for dangerous or end-run around IETF process. Not for mere quality
>> issues.
> The IETF process itself can lead to non-publishing.  How many more
> RFCs are there than expired I-Ds?

Expired can mean abandoned for various reasons (lack of resources, 
etc.), not just rejected from publication.

The key metric is how many IDs were rejected after being submitted for 
publication.

Joe

From nico@cryptonector.com  Fri May  3 13:14:26 2013
Return-Path: <nico@cryptonector.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB61021F8B8F for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 13:14:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.578
X-Spam-Level: 
X-Spam-Status: No, score=-1.578 tagged_above=-999 required=5 tests=[AWL=-0.399, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IG6hG+G9KZvT for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 13:14:21 -0700 (PDT)
Received: from homiemail-a96.g.dreamhost.com (caiajhbdccah.dreamhost.com [208.97.132.207]) by ietfa.amsl.com (Postfix) with ESMTP id EB99921F8A74 for <irtf-discuss@irtf.org>; Fri,  3 May 2013 13:14:21 -0700 (PDT)
Received: from homiemail-a96.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a96.g.dreamhost.com (Postfix) with ESMTP id A42FB3B8062 for <irtf-discuss@irtf.org>; Fri,  3 May 2013 13:14:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=hbLY1XYhikkB2jCE4sYh Zfzw/4c=; b=Lth0sSGccjhdiWoETJPWnS78I3AFLjRUz2rl/4mSKIm9MZKXzht6 0+UjvfOzp6MtbLJ0in7Our3BX23bytcLq1tnTQsFSgv/4JvvO6Mbd7+7lZzuwwCl +eDR4ZMKKr8SeK86V0hHsxU+aIjgaVygZ7SSDrNID2vwVAlAykzddTc=
Received: from mail-we0-f170.google.com (mail-we0-f170.google.com [74.125.82.170]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a96.g.dreamhost.com (Postfix) with ESMTPSA id 4CD6A3B805B for <irtf-discuss@irtf.org>; Fri,  3 May 2013 13:14:21 -0700 (PDT)
Received: by mail-we0-f170.google.com with SMTP id z53so1583015wey.15 for <irtf-discuss@irtf.org>; Fri, 03 May 2013 13:14:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=QEirIHh6h+Cb2NPU3Xki1j+8uhAe4MkQ7vQRCR07Z6M=; b=BFK45CycwcGZVaaYfIWGeF0FXtsbej+mXU+UThfuUBcL/c4+rKHZnyNNxJWk7qxPX3 3+j76JrodjbykDWvG9+fuixsr9bHIdVAX+MUoE0vQWEB7hFbgX2U4oGNa5LRoY2gV5dM BC9rwVP0J0RlZx2hILzv6OQ/Bh2hnSR8bplZy/RZWyHspRYG5GwpfCaAp1N3jIM0/FZw GcT7B2Q4684hDK3Fp7xZ39xUswTv3MsGQ0rNjGPpYP9Rbm7jQYMNIUhGy0tm1HdBACFa 7nNoLYjpekQvAG8qrh/uHkabPFOq9hNrq6cu1PzfWsOA/qymW0GEGSzjnCN3Z4W0NoNu pyEg==
MIME-Version: 1.0
X-Received: by 10.194.71.103 with SMTP id t7mr15976557wju.38.1367612059916; Fri, 03 May 2013 13:14:19 -0700 (PDT)
Received: by 10.216.111.132 with HTTP; Fri, 3 May 2013 13:14:19 -0700 (PDT)
In-Reply-To: <5184195D.8050809@gmail.com>
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.> <5182F84F.8000402@isi.edu> <2EF12BD5-908C-4D8C-81F2-C88B8AF52BA2@piuha.net> <51830554.6040604@isi.edu> <51832E10.9010101@gmail.com> <1A457452-F465-4D07-9373-0061CC5EF81D@isi.edu> <51834C97.1040209@gmail.com> <C8BA4BA7-8F0E-4093-B196-0774C855E0B2@isi.edu> <5184195D.8050809@gmail.com>
Date: Fri, 3 May 2013 15:14:19 -0500
Message-ID: <CAK3OfOg1h-QNRVXYsgvJwQAsOeejNE_HD00L3DMLTsHchsLSEA@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Mailman-Approved-At: Fri, 03 May 2013 21:30:58 -0700
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "bmanning@vacation.karoshi.com" <bmanning@vacation.karoshi.com>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: Re: [irtf-discuss] [rfc-i]  RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 20:14:26 -0000

And the IESG can request that the RFC-Editor not publish.

From nico@cryptonector.com  Fri May  3 13:50:56 2013
Return-Path: <nico@cryptonector.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B07CF21F9164 for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 13:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.178
X-Spam-Level: 
X-Spam-Status: No, score=-1.178 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wDVY2S9ddTUM for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 13:50:50 -0700 (PDT)
Received: from homiemail-a30.g.dreamhost.com (caiajhbdcahe.dreamhost.com [208.97.132.74]) by ietfa.amsl.com (Postfix) with ESMTP id 6CB8C21F8E8F for <irtf-discuss@irtf.org>; Fri,  3 May 2013 13:50:50 -0700 (PDT)
Received: from homiemail-a30.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a30.g.dreamhost.com (Postfix) with ESMTP id 5BAB721DE59 for <irtf-discuss@irtf.org>; Fri,  3 May 2013 13:50:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=UjMCYSxSWM32Vmc6Cm+D 2r2QUAA=; b=gCQX63Z5Sj30F0FqtQhmKEqGvI1UzKaSsA7rpbYfJ2jBbhYE6iVO K4wspY5l462WwQEFgoEVDGm/0O9d5PmzX2vbEuM6tafFXjuaEi4mM07svu4Jhd2R VAWxIEZvAYcYnA3FpG1O7c73+e52jkpihFGdoy1sGpMJwKTNSKHmkBs=
Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com [209.85.212.177]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a30.g.dreamhost.com (Postfix) with ESMTPSA id F072A21DE58 for <irtf-discuss@irtf.org>; Fri,  3 May 2013 13:50:48 -0700 (PDT)
Received: by mail-wi0-f177.google.com with SMTP id hq12so1004002wib.10 for <irtf-discuss@irtf.org>; Fri, 03 May 2013 13:50:47 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=8TdTCXLcuFsGW0f3YqTpVQL6U9AtIx1uoRIAm+B1PuY=; b=RqokhKjlIpqGQ7Vn8UiWFgQVQVmDSx5BTSaCOaRGp6mAfO/Jy3UGrMYLFuL4QwIJ+m 6FPaXWZKIJiUx0sCmE3tUD1IdS8ZCmt6oOAaP6K+H//FJWOqnfnDVzt0agQSiinq0Cr7 E2aNTkjEf4TnQTL5l/grDof61hz25jlWmcTsAWn/HPKc4yoogrmitjgfST0ptq27ugm+ 1c3oMVgn1rsJ4s3/SYbuybMJFmZECXPmM0IxrB2Hsaqu1rHrR/dko5xO+9mJ+XUQeCEf xWTqUf1ysLL0ZFU2IQIizOs9cZnO1PVj3++Ur5tcFiBjWjEBiOblCXM+jAKS9tYkUwCp HQKg==
MIME-Version: 1.0
X-Received: by 10.180.183.139 with SMTP id em11mr21122237wic.16.1367614247611;  Fri, 03 May 2013 13:50:47 -0700 (PDT)
Received: by 10.216.111.132 with HTTP; Fri, 3 May 2013 13:50:47 -0700 (PDT)
In-Reply-To: <51841E1D.8040703@isi.edu>
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.> <5182F84F.8000402@isi.edu> <2EF12BD5-908C-4D8C-81F2-C88B8AF52BA2@piuha.net> <51830554.6040604@isi.edu> <51832E10.9010101@gmail.com> <1A457452-F465-4D07-9373-0061CC5EF81D@isi.edu> <51834C97.1040209@gmail.com> <C8BA4BA7-8F0E-4093-B196-0774C855E0B2@isi.edu> <5184195D.8050809@gmail.com> <CAK3OfOg1h-QNRVXYsgvJwQAsOeejNE_HD00L3DMLTsHchsLSEA@mail.gmail.com> <51841E1D.8040703@isi.edu>
Date: Fri, 3 May 2013 15:50:47 -0500
Message-ID: <CAK3OfOhswEzzHS9BTBcRZZ0J_k+edUV9YQhJWP39Zyqdd_6hzQ@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Joe Touch <touch@isi.edu>
Content-Type: text/plain; charset=UTF-8
X-Mailman-Approved-At: Fri, 03 May 2013 21:30:58 -0700
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "bmanning@vacation.karoshi.com" <bmanning@vacation.karoshi.com>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [irtf-discuss] [rfc-i]  RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 20:50:56 -0000

On Fri, May 3, 2013 at 3:29 PM, Joe Touch <touch@isi.edu> wrote:
> On 5/3/2013 1:14 PM, Nico Williams wrote:
>>
>> And the IESG can request that the RFC-Editor not publish.
>
>
> Only for dangerous or end-run around IETF process. Not for mere quality
> issues.

The IETF process itself can lead to non-publishing.  How many more
RFCs are there than expired I-Ds?

From nico@cryptonector.com  Fri May  3 14:43:02 2013
Return-Path: <nico@cryptonector.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A494021F9079 for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 14:43:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.178
X-Spam-Level: 
X-Spam-Status: No, score=-1.178 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s4kOYQTAkMUD for <irtf-discuss@ietfa.amsl.com>; Fri,  3 May 2013 14:42:57 -0700 (PDT)
Received: from homiemail-a98.g.dreamhost.com (caiajhbdcaid.dreamhost.com [208.97.132.83]) by ietfa.amsl.com (Postfix) with ESMTP id BDB8D21F8BDE for <irtf-discuss@irtf.org>; Fri,  3 May 2013 14:42:57 -0700 (PDT)
Received: from homiemail-a98.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a98.g.dreamhost.com (Postfix) with ESMTP id 5024B2C200D for <irtf-discuss@irtf.org>; Fri,  3 May 2013 14:42:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=O3yDooHjxbQ2kTtkUBQb ONIM7M4=; b=MBkjSegxycxX7m/gHkzU6Hg+2TyrBjtfddxIu3hI3f9ppY6JOxIg LhIyeCQTZj+zK1PiOsPMX6SxmIlr8JQmDKffUn850wXWprXwYOPMo+Qc2vuSaYQJ WW2ifqB9NY3fZPRd1ynu34ao3S05iSNtQk6wdEVxMJUIYfK/zGXKN7U=
Received: from mail-wi0-f169.google.com (mail-wi0-f169.google.com [209.85.212.169]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a98.g.dreamhost.com (Postfix) with ESMTPSA id D38522C2005 for <irtf-discuss@irtf.org>; Fri,  3 May 2013 14:42:56 -0700 (PDT)
Received: by mail-wi0-f169.google.com with SMTP id h11so1157472wiv.2 for <irtf-discuss@irtf.org>; Fri, 03 May 2013 14:42:54 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=g2wgcd0/dZ9KH9FH3m2i/JqQpF085N+TtsorApdM7S0=; b=gkSfbGRjwh5yc7wT3E77ej/9KsuBjow4phdVJz4qSYA6iIYJqgLKAbzq4OWCD0eHXx oAsZk9D9Q2eYWWXRQFCOVpl5nhFUcxHp2WNPfs4OvMFCNyibsBWYJdZ8A+t9b58CVgem ZxOflat/qBuohY4ZLqQ4SRGNRX1PX44m6kmgiQsrm22CFN/1XiWTsiUy1kof3Qyxl0IS u80d1PP8kp26+zw4MiPJuIpZQ27lpkDj2QZcPy3x8r/b58BLqxKeEn3Nmbke45TXIVY9 4Qt4NaH2VT/t0tZbf9zfmVUEZJDX6ck7wHGAdxJSjUWhnR3XOBFijddSX7iUhiN7Bywf m8uQ==
MIME-Version: 1.0
X-Received: by 10.194.173.167 with SMTP id bl7mr16164047wjc.50.1367617374848;  Fri, 03 May 2013 14:42:54 -0700 (PDT)
Received: by 10.216.111.132 with HTTP; Fri, 3 May 2013 14:42:54 -0700 (PDT)
In-Reply-To: <51842D4D.3060708@isi.edu>
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.> <5182F84F.8000402@isi.edu> <2EF12BD5-908C-4D8C-81F2-C88B8AF52BA2@piuha.net> <51830554.6040604@isi.edu> <51832E10.9010101@gmail.com> <1A457452-F465-4D07-9373-0061CC5EF81D@isi.edu> <51834C97.1040209@gmail.com> <C8BA4BA7-8F0E-4093-B196-0774C855E0B2@isi.edu> <5184195D.8050809@gmail.com> <CAK3OfOg1h-QNRVXYsgvJwQAsOeejNE_HD00L3DMLTsHchsLSEA@mail.gmail.com> <51841E1D.8040703@isi.edu> <CAK3OfOhswEzzHS9BTBcRZZ0J_k+edUV9YQhJWP39Zyqdd_6hzQ@mail.gmail.com> <51842D4D.3060708@isi.edu>
Date: Fri, 3 May 2013 16:42:54 -0500
Message-ID: <CAK3OfOj15WEZUB0aFN00Mt0hsYZuQkvVVoZjkFU5K8AurNOopA@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Joe Touch <touch@isi.edu>
Content-Type: text/plain; charset=UTF-8
X-Mailman-Approved-At: Fri, 03 May 2013 21:30:58 -0700
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "bmanning@vacation.karoshi.com" <bmanning@vacation.karoshi.com>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [irtf-discuss] [rfc-i]  RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 21:43:02 -0000

On Fri, May 3, 2013 at 4:34 PM, Joe Touch <touch@isi.edu> wrote:
> On 5/3/2013 1:50 PM, Nico Williams wrote:
>> The IETF process itself can lead to non-publishing.  How many more
>> RFCs are there than expired I-Ds?
>
>
> Expired can mean abandoned for various reasons (lack of resources, etc.),
> not just rejected from publication.
>
> The key metric is how many IDs were rejected after being submitted for
> publication.

That's a misleading metric.  The number of such rejections is probably
in the single digits.  Abandonment of I-Ds is often a result of lack
of interest because the proposed RFC was crap, or there's no interest
in the technology in question, but there's no way to measure that --
at best you could do some sampling and make your own [often
subjective] determination of why an I-D was abandoned, something that
requires a lot of effort.

An I-D that reaches WGLC or IETF LC is one that has reached consensus
to get pretty down far on the road to publication, so any problems
with it will be fixed rather than result in abandonment.

RFC publication rejection is informal, and highly social.  But it does
happen, and plenty.

Nico
--

From marcelo@it.uc3m.es  Sun May  5 11:41:20 2013
Return-Path: <marcelo@it.uc3m.es>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5420521F9727 for <irtf-discuss@ietfa.amsl.com>; Sun,  5 May 2013 11:41:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.8
X-Spam-Level: 
X-Spam-Status: No, score=-105.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zVgEbypfOzaE for <irtf-discuss@ietfa.amsl.com>; Sun,  5 May 2013 11:41:15 -0700 (PDT)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by ietfa.amsl.com (Postfix) with ESMTP id 0E07D21F9726 for <irtf-discuss@irtf.org>; Sun,  5 May 2013 11:41:14 -0700 (PDT)
Received: from smtp03.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id 9E15711A2111; Sun,  5 May 2013 20:41:13 +0200 (CEST)
X-uc3m-safe: yes
Received: from [10.0.1.7] (176.170.78.188.dynamic.jazztel.es [188.78.170.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: marcelo@smtp03.uc3m.es) by smtp03.uc3m.es (Postfix) with ESMTPSA id 4C61511A1318; Sun,  5 May 2013 20:41:13 +0200 (CEST)
Message-ID: <5186A7D3.6030209@it.uc3m.es>
Date: Sun, 05 May 2013 20:41:23 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.> <5182F84F.8000402@isi.edu>
In-Reply-To: <5182F84F.8000402@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTHACL 134 matched, not delayed by milter-greylist-4.2.7 (smtp03.uc3m.es); Sun, 05 May 2013 20:41:13 +0200 (CEST)
X-TM-AS-Product-Ver: IMSS-7.1.0.1224-7.0.0.1014-19846.001
X-TM-AS-Result: No--22.348-7.0-31-1
X-imss-scan-details: No--22.348-7.0-31-1
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, bmanning@vacation.karoshi.com, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: Re: [irtf-discuss] RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 May 2013 18:41:20 -0000

Just one clarification.

I am not sure if this the point that you were trying to make but in 
journal there are also editorial papers that are usually not considered 
peer reviewed.

I mean, my point is that even if there are some RFCs that are not peer 
reviewed, this should not be an obstacle to consider the RFCs that are 
peer reviewed as peer reviewed papers imho


El 03/05/13 01:35, Joe Touch escribió:
> IETF-stream and IRTF-streams are often considered peer-reviewed.
>
> Other streams may or may not be considered peer-reviewed (I would not 
> consider IAB documents as such), but independent submissions are 
> generally not (they only purpose of the one review they get is to make 
> sure they're on-topic and not bogus).
>
> Joe
>
> On 4/25/2013 7:08 AM, bmanning@vacation.karoshi.com wrote:
>>
>>   at least a few university communities consider RFCs as peer 
>> reviewed papers.
>>
>> /bill
>>
>>
>> On Thu, Apr 25, 2013 at 12:42:54PM +0000, Yaakov Stein wrote:
>>> I just checked and my request is marked "under consideration" with 
>>> no-one else voting for it.
>>>
>>> See 
>>> https://feedback.researchgate.net/responses/please-allow-enter-ietf-rfcs-as-peer-reviewed-papers
>>>
>>> Perhaps if some other ResearchGate members vote for it the RG staff 
>>> will take notice.
>>>
>>> Y(J)S
>>>
>>>
>>> -----Original Message-----
>>> From: irtf-discuss-bounces@irtf.org 
>>> [mailto:irtf-discuss-bounces@irtf.org] On Behalf Of Yaakov Stein
>>> Sent: 25 April, 2013 15:33
>>> To: marcelo bagnulo braun; SM
>>> Cc: irtf-discuss@irtf.org; rfc-interest@rfc-editor.org
>>> Subject: Re: [irtf-discuss] RFCs accepted journal articles
>>>
>>>
>>> I submitted a request to ResearchGate to accept RFCs as a valid 
>>> publication type.
>>>
>>> However, I never received any feedback from them.
>>>
>>> Y(J)S
>>>
>>>
>>> -----Original Message-----
>>> From: irtf-discuss-bounces@irtf.org 
>>> [mailto:irtf-discuss-bounces@irtf.org] On Behalf Of marcelo bagnulo 
>>> braun
>>> Sent: 25 April, 2013 15:19
>>> To: SM
>>> Cc: irtf-discuss@irtf.org; rfc-interest@rfc-editor.org
>>> Subject: Re: [irtf-discuss] RFCs accepted journal articles
>>>
>>> I already did quite a while ago. No reply so far.
>>>
>>> El 25/04/13 11:00, SM escribis:
>>>> Hi Marcelo,
>>>> At 01:32 25-04-2013, marcelo bagnulo braun wrote:
>>>>> What would be really useful would be that the RFC series are included
>>>>> in the Journal Citation Report. I have asked this to the RFC editor a
>>>>> while ago, but i didnt received any reply.
>>>>>
>>>>> This would go a very long way (at least in this part of the world) to
>>>>> make them valid as a an merit for the academics.
>>>>
>>>> I suggest asking the RSE about the above.
>>>>
>>>> Regards,
>>>> -sm
>>>>
>>>
>


From mcr@sandelman.ca  Mon May  6 05:54:20 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4C3621F8EF7 for <irtf-discuss@ietfa.amsl.com>; Mon,  6 May 2013 05:54:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 77oilHDgdoJr for <irtf-discuss@ietfa.amsl.com>; Mon,  6 May 2013 05:54:15 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.252.184]) by ietfa.amsl.com (Postfix) with ESMTP id 0FB4121F8EDA for <irtf-discuss@irtf.org>; Mon,  6 May 2013 05:54:13 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id DB2CD2016E; Mon,  6 May 2013 09:05:22 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 28EFB63A7C; Mon,  6 May 2013 08:53:08 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 17927639DF; Mon,  6 May 2013 08:53:08 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Nico Williams <nico@cryptonector.com>
In-Reply-To: <CAK3OfOhswEzzHS9BTBcRZZ0J_k+edUV9YQhJWP39Zyqdd_6hzQ@mail.gmail.com>
References: <1BC72FF7-B1B7-4E8D-B24F-56A1E368C793@piuha.net> <09609744-6380-4B5C-951C-B7D4A53614AB@netapp.com> <5177C089.1000904@cs.helsinki.fi> <C1CCD180-E88B-48CF-A3A1-9AF0A5E0BEE3@netapp.com> <5178062D.8030904@cs.helsinki.fi> <5178EA17.7050504@it.uc3m.es> <6.2.5.6.2.20130425015837.0b9aece0@resistor.net> <51791F3E.6040707@it.uc3m.es> <07F7D7DED63154409F13298786A2ADC904D02C23@EXRAD5.ad.rad.co.il> <07F7D7DED63154409F13298786A2ADC904D02C3D@EXRAD5.ad.rad.co.il> <20130425140830.GA21669@vacation.karoshi.com.> <5182F84F.8000402@isi.edu> <2EF12BD5-908C-4D8C-81F2-C88B8AF52BA2@piuha.net> <51830554.6040604@isi.edu> <51832E10.9010101@gmail.com> <1A457452-F465-4D07-9373-0061CC5EF81D@isi.edu> <51834C97.1040209@gmail.com> <C8BA4BA7-8F0E-4093-B196-0774C855E0B2@isi.edu> <5184195D.8050809@gmail.com> <CAK3OfOg1h-QNRVXYsgvJwQAsOeejNE_HD00L3DMLTsHchsLSEA@mail.gmail.com> <51841E1D.8040703@isi.edu> <CAK3OfOhswEzzHS9BTBcRZZ0J_k+edUV9YQhJWP39Zyqdd_6hzQ@mail.gmail.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
Date: Mon, 06 May 2013 08:53:08 -0400
Message-ID: <13740.1367844788@sandelman.ca>
Sender: mcr@sandelman.ca
X-Mailman-Approved-At: Mon, 06 May 2013 05:55:20 -0700
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "bmanning@vacation.karoshi.com" <bmanning@vacation.karoshi.com>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: Re: [irtf-discuss] [rfc-i]  RFCs accepted journal articles
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2013 12:54:21 -0000

>>>>> "Nico" == Nico Williams <nico@cryptonector.com> writes:
    >> On 5/3/2013 1:14 PM, Nico Williams wrote:
    >>> And the IESG can request that the RFC-Editor not publish.
    >> 
    >> 
    >> Only for dangerous or end-run around IETF process. Not for mere
    >> quality issues.

    Nico> The IETF process itself can lead to non-publishing.  How many
    Nico> more RFCs are there than expired I-Ds?

I'd still like to non-publish the documents in the CFR (anti-RFC) or
some such series.  Probably in HTML only, with a CSS of:
  color: #fff;
  background-color: #fff;

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [ 
	

From lars@netapp.com  Thu May 23 10:28:43 2013
Return-Path: <lars@netapp.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C43421F9206 for <irtf-discuss@ietfa.amsl.com>; Thu, 23 May 2013 10:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.149
X-Spam-Level: 
X-Spam-Status: No, score=-10.149 tagged_above=-999 required=5 tests=[AWL=0.450, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nXqbuTiK3QlT for <irtf-discuss@ietfa.amsl.com>; Thu, 23 May 2013 10:28:22 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 4FE2621F95E4 for <irtf-discuss@irtf.org>; Thu, 23 May 2013 10:18:59 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,729,1363158000"; d="scan'208";a="57047359"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx12-out.netapp.com with ESMTP; 23 May 2013 10:18:59 -0700
Received: from vmwexceht04-prd.hq.netapp.com (vmwexceht04-prd.hq.netapp.com [10.106.77.34]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r4NHIx1x018784 for <irtf-discuss@irtf.org>; Thu, 23 May 2013 10:18:59 -0700 (PDT)
Received: from VMWEXCEHT06-PRD.hq.netapp.com (10.106.77.104) by vmwexceht04-prd.hq.netapp.com (10.106.77.34) with Microsoft SMTP Server (TLS) id 14.3.123.3; Thu, 23 May 2013 10:18:58 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.208]) by vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) with mapi id 14.03.0123.003; Thu, 23 May 2013 10:18:58 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>
Thread-Topic: IETF Meeting in South America
Thread-Index: AQHOV83ts1sfrBEE9USHzDa876uwkA==
Date: Thu, 23 May 2013 17:18:57 +0000
Message-ID: <FAA31FF8-48FB-4C9B-B2AD-6B091D05A83A@netapp.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.118]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2DD3B65EC302F84E8A0DE84DAFF31FBE@hq.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [irtf-discuss] Fwd: IETF Meeting in South America
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2013 17:28:43 -0000

Begin forwarded message:

> From: The IAOC <bob.hinden@gmail.com>
> Subject: IETF Meeting in South America
> Date: May 23, 2013 17:54:12 GMT+02:00
> To: IETF Announcement List <ietf-announce@ietf.org>
> Cc: <ietf@ietf.org>
>=20
> As you may know the IAOC has been investigating the feasibility of having=
 an IETF
> meeting in South America.  There was a site visit to South America last F=
ebruary.=20
> We have found two venues that we believe will support a successful IETF m=
eeting
> and we would like to get feedback from the community.
>=20
> The venues are in Buenos Aires.  They meet our requirements for the meeti=
ng
> space, networking, nearby restaurants and bars, hotel room rates in the m=
id $200
> dollar range, nearby alternate hotels at a broad range of prices, nice ar=
ea in the
> city, safe, direct international flights, and accessible visas.  The IAOC=
 thinks we
> could have a successful IETF meeting in Buenos Aires and that attendees w=
ould
> like the venues.
>=20
> There has been a consistent level of IETF participation from South and Ce=
ntral
> America, and it has been growing since IETF82.  The data on this is poste=
d at=20
>=20
>   http://iaoc.ietf.org/documents/IETF-Regional-Attendance-00.pdf. =20
>=20
> The current meeting regional rotation (announced at IETF79) allows for an
> occasional IETF meeting outside of our main regions (Europe, North Americ=
a,
> Asia/Pacific). =20
>=20
> IETF standards are made more valuable the more relevant they are and the =
more
> uptake they get.  IETF standards are also made more robust when all persp=
ectives
> are represented during their development.  Encouraging growing participat=
ion
> will help strengthen the Internet, further encourage participation from t=
hose areas
> that will see the most growth in the coming years, and will help advance =
the IETF
> in political and international circles which is becoming more of an imper=
ative.
>=20
> We have asked the IESG for their feedback and they are supportive of a me=
eting in
> South America if there is community support and active participants atten=
d.
>=20
> Things to consider are that it will be a long trip for the majority of IE=
TFers and the
> air fares are more expensive (about 10% to 20% higher than average), thou=
gh
> restaurants are less expensive.  This would be a case where most IETFers =
would
> bear more travel pain and expense. =20
>=20
> The IAOC would like to understand if the IETF community thinks that the I=
ETF
> should have a meeting in the next few years in Buenos Aires.  The IAOC wo=
uld
> also like to get feedback on how we can ensure the meeting is as successf=
ul as
> possible and on ways to grow participation in the region.
>=20
> We have set up a survey at  https://www.surveymonkey.com/s/NWYLQCD  where
> you can indicate your likelihood of attending, and we encourage you to se=
nd your
> general feedback to the IETF list <ietf@ietf.org>.
>=20
> Thanks,
> Bob Hinden
> IAOC Chair


From lars@netapp.com  Sun May 26 06:45:51 2013
Return-Path: <lars@netapp.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0794221F9003 for <irtf-discuss@ietfa.amsl.com>; Sun, 26 May 2013 06:45:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.47
X-Spam-Level: 
X-Spam-Status: No, score=-10.47 tagged_above=-999 required=5 tests=[AWL=0.129,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MlK5ZIoOimEI for <irtf-discuss@ietfa.amsl.com>; Sun, 26 May 2013 06:45:46 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 04B4721F8FF3 for <irtf-discuss@irtf.org>; Sun, 26 May 2013 06:45:45 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,745,1363158000"; d="scan'208";a="58068213"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 26 May 2013 06:45:44 -0700
Received: from vmwexceht04-prd.hq.netapp.com (vmwexceht04-prd.hq.netapp.com [10.106.77.34]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r4QDjijV010718; Sun, 26 May 2013 06:45:44 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.208]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.03.0123.003; Sun, 26 May 2013 06:45:44 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>
Thread-Topic: [e2e] Network Research
Thread-Index: AQHOWVkfAPTiGXCqhkaJ+w6ushsf0Q==
Date: Sun, 26 May 2013 13:45:44 +0000
Message-ID: <188C915A-203A-46BD-94B6-0E73EB629038@netapp.com>
References: <CAAWx_pXC68x_aF5AtCQ7xXCoQ2OrXYGq5d_hvWv9AyxSjEt3kA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.118]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <C77DE14F521A1E47B6781B11CFEB11CE@hq.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "jwbensley@gmail.com" <jwbensley@gmail.com>
Subject: [irtf-discuss] Fwd: [e2e] Network Research
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 May 2013 13:45:51 -0000

Begin forwarded message:

> From: James Bensley <jwbensley@gmail.com>
> Subject: [e2e] Network Research
> Date: May 25, 2013 16:27:12 GMT+02:00
> To: <end2end-interest@postel.org>
>=20
> Hello everyone,
>=20
> I am currently undertaking a research project as part of a masters
> degree in advanced networking. I want the input of the community and
> industry at large. I have created a small on-line survey and would be
> very grateful to anyone that could give 3 minutes to fill it out. You
> will be benefiting networking research so I'm sure you are all wanting
> to participate;
>=20
> The survey is here:
> https://docs.google.com/forms/d/1lqigAHYHEgLLHr2kifiyBwgJ9Nw5AFS6d_XVXfhK=
kTw/viewform
>=20
> When the research project is complete I will be uploading it for all
> and sundry to read and distribute. All results will be anonymised!
>=20
> If you want a copy of the anonymised results, or have any queries
> about the research or the survey, please email me off-list to save
> on-list noise.
>=20
> Kind regards,
> James
>=20
> P.S. Apologies if you are on multiple mailing lists and receive this
> email multiple times!


From lars@netapp.com  Mon May 27 03:01:13 2013
Return-Path: <lars@netapp.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82E3A21F90FD; Mon, 27 May 2013 03:01:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.092
X-Spam-Level: 
X-Spam-Status: No, score=-9.092 tagged_above=-999 required=5 tests=[AWL=-1.507, BAYES_40=-0.185, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NGc0E14qVsoQ; Mon, 27 May 2013 03:01:09 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id B369521F8A68; Mon, 27 May 2013 03:01:05 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,750,1363158000"; d="scan'208";a="58319803"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx12-out.netapp.com with ESMTP; 27 May 2013 03:01:05 -0700
Received: from vmwexceht01-prd.hq.netapp.com (vmwexceht01-prd.hq.netapp.com [10.106.76.239]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r4RA15IC029361; Mon, 27 May 2013 03:01:05 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.208]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.03.0123.003; Mon, 27 May 2013 03:01:02 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "irtf-announce@irtf.org" <irtf-announce@irtf.org>, "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>
Thread-Topic: Applied Networking Research Prize 2013 presentation		at IETF-87
Thread-Index: AQHOWsEXr7MGP7mViEyv5SghizkwqQ==
Date: Mon, 27 May 2013 10:01:01 +0000
Message-ID: <9B4B749D-239D-44AB-B9C4-F8D3095D9249@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="utf-8"
Content-ID: <57A17D246A783342A99A406E12DD59BD@hq.netapp.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: [irtf-discuss] Applied Networking Research Prize 2013 presentation		at IETF-87
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "anrp@irtf.org" <anrp@irtf.org>
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 10:01:13 -0000

DQpIaSwNCg0Kd2UgYXJlIGV4dHJlbWVseSBwbGVhc2VkIHRvIHJlcG9ydCB0aGF0IGZvciB0aGUg
MjAxMyBhd2FyZCBwZXJpb2Qgb2YNCnRoZSBBcHBsaWVkIE5ldHdvcmtpbmcgUmVzZWFyY2ggUHJp
emUgKEFOUlApLCAzNiBlbGlnaWJsZSBub21pbmF0aW9ucw0Kd2VyZSByZWNlaXZlZC4gRWFjaCBz
dWJtaXNzaW9uIHdhcyByZXZpZXdlZCBieSBlaWdodCBtZW1iZXJzIG9mIHRoZQ0Kc2VsZWN0aW9u
IGNvbW1pdHRlZSBhY2NvcmRpbmcgdG8gYSBkaXZlcnNlIHNldCBvZiBjcml0ZXJpYSwgaW5jbHVk
aW5nDQpzY2llbnRpZmljIGV4Y2VsbGVuY2UgYW5kIHN1YnN0YW5jZSwgdGltZWxpbmVzcywgcmVs
ZXZhbmNlLCBhbmQNCnBvdGVudGlhbCBpbXBhY3Qgb24gdGhlIEludGVybmV0Lg0KDQpCYXNlZCBv
biB0aGlzIHJldmlldywgZm91ciBzdWJtaXNzaW9ucyB3ZXJlIGF3YXJkZWQgYW4gQU5SUCBpbiAy
MDEzLA0KdGhlIGZpcnN0IG9mIHdoaWNoIHdhcyBhbHJlYWR5IHByZXNlbnRlZCBhdCBJRVRGLTg2
LiANCg0KVGhlIHNlY29uZCBhbmQgdGhpcmQgYXdhcmRzIHdpbGwgaGFwcGVuIGF0IElFVEYtODcg
aW4gQmVybGluLCBHZXJtYW55Lg0KVGhleSBnbyB0bzoNCg0KICAqKiogVGUtWXVhbiBIdWFuZyAq
KiogZm9yIGluc2lnaHRzIGludG8gdGhlIGRpZmZpY3VsdGllcyBvZiByYXRlDQogIGFkYXB0YXRp
b24gZm9yIHN0cmVhbWluZyB2aWRlbzoNCg0KICAgIFRlLVl1YW4gSHVhbmcsIE5pa2hpbCBIYW5k
aWdvbCwgQnJhbmRvbiBIZWxsZXIsIE5pY2sgTWNLZW93bg0KICAgIGFuZCBSYW1lc2ggSm9oYXJp
LiBDb25mdXNlZCwgVGltaWQsIGFuZCBVbnN0YWJsZTogUGlja2luZyBhDQogICAgVmlkZW8gU3Ry
ZWFtaW5nIFJhdGUgaXMgSGFyZC4gUHJvYy4gQUNNIEludGVybmV0IE1lYXN1cmVtZW50DQogICAg
Q29uZmVyZW5jZSAoSU1DKSxOb3ZlbWJlciAyMDEyLCBCb3N0b24sIE1BLCBVU0EuDQoNCiAgKioq
IExhdXJlbnQgVmFuYmV2ZXIgKioqIGZvciBwcm9wb3NpbmcgYSBmcmFtZXdvcmsgdG8gYWxsb3cg
c2VhbWxlc3MNCiAgQkdQIHJlY29uZmlndXJhdGlvbnM6DQoNCiAgICBTdGVmYW5vIFZpc3NpY2No
aW8sIExhdXJlbnQgVmFuYmV2ZXIsIENyaXN0ZWwgUGVsc3NlciwgTHVjYQ0KICAgIENpdHRhZGlu
aSwgUGllcnJlIEZyYW5jb2lzIGFuZCBPbGl2aWVyIEJvbmF2ZW50dXJlLiBJbXByb3ZpbmcNCiAg
ICBOZXR3b3JrIEFnaWxpdHkgd2l0aCBTZWFtbGVzcyBCR1AgUmVjb27vrIFndXJhdGlvbnMuIFBy
b2MuIElFRUUvQUNNDQogICAgVHJhbnNhY3Rpb25zIG9uIE5ldHdvcmtpbmcgKFRPTiksIFRvIEFw
cGVhci4NCg0KVGUtWXVhbiBhbmQgTGF1cmVudCBoYXZlIGJlZW4gaW52aXRlZCB0byBwcmVzZW50
IGhlciBmaW5kaW5ncyBpbiB0aGUgSVJURg0KT3BlbiBNZWV0aW5nIGR1cmluZyBJRVRGLTg3LCBK
dWx5IDI4IC0gQXVndXN0IDIsIDIwMTMgaW4gQmVybGluLCBHZXJtYW55Lg0KSm9pbiB0aGVtIHRo
ZXJlIQ0KDQpUaGUgY2FsbCBmb3IgQU5SUCBub21pbmF0aW9ucyBmb3IgdGhlIDIwMTQgYXdhcmRz
IGN5Y2xlIHdpbGwgb3BlbiBpbiB0aGUNCmZhbGwgb2YgMjAxMy4gUmVhZCBtb3JlIGFib3V0IHRo
ZSBBTlJQIGF0IGh0dHA6Ly9pcnRmLm9yZy9hbnJwLg0KDQpQbGVhc2Ugc3Vic2NyaWJlIHRvIHRo
ZSBJUlRGLUFubm91bmNlIG1haWxpbmcgbGlzdCBpbiBvcmRlciB0byByZWNlaXZlDQpmdXR1cmUg
Y2FsbHMgZm9yIEFOUlAgbm9taW5hdGlvbnMgYW5kIGpvaW4gSVNPQyB0byBzdGF5IGluZm9ybWVk
IG9mDQpvdGhlciBuZXR3b3JraW5nIHJlc2VhcmNoIGluaXRpYXRpdmVzOg0KDQogIGh0dHA6Ly9p
cnRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lydGYtYW5ub3VuY2UNCiAgaHR0cDovL2lzb2Mub3Jn
L2pvaW4NCg0KUmVnYXJkcywNCg0KTGFycyBFZ2dlcnQsIElSVEYgQ2hhaXIgICAgICAgICAgICBo
dHRwOi8vaXJ0Zi5vcmcvYW5ycA0KTWF0IEZvcmQsIEludGVybmV0IFNvY2lldHkgICAgICAgICBo
dHRwOi8vaXNvYy5vcmcvcmVzZWFyY2gNCg0KLS0NCg0KMjAxMyBBTlJQIFNlbGVjdGlvbiBDb21t
aXR0ZWUNCg0KTWFyayBBbGxtYW4sIElDSVINCk1hcmNlbG8gQmFnbnVsbywgVUMzTQ0KTG91IEJl
cmdlciwgTGFiTg0KT2xpdmllciBCb25hdmVudHVyZSwgVUNMIExvdXZhaW4NClJvc3MgQ2FsbG9u
LCBKdW5pcGVyDQpMYXJzIEVnZ2VydCwgTmV0QXBwDQpPbGl2aWVyIEZlc3RvciwgSU5SSUENCk1h
dCBGb3JkLCBJU09DDQpMaXNhbmRybyBHcmFudmlsbGUsIFVGUkdTDQpWb2xrZXIgSGlsdCwgQmVs
bCBMYWJzDQpTdXJlc2ggS3Jpc2huYW4sIEVyaWNzc29uDQpEYW4gTWFzc2V5LCBDb2xvcmFkbyBT
dGF0ZQ0KQWwgTW9ydG9uLCBBVCZUIExhYm9yYXRvcmllcw0KSsO2cmcgT3R0LCBBYWx0byBVbml2
ZXJzaXR5DQpDb2xpbiBQZXJraW5zLCBVbml2ZXJzaXR5IG9mIEdsYXNnb3cNClN0ZWZhbm8gUHJl
dmlkaSwgQ2lzY28NCkrDvHJnZW4gU2Now7Zud8OkbGRlciwgSmFjb2JzIFVuaXZlcnNpdHkgQnJl
bWVuDQpZYW5nIFJpY2hhcmQgWWFuZywgWWFsZQ0KTGl4aWEgWmhhbmcsIFVDTEE=

From lars@netapp.com  Thu May 30 00:36:37 2013
Return-Path: <lars@netapp.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7982321F9003 for <irtf-discuss@ietfa.amsl.com>; Thu, 30 May 2013 00:36:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.367
X-Spam-Level: 
X-Spam-Status: No, score=-10.367 tagged_above=-999 required=5 tests=[AWL=0.232, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Duug0iqT6Kkn for <irtf-discuss@ietfa.amsl.com>; Thu, 30 May 2013 00:36:31 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id A77DD21F961C for <irtf-discuss@irtf.org>; Thu, 30 May 2013 00:36:30 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,769,1363158000"; d="scan'208";a="59496270"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 30 May 2013 00:36:26 -0700
Received: from vmwexceht05-prd.hq.netapp.com (exchsmtp.hq.netapp.com [10.106.77.35]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r4U7aQn4014451 for <irtf-discuss@irtf.org>; Thu, 30 May 2013 00:36:26 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.208]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.03.0123.003; Thu, 30 May 2013 00:36:26 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>
Thread-Topic: Nomcom 2013-14 Volunteering - 2nd Call
Thread-Index: AQHOXLAohg3/5/hJhka74OTHCGTCZQ==
Date: Thu, 30 May 2013 07:36:26 +0000
Message-ID: <30F532E3-AD8E-4F5A-92F4-142F1D85B0B2@netapp.com>
References: <D9F5D76C-1929-4C6B-B902-3A0854821FB7@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.118]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8BFB96116EAE82499873EFF92DB230C9@hq.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [irtf-discuss] Fwd: Nomcom 2013-14 Volunteering - 2nd Call
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Allison Mankin <amankin@verisign.com>
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 May 2013 07:36:37 -0000

Please consider volunteering for NomCom.

Begin forwarded message:

> From: "Mankin, Allison" <amankin@verisign.com>
> Subject: Nomcom 2013-14 Volunteering - 2nd Call
> Date: May 29, 2013 23:04:51 GMT+02:00
> To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
> Cc: "<ietf@ietf.org>" <ietf@ietf.org>
>=20
> Hi, everyone,
>=20
> Remember that I'm challenging the IETF to come up with 200 volunteers for=
=20
> the upcoming nomcom.  You can volunteer just by hitting Reply to this ema=
il.
>=20
> What are you waiting for??  The more volunteers we get, the better chance=
 we
> have of choosing a random yet representative cross section of the IETF=20
> population.  Respond to the 200-volunteer challenge and hit Reply right n=
ow.=20
> (Well, much as I want you to do this, please look below at the posts bein=
g
> filled and be sure you are willing to forgo trying for any of them this y=
ear).
>=20
> The official information:
> The IETF nominating committee (nomcom) process for 2013-14 is under way. =
The=20
> IETF nomcom appoints folks to fill the open slots on the IAOC, the IAB,
> and the IESG. Ten voting members for the nomcom are selected in a verifia=
bly
> random way from a pool of volunteers.=20
>=20
> The details of the selection and operation of the nomcom can be found=20
> in RFCs 3777, 5078, 5633, 5680, and 6859.  Four of those RFCs  (3777, 563=
3,=20
> 5680 and 6859)  comprise BCP 10. We will also reference RFC 3797.
>=20
> Volunteers must have attended 3 of the past 5 IETF meetings.  As specifie=
d in
> RFC 3777, that means three out of the five past meetings up to the time t=
his
> email announcement goes out to start the solicitation of volunteers. The =
five
> meetings out of which you must have attended three are IETF 82, 83, 84, 8=
5, 86.
>=20
> If you qualify, reply to this email and volunteer. =20
>=20
> The list of people and posts whose terms end with the March 2014 IETF
> meeting, and thus the positions for which this nomcom is responsible, are
> IAOC:
> Chris Griffiths
>=20
> IAB:
> Bernard Aboba
> Marc Blanchet
> Ross Callon
> Eliot Lear
> Hannes Tschofenig
>=20
> IESG:
> Barry Leiba (Applications)
> Brian Haberman (Internet)
> Benoit Claise (Operations and Management)
> Gonzalo Camarillo (RAI)
> Stewart Bryant (Routing)
> Sean Turner (Security)
> Martin Stiemerling (Transport)
>=20
> The primary activity for this nomcom will begin in July 2013 and should b=
e
> completed in January 2014.  Being a nomcom member will require some time
> commitment - there will be interviews with candidates at meetings, regula=
rly
> scheduled conference calls to ensure progress, collection and review of=20
> requirements from the commitment, review of candidate questionnaires and
> of community feedback.  A more detailed timetable for the nomcom tasks
> will appear soon.
>=20
> Please respond to this email before 11:59 pm EDT (UTC -4 hours)=20
> June 16, 2013.  In the body include:=20
> 1. your Given Name as you enter it when you register for the IETF
> 2. your Family Name as you enter it when you register for the IETF
> 3. your current primary affilation (the information you enter into the Co=
mpany field)
> 4. any/all email addresses you've used to register for IETF meetings=20
> 5. which email address you prefer=20
> 6. your phone number (for our use in confirming you if selected).
>=20
> You should expect an email response from me within 3 business days statin=
g
> whether or not you are qualified (and added to the list).  If you don't r=
eceive this
> response, please re-send your email adding the tag "RESEND" to the subjec=
t line.
>=20
> Participating in the IETF nomcom is a meaningful and fun way to contribut=
e to the IETF. =20
> Please help us meet the 200-volunteer challenge by hitting Reply to this =
message today. =20
>=20
> Allison=20
>=20
> Allison Mankin
> Nomcom Chair 2013-2014

