The router object

 bonito at nis.garr.it (Antonio_Blasco Bonito) writes:

  * 
  * The example should list also interior peers with internal routing protocols
  * and the explanation text should mention that too.
  *
Well it does have an IBGP interior example. I can add something in the
text as well. 
  * > 
  * > 
  * >           <Interface Address> must be  a  "dotted-quad"  represented
  * >           host address.  It should be noted that at least ONE ifaddr
  * >           must be configured for the inet-rtr object  to  be  valid.
  * >           This  facilitates  the  registering of route servers which
  * >           may only have one interface address and are purely routing
  * >           engines.
  * 
  * Uhmmm, a route server which does not route packets but is only used by
  * actual routers as a source of routing information IS NOT a router. Does it
  * need to be registered? If yes I think it should be clearly distinguishable
  * by actual routers.
  *
Uhmmm..sorry not where I come from. A router is something that
exchanges routing information - I see no reason why a router needs to
forward packets. In fact a route server is specifically configured to
not to forward packets. You are confusing routing with forwarding. I see no
real reason to distinguish an RS. Whilst it is perhaps a special case
it still fits simply into the general schema of the object. By having
a single interface you give an indication of route serving (of course
you can forward in and out of this as well but..). 
It is not the intent of this object to catch every special case
(otherwise we have to support to ebgp multihop - tunnels, etc). 
  * > 
  * >      Examples:
  * > 
  * >           ifaddr: 192.87.45.190
  * >           ifaddr: 192.87.4.99 AS1755
  *                                 ^^^^^^
  * This should be removed after the mod from Tony, right?
  * 
Yep - overhanging mistake.


  * 
  * Text to be added:
  *             Note that in some cases a router configured as being in more
  *             than one AS can also peer with itself to exchange routes
  *             among its ASes
  *
Really ? what is the exact purpose of this and how is it acheived ?

  * > 
  * > notify:
  * >      The notify attribute contains an email address to which notifi-
  * >      cations of changes to this object should be send.
  * 
  * The meaning and usage of this attribute is not clear: which kind of changes
  * ?
  *
Any update - please look at the relavent ripe document for more
details.
ripe-096.txt btw.

  * > 
  * > maintainer:
  * >      The maintainer attribute contains a registered maintainer name.
  * 

  * The meaning and purpose of this attribute is not clear.

See ripe-096 for more details.

		--Tony.