Hi Susan,

> I2RS is specified to have data which is just ephemeral state.

Missed that part. So basically you only need to address comment one and mention 
that.

Thanks,
Mirja


> Am 24.10.2016 um 13:15 schrieb Susan Hares <[email protected]>:
> 
> Mirja: 
> 
> 
> 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.
> 
> I will add a few sentences to 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?
> 
> All of these requirements are required in order to do ephemeral state.   I2RS 
> is specified to have data which is just ephemeral state.  So... I'm not sure 
> what the question is. 
> 
> Sue 
> 
> -----Original Message-----
> From: Mirja Kuehlewind [mailto:[email protected]] 
> Sent: Monday, October 24, 2016 6:32 AM
> To: The IESG
> Cc: [email protected]; Joe Clarke; 
> [email protected]; [email protected]; [email protected]
> Subject: Mirja Kühlewind's No Objection on 
> draft-ietf-i2rs-ephemeral-state-19: (with COMMENT)
> 
> 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?
> 
> 
> 

_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs

Reply via email to