Re: Doc Representing IP Info..

Jon Crowcroft <J.Crowcroft@cs.ucl.ac.uk> Mon, 09 November 1992 20:03 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa21914; 9 Nov 92 15:03 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa21909; 9 Nov 92 15:03 EST
Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa06623; 9 Nov 92 15:04 EST
Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id <g.06893-0@haig.cs.ucl.ac.uk>; Mon, 9 Nov 1992 18:44:34 +0000
Received: from waffle.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id <g.24207-0@bells.cs.ucl.ac.uk>; Mon, 9 Nov 1992 18:44:15 +0000
To: Sylvain Langlois <Sylvain.Langlois@der.edf.fr>
cc: Jon Crowcroft <J.Crowcroft@cs.ucl.ac.uk>, osi-ds@cs.ucl.ac.uk, J.Crowcroft@cs.ucl.ac.uk
Subject: Re: Doc Representing IP Info..
In-reply-to: Your message of "Mon, 09 Nov 92 16:06:10 +0100." <27139.721321570@cli53an>
Date: Mon, 09 Nov 92 18:44:14 +0000
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Jon Crowcroft <J.Crowcroft@cs.ucl.ac.uk>
Message-ID: <9211091504.aa06623@CNRI.Reston.VA.US>


 >> multimedia Conference Name, plus class D address and transport Port used
 >> & > conference member/site id
 >I might be wrong but if your aim is to represent a particular instance
 >of an ongoing  conference  into the DIT, the information is not stable
 >enough  to  be able to  be  represented  in  the  Directory. I  'm not

Sylvain

if a conference is longterm as the ietf one (i.e. 224.2.0.1/3456) then
it is certainly approprtiate to put such info in the directory imho

cheers

 jon