[i2rs] Mirja Kühlewind's No Objection on draft-ietf-i2rs-ephemeral-state-19: (with COMMENT)

["Mirja Kuehlewind" <[e-mail]>]

Mirja Kühlewind has entered the following ballot position for
draft-ietf-i2rs-ephemeral-state-19: 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/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-i2rs-ephemeral-state/



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

Two comments:

1) "I2RS requires ephemeral state; i.e. state that does
   not persist across reboots." -> why? Maybe add 1-2 sentences about the
use (case) in the introduction.

2) Are all these requirements specific to ephemeral state? I would assume
that some requirements are more general, e.g. don't you need priorities
also for all other state updates?