From cff0cfe228c63d7c20e0d02f471f5a52600cd4c7 Mon Sep 17 00:00:00 2001 From: Jet Hughes Date: Mon, 17 Oct 2022 13:28:03 +1300 Subject: [PATCH] vault backup: 2022-10-17 13:28:03 --- content/notes/18-ML-in-IA-2.md | 6 ++-- content/notes/18-transport-layer.md | 43 ++++++++++++++++++++++-- content/notes/19-deepfakes.md | 6 ++-- content/notes/21-SE-in-IA-2.md | 6 ++-- content/notes/22-digital-preservation.md | 6 ++-- 5 files changed, 53 insertions(+), 14 deletions(-) diff --git a/content/notes/18-ML-in-IA-2.md b/content/notes/18-ML-in-IA-2.md index 148f3cbc5..a4df61bd4 100644 --- a/content/notes/18-ML-in-IA-2.md +++ b/content/notes/18-ML-in-IA-2.md @@ -4,9 +4,9 @@ aliases: tags: - lecture - comp210 -sr-due: 2022-10-13 -sr-interval: 3 -sr-ease: 250 +sr-due: 2022-11-08 +sr-interval: 22 +sr-ease: 270 --- # nefarious uses of ml diff --git a/content/notes/18-transport-layer.md b/content/notes/18-transport-layer.md index a0e5d3ae6..eccebabcf 100644 --- a/content/notes/18-transport-layer.md +++ b/content/notes/18-transport-layer.md @@ -4,6 +4,9 @@ aliases: tags: - cosc203 - lecture +sr-due: 2022-10-20 +sr-interval: 3 +sr-ease: 250 --- chapter 3 # service provided by transport layer @@ -151,5 +154,41 @@ different from flow control (one sender too fast for one reciever) ![causes](https://i.imgur.com/Ae5xOa3.png) -AIMD - senders can increase sending rate until packet loss occurs, then decrese rate on loss event -# UDP \ No newline at end of file +AIMD +- senders can increase sending rate until packet loss occurs, then decrese rate on loss event +- additive increase: increase sending rate by 1 maximum segment size every RTT until loss detected +- multiplicative decrease: at each loss event, cut sending rate: in half (TCP Reno), to 1 MSS (TCP Tahoe) +- ![diagram](https://i.imgur.com/AeOEapp.png) +- creates sawtooth behavioiur: probing for bandwidth + +![](https://i.imgur.com/Citauiv.png) +- tcp sender limits transmission: LastByteSent- LastByteAcked < cwnd +- cwnd is dynamically adjusted in response to observed network congestion (implementing TCP congestion control) + +TCP sending behavior: roughly: +- send cwnd bytes, +- wait RTT for ACKS, +- then send more bytes + +TCP rate = cwnd/RTT * bytes/sec + +TCP slow start +- when connectin begins, increase rate exponentially until first loss event + - intially, cwnd = 1 MSS + - double cwnd every RTT + - increment cwnd for every ack recieved +- initally slow but ramps up fast +- ![](https://i.imgur.com/khbzr79.png) + +ssthresh variable: determines when to switch between exponential and linear + +# UDP +- connectionless: + - no handshaking between UDP sender, reciever + - each UDP segment handled independently of others +- beset effort service, UDP segments may be lost or delivered out of order +- no flow and congestion control +- applications + - streaming + - dns SNMP +- less overhead \ No newline at end of file diff --git a/content/notes/19-deepfakes.md b/content/notes/19-deepfakes.md index b40f37f91..3aa286ed1 100644 --- a/content/notes/19-deepfakes.md +++ b/content/notes/19-deepfakes.md @@ -4,9 +4,9 @@ aliases: tags: - comp210 - lecture -sr-due: 2022-10-13 -sr-interval: 3 -sr-ease: 250 +sr-due: 2022-12-29 +sr-interval: 73 +sr-ease: 290 --- # what, origins, how diff --git a/content/notes/21-SE-in-IA-2.md b/content/notes/21-SE-in-IA-2.md index 1fa102723..14a64bac8 100644 --- a/content/notes/21-SE-in-IA-2.md +++ b/content/notes/21-SE-in-IA-2.md @@ -4,9 +4,9 @@ aliases: tags: - comp210 - lecture -sr-due: 2022-10-13 -sr-interval: 3 -sr-ease: 250 +sr-due: 2022-11-07 +sr-interval: 21 +sr-ease: 270 --- # need in all phases diff --git a/content/notes/22-digital-preservation.md b/content/notes/22-digital-preservation.md index c188c2e6b..5c621f074 100644 --- a/content/notes/22-digital-preservation.md +++ b/content/notes/22-digital-preservation.md @@ -4,9 +4,9 @@ aliases: tags: - comp210 - lecture -sr-due: 2022-10-13 -sr-interval: 3 -sr-ease: 250 +sr-due: 2022-11-06 +sr-interval: 20 +sr-ease: 270 --- how long will data survive?