SLIP Payload Encoder

SLIP payload escaping using RFC 1055 END/ESC byte mappings, excluding boundary END bytes; input limited to 64 bytes.

Description

SLIP payload escaping using RFC 1055 END/ESC byte mappings, excluding boundary END bytes; input limited to 64 bytes.

SLIP payload escaping keeps its two reserved octets out of the encoded payload. Framing delimiters are a separate step.

When to use this tool

SLIP payload escaping using RFC 1055 END/ESC byte mappings, excluding boundary END bytes; input limited to 64 bytes.

Prepare the supplied bytes fields for this operation.
Compare the complete example with the representation used by your own input before carrying the result into another step.

How to use the tool and how it works

Enter bytes. Use the exact text syntax, units and index conventions explained below.
Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
Read result.bytes. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Accept at most 64 payload bytes. Map 192 to [219,220], 219 to [219,221] and copy all others, keeping worst-case output within 128 bytes.^[1]

Input field	Meaning and representation	Accepted input
bytes	bytes.	List of finite numbers; at most 128 entries

Output field	Interpretation
result	Object containing the named outputs below.
result.bytes	The bytes list in the ordering and representation described above.

json

{
  "input": {
    "bytes": [
      1,
      192,
      219
    ]
  },
  "output": {
    "result": {
      "bytes": [
        1,
        219,
        220,
        219,
        221
      ]
    }
  }
}

Limitations and assumptions

No END delimiters are added and no checksum or serial transmission is performed.
All declared input fields are required and unexpected top-level fields are rejected. Numbers must be finite; lists are limited to 128 entries and ordinary text fields to 8,192 UTF-16 code units, with tighter limits where stated.
JSON text inputs must parse within bounded nesting and size limits. Numeric outputs outside the safe finite range are rejected; large exact integer results use decimal strings. Indexes and half-open spans are zero-based unless a rank is explicitly described as one-based.

Alternative or Complementary methods

Use a stateful protocol parser when processing partial streams or validating complete packets. Retain the declared prefix width, byte order and payload-versus-frame boundary convention when composing these operations.

References

Tool behavior and example: SLIP Payload Encoder — tool.io

Similar or alternative tools

COBS Payload Encoder
COBS payload encode without a framing zero delimiter; bounded payload to 126 bytes, with strict block bounds.
SLIP Payload Decoder
SLIP payload unescaping using RFC 1055 END/ESC byte mappings, excluding boundary END bytes; strict invalid-escape rejection.