[lemonade] some questions in draft-ietf-lemonade-notifications-03

Hi All,

I have some questions as follows:

Questions 1:

In 10.2 (Provision Entries), "push.shared" is defined as an attribute of in-band notifications (not the attribute of outband notifications) while in the first example in 10.4 "push.shared" is regarded as the attribute of outband notifications.

Why? Maybe "push.shared" should be defined as an attribute of outband notifications too.

Question 2:

In 10.3

"limit.priv" = "size=" nz-number | "total=" nz-number

;the maximum number of bytes to send in notification payloads or the total number of messages to send. Both per-day

What's the benefit of limiting the total number of messages (notifications) per-day? If the number of notifications sent that day has reached the limit (e.g. 10 notifications per-day ) but then a very important email arrives, what should the server do?

Question 3:

In 10.3:

"push.priv" = "push" / "pull"

;specifies whether the client expects new messages to be pushed via the unsolicited FETCH response defined above, or via client issued FETCH in response to an EXISTS response.

Is it possible to push new messages via outband notifications? E.g. through MMS channel. If it's possible, maybe we could define such an attribute for outband notification.

Question 4:

In 13.8

It MUST be possible to provide acknowledgment by the target to the messaging system or to repeat notification until such an acknowledgement is provided if supported by the notification channel.

Does it mean that the target (client) should provide acknowledgment for per-notification and the messaging system should repeat the same notification (not send the following notifications) until receive the acknowledgment for the notification?

If so, maybe it's more appropriate to send a notification after determining that the client is online (e.g. according to presence status of the client provided by presence enabler).

Best Regards,
Lingyan
Huawei Technologies Co., Ltd.