RFC 1926

RFC 1926: An Experimental Encapsulation of IP Datagrams on Top of ATM 💖

Okay bestie, let's start with the title block 🎀 This one is from the Network Working Group and was written by J. Eriksson of KTH NOC (that's Johnny Eriksson, if we're being formal 🙈). It's Category: Informational and it's dated 1 April 1996, which is very suspicious, iykyk 💀. Nothing in the header says it obsoletes or updates anything, so it's just vibing solo ✨

Status of this Memo 📜

This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. 🦋

Abstract 🌸

Okay so this RFC is about encapsulating IP datagrams on top of Acoustical Transmission Media (ATM) 🔊 It's giving non-recommended standard energy, and the document says the distribution of this memo is unnecessary 💅

Overview 👑

The modern laptop of today is literally already packed with the hardware needed for wireless communication over Acoustical Transmission Media, which is just sound waves!! 🔥 Until this moment there has been no standard for how to run IP on such media. This document is an attempt to fill this silence 🥺🫶

Frame transmission 🎶

Here's the vibe check. The IP datagram gets split into four-bit chunks, in network beep order, and each chunk becomes a character based on the table below ✨ A single "b" character gets prepended as a frame start signal. Then everything is sent as ordinary morse code by switching a steady tone on and off 📡 The frequency of that tone is also called the Acoustical Signature (AS number) of the sender, so it's basically their sound-based ID 🧚

    Bits    Character       Bits    Character

    0000    "i"             1000    "u"
    0001    "t"             1001    "m"
    0010    "s"             1010    "v"
    0011    "a"             1011    "f"
    0100    "n"             1100    "w"
    0101    "h"             1101    "l"
    0110    "d"             1110    "k"
    0111    "r"             1111    "g"

To let more than one Local Acoustical Network (LAN) coexist, the document suggests using different AS numbers for different LANs 🌈 It also proposes seven standard AS numbers, which you can check out in the table below 💜

    Name   Frequency

    "a"     440 Hz
    "b"     494 Hz
    "c"     523 Hz
    "d"     587 Hz
    "e"     659 Hz
    "f"     698 Hz
    "g"     784 Hz

For normal operation, AS number "a" (440 Hz) is assumed to be used. Main character energy 🎀

Frame reception 🦋

Literally just the transmission process, but backwards 🔄 bestie that's it, that's the whole section 💀

Security Considerations 🔥

Okay, this one is serious, so listen up 🙈 The author assumes that users take whatever precautions are necessary before trying to use this protocol in any crowded area. Please don't be the girl who starts beeping in a packed room without checking first 😭 Stay safe out there, besties 🫶

Author's Address 💌

Johnny Eriksson KTH NOC EMail: bygg@sunet.se

or

-... -.-- --. --. @ ... ..- .- . - .-.-.- ... . 🧚✨

That's the whole RFC, bestie 🌈💖 Honestly the protocol is iconic and I'm obsessed 💅