Hi Don,

Site A will see the IX ASN in routes received from the IX announced by B

Site B will not see the IX ASN in the routes received from the IX announced by A

There���s one knob for the implementations I���ve looked at

- per client session

-  off or on

On 7/09/16, 12:48, "nznog-bounces@list.waikato.ac.nz on behalf of Don Stokes" <nznog-bounces@list.waikato.ac.nz on behalf of don@daedalus.co.nz> wrote:

Hi Tim, Sid,

So can we clarify ... if Site A is "opt out" (i.e. old and busted behaviour, IX ASN inserted) and site B is "opt in" (new hotness behaviour, IX ASN not inserted):

• Would Site A see the IX ASN inserted in routes announced to the route servers by Site B?
• Would Site B see the IX ASN inserted in routes announced to the route servers by Site A?

That is, is the ASN inserted into a route's AS path based on where the route comes from, or where it's announced to? Is there more than one setting?

-- don