Re: draft-ietf-dnsop-ipv6-dns-issues-04.txt [Re: [dnsop] WG Last Call: draft-ietf-dnsop-misbehavior-against-aaaa-00.txt]

Pekka Savola <pekkas@netcore.fi> Fri, 26 March 2004 09:32 UTC

Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09504 for <dnsop-archive@lists.ietf.org>; Fri, 26 Mar 2004 04:32:41 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1]) by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i2Q7njRE018696 for <dnsop-outgoing@darkwing.uoregon.edu>; Thu, 25 Mar 2004 23:49:45 -0800 (PST)
Received: (from majordom@localhost) by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i2Q7njjw018695 for dnsop-outgoing; Thu, 25 Mar 2004 23:49:45 -0800 (PST)
Received: from netcore.fi (netcore.fi [193.94.160.1]) by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i2Q7nhDQ018602 for <dnsop@lists.uoregon.edu>; Thu, 25 Mar 2004 23:49:44 -0800 (PST)
Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id i2Q7nZi04292; Fri, 26 Mar 2004 09:49:35 +0200
Date: Fri, 26 Mar 2004 09:49:35 +0200
From: Pekka Savola <pekkas@netcore.fi>
To: "J-F C. (Jefsey) Morfin" <jefsey@club-internet.fr>
cc: dnsop@lists.uoregon.edu
Subject: Re: draft-ietf-dnsop-ipv6-dns-issues-04.txt [Re: [dnsop] WG Last Call: draft-ietf-dnsop-misbehavior-against-aaaa-00.txt]
In-Reply-To: <6.0.1.1.2.20040325165452.04c57660@mail.club-internet.fr>
Message-ID: <Pine.LNX.4.44.0403260948150.3028-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Pekka Savola <pekkas@netcore.fi>

On Thu, 25 Mar 2004, J-F C. (Jefsey)  Morfin wrote:
> At 14:23 25/03/04, Pekka Savola wrote:
> >OK; I tried to fuel the thinking a bit:
> >
> >         <t>A problem with defining the clean-up process is that it is
> >difficult to ensure that a specific IP address and the corresponding
> >record are no longer being used.  Considering the huge address space,
> >and the unlikelyhood of collision within 64 bits of the interface
> >identifiers, a process which would remove the record after no traffic
> >has been seen from a node in a period of time (e.g., a year) might be
> >one possible approach.</t>
> 
> Great: I mean in term of explaining - however I am not sure it
> should not call for a TTO (Time to Obsolecence) to be specified?

This was added just to convey the time frame, that is, "months or
years" rather than "every hour".  I'll change it to be a bit more 
vague..

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html