# 1.6 Layering Principle

### Layering 

![](/files/-MgXG8vPVXlDtHKpgwoj)

* E.x. flights: google flights --> airlines (abstract the details of each airlines) 
* E.x. postal service 
  * Mail 
  * Postal service 
  * Medias 
  * Mailman 
* Can improve each layer independently over time (the interface is the same)
* E.x. computer system 
  * Breakdown into functional components, each with well-defined roles 
  * Clear separations of concerns 
  * Each can be improved, updated over time 

![E.x. computer system ](/files/-MgXH4hzOQTm-UKaO60k)

* Break the layers boundary only if needed 

### Reasons for layering 

![](/files/-MgXIHbF26usHlWYDukn)

* p2p: specific to layered communication systems 
  * 4-layer: each layer communicate with its peer on the another system, using the delivery service provided by the layers below 


---

# 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://sliu583.gitbook.io/blog/networking/index/computer-networking-a-top-down-approach/stanford-cs144/chapter-1/1.6-layering-principle.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.