Re: Last Call: <draft-ietf-lime-yang-connection-oriented-oam-model-04.txt> (Generic YANG Data Model for Connection Oriented Operations, Administration, and Maintenance(OAM) protocols) to Proposed Standard

["tom p." <[e-mail]>]

----- Original Message -----
From: "Qin Wu" <[e-mail]>
Sent: Friday, February 23, 2018 12:00 PM


> -----邮件原件-----
> 发件人: tom p. [mailto:[e-mail]]
> 发送时间: 2018年2月23日 19:42
> 收件人: Qin Wu; ietf
>
> ----- Original Message -----
> From: "Qin Wu" <[e-mail]>
> Sent: Thursday, February 22, 2018 3:00 AM
>
> > Thanks Tom, please see my reply inline below.
>
> Looks good.
>
> I still see
>  ...  [RFC6371] highlights   ...
> which looks to me like an XML/HTML style of reference from within the
YANG module which does not work since the YANG module has to work as
plain text.  Yes, the reference clause is now there, which is good, but
I think that the [RFC6371] needs removing if it is what I suspect that
it is.
>
> And I always like the RFC Editor to have an easy time and so include a
note asking them to replace the xxxx.  I like the way that
draft-ietf-softwire-dslite-yang does this.
>
> [Qin]: Note that I had added a explicit reference under that
description within the YANG module in v-06 as follows:
> "
>     reference
>       "RFC 6371: Operations, Administration, and Maintenance
>        Framework for MPLS-Based Transport Networks";
> "
> So it is not XML/HTML style any more. :-)

But look just above that, as in the extract below,  and  I see [RFC6371]
which still looks like an XML/HTML style reference from within the YANG
module.

identity cv-defect {
    base defect-types;
    description
      "This function should support monitoring between
       the Maintenance End Points (MEPs) and,
       in addition, between a MEP and Maintenance Intermediate
       Point (MIP). [RFC6371] highlights ....

Tom Petch


> > -----邮件原件-----
> > 发件人: tom p. [mailto:[e-mail]]
> > 发送时间: 2018年2月14日 23:45
> > 收件人: ietf
> > 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].
> >
> > [Qin]: Fixed.
> >
> > -ITU-T [G.8013], MEF Service OAM, MPLS-TP [RFC6371], ...
> > MEF Service OAM wants a reference
> >
> > [Qin]:Fixed.
> >
> > - 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)
> >
> > [Qin]: Thanks, fixed.
> >
> > "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
> >
> > [Qin]: Good catch, fixed.
> >
> > /This is the base identy of//This is the base identity of
> >
> > [Qin]:Fixed.
> > '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
> >
> > [Qin]: Will add reference to RFC6905.
> >  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:-)
> >
> > [Qin]: Will add reference to RFC6371.
> >
> > - s6.3 In the Based Mode of operation
> > Is this the same as the Base mode of operation
> >
> > [Qin]: It is typo, thanks, fixed.
> > IETF XML registry [RFC3688] [RFC3688].
> > A duplicate reference, or a missing reference, perhaps
> >
> > [Qin]:Fixed.
> >
> > Tom Petch
> >
> > ----- Original Message -----
> > From: "The IESG" <[e-mail]>
> > To: "IETF-Announce" <[e-mail]>
> > Cc: <[e-mail]>; <[e-mail]>;
> <[e-mail]>; <[e-mail]>;
<[e-mail]>
> > 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
> > > [e-mail] mailing lists by 2018-02-19. Exceptionally, comments
> may
> > be
> > > sent to [e-mail] 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)
> > >
> > >
> > >
> >
> >
>
>