The router object

> 
> Here the latest draft with the comments from Blasco. I would like to
> have this agreed at the latest at the next RIPE meeting. Comments are
> of course still welcome. However, I am about to depart for a month so
> they will have to wait to be folded in.
> 
> 		--Tony.

An inconsistency due to working in a hurry, I guess...

> . . . 
> 
> 3.  Router Representation
> 
> The representation must be capable of representing both ``interior''
> and  ``border''  routers  within  ones  own  autonomous system. Each
> object is uniquely identified by its object name. Here is  a  simple
> example of a router object:
> 
> 
> inet-rtr: Amsterdam.ripe.net
> localas:  AS3333
> ifaddr:   192.87.45.190
> ifaddr:   192.87.4.28
> ifaddr:   193.0.0.222
> peer:     192.87.45.6 AS2122 BGP4
> peer:     193.0.0.219 AS2122 BGP
> peer:     193.0.0.221 AS1104 BGP
> peer:     192.87.4.18 AS1103 BGP4
> peer:     192.87.4.24 AS1103 BGP4
> peer:     192.87.4.20 AS286 BGP4
> peer:     192.87.4.5 AS3333 IBGP4
> peer:     192.87.4.2 AS3333 IGP
> admin-c:  Daniel Karrenberg
> tech-c:   Tony Bates
> tech-c:   Marten Terpstra
> notify:   ops at ripe.net
> remarks:  The router for the RIPE NCC
> changed:  tony at ripe.net 940720
> source:   RIPE
> 
> 
> This object provides several key pieces of  information.  The  exact
> syntax for each attribute is discussed in the next section. However,
> some general remarks about this example are  worthy  of  note.  From
> this  you  can see immediately that this router "Amsterdam.ripe.net"
> is in the autonomous system 3333 and  has  three  configured  inter-
> faces. You also see that it has several exterior peers and one inte-
                                                             ^^^
                                                   Should be two

> rior peer (192.87.45.6). Details of the actual routing protocol  are
             ^^^^^^^^^^^
  should be (192.87.4.5, 192.87.4.2)

> given.  This  can  be extremely useful. For example a BGP3 router is
> not CIDR [6] capable whereas a BGP4 capable router is. A tool  could
> use  this information when examining routing policy to see if a peer
> can make use of aggregation.  Finally, we also see who we  can  con-
> tact when problems occur with this router.
> 

----------                                                     ----------
Antonio_Blasco Bonito                          E-Mail: bonito at nis.garr.it
GARR - Network Information Service      c=it;a=garr;p=garr;o=nis;s=bonito
c/o CNUCE - Istituto del CNR                         Tel: +39 (50) 593246
Via S. Maria, 36                                    Telex: 500371 CNUCE I
56126 PISA   Italy                                   Fax: +39 (50) 904052
----------                                                     ----------