Which one is not done by Data link layer ?
1. bit stuffing
2. LRC
3. CRC
4. parity check
Answers were Sorted based on User's Feedback
Answer / zgeorgem
1. bit stuffing
2. LRC
3. CRC
4. parity check
here 1 2 3 are either error detection or error correction
which can be potentially done by DataLink Layer
But bit stuffing (from wikipedia) seems to be done by the
physical layer so that the data arrives at the device
synchronized... (i am not sure of the working but i am sure
that it is a layer1 concept)
| Is This Answer Correct ? | 14 Yes | 4 No |
Answer / yogesh babar
LRC is not done by Data Link Layer.
Reason- Bit stuffing is used in DLL to identify the new frame and the older frame which is recognized by adding 0111 at the end of every frame so that receiver will get idea that from this moment new frame will start.
Regarding CRC is used for to check whether data is altered during transmission or not and parity is also doing the same.
So remaining is LRC which is not present at DLL at all.
| Is This Answer Correct ? | 5 Yes | 1 No |
1.what is ram , hard disk ,processor,motherboard ,bios and use of
I am using vm ware In my system and I am using 2003server in vm ware ( my o.s is XP ) Now I would like to install .zip in my 2003server machine .how can I do this
draw the diagrams for TDMA,CDMA, FDMA and explain it. explain congestion control, congestion avoidence, sliding window protocol..
1 Answers Aricent, Jaypee, Multinet, NTPC, Wipro,
Tell the correct definition of router, hub and switch and where do we use these?
How to communicate between difference process?
What is MAC address
how would you troubleshoot a situation where there is no display on a monitor?
what is the name of the Jack used for Network Setup between one computer to Another and from computer to another device?
what is the function of msconfig in our system...?
What are the advantages and disadvantages of router
17 Answers Cisco, Cognizant, HP, IBM, TATA,
Explain distance vector routing . What are its limitations and how are they overcome?
Differentiate between ISO-OSI and TCP/IP reference model.