Thoughts on router object

	I do not care about the name. As long as it can represent
border *and* internal routers. Routers will be looked up by their ip addresses,
so the definition of the name is kind of loose. A router can have several
DNS names. I 'd like to change the syntax to:

SYNTAX:  text string

> > router:                 MANDATORY, UNIQUE
> > 	The domain of the router.
> > 	SYNTAX:  Full qulified domain name without trailing "."
> > 	EXAMPLE: router: t3-0.enss132.t3.ans.net
> > 	Merit extension
> > 

	You can forget about the db_reference stuff. It is useless.
As for the 'peer' definition', we  (ala and rlr) are working with
some NSP in order to include any attributes needed to generate a *full* cisco
config file. The definition of the peer is still pending so maybe we can
ignore it until we find out more about what information we need.
		Laurent
PS: I didn't write this document :) Just the ??????
-- 
Laurent Joncheray,                                 E-Mail: lpj at merit.edu
    Merit Network Inc, 1071 Beal Avenue,           Phone:  +1 (313) 936 2065
    Ann Arbor, MI 48109, USA                       Fax:    +1 (313) 747 3745
"This is the end, Beautiful friend. This is the end, My only friend, the end" JM



-------- Logged at  Fri Jul 15 20:52:52 MET DST 1994  ---------