Thomas Johannsen <> Mon, 06 July 1992 04:45 UTC

Received: from by IETF.NRI.Reston.VA.US id aa04601; 6 Jul 92 0:45 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa04597; 6 Jul 92 0:45 EDT
Received: from by NRI.Reston.VA.US id aa17522; 6 Jul 92 0:47 EDT
Received: from by with local SMTP id <>; Mon, 6 Jul 1992 05:08:43 +0100
Received: from by with Internet SMTP id <>; Mon, 6 Jul 1992 05:08:34 +0100
Received: from by (5.65+1.6W/2.8Wb-jp-gate/1.2) with SMTP id AA10640; Mon, 6 Jul 92 13:08:26 JST
Received: from ([]) by (4.1/2.7W) id AA10384; Mon, 6 Jul 92 13:08:20 JST
Received: from by (4.0/6.4J.6-92/2) id AA11286; Mon, 6 Jul 92 13:08:19 JST
Received: by (4.1/6.4J.6-91/1/29) id AA00268; Mon, 6 Jul 92 13:08:18 JST
Date: Mon, 6 Jul 92 13:08:18 JST
From: Thomas Johannsen <>
Return-Path: <>
Message-Id: <>
Subject: Re: DNS on CLNP RRs
In-Reply-To: Mail from 'George Michaelson <>' dated: Mon, 06 Jul 92 13:02:53 +1000

> These people are representing OSI network layer address info and
> mapping into DNS hostnames, which I think requires to be added to the
> set of objects represented in X.500, and preferably mastered there.
> I think you're talking about the generalized model for adding DNS info into
> the X.500 DIT. This isn't exactly the same thing!
> -George

That's right, I didn't talk about OSI address info. But I think I'm coming
from the other end to that question: Where and how do you store this kind
of information in the DIT. 

RFC 1279 proposes a DNS tree which has pointers to the organizational tree
(i.e. c/o/ou/cn). Actually the latter should be the place to hold infos
about hosts or nodes or whatever you'd like to call them. We have proposed
to set up a second "index tree" for IP numbers. From there again you'll
find pointers to objects within an organization. 

Node objects have attributes holding values for IP, domain name etc. 
I think the same scheme can be used for other address information. We
would have one entry per host with all applications, addresses and other
properties attached and several index mechanisms to come from addresses
(which, unfortunately, do not fall into this c/o/ou tree) to the node.