> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/n/network-protocol.md). # Network Protocol A set of rules that define how data is transmitted over a network. A network protocol is a set of rules and conventions that govern how data is formatted, transmitted, and received across a computer network. Protocols define the syntax, semantics, and synchronization of communication, ensuring that different devices and software can exchange information reliably. Network protocols operate at different layers of the OSI model. Low-level protocols like TCP and UDP handle reliable data transport, while higher-level protocols like HTTP, HTTPS, WebSocket, and gRPC define application-level communication. DNS resolves domain names to IP addresses, and TLS provides encryption for secure communication. In API development, HTTP and HTTPS are the most commonly used protocols. API gateways primarily operate at the application layer (Layer 7), inspecting HTTP headers, paths, and bodies to make routing and policy decisions. Some gateways also support WebSocket connections for real-time communication and gRPC for high-performance service-to-service communication. Understanding the underlying protocols is essential for diagnosing connectivity issues and optimizing API performance. --- # 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://docs.serverlessapigateway.com/glossary/n/network-protocol.md?ask=&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.