# Internet Protocol

Unlike TCP, **IP is an unreliable, connectionless protocol**.

**IP's job is too send and route packets to other computers**.&#x20;

IP packets are independent entities and may arrive out of order or not at all. It is TCP's job to make sure packets arrive and are in the correct order.

![](https://2548495579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTsnKOX7xLvOtvOXY9MlI%2Fuploads%2FKrr9yJpuzoVYqLTa5hAw%2Fimage.png?alt=media\&token=30ab1cd7-b0bf-49a2-8295-dd03cd9b8b3a)

The application layer data is segmented in the TCP layer, the TCP header is added, the packet continues to the IP layer, the IP header is added, and then the packet is transmitted across the Internet.

![](https://2548495579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTsnKOX7xLvOtvOXY9MlI%2Fuploads%2FLCx8e1ZhNoKH5ZPJOspi%2Fimage.png?alt=media\&token=f4dbd726-4a76-40b3-be5f-5d2b39653451)


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://til.notdu.com/back-end/network/the-internet/internet-protocol.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
