Please see attached review.
I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft (for background on Gen-ART, please see
http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
Please wait for direction from your document shepherd
or AD before posting a new version of the draft.
Document: draft-ietf-sieve-notify-sip-message-05.txt
Reviewer: Brian Carpenter
Review Date: 2011-10-04
IETF LC End Date: 2011-10-05
IESG Telechat date: 2011-10-06
Summary: Almost Ready
--------
Minor issue:
------------
I was briefly confused by Section 2.4. (Notify tag ":importance")
It only mentions three possible values of "Priority" but RFC 3261
mentions four (the extra one is "emergency") and states that
"additional values can be defined elsewhere." I think it should be
noted that the :importance tag can only express a subset of the SIP
Priority header semantics, and does not provide a separate category
for "when life, limb, or property are in imminent danger" [RFC3261].
I realise that the direction of translation is Sieve --> SIP
but one tends to expect symmetry.
Proposal by Barry Leiba to fix this (not in -05 version):
New text of section 2.4:
The ":importance" tag is intended to convey the importance of the
SIP MESSAGE notification, not the importance of the email message
that generated the notification.
The value of the ":importance" tag MAY, therefore, be transformed into SIP
"Priority" header field (in addition to or instead of including it in the
body of the message).
Note that because the Sieve ":importance" tag only has three values,
not all SIP "Priority" values can be represented in the transformation.
If this transformation is done, the value of the "Priority" header field MUST
be
"urgent" if the value of the ":importance" tag is "1",
"normal" if the value of the ":importance" tag is "2",
and "non-urgent" if the value of the ":importance" tag is "3".
There is no mapping to the SIP value "emergency", nor to any additional values
that might be defined.
_______________________________________________
Gen-art mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/gen-art
