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

[Gert Doering]

Hi,

On Fri, Aug 17, 2012 at 02:43:51PM +0200, "Roger Jørgensen" wrote:
> > On Fri, Aug 17, 2012 at 02:38:25PM +0200, Jeroen Massar wrote:
> >> 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.
> >
> > "Please send all BGP prefixes that you have in your routers, except those
> > that are generated in your AS or in downstream ASes and not advertised to
> > upstream (transit) routers"
> >
> > Might be too complicated to understand, tho...
> 
> "Please send us all BGP prefixes announced to your upstream (transit)" ?

No, that's not the right one.  GRH wants to see "what people see", so 
everything *received* from the upstream is much more worth for GRH than
"sent to upstream".

"sent to upstream" is only a useful criteria for prefixes generated 
internally (to differenciate between "the aggregate" and "all the 
unaggregated stuff one needs inside the AS, but the world should never
see").

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 306 bytes
Desc: not available
URL: <https://lists.cluenet.de/pipermail/ipv6-ops/attachments/20120817/6473b7a4/attachment.sig>