Typos in assignments

 rv at deins.informatik.uni-dortmund.de writes:

 * The initial announcement for <assign at ripe.net> probably was not perfectly cl
 * ear
 * to restrict the use of this address to 193.x.y  AND  I remember that for som
 * e
 * other reassignments (well, not my own) sent directly to DDN-NIC it was reque
 * sted
 * to channel all European reassignments via the NCC.
 * 
 * Thus I have been using assign at RIPE.net for updates which I intended to
 * "write-through" to DDN-NIC (all messages including records for "old"
 * blocks included a remark telling so).
 * 
 * If we would know a little more about the state of how data base alignment
 * between DDN-NIC and RIPE-NCC actually works or what the intended ways are,
 * it might become easier for local registries to avoid misinterpretation
 * of procedures. Sure, I know, that unfortunately progress on the data base
 * alignement/exchange issue has been lagging far behind behind our hopes
 * and needs for improvement, and I sure can appreciate some of the problems
 * standing in the way (including the courtesy not explain all the problems
 * in public).

OK, here;s a small update.  The database alignment is in a stage where
the exchange format is finished, and first tests with incorporating each
others information in exchange format has begun.  This week we will
start using the exchange format database that MERIT generates in the
RIPE database, to replace the current information with source MERIT. 
The NIC has had a big file with all 193 nets and contact people a few
weeks ago from the NCC to test the interaction tools they have written
for their databases.  We have not yet had any results from those tests. 

The procedure for aligning databases has not yet been established. We are
not quite sure whether to do this incremental or just a full update. My
guess is that this will be discussed at the SWIP BOF at the IETF next week.
If people have problems that result from the fact that the different
databases are not aligned we would like to hear from them, so we can take
action.

 * Well, we hope that with the INTERNIC service contracts now in place

Not yet. They start 1st of April.

 * t will get easier to establish a smooth data flow - and make it known to the
 * registries. Probably some folks will be discussing some of this somewhere
 * in Ohio in a weeks time...   (unapproved, closed mini-BOF in the 1:00 to 3:3
 * 0 AM
 * time after the social event? :-)

Fine with me ;-)

-Marten