diff options
| author | Florian Dold <florian.dold@gmail.com> | 2019-09-13 01:55:34 +0200 |
|---|---|---|
| committer | Florian Dold <florian.dold@gmail.com> | 2019-09-13 01:55:34 +0200 |
| commit | ed0e2eda07dadf9fd79adf0afa6a7acedd31d929 (patch) | |
| tree | 422e18c1a87734025c2474dc9f203715f53d42d5 | |
| parent | a94b3f91e685036ab05275c1e5ce87fd09e7cf61 (diff) | |
| download | docs-ed0e2eda07dadf9fd79adf0afa6a7acedd31d929.tar.gz docs-ed0e2eda07dadf9fd79adf0afa6a7acedd31d929.tar.bz2 docs-ed0e2eda07dadf9fd79adf0afa6a7acedd31d929.zip | |
nfc: more tunneling
| -rw-r--r-- | taler-nfc-guide.rst | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/taler-nfc-guide.rst b/taler-nfc-guide.rst index 1c0ecae9..50562953 100644 --- a/taler-nfc-guide.rst +++ b/taler-nfc-guide.rst @@ -184,13 +184,16 @@ the ``taler://pay`` URI from the example above: Request tunneling ================= -Request tunnelling allows tunneling a (very) restricted subset of HTTP through NFC. +Request tunneling allows tunneling a (very) restricted subset of HTTP through NFC. In particular, only JSON request and response bodies are allowed. It is currently assumed that the requests and responses fit into one APDU frame. For devices with more limited maximum APDU sizes, additional TIDs for segmented tunnel requests/responsed may be defined in the future. +A request for tunneling is initiated with TID 3 and responded to with TID 2 (see tables above). A tunneling request +is identified by a numeric ID, which must be unique during one pairing between reader and tag. + The request tunneling request/response JSON messages have the following schema: .. code-block:: tsref |