Re: IP namespace (Was: Re: root knowledge)
"William C. Green" <W.Green@utexas.edu> Wed, 13 May 1992 23:43 UTC
Received: from nri.nri.reston.va.us by ietf.NRI.Reston.VA.US id aa04762; 13 May 92 19:43 EDT
Received: from nri.reston.va.us by NRI.Reston.VA.US id aa16137; 13 May 92 19:49 EDT
Received: from bells.cs.ucl.ac.uk by NRI.Reston.VA.US id aa16132; 13 May 92 19:49 EDT
Received: from mojo.ots.utexas.edu by bells.cs.ucl.ac.uk with Internet SMTP id <g.12970-0@bells.cs.ucl.ac.uk>; Wed, 13 May 1992 22:39:27 +0100
Received: from wowbagger.cc.utexas.edu by mojo.ots.utexas.edu with SMTP id AA04816 (5.65+/IDA-1.3.5 for osi-ds@cs.ucl.ac.uk); Wed, 13 May 92 16:39:16 -0500
Date: Wed, 13 May 1992 16:11:54 -0600
From: "William C. Green" <W.Green@utexas.edu>
Sender: "William C. Green" <green@wowbagger.cc.utexas.edu>
Subject: Re: IP namespace (Was: Re: root knowledge)
To: osi-ds@cs.ucl.ac.uk
In-Reply-To: <9205131240.AA00325@spartacus.psi.com>
Message-Id: <MailManager.705795114.176.green@wowbagger.cc.utexas.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
It seems to me that the Internet should not appear under o=Internet somewhere in the DIT (whichever DIT this happens to be), but rather should be an ADDMD. The Internet ADDMD might have 'connections' to multiple listing services, one of which might be NADF, for example. This would not only yield great flexibility for organization under the Internet ADDMD, but would work well when it comes to maintaining public portions of other DITs, like the public portion of the NADF DIT. I may be missing something very basic though. -- Will
- IP namespace (Was: Re: root knowledge) Thomas Johannsen
- Re: IP namespace (Was: Re: root knowledge) yeongw
- Re: IP namespace (Was: Re: root knowledge) William C. Green
- Re: IP namespace (Was: Re: root knowledge) Christian Huitema
- Re: IP namespace (Was: Re: root knowledge) Thomas Johannsen
- Re: IP namespace (Was: Re: root knowledge) Steve Hardcastle-Kille