The description suggests this is useful for durable subscriptions but it isn't clear if the writer intended it to only be for the in memory queue or also the lifetime of non-volatile queues.
Do we want to define 2 Properties here?

• MaxMonitoredItemsQueueSize - This would describe the normal maximum size of a monitored item.
• MaxDurableSubscriptionLifetime - This would describe the normal maximum lifetime, in hours, of a durable subscription.

Comments from Karl,

We have not talked about the lifetime but for me it makes sense to add this property also.

I wonder if we also need two queueSize properties. One for "normal" subscriptions (there it will be a handful as it is kept in memory) and one for durable subscriptions. Servers will often use disk space for queues of durable subscriptions and may support large queue sizes.

Add MaxMonitoredItemsQueueSize to ServerCapabilitiesType

Agreed to changes in Munich F2F.