Re: [Asrg] DNSSEC is NOT secure end to end

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Mon, 08 June 2009 05:23 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 97CFC3A6A95 for <asrg@core3.amsl.com>; Sun, 7 Jun 2009 22:23:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level:
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id znhk-LeDQjwn for <asrg@core3.amsl.com>; Sun, 7 Jun 2009 22:23:15 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by core3.amsl.com (Postfix) with SMTP id 240523A6989 for <asrg@irtf.org>; Sun, 7 Jun 2009 22:23:15 -0700 (PDT)
Received: (qmail 30973 invoked from network); 8 Jun 2009 06:55:13 -0000
Received: from unknown (HELO necom830.hpcl.titech.ac.jp) (202.249.37.19) by necom830.hpcl.titech.ac.jp with SMTP; 8 Jun 2009 06:55:13 -0000
Message-ID: <4A2CA014.8090701@necom830.hpcl.titech.ac.jp>
Date: Mon, 08 Jun 2009 14:22:28 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
References: <200905302032.n4UKVxaZ048822@givry.fdupont.fr> <4A21C0CB.8070409@necom830.hpcl.titech.ac.jp> <a123a5d60906072102j2bf5c117i30ce83140b5bf2b8@mail.gmail.com>
In-Reply-To: <a123a5d60906072102j2bf5c117i30ce83140b5bf2b8@mail.gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: Francis Dupont <Francis.Dupont@fdupont.fr>, ietf@ietf.org, Anti-Spam Research Group - IRTF <asrg@irtf.org>
Subject: Re: [Asrg] DNSSEC is NOT secure end to end
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jun 2009 05:23:16 -0000

Phillip Hallam-Baker wrote:

> I was at a dinner with Dave Clarke last week. Those who invoke his
> name in these arguments rarely seem to have read his paper on the end
> to end principle IN NETWORKING.

Which paper is, are you saying, "his paper"? The original one or
latter one (published in 2001) which includes discussion on PKI,
which I referred in previous mails.

As you say "IN NETWORKING", I'm afraid you haven't read his original
paper "END-TO-END ARGUMENTS IN SYSTEM DESIGN", which is on "system
design" in general and not necessarily "in networking". For example,
in the original paper, RISC (Reduced Instruction Set Computer) is
given as an example of end to end design.

> Depending on your level of abstraction you choose to work at you can
> argue that anything is an end.

Apparently, he taught you basic points in his original paper
but not beyond.

It is discussed in the original paper that:

	Identifying the ends
	Using the end-to-end argument sometimes requires subtlety
	of analysis of application requirements.
	one must use some care to identify the end points to which
	the argument should be applied.

Beyond the original paper, the application of the end to end
argument to PKI including DNSSEC is discussed in his latter
paper in 2001 with PROPERLY IDENTIFIED "end points". In the
paper, certificate authorities are identified to be third
parties. 

With the discussion, there is no point denying "DNSSEC is NOT
secure end to end".

> It would be nice if the paper was available in unencumbered form.

Both of the papers are freely downloadable.

The original paper:

http://web.mit.edu/Saltzer/www/publications/endtoend/endtoend.pdf

The paper in 2001:

http://www.csd.uoc.gr/~hy558/papers/Rethinking_2001.pdf

You should have read both of them to make the dinner more valuable.

> Publication in ACM does not help anything but the author's academic
> career.

I gave a link to the paper in 2001 through ACM because it has DOI,
assuming that anyone can use search engines and that all the people
who talks about the end to end principle should have read the
original paper in advance.

						Masataka Ohta