Describes the
motivation,
rationale, and
competitive analysis
that went into the
creation and
definition of the
Nest Weave: Tag
Length Value (TLV)
data representation
format. In the
competitive analysis,
comparisons are made
against alternative
representations such
as JSON, Google
Protocol Buffers,
ASN.1, EXI, Apache
Thrift, and CBOR
along a number of
evaluation criteria.
Describes a canonical translation for all documents encoded in Weave TLV format to and from their corresponding encoding as documents in the Concise Binary Object Representation (CBOR).
Introduces the specification for a derived Weave Common trait that generalizes how any Weave device resource presents battery power source information common to any such device.
Describes the expected behavior of a Weave device with respect to how it configures its network interfaces and network routing information in various situations.