Re: [netmod] Adoption Poll: draft-rtgyangdt-netmod-module-tags-02

"t.petch" <ietfc@btconnect.com> Fri, 09 February 2018 15:23 UTC

Return-Path: <ietfc@btconnect.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9430127058 for <netmod@ietfa.amsl.com>; Fri, 9 Feb 2018 07:23:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level:
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham 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 8oz6Aa4b5oka for <netmod@ietfa.amsl.com>; Fri, 9 Feb 2018 07:23:00 -0800 (PST)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0109.outbound.protection.outlook.com [104.47.2.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9385126BF7 for <netmod@ietf.org>; Fri, 9 Feb 2018 07:22:58 -0800 (PST)
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; bh=jhWyI8/+iOQ0BWtKvSZOaVKOGDZ7w9g1BJfB2y2kojk=; b=RT9H8g0OZBJvZFbfHrCXvgzSzG7AKOq0gTSs8KDyM2T7KeiI0AAG5QKSWAlYZW0ocLhW0aX6/Nx0NbdxpF72ZhkPiDduazdhjE/QfNk522JhTFn0HAeoSvTHpuGeBUC5kmHfvTMJouV95Q2z2VfNXOvu18iCWHbWxC3Br/HGBLY=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com;
Received: from pc6 (86.176.21.219) by HE1PR0701MB3003.eurprd07.prod.outlook.com (2603:10a6:3:4d::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.485.3; Fri, 9 Feb 2018 15:22:56 +0000
Message-ID: <026201d3a1b9$9e7ead00$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: NETMOD Working Group <netmod@ietf.org>
References: <201802071859.w17IxjwU073675@idle.juniper.net>
Date: Fri, 09 Feb 2018 15:19:40 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
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.176.21.219]
X-ClientProxiedBy: HE1PR0301CA0006.eurprd03.prod.outlook.com (2603:10a6:3:76::16) To HE1PR0701MB3003.eurprd07.prod.outlook.com (2603:10a6:3:4d::9)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 54e7d433-ff4d-424a-102a-08d56fd0ff71
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(8989060)(5600026)(4604075)(4534165)(4627221)(201703031133081)(201702281549075)(8990040)(2017052603307)(7193020); SRVR:HE1PR0701MB3003;
X-Microsoft-Exchange-Diagnostics: 1; HE1PR0701MB3003; 3:R+9FRChj8nS5RHYvZT14ihhqY1RuF6PRwW82ZiyPuTzzGsDOylCEw68ub6DjyQFtvhc3vV4+POEk9zD1B4IwsFfjZtBxAzLAl+/Nz/km2Ieyvgn8nbJA8y3tjvbmOmOhUMQ1XX1x8fJwW3f+g5XZwwSpf5Ac6/WIMtXnJG7kovxh99iA0068q5t3ZZu2mrw6DfubKHoOZupUl4sb/772wSUOz1k9JH0GsNmeCyfGv4hH9to1N40u5aJkbFNj4i1/; 25:vGUc0FOS/pWSUrlZlp++h6iZgBahS4+DUCdwk4kTFRe63KfbjsgS5dSwU1ljoKrhvZ45EAF1UthLnqGlZBfE+jKgQWVctMq+QUPgkicNKz/jFRQudWmdaPIiXj3nJpYQUftrM3a8tx3/lz7PnTm1GXejDuLqyr3dE3vx1solD7i4m6kV4FUPiiIQfqjPgl4XHpF2h+XsUztiHbSAMrEAS+isfcf+iU7F3dt4qiLfoaRRTrpKiUpO+c8WLR/3TlUYPMRbFmDeBY+dgRWKQ4Gxsj1eUg9B2rJcHaAoTcjvKqj/TyaGy1BHY3ESpfKqxMgIV0SBVi/r64MeVd6RrxnL5g==; 31:NIIAufg/LEf/Ze6OQBbVqIEQFH47bfkYnXdni9FT/1eQTc2Xlr67hYSCm5lwyrzQOZt3esDA6eH7kynYvgylLhXGuA1LO+Eq8a1/M4fu7YGfq8UMFtERSJsbSAwGuK7wvDZCZpAw8RCsAARaSIKYM1ia/D2KlEsNX+I5qVKhLv8NO6IcJHnGwaAVBEqOgY/p4JuRfNydXlA5oS6/lRE8Fs3em2jwvctibcz7lHnzlAE=
X-MS-TrafficTypeDiagnostic: HE1PR0701MB3003:
X-Microsoft-Antispam-PRVS: <HE1PR0701MB300396E0D9DB1CEEF5A74602A0F20@HE1PR0701MB3003.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(278428928389397)(131327999870524)(138986009662008);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(61425038)(6040501)(2401047)(5005006)(8121501046)(3231101)(2400082)(944501161)(93006095)(93001095)(3002001)(10201501046)(6055026)(61426038)(61427038)(6041288)(20161123558120)(20161123562045)(20161123564045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:HE1PR0701MB3003; BCL:0; PCL:0; RULEID:; SRVR:HE1PR0701MB3003;
X-Microsoft-Exchange-Diagnostics: 1; HE1PR0701MB3003; 4:Vt80/WBk/GIdtDRcsHqOgBon5KRDxkO2Fn+isRQisTI9H5hzk4Svx05B+kFN9NO/NbofZBx2qdFB5PIlrJFuI8/4+mLJts7+vfnR+eFA/0ic0jjJYWm9Eu8zRpPDEIUc8C+SEBdcYkN+iIxGRGUPn28VKhMlY4Jboo14lgWsSJVP/1xcKqDxB87rgLsOKMPbJ+WFu4nd9HFkYHiYmuxYctwIT2L/+ImDZE8dUeJjAPbMCjodoRHNUq2chlCPF3X16pknBC0Pi3n0PfS5od5LwrEDKt9KlI6KeBqsoIwRBR5Yq+9JFxDLQ08Fs7OAy0QMQfK/Xiq2FHuhsois2uXAvmXBHatFdVWSVDujkM1wIKCN6e74OoaDhu8ZaDlNmrad
X-Forefront-PRVS: 057859F9C5
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(39380400002)(366004)(376002)(396003)(346002)(39860400002)(13464003)(199004)(189003)(52116002)(1556002)(2906002)(6916009)(305945005)(84392002)(9686003)(81816011)(6496006)(229853002)(50466002)(33896004)(7736002)(105586002)(44736005)(230700001)(23756003)(81686011)(86362001)(966005)(6116002)(26005)(47776003)(3846002)(53936002)(14496001)(6306002)(106356001)(66066001)(6666003)(61296003)(50226002)(186003)(76176011)(81166006)(59450400001)(81156014)(25786009)(8936002)(8676002)(478600001)(316002)(97736004)(16526019)(68736007)(6486002)(6246003)(44716002)(5660300001)(4720700003)(386003)(62236002)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR0701MB3003; H:pc6; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en;
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: 1; HE1PR0701MB3003; 23:YiX/rcub8ohME+x3ML2evhmZf1ACrbDtU5K8njqFWORv26DvPrMxUNLIn5FZ074IfEmrwwKxrJ+Bx9iej/T9J/TpWE69HY0ebNDL8NW3cJYC2NS7hB8n6vy94LQ/xh7tN7o4EgXE1WMp4hA17Zxlfa+tv41lpiT0unZwFdKXgfaxJ32gwASwUKWX2S6OQCXnqflm/RUtGAZo8TyPLmI6FDkqbTu2fgFQ9nNzCiYvuSaLAKm/AHslZIL/2hL4bmix8ve0F+kedjwRsrO3sqPXMvixp+mPkpYfYolL/MrgCKGYymr05SBoWD8GXNuOVmXRsAkGM0O9wL/6izAUJfyRPGnGBwxkt7JcJm7nuvEdkVlv96h6UhGS4WEk5O3E9cIumdliQ0YvhhMAECdh+5AlkEiNJuUcrSUfPFo67r7hAnuevJkYHHrepg1a2DqoMMLxAfKWX8jXqidE/TfD2u+aYRd/9qilOUh+AUhPJsN7/RNMYoqnT19DG9OeBmAxSzDOaKsdBV0pKxS5KTM0QK/2DMuSnkBnhCYmJ1iZL7AjFgWMhIAZsBrEVsPQMMg2s7e1qBeh7FqS2AgQyHRcoLbQ6/L1Mz8GqNOGgJXgZaTPw7U379VRkJ01P5SkcjG0CqTt+cVgBeirBwfny8zlxkBbnLXQ4w2fFuF+GshTsySLIfcwvDfvgGfR5qVQVeZ0OpXgR5KmalVmvn/+VVBU7klEucu0Mf1eg0V66jbdqdWbQdJ9PG8ziTRK+D4mesQ/PYjDmi7IR0YQKm/dgSk+GKqE+IvkYHm6jsl+bK4oyZ+CcSVbUN3q14qltd9Zi+Y3xoofnl+x1yuhM1nU4wOlzcdW0AOolXLmf3AJ5RzI6CMN+RNiA4AsSUS55uoYjOWWAQHWyca3n2dHicc+MB98fGodigieEm3SHSZmkE2h0hm8xwY4pc94xgtSc9I8VqHjf3Sr3RONMcB5NyzPvkAqxy3TnzKtqx0/1Be+awN0GDIOIxLJj+VPLVuE6h/ek8ePTghyly0MWCmYR/R4+ued9C3myGYJ+r8qPkAyZ8p3A493gEaBZ+cVUcUfGxVgorU6vrR8SeXCvYNc5gOyvHH0hew9s/eK0gzXjn0TCfMdRVTF1f4SvYMgCQMKbdS+B3GXpyl9NsANHWd+zkLDzckOdX7rKkUUO3A+a0IetixfEcqCH6Hj/ml93E3cXoRkj4z5R/GM/PadxTL2CsG3bJq8yQc2wN5tpibKXwHu+dbX8Sg2vgX2xDJl0BVpD5uNzdJkjnvbk1rBdKnY7wa0WlLfJR//ccOzjhQlRIZoOrsEQTyjOp4Mxbf13uqallmF1B4MlvRFlZPIGYyyO4a8953+z9tJIXNUy5b6b+2/nNhWJ3tzyUHZ7+gkYzeNxx8VZFrXwZVIIByaJ6QRn/npUl9FX/NKIQ==
X-Microsoft-Exchange-Diagnostics: 1; HE1PR0701MB3003; 6:jgQApFGulxIqPG0oKUZu3R9ZbeALYWWgGh8y2GTpvXhl/QLuAHXj17qQaRVg+U5bC4tKrL5bWomuP5IOtMngq9pNhwvkJkyAdKdxurOjMgq979B4Yzy3j6wQTF6W+g7f8Py4dbERG1BfdFQ6PGnuBe7xwb+069qt8BmuD/aqoCdILQRpwFJzL1KQdAFT/mblQdfrbu4xeVn6/7zp44YaOUBEQPWeRhX5nVR/wU+sgYcp+2qjyrygCBMUM4LGOF1GNOr1HMI1xQNBNuEhCPHCAfm6CLze34dHtsjiAGupkW/aC5+SsOvjPgckaVij5P8IskUf5MUumHvLv5w18cRwgv5U3GUt0iSluqd6v8JhNjk=; 5:UdXXGza77CRonG1n6mc689EvOfBT8k0UTGQwu/y9rFv8rUECRcCucWmgIVDRhQzP1Yr2gZBSEIl0joPp68qWW+57pJtUk+2fjaE8LFuUnk65laymtIKWo/IrFTuFkaj+v5svwYBqM/5a/Dpu1Z0JD/wgcgipd1LiwMVxFY2nQG0=; 24:ds3nIqwV+ZVusTWKxis3HF1IEN78/rEixBLxBrMkehN6kruwat2jkq5iDTdOLbzk3uQsmH+HjyTb381+jmsIjksUnP+dB5rA9+bVZdIroNY=; 7:VNeRktViz08Uo6gNGnz3ms72yE9GtoZqYzSIXKkBqRTmC/zTM1DG5fltE2nq59CASr37rdNTsoZ9VJSVw61JqwVcHodrKBRXboZCqMbGllh7jB1yKRiRy3iLJpNWCwe5lxwgOUpJR/kqtMBo6tiVItOrMCn5LzPCqLm5iaPY64tWufCGauauNyN3HcuJa/BZlhMeVU2+NFwAoWqN8LzVa6Tmg73lHOMm9VCZfi3xF90YlYXd6zet7OtiHRbnjQHN
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 09 Feb 2018 15:22:56.9617 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 54e7d433-ff4d-424a-102a-08d56fd0ff71
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB3003
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/DgKZBqFY8ic5a15c8SXD2siKJ6w>
Subject: Re: [netmod] Adoption Poll: draft-rtgyangdt-netmod-module-tags-02
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Feb 2018 15:23:03 -0000

Oppose adoption

As others have said, there is a lack of a problem to solve.

When I ask users of a technology that uses #hashtags where they come
from, how they come into being and similar elements of procedure, I
never get an answer.  #hashtags seem to be provided to allow a storm to
gather on social media, around some vague idea, in order to put pressure
on someone or something that would otherwise be unjustified:-)

The tags listed in Section 10.2 seem just as vague and I do not see a
role for something somewhat ill-defined in YANG.

Tom Petch

----- Original Message -----
From: "Phil Shafer" <phil@juniper.net>
To: "Andy Bierman" <andy@yumaworks.com>
Cc: "NETMOD Working Group" <netmod@ietf.org>
Sent: Wednesday, February 07, 2018 6:59 PM
Subject: Re: [netmod] Adoption Poll:
draft-rtgyangdt-netmod-module-tags-02


> Andy Bierman writes:
> >The draft avoids discussion of any useful operations based on tags.
>
> Nor does it really clearly say "what" is being tagged.  The absract
> talks about "used to help classify and organize modules", but the
> Introduction lacks any expansion on this.  There's really no clear
> problem statement or a clear definition of why we need tags or what
> one would use them for.
>
> It would also be helpful to understand why "#hashtag" and the string
> format ("ietf:routing", "vendor:super-duper:...") are chosen over
> YANG identities.  It seems like identity naming standards and
inheritance
> would be good features.
>
> Also it's not clear why these would be configurable rather that
> controlled by the module author.  I'd rather have the OAM standard
> YANG module say something like:
>
>     module ietf-oam {
>         import "ietf-category" { prefix ietf-category; }
>
>         identify ietf-oam {
>             base ietf-category:ietf-standard;
>             description "This module category represents something
>                          OAM related.";
>         }
>
>         ietf-category:module-category ietf-oam;
>         ...
>     }
>
> The draft says:
>
>    Implementations that do not support the reset rpc statement
(whether
>    at all, or just for a particular rpc or module) MUST respond with
an
>    YANG transport protocol-appropriate rpc layer error when such a
>    statement is received.
>
> The entire idea of NETCONF/YANG is that the client _knows_ what it
> can safely send instead of tossing spaghetti at the wall until
> something sticks.  Avoid programming-by-error-detection, which
> creates fragile infrastructure.
>
> Use "feature" to control optional portions of a YANG module.  I'd
> suggest one feature for "reset" support and another for "read-only",
> since IMHO the idea of someone munging the categories of standard
> modules is, well, disconcerting.
>
> "Local" tags are not well explained.  The idea of a user/admin
> tagging modules means that something is broken.  Users shouldn't
> understand YANG modules.  Users use applications, some of which are
> home-grown.  Is "local" appropriate for my "audit interfaces" script?
>
> 6.1 is missing the list "module-tags".
>
> 9.1 advocates putting vital information in the description string,
> which is IMHO not a good idea.  We want to put as much information
> in machine-readable format as possible, so I can ask ietf.org
> questions like "give me a list of ietf-oam-related yang modules"
> and get a nice list.
>
> It also talks about "SHOULD" and "MAY" tags without giving any
> clue as to why or when this would be appropriate or useful.
>
> So my vote would be that this document needs some significant work
> and expansion before it's a supportable draft.  I think the authors
> have more in their heads than they've put into the draft and I'd
> like to see the rest of their thoughts.
>
> Thanks,
>  Phil
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod