| Internet-Draft | Abbreviated Title | February 2026 |
| ZOUNDI | Expires 16 August 2026 | [Page] |
The Border Gateway Protocol (BGP) is a very important protocol in the
Internet to exchange routing information between network domains.
BGP populates the routing table with valid routes, sometimes the routes populated
by BGP are not the best choices specially when a ISP provides IP Transit service
to an other ISP, and the two ISP are peering at an Internet Exchange Point.
¶
Let us assume that ISP A provides IP Transit to ISP B, and the two are peering at an Internet Exchange Point.
The return traffic from Internet to ISP B via ISP A will be routed over the Internet Exchange Point
instead of the IP Transit link between the two ISP, because of BGP Local preference
which has usually a higher value on Internet Exchange links.
This will lead to an issue because the return traffic IP Transit service is now passing over the Internet Exchange link.
¶
An other issue faced in Internet Exchange Point, is the sub-optimal routing caused by the advertisment
of the most specific routes over Internet by ISP.
Let us assume that ISP A wants to advertise most specific routes to Internet for traffic Engineering,
the peers of ISP A at the Internet Exchange Point could also receive the most specific routes over Internet .
This will mean that traffic from the peers of ISP A towards ISP A will now go through Internet because of most specific
routes which is not suppposed to be the case.
¶
To solve that ISP A will have to send the same specific routes over the Internet Exchange Point which will increase
complexity.
This document provides aletrnative solutions that can be used to solve the above problems¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 16 August 2026.¶
Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶