[pkix] [Technical Errata Reported] RFC3161 (1879)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 15 September 2009 11:16 UTC
Return-Path: <web-usrn@ISI.EDU>
X-Original-To: pkix@core3.amsl.com
Delivered-To: pkix@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E47863A6A04 for <pkix@core3.amsl.com>; Tue, 15 Sep 2009 04:16:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.872
X-Spam-Level:
X-Spam-Status: No, score=-16.872 tagged_above=-999 required=5 tests=[AWL=0.727, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lKnUZnr2EKtR for <pkix@core3.amsl.com>; Tue, 15 Sep 2009 04:16:27 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 0CED03A67B7 for <pkix@ietf.org>; Tue, 15 Sep 2009 04:16:27 -0700 (PDT)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n8FBFYJh002467; Tue, 15 Sep 2009 04:15:35 -0700 (PDT)
Received: (from web-usrn@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id n8FBFUMn002431; Tue, 15 Sep 2009 04:15:30 -0700 (PDT)
Date: Tue, 15 Sep 2009 04:15:30 -0700
Message-Id: <200909151115.n8FBFUMn002431@boreas.isi.edu>
To: cadams@entrust.com, pcain@bbn.com, Denis.Pinkas@bull.net, robert.zuccherato@entrust.com, tim.polk@nist.gov, pasi.eronen@nokia.com, kent@bbn.com, stefan@aaa-sec.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: web-usrn@boreas.isi.edu
X-Mailman-Approved-At: Tue, 15 Sep 2009 04:53:38 -0700
Cc: nick.pope@thales-esecurity.com, rfc-editor@rfc-editor.org, pkix@ietf.org
Subject: [pkix] [Technical Errata Reported] RFC3161 (1879)
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pkix>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Sep 2009 11:16:28 -0000
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 <nick.pope@thales-esecurity.com> 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
- [pkix] [Technical Errata Reported] RFC3161 (1879) RFC Errata System