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

["J-F C. (Jefsey) Morfin" <[e-mail]>]

At 16:01 26/03/04, Pekka Savola wrote:

>On Fri, 26 Mar 2004, J-F C. (Jefsey)  Morfin wrote:
> > Oh! I try to get the text more specific!
> >
> > What I mean is that if you introduce a new concept in the DNS
> > affecting the availability/existance of the RRs you should make
> > ita very precise feature. From what I gather the TTO would be the
> > delay before non called entry should be discarded. I think the
> > concept is great as it may really help managers tracing their
> > own mismanagement.
> >
> > 1. I do not know where it is to be introduced because I do not
> >      see easily how it may survive a reload (we are talking of the
> >      master file management). This means an associated base
> >      keeping the date of the last use and called at loading time.
> >
> > 2. this would pemit a feature I want for a long in the DNS, which
> >      is temporary names for security/ebusiness purposes. If I set
> >      a TTO of 15 minutes and a TTL of 5 minutes on a Dynamic
> >      entry : the name will be valid for 20 minutes maximum on the
> >      network.
>
>
>I think there has been a misunderstanding about the context where such
>a janitorial process would operate.  I was not proposing changes to
>DNS records, but rather how the zones are operated.

Full agreement. It is just that something timely negative (removing on a 
time condition cannot be limited to zone management) you need
indepednent references.


>After you've collected a lot of data like this, you would run some process 
>which would find the old information from the pile, and remove their 
>records from the DNS files.

Yes. my idea was not to remove them from DNS files (authority decision and 
you do not know if they arenot generated by another process - I use virtual 
zones to support IDNA and co-registries). Just not to load them and report, 
the manager could force them.

I tend to think that IPv6 will lead to a drastic change in the files 
actually used by the zone managers.

>doesn't need to go into this document, especially if it takes a lot of 
>time to "get right".

Yes. Far too premature. IPv6 is the first significant change in the DNS for 
20 years. A lot of delayed needs will show up. They shouldl stabilize first 
and be reduced to a simple common configuration language or format.
jfc







>--
>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