Re: Experimental ICMP Domain Name messages - RFC-to-be

Paul Mockapetris <pvm@isi.edu> Mon, 20 March 1995 06:14 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa15535; 20 Mar 95 1:14 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa15531; 20 Mar 95 1:14 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa17115; 20 Mar 95 1:14 EST
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa15523; 20 Mar 95 1:14 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa15519; 20 Mar 95 1:14 EST
Received: from venera.isi.edu by CNRI.Reston.VA.US id aa17110; 20 Mar 95 1:14 EST
Received: from zephyr.isi.edu by venera.isi.edu (5.65c/5.61+local-21) id <AA13578>; Sun, 19 Mar 1995 22:14:58 -0800
Received: from aloha.isi.edu by zephyr.isi.edu (5.65c/5.61+local-17) id <AA24378>; Sun, 19 Mar 1995 22:14:58 -0800
Message-Id: <199503200614.AA24378@zephyr.isi.edu>
To: jkrey@isi.edu
Cc: scoya@CNRI.Reston.VA.US, iesg@isi.edu, rfc-editor@isi.edu
Reply-To: pvm@isi.edu
Subject: Re: Experimental ICMP Domain Name messages - RFC-to-be
In-Reply-To: Your message of Fri, 17 Mar 1995 10:45:50 -0800. <199503171845.AA03359@akamai.isi.edu>
Date: Sun, 19 Mar 1995 22:14:00 -0800
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Paul Mockapetris <pvm@isi.edu>

As one would expect, Bill doesn't deal in grey, just black or white.
The discussion of IN-addr seems a bit exaggerated.

I would wonder whether the IPv6 world has really given up on the
reverse domain.

Anyway, there are some technical questions:

Are these responses cached?  If so, how?

How is this integrated with other DNS services, if at all?

It seem like there is a bootstrapping problem whereby you have to know
a key associated with the destination to securely ask it for its name.
A short explanation would be good.

paul
 
USC/Information Sciences Institute      phone: 310-822-1511 x285
4676 Admiralty Way, Marina del Rey, CA  fax:   310-823-6714
90292