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

Dhruv Dhody <dhruv.ietf@gmail.com> Sun, 24 March 2019 21:08 UTC

Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDE4A120100 for <pce@ietfa.amsl.com>; Sun, 24 Mar 2019 14:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i5ejakoZ_F46 for <pce@ietfa.amsl.com>; Sun, 24 Mar 2019 14:08:48 -0700 (PDT)
Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DFE4120106 for <pce@ietf.org>; Sun, 24 Mar 2019 14:08:48 -0700 (PDT)
Received: by mail-io1-xd35.google.com with SMTP id v4so6017672ioj.5 for <pce@ietf.org>; Sun, 24 Mar 2019 14:08:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZAoe88n2DwoNm2s5D6dr0JFJzP1SNPB51oDIHIrlAuw=; b=QB0h8mGzjHpaZCAH5uTigeP8XbA8jQpnYzLIAPcaAy7TVhkv9zC673KJRmQPFitF5A UbD4MA7TI5c9KDE0B+1ipHoJ3ub3hzrAQGqV1ujpsw/mIMfEaEGgooEf0voWfTBxACgE EQiGvNVUv/ob4MpQyUV03UnM+xf9WV+6zNGoKSq0R2xVVuBXQlXhqX3U/rY0Buz41/KI EJo0XDDgn/xILkAmgk4zxoFjVryh/oYoE8oH2859gQrFDUqh4XgO9KR2LQmdoXlyBQuW feKDghjxAWtccJ0xLCf4B1uOyjve1MxPMXQcihEw/nVEePioQTHpkmVORRNTTtLEfw01 7qJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZAoe88n2DwoNm2s5D6dr0JFJzP1SNPB51oDIHIrlAuw=; b=oKpZpUFeWafFcTJ1GikM57t8HOJ/gAW7sKQFFjAJtEWPOju8QXQwXiadyEikDlsOZ0 0wP1ESdUzBshxDz2QPPmIAUns/OzCxFlEVRugQhLq0+2a3wxoFc0mnq+PnviI4oRY35G 4e2hGPOIr9INLCbpIXOrteiVJLF124+vUCqOtAjg6eiBBtq7w7kxJ1G4S5uz814a2dqV M+f9aE6sl3VObcB8psaHbFJo+Ona001zQ5KUzcIwCwdIgH5znNEg+lcUHPed5KbsIuiF UOVnMwoXmG9C025VJCwaJV0y9PwNuTc5UfGByYRlcuHNUSbL/jX1l9fbuDwTvOIaXCbo Bdrg==
X-Gm-Message-State: APjAAAW3hZTWNAAGPoVbgfJ+ot3VLbjzjamq87cifsRpuRF/chOd9sus NaJZXqCBAHuHrK9pMidV5XH0QQTHc7RpnabfRuI=
X-Google-Smtp-Source: APXvYqwGd5UwfLGKzRyOec4QKQtHVXeMG1FFlFseg+uR3/O16vcivy0QwnVBE8z2Q83Ow1MrhopH8UgYbnNTQOEyMwQ=
X-Received: by 2002:a6b:3ec3:: with SMTP id l186mr13752820ioa.255.1553461727693; Sun, 24 Mar 2019 14:08:47 -0700 (PDT)
MIME-Version: 1.0
References: <153960851213.19528.13097587822287903427@ietfa.amsl.com> <CAB75xn5S0iKSgNnQNFGiVWgdkkd5pvOvXU62+-M0RWK8OdZKAA@mail.gmail.com> <00b701d46570$8b2b4bc0$4001a8c0@gateway.2wire.net> <23CE718903A838468A8B325B80962F9B8D81D2E2@BLREML503-MBX.china.huawei.com> <02c801d46702$f2f31740$4001a8c0@gateway.2wire.net>
In-Reply-To: <02c801d46702$f2f31740$4001a8c0@gateway.2wire.net>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Sun, 24 Mar 2019 22:08:11 +0100
Message-ID: <CAB75xn5SEqRun3Mb4XTGenHJS+52iebmdjHrNm56MvnLmPs0pQ@mail.gmail.com>
To: tom petch <ietfc@btconnect.com>
Cc: Dhruv Dhody <dhruv.dhody@huawei.com>, "pce@ietf.org" <pce@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/64i0LK1-2tHNPN2b882OMdfOwCo>
Subject: Re: [Pce] I-D Action: draft-ietf-pce-pcep-yang-09.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Mar 2019 21:08:52 -0000

Hi Tom,

Thanks again for your review. I made an update to the draft (-10).

More inline..

On Thu, Oct 18, 2018 at 6:53 PM tom petch <ietfc@btconnect.com> wrote:
>
> Dhruv
>
> I will have some more in a day or so.  Meanwhile,
>
> I note that some of the lines exceed the limit allowed for an RFC, e.g.
> in the tree diagrams.
>

done.

> The convention (rule almost) is to use the same prefix for the same
> module in all cases; here you have
>        import ietf-pcep {
>           prefix p;
> and
> module ietf-pcep {
> ...
>     prefix pcep;
>

well I updated the prefix at module ietf-pcep to "p".
Using a big prefix makes keeping everything within 80 characters difficult.

> I find it useful for the YANG reference clauses to include the name of
> the RFC as well as the RFC number e.g.
>        reference
>          "RFC4360: BGP Extended Communities Attribute.
>           RFC5668: 4-Octet AS Specific BGP Extended Community.";
>

Updated.

> > 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!
> >

Updated.

> > 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.
> >

Updated.

> > 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'.
> >

Updated.

Thanks for your continued reviews of all the yang work and keeping
everyone on their toes :)

Thanks,
Dhruv

> > 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 <internet-drafts@ietf.org> 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
>