Francesca Palombini has entered the following ballot position for
draft-ietf-emu-aka-pfs-11: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to 
https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-emu-aka-pfs/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for the work on this document.

Many thanks to Sean Turner for his ART ART review:
https://mailarchive.ietf.org/arch/msg/art/Aua-Uh5CRr9oDEIanfD6qw8WqVM/.

I only have two very minor comments.

Section 6.1: AT_PUB_ECDHE. The way Length is defined in RFC4187 (specifying the
length of the attribute in multiple of 4 bytes), and given the length of the
ECDHE public key in the attribute value (currently 32 or 33 bytes), you
probably should mention something about padding. I expect something analogous
to what RFC4187 defines for AT_IDENTITY "Because the length of the attribute
must be a multiple of 4 bytes, the sender pads the identity with zero bytes
when necessary."

Section 8: IANA Considerations. The section doesn't spell out the fields of the
"EAP-AKA' AT_KDF_FS Key Derivation Function Values" registry (Value,
Description, Reference), although those are pretty obvious from the table
itself. What I think is really missing is the expert guidelines - as RFC8126
specifies, the policy "Specification required" still requires review and
approval by a designated expert. "As with Expert Review, clear guidance to the
designated expert should be provided when defining the registry". What criteria
is the expert supposed to base their decision on when deciding if a new value
should be registered?



_______________________________________________
Emu mailing list
Emu@ietf.org
https://www.ietf.org/mailman/listinfo/emu

Reply via email to