Re: [ietf-privacy] [perpass] Wiki for managing PPM reviews of existing RFCs

Stephen Farrell <stephen.farrell@cs.tcd.ie> Mon, 24 March 2014 09:54 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf-privacy@ietfa.amsl.com
Delivered-To: ietf-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D3DC1A0185; Mon, 24 Mar 2014 02:54:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eYt83QIOlf7h; Mon, 24 Mar 2014 02:53:55 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 44B5B1A0184; Mon, 24 Mar 2014 02:53:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 5EE54BE5C; Mon, 24 Mar 2014 09:53:54 +0000 (GMT)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ybp14VqWV1o5; Mon, 24 Mar 2014 09:53:54 +0000 (GMT)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 278B9BE57; Mon, 24 Mar 2014 09:53:54 +0000 (GMT)
Message-ID: <533000B2.9070500@cs.tcd.ie>
Date: Mon, 24 Mar 2014 09:53:54 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
References: <CAPv4CP9otoccFv9ARVHwqqF6nzKT-p7uDWF=ceCotiDCgL=rqA@mail.gmail.com> <201403241049032689006@cnnic.cn> <532FAA9F.7040200@gmail.com>
In-Reply-To: <532FAA9F.7040200@gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-privacy/JaR-XCN8gShgkKpi9Em5lwgSwGY
Cc: "ietf-privacy@ietf.org" <ietf-privacy@ietf.org>
Subject: Re: [ietf-privacy] [perpass] Wiki for managing PPM reviews of existing RFCs
X-BeenThere: ietf-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Internet Privacy Discussion List <ietf-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-privacy>, <mailto:ietf-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-privacy/>
List-Post: <mailto:ietf-privacy@ietf.org>
List-Help: <mailto:ietf-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-privacy>, <mailto:ietf-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Mar 2014 09:54:06 -0000

(bcc'ing perpass and moving this to ietf-privacy which
we agreed was a better list for this)

On 03/24/2014 03:46 AM, Melinda Shore wrote:
> On 3/23/14 6:49 PM, Jiankang Yao wrote:
>> it is a good start. thanks.
>> since there are thousands of RFCs, it is better that they can be
>> reviewd by category.
>> for example, based on the following category:
>> http://www.faqs.org/rfcs/np.html
> 
> I'm not sure about that - there are a lot of documents
> defining protocols that have never been implemented or
> deployed, and so on.  It seems likely to me that as this
> process is starting up, people will tend to review
> significant documents, which is what probably the best
> place to start anyway.  As more documents are reviewed
> there may be a need to become more systematic.  But
> for now, I think the current situation is good.

I agree with Melinda. Let's get a body of work done
that people want to do or feel is important to do
and then we can organise that.

So jump in and review something.

S.

> 
> Melinda
> 
> 
> _______________________________________________
> perpass mailing list
> perpass@ietf.org
> https://www.ietf.org/mailman/listinfo/perpass
>