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

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/13098
------------------------------------------------------------------------------
  Ticket             | 13098
  Updated By         | play at bitfire.at
  Summary            | Horde seems to drop extended properties
  Queue              | Turba
  Version            | Git master
  Type               | Bug
  State              | Not A Bug
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


play at bitfire.at (2014-04-08 08:37) wrote:

> 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.