Subject: [siprec] IESG review for requirement draft - ver 11

From: Leon Portman <[email-masked]>
Date: Sun, 29 May 2011 16:28:37 +0300

Hello

Please see below list of main changes following IESG review. We need to receive comments or objection as fast as possible.

1.       Removed REQ-25 because it is confusing and does not provide any specific requirements for RS and CS keys relationship (all configurations should be supported). It is too solution oriented.  REQ-31 is generic enough for ensuring RS confidentiality.

2.       Added text to REQ-017 in order to cover also how UA will know regarding success of failure of recording preferences requests:

REQ-017: The mechanism MUST support a means for a recording-aware UA involved

                in a CS to request during a session that the recording of the CS  should be started,

                paused, resumed or stopped, the honoring of such a request being dependent on policy.

                Such recording-aware UA MUST be notified about outcome of such requests.

3.       Removed "non-repudiation" examples from "Privacy Consideration" and "Security Considerations" sections, because it is not clear what are specific requirements.

4.       Removed second "integrity" from the last paragraph of "Security Considerations" section in order to remove confusion that we are talking about protection of SRC and not data on the wire.

5.       Minor rephrase of  a paragraph in "Introduction"  (starting with "Furthemore..")

6.        REQ-005 - Add reference to RS in loss of media sentence

7.       REQ-012 - change "indentities" to " identifiers "

8.       Added RFC 4949 reference for security considerations

9.       Added timelines to figures

Attached updated draft ver-11

Leon