diff --git a/mbuni/doc/userguide.shtml b/mbuni/doc/userguide.shtml
index f6e4862..08ae4c0 100644
--- a/mbuni/doc/userguide.shtml
+++ b/mbuni/doc/userguide.shtml
@@ -1562,8 +1562,8 @@ function of each of these in turn.
This component (mmsproxy) is the main point of interaction between the
-gateway and MMS clients. It provides an HTTP interface through which
-clients can send MMS messages. The message types expected on this
+gateway and MMS clients and VASPs. It provides an HTTP interface through which
+clients can send MMS messages. From clients, message types expected on this
interface are typically:
- Send Request: Used by client to submit an MM to the
@@ -1594,9 +1594,6 @@ All the above messages are sent to the proxy as the body of an HTTP POST request
Messages are retrieved by supplying the message URL in an HTTP GET
request. When such a request is received, the proxy:
-
-Currently, no MMbox quotas are imposed.
-
- Locates the message: From the URL, the proxy can tell if this
@@ -1617,6 +1614,29 @@ as:
result of the HTTP request.
+
+
+Currently, no MMbox quotas are imposed.
+
+
+
+From VASPs mmsproxy expects and processes:
+
+- Send Requests: Used to submit messages for onward transmission by
+Mbuni
+
- Cancellations: A previously submitted message can be cancelled if
+it hasn't yet been routed to the next processor or receiver. (That is,
+only messages still in the global queue can be cancelled.) Only the
+original submitted can cancel a message.
+
- Replacement: A submitted message can be changed — the VASP may
+ supply different content, which will
+ then replace any content currently in
+ th queue.
+
+
+Note that only SOAP MM7 requests are supported at this stage.
+
+
This component must always be running.