Diff: xDotBridge/README.md

Revision:

61:8d9efd33cac9

Parent:

55:79ab0bbc5008

Child:

62:9751a8504c82

--- a/xDotBridge/README.md	Mon Mar 06 15:16:58 2017 -0700
+++ b/xDotBridge/README.md	Thu Mar 09 16:47:42 2017 -0700
@@ -65,6 +65,57 @@
 and data session keys.  This guarantees by design that all message sent can
 only be received and decoded by units in the pair group.
 
+### Brute force algorithm
+TODO
+
+#### Brute force alert message
+==============================================
+= Offset | Size (in Bytes) | Name            =
+==============================================
+= 0x00 | 2 Bytes | Alert Msg Flag  (0xEF10)  =
+==============================================
+= 0x02 | 8 Bytes | xDot EUI                  =
+==============================================
+= 0x0A | 2 Bytes | Alert Data                =
+==============================================
+= 0x0C | 4 Bytes | Alert Sequence Number     =
+==============================================
+Total of 16 bytes
+
+#### Brute force pair request message
+==============================================
+= Offset | Size (in Bytes) | Name            =
+==============================================
+= 0x00 | 2 Bytes | Pair Request Flag (0xFE01)=
+==============================================
+= 0x02 | 8 Bytes | xDot EUI (requester)      =
+==============================================
+= 0x0A | 6 Bytes | Reserved                  =
+==============================================
+* Total of 16 Bytes
+
+Ideas for reserved:
+ * Network type desired
+ * Messages generated
+
+#### Brute force pair accept message
+==============================================
+= Offset | Size (in Bytes) | Name            =
+==============================================
+= 0x00 | 2 Bytes | Pair Accept Flag (0xFD02) =
+==============================================
+= 0x02 | 8 Bytes | xDot EUI (RX Master)      =
+==============================================
+= 0x0A | 4 Bytes | Reserved for Frequency    =
+==============================================
+= 0x0D | 4 Bytes | Network ID                =
+==============================================
+= 0x12 | 8 Bytes | Network Key               =
+==============================================
+= 0x1A | 8 Bytes | Data session Key          =
+==============================================
+* Total of 34 Bytes
+
 ## Peer to Peer Pair
 Pairing needs to support many topologies including one TX to one RX, many TX to
 one RX, and finally many TX to many RX.  The pairing process not only has the
@@ -107,7 +158,9 @@
 track of the copies.
 * This scheme does not support hybrid pairing where two RX can receive one TX
 and one of the two can receive additional TX messages the other cannot.  It might be
-possible to support this but the pairing process would become more complex. 
+possible to support this but the pairing process would become more complex.
+
+#### Pair message details
 
 ## LoRaWAN
 Just use the xDots and the conduit as they are designed to be used.  No pairing just straight LoRaWAN.