re: Doc Representing IP Info..

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

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa12816; 9 Nov 92 7:47 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa12812; 9 Nov 92 7:47 EST
Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa21949; 9 Nov 92 7:48 EST
Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id <g.04138-0@haig.cs.ucl.ac.uk>; Mon, 9 Nov 1992 12:05:52 +0000
Received: from waffle.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id <g.28618-0@bells.cs.ucl.ac.uk>; Mon, 9 Nov 1992 12:05:39 +0000
To: osi-ds@cs.ucl.ac.uk
Subject: re: Doc Representing IP Info..
Date: Mon, 09 Nov 92 12:05:35 +0000
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Jon Crowcroft <J.Crowcroft@cs.ucl.ac.uk>
Message-ID: <9211090748.aa21949@CNRI.Reston.VA.US>

it would be most useful if you could add :

Class D addresses for multicast (which is now in operational use.)_

and possibly very interesting if you could add...

multimedia Conference Name, plus class D address and transport Port used
&
conference member/site id

i have (unfortunately) no idea how this latter is best represented in
the DIT.

jon