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

tom petch <ietfc@btconnect.com> Tue, 12 November 2019 16:44 UTC

Return-Path: <ietfc@btconnect.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 8D158120833; Tue, 12 Nov 2019 08:44:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.248
X-Spam-Level:
X-Spam-Status: No, score=0.248 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RATWARE_MS_HASH=2.148, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 GaGbFonIxYZk; Tue, 12 Nov 2019 08:44:38 -0800 (PST)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-vi1eur04on0724.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe0e::724]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EE2A12082E; Tue, 12 Nov 2019 08:44:38 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=k+C3Ea/m3xmbKgKikiyvekMCc7E12wyQxgo/tcgFkgUAqf0T51gNHzSURNnW2aUAoe3iWVTbzmhREV26iS053Jb426BfBd527FGdUMv1GIkgCLhNZ8Gyupum+wXJ5Cd1F17VjJUZhJyoSsSH3fzMktyV7RFXw0aiPYQCbUv4IlBhGRQbdDQHqN666u7el4f4MyZ1FFwyWXZD4Jo5lVAxIuCuR5+P4Y9AOceO+OxCmYGg9zVtTriKWWSfqsmWHm2hsUPmPdbzj4U6snylQCIKtKfOU5ZybA0jpVZF5vt9+n1Z1Vz867z3+9tyCY4evWL5dnSSunk/Yir8yDg29V6z5A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=tMrK45cXqBMNQG9hCWFl8yW9t1lE3hI/1uHkab1Oub0=; b=h6lzea9PRHt8yFj+9/oHidT0nq0QqZ6OApIGghd8uPy2UcgAHFG0tl8y4h1nVr1Grjs9CAggQT+KdyNPrqGaqzBJvqzlUV6SxsV4riprRkpGEg6vqju8ln3xlM9RPdy4BqpEZE+pDdkhIlURFjwQhYs0o2gmcL/8kMZeFfjn4pRSGEaWSNx80i0mCrIeiXX7XVztGTjJmmJNNqGOUzM6Ti14fueb/d+nWJAsThS2uAd3wRxd+bg30C2LCDT7tqxXD4wGrkM4e18ztwbXkL5XHgRexzsVlF5fKNot+uWhA460TIcRZOW8Nvj9RD/GoM3EzTnecpHBqSEqFQOmwS6odA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=tMrK45cXqBMNQG9hCWFl8yW9t1lE3hI/1uHkab1Oub0=; b=Gzxr1eg6hdMNYR5CBQ7KDeexVlxNE0VqeecDKJuyyaaXFd3f6/x0yTffzCx3Scf+XzeXulEm3ESSzlA0TPFbEETUFffuRmp3SLfQtuKTSRGHrPm4HIdUxE4hQG0A4DfU9Ts9QiJTgUxNK14kQMgLLKY+tQDR8qpYvOb/oQFrt7A=
Received: from DB7PR07MB5147.eurprd07.prod.outlook.com (20.178.42.32) by DB7PR07MB5063.eurprd07.prod.outlook.com (20.177.123.87) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2451.16; Tue, 12 Nov 2019 16:44:35 +0000
Received: from DB7PR07MB5147.eurprd07.prod.outlook.com ([fe80::e5bf:72e6:a66c:401a]) by DB7PR07MB5147.eurprd07.prod.outlook.com ([fe80::e5bf:72e6:a66c:401a%3]) with mapi id 15.20.2451.018; Tue, 12 Nov 2019 16:44:35 +0000
From: tom petch <ietfc@btconnect.com>
To: Dhruv Dhody <dhruv.dhody@huawei.com>, Dhruv Dhody <dhruv.ietf@gmail.com>, "pce@ietf.org" <pce@ietf.org>
CC: "draft-ietf-pce-pcep-yang@ietf.org" <draft-ietf-pce-pcep-yang@ietf.org>
Thread-Topic: [Pce] I-D Action: draft-ietf-pce-pcep-yang-12.txt
Thread-Index: AQHVmVLsoYyR5rK+50+AH7HDzlP0rg==
Date: Tue, 12 Nov 2019 16:44:34 +0000
Message-ID: <007d01d59978$6dd68c00$4001a8c0@gateway.2wire.net>
References: <156198024658.5639.14789358326677338506@ietfa.amsl.com> <CAB75xn4ODQ5itnhWhp1dGF_SwYyYXU-VsQMftU46f5jfy1siQA@mail.gmail.com> <04e201d59952$e3c05b60$4001a8c0@gateway.2wire.net> <23CE718903A838468A8B325B80962F9B8DC9857C@BLREML503-MBX.china.huawei.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: LNXP265CA0075.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:76::15) To DB7PR07MB5147.eurprd07.prod.outlook.com (2603:10a6:10:68::32)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-mailer: Microsoft Outlook Express 6.00.2800.1106
x-originating-ip: [86.139.211.103]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3a8bf8f0-67a7-466a-41c2-08d7678f994c
x-ms-traffictypediagnostic: DB7PR07MB5063:
x-microsoft-antispam-prvs: <DB7PR07MB5063F872C8C6481F4A450A28A0770@DB7PR07MB5063.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 021975AE46
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(39860400002)(136003)(346002)(366004)(376002)(189003)(199004)(13464003)(478600001)(102836004)(966005)(305945005)(76176011)(81816011)(81686011)(7736002)(86362001)(2906002)(66574012)(71200400001)(5660300002)(71190400001)(6486002)(316002)(61296003)(6246003)(8676002)(2501003)(446003)(14454004)(386003)(6506007)(53546011)(229853002)(476003)(486006)(62236002)(1556002)(44716002)(186003)(6512007)(9686003)(66066001)(66476007)(99286004)(256004)(6436002)(3846002)(14444005)(6306002)(44736005)(66946007)(110136005)(4326008)(6116002)(81156014)(4720700003)(81166006)(25786009)(66446008)(14496001)(8936002)(66556008)(52116002)(50226002)(26005)(64756008)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB7PR07MB5063; H:DB7PR07MB5147.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0;
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: qJIWajMcf+5ZBsZ230PgfarSA0MM3oxQsixGqdFAWP5MQQEvW3uZkt9pfBriLSf26MfQg7LGtN3XLNBO4/GaIBAcsHgutKJvwUa7qsJnm0t6JhtRVq/utvN/xQ31Wm1CyIJMDa05tDON9YWuRvzlGBsb2wJGFR6CnBdH3WS9q6kOCCL9i7w3ImFDpjmjfiqREo8IAjqmVGS4j9O16pTLoKHN9t03BDb3t5rHtZoNpsGpGkyEpUIxTzGS6r1dTVdRzXQzpEbgOalBThjvjqmTG/j6BEtHKSZGLIa459qLb/wyHLiUCUhS66rd8daaYTvsKuR96zjBPkTcpxexeWzbeJTIAO2tqhm7/K87axlIu8lrvXtyHYwt7O5ED449qMxtVINwMK0NRZ1JGp3pFIU7ZJ7BE1kYff90lPwW3W53q1RYLETtBrB6nqjxbJDOBmcF
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <2DB539E18CE7494FA3C5AB4262B60F9D@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 3a8bf8f0-67a7-466a-41c2-08d7678f994c
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Nov 2019 16:44:35.1727 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: +7mqTeXKZX1DsN35omYszolr7x1spDFDCjwCjIHzQFo+lg4Uccwwo9Ly6TYZo/eMz7rwbLUxprRFlo0j7W4uCQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB7PR07MB5063
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/xbtkkDBQwUGB3kwwtOIn6AV3rZA>
Subject: Re: [Pce] I-D Action: draft-ietf-pce-pcep-yang-12.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: Tue, 12 Nov 2019 16:44:41 -0000

----- Original Message -----
From: "Dhruv Dhody" <dhruv.dhody@huawei.com>
Sent: Tuesday, November 12, 2019 4:21 PM

Hi Tom,

The -13 version does not have any technical change, it handles a few
yang guideline statement ordering and tree depth change.

https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-pcep-yang-13

We are awaiting movement of some dependent yang models before moving
ahead with this one!

<tp>

If you are waiting for what I think you are waiting for, it could be a
long wait.  Quote from a recent post on another list talking generally
about a large cluster of I-D, one of which is in the Normative
References here

"
> I think it is quite clear that the WG doesn't want more delays.

Is it?   I only know that Balazs K. wishes to have the first three
drafts (crypto-types, truststore, and keystore) completed soon.  The
Nokia/BBF folks were interested in netconf-server, but forked long ago.
Otherwise, I'm unaware of anyone stating a preference.   For myself, I
only hope to achieve a good result.
"

Keep waiting:-(

Tom Petch

Thanks!
Dhruv

> -----Original Message-----
> From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of tom petch
> Sent: 12 November 2019 17:46
> To: Dhruv Dhody <dhruv.ietf@gmail.com>; pce@ietf.org
> Cc: draft-ietf-pce-pcep-yang@ietf.org
> Subject: Re: [Pce] I-D Action: draft-ietf-pce-pcep-yang-12.txt
>
> Dhruv
>
> I note that -13 has appeared and wondered what significance I should
read
> into this.
>
> Tom Petch
>
>
> ----- Original Message -----
> From: "Dhruv Dhody" <dhruv.ietf@gmail.com>
> To: <pce@ietf.org>
> Cc: <draft-ietf-pce-pcep-yang@ietf.org>
> Sent: Monday, July 01, 2019 1:14 PM
>
> > Hi WG,
> >
> > This update includes -
> >
> > * Pending issues as pointed out by Tom Petch
> >      - Use the right prefix for imported modules
> >      - Removed [] around the reference I-Ds in YANG modules
> >      - Updated IANA
> > * Added lsp-id as an additional key for LSP-DB
> >      - Useful in case of MBB
> > * Added implementation section
> >      - If you are aware of an implementation of this YANG module,
> please
> >        reach out.
> >
> >
> > Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-pcep-yang-12
> >
> > Thanks!
> > Dhruv (on behalf of co-authors)
> >
> > On Mon, Jul 1, 2019 at 4:54 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-12.txt
> > >         Pages           : 113
> > >         Date            : 2019-07-01
> > >
> > > 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 and state data.
> > >
> > >
> > > 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-12
> > > https://datatracker.ietf.org/doc/html/draft-ietf-pce-pcep-yang-12
> > >
> > > A diff from the previous version is available at:
> > > https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-pcep-yang-12
> > >
> > >
> > > 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/
> > >
> > > _______________________________________________
>pce