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

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

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03600; 20 Mar 95 10:07 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa03596; 20 Mar 95 10:06 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa06793; 20 Mar 95 10:06 EST
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03589; 20 Mar 95 10:06 EST
Received: from zephyr.isi.edu by IETF.CNRI.Reston.VA.US id aa03585; 20 Mar 95 10:06 EST
Received: from zephyr.isi.edu by zephyr.isi.edu (5.65c/5.61+local-17) id <AA05053>; Mon, 20 Mar 1995 07:07:24 -0800
Message-Id: <199503201507.AA05053@zephyr.isi.edu>
To: Scott Bradner <sob@newdev.harvard.edu>
Cc: iesg@IETF.CNRI.Reston.VA.US
Reply-To: pvm@isi.edu
Subject: Re: Experimental ICMP Domain Name messages - RFC-to-be
In-Reply-To: Your message of Mon, 20 Mar 1995 07:58:13 -0500. <199503201258.HAA04750@newdev.harvard.edu>
Date: Mon, 20 Mar 1995 07:07:24 -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>

Scott,

Its really an IPng issue.  The DNS people should be involved with this
only if some new feature in DNS is required, not if IPng decides not
to use the DNS.

The DNS is extremely flexible in supporting non-use.

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