Re: [pkix] New draft-ietf-pkix-rfc2560bis-06

mrex@sap.com (Martin Rex) Tue, 23 October 2012 10:50 UTC

Return-Path: <mrex@sap.com>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16CE321F86D0 for <pkix@ietfa.amsl.com>; Tue, 23 Oct 2012 03:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.209
X-Spam-Level:
X-Spam-Status: No, score=-10.209 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uTVv170RmGJQ for <pkix@ietfa.amsl.com>; Tue, 23 Oct 2012 03:50:31 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 49ECD21F86CB for <pkix@ietf.org>; Tue, 23 Oct 2012 03:50:30 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q9NAoNrg017498 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 23 Oct 2012 12:50:24 +0200 (MEST)
In-Reply-To: <CA+i=0E7cXwWWGeQCKO-wVCvYYXxme4+z9DqbD0Wrip76CZVRvA@mail.gmail.com>
To: Erwann Abalea <eabalea@gmail.com>
Date: Tue, 23 Oct 2012 12:50:23 +0200
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20121023105023.569FB1A2EE@ld9781.wdf.sap.corp>
From: mrex@sap.com
X-SAP: out
Cc: pkix@ietf.org
Subject: Re: [pkix] New draft-ietf-pkix-rfc2560bis-06
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 23 Oct 2012 10:50:32 -0000

Erwann Abalea wrote:
> 
> RFC5280 doesn't say anything about the meaning of revocation reason codes.
> X.509 do, in 8.5.2.2:
> "A certificate may be placed on hold by issuing a CRL entry with a reason
> code of certificateHold. The certificate hold
> notice may include an optional hold instruction code to convey additional
> information to certificate users (see 8.5.2.3)."

Now you're kidding me.

We're talking about the semantics of the "certificateHold" status.
A protocol element without semantics would be utterly useless.

And the text that you quote gives a STRONG HINT that this status
was intended to have a rather broad meaning, and not only the
narrow meaning of two specific usage cases that you mentioned
(token lost, or new token in the mail).

-Martin