Re: [ietf-privacy] old RFC reviews - please try this...

Scott Brim <scott.brim@gmail.com> Tue, 20 May 2014 11:04 UTC

Return-Path: <scott.brim@gmail.com>
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 50E201A033D for <ietf-privacy@ietfa.amsl.com>; Tue, 20 May 2014 04:04:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 K0zPx11NY8uA for <ietf-privacy@ietfa.amsl.com>; Tue, 20 May 2014 04:04:42 -0700 (PDT)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 186E61A032F for <ietf-privacy@ietf.org>; Tue, 20 May 2014 04:04:42 -0700 (PDT)
Received: by mail-ob0-f174.google.com with SMTP id uz6so292060obc.19 for <ietf-privacy@ietf.org>; Tue, 20 May 2014 04:04:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zHTrr/yqq9iZrt54l3sZyKJfYN41NfHCrs/YTMK61ac=; b=yqJspSImjqo9UT5QSs/cY7z6WbqvhoKcLAZudrEYnqVIY+64SwEwxkKD8McftIh3QX rPikTf0NI1CBE37cNYljMrnUU5pQLVWJaUVN9pULumr6uVH6qSKg8sCZOMXHU9joevkk LXXSnl6MJrEjrgCT8peMCo6kQG7BnU6MewWXxEztQsTg5m1uJ103egPKD53KtWl9nVR6 qAkJ4VhKahrE7VLeDcwzvP84bMsVnL4Ft8DGiKPa9HpL5Xf5mjXlx1jNljby+V01zTBg p1hx56Sxw0bR+uz9G+BLIv3JZD9Ue9pCTvSal322cUKp8ZeoSAlD7+KTAyjI6TWUgpqi qwOQ==
MIME-Version: 1.0
X-Received: by 10.60.73.97 with SMTP id k1mr31091254oev.54.1400583881433; Tue, 20 May 2014 04:04:41 -0700 (PDT)
Received: by 10.183.8.7 with HTTP; Tue, 20 May 2014 04:04:41 -0700 (PDT)
Received: by 10.183.8.7 with HTTP; Tue, 20 May 2014 04:04:41 -0700 (PDT)
In-Reply-To: <537B1F16.9070801@cs.tcd.ie>
References: <537B1F16.9070801@cs.tcd.ie>
Date: Tue, 20 May 2014 07:04:41 -0400
Message-ID: <CAPv4CP8FT_yBL-vh2zNNjcKRsWRDwyTYfY7VKoh0J-dh4O0E1Q@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary=001a1134c67cbb294a04f9d2d8ed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-privacy/kE1coJwBHSkC8N4FNyVHjk_iGXU
Cc: ietf-privacy@ietf.org
Subject: Re: [ietf-privacy] old RFC reviews - please try this...
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: Tue, 20 May 2014 11:04:43 -0000

Here's a further suggestion: use the random draw as a starting point for an
RFC cluster. For example, if you get 5068, follow the normative references
toward the critical RFCs for mail and make sure those get done too.

Scott