ASN.1 OID for TIGER/192

David Shaw <> Fri, 27 September 2002 13:05 UTC

Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id JAA19132 for <>; Fri, 27 Sep 2002 09:05:17 -0400 (EDT)
Received: (from majordomo@localhost) by (8.11.6/8.11.3) id g8RCtsT01321 for ietf-openpgp-bks; Fri, 27 Sep 2002 05:55:54 -0700 (PDT)
Received: from ( []) by (8.11.6/8.11.3) with ESMTP id g8RCtrv01316 for <>; Fri, 27 Sep 2002 05:55:53 -0700 (PDT)
Received: (from dshaw@localhost) by (8.11.6/8.11.6) id g8RCtoI14105 for; Fri, 27 Sep 2002 08:55:50 -0400
Date: Fri, 27 Sep 2002 08:55:50 -0400
From: David Shaw <>
Subject: ASN.1 OID for TIGER/192
Message-ID: <>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-PGP-Key: 99242560 / 7D92 FD31 3AB6 F373 4CC5 9CA1 DB69 8D71 9924 2560
User-Agent: Mutt/1.5.1i
Precedence: bulk
List-Archive: <>
List-Unsubscribe: <>
List-ID: <>


In 2440 and in all the 2440bis drafts, the TIGER/192 hash is not fully
usable as it has no OID.  Werner Koch and I, with the cooperation of
TIGER's authors, recently arranged an OID for it:

It would be good to put this in 2440bis so TIGER will be usable.

I have a sneaking suspicion that this may raise the question whether
TIGER should be in the standard at all, as so long as it did not have
an OID, the question was moot.  I have no strong feelings on this
point, but if we are not going to allow the use of TIGER, then perhaps
we should remove it from the standard altogether or explicitly
disallow its use as the current halfway state is confusing now that
there is an OID available.


   David Shaw  |  |  WWW
   "There are two major products that come out of Berkeley: LSD and UNIX.
      We don't believe this to be a coincidence." - Jeremy S. Anderson