[OTR-dev] making DATA_REQUEST and DATA_RESPONSE official TLVs (aka OTRDATA)

Hans-Christoph Steiner hans at guardianproject.info
Fri Feb 6 04:32:19 EST 2015

So far, resounding silence on this, so I'll try again!

We (Guardian Project/ChatSecure) are currently working on nailing down the
final API of our DATA_RESPONSE and DATA_REQUEST TLVs for in-band data
transfer.  We have it implemented now in otr4j and OTRKit, its been integrated
in ChatSecure-android for 6+ months, and now we are pushing forward getting
this integrated into more apps.

We have been using the TLV numbers 100 and 101 to make sure that we don't
conflict with anything that might be in the works.  I think now is the time to
make an official number so that new apps do not need to handle a migration
from the temp numbers.

What do we need to officially claim TLV numbers in the OTR protocol? How about
9 and 10?  Should I submit a patch to libotr?  Once we get it nailed down, the
OTRKit code can be ported to libotr, since OTRKit is really a wrapper of libotr.

Here is some more discussion, for those who want to know more details:

And OTRKit's implementation:


PGP fingerprint: 5E61 C878 0F86 295C E17D  8677 9F0F E587 374B BE81

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.cypherpunks.ca/pipermail/otr-dev/attachments/20150206/5229320c/attachment.pgp>

More information about the OTR-dev mailing list