Hi I2NSF WG!

> -----Original Message-----
> From: iesg <[email protected]> On Behalf Of Zaheduzzaman Sarker via
> Datatracker
> Sent: Wednesday, February 16, 2022 11:06 AM
> To: The IESG <[email protected]>
> Cc: [email protected]; [email protected];
> [email protected]; [email protected]
> Subject: Zaheduzzaman Sarker's No Objection on draft-ietf-i2nsf-nsf-
> monitoring-data-model-15: (with COMMENT)
> 
> Zaheduzzaman Sarker has entered the following ballot position for
> draft-ietf-i2nsf-nsf-monitoring-data-model-15: 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/blog/handling-iesg-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-i2nsf-nsf-monitoring-data-model/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------

[snip]

> I am curious to know why doesn't "i2nsf-nsf-event" sub leaf "i2nsf-nsf-
> detection-voip-vocn" have a "action*" where rest of the events have actions?

I wanted to follow-up on this comment.  It seems that in -18, "action*" is now 
dropped from all "i2nsf-nsf-event" sub leafs but "i2nsf-nsf-log-dpi".  We 
appear to be in a different inconsistent situation.  Was this intention?

Regards,
Roman
_______________________________________________
I2nsf mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2nsf

Reply via email to