>> the immediate problem with BGP (ignoring the logistic and legal
>> aspects) would be utilizing both uplinks in an active/active fashion.
>> Or rather, ensuring the return traffic honors the original uplink
>> choice of the request traffic.
>Why is that relevant?
Imagine for example a network admin who wishes to use a "fat pipe" uplink for large file downloads: the intuitive approach to accomplish this would be for him to configure the gateway so that it forwarded e.g. Dropbox traffic over that link. If the return flow came back from the other uplink, perhaps having a much smaller capacity, that would quickly saturate it and render the steering pointless.
The same considerations apply to uplinks with different delay/jitter characteristics, or even privacy (private circuits vs a shared medium like GPON) and the jurisdictions the data flows through. Simply put, it is intuitive for admins to assume that the return traffic will come back from the same link (of course, it is incorrect to assume so). An asymmetric return may also cause issues when the gateway is a stateful device such as a firewall.
Paolo
Am 06.03.2025 um 14:38:13 Uhr schrieb Paolo Nero:
> the immediate problem with BGP (ignoring the logistic and legal
> aspects) would be utilizing both uplinks in an active/active fashion.
> Or rather, ensuring the return traffic honors the original uplink
> choice of the request traffic.
Why is that relevant?
--
Gruß
Marco
Send unsolicited bulk mail to 1741268293muell@cartoonies.org
-----
To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ipv6-wg.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/