So, it looks like MD5 and HMAC are "Other Specifications" for
which the IESG has requested to be published as Informational RFCs
such that they can be referenced by Standard Track specifications
(per RFC 2026 7.1.2). I found references to this affect in
the minutes of the IESG (excerpts provided below).
With MD5/HMAC, I assumed something like this would be the case.
I'll have to go through the other Informational RFC references
I found in the LDAP (and dependent) specifications to see if
they also fall within this category.
Kurt
----
IESG, 92-03-26, 3.6.
Several Security related protocols reference the MD2 and MD5 Message
Digest Algorithms. These algorithms are documented in Internet
Drafts that should be published as informational RFC's.
IESG, 96-09-19, 2.
The IESG approved publication of IMAP/POP AUTHorize Extension for
Simple Challenge/Response <draft-klensin-cram-02.txt> as a Proposed
Standard. However, as it is dependent on HMAC-IP Authentication
with Replay Prevention <draft-ietf-ipsec-hmac-md5-00.txt>, the
announcement will not be sent until the hmac document is approved.
IESG, 96-11-21, 15.
The IESG approved publication of HMAC: Keyed-Hashing for Message
Authentication <draft-ietf-ipsec-hmac-md5-01.txt> as an
Informational RFC. Steve to send announcement.
With the approval of the above, the announcement of the IESG's
approval of the Klensin-cram document may also be sent (approved in
September).