RFC Errata System
2011-10-10 19:00:13 UTC
The following errata report has been submitted for RFC6072,
"Certificate Management Service for the Session Initiation Protocol (SIP)".
--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6072&eid=2988
--------------------------------------
Type: Editorial
Reported by: Olle E. Johansson <***@edvina.net>
Section: 8
Original Text
-------------
The [RFC4474] authentication service defined a signature algorithm
based on SHA-1 called rsa-sha1. This specification adds a signature
algorithm that is roughly the same but based on SHA-256 and called
rsa-sha256.
Corrected Text
--------------
The [RFC4474] authentication service defined a signature algorithm
based on SHA-1 called rsa-sha1. This specification adds a signature
algorithm that is roughly the same but based on SHA-256 and called
rsa-sha256. This is an update of RFC 4474.
Notes
-----
The Masthead doesn't indicate clearly that this RFC updates 4474 and thus the IETF tools web site doesn't indicate that 4474 is updated.
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.
--------------------------------------
RFC6072 (draft-ietf-sip-certs-15)
--------------------------------------
Title : Certificate Management Service for the Session Initiation Protocol (SIP)
Publication Date : February 2011
Author(s) : C. Jennings, J. Fischl, Ed.
Category : PROPOSED STANDARD
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.
"Certificate Management Service for the Session Initiation Protocol (SIP)".
--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6072&eid=2988
--------------------------------------
Type: Editorial
Reported by: Olle E. Johansson <***@edvina.net>
Section: 8
Original Text
-------------
The [RFC4474] authentication service defined a signature algorithm
based on SHA-1 called rsa-sha1. This specification adds a signature
algorithm that is roughly the same but based on SHA-256 and called
rsa-sha256.
Corrected Text
--------------
The [RFC4474] authentication service defined a signature algorithm
based on SHA-1 called rsa-sha1. This specification adds a signature
algorithm that is roughly the same but based on SHA-256 and called
rsa-sha256. This is an update of RFC 4474.
Notes
-----
The Masthead doesn't indicate clearly that this RFC updates 4474 and thus the IETF tools web site doesn't indicate that 4474 is updated.
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.
--------------------------------------
RFC6072 (draft-ietf-sip-certs-15)
--------------------------------------
Title : Certificate Management Service for the Session Initiation Protocol (SIP)
Publication Date : February 2011
Author(s) : C. Jennings, J. Fischl, Ed.
Category : PROPOSED STANDARD
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.