|
Question : udp error detection
|
|
Hey,
just a few quick question im not too sure in how this works:
UDP isnt connection orientated... correct? UDP offers no Error detection......correct?
Design and Specify an Application Level Single-Shot-Protocol that will provide reliable delivery of individual single component messages over IP networks.
1. i was thinking about firstly a timeout? but as i am a complete begginer how would i calculate an appropriate time to time out! i really have very limited knowledge so please explain everything ie acronyms etc.
2. also the extra protocol that im designing would appear in the Application level? is that correct?
3, also when passing packets how would the end user know that they havent recieved a packet because from wat i can gather UDP doesnt number the packlets like TCP. Would i have to do this in the protocol im designing or is there a way around this.
4. How does the header work in UDP? is there any extra bites that could be used to pass info around to help in error detections
5. or am i completely wrong! if so please help!
6. and one last Q WHAT IS A SINGLE SHOT PROTOCOL?
CAN SUM1 PLEASE TELL ME WHERE TO START WITH THIS AND HOW I SHOULD GO ABOUT THIS!
thank u
|
Answer : udp error detection
|
|
> UDP isnt connection orientated... correct?
Correct. There is nothing in the UDP layer to link packets together in a session (HINT).
> UDP offers no Error detection......correct?
Incorrect. A checksum allows corrupted UDP packets to be detected and discarded. UDP provides no inherent mechanism for signalling an error back to the sender and requesting retransmission (HINT).
Both of these are also true of IP, but are added on top of IP by TCP. So it is possible to build something that would add these features on top of UDP, and that's what your course has asked you to do.
|
|
|