On Thu, Dec 5, 2024 at 2:34 PM Ryan Hamel <[email protected]> wrote: > This same thing also applies to operators of route optimizers. They > are responsible for writing the correct import/export policies for their > network, just like the carriers for writing sane policies for customer > circuits
Hi Ryan, Is there room or use for standards work here? Just spitballing, but something along the lines of: A synthetic BGP route is a BGP route produced by an AS other than the original origin of the IP addresses contained. Examples include default routes, black-hole routes and routes produced by a route optimizer in a middle network. The producer of a synthetic BGP route MUST mark the route with community XXX. Routers MUST NOT remove the synthetic community XXX from a route. Synthetic routes learned from EBGP sessions MUST be rejected by default. Routers MAY accept synthetic routes learned from EBGP sessions if explicitly configured to do so. Regards, Bill Herrin -- William Herrin [email protected] https://bill.herrin.us/
