Re: [Pce] I-D Action: draft-ietf-pce-pcep-yang-09.txt

[tom petch <[e-mail]>]

---- Original Message -----
From: "Dhruv Dhody" <[e-mail]>
Sent: Monday, October 15, 2018 2:14 PM

> The changes in this update are -
>
> - Use of identity instead of typedef for lsp-error
> - Reusing PST, Objective function, association-types from the te-types
> - Update to PCEP-SR as per the SR capability TLV
> - Simplification of key (as done by other yang models)
> - Alignment to explicit-route-hop in te-types
>
> The draft does not have any other pending actions.

Mmm why can I not resist the challenge?

You say
   RFC Ed.: In this section, replace all occurrences of 'XXXX' with the
   actual RFC number ...
and then
    import ietf-te {    prefix "te";    reference "RFC XXXX";    }
    import ietf-te-types {     prefix "te-types";    reference "RFC
XXXX";
    import ietf-tls-server {   prefix "tls-server";    reference "RFC
XXXX";   }
    import ietf-tls-client {    prefix "tls-client";     reference "RFC
XXXX";

Mmm I think not!

And, I like all the references in the YANG module but they need to be in
the references of the I-D.  I think you are missing

3209
5088
5089
5520
5541
5557
6536
8232
8306

while
8253
is there but Informative; my preference is for such references to be
Normative.

A common practice is to have a section just prior to the module proper
which gives references to all the RFC which the module references, which
obviates the appearance of warnings about  'Unused Reference'.

Tom Petch


> Dhruv
> PS. The yang errors in the datatracker are in the imported yang
modules.
>
> On Mon, Oct 15, 2018 at 6:32 PM <[e-mail]> wrote:
>
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> > This draft is a work item of the Path Computation Element WG of the
IETF.
> >
> >         Title           : A YANG Data Model for Path Computation
Element
> > Communications Protocol (PCEP)
> >         Authors         : Dhruv Dhody
> >                           Jonathan Hardwick
> >                           Vishnu Pavan Beeram
> >                           Jeff Tantsura
> >         Filename        : draft-ietf-pce-pcep-yang-09.txt
> >         Pages           : 116
> >         Date            : 2018-10-15
> >
> > Abstract:
> >    This document defines a YANG data model for the management of
Path
> >    Computation Element communications Protocol (PCEP) for
communications
> >    between a Path Computation Client (PCC) and a Path Computation
> >    Element (PCE), or between two PCEs.  The data model includes
> >    configuration data and state data (status information and
counters
> >    for the collection of statistics).
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-yang/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-ietf-pce-pcep-yang-09
> > https://datatracker.ietf.org/doc/html/draft-ietf-pce-pcep-yang-09
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-pcep-yang-09
> >
> >
> > 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/
> >