diff options
Diffstat (limited to 'design-documents/006-extensions.rst')
| -rw-r--r-- | design-documents/006-extensions.rst | 12 |
1 files changed, 5 insertions, 7 deletions
diff --git a/design-documents/006-extensions.rst b/design-documents/006-extensions.rst index 42a0e575..576809ad 100644 --- a/design-documents/006-extensions.rst +++ b/design-documents/006-extensions.rst @@ -1,5 +1,5 @@ -Design Doc 006: Extensions for GNU Taler -############################################# +DD6: Extensions for GNU Taler +############################# Summary ======= @@ -84,7 +84,7 @@ Extension object ---------------- The definition of ``Extension`` object itself is mostly up to the particular -feature. **However**, it MUST have +feature. **However**, it MUST have #. the boolean field ``critical`` that has the same semantics as as "critical" has for extensions in X.509_: if true, the client must "understand" the @@ -93,7 +93,7 @@ feature. **However**, it MUST have #. the field ``version`` of type `LibtoolVersion` which contains the version information of the extension in Taler's `protocol version ranges notation`_. - + .. _X.509: https://datatracker.ietf.org/doc/html/rfc5280#section-4.2 .. _`protocol version ranges notation`: https://docs.taler.net/core/api-common.html#protocol-version-ranges @@ -150,7 +150,7 @@ object MUST be signed by the exchange's master signing key. Whenever extensions are enabled or disabled, the offline tool MUST sign the SHA256 hash of the normalized JSON-string of the ``extensions`` object, if it is not empty. -In order to do so, the ``taler-exchange-offline`` tool MUST +In order to do so, the ``taler-exchange-offline`` tool MUST #. have the complete list of all available optional features/extensions and their versions builtin and @@ -209,5 +209,3 @@ Discussion / Q&A The initial ideas presented here are based on discussions between Özgür Kesim and Christian Grothoff. - - |