(Predefined Aux-Item Types): Added a draft description of the

	allowed-content-type aux item.

doc/Protocol-A.texi

@@ -2,7 +2,7 @@
 @c
 @c FIXME: Explain how the garb works with nice and keep-commented
 @c
-@c $Id: Protocol-A.texi,v 1.96 1999/11/20 20:06:30 ceder Exp $
+@c $Id: Protocol-A.texi,v 1.97 2000/08/04 17:05:57 ceder Exp $
 @c %**start of header
 @setfilename protocol-a.info
 @settitle LysKOM Protocol A
@@ -1167,6 +1167,45 @@ This is a recommendation only; it is up to the client that creates a new
 person to also add him to the conferences that are specified via
 @code{recommended-conf}.
 
+@item allowed-content-type [30] (conference)
+
+@c FIXME: see comments to 5323623.
+
+Data is a non-negative decimal priority number, followed by a space,
+followed by a LysKOM content type glob pattern.  Clients should send
+texts to a conference only if the content-type matches any of the
+allowed-content-type glob patterns.
+
+If there are allowed-content-type aux-items with different priority
+numbers, it is a hint to the client about which content-type is most
+desirable.  Content-types that matches a lower priority number are
+preferred.
+
+As an example, consider a conference with the following four
+allowed-content-type aux-items:
+
+@example
+1 text/plain
+2 x-kom/basic
+2 text/enriched
+3 text/*
+@end example
+
+This means that text/plain is preferred, that x-kom/basic and
+text/enriched can be used if there is a reason why text/plain is
+inadequate, and that any text type (such as text/html) is acceptable.
+Other content types, such as x-kom/user-area, should not be used.
+
+If no allowed-content-type aux-item exists, it should be interpreted as
+if a single allowed-content-type aux-item with the value @samp{1
+text/plain} exists.
+
+The server does not currently enforce the above restriction on the
+content type of new texts.  This mechanism is currently a hint to the
+client (or to the author of a new text).  This may change in the
+future, if experience shows that it is desirable to have the server
+enforce the content type.
+
 @end table
 
 @node Client-Specific Aux-Item Types