Re: [CCAMP] I-D Action: draft-ietf-ccamp-otn-topo-yang-03.txt

"t.petch" <ietfc@btconnect.com> Tue, 19 June 2018 11:18 UTC

Return-Path: <ietfc@btconnect.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 349B9130E43 for <ccamp@ietfa.amsl.com>; Tue, 19 Jun 2018 04:18:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level:
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" 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 KRMfTLTcHh1Q for <ccamp@ietfa.amsl.com>; Tue, 19 Jun 2018 04:18:02 -0700 (PDT)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0121.outbound.protection.outlook.com [104.47.1.121]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7185E130DDC for <ccamp@ietf.org>; Tue, 19 Jun 2018 04:18:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=6LsceFAtT0E7Hhn46jWmQlddLnP6boT4TCohYHwXiyY=; b=OCNZUv25Ksn2nIHVN1jBSNRHM22yc8GSklIuiex1d4lyIBQrEPRP239cuPfCzG3hynMsTJFWMhgUjaVEeruVNk8hvNVUj6BK0ZFfw2sNZClVKqffjkY0YJutDcdReoIG8OF8GSK7V2L27jSo3NXKlyq2Qm3+WLbGvoXku+Snd8g=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com;
Received: from pc6 (86.156.84.71) by VI1PR07MB0831.eurprd07.prod.outlook.com (2a01:111:e400:508e::26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.884.15; Tue, 19 Jun 2018 11:17:58 +0000
Message-ID: <051a01d407be$e1829880$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "Zhenghaomian \(Zhenghaomian, Optical &Microwave Technology Research Dept\)" <zhenghaomian@huawei.com>, <ccamp@ietf.org>
References: <E0C26CAA2504C84093A49B2CAC3261A43B699664@dggeml511-mbx.china.huawei.com> <027601d40566$efe5b9c0$4001a8c0@gateway.2wire.net> <E0C26CAA2504C84093A49B2CAC3261A43B699DBB@dggeml511-mbx.china.huawei.com>
Date: Tue, 19 Jun 2018 12:15:42 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [86.156.84.71]
X-ClientProxiedBy: CWLP265CA0230.GBRP265.PROD.OUTLOOK.COM (2603:10a6:401:4f::26) To VI1PR07MB0831.eurprd07.prod.outlook.com (2a01:111:e400:508e::26)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: d98edbd4-ac73-47f5-30af-08d5d5d6500b
X-Microsoft-Antispam: UriScan:(219612443155931); BCL:0; PCL:0; RULEID:(7020095)(4652020)(8989080)(4534165)(4627221)(201703031133081)(201702281549075)(8990040)(5600026)(711020)(2017052603328)(7193020); SRVR:VI1PR07MB0831;
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB0831; 3:mDuplnpHkjMi8mROJMZ6DGNcPdh2VZt/R6B8TgyjvQK/0ghYb/MXV5OpYFGhnop1I1Il89vJP2fVpHu9SgKoNe7qB8fSNMuDXNdWc6jFAG7ZJXk6wLrdLhsLzAnreiRoaP8tbZtitQk7XuQQFbrgCvRjkXbWvHnOmgNt4yHZgGf0t5HkS3zQ4qnwh2OXlP0sg22tptFNncBeSHqkbfPbQl/tTra5iHi1+vXn7srnloJQwXFrtuqB+dAsnvnTzEDBf/TMV5dm+1mIV+zl4lY+PSqVKz8KnL9K4vjsNYK4OYY=; 25:PkRZ/4ltyt/yboaf6/Ir4m85Taa1VW+kNOSQI7WSBCv/GDTvI36YzawgOalVwtFepCH1NY5/l0U6yY6Q2fS5t5zfVd+XIz/T0MsvxuydH0G75uysuo9kuV+7f8pgB0GAUTZxKJNwu9hsefux3QAtDiP8gw0ZnGC/qwAmFL6+LRTFYZhTRuQLO5gGj+x0h34BEXWuClAS/ffh/aMLWUNKBmpbWFH4X90DrDOFr/GK2z3bLvvv3ESJum3XOBpc6pnNqOORTkzty2kOOIQQRTJTvI8pmPMYONnnGJuIVsGSpZ3OBEndrtbnn2xDpVBAw5gahjb4YwqoYRK2xCDVEDGMhmnOwAOZ2+gXTiEx74trMvQ=; 31:dxK+HL4UAuePEqTz74Yjzlt5tbfRVGfkaFOqKSaA/BwbpkfbPUMFa64KB4OjQrtJ0ROxI0A3UiVyLig5t/ovQqOboJtNBM9rv04dzzw8TiMXbyrcTTjBdQ+zI/j6oNF435E3hOlNV6aFiN3FJ9NT0M+KXtlOvF5KAxng1NVVz5FgIO/zge0qR51VbtbCrdbv9DZ9ee48mN/IsVWlp610zCWPbzkPu4+vcPIokGjiNSM=
X-MS-TrafficTypeDiagnostic: VI1PR07MB0831:
X-Microsoft-Antispam-PRVS: <VI1PR07MB083198C3287974E3852A15DBA0700@VI1PR07MB0831.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(178726229863574)(120809045254105)(166708455590820)(35073007944872)(50582790962513)(219612443155931);
X-MS-Exchange-SenderADCheck: 1
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(3231254)(944501410)(52105095)(6055026)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123560045)(20161123558120)(20161123562045)(6072148)(201708071742011)(7699016); SRVR:VI1PR07MB0831; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB0831;
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB0831; 4:3tB5GO0lgHMwzIAsSdcgULbuaP3zWFI7AeswmSLbpYT9dVm4oj6WJR3dOO15IFEPqfy6L0OoTwsqPtOL3HmavWyGRRoR+EJ/sk7oXyxH4QqnVQFSpsZV3dMSimXqVZ71+GPQeBr08ZVgzc2zn5c3k4Qe/IRZQNMFhixvkDXZc6SdGhVMnka7zowm29Ji0OrSFSDLlGqFc+howj9Z3YmJa8DUsdBNj7z0qq+fgEsXD5rIPmQSEIbzIPll6qKVSKdg1AwSLY5buvOFNldJxCuYS6+RAxlA40fASEjNkebmq1IQY9xhXIVDmGwYqlxtH4JZK9oAesEBJ+Ubmia4wmyxpfYT2kw+JKtocewX7OfVlsbuvzytigzRUkHXzhJO+Q84EaFPoDaK+Nm6O4Ryd9dAuU4nsaQ6j2eYKeqDCdHtNvGxQn2buzJWcuUC1Cmch8pe9YcNW6YXh7gOim7bSe1kme8k+bjXV64kacXOdwKlDhw=
X-Forefront-PRVS: 07083FF734
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(346002)(376002)(366004)(396003)(39380400002)(39860400002)(13464003)(51444003)(189003)(199004)(966005)(6486002)(44736005)(68736007)(26005)(105586002)(16526019)(186003)(478600001)(61296003)(6666003)(8936002)(50226002)(345774005)(4720700003)(7736002)(81166006)(5660300001)(305945005)(50466002)(8676002)(81156014)(23696002)(229853002)(6116002)(6496006)(14496001)(25786009)(110136005)(1556002)(52116002)(3846002)(446003)(97736004)(86362001)(476003)(6246003)(53936002)(6306002)(956004)(9686003)(47776003)(48336001)(2870700001)(486006)(2906002)(59450400001)(386003)(47136003)(106356001)(84392002)(62236002)(44716002)(33896004)(81816011)(76176011)(81686011)(66066001)(316002)(4470400001)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB0831; H:pc6; 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-Microsoft-Exchange-Diagnostics: =?gb2312?B?MTtWSTFQUjA3TUIwODMxOzIzOnVGeFB0R0ZFajJDOTNqS1RrT0s2V3JnWWdt?= =?gb2312?B?WmNmZHFHd3I0b0VYUmtGR1p5ZVNDWUIvVzluN0E3cEp2emIzVzd6dWFIL3ZX?= =?gb2312?B?Q3lmbUNDVlhsaVpQbzV6c1JQdXg5c2c5dCt2N0JHVTNobGxxRmF3dmRma1k4?= =?gb2312?B?NVhCNW5YRyt0SzM2bDNLc214SDlvWFduZ3Q2bDVZakw5Y2hNcWlrL3g2RktL?= =?gb2312?B?b0pQdmFrRWNvVDFjS1U2MHpzM2tXS0xxT3hEbzlOeVYxaWZWelNBeG5Yd3Vn?= =?gb2312?B?WGVsS2FWbWxCN0N6QkZRcHJWbG1Yd3JRWHk5L3hOZ3ZmWDNObjh2OGZST05Y?= =?gb2312?B?cFdDeFU1SEkxdHcxN1BjcWRUeldUZERieFZldkpCVk5NdEFvWEtMdFJidUww?= =?gb2312?B?UGdHRkI2dlQwOFR0dGlaSkkvRW13QkU1cTkzTTRjV1FzaTg5a2FsSjI3TFVO?= =?gb2312?B?OFFvK3hpMXorVEVDUEN3OFpJN1RMK1VaaFM1YVc3TGVQWnlGdzl3TFV0dGRy?= =?gb2312?B?dTFGcHloWXhFcU54QmZPYnBZK0JyUEo3cXNRZDFWTlFxb2EwdlBVcXRmT2JT?= =?gb2312?B?RUh2ZEJKMW9yQ2tnbHY3MS9pazNYRWNqY0ZPNjgzNVMzRm42TnhqRnJrdTM4?= =?gb2312?B?c0E0SmcrbzNsQmdiTnpNZXFuVGpoU3NrWHpvNnpqaDU0dTYrZU1BQTRDZVVj?= =?gb2312?B?bnJmMEc0dmN1emRwb2hJSWxqRlFUL1lsWnlONnNoL3l3aVcwSElRNG54VkZx?= =?gb2312?B?VW96N2tpV2UvcTl1WnBnRnpnRzh2WEIwdmRIMmNlVnFuc1JWVlVSZWoycjVr?= =?gb2312?B?Z2E2Y2N1aE9sK1hwcHVvaUJibHk2S3RDZVV0ZTNIYWI3eUdnd2FWVW8rVHhB?= =?gb2312?B?SUVHR1N5L2ZDMFEwRTh5ejRJaTIwQUlGc0ZUMjNTSWk5SWxEMmZWYXV5WGda?= =?gb2312?B?K0VwOWZkMHdkTElFS0RiaUNUcnpmMHpXZWZUOTZBS2ptNWxnR2hsMHl5TEsv?= =?gb2312?B?NHJIN1NvS3dZRmlFYkxUc0JFbXY4Tnk3cFdhdkpiS0pkWkdxemNOeExFR1pz?= =?gb2312?B?SUFOcXVXckNycFhqTjFWT0paaW9nQkhsRDhPVFJpa0M4RTNoUFZQQXIzZlli?= =?gb2312?B?M3NNaVA4YmEvQVF4OHJoR0lpbVNReWxqUHIyLzJrQVk0dmMwRlc4cWU3NDVr?= =?gb2312?B?d3V1bnBCN0R4aGl4YUZpVG1VbVEzM1FsV0hGS05WQ1M3V2xBKzNHb25scmJF?= =?gb2312?B?SmMzV2Z3WDdXTGZTaEdZcm9aOTRMRU1WeUprcG4xcG15SUEwaVRKdEJ5MmZm?= =?gb2312?B?bUR4d3VmRXRMMTJzbXIwaUZDOFc2QVphN3hlaWhtTXdhTTNpN2M0Q2xMNEFB?= =?gb2312?B?NWc0U0FQQnVzaW1rRzVjVUxIUWVOcUZseTR6NnR4MjNtenAzUGdzVW43ZkNn?= =?gb2312?B?bHMyZ3FEZW1lbXJab1pZRGo1TExPSWpKQ2c2QWxFb0xabkFCWlVUYnY0SkhM?= =?gb2312?B?YTNaYXVuazlLMUZ4Qk0vMWdIWXBjSkYySXU5cDJ2aGtBbzVLaXp4aW0zZHli?= =?gb2312?B?d3l6U0xDRU1sREZyRER1cldzbjRiUERaelpHYS9rcVAwVmk1ZUtzOEt4dVhP?= =?gb2312?B?NDRWeVBnSXpkRUhEM3hLR1JxT2xOYlY1YjJka1lwM2prek9xbTJVSFhpc0sz?= =?gb2312?B?R0V5Nkg4U0FleVYyUmxFK0Y0RmdNU0VxaGwyMWFKQ2kvbXNqYkw5L2puWVZD?= =?gb2312?B?VVNCdTdZS2ltKzdHT2h6Sk9yZkNSWmp2ckZYQ1RQNzU5SWRHSzhhVXZQRzU4?= =?gb2312?B?K2MwUEFDY3dmRWI4K2VSTVpJck04eWZtSVRaSGlZMjJOVmNhZ01QUEFFbGg5?= =?gb2312?B?UHRWR3RLVEJEd2FXbUZOUk5OYzZJUXNJa3lWbWVUNCs2dWYySXpmby94OFZ1?= =?gb2312?B?OFNUTEdEalNGYVlpa2ZZQ3F6Wkk5Tkh2L3V4OHBjeGNHRHFVQzJHSkFDbTQ2?= =?gb2312?B?dTlwMHhnU25URk5PdHFQenp1WU9VMWI5dWo0eVFTNW5xaGxtSjR4VHEvNk00?= =?gb2312?B?aXlWMzZXejJtSzJsaDM4R2NGODNPem51U0FxRVpmZ292QzZBSkQySElQUm1h?= =?gb2312?Q?fQxq34tin/QV+f7sHOGceBBniFAGer7Tuy7TMcq+0Acc?=
X-Microsoft-Antispam-Message-Info: uonzgEXsl7GZMjmsZDbhXpUaCNioGPMxKorYerOPUOc9ESt5ChdwwUYpN/a1ZSHsOpi6VEZbADQaJmou8EEOmf1fkMgfh44iM7p2ShY0sA/YSl90OqWRGgU8U1MTRZwjuMogtQEckQIW3No45653n/eX+hTv3s/jbf2D1NYg67GMTekKDolMK1Yl6tGaA20WQx+Clh/ZmraJr99gDe7C3tOx56s9eOtYEvru4+3cFuTgKhdDVIXkDvQ+vb8CHmQBMH3bG2TtDu2QHZ6J56+YxLN8ZxCDRzfBstdsJhdLJECaSqfz2JN6qbJLe6IZjIB6urtZsU5eIsEbZQSzabP6zw==
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB0831; 6:FMNfLEjB4gOP1b1aqdIlERR5KfzGj/7/XX0FlB8YpwQZU4K0XgzdVQxyDvH9kejxJ0SIVrZV0MdMVlOgAJabBHfkjixqXSP8JquJDIl/UjBVftCjgpFj8cTP5pcKm6Fx+u5k0scCLb6cYbLkoKv7vgVZX0KiFX3xxQc3iGXwqlulWKsTtnaR+yMkhnCSkQoTcPFRlBggQOOg8gL0bMOGpXlAkzmxPQcqGANRFzWzVhnwtrq2cAs1r6+TrLP/erpxieqbUUBznX8IQdPGM4yPAg/xzqxBdVIipxARkrjchsfotJjQG0mnVuNSHpT2puUyu+HaYQ7NkvXhkAt8+GK/ydQsFmpdjS9hrGnL3af22oJKbFCaLWZxYj1dRBIrQGurEhVzet0pu5jrXPFEVUuLc7eqOH9DbGO01oSmWbeq3qNCgoZIPhva4w/0rnzzRaRA5ExkyYI9DRad2GnyEMUu/g==; 5:ajPeLDzVXRR68iL7zCpYxzP8HPtYzPM2wGVJQKKnZgQndy29LDgzgnW3qsjPpd/nSzyDp9sDg8lklsk/obJ/XQtoa/zUUN+piH8DX9QRGoazDrcn1RiiGW5hDfTia9f1XbOO7pdL/ys9zEjTZ+x2T3tUHgks1LtD0ZIf4SHAF0Q=; 24:sSzZOLHR6lzVmyOWEUlee/mxUNJFTv0zhu3/0EHnArkI+ebNHflSm0qTyW2YXWgzjaiY7eKXw0JPn8XJorkhKVhfaYsDhmuFkElyWU08cS0=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB0831; 7:O5oEAZWWMqFknicHWMUp9jHFMou9uSygQTgY8AhoLvTlHkwzaOGRpfhgD5jjUbKsx/121ofWQq9u32pofmAN2pxcnwzeOaOfVz4HQwVpCK53DNxEgq+JnsaLKydwPghDxXEeT70dNYHJY04H8XxZFnpNEOQt0IlX/5QyS7jyvKaotLC3iR7RphV0lqGjWjCyDz7GMcaAryIwXl/Pl4dAwigt3vkjMuG6l7jZh0UfpnGl1CGWvQRII7OJOtWqL9/B
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 19 Jun 2018 11:17:58.1798 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: d98edbd4-ac73-47f5-30af-08d5d5d6500b
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB0831
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/dAhtqKzUJV20eUeHk6pzDQAtxlY>
Subject: Re: [CCAMP] I-D Action: draft-ietf-ccamp-otn-topo-yang-03.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2018 11:18:04 -0000

I am afraid that my knowledge of YANG is not up to seeing alternative
approaches (unless and until I see them used in other I-Ds:-).  Other
computer languages are much more elegant when it comes to slotting in
multiple adjustments in multiple places.  Here I struggle even to
reverse engineer the YANG to see what is intended.

I think that your hand is forced by draft-ietf-teas-yang-te-topo which I
had looked at, but had not grasped the consequences of, until I saw your
I-D even though I had looked at Appendix C, the example of augmentation,
in the former; and forced again by the rules in RFC8340.

Part of the problem is the depth of the data tree, up to 20 levels or
so, which makes any absolute form of 'augment' or 'when' lengthy,
fragile and error prone.  I see
    when "../../../../../../../../../../../../"
       + "nw:network-types/tet:te-topology/"
       + "otntopo:otn-topology" {
as well as
    when "../../../../../nw:network-types/tet:te-topology/"
       + "otntopo:otn-topology" {
similar but different; are both correct? hard to tell.  Collapsing the
tree to much fewer levels would make it so much easier to follow but is
obviously problematic.  'when' can sometimes be replaced by 'if-feature'
again a significant change even when it is practicable.

Likewise use of relative rather than absolute references in 'augment'
would make it much clearer to me but I am uncertain how feasible that
is.

And then it is possible to add your own extensions to YANG which
increases the scope somewhat:-)

You need one who shares my concern as to how easy (or not) this is to
review with a deep understanding of all that YANG can offer, perhaps one
of the architects of YANG.

Tom Petch


----- Original Message -----
From: "Zhenghaomian (Zhenghaomian, Optical &Microwave Technology
Research Dept)" <zhenghaomian@huawei.com>
To: "t.petch" <ietfc@btconnect.com>om>; <ccamp@ietf.org>
Sent: Tuesday, June 19, 2018 2:22 AM

> Hi, Tom,
>
> Thank you for providing the information. I fully agree with you and
would like to spend some effort on make the work easier to read.
However, I need some guidance and toolkit (UML editing is not
sufficient) to accomplish the work.
>
> I also received some similar problems from other YANG editors, maybe a
side-meeting in Montreal would be helpful for us to deal with it. Your
suggestion are highly welcomed, thanks.
>
> Best wishes,
> Haomian
>
> -----邮件原件-----
> 发件人: t.petch [mailto:ietfc@btconnect.com]
> 发送时间: 2018年6月16日 19:16
> 收件人: Zhenghaomian (Zhenghaomian, Optical &Microwave Technology
Research Dept) <zhenghaomian@huawei.com>om>; ccamp@ietf.org
> 主题: Re: [CCAMP] I-D Action: draft-ietf-ccamp-otn-topo-yang-03.txt
>
> ----- Original Message -----
> From: "Zhenghaomian (Zhenghaomian, Optical &Microwave Technology
Research Dept)" <zhenghaomian@huawei.com>
> Sent: Friday, June 15, 2018 11:36 AM
>
> > Dear WG,
> >
> > This is an update to OTN topology after 8 month, as we are waiting
for
> the maturity of basic TE topology model. Now the model is updated to
be aligned with TE one. You are welcome to review and provide your
comments.
>
> It's a tough read.
>
> I might find section 3.2 easier to follow if it was written in
Assembler:-(  A tree is intended to make a module easier to grasp but I
think that this fails here.  As RFC8340 says " As tree diagrams are
intended to provide a simplified
>    view of a module, diagrams longer than a page should generally be
>    avoided.  "
>
> Nor is the module itself much simpler e.g.
>
>   augment "/nw:networks/nw:network/nw:node/tet:te/"
>         + "tet:information-source-entry/tet:connectivity-matrices/"
>         + "tet:optimizations/tet:algorithm/tet:metric/"
>         + "tet:optimization-metric/"
>         + "tet:explicit-route-exclude-objects/"
>         + "tet:route-object-exclude-object/tet:type/"
>         + "tet:label/tet:label-hop/tet:te-label/tet:technology" {
>     when "../../../../../../../../../../../../../../../"
>        + "nw:network-types/tet:te-topology/"
>        + "otntopo:otn-topology" {
>
> rinse and repeat, seventy times.
>
> I do not have a solution, just think that YANG has got it wrong
somewhere:-(
>
> Meanwhile, there are my usual red tape issues.
>  - copyright
>  - date on module
>  - reference statements on import
>  - I-D References for any references in the module
>
> along with incomplete sections 5, 6, 7.
>
> I think that the failure of the tree diagram is the one that needs
tackling, perhaps with assistance from the contributors to RFC8340.
>
> Tom Petch
>
> >
> > There are still some YANG errors because of the incorrect reference
to
> OTN tunnel model and OTN types, which have not been updated yet. The
other OTN tunnel model draft is under our processing and will be
announced in the next week. All the OTN models can be found at the
> github:
>
https://github.com/haomianzheng/IETF-ACTN-YANG-Model/tree/master/YANG/cc
> amp, and you are welcome to comments.
> >
> > Thank you.
> >
> > Best wishes,
> > Haomian
> >
> > -----邮件原件-----
> > 发件人: CCAMP [mailto:ccamp-bounces@ietf.org] 代表
> internet-drafts@ietf.org
> > 发送时间: 2018年6月15日 17:14
> > 收件人: i-d-announce@ietf.org
> > 抄送: ccamp@ietf.org
> > 主题: [CCAMP] I-D Action: draft-ietf-ccamp-otn-topo-yang-03.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> > This draft is a work item of the Common Control and Measurement
Plane
> WG of the IETF.
> >
> >         Title           : A YANG Data Model for Optical Transport
> Network Topology
> >         Authors         : Haomian Zheng
> >                           Aihua Guo
> >                           Italo Busi
> >                           Anurag Sharma
> >                           Xufeng Liu
> >                           Sergio Belotti
> >                           Yunbin Xu
> >                           Lei Wang
> >                           Oscar Gonzalez de Dios
> > Filename        : draft-ietf-ccamp-otn-topo-yang-03.txt
> > Pages           : 58
> > Date            : 2018-06-15
> >
> > Abstract:
> >    A transport network is a server-layer network designed to provide
> >    connectivity services for a client-layer network to carry the
> client
> >    traffic transparently across the server-layer network resources.
A
> >    transport network can be constructed from equipments utilizing
any
> of
> >    a number of different transport technologies such as the evolving
> >    Optical Transport Networks (OTN) or packet transport as provided
by
> >    the MPLS-Transport Profile (MPLS-TP).
> >
> >    This document describes a YANG data model to describe the
> topologies
> >    of an Optical Transport Network (OTN).  It is independent of
> control
> >    plane protocols and captures topological and resource related
> >    information pertaining to OTN.  This model enables clients, which
> >    interact with a transport domain controller via a REST interface,
> for
> >    OTN topology related operations such as obtaining the relevant
> >    topology resource information.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-ccamp-otn-topo-yang/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-ietf-ccamp-otn-topo-yang-03
> >
>
https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-otn-topo-yang-03
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-ccamp-otn-topo-yang-03
> >
> >
> > 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/
> >
> > _______________________________________________
> > CCAMP mailing list
> > CCAMP@ietf.org
> > https://www.ietf.org/mailman/listinfo/ccamp
> > _______________________________________________
> > CCAMP mailing list
> > CCAMP@ietf.org
> > https://www.ietf.org/mailman/listinfo/ccamp
> >
>
>