# Fundamentals of Communications and Networks — Stale course audit

- URL: https://getstale.tech/run/web_20260504T212437Z
- Target role: Network Engineer
- Course focus: Computer Networks — Tcp/ip Layered Protocol Stack
- Audit date: 2026-05-04T21:24:37Z
- Verified findings: 5
- Structured data: https://getstale.tech/run/web_20260504T212437Z.json

## Findings

### 1. Security risk (high severity)

**Location:** Week 15 - VPNs.pptx slide 5

**What the slide says:**

> Most common VPN communications protocol standards: Point-to-Point Tunneling Protocol (PPTP) for individual client to server connections; Layer 2 Tunneling Protocol (L2TP) for individual client to server connections

**Primary source:** https://learn.microsoft.com/en-us/windows-server/remote/remote-access/configure-vpn-protocols (verified)

> Beginning with Windows Server 2025, new RRAS setups don't accept VPN connections based on PPTP and L2TP protocols.

**What to learn instead:** Do not present PPTP and L2TP as 'most common' VPN standards. Microsoft formally deprecated both in Windows Server and explicitly recommends against their use 'due to their lack of security features'. Teach IKEv2/IPsec, OpenVPN, WireGuard, and SSTP instead; if PPTP/L2TP are mentioned, frame them as legacy/insecure for historical context only (PPTP's MS-CHAPv2 has been broken since 2012).

### 2. Incorrect (medium severity)

**Location:** Week 12 _13 _ 14 - Application Layer.pptx slide 14

**What the slide says:**

> HTTP 1.1 [RFC 7320]

**Primary source:** https://www.rfc-editor.org/rfc/rfc7320 (verified)

> URI Design and Ownership

**What to learn instead:** RFC 7320 is titled 'URI Design and Ownership' and has nothing to do with HTTP/1.1. The HTTP/1.1 messaging spec is currently RFC 9112 (which obsoletes RFC 7230); HTTP semantics are in RFC 9110. Update the citation to RFC 9110/9112 (or, if older material is desired, RFC 7230).

### 3. No longer works (medium severity)

**Location:** Week 12 _13 _ 14 - Application Layer.pptx slide 16

**What the slide says:**

> object can be HTML file, JPEG image, Java applet, audio file,…

**Primary source:** https://docs.oracle.com/en/java/javase/17/docs/api/java.desktop/java/applet/Applet.html (verified)

> The Applet API is deprecated, no replacement.

**What to learn instead:** Remove 'Java applet' from the list of web-page object types. The Applet API was deprecated in JDK 9 (JEP 289), deprecated for removal in JDK 17 (JEP 398), and all major browsers have removed support for the NPAPI Java plug-in. Use HTML5/JavaScript/WebAssembly instead.

### 4. Outdated (medium severity)

**Location:** Week 15 - VPNs.pptx slide 5

**What the slide says:**

> IPsec is built into IPv6 standard and is implemented as an add-on to IPv4

**Primary source:** https://www.rfc-editor.org/rfc/rfc6434 (verified)

> Previously, IPv6 mandated implementation of IPsec and recommended the key management approach of IKE. This document updates that recommendation by making support of the IPsec Architecture [RFC4301] a SHOULD for all IPv6 nodes.

**What to learn instead:** Update the slide to reflect that IPv6 no longer mandates IPsec. RFC 6434 (Dec 2011), and its successor RFC 8504, downgraded IPsec from MUST to SHOULD for IPv6 nodes. IPsec is available for both IPv4 and IPv6 but is not a built-in mandatory part of IPv6 in current standards.

### 5. Outdated (low severity)

**Location:** Week 12 _13 _ 14 - Application Layer.pptx slide 42

**What the slide says:**

> RFC 2822 defines syntax for e-mail message itself

**Primary source:** https://www.rfc-editor.org/rfc/rfc5322 (verified)

> Obsoletes: 2822

**What to learn instead:** Cite RFC 5322 (Internet Message Format, October 2008), which obsoletes RFC 2822. RFC 5322 has itself been updated by RFC 6854.

## Market fit

Course is a TCP/IP networking-fundamentals survey; every high-frequency DevOps/SRE demand (Docker, Kubernetes, Terraform, CI/CD, Prometheus/Grafana/Datadog, AWS, Linux, Bash, Git, Go, on-call/SLOs) is cross-domain to networking with zero partial coverage to extend, so no in-scope gaps can be surfaced under the extend-only and depth-bound rules.

## Recommended topics

No prescriptions are issued. The Market-fit agent surfaced zero in-scope gaps (gaps: []). The course is an undergraduate TCP/IP networking-fundamentals survey, and every high-frequency DevOps/SRE demand in the postings — Docker (100%, post_061–post_072), Bash (100%, post_061–post_072), Python (92%), Git (92%), Linux/Kubernetes/Monitoring (83%), Terraform/CI-CD/AWS (75%), Prometheus/GitHub Actions/On-call/Go (67%), Helm/Datadog (58%), Jenkins/Grafana/SLOs/Ansible (50%), GitLab CI/ArgoCD/Vault/Incident Response (42%) — is a cross-domain tooling/operations skill with no partial coverage in any of the seven course weeks to extend. Under Rule 1 (extend-only) and Rule 2 (respect the conceptual depth bound of a top-down networking survey), none of these tools can be honestly grafted onto Weeks 1, 4/5, 6/7, 8/9, 10/11, 12/13/14, or 15 without inventing a wholly new topic or pushing the course past its stated depth.

---
Produced by Stale (https://getstale.tech). Request a course audit: https://getstale.tech/request-audit