The document discusses protocol layers and addressing in computer networks. It introduces the OSI model, which defines 7 layers of network communication. It also describes the TCP/IP protocol suite, which has similar but not identical layers to the OSI model. The document provides examples of how different address types, such as physical, logical, port, and application-specific addresses, are used at each layer for effective end-to-end communication across networks.
Here is the presentation for Network Layer Numericals from the book Andrew S. Tanenbaum (Computer Networks) and B A Forouzan ( Data Communication and Networking)
Here is the presentation for Network Layer Numericals from the book Andrew S. Tanenbaum (Computer Networks) and B A Forouzan ( Data Communication and Networking)
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!SOFTTECHHUB
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
UiPath Test Automation using UiPath Test Suite series, part 5DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
GridMate - End to end testing is a critical piece to ensure quality and avoid...ThomasParaiso2
End to end testing is a critical piece to ensure quality and avoid regressions. In this session, we share our journey building an E2E testing pipeline for GridMate components (LWC and Aura) using Cypress, JSForce, FakerJS…
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
2. OBJECTIVES:
To discuss the idea of multiple layering in data communication
and networking and the interrelationship between layers.
To discuss the OSI model and its layer architecture and to show
the interface between the layers.
To briefly discuss the functions of each layer in the OSI model.
To introduce the TCP/IP protocol suite and compare its layers
with the ones in the OSI model.
To show the functionality of each layer in the TCP/IP protocol
with some examples.
To discuss the addressing mechanism used in some layers of the
TCP/IP protocol suite for the delivery of a message from the
source to the destination.
TCP/IP Protocol Suite 2
3. Chapter 2.1 Protocol Layers
Outline
2.2 The OS M
I odel
2.3 TCP IPP
/ rotocol Suite
2.4 Addressing
TCP/IP Protocol Suite 3
4. 2-1 PROTOCOL LAYERS
In Chapter 1, we discussed that a protocol is
required when two entities need to
communicate. When communication is not
simple, we may divide the complex task of
communication into several layers. In this
case, we may need several protocols, one
for each layer.
Let us use a scenario in communication in
which the role of protocol layering may be
better understood. We use two examples. In
the first example, communication is so
TCP/IP Protocol Suite can occur in only one layer.
simple that it 4
6. Example 2.1
Assume Maria and Ann are neighbors with a lot of
common ideas. However, Maria speaks only Spanish,
and Ann speaks only English. Since both have
learned the sign language in their childhood, they
enjoy meeting in a cafe a couple of days per week
and exchange their ideas using signs. Occasionally,
they also use a bilingual dictionary. Communication is
face to face and Happens in one layer as shown in
Figure 2.1.
TCP/IP Protocol Suite 6
8. Example 2.2
Now assume that Ann has to move to another town
because of her job. Before she moves, the two meet
for the last time in the same cafe. Although both are
sad, Maria surprises Ann when she opens a packet
that contains two small machines. The first machine
can scan and transform a letter in English to a secret
code or vice versa. The other machine can scan and
translate a letter in Spanish to the same secret code
or vice versa. Ann takes the first machine; Maria
keeps the second one. The two friends can still
communicate using the secret code, as shown in
Figure 2.2.
TCP/IP Protocol Suite 8
10. 2-2 THE OSI MODEL
Established in 1947, the International
Standards Organization (ISO) is a
multinational body dedicated to worldwide
agreement on international standards.
Almost three-fourths of countries in the
world are represented in the ISO. An ISO
standard that covers all aspects of network
communications is the Open Systems
Interconnection (OSI) model. It was first
introduced in the late 1970s.
TCP/IP Protocol Suite 10
11. Topics Discussed in the Section
Layered Architecture
Layer-to-layer Communication
Encapsulation
Layers in the OSI Model
Summary of OSI Layers
TCP/IP Protocol Suite 11
12. Note
ISO is the organization;
OSI is the model.
TCP/IP Protocol Suite 12
13. Figure 2.3 The OSI model
TCP/IP Protocol Suite 13
14. Figure 2.4 OSI layers
TCP/IP Protocol Suite 14
15. Figure 2.5 An exchange using the OSI model
TCP/IP Protocol Suite 15
16. Note
The physical layer is responsible for
moving individual bits from one
(node) to the next.
TCP/IP Protocol Suite 16
17. Figure 2.6 Summary of OSI Layers
TCP/IP Protocol Suite 17
18. 2-3 TCP/IP PROTOCOL SUITE
The TCP/IP protocol suite was developed
prior to the OSI model. Therefore, the layers
in the TCP/IP protocol suite do not match
exactly with those in the OSI model. The
original TCP/IP protocol suite was defined
as four software layers built upon the
hardware. Today, however, TCP/IP is
thought of as a five-layer model with the
layers named similarly to the ones in the
OSI model. Figure 2.7 shows both
configurations.
TCP/IP Protocol Suite 18
19. Topics Discussed in the Section
Comparison between OSI and TCP/IP
Layers in the TCP/IP Suite
TCP/IP Protocol Suite 19
20. Figure 2.7 Layers in the TCP/IP Protocol Suite
TCP/IP Protocol Suite 20
21. Figure 2.8 TCP/IP and OSI model
TCP/IP Protocol Suite 21
22. Figure 2.9 A private internet
TCP/IP Protocol Suite 22
23. Figure 2.10 Communication at the physical layer
Legend Source Destination
A R1 R3 R4 B
Physical Physical
layer layer
Link 1 Link 3 Link 5 Link 6
011 ... 101
01
1.
..
10
1
011 ... 101 011 ... 101
TCP/IP Protocol Suite 23
24. Note
The unit of communication at the
physical layer is a bit.
TCP/IP Protocol Suite 24
25. Figure 2.11 Communication at the data link layer
Legend Source Destination D Data H Header
A R1 R3 R4 B
Data link Data link
Physical Physical
Link 1 Link 3 Link 5 Link 6
D2 H2
Frame
D2 ame
Fr
H2
D2 H2 D2 H2
Frame Frame
TCP/IP Protocol Suite 25
26. Note
The unit of communication at the data
link layer is a frame.
TCP/IP Protocol Suite 26
27. Figure 2.12 Communication at the network layer
Legend Source Destination D Data H Header
A R1 R3 R4 B
Network Network
Data link Data link
Physical Physical
D3 H3
Datagram
D3 H3
Datagram
TCP/IP Protocol Suite 27
28. Note
The unit of communication at the
network layer is a datagram.
TCP/IP Protocol Suite 28
29. Figure 2.13 Communication at transport layer
A Legend Source Destination D Data H Header B
Transport Transport
R1 R3 R4
Network Network
Data link Data link
Physical Physical
D4 H4
Segment
D4 H4
Segment
TCP/IP Protocol Suite 29
30. Note
The unit of communication at the
transport layer is a segment, user
datagram, or a packet, depending on the
specific protocol used in this layer.
TCP/IP Protocol Suite 30
31. Figure 2.14 Communication at application layer
A B
Application Legend Source Destination D Data H Header Application
Transport Transport
R1 R3 R4
Network Network
Data link Data link
Physical Physical
D5 D5
Message
D5 D5
TCP/IP Protocol Suite 31 Message
32. Note
The unit of communication at the
application layer is a message.
TCP/IP Protocol Suite 32
33. 2-4 ADDRESSING
Four levels of addresses are used in an
internet employing the TCP/IP protocols:
physical address, logical address, port
address, and application-specific address.
Each address is related to a one layer in the
TCP/IP architecture, as shown in Figure
2.15.
TCP/IP Protocol Suite 33
34. Topics Discussed in the Section
Physical Addresses
Logical Addresses
Port Addresses
Application-Specific Addresses
TCP/IP Protocol Suite 34
35. Figure 2.15 Addresses in the TCP/IP protocol suite
TCP/IP Protocol Suite 35
36. Example 2.3
In Figure 2.16 a node with physical address 10 sends a
frame to a node with physical address 87. The two nodes
are connected by a link (a LAN). At the data link layer, this
frame contains physical (link) addresses in the header.
These are the only addresses needed. The rest of the
header contains other information needed at this level. As
the figure shows, the computer with physical address 10 is
the sender, and the computer with physical address 87 is
the receiver. The data link layer at the sender receives
data from an upper layer. It encapsulates the data in a
frame. The frame is propagated through the LAN. Each
station with a physical address other than 87 drops the
frame because the destination address in the frame does
not match its own physical address. The intended
destination computer, however, finds a match between the
destination address in the frame and its own physical
address.
TCP/IP Protocol Suite 36
37. Figure 2.16 Example 2.3: physical addresses
packet packet
discarded discarded
1 packet 87 10
87 10 Data accepted
Data
2 3
4
TCP/IP Protocol Suite 37
38. Example 2.4
As we will see in Chapter 3, most local area networks
use a 48-bit (6-byte) physical address written as 12
hexadecimal digits; every byte (2 hexadecimal digits)
is separated by a colon, as shown below:
07:01:02:01:2C:4B
A 6-byte (12 hexadecimal digits) physical address
TCP/IP Protocol Suite 38
39. Example 2.5
Figure 2.17 shows a part of an internet with two routers
connecting three LANs. Each device (computer or router)
has a pair of addresses (logical and physical) for each
connection. In this case, each computer is connected to
only one link and therefore has only one pair of addresses.
Each router, however, is connected to three networks. So
each router has three pairs of addresses, one for each
connection. Although it may be obvious that each router
must have a separate physical address for each
connection, it may not be obvious why it needs a logical
address for each connection. We discuss these issues in
Chapters 11 and 12 when we discuss routing. The
computer with logical address A and physical address 10
needs to send a packet to the computer with logical
address P and physical address 95. We use letters to show
the logical addresses and numbers for physical addresses,
but note that both are actually numbers, as we will see in
TCP/IP Protocol Suite
later chapters. 39
40. Figure 2.17 Example 2.5: logical addresses
20 10 A P Data 20 10 A P Data 33 99 A P Data
Physical
addresses
changed
95 66 A P Data 95 66 A P Data
33 99 A P Data
Physical
addresses
changed
TCP/IP Protocol Suite 40
41. Note
The physical addresses will change
from hop to hop, but the logical
addresses remain the same.
TCP/IP Protocol Suite 41
42. Example 2.6
Figure 2.18 shows two computers communicating via
the Internet. The sending computer is running three
processes at this time with port addresses a, b, and
c. The receiving computer is running two processes at
this time with port addresses j and k. Process a in the
sending computer needs to communicate with process
j in the receiving computer. Note that although both
computers are using the same application, FTP, for
example, the port addresses are different because
one is a client program and the other is a server
program, as we will see in Chapter 17.
TCP/IP Protocol Suite 42
43. Figure 2.18 Example 2.6: port numbers
A Sender Receiver P
Data Data
a j Data a j Data
A P a j Data A P a j Data
H2 A P a j Data H2 A P a j Data
Internet
TCP/IP Protocol Suite 43
44. Note
The physical addresses change from
hop to hop, but the logical and port
addresses usually remain the same.
TCP/IP Protocol Suite 44
45. Example 2.7
As we will see in future chapters, a port address is a
16-bit address represented by one decimal number as
shown.
753
A 16-bit port address represented as one single
number
TCP/IP Protocol Suite 45