From 8f8c2ad8b32eb808a942e056a63b9452dbf5219f Mon Sep 17 00:00:00 2001 From: Steve Kille Date: Wed, 2 Nov 2016 10:26:02 +0000 Subject: [PATCH] Remove question on where to standardize MIX Proxy --- xep-0369.xml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/xep-0369.xml b/xep-0369.xml index e846fb48..b0cc9fd1 100644 --- a/xep-0369.xml +++ b/xep-0369.xml @@ -200,7 +200,7 @@

The behaviour of a MIX Proxy and the protocol between MIX Proxy and MIX Client is not currently defined in this specification. It will be defined in one of three places. - It may be desirable in some situations to provide different service to different clients. For example, a mobile client may participate in a smaller set of MIX channels than a desktop client. This needs support from the server to which the client connects, so that MIX client and the connected server can negotiate which channels to send. This is not supported by the core MIX specification, but it is anticipated that this will be supported by another specification. + It may be desirable in some situations to provide different service to different clients. For example, a mobile client may participate in a smaller set of MIX channels than a desktop client. This needs support from the server to which the client connects, so that MIX client and the connected server can negotiate which channels to send. This is not supported by the core MIX specification, but it is anticipated that this will be specified in one of the following ways:

    @@ -211,7 +211,6 @@
  1. As a new section in a future version of the MIX Specification.
-

QUESTION: Input is sought on the best place to standardize MIX Proxy.