Subject: [pkix] [Technical Errata Reported] RFC3161 (1879)

From: RFC Errata System <[email-masked]>
Date: Tue, 15 Sep 2009 04:15:30 -0700 (PDT)

The following errata report has been submitted for RFC3161,
"Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)".

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

--------------------------------------
Type: Technical
Reported by: Nick Pope <[email-masked]>

Section: 3.6

Original Text
-------------
Upon receiving a valid request, the server MUST respond with either a valid response with content type application/timestamp-response or with an HTTP error.

Corrected Text
--------------
Upon receiving a valid request, the server MUST respond with either a valid response with content type application/timestamp-reply or with an HTTP error.

Notes
-----
"application/timestamp-reply" are used in the rest parts of RFC 3161 (4 occurencies).  Furthermore, known existing implementations are using 
"application/timestamp-reply".

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. 

--------------------------------------
RFC3161 (draft-ietf-pkix-time-stamp-15)
--------------------------------------
Title               : Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)
Publication Date    : August 2001
Author(s)           : C. Adams, P. Cain, D. Pinkas, R. Zuccherato
Category            : PROPOSED STANDARD
Source              : Public-Key Infrastructure (X.509)
Area                : Security
Stream              : IETF
Verifying Party     : IESG