One more thing i do not get Neso only like those comment, where people show love and affection for this channel, they do not even look at us our confusing brains with so many doubts
Thank you so much for explaining something that is fundamentally really simpe. I wish my university lecturers changed their approach on explaining to something like this.
I am confused here you said in problem 1 : "sender waits for ACK for an infinite amount of time " in problem 3 :"After timeout on sender side, a delayed ACK might be wrongly considered as ACK of some other data packet." my question is that, if sender waits for infinite amount of time then how there will be timeout in sender side ?
A late reply but can help students in future. Problem: sender waits for ACK for an infinite amount of time Solution: Introduce "time out" on sender side. New problem: ack not received in given "time out" period. Solution: Give sender's packet a sequence #SN,if receiver sends back Request number==#SN as ack, send the next frame/packet with #SN+1. Otherwise, resend the packet having Sequence number #SN to the receiver.
yes there's mistake sender does not wait for infinite amount of time . There is a timer set at the sender when a frame is send if it does not receive ack in given amount of time it would send the same frame again.
It is simple *it has no flow or error control *data frames are traveling in only one direction from sender to reciever *the data link layer of the reciever immediately remove the header from the frame and hands the data packet to its network layer
One thing was incorrect - 5:54 "This protocol has a drawback of delay in acknowledgement if received after timeout" But there is no concept of timeout in this protocol. This is a drawback of Stop and wait ARQ protocol not the simple stop and wait. Please correct.
IG Noiseless essentially means no noise is added to the data but there are more ways of signal getting distorted. For example, the signal can weaken over time.
in the third issue : if sender have sent a data packet let say Dn and it is waiting for ack An and have not sent any other data packet and as protocol it has recived ack for previous data packets sent ( that's why the sender sent Dn ) let say now it waits for a time period t and then it recieves ack from the reciever , how can the sender consider the ack to be of some other packet sent
Sir I have an query in problem no. 3(problem due to delya in ack/data) if we are sending 1 packet at a time and no other packet is send before receiving an ack how can it can consider the ack for any another packet due to delay?????
Stop and wait, protocol we will be only sending one packet, only after receiving the acknowledgement. How can the delayed acknowledgement or the data be a problem here? once the data packet is sent to the receiver, unless and until some kind of acknowledgement is received from the receiver, then only we can send another packet. so whatever delayed acknowledgement, which is received from the receiver side is that of the previous packet or the most recent packet sent..? Then why are we considering it as a problem? By considering that, it might be wrongly considered as acknowledgement of some other data packet.
I did not understand delay wala part. If frames are transfered one by one then if there is a delay in ack, why it will conclude that it is of different packet?
Sender wait kar raha hoga ke acknowledgement aaye, but ack raaste mein hi lost hogayi toh sender ka timer out hone par woh phir se frame bheje ga taake receiver ko pata chal jaaye ke ack lost hogayi thi.
I didn't get it how can the computer think that acknowledgement as the acknowledgement of some other data as at a time only 1 data can be send. And if their is a timeout then why the sender waits for infinite amount of time to receive the acknowledgement.
If sender only sends data after receiving the ACK and it happening one by one then how a delayed ack might be wrongly considered as ack of the some other data???? The Ack must be of the data sent before it. !! Right ?
Sir u said if ack is lost sender waits for infinite time for it. This tells that it has got no timer based connection them how ack delay is even a problem for the sender. It is sending one data at a time why is it even going to thing it is the ack of some other data ?
good to see how easy they've made it understand, but stop and wait protocol is not an unidirectional protocol , receiver also sends an ACK. packet to the sender.
If the sender is waiting for the ack before sending the next frame.. there cannot be a problem due to delayed ack.. as sender will not send the next frame until it receives the ack. So, tp1 != tp2 won't cause a problem until there is a timer. Am I missing something??
1. Everytime sender sends a packet, it starts a timer. If sender receives ACK before timer expires it sends next packet. If timer expires and no ACK is received then it sends the same packet again. Nobody waits for an infinite amount of time. Yes, they have to wait for a longer period of time. 2. Receiver always sends an ACK Number of the next packet it is expecting from the sender. If sender sent a packet with sequence number n then receiver will send an ACK with number n+1 to tell the sender that it is expecting a packet with sequence number n+1. So i do not understand how sender can misjudge the ACK???
One more thing i do not get
Neso only like those comment, where people show love and affection for this channel, they do not even look at us our confusing brains with so many doubts
true
Fr.....
JazakAllah for this easy and wonderful lecture on this topic.
May Allah gives you more knowledge.
Very well explain. Simple and easy to understand.
You are my teacher bro❤️, you saved me😃
You are the best teacher❤
Thank you so much for explaining something that is fundamentally really simpe. I wish my university lecturers changed their approach on explaining to something like this.
I am confused here
you said in problem 1 : "sender waits for ACK for an infinite amount of time "
in problem 3 :"After timeout on sender side, a delayed ACK might be wrongly considered as ACK of some other data packet."
my question is that, if sender waits for infinite amount of time then how there will be timeout in sender side ?
Obviously bro, you are right. I am also confused for the same
A late reply but can help students in future.
Problem: sender waits for ACK for an infinite amount of time
Solution: Introduce "time out" on sender side.
New problem: ack not received in given "time out" period.
Solution: Give sender's packet a sequence #SN,if receiver sends back Request number==#SN as ack, send the next frame/packet with #SN+1.
Otherwise, resend the packet having Sequence number #SN to the receiver.
yes there's mistake sender does not wait for infinite amount of time . There is a timer set at the sender when a frame is send if it does not receive ack in given amount of time it would send the same frame again.
@@pradeepjaiswal9706 Thank you
@@somalrudra5805 Thank you so much.
Thank you ...sir simplest protocol for noiseless channel was missed
It is simple
*it has no flow or error control
*data frames are traveling in only one direction from sender to reciever
*the data link layer of the reciever immediately remove the header from the frame and hands the data packet to its network layer
@@sheffyjoseph thank you
@@sheffyjosephcollision?
@@arfatbagwan48 what? It's unidirectional
very well explained
good job
Awesome video! Thank you so much! 😊
One thing was incorrect -
5:54 "This protocol has a drawback of delay in acknowledgement if received after timeout"
But there is no concept of timeout in this protocol.
This is a drawback of Stop and wait ARQ protocol not the simple stop and wait.
Please correct.
exactly !
Thank you so much 💓 💗 💛 💖 ☺️
Thank you so much sir, very nice presentation ❤️👏
thanks sir for such a brilliant lecture 👌👌👌
Thank you sir for the explanation keep simple of this excellent lecture
Brilliant man...... 💯
excellent explanation
Thank you
thank you sir ❤️
Yes I clearly understand
thank you a lot
Very good presentation 💘💘
5:25 I think that is , sender is waiting for ack for infinite amount of time , not reciever
very helpful
aap bohot acha padhaate ho
Great Explanation
Explained very easily
Great explanation 👍
Animation is wow... What software is using do this animation... Waiting for respone
thank you very much , it is super easy to understand , good job .
If channel is considered as noiseless, then how can data or acknowledgement gets lost ?
yeah, i think instead of caling it noiseless, he should have only called it stop and wait without arq
IG Noiseless essentially means no noise is added to the data but there are more ways of signal getting distorted. For example, the signal can weaken over time.
Best video
Heartfelt Thankyou 💗✨..
Great lecture!
helpful !!
in the third issue : if sender have sent a data packet let say Dn and it is waiting for ack An and have not sent any other data packet and as protocol it has recived ack for previous data packets sent ( that's why the sender sent Dn ) let say now it waits for a time period t and then it recieves ack from the reciever , how can the sender consider the ack to be of some other packet sent
Sir I have an query in problem no. 3(problem due to delya in ack/data) if we are sending 1 packet at a time and no other packet is send before receiving an ack how can it can consider the ack for any another packet due to delay?????
Yeah I had the same question too
Sir ,what is meant by noiseless channels and noisy channel?..
Tq❤
Stop and wait, protocol we will be only sending one packet, only after receiving the acknowledgement. How can the delayed acknowledgement or the data be a problem here? once the data packet is sent to the receiver, unless and until some kind of acknowledgement is received from the receiver, then only we can send another packet. so whatever delayed acknowledgement, which is received from the receiver side is that of the previous packet or the most recent packet sent..? Then why are we considering it as a problem? By considering that, it might be wrongly considered as acknowledgement of some other data packet.
I did not understand delay wala part. If frames are transfered one by one then if there is a delay in ack, why it will conclude that it is of different packet?
Sender wait kar raha hoga ke acknowledgement aaye, but ack raaste mein hi lost hogayi toh sender ka timer out hone par woh phir se frame bheje ga taake receiver ko pata chal jaaye ke ack lost hogayi thi.
@@hunainaghai3342 ek time pe ek hi frame send hota hai isme to par jab tak last sent frame ka acknowledge na mile to next thode send karte hai
if there is time delay concept then why sender and receiver is waiting for infinite amount of time for ack or data ?
Please upload session later transport layer
I didn't get it how can the computer think that acknowledgement as the acknowledgement of some other data as at a time only 1 data can be send. And if their is a timeout then why the sender waits for infinite amount of time to receive the acknowledgement.
yea this is kinda wrong lol
apllied mathematics for bscit ke bhi video daaalo naa sir
How the sender is set the ack time and receiver data time in case this is protocol okay then how the sender and receiver is wait for infinite time
In DL layer it is frames and not data packets.. pls clarify
what is simplest protocol? in noiseless channels
STOP & WAIT
If sender only sends data after receiving the ACK and it happening one by one then how a delayed ack might be wrongly considered as ack of the some other data???? The Ack must be of the data sent before it. !! Right ?
Tnq ..🔥❤️
uninstalled and then again reinstalled, do you know what might have happened to them ?!
Sir u said if ack is lost sender waits for infinite time for it. This tells that it has got no timer based connection them how ack delay is even a problem for the sender. It is sending one data at a time why is it even going to thing it is the ack of some other data ?
Stop and wait me timeout nhi hota according to problem no 2
what is noiseless and noise channel?
every channel has noises, noiseless channel is just in ideal conditions, noises make the data's quality decrese
Why did the lecturer explain this simple concept like rocket science?
8/7/21
11:27 am
Material pls
Could please provide slide link?
good to see how easy they've made it understand, but stop and wait protocol is not an unidirectional protocol , receiver also sends an ACK. packet to the sender.
its unidirectional here unidirection mean sender and reciever cannot send frame at a same time
6:09 minutes why using concept of timeout in stop and wait protocol????? Sender will wait for an infinite amount of time
where are you from bro?
"Bro" ? 😂
U said The sender has to wait for long time . But again u said there will be timeout.. I can't get this 🙄
Sir... Instead of saying data packets.. You can say frame....
I think using packet name in DLL is totally wrong ..
Thank u😊
You're correct, but it is not at all an issue as frames and packets are used interchangeably even by highly revered authors.
NO ONE CAN CLEARLY THAN THIS VIDEO
nah this video missed so much knowledge for real
If the sender is waiting for the ack before sending the next frame.. there cannot be a problem due to delayed ack.. as sender will not send the next frame until it receives the ack. So, tp1 != tp2 won't cause a problem until there is a timer. Am I missing something??
Yes, i also thought same about it . If there is no timer then sender will wait for infinite amount of time before receiving an ACK .
1. Everytime sender sends a packet, it starts a timer. If sender receives ACK before timer expires it sends next packet. If timer expires and no ACK is received then it sends the same packet again. Nobody waits for an infinite amount of time. Yes, they have to wait for a longer period of time.
2. Receiver always sends an ACK Number of the next packet it is expecting from the sender. If sender sent a packet with sequence number n then receiver will send an ACK with number n+1 to tell the sender that it is expecting a packet with sequence number n+1. So i do not understand how sender can misjudge the ACK???
No sequence number in stop and wait protocol. It is a theoretical protocol. He is correct to the best of my knowledge
First of all in noise less channel how data will be missed ....???
But the same mistake goes for error control?
Why? Do u know?
best
i think you should use data frames instead of packet
Bhai numerical quantities badao yar every topic ka different different type numerical
It is "we will see what they are". Not "We will see what are they"
my professor uses your video ss to teach us , lol
The explanation you gave for unidirectional data transmission is wrong
Hello
Data packet Retransmitting is not explained
Indians