Hi,

I reviewed the document. Please find my comments below.

Yours,
Daniel



   Metadata:  Data that provides information about other data.

MGLT: This is actually how metadata is defined. However, it might be usefull
to provide an example, or conplete the definition. I an also wondering if
I2NSF only defines metadata associated to YANG models. If so woudl it be
relevant to mention RFC7952 ? The examples do not seem to ilustrate what
metadata is, instead they mention protocols that use YANG for which metadta
is defined.

      Examples include IETF network management protocols (e.g.  NETCONF,
      RESTCONF, IPFIX) or IETF routing interfaces (I2RS).  The I2NSF
      security interface may utilize Metadata to describe and/or
      prescribe characteristics and behavior of the YANG data models.


   Network Security Function (NSF):  Software that provides a set of
      security-related services.  Examples include detecting unwanted
      activity and blocking or mitigating the effect of such unwanted
      activity in order to fulfil service requirements.  The NSF can
      also help in supporting communication stream integrity and
      confidentiality.

MGLT: It is not clear to me the relation between function and service. My
understanding is that service may involve multiple functions. But I believe
it would be helpful to position these two concepts - at least in this
definition.


   Producer:  A Producer is a Role that is assigned to an I2NSF
      Component that can send information and/or commands to another
      I2NSF Component.  See also: Consumer, Role.

MGLT: Is Producer equivalent to provider ? If so maybe that would hepl to
use a single designation.





On Sun, Oct 23, 2016 at 9:44 PM, <[email protected]> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Interface to Network Security Functions
> of the IETF.
>
>         Title           : Interface to Network Security Functions (I2NSF)
> Terminology
>         Authors         : Susan Hares
>                           John Strassner
>                           Diego R. Lopez
>                           Liang Xia
>                           Henk Birkholz
>         Filename        : draft-ietf-i2nsf-terminology-02.txt
>         Pages           : 13
>         Date            : 2016-10-23
>
> Abstract:
>    This document defines a set of terms that are used for the Interface
>    to Network Security Functions (I2NSF) effort.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-i2nsf-terminology/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-i2nsf-terminology-02
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-i2nsf-terminology-02
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I2nsf mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/i2nsf
>
_______________________________________________
I2nsf mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2nsf

Reply via email to