> For the complete documentation index, see [llms.txt](https://digitalgarden.batamladen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://digitalgarden.batamladen.com/notes/services/routing-protocols/dynamic.md).

# Dynamic

Dynamic routing protocols, as their name suggests, are used to dynamically exchange routing information between routers. Their implementation allows network topologies to dynamically adjust to changing network conditions, and to ensure that efficient and redundant routing continues in spite of any changes.

{% hint style="success" %}
**Definition:**\
Dynamic routing is a mechanism through which routing information is exchanged between routers to determine the optimal path between network devices. A routing protocol is used to identify and announce network paths.
{% endhint %}

Compared to statically configuring routing in topology, the implementation of dynamic routing protocols vastly improves the scalability of networks.

The first dynamic routing protocol was the [Exterior Gateway Protocol (EGP)](/notes/services/routing-protocols/dynamic/egp.md)

***

## Dynamic protocols categories:

* [Interior Gateway Protocol (IGP)](/notes/services/routing-protocols/dynamic/igp.md)
* [Exterior Gateway Protocol (EGP)](/notes/services/routing-protocols/dynamic/egp.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://digitalgarden.batamladen.com/notes/services/routing-protocols/dynamic.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.