The following errata report has been submitted for RFC5479,
"Requirements and Analysis of Media Security Management Protocols".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5479&eid=2122

--------------------------------------
Type: Editorial
Reported by: Alfred Hoenes <a...@tr-sys.de>

Section: App. A

Original Text
-------------
[[ second-to-last paragraph, on mid-page 24: ]]

   Related to SRTP's characteristics is a goal that any SRTP keying
|  mechanism to also be efficient and not cause additional call setup
   delay.

Corrected Text
--------------
   Related to SRTP's characteristics is a goal that any SRTP keying
|  mechanism also be efficient and not cause additional call setup
   delay.

Notes
-----
Rationale: language/grammar improvement -- keep for update!

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC5479 (draft-ietf-sip-media-security-requirements-09)
--------------------------------------
Title               : Requirements and Analysis of Media Security Management 
Protocols
Publication Date    : April 2009
Author(s)           : D. Wing, Ed., S. Fries, H. Tschofenig, F. Audet
Category            : INFORMATIONAL
Source              : Session Initiation Protocol
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is essentially closed and only used for finishing old business.
Use sip-implement...@cs.columbia.edu for questions on how to develop a SIP 
implementation.
Use dispa...@ietf.org for new developments on the application of sip.
Use sipc...@ietf.org for issues related to maintenance of the core SIP 
specifications.

Reply via email to