[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unidata IDD project status

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: Unidata IDD project status
  • Date: Thu, 10 Jun 1999 10:18:44 -0600 (MDT)
Kai,

Our first tier and some second tier IDD topology nodes are all on vBNS.
Without this architecture the data rates and latencies would be
unacceptable. At this time we estimate that the IDD delivers over 180
gigabytes of data over 150 sites per day. For detail information on the
IDD data rates and architecture look at our IDD web pages. at:

http://www.unidata.ucar.edu/projects/idd/statsummary.html
http://www.unidata.ucar.edu/projects/idd/iddgeneral.html#status


If you have any questions let me know.

Robb... 



On Wed, 9 Jun 1999, Kai Chen wrote:

> 
> Dear Robb Kambic,
> 
> We are preparing a report to NSF about vBNS utilizations, and your Unidata
> IDD project comes into our scope.
> 
> We would like to know the status of your project, how much network
> bandwidth being used, and your future plans, etc. Could you please send me
> an email, or call me at 217-265-4078?
> 
> Thank you.
> 
> -Kai
> 
> --
> Kai Chen                Research Programmer
> 217-265-4078            NLANR Application Support
> address@hidden         NCSA - U of Illinois at Urbana-Champaign
> 
> 

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================