Self-Reflection 2: Network
Fundamentals & Protocol Architectures
Part A – Network Fundamentals
1. Fundamental elements of a communication protocol
• Three critical components:
- Syntax → The layout and framing of information (e.g., how bits are structured into
frames or packages).
- Semantics → The interpretation of every portion of bits (based on headers, control &
error codes, etc.).
- Timing → Refers to how events are synchronized, such as when data is generated and
the rate at which it’s transmitted.
• Example (Web Browser & Server – HTTP): In HTTP communications, the structure of
the request and response determines the syntax, the status codes (e.g., 200 OK, 404 Not
Found) determine the semantics, and the browser waiting for the server to respond
illustrates the timing.
• Protocol failure: If one side uses HTTP, and the other is expecting FTP, they will not be
capable of interpreting one another’s syntax and semantics, creating a failure to
communicate..
2. Protocol architecture and encapsulation
• In the OSI model encapsulation: data is moving down layers, which adds headers (and,
sometimes, trailers).
- Application --> Data
- Transport --> Segment
- Network --> Packet
- Data Link --> Frame
- Physical --> Bits
• Protocol Data Units (PDU)
- Transport --> segment (ports, sequence, checksum)
- Network --> packet (IP addresses, TTL)
- Data Link --> frame (MAC addresses, error check)•
“It’s easy to troubleshoot, works in separate modules, and can connect with other systems
without issues.”
3. Networking switching technologies
• Circuit switching: Establishes a dedicated end-to-end path imbued with a single
capacity for tandem communication (e.g. a telephone call).
• Packet switching is a method of breaking data down into distinct packets that are sent
separately over a common network before being reassembled at their target destination
(like the Internet).
• Advantages: Better use of bandwidth, handles sudden spikes in traffic very well, allows
the retransmission of packets when a packet gets lost, while minimizing expenses as
much as possible.
• Today’s systems: Frame Relay had lower overhead once communication networks were
deemed reliable demonstrating a shift from redundancy to efficiency.
Part B – Protocol Architectures & Standards
1. OSI versus TCP/IP Models
• Basically, it is a theoretical model with seven layers.
• The TCP-IP Model with its four layers is often used and practical in contrast to the OSI
model.
• Adoption: Because ARPANET found usefulness and application, TCP/IP got accepted
in the industry.
• Layer Mapping (OSI → TCP/IP): Application, Presentation, Session → Application
Transport → Transport Network → Internet Data Link + Physical → Network Access
• Key Point: TCP/IP is considered more practical since it is directly supporting present-
day use of the Internet.
2. Addressing at various levels
Looking for a device in a network, remember: the Network Level (IP).
• Process level (Port): locates the application.
• Which both address schemes must direct (route) the data to the correct service.
• Connection identifiers: short identifiers achieve overhead savings by accelerating the
lookup of an identifier once established.
• Addressing modes:
- unicast: one-to-one (for example, loading a web page)
- broadcast: one-to-all (for example, ARP request)
- multicast: one-to-many (for example, streaming).
3. Standardized Protocols & Scalability
• Without standards: The number of implementations grows fast. “For instance, with 5 of
K and 10 of L, you’d end up with 100 possible ways to implement it.”
• With standards: The number of implementations is much smaller. “For example, 5 + 10
gives 15 possible implementations.”
• Other benefits of using standards include easier system compatibility, lower costs, and
simpler scaling and maintenance.”
Self-Reflection
Doing this task has provided me with a better appreciation of how protocols and layered
architectures form the backbone of trustworthy communication. The syntax, semantics,
and timing concept reminded me that the idea of two devices needing to "speak the same
language" if communication is to be successful. It was also intriguing to observe how the
encapsulation is now better described by means of each layer of OSI model and how each
layer is inserting a header to form PDUs and how the encapsulation merely provides easy
troubleshooting and modularity in design.
When comparing packet switching and circuit switching, I understand the logic behind
why packet switching is used on the internet to build efficient and scalable
communication. The same applies to TCP/IP and OSI, I know that OSI was very helpful
to learn the subject, but impractical for actual usage.
Lastly, the addressing schemes and some of the standard protocols made interoperability
essential. Without standards, it would have been a mess and pointless. I now have a much
better appreciation for how the theoretical concepts can be of actual value in the internet
that we utilize in real life.