AS3.5 received as AS_TRANS from 1 RIS peer
Following Surfnet's announcement of their as3.5 beacon to the nanog list, I had a quick look at RIS. (see below) For 93 peers the transition mechanism succeeds, the route collectors succesfully recreate a 4-byte AS path with 4-byte origin ASN. However, for 1 peer the RRC01 collector reports AS_TRANS as origin. This suggests the supposed transitive NEW_AS_PATH attribute was lost either in the peer or in one of its upstreams. BTW, has the APNIC 4-byte asn beacon been switched off? RISwhois only 'sees' two IPv4 prefixes with 4-byte origin ASNs: dog [~]; whois -h riswhois dump |grep '^[0-9]*\.[0-9]' 3.7 84.205.88.0/24 74 3.5 145.125.0.0/20 93 The RIS beacon, AS3.7, has somewhat less visibility than the route inserted by Surfnet (seen by 74 instead of 93 peers). -- Rene $ whois -h riswhois 145.125/20 % For more information visit http://www.ripe.net/ris/riswhois.html route: 145.125.0.0/20 origin: AS3.5 descr: SURFNET-NL SURFnet, The Netherlands lastupd-frst: 2007-03-29 11:54Z 80.81.192.8@rrc12 lastupd-last: 2007-04-10 15:27Z 198.32.160.179@rrc11 seen-at: rrc00,rrc01,rrc03,rrc04,rrc05,rrc06,rrc07,rrc10,rrc11,rrc12,rrc13,rrc14,rrc15 num-rispeers: 93 source: RISWHOIS route: 145.125.0.0/20 origin: AS23456 descr: AS_TRANS lastupd-frst: 2007-04-10 03:14Z 195.66.224.68@rrc01 lastupd-last: 2007-04-10 03:14Z 195.66.224.68@rrc01 seen-at: rrc01 num-rispeers: 1 source: RISWHOIS
Suggestion: contact the peer where AS_TRANS appears and try to trace this problem back. Write this up a little more formally and send it tot the routing-wg and nanog. Present at routing-wg @ talinn? Daniel
On Apr 11, 2007, at 7:53 AM, Daniel Karrenberg wrote:
Suggestion: contact the peer where AS_TRANS appears and try to trace this problem back.
Done already last week. They forwarded it to one of their upstreams that do some strange AS path mangling that may be related. Didn't get more from them yet, will poke them. cheers, -- Erik Romijn RIPE NCC jr. software engineer http://www.ripe.net/ Information Services dept.
On Apr 10, 2007, at 10:20 PM, Rene Wilhelm wrote:
BTW, has the APNIC 4-byte asn beacon been switched off? RISwhois only 'sees' two IPv4 prefixes with 4-byte origin ASNs:
So do the looking glasses. This did work before, so I assume they switched it off. cheers, -- Erik Romijn RIPE NCC jr. software engineer http://www.ripe.net/ Information Services dept.
On Tue, Apr 10, 2007 at 10:20:23PM +0200, Rene Wilhelm wrote:
The RIS beacon, AS3.7, has somewhat less visibility than the route inserted by Surfnet (seen by 74 instead of 93 peers).
This -might- be because peers filter on 12654$ for routes from rrc03. And therefore don't accept "12654 23456". We didn't send an announcement about this to the AMS-IX filter-updates list. RR data is up-to-date ofcourse. cheers, -- Erik Romijn RIPE NCC jr. software engineer http://www.ripe.net/ Information Services dept.
On Wed, 11 Apr 2007, Erik Romijn wrote:
On Tue, Apr 10, 2007 at 10:20:23PM +0200, Rene Wilhelm wrote:
The RIS beacon, AS3.7, has somewhat less visibility than the route inserted by Surfnet (seen by 74 instead of 93 peers).
This -might- be because peers filter on 12654$ for routes from rrc03. And therefore don't accept "12654 23456".
Understood. It was just an observation, not a complaint. RIS started with 'collecting only' and peers are under no obligation to forward announcements received from the route collectors. Still, 74 peers isn't bad at all.
We didn't send an announcement about this to the AMS-IX filter-updates list. RR data is up-to-date ofcourse.
-- Rene
participants (3)
-
Daniel Karrenberg -
Erik Romijn -
Rene Wilhelm