IETF Logo Mail Archive

Re: [dnsext] draft-mohan-dns-query-xml-00.txt

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Wed, 05 October 2011 05:07 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 651B521F858C for <dnsext@ietfa.amsl.com>; Tue, 4 Oct 2011 22:07:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.04
X-Spam-Level:
X-Spam-Status: No, score=-0.04 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 E2l82xM5tigq for <dnsext@ietfa.amsl.com>; Tue, 4 Oct 2011 22:07:53 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 9092921F8569 for <dnsext@ietf.org>; Tue, 4 Oct 2011 22:07:51 -0700 (PDT)
Received: (qmail 47087 invoked from network); 5 Oct 2011 05:26:07 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 5 Oct 2011 05:26:07 -0000
Message-ID: <4E8BE6DF.5040201@necom830.hpcl.titech.ac.jp>
Date: Wed, 05 Oct 2011 14:10:55 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
References: <20111004143947.205a61dff9fc1684c258b274662bb912.04bcda2f2f.wbe@email00.secureserver.net> <CAH1iCir9T0kSL=_-f_FW1jcfN3D+z5tHc18ML0L9h5Znm45vZw@mail.gmail.com> <4E8BD559.3060502@necom830.hpcl.titech.ac.jp> <20111005042728.4D8A514A46C1@drugs.dv.isc.org>
In-Reply-To: <20111005042728.4D8A514A46C1@drugs.dv.isc.org>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Cc: dnsext@ietf.org
Subject: Re: [dnsext] draft-mohan-dns-query-xml-00.txt
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2011 05:07:53 -0000

Mark Andrews wrote:

> Personally, I look at my wristwatch.

You may but your computers can not.

> DNSSEC only requires loose
> time syncronization.  Most machines, provided they have a battery
> backed up clock, could run their entire life on the time as set
> by the manufacturer.

A problem is that, even though an hour of error is not significant
to DNSSEC, it is significant to most other purposes, which
means the clock is synchronized to external source.

						Masataka Ohta

v2.23.0 | Report a Bug | By Email