IETF Logo Mail Archive

Re: [DNSOP] Fw: New Version Notification for draft-yao-dnsop-root-cache-00.txt

Robert Edmonds <edmonds@mycre.ws> Wed, 28 October 2015 22:39 UTC

Return-Path: <edmonds@mycre.ws>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01C9F1B29CA for <dnsop@ietfa.amsl.com>; Wed, 28 Oct 2015 15:39:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.51
X-Spam-Level:
X-Spam-Status: No, score=-0.51 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, T_RP_MATCHES_RCVD=-0.01] 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 kArRvPRK9Kfp for <dnsop@ietfa.amsl.com>; Wed, 28 Oct 2015 15:39:23 -0700 (PDT)
Received: from chase.mycre.ws (chase.mycre.ws [70.89.251.89]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09C8B1A0021 for <dnsop@ietf.org>; Wed, 28 Oct 2015 15:39:23 -0700 (PDT)
Received: by chase.mycre.ws (Postfix, from userid 1000) id 536D81C40200; Wed, 28 Oct 2015 18:39:22 -0400 (EDT)
Date: Wed, 28 Oct 2015 18:39:22 -0400
From: Robert Edmonds <edmonds@mycre.ws>
To: Bob Harold <rharolde@umich.edu>
Message-ID: <20151028223922.GA7699@mycre.ws>
References: <201509291227269136613@cnnic.cn> <20150929092049.4d005a16@casual> <CA+nkc8DExG8=hpJzmE8qmjbsj3njzVGQFNH5aXwEgUrG6GgE6g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CA+nkc8DExG8=hpJzmE8qmjbsj3njzVGQFNH5aXwEgUrG6GgE6g@mail.gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/XuaYT3Su_m3KUnvdkeDy5cwUIOg>
Cc: Shane Kerr <shane@time-travellers.org>, Jiankang Yao <yaojk@cnnic.cn>, dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] Fw: New Version Notification for draft-yao-dnsop-root-cache-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Oct 2015 22:39:24 -0000

Bob Harold wrote:
> Reading these various ideas brings up a question in my mind.  If a server
> queries for the SOA of a zone and the serial number has not changed, can it
> then assume that all of the entries in its cache for that zone should still
> be valid now, and for the their original TTL value starting now?  If the
> values had changed, wouldn't the serial # also change?  Seems like I must
> be missing something here.

No inferences like that can be drawn based on the SOA SERIAL field,
because the serial number may have wrapped around to the same value that
was observed previously.  (Even if the time between queries is very
small, there is still a finite window of time during which the zone
publisher can fit as many zone updates into as needed -- at least
conceptually.)

-- 
Robert Edmonds

v2.23.0 | Report a Bug | By Email