Subject: [Simple] comments on draft-ietf-simple-xcap-package-01

From: [email-masked]
Date: Sun, 29 Feb 2004 09:24:44 +0200

- Section 2.2 has an open issue about how to specify that a subscription is to multiple documents. Can this be done with multiple doc-component params or one doc-component param with comma separated values?

- Section 2.3 talks about filters. That's Ok. But I don't feel comfortable about this draft specifying that honouring of the filter is at the policy discretion of the notifier (even though I agree with that, I feel it is not the place for this draft to say that).

- Section 2.5 has an open issue about what to represent in a NOTIFY. I think I already indicated earlier my feelings about this one. I prefer option 2 where the NOTIFY carries the actual change that was made to the document.

- Section 2.6: Why is HTTP digest support a MUST? The text says: A notifier of this package SHOULD authenticate all subscribers. I believe that is enough. Mandating an authentication mechanism is too strong here. There are other authentication mechanisms than http digest.

- Section 2.7: It is defined in another section that a subscribe request can be to on element. Yet, this section says that that hash is for the whole XML document. Was that intentional?

- Section 2.7 talks about document version. Is it talking about etags? If so, then use the term etag instead of version. I was confused when I read "Notifications sent in response to SUBSCRIBE requests (either initial or refresh) or sent when there is a change in subscription state, will normally only contain the current version of the XML document being subscribed to". this to me sound like the document needs to be in the NOTIFY.

- Section 2.8 reads "When a client receives a notification, it checks the version against which the changes are relative". What does that mean? should it say "against the locally stored version"? Again, here the use of the word version is confusing. Version number or etag is better.

- Section 2.8: reading about the version thing further, I get more confused. If the version is different, then the client SHOULD use XCAP to fetch the latest, but if the version is the same, then the client applies the changes to its local cache. Why would there be changes in the version is the same? when does a version change. Maybe I don't understand what version means in this context.

What I understand is: If there is a change, the client gets a new etag. if there is no change, the client does not get a NOTIFY at all unless it is in response to a SUBSCRIBE request, in which case the etag is not changed which means there is no change to the document.

- Section 3: the <documents> element has 0 or more <document> sub-elements which carry the changes in a document. But what if the subscription was for an element? It might be ok like this, but the <change> text must only be for that element that the subscription was for.

- Section 3: <change> element contains the exact value present in the HTTP request that caused that change. It is worth noting here that if the HTTP request was a DELETE, then the <change> element is empty.

Regards,
Hisham

_______________________________________________
Simple mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/simple