Week 1 Status Report

Tony,

>   * 
>   * Fine here.  Any mechanism you'd like would be ok.  Perhaps "patch", with
>   * full releases the last day of every month, and a patch distribution numbere
>   * d
>   * the day of the month for the 1st, 2nd, ...  ?  
>   * 
> This is fine for the DB. For pride tools (which I'm not sure you mean) I
> don't want anything too restrictive. Currently it is still quite early days
> for the tools so we need flexibility to release as we need rather than
> by date or anything else.

Yep;  this was only for nightly transfers of our respective parts of the
DB each way.  For tools, I presume you'd release or patch as required.

...

> I'd like to bring up one other thing which is important in the tools which
> may have been overlooked. That of nets which are DMZs. Network entries
> have an attribute known as ias-int. This allows the network owner to register
> interfaces on his net belonging to other ASes. This is a special case
> and away from the one net / one AS idea we have. This is not guarded 
> but should be used wherever possible.

Yes, we've looked at this here.  Is there a particular action item for
Merit, other than encouraging anyone who uses our copy of the database to
fill them in?  (Since we're using your software almost unmodified, we
automatically get this stuff for free, right?  Or do we need to add in
some code not yet in the beta release that we've picked up?)


Thanks for the documentation!  (If you need reviewers of early drafts,
we're hungry for new docs...)

-Dale



-------- Logged at  Wed Feb 23 00:02:57 MET 1994  ---------