If you want to advertise prefixes from another network (ASN) to your embedded OCA(s), you should first ensure that you have created an AS-SET in your internet routing registry (IRR) record that includes the ASN(s) that are associated with those prefixes.
What is the benefit of taking this action?
AS-SETs provide a mechanism for publicly documenting the relationship between autonomous systems (AS). By creating an AS-SET with a members attribute that includes each network (ASN) with which you have an established relationship (transit, peering, and so on), you can formally document the networks that are authorized and expected to be served from your OCA(s). As a result, Netflix will receive an unambiguous signal that all prefixes associated with the ASNs in your AS-SET are not leaked routes, but fully authorized and expected. This will prevent us from erroneously flagging potentially leaked routes.
How can I verify that my AS-SET is set up correctly?
To verify that your AS-SET is correctly defined, you can run a query via RADb.
For more information about AS-SETs, see these additional resources: