Technical issues:
What if both Suppress-Body-If-Match and SuppressN-Notify-If-Match are
specified? We probably don't really care, but the document should
make it clear if the combination is standardized or not.
The entity-tag values for a single resource are the same across
subscriptions, but it is not clear whether they are in some sense the
same between subscriptions for different resources, or for different
resource-IDs that refer to "the same" underlying resource. This may
have significance for renewed subscriptions whose initial requests are
sent to the same resource AOR but which are ultimately routed to
different but "equivalent" resource-IDs.
Nits:
Section 2.2
o Relatively low rate of actual notifications triggered by actual
state changes
Better phrased "Relatively low rate of notifications triggered by
state changes".
Section 3:
The entity-tag header is "SIP-ETag", but the "SIP-" portion is
redundant. I suppose it's too late to change it to just "ETag".
Sections 3 and 4.2:
"two types of Xs" is better phrased "two Xs".
Section 4.5:
2. If the condition evaluates to true, the notifier sends a 204 (No
Notification) response sends no NOTIFY request.
Should be "sends a 204 (No Notification) response and sends no NOTIFY
request.
Section 5.1:
The notifier is free to decide the means for generating an
entity-tag, except for the special "*" value.
Better phrased "free to decide how to generate the entity-tag values,
except that no entity-tag may be the special "*" value."
Section 5.3:
the notifier MUST suppress the resulting NOTIFY request, and
generate a 204 (No Notification) "No Notification" response.
Should be "a 204 (No Notification) response".
Sections 8.3 and 8.4:
This document registers two new SIP header field names. These
headers are defined by the following information, which has been
added to the header fields sub-registry under
http://www.iana.org/assignments/sip-parameters.
This paragraph is duplicated, and it appears to be addressing both
header registrations together, rather than either one alone.
Dale
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
