GRH Peering Policy (Was: 1::1/128 + 2::2/128 - GRH Anomalies Delta (2012-08-17))

[Daniel Roesen]

On Fri, Aug 17, 2012 at 02:38:25PM +0200, Jeroen Massar wrote:
> In the current system it would not be possible, but the idea
> in my head (grh specific bgpd) would allow a peer to say 'if this
> community is present it is an internal route not exported to clients'
> and avoid this issue but does allow one to send all prefixes that way.

How many peers do you think will manage to tag things up properly? :)

> As such, if possible please formulate a proper GRH peering policy that
> works best for the community that uses the system, we can then put it up
> on the GRH pages and inform peers of this change.

"Send the set of prefixes you send to downstream BGP customers".

Plain simple.

Best regards,
Daniel

-- 
CLUE-RIPE -- Jabber: dr at cluenet.de -- dr at IRCnet -- PGP: 0xA85C8AA0