3.3 Networking Fundamentals for Remote Reporting
Key Takeaways
- Private IPv4 ranges defined in RFC 1918 (10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16) are not routed on the public internet and reach remote participants through Network Address Translation (NAT).
- A 169.254.x.x address means the computer failed to reach a DHCP server and assigned itself an APIPA link-local address, so it cannot reach the internet.
- For remote proceedings, plan for steady upload capacity, low latency, and low jitter; audio breaks up first when jitter and packet loss rise.
- Avoid WEP and WPA-TKIP, which are broken; use WPA2-AES or WPA3 to protect confidential realtime text.
- A standalone cellular hotspot on a different carrier gives remote reporters a backup connection if venue or home broadband fails.
3.3 Networking Fundamentals for Remote Reporting
Quick Summary: Remote and hybrid proceedings demand a solid grasp of IP networking, router architectures, and bandwidth metrics. Mastering private versus public IPv4 schemes, DHCP versus static addressing, firewall port navigation, modern WPA2/WPA3 Wi-Fi encryption, and cellular hotspot failover protocols ensures that your remote audio, video, and realtime steno streams operate without interruption.
The Remote Reporting Landscape
The legal landscape underwent a permanent structural transformation with the widespread adoption of remote and hybrid depositions, arbitrations, and administrative hearings. Today's court reporter frequently operates not from a physical deposition conference room, but from a high-tech remote command station, capturing verbatim testimony across videoconferencing platforms (such as Zoom, Microsoft Teams, or Webex) while simultaneously streaming realtime text feeds to counsel across the globe.
In this distributed environment, the court reporter's duties expand beyond machine mastery and transcript formatting. The reporter is responsible for maintaining an uninterrupted telecommunications conduit. A technical disruption in the reporter's home office or remote facility—such as an audio packet drop, a video freeze, or an IP conflict—threatens the integrity of the official proceeding. The RPR job analysis lists hot spots, Wi-Fi, LANs, and WANs among the Domain 1 topics for troubleshooting a realtime file.
IP Addressing Architectures: IPv4, IPv6, and Subnetting
Every device connected to an Internet Protocol (IP) network—whether a CAT laptop, a wireless realtime tablet, or an IP audio interface—must possess a unique IP address that identifies its location and enables packet routing.
IPv4 vs. IPv6
- IPv4 (Internet Protocol Version 4): Employs a 32-bit binary address expressed in dot-decimal notation consisting of four octets (e.g.,
192.168.1.100), yielding approximately 4.3 billion possible unique addresses. Due to global address exhaustion, private addressing and NAT are universally utilized. - IPv6 (Internet Protocol Version 6): Employs a 128-bit hexadecimal address formatted as eight groups of four hexadecimal digits separated by colons (e.g.,
2001:0db8:85a3:0000:0000:8a2e:0370:7334), providing an inexhaustible pool of $3.4 \times 10^{38}$ addresses.
Public vs. Private IP Addresses (RFC 1918)
The Internet Assigned Numbers Authority (IANA) reserved three blocks of IPv4 addresses under RFC 1918 specifically for private local area networks (LANs). These addresses are strictly non-routable across the public Internet:
| Private Address Class | Subnet Range | CIDR Prefix | Total Host Capacity | Typical Use Case in Court Reporting |
|---|---|---|---|---|
| Class A | 10.0.0.0 to 10.255.255.255 | 10.0.0.0/8 | 16,777,216 addresses | Large corporate law firms, municipal courthouses, enterprise networks. |
| Class B | 172.16.0.0 to 172.31.255.255 | 172.16.0.0/12 | 1,048,576 addresses | Regional enterprise networks, university legal clinics. |
| Class C | 192.168.0.0 to 192.168.255.255 | 192.168.0.0/16 | 65,536 addresses (commonly /24 = 254) | Standard residential routers, portable steno travel routers, mobile hotspots. |
Special Purpose IP Addresses: Loopback and APIPA
- Loopback Address (
127.0.0.1): A special internal software address that routes traffic directly back into the local computer. Reporters use127.0.0.1(orlocalhost) to test CAT software realtime output to a locally installed viewer client on the same machine without accessing an external network. - Automatic Private IP Addressing (APIPA -
169.254.x.x): The address block169.254.0.1to169.254.255.254(with subnet mask255.255.0.0) is automatically assigned by the operating system when a network interface is set to obtain an IP automatically via DHCP, but no DHCP server responds.
[!WARNING] The APIPA Danger Signal: If your CAT laptop displays an IP address starting with
169.254.x.x, your computer has failed to communicate with the local router or access point. You will have zero internet access, cannot reach the default gateway, and will be completely unable to stream remote realtime text or connect to videoconference depositions.
IP Assignment: DHCP vs. Static Configuration
Network interfaces receive IP configurations through one of two mechanisms:
Dynamic Host Configuration Protocol (DHCP)
DHCP automates network configuration through a four-step handshake known as DORA:
- Discover: The client broadcasts a request searching for an active DHCP server.
- Offer: The server responds with an available IP address, subnet mask, default gateway, and DNS servers.
- Request: The client formally requests the offered configuration.
- Acknowledge (ACK): The server confirms the assignment and binds the IP to the client's MAC address for a specified Lease Time.
Note: A client normally renews its lease automatically about halfway through the lease time, usually without any interruption. Problems arise when the DHCP server is unreachable or its address pool is exhausted, which is when APIPA addresses appear.
Static IP Addressing
A static IP address is manually entered into the network adapter properties and never expires or changes.
- When to Use Static IPs: When a reporter travels with a dedicated portable router to host an in-person or hybrid realtime feed (e.g., distributing text to 5 iPads via CaseViewNet or Bridge), assigning the host CAT laptop a static IP (such as
192.168.1.10) ensures that client devices always know exactly where to send their socket connection requests without relying on DNS lookups.
Network Hardware, Firewalls, and Port Management
Data traversing a modern network passes through multiple functional hardware layers:
[CAT Laptop / Host]
| (Ethernet or Wi-Fi)
v
[Network Switch] (Layer 2 - Frames via MAC Addresses)
|
v
[Gateway Router] (Layer 3 - Packets via IP Addresses & NAT)
|
v
[Stateful Firewall] (Inspects ports & blocks unsolicited traffic)
|
v
[Public Internet (WAN)] ====> [Remote Counsel / Streaming Relay Server]
Network Address Translation (NAT)
Because private RFC 1918 addresses cannot traverse the public Internet, the gateway router executes Network Address Translation (NAT). NAT modifies the private source IP address in the packet header to the router's single public WAN IP address, tracking individual internal socket connections via unique port numbers.
Firewalls and Port Forwarding
Firewalls protect internal networks by blocking unauthorized inbound connections.
- Port Numbers: Software applications communicate over standardized 16-bit port numbers (ranging from 0 to 65535). Common ports include:
- Port 80 (HTTP): Unencrypted web traffic.
- Port 443 (HTTPS): Encrypted web traffic (used by browser-based realtime viewers and Zoom signaling).
- Port 53 (DNS): Domain Name System address resolution.
- Port Forwarding: In legacy peer-to-peer realtime streaming setups where external attorneys connected directly to the reporter's laptop across the Internet, the reporter had to configure Port Forwarding rules in their router, instructing it to forward all incoming traffic on a specific port (e.g., port
1099or8080) directly to the CAT laptop's internal private IP. - Modern Cloud Relays: Cloud-based streaming services offered with CAT systems (for example, Stenograph's CaseViewNet and Advantage Software's Bridge) avoid inbound port forwarding. The CAT laptop makes an outbound encrypted connection, typically over port 443, to a relay server that authorized viewers join with a session code.
Wireless LAN Engineering & Encryption Protocols
When operating over Wi-Fi, the reporter must balance radio performance against data security.
Wi-Fi Frequency Bands: 2.4 GHz vs. 5 GHz
- 2.4 GHz Band: Penetrates walls and solid obstacles effectively, but has lower maximum throughput, only 3 non-overlapping channels (1, 6, and 11), and suffers heavy interference from Bluetooth and consumer gadgets.
- 5 GHz Band: Offers 24+ non-overlapping channels, vastly higher data throughput, and minimal RF congestion. However, 5 GHz radio waves attenuate rapidly through solid walls. For remote reporting setups, the CAT workstation should always be connected via physical Ethernet or placed in close proximity to a 5 GHz Wi-Fi 5 (802.11ac) or Wi-Fi 6 (802.11ax) access point.
Wi-Fi Security Protocols
Sending confidential text over open or weakly secured Wi-Fi conflicts with the duty to ensure the security of information (COPE Provision 4).
| Protocol | Release Year | Cryptographic Engine | Security Status & Recommendation |
|---|---|---|---|
| WEP (Wired Equivalent Privacy) | 1997 | 64-bit / 128-bit RC4 | Completely Broken. Can be cracked in seconds using automated tools. Never use. |
| WPA-TKIP | 2003 | RC4 with Temporal Key Integrity | Deprecated. Vulnerable to key extraction attacks. Do not use. |
| WPA2-Personal | 2004 | AES-CCMP (128-bit) | Current Robust Standard. Secure for professional transcript transmission if paired with a complex passphrase. |
| WPA3-Personal | 2018 | SAE (Simultaneous Authentication of Equals) | Strongest current option. SAE resists offline dictionary attacks. Recommended where supported. |
Bandwidth, Latency, and Jitter Metrics for Remote Litigation
Remote court reporting places simultaneous, competing demands on a telecommunications connection. The reporter must upload high-definition video, transmit crystal-clear audio, maintain an uncompressed backup audio stream, and transmit realtime steno packets.
Understanding the distinction between bandwidth, latency, and jitter is vital when evaluating a remote setup. The figures in the table are practical planning targets, not NCRA requirements; videoconference providers publish their own minimums.
[Bandwidth] = Width of the pipe (volume of data per second: Mbps)
[Latency] = Travel time from sender to receiver (ping delay: milliseconds)
[Jitter] = Variation in packet arrival times (delay instability: milliseconds)
| Metric | Minimum Specification | Recommended Professional Spec | Impact of Degradation on Remote Proceedings |
|---|---|---|---|
| Download Speed | 10 Mbps | 25+ Mbps | Video feeds freeze; shared exhibits and documents render slowly. |
| Upload Speed | 5 Mbps | 15+ Mbps | Crucial. Low upload causes the reporter's video to stutter and outbound audio to drop syllables. |
| Ping Latency | < 50 ms | < 25 ms | Delays between speech and reception; causes participants to talk over each other constantly. |
| Jitter | < 10 ms | < 5 ms | Causes robotic audio distortion, packet buffer overflows, and lip-sync desynchronization. |
| Packet Loss | 0.0% | 0.0% | Dropped words, missing steno strokes, distorted syllables requiring constant colloquy interruptions. |
[!NOTE] Why Audio Suffers First: Videoconferencing software uses UDP (User Datagram Protocol) for audio and video streams to prioritize real-time delivery over perfect error checking. While high-bandwidth video packets can drop resolution gracefully, audio packets cannot be delayed; when latency spikes or jitter exceeds buffer limits, audio chunks are discarded, creating "robotic speech" or silent gaps that destroy verbatim record capture.
Cellular Mobile Hotspots & Redundant Failover Strategy
Relying on a single residential broadband or courthouse internet connection creates a catastrophic single point of failure. If an ISP truck hits a neighborhood fiber line or a local transformer blows, an active multi-million-dollar deposition will be abruptly paralyzed.
Professional Hotspot Protocol
Many remote reporters keep an independent, battery-powered cellular mobile hotspot (LTE or 5G) on a different carrier than their home or office internet (e.g., AT&T fiber broadband backed up by a Verizon or T-Mobile 5G cellular hotspot).
- Standalone Hotspots vs. Smartphone Tethering: Dedicated hotspot pucks possess superior MIMO antenna arrays, sustained thermal management, and do not suffer disconnection when incoming cellular voice calls are received.
- Failover Routine: If primary broadband drops:
- The reporter should immediately alert participants via audio that a network switchover is occurring.
- Switch the laptop to the active hotspot Wi-Fi or USB tether.
- Re-engage the videoconference and cloud realtime feeds.
- Where coverage is good, the proceeding can often resume within a minute or two.
A court reporter setting up for a remote deposition connects their CAT laptop to the local deposition conference room network via Ethernet, but cannot access the Internet or stream their realtime text. Checking the network adapter status, the reporter observes the IPv4 address is 169.254.112.45. What does this address indicate?
Given the COPE Provision 4 duty to preserve confidentiality and ensure the security of information, which wireless security protocol should a reporter strictly prohibit when setting up a local Wi-Fi router for wireless realtime streaming?
When broadcasting a simultaneous video conference, digital audio recording, and live realtime text feed during a remote trial, which network performance metric is most critical for preventing audio breakup, robotic distortion, and speech desynchronization?