[secdir] Secdir review of draft-ietf-alto-reqs

Paul Hoffman <paul.hoffman@vpnc.org> Sat, 14 January 2012 23:46 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 4751B21F84CE for <secdir@ietfa.amsl.com>; Sat, 14 Jan 2012 15:46:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.456
X-Spam-Level:
X-Spam-Status: No, score=-102.456 tagged_above=-999 required=5 tests=[AWL=-0.084, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, 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 o3OI5nLOvuJu for <secdir@ietfa.amsl.com>; Sat, 14 Jan 2012 15:46:28 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id D8FB321F84C4 for <secdir@ietf.org>; Sat, 14 Jan 2012 15:46:27 -0800 (PST)
Received: from [10.20.30.103] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.3) with ESMTP id q0ENkNMF094256 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 14 Jan 2012 16:46:25 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 14 Jan 2012 15:46:23 -0800
Message-Id: <D3945394-26BF-42A9-8886-BD5FB4970AAC@vpnc.org>
To: secdir <secdir@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1251.1)
X-Mailer: Apple Mail (2.1251.1)
Cc: draft-ietf-alto-reqs-all@tools.ietf.org
Subject: [secdir] Secdir review of draft-ietf-alto-reqs
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: Sat, 14 Jan 2012 23:46:28 -0000

Greetings again. This is a security review of draft-ietf-alto-reqs, "Application-Layer Traffic Optimization (ALTO) Requirements". An ALTO protocol would allow optimization of network resources when information is in multiple places; a client can ask a server where to get the information, and the server can give hopefully-intelligent answers based on what the server knows of the network load, server load, network topology, and so on.

This document does quite a good job of covering the many security issues with such a protocol. It lays out many of the competing security considerations, particularly the privacy of each party and, being a requirements document, doesn't answer any of the hard questions that will need to come in the upcoming protocol document.

--Paul Hoffman