[connect-bof] Peering

Le 15/11/2013 21:35, Gordon Lennox a écrit :
> People I have worked with in the past have viewed peering as something primitive, something akin to barter. I don't agree and I strongly don't agree. But maybe why I personally don't agree is for another time.
>
> But if people want to change that initial perception then maybe AS3320 is not the best target right now.
>
> What about the European Commission? 
>
> In some ways they are a politically important, highly visible, not-for-profit "ISP". In these times they should be looking to reduce costs by peering. If they are then it should be made known. If they are not then the question could be put.
>
> I remember also being told they had an interesting chunk of v4 space. I am not sure whether they have applied for v6 space.

Hi Gordon, friends, public info:

mh at home:~$ whois -h whois.ripe.net -i origin AS3320 |grep route6
route6:         2001:67c:14c4::/48
route6:         2003::/19
route6:         2003::/20
route6:         2a00:8a00:6000::/35
route6:         2a01:598::/29
mh at home:~$

... I worked from time to time with Ruediger to kick these into the 
peering with AS6453,
Teleglobe/Tata, with some success, before my late departure.

Sanity-check of my statement:


route-views6.routeviews.org> sh bgp regexp _3320_
BGP table version is 0, local router ID is 128.223.51.112
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal,
              r RIB-failure, S Stale, R Removed
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
*  2001:3b8::/32    2001:1890:111d::1
                                                           0 7018 3320
2527 i
*  2001:62a::/31    2001:240:100:ff::2497:2
                                                           0 2497 3320
1764 760 i
*  2001:638::/32    2001:428::205:171:203:138
                                       8000051             0 209 3320 680 i
*  2001:678:c::/48  2001:240:100:ff::2497:2
                                                           0 2497 3320
2484 i
*  2001:678:88::/48 2001:418:0:1000::f000
                                             0             0 2914 3320
12578 15440 42549 44358 i
*                   2001:240:100:ff::2497:2
                                                           0 2497 3320
12578 15440 42549 44358 i
*  2001:67c:14::/48 2001:200:901::5                        0 7660 2516
3320 15456 15960 ?
*  2001:67c:fc::/48 2001:200:901::5                        0 7660 2516
3320 15456 15960 ?
<snip/>

and

route-views6.routeviews.org> sh bgp regexp _3320$
BGP table version is 0, local router ID is 128.223.51.112
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal,
              r RIB-failure, S Stale, R Removed
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
*  2001:67c:14c4::/48
                    2001:4830::5           562             0 30071 6939
9121 3320 i
*                   2600:803::15                           0 701 6939
9121 3320 i
*                   2001:4830::e            72             0 30071 6939
9121 3320 i
*                   2001:200:901::5                        0 7660 4635
6939 9121 3320 i
<snip/>

... seen worse.

I agree, that peering is generally a good thing (engineer I am since
some time now),
business model of yesterday in need of thoughtful remake I hear/think
since quite a
while now. Let's not forget about the extra-financial bits.;-)

Cheers,
mh

>
> Gordon
>
>
> _______________________________________________
> connect-bof mailing list
> connect-bof at ripe.net
> https://www.ripe.net/mailman/listinfo/connect-bof