TCP/IP and IPv4/IPv6 Protocol Overhead Calculation
VerifiedAdded on 2025/05/03
|9
|2470
|493
AI Summary
Desklib provides solved assignments and past papers to help students succeed.

ASSESSMENT 4 - ASSIGNMENT 2
NETWORK PROTOCOLS, SDLC & ITSM
NETWORK PROTOCOLS, SDLC & ITSM
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

A station running TCP/IP needs to transfer a file to a host. The file contains 1024 bytes. How many
bytes, including all of the TCP/IP overhead, would be sent, assuming a payload size of 128 bytes
and both systems are running IPv4? (Also assume that the three-way handshake and window size
negotiation have been completed and that no errors occur during transmission.)
What is the protocol overhead (stated as a percentage)?
Transfer of the files to a host is done by using the IPv4 protocol. The file which is given is of 1024 bytes.
And payload size is given to be 128 bytes. TCP header is being composed for the file which is of 20
bytes. IPv4 header uses 24 bytes. 40 bytes is the total bytes used for the TCP/IP protocol. It was seen that
1024 bytes were divided into 8 segments. Therefore, each segment uses 128 bytes;
(128+40)*8= 1344 bytes
TCP/IP is used to transmit the file, and the total bytes used is 1344 bytes
Data sent= 1344 bytes
The given file size= 1024 bytes
Hence,
1344*100/1024= 131.25%
The protocol overhead (in %) =131.25-100
= 31.25%
Perform the same calculation, this time assuming that both clients are using IPv6.
The size of the files is 1024 bytes which are being transmitted, and payload size is 128 bytes. 60(20+40)
bytes are used for composing TCP header is. 20 bytes is used for IPv4 header, and a total of 40 bytes for
the TCP/IP header are divided. 1024 bytes are divided into 8 segments making 128 bytes for each
segment, therefore,
8 * (60+128) = 1504 bytes
TCP/IP overhead is included of total 1504 bytes to transmit the file.
Therefore, the given file size= 1024 bytes
Data sent= 1504 bytes
Hence,
1504*100/1024= 146.87%
The protocol overhead (in %) =146.87-100
= 46.87%
bytes, including all of the TCP/IP overhead, would be sent, assuming a payload size of 128 bytes
and both systems are running IPv4? (Also assume that the three-way handshake and window size
negotiation have been completed and that no errors occur during transmission.)
What is the protocol overhead (stated as a percentage)?
Transfer of the files to a host is done by using the IPv4 protocol. The file which is given is of 1024 bytes.
And payload size is given to be 128 bytes. TCP header is being composed for the file which is of 20
bytes. IPv4 header uses 24 bytes. 40 bytes is the total bytes used for the TCP/IP protocol. It was seen that
1024 bytes were divided into 8 segments. Therefore, each segment uses 128 bytes;
(128+40)*8= 1344 bytes
TCP/IP is used to transmit the file, and the total bytes used is 1344 bytes
Data sent= 1344 bytes
The given file size= 1024 bytes
Hence,
1344*100/1024= 131.25%
The protocol overhead (in %) =131.25-100
= 31.25%
Perform the same calculation, this time assuming that both clients are using IPv6.
The size of the files is 1024 bytes which are being transmitted, and payload size is 128 bytes. 60(20+40)
bytes are used for composing TCP header is. 20 bytes is used for IPv4 header, and a total of 40 bytes for
the TCP/IP header are divided. 1024 bytes are divided into 8 segments making 128 bytes for each
segment, therefore,
8 * (60+128) = 1504 bytes
TCP/IP overhead is included of total 1504 bytes to transmit the file.
Therefore, the given file size= 1024 bytes
Data sent= 1504 bytes
Hence,
1504*100/1024= 146.87%
The protocol overhead (in %) =146.87-100
= 46.87%

IP is a connection-less protocol, whereas TCP is connection-oriented. How can these two protocols
coexist in the same protocol stack?
The TCP /IP protocol co-exist in the same protocol stack by forming a different level of layers, through
which the data is transmitted. These layers are discussed below:
The Network Layer
The network layer of the OSI version characterises conventions that assure that the data touches base on
the proper aim. This is probably the most often tested layer of the OSI model.
Device Layer standards
The accompanying ideas are the most sizable community layer thoughts: practical device tending to steer
realistic network Addressing maximum systems impart utilising conventions that should have their very
own tending to conspire. As an instance, a TCP/IP address isn't equal to an IPX cope with. Moreover, the
two conventions can coincide on a comparable interface without strife, every all the while limiting itself
to the convention self-sustaining MAC deal with for the associated interface anyhow, specific interfaces
utilizing a similar convention can't have the equivalent coherent gadget address on a similar machine.
The shipping Layer
The shipping layer characterises the conventions for organizing messages and tests the legitimacy of
transmissions. In any case, if those things are to be provided, the transport layer is for the maximum
component wherein you need to search for such help.
Delivery Layer principles
The shipping layer is reminiscent of the old saying that internet Tech educators used to pound into their
understudies' heads: "stable begin to finish mistake and flow management." The delivery layer does
various things too; however, the conventions that paintings on the transport layer guarantee reliable
correspondences between top accomplice layers. Truth is informed, UDP, as you will see, is a stripped-
down convention that has one employment, to interface the upper layers with the network layer. It would
not fear approximately things like unwavering excellent, association foundation, and circulation manages.
coexist in the same protocol stack?
The TCP /IP protocol co-exist in the same protocol stack by forming a different level of layers, through
which the data is transmitted. These layers are discussed below:
The Network Layer
The network layer of the OSI version characterises conventions that assure that the data touches base on
the proper aim. This is probably the most often tested layer of the OSI model.
Device Layer standards
The accompanying ideas are the most sizable community layer thoughts: practical device tending to steer
realistic network Addressing maximum systems impart utilising conventions that should have their very
own tending to conspire. As an instance, a TCP/IP address isn't equal to an IPX cope with. Moreover, the
two conventions can coincide on a comparable interface without strife, every all the while limiting itself
to the convention self-sustaining MAC deal with for the associated interface anyhow, specific interfaces
utilizing a similar convention can't have the equivalent coherent gadget address on a similar machine.
The shipping Layer
The shipping layer characterises the conventions for organizing messages and tests the legitimacy of
transmissions. In any case, if those things are to be provided, the transport layer is for the maximum
component wherein you need to search for such help.
Delivery Layer principles
The shipping layer is reminiscent of the old saying that internet Tech educators used to pound into their
understudies' heads: "stable begin to finish mistake and flow management." The delivery layer does
various things too; however, the conventions that paintings on the transport layer guarantee reliable
correspondences between top accomplice layers. Truth is informed, UDP, as you will see, is a stripped-
down convention that has one employment, to interface the upper layers with the network layer. It would
not fear approximately things like unwavering excellent, association foundation, and circulation manages.
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

Mention one advantage and one disadvantage of the Agile method.
Agile method is used to deliver a project on a specified time to the customer. This helps with the proper
planning for executing a project so that the end time taken by the employees will be shortened. This will
help the employee as well as the end user by delivering the best product and also early. In networking,
sometimes agile method can be seen as a negative method to follow. Negative for those who don’t know
how to implement this method for their ongoing processes.
Advantage of this method is:
End-user satisfaction by continuous, rapid delivery of the useful product
The main of any organisation is to deliver a product fast and according to their customer needs and
demands. The agile method helps with this by focusing on the work of every people in completing the
project. This will help in reducing the workload of the employee as well as the integrity of the
organisation, will be maintained. Continuous delivery of the projects will be seen if the agile method is
used. The agile method also ensures that the value of the project is maintained throughout the project, and
no quality hamper in delivering the project is done.
The project can be seen going off-rail if the client is not clear of the outcome needed
With the advantages, there comes a disadvantage, too, which can take the project out of the lane in a
couple of seconds. This depends majorly on the customer and the communication done between the client
and the organisation. If a client is not clear in his mind that it can cause difficulty for the organisation to
deliver the desired outcome wanted by the client. This will consume a lot of time. Also, it will not be
clear how and what to achieve or when to deliver a certain thing. This will make the entire process slow.
Agile method is used to deliver a project on a specified time to the customer. This helps with the proper
planning for executing a project so that the end time taken by the employees will be shortened. This will
help the employee as well as the end user by delivering the best product and also early. In networking,
sometimes agile method can be seen as a negative method to follow. Negative for those who don’t know
how to implement this method for their ongoing processes.
Advantage of this method is:
End-user satisfaction by continuous, rapid delivery of the useful product
The main of any organisation is to deliver a product fast and according to their customer needs and
demands. The agile method helps with this by focusing on the work of every people in completing the
project. This will help in reducing the workload of the employee as well as the integrity of the
organisation, will be maintained. Continuous delivery of the projects will be seen if the agile method is
used. The agile method also ensures that the value of the project is maintained throughout the project, and
no quality hamper in delivering the project is done.
The project can be seen going off-rail if the client is not clear of the outcome needed
With the advantages, there comes a disadvantage, too, which can take the project out of the lane in a
couple of seconds. This depends majorly on the customer and the communication done between the client
and the organisation. If a client is not clear in his mind that it can cause difficulty for the organisation to
deliver the desired outcome wanted by the client. This will consume a lot of time. Also, it will not be
clear how and what to achieve or when to deliver a certain thing. This will make the entire process slow.
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Compare and contrast the Agile method and Evolutionary software development process. Explain
with an example.
Agile method is seen as a very effective method for the development of software or rather delivering of a
project. Agile method is composed of iteration or sprint in which the whole project is divided into a group
or one can say that it is divided. This is done, to proceed with the project fast and deliver the working
software early and in given time only. Example of this can be seen as, for delivering a project by a
company, say Microsoft, the project is followed by many parts. First, the requirement is collected for the
project or the iteration, then analysis, design, and coding for the project is done. This is all done for a
specific time to deliver working software after some time. As the end approaches, test and learning are
done according to it.
On the other hand, the evolutionary development process is more a rigid process, which sticks to a
technique, despite gaining any profit from it. In this, the project is started from raw data, rather than
specific data and thinking of a specific outcome. The software is updated upon the previous version of the
project version. Evolutionary development as the name suggests updates from the feedback of the client
and then it is implemented. Agile is a type of evolutionary development process, but the evolutionary
process is not an agile method. The evolutionary process helps with updating of the project side by side.
This is very much needed for the development of the project. Example of this can be seen as at first, the
design of the version is done; the code is developed, then the testing of the version is done, which is
followed by the gaining of feedback from the client. In the end, the feedback is implemented, and again,
the cycle of the process is done.
with an example.
Agile method is seen as a very effective method for the development of software or rather delivering of a
project. Agile method is composed of iteration or sprint in which the whole project is divided into a group
or one can say that it is divided. This is done, to proceed with the project fast and deliver the working
software early and in given time only. Example of this can be seen as, for delivering a project by a
company, say Microsoft, the project is followed by many parts. First, the requirement is collected for the
project or the iteration, then analysis, design, and coding for the project is done. This is all done for a
specific time to deliver working software after some time. As the end approaches, test and learning are
done according to it.
On the other hand, the evolutionary development process is more a rigid process, which sticks to a
technique, despite gaining any profit from it. In this, the project is started from raw data, rather than
specific data and thinking of a specific outcome. The software is updated upon the previous version of the
project version. Evolutionary development as the name suggests updates from the feedback of the client
and then it is implemented. Agile is a type of evolutionary development process, but the evolutionary
process is not an agile method. The evolutionary process helps with updating of the project side by side.
This is very much needed for the development of the project. Example of this can be seen as at first, the
design of the version is done; the code is developed, then the testing of the version is done, which is
followed by the gaining of feedback from the client. In the end, the feedback is implemented, and again,
the cycle of the process is done.

Analyse the uniqueness of Apple design process.
Apple is the top company in the world of software design. Apple design process is expensive, complex
and demanding. But despite all this, it still has more impact in the business industry than the other design
processes. The uniqueness of this process is the steps that are taken by the company to develop a product.
Apple design firstly focuses on what the design is by dividing a group of people, specifically for this
purpose. Designing is done, and before implementing it, a meeting is done. In the meeting, the design is
discussed, any limitation for the design is seen, and what are the possible solutions for it is seen. All this
helps with the planning and executing of the process. If there is no solution achieved, then the design
team will not move forward to any other plan or design but focuses on finding the best solution for the
problem only.
Further, the engineering program manager helps with the production when the design is completed. Their
work starts before the design is even being implemented. The work of EPM carries on until the product is
out in the market. Also, the design team does not stop after the work has been implemented or the product
is made. But in turn, it is seen that if the product is not good, then the whole designing and implementing
process id done again. This is done until the product is not achieved according to the designer's need.
Iteration is the main feature of this design process. The building of the design, testing and reviewing it
continuously helps with the work. This is a costly approach, but it helps in delivering the best product.
Afterwards, the product release and price is discussed and bring in the market. Being an expensive and
complex process, it is still the best processes than many other processes.
Apple is the top company in the world of software design. Apple design process is expensive, complex
and demanding. But despite all this, it still has more impact in the business industry than the other design
processes. The uniqueness of this process is the steps that are taken by the company to develop a product.
Apple design firstly focuses on what the design is by dividing a group of people, specifically for this
purpose. Designing is done, and before implementing it, a meeting is done. In the meeting, the design is
discussed, any limitation for the design is seen, and what are the possible solutions for it is seen. All this
helps with the planning and executing of the process. If there is no solution achieved, then the design
team will not move forward to any other plan or design but focuses on finding the best solution for the
problem only.
Further, the engineering program manager helps with the production when the design is completed. Their
work starts before the design is even being implemented. The work of EPM carries on until the product is
out in the market. Also, the design team does not stop after the work has been implemented or the product
is made. But in turn, it is seen that if the product is not good, then the whole designing and implementing
process id done again. This is done until the product is not achieved according to the designer's need.
Iteration is the main feature of this design process. The building of the design, testing and reviewing it
continuously helps with the work. This is a costly approach, but it helps in delivering the best product.
Afterwards, the product release and price is discussed and bring in the market. Being an expensive and
complex process, it is still the best processes than many other processes.
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

Describe three reasons for project failure.
There can be many reasons for making a project success, but one reason is enough for project failure. All
the aspects should be treated carefully so that nothing can cause project failure. As this will cause a delay
in delivery of the project, also all the resources like time, cost, labour will go to waste. Three reasons for
project failure are discussed below:
1. Project scope is not clearly defined
This is main for making a project bloom. If the project scope is not clearly defined, then it will
create havoc for the entire project. The whole process can go in the wrong direction. This will
make the employees confuse, and they will not know what and how to do the project. Also, the
main question will be what the client want. If all this is not cleared, then the whole project can go
down.
2. Lack of communication at every level
Communication is very much needed at every step of the design process. This is done to make it
clear to the employee and the client as well, that how the process is going to take place. If the
communication lacks at any of the levels, then the entire product can go down. This will affect
the client and employees as well. As, if the wrong information is circulated than the end of the
product or the outcome will be a very different thing from what was desired.
3. Inaccurate effort and time estimates
All type of resources is needed to make a project successful. If the estimate of these resources is
not done accurately, then it will be a huge failure for a process. As the resources will go waste if
the estimate is not done properly. So, the estimate for the time and effort needed for making the
project success should be done accurately.
There can be many reasons for making a project success, but one reason is enough for project failure. All
the aspects should be treated carefully so that nothing can cause project failure. As this will cause a delay
in delivery of the project, also all the resources like time, cost, labour will go to waste. Three reasons for
project failure are discussed below:
1. Project scope is not clearly defined
This is main for making a project bloom. If the project scope is not clearly defined, then it will
create havoc for the entire project. The whole process can go in the wrong direction. This will
make the employees confuse, and they will not know what and how to do the project. Also, the
main question will be what the client want. If all this is not cleared, then the whole project can go
down.
2. Lack of communication at every level
Communication is very much needed at every step of the design process. This is done to make it
clear to the employee and the client as well, that how the process is going to take place. If the
communication lacks at any of the levels, then the entire product can go down. This will affect
the client and employees as well. As, if the wrong information is circulated than the end of the
product or the outcome will be a very different thing from what was desired.
3. Inaccurate effort and time estimates
All type of resources is needed to make a project successful. If the estimate of these resources is
not done accurately, then it will be a huge failure for a process. As the resources will go waste if
the estimate is not done properly. So, the estimate for the time and effort needed for making the
project success should be done accurately.
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Your company owns several software and asked you to manage them within company budget
constraints. What will be your goals?
For running a company, it is very important to choose people accordingly to manage it at a lower level.
Managing the software with the company budget constraints is very important. To manage these, some
goals need to be thought about. These goals should be maintained to manage the company transactions.
Some of the goals which should be set before operating this are:
One should set a goal for remaining in the budget. This is very important so that there is no loss to the
organization. If the budget slightly goes upwards, it will affect the product at any levels, for example, in
it’s selling price, employee's salary. So this should be done with proper care.
The next goal can be set for finding the talent in the employees, which can help in delivering the software
on time. This will also help with the maintenance of budget within the specified time. By recognizing the
hidden talents of the employees, the work will be done more precisely. After this, the next goal can be set
of finishing the project on time. This is related to the person only. As when an individual works with it’s
the best self, then only the project can be finished on time.
Another goal can be set as gaining everything that has been lost while processing any other product. This
is done to help the employees with many things. One of them is to achieve the best of resources, to help
the employees during the ongoing process. Winning back the resources helps in achieving the customer's
trust too, which was lost during the loss of other resources.
All these goals need to be set up before thinking of managing a software company when the budget is
constrained. This will not only help the team but also help the individuals as well. And also helps with the
delivering of good and efficient product.
constraints. What will be your goals?
For running a company, it is very important to choose people accordingly to manage it at a lower level.
Managing the software with the company budget constraints is very important. To manage these, some
goals need to be thought about. These goals should be maintained to manage the company transactions.
Some of the goals which should be set before operating this are:
One should set a goal for remaining in the budget. This is very important so that there is no loss to the
organization. If the budget slightly goes upwards, it will affect the product at any levels, for example, in
it’s selling price, employee's salary. So this should be done with proper care.
The next goal can be set for finding the talent in the employees, which can help in delivering the software
on time. This will also help with the maintenance of budget within the specified time. By recognizing the
hidden talents of the employees, the work will be done more precisely. After this, the next goal can be set
of finishing the project on time. This is related to the person only. As when an individual works with it’s
the best self, then only the project can be finished on time.
Another goal can be set as gaining everything that has been lost while processing any other product. This
is done to help the employees with many things. One of them is to achieve the best of resources, to help
the employees during the ongoing process. Winning back the resources helps in achieving the customer's
trust too, which was lost during the loss of other resources.
All these goals need to be set up before thinking of managing a software company when the budget is
constrained. This will not only help the team but also help the individuals as well. And also helps with the
delivering of good and efficient product.

References
Bouabdellah, M., Kaabouch, N., El Bouanani, F., & Ben-Azza, H. (2018). Network layer attacks and
countermeasures in cognitive radio networks: A survey. Journal of information security and
applications, 38, 40-49.
Davidson, S., Xie, S., Torng, C., Al-Hawai, K., Rovinski, A., Ajayi, T., ... & Amarnath, A. (2018). The
Celerity open-source 511-core RISC-V tiered accelerator fabric: Fast architectures and design
methodologies for fast chips. IEEE Micro, 38(2), 30-41.
Firestone, D., Putnam, A., Mundkur, S., Chiou, D., Dabagh, A., Andrewartha, M., ... & Chandrappa, H.
K. (2018). Azure accelerated networking: SmartNICs in the public cloud. In 15th {USENIX} Symposium
on Networked Systems Design and Implementation ({NSDI} 18) (pp. 51-66).
Jafari, M., Alsadoon, A., Withana, C., Ali, S., & Elchouemic, A. (2018, January). Segment based model
for TCP protocol optimization: Enhancing the bandwidth and congestion. In 2018 IEEE 8th Annual
Computing and Communication Workshop and Conference (CCWC) (pp. 918-924). IEEE.
Krishnan, P., & Achuthan, K. (2018, September). Managing Network Functions in Stateful Application
Aware SDN. In International Symposium on Security in Computing and Communication (pp. 88-103).
Springer, Singapore.
Mattos, D. M. F., Velloso, P. B., & Duarte, O. C. M. B. (2019). An agile and effective network function
virtualization infrastructure for the Internet of Things. Journal of Internet Services and
Applications, 10(1), 6.
Zhang, Q. Y., Wang, X. W., Huang, M., Li, K. Q., & Das, S. K. (2018). Software defined networking
meets information centric networking: A survey. IEEE Access, 6, 39547-39563.
Bouabdellah, M., Kaabouch, N., El Bouanani, F., & Ben-Azza, H. (2018). Network layer attacks and
countermeasures in cognitive radio networks: A survey. Journal of information security and
applications, 38, 40-49.
Davidson, S., Xie, S., Torng, C., Al-Hawai, K., Rovinski, A., Ajayi, T., ... & Amarnath, A. (2018). The
Celerity open-source 511-core RISC-V tiered accelerator fabric: Fast architectures and design
methodologies for fast chips. IEEE Micro, 38(2), 30-41.
Firestone, D., Putnam, A., Mundkur, S., Chiou, D., Dabagh, A., Andrewartha, M., ... & Chandrappa, H.
K. (2018). Azure accelerated networking: SmartNICs in the public cloud. In 15th {USENIX} Symposium
on Networked Systems Design and Implementation ({NSDI} 18) (pp. 51-66).
Jafari, M., Alsadoon, A., Withana, C., Ali, S., & Elchouemic, A. (2018, January). Segment based model
for TCP protocol optimization: Enhancing the bandwidth and congestion. In 2018 IEEE 8th Annual
Computing and Communication Workshop and Conference (CCWC) (pp. 918-924). IEEE.
Krishnan, P., & Achuthan, K. (2018, September). Managing Network Functions in Stateful Application
Aware SDN. In International Symposium on Security in Computing and Communication (pp. 88-103).
Springer, Singapore.
Mattos, D. M. F., Velloso, P. B., & Duarte, O. C. M. B. (2019). An agile and effective network function
virtualization infrastructure for the Internet of Things. Journal of Internet Services and
Applications, 10(1), 6.
Zhang, Q. Y., Wang, X. W., Huang, M., Li, K. Q., & Das, S. K. (2018). Software defined networking
meets information centric networking: A survey. IEEE Access, 6, 39547-39563.
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide
1 out of 9
Related Documents

Your All-in-One AI-Powered Toolkit for Academic Success.
+13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
Copyright © 2020–2025 A2Z Services. All Rights Reserved. Developed and managed by ZUCOL.