Reply to Mapping trees populated

Kevin Jordan <Kevin.E.Jordan@cdc.com> Mon, 23 January 1995 04:22 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08989; 22 Jan 95 23:22 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa08985; 22 Jan 95 23:22 EST
Received: from mercury91.udev.cdc.com by CNRI.Reston.VA.US id aa16014; 22 Jan 95 23:22 EST
Received: by mercury.udev.cdc.com; Sun, 22 Jan 95 22:07:22 -0600
X-From: kej@mercury.udev.cdc.com Sun Jan 22 22:07 CST 1995
Received: from localhost by mercury.udev.cdc.com; Sun, 22 Jan 95 22:07:19 -0600
To: Harald.T.Alvestrand@uninett.no
cc: mhs-ds@mercury.udev.cdc.com
Subject: Reply to Mapping trees populated
In-reply-to: Your message of "Sun, 22 Jan 95 18:48:10 +0100" <199501221748.SAA02573@dale.uninett.no>
Date: Sun, 22 Jan 95 22:07:18 -0600
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Kevin Jordan <Kevin.E.Jordan@cdc.com>
Message-Id: <2f232b77382b002@mercury.udev.cdc.com>

> What is the update schedule?
> That is, how often do you update the tree from the tables?

I have exchanged mail with Urs about this.  I am planning to update the trees
once per day by obtaining a copy of the daily updates from SWITCH, running
"diff" against these and the previous day's data, and using this information
to add/modify/delete new/old entries.  This system should be operational in
the next few days.