Looking at the YANG:
RFC4443 is referenced and so must be in the I-D References
RFC790 is referenced but this is now online under IANA - you can see the
IANA reference in
draft-ietf-i2nsf-sdn-ipsec-flow-protection-08
but that I-D needs to add it to the I-D references as this one will need
to; I note that this announcement flags it as a downref but think that
that is misguided - it needs replacing.
IPsec is the correct spelling - there are some IPSec in YANG
description clauses
Figure 8
2. The location of the NSF is 221.159.112.140.
This address does not appear in the XML, nor is it an address reserved
for use in documentation AFAICT; in fact, I cannot see any ipaddress
anywhere in this I-D
s.2 correctly cites RFC8174 but does not use the text prescribed there.
' identity system-event-capability'
references system-alarm - system event would seem more apt. More
generally, these references for identity could be more specific, e.g
identity access-violation
could reference 'access-violation ' rather than the more generic 'system
event'
Tom Petch
----- Original Message -----
From: "The IESG" <iesg-secretary@xxxxxxxx>
To: "IETF-Announce" <ietf-announce@xxxxxxxx>
Cc: <rdd@xxxxxxxx>; <i2nsf@xxxxxxxx>;
<draft-ietf-i2nsf-capability-data-model@xxxxxxxx>;
<i2nsf-chairs@xxxxxxxx>; "Linda Dunbar" <dunbar.ll@xxxxxxxxx>
Sent: Tuesday, August 25, 2020 6:59 PM
The IESG has received a request from the Interface to Network Security
Functions WG (i2nsf) to consider the following document: - 'I2NSF
Capability
YANG Data Model'
<draft-ietf-i2nsf-capability-data-model-08.txt> as Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits
final
comments on this action. Please send substantive comments to the
last-call@xxxxxxxx mailing lists by 2020-09-08. Exceptionally,
comments may
be sent to iesg@xxxxxxxx instead. In either case, please retain the
beginning
of the Subject line to allow automated sorting.
Abstract
This document defines a YANG data model for the capabilities of
various Network Security Functions (NSFs) in the Interface to
Network
Security Functions (I2NSF) framework to centrally manage the
capabilities of the various NSFs.
The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-i2nsf-capability-data-model/
The following IPR Declarations may be related to this I-D:
https://datatracker.ietf.org/ipr/3556/
https://datatracker.ietf.org/ipr/3606/
The document contains these normative downward references.
See RFC 3967 for additional information:
rfc8329: Framework for Interface to Network Security Functions
(Informational - IETF stream)
rfc8192: Interface to Network Security Functions (I2NSF): Problem
Statement and Use Cases (Informational - IETF stream)
rfc790: Assigned numbers (Historic - Legacy stream)
rfc3444: On the Difference between Information Models and Data
Models (Informational - IETF stream)
draft-ietf-i2nsf-nsf-monitoring-data-model: I2NSF NSF Monitoring
YANG Data Model (None - IETF stream)
_______________________________________________
IETF-Announce mailing list
IETF-Announce@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf-announce
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
