Commit a3506fb0 authored by Filip Gospodinov's avatar Filip Gospodinov
Browse files

core: move explanation about extensions into extension section

Also, drop the mention of the two RESTful endpoints. This was
true only for the initial version of TRP.
parent 11a9188e
......@@ -282,11 +282,6 @@ without custom implementation out-of-the-box with
### Core Protocol
Each VASP who wants to be compliant with this specification must expose two
RESTful endpoints. In addition, and entirely optional, zero or more extensions
can be supported. Users of the TRP protocol should agree on a bilateral basis
on which extensions they will use.
### Headers
Each request must have the following header fields:
......@@ -318,6 +313,10 @@ request-identifier: 2351f3f1-bcff-4a06-a07a-8de94220a9b0
### Extensions
Entirely optional, zero or more extensions can be supported.
Users of the TRP protocol should agree on a bilateral basis
on which extensions they will use.
#### Scope
Extensions can add any and all HTTP headers or parameters.
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment