Consistent routing policy?

• Subject: Consistent routing policy?
• From: mark.tinka at seacom.mu (Mark Tinka)
• Date: Tue, 17 Sep 2019 13:41:57 +0200
• In-reply-to: <CA[email protected]>
• References: <CA[email protected]> <[email protected]> <CA+GrwCOpEs[email protected]> <[email protected]> <CA[email protected]>

On 16/Sep/19 20:26, Töma Gavrichenkov wrote:

>
>
> Not always.

No, longest match ALWAYS wins.


>
> E.g. imagine an ISP who has two connections to the outside world: one
> through a major ISP and the other through an IX.
>
> Such an ISP would be quite inclined both financially and technically
> to import routes just from the IX and set the default to the upstream
> ISP link.  Therefore, an advertisement from the IX would always win no
> matter the length.

Which is why I included, in my previous message:

    So, for example, if the upstream to whom you are sending the /21 doesn't
    do anything about how they learn the /22 from another source, (for their
    network)...

Mark.

• References:
  • Consistent routing policy?
    • From: benlogan at myriverstreet.net (Ben Logan)
  • Consistent routing policy?
    • From: mark.tinka at seacom.mu (Mark Tinka)
  • Consistent routing policy?
    • From: benlogan at myriverstreet.net (Ben Logan)
  • Consistent routing policy?
    • From: mark.tinka at seacom.mu (Mark Tinka)
  • Consistent routing policy?
    • From: ximaera at gmail.com (Töma Gavrichenkov)

• Prev by Date: diversity in the RIPE Route Collectors
• Next by Date: Consistent routing policy?
• Previous by thread: Consistent routing policy?
• Next by thread: Security alert aggregator?
• Index(es):
  • Date
  • Thread