[secdir] secdir review of draft-sparks-genarea-imaparch

Carl Wallace <carl@redhoundsoftware.com> Sun, 05 May 2013 14:00 UTC

Return-Path: <carl@redhoundsoftware.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EF0B21F937E for <secdir@ietfa.amsl.com>; Sun, 5 May 2013 07:00:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 TJ2vbyULWGKH for <secdir@ietfa.amsl.com>; Sun, 5 May 2013 07:00:24 -0700 (PDT)
Received: from mail-qa0-x22b.google.com (mail-qa0-x22b.google.com [IPv6:2607:f8b0:400d:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 0411B21F933B for <secdir@ietf.org>; Sun, 5 May 2013 07:00:23 -0700 (PDT)
Received: by mail-qa0-f43.google.com with SMTP id bs12so1060615qab.2 for <secdir@ietf.org>; Sun, 05 May 2013 07:00:23 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:user-agent:date:subject:from:to:cc:message-id :thread-topic:mime-version:content-type:content-transfer-encoding :x-gm-message-state; bh=b3rT9rcm3Bo/duQP01DCVQHhzIEDzXpR3zHQq/YUV6s=; b=KgJ3EkVFes8nomFk7xUEmJtfAk09JpAePRehbhLesfpU/+8/RxkdoqIalio9nhr94l ve+vhZzFOQw4Rtw0TlDEfWofeWwR2lHQKIDAZtiAuvQcvH9+yzTF3azsMgCKk7NGWQWo ots/J8Xh9dCVUXzvufbVJ8qM33ufF4buy4lTzUwLhIN1jrCG/Z2Zl1dEVuwhvDklYgYb tX06dQaic5Y5PhI0/TOqsg5sWkMKxTPaRggxZaS8F207lIRURcAyhxmJJHGb5nYGDlcs uCjL15N3qG/o6PtlQtL3Waqn5UZXHm+omhgWBduqOcsAo0daTdAY6oLj2PfEeMTwUR4V 3zxw==
X-Received: by 10.224.198.134 with SMTP id eo6mr3934734qab.74.1367762423424; Sun, 05 May 2013 07:00:23 -0700 (PDT)
Received: from [192.168.2.7] (pool-173-79-106-247.washdc.fios.verizon.net. [173.79.106.247]) by mx.google.com with ESMTPSA id fq5sm31809495qab.2.2013.05.05.07.00.20 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 05 May 2013 07:00:22 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/14.3.1.130117
Date: Sun, 05 May 2013 10:00:22 -0400
From: Carl Wallace <carl@redhoundsoftware.com>
To: <draft-sparks-genarea-imaparch.all@tools.ietf.org>
Message-ID: <CDABDE36.4013C%carl@redhoundsoftware.com>
Thread-Topic: secdir review of draft-sparks-genarea-imaparch
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Gm-Message-State: ALoCoQkjr/uzAY9woQCj+v/VOEN8pkVZb8EYJM91IqnudXtwYqLtpuuJJRlrR9jS7BfES+bNIUQT
Cc: iesg@ietf.org, secdir@ietf.org
Subject: [secdir] secdir review of draft-sparks-genarea-imaparch
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 May 2013 14:00:24 -0000

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the IESG.
These comments were written primarily for the benefit of the security area
directors.  Document editors and WG chairs should treat these comments
just like any other last call comments.

This draft describes the requirements for providing an IMAP interface for
IETF mail archives.  The first item in the security considerations is
correct, but in general the security considerations seem too narrowly
focused on searching and storage.  Some discussion of the following may be
worthwhile: how the server is authenticated to users, how users are
authenticated to the server (unless the reference to the datatracker
system is viewed as sufficient), details of the interface with the
datatracker authentication system, (maybe) how archive integrity is
maintained, identification of what should or should not be logged.