23456 without AS4_PATH?

Egor Zimin lesnix at gmail.com
Sat Feb 28 10:38:31 CST 2009


Take a watch on this route:

show route 195.128.231.0/24 detail
[..omitted..]
                AS path: AS2 PA[5]: 39792 35320 AS_TRANS AS_TRANS 35748
                AS path: AS4 PA[4]: 35320 3.21 AS_TRANS 35748
                AS path: Merged[5]: 39792 35320 3.21 AS_TRANS 35748 I
[...omitted...]

AS4_PATH contain AS_TRANS, it's also RFC violation, isn't it ?

sthaug at nethelp.no пишет:
>> Anyone else seeing this:
>> *> 91.196.186.0/24  62.237.167.25                          0 3292 3549 15703 43531 23456 i
>>
>> http://www.ietf.org/rfc/rfc4893.txt
>> 6.  Transition
>>    An OLD BGP speaker MUST NOT use AS_TRANS as its Autonomous System
>>    number.
>>     
>
> Seeing it here too. On our 4-byte capable routers:
>
> 91.196.186.0/24    *[BGP/170] 1d 13:36:53, MED 0, localpref 105, from 193.75.0.204
>                       AS path: 16150 15703 43531 AS_TRANS I
>                       AS path: 3356 6461 15703 43531 AS_TRANS I
>                       AS path: 1299 3549 15703 43531 AS_TRANS I
>
> And on our non 4-byte capable routers it is simply shown as 23456. This
> ASN should not be used to originate prefixes, agreed.
>
> Steinar Haug, Nethelp consulting, sthaug at nethelp.no
>
>   

-- 
С уважением, 
   Егор Зимин





More information about the NANOG mailing list