Use of Password Based Message Authentication Code 1 (PBMAC1) in PKCS #12 Syntax
draft-ietf-lamps-pkcs12-pbmac1-09

# Éric Vyncke, INT AD, comments for draft-ietf-lamps-pkcs12-pbmac1-08

Thank you for the work put into this document. As indicated below, I wonder why it is an informational only document.

Please find below some non-blocking COMMENT points (but replies would be appreciated even if only for my own education), and some nits.

Special thanks to Russ Housley for the shepherd's detailed write-up including the WG consensus *but* it lacks the justification of the intended status.

I hope that this review helps to improve the document,

Regards,

-éric


# COMMENTS (non-blocking)

## Section 3, BCP14, and intended status

There should be no such BCP14 in an informational I-D and normative language does not seem relevant in my view. The 2 RFC obsoleted by this I-D do not rely on normative language.

OTOH, this kind of document should probably be standards track as it is key for interoperation. I urge the SEC AD to upgrade the status of this document to PS even if it requires another IETF Last Call.

## Section 5

A lot of "SHOULD" without any explanation about the case when this "SHOULD" can be bypassed.

# NITS (non-blocking / cosmetic)

## Section 2

Usually, I-Ds do not use a personal tone such as `we propose`.

Thank you for this document. When I initially opened it to review, I was somewhat apprehensive - PKCS #12 and I are not friends, and this implied that I was going to endure it for ~17 pages...
and then I was pleasantly surprised to discover that 1: there is very little actual PKCS #12 involved, and 2: it's really only ~5 pages of text, and the rest is test vectors (which I'll happily admit I just ignored :-))