Re: [I2nsf] Zaheduzzaman Sarker's No Objection on draft-ietf-i2nsf-nsf-monitoring-data-model-15: (with COMMENT)

Hi Roman,
In the draft of Monitoring Interface YANG Data Model (
https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-nsf-monitoring-data-model-18#page-28
),
we don't have actions for those events (including
i2nsf-nsf-detection-voip-vocn) any more except for i2nsf-nsf-log-dpi,
but have notifications for them instead of the actions.
Note that i2nsf-nsf-log-dpi is an NSF Log with an action of logging and a
notification.

Therefore, there is no problem in the current draft.

Thanks.

Best Regards,
Paul

On Wed, May 18, 2022 at 7:07 AM Roman Danyliw <rdd@cert.org> wrote:

> Hi I2NSF WG!
>
> > -----Original Message-----
> > From: iesg <iesg-bounces@ietf.org> On Behalf Of Zaheduzzaman Sarker via
> > Datatracker
> > Sent: Wednesday, February 16, 2022 11:06 AM
> > To: The IESG <iesg@ietf.org>
> > Cc: draft-ietf-i2nsf-nsf-monitoring-data-model@ietf.org; i2nsf@ietf.org;
> > dunbar.ll@gmail.com; i2nsf-chairs@ietf.org
> > 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
> I2nsf@ietf.org
> https://www.ietf.org/mailman/listinfo/i2nsf
>