Tickets :: Comment on [#13098] Horde seems to drop extended properties

* Your Email Address
* Spam protection	Enter the letters below: . ,.__ .__. ..___ \./ [ __\| \| \|[__ \| [_./\|__\\__\|[___
Comment	>> Horde is the server, not the client, so the arguments don't apply. We >> simply don't support certain attributes. You can't synchronize the >> same data from one client to many servers, but you will synchronize >> the same data from one server to many clients. Thus the server is the >> definite reference of contact information. > > In my recherches in RFC 6352, I could find only hints that clients > should support unknown/extended properties ("As a result, the client > will have to cache the entire set of properties on a resource that is > being changed." in section 9.1). For servers, you can read in section > 6.3.2.2 [https://tools.ietf.org/html/rfc6352#section-6.3.2.2]: > >> Servers MUST support the use of non-standard properties and >> parameters in address object resources stored via the PUT method. > > If I understand this correctly, there's very little scope of interpretation.
Attachment
Watch this ticket