Hello @Mitrixsen,
When a router that supports 4-Byte ASNs advertises routes to routers that do not support 4-Byte ASNs, it uses a special AS_TRANS value in the AS Path field. This AS_TRANS value indicates that a 4-byte AS number is present, but it cannot be represented fully due to the limitation of the receiving routers.
So, in your first scenario, R1 and R3 would see the actual 4-byte AS number in the AS Path field when receiving routes from R2. The AS_TRANS value is used internally in BGP to indicate the presence of a 4-byte AS number.
If you add a fourth router that supports 4-Byte ASNs, it would also see the actual 4-byte AS number in the AS Path field when receiving routes from R2.
https://datatracker.ietf.org/doc/html/rfc6793:
This document reserves a two-octet AS number called "AS_TRANS". AS_TRANS can be used to represent non-mappable four-octet AS numbers as two-octet AS numbers in AS path information that is encoded with two-octet AS numbers. (In this context, four-octet AS numbers that are not mapped from two-octet AS numbers are referred to as "non-mappable".) We denote this special AS number as AS_TRANS for ease of description in the rest of this specification. This AS number is also placed in the "My Autonomous System" field of the OPEN message originated by a NEW BGP speaker, if and only if the speaker does not have a (globally unique) two-octet AS number.
Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.