RFC Errata System
2010-04-05 17:56:55 UTC
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=2123
--------------------------------------
Type: Editorial
Reported by: Alfred Hoenes <***@TR-Sys.de>
Section: A.1.7
Original Text
-------------
[[ second paragraph: ]]
With this proposal, the ECDSA signature, MIKEY-ECIES, and MIKEY-ECMQV
| function exactly like MIKEY-RSA, and the new DH-Group code function
exactly like MIKEY-DHSIGN. Therefore, these ECC mechanisms are not
discussed separately in this document.
Corrected Text
--------------
With this proposal, the ECDSA signature, MIKEY-ECIES, and MIKEY-ECMQV
| function exactly like MIKEY-RSA, and the new DH-Group code functions
exactly like MIKEY-DHSIGN. Therefore, these ECC mechanisms are not
discussed separately in this document.
Notes
-----
Rationale: singular/plural mismatch -- 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-***@cs.columbia.edu for questions on how to develop a SIP implementation.
Use ***@ietf.org for new developments on the application of sip.
Use ***@ietf.org for issues related to maintenance of the core SIP specifications.
"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=2123
--------------------------------------
Type: Editorial
Reported by: Alfred Hoenes <***@TR-Sys.de>
Section: A.1.7
Original Text
-------------
[[ second paragraph: ]]
With this proposal, the ECDSA signature, MIKEY-ECIES, and MIKEY-ECMQV
| function exactly like MIKEY-RSA, and the new DH-Group code function
exactly like MIKEY-DHSIGN. Therefore, these ECC mechanisms are not
discussed separately in this document.
Corrected Text
--------------
With this proposal, the ECDSA signature, MIKEY-ECIES, and MIKEY-ECMQV
| function exactly like MIKEY-RSA, and the new DH-Group code functions
exactly like MIKEY-DHSIGN. Therefore, these ECC mechanisms are not
discussed separately in this document.
Notes
-----
Rationale: singular/plural mismatch -- 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-***@cs.columbia.edu for questions on how to develop a SIP implementation.
Use ***@ietf.org for new developments on the application of sip.
Use ***@ietf.org for issues related to maintenance of the core SIP specifications.