There seems to be a number of defects, mostly in the YANG module
- Abstract appears to contain a reference to
[I-D.ietf-netmod-revised-datastores].
-ITU-T [G.8013], MEF Service OAM, MPLS-TP [RFC6371], ...
MEF Service OAM wants a reference
- There is no note to RFC Editor asking that the date of the file name
and the Revision clause in the YANG module to be updated
- The YANG Module imports from
ietf-yang-types
ietf-inet-types
ietf-interfaces
but there is no mention of where these can be found and the relevant
RFC, perhaps 6991 for ietf-yang-types, seem not to appear in the I-D
References. (See draft-ietf-netmod-rfc7277bis or
draft-ietf-netmod-rfc8022bis for examples of how this might be handled)
"Initial revision. - 12 version";
reference "draft-ietf-lime-yang-oam-model";
I would expect this to refer to the subsequent RFC in which case it
needs a note to the RFC Editor asking them to insert the allocated
number
/This is the base identy of//This is the base identity of
'rfc6905 trill OAM'
this looks like a reference to an RFC but I see no sign of 6905 in the
References for the I-D
identity cv-defect
...........
[RFC6371] highlights, when performing ...
This looks like a reference, using XML, in the YANG module which does
not work since the YANG module will be in plain text only (but 6371 does
appear in the References of the I-D:-)
- s6.3 In the Based Mode of operation
Is this the same as the Base mode of operation
IETF XML registry [RFC3688] [RFC3688].
A duplicate reference, or a missing reference, perhaps
Tom Petch
----- Original Message -----
From: "The IESG" <iesg-secretary@xxxxxxxx>
To: "IETF-Announce" <ietf-announce@xxxxxxxx>
Cc: <bclaise@xxxxxxxxx>; <rbonica@xxxxxxxxxxx>; <lime-chairs@xxxxxxxx>;
<lime@xxxxxxxx>;
<draft-ietf-lime-yang-connection-oriented-oam-model@xxxxxxxx>
Sent: Monday, February 05, 2018 3:07 PM
The IESG has received a request from the Layer Independent OAM
Management in
the Multi-Layer Environment WG (lime) to consider the following
document: -
'Generic YANG Data Model for Connection Oriented Operations,
Administration, and Maintenance(OAM) protocols'
<draft-ietf-lime-yang-connection-oriented-oam-model-04.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
ietf@xxxxxxxx mailing lists by 2018-02-19. 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 presents a base YANG Data model for connection
oriented
OAM protocols. It provides a technology-independent abstraction of
key OAM constructs for such protocols. The model presented here
can
be extended to include technology specific details. This
guarantees
uniformity in the management of OAM protocols and provides support
for nested OAM workflows (i.e., performing OAM functions at
different
levels through a unified interface)
The YANG model in this document conforms to the Network Management
Datastore Architecture defined in
[I-D.ietf-netmod-revised-datastores].
The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connection-oriente
d-oam-model/
IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connection-oriente
d-oam-model/ballot/
No IPR declarations have been submitted directly on this I-D.
The document contains these normative downward references.
See RFC 3967 for additional information:
rfc6905: Requirements for Operations, Administration, and
Maintenance (OAM) in Transparent Interconnection of Lots of Links
(TRILL) (Informational - IETF stream)
.
