bonito@nis.garr.it (Antonio_Blasco Bonito) writes: * * I meant IGP should be there too. Usually you get information on internal * routes via some IGP (OSPF, I-ISIS, RIP, IGRP, ...). It is wise to mention t * hat * in the example, I guess. * Okay. * > * * > Really ? what is the exact purpose of this and how is it acheived ? * * Suppose you are running two BGP processes in a router you may want to run * an IBGP between the two to echange routes eventually applying some policy * filtering to the exchange. Exactly what is done if you have two different * boxes... * Is this possible to do ??? in the same box. The BGP RIB(s) (i.e. its tables, the Adj-RIBs-In, the Loc-RIB, and the Adj-RIBs-Out) are single for whole box. Also IBGP is a sync not a policy setter. Two boxes is a subtle difference plus the IBGP part will only be of interest in terms of the Exterior routes passed in the IBGP. I would be interested if there is such a box that can have (currently) more than one (effective) BGP process in a box. I am a little lost on this matter I must admit ? * > * > * > * > * > 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 c * hanges * > * ? * > * * > Any update - please look at the relavent ripe document for more * > details. * > ripe-096.txt btw. * * OK, so please insert a reference to ripe-096 in the text. * Will do.... * > * > * > * > * > 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. * * OK, so please insert a reference to ripe-096 in the text. * Will do... Thanks for your comments. --Tony.