From bb98c7d24be26da48072c24018a4d68c18ac71e2 Mon Sep 17 00:00:00 2001
From: Alex Van Boxel <alex@vanboxel.be>
Date: Sun, 31 Jan 2016 11:57:44 +0100
Subject: [PATCH] Allow for two custom frames.

---
 protocol-specification.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/protocol-specification.md b/protocol-specification.md
index 59b037b..6b1d6ef 100644
--- a/protocol-specification.md
+++ b/protocol-specification.md
@@ -17,6 +17,12 @@ TLM | `0010` | `0x20`
 RESERVED | `0011` | `0x30`
 RESERVED | `0100` | `0x40`
 
+The specification allows for two custom frames that are not described in the spec and are provider specific. Because they don't have a formal specification they should always be paired with either a UID or URL frame so the receiver can identify the provider.
+
+Frame Type | High-Order 4 bits | Byte Value
+:----------|:-----------------:|:---------:
+CUSTOM | `1110` | `0xE0`
+CUSTOM | `1111` | `0xF0`
 
 The four low-order bits are reserved for future use and must be `0000`.