Re: [netmod] Publication has been requested for draft-ietf-netmod-module-tags-04
Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Wed, 13 February 2019 06:53 UTC
Return-Path: <j.schoenwaelder@jacobs-university.de>
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 007F512D4EF for <netmod@ietfa.amsl.com>; Tue, 12 Feb 2019 22:53:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 d2Ju0KxubLVD for <netmod@ietfa.amsl.com>; Tue, 12 Feb 2019 22:53:14 -0800 (PST)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B8C012D4E6 for <netmod@ietf.org>; Tue, 12 Feb 2019 22:53:14 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id CB3F2B31; Wed, 13 Feb 2019 07:53:11 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id KLmcWSEO3NKl; Wed, 13 Feb 2019 07:53:11 +0100 (CET)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas5.jacobs-university.de (Postfix) with ESMTPS; Wed, 13 Feb 2019 07:53:11 +0100 (CET)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id B448F20054; Wed, 13 Feb 2019 07:53:11 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id W-Zulzmsta6K; Wed, 13 Feb 2019 07:53:11 +0100 (CET)
Received: from exchange.jacobs-university.de (sxchmb04.jacobs.jacobs-university.de [10.70.0.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "exchange.jacobs-university.de", Issuer "DFN-Verein Global Issuing CA" (verified OK)) by hermes.jacobs-university.de (Postfix) with ESMTPS id 4698420055; Wed, 13 Feb 2019 07:53:11 +0100 (CET)
Received: from anna.localdomain (10.50.218.117) by sxchmb03.jacobs.jacobs-university.de (10.70.0.155) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.1591.10; Wed, 13 Feb 2019 07:53:10 +0100
Received: by anna.localdomain (Postfix, from userid 501) id 747C3300655A2F; Wed, 13 Feb 2019 07:53:09 +0100 (CET)
Date: Wed, 13 Feb 2019 07:53:09 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Joel Jaeggli <joelja@gmail.com>
CC: netmod@ietf.org
Message-ID: <20190213065309.algwcdny2k2x57ss@anna.jacobs.jacobs-university.de>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Joel Jaeggli <joelja@gmail.com>, netmod@ietf.org
References: <155001540814.8555.686066688931046366.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <155001540814.8555.686066688931046366.idtracker@ietfa.amsl.com>
User-Agent: NeoMutt/20180716
X-ClientProxiedBy: SXCHMB01.jacobs.jacobs-university.de (10.70.0.120) To sxchmb03.jacobs.jacobs-university.de (10.70.0.155)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/0D1ZjrlZ6AaW9pRY0xHEWyOhSt4>
Subject: Re: [netmod] Publication has been requested for draft-ietf-netmod-module-tags-04
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 13 Feb 2019 06:53:17 -0000
On Tue, Feb 12, 2019 at 03:50:08PM -0800, Joel Jaeggli wrote: > Joel Jaeggli has requested publication of draft-ietf-netmod-module-tags-04 as Proposed Standard on behalf of the NETMOD working group. > > Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-netmod-module-tags/ > I just looked at the latest diff and I stumbled over the example using tags like ietf:rfc8199-element and ietf:routing and while I had an intuitive idea what ietf:routing may mean, I was pretty clueless what ietf:rfc8199-element is. Back in the old SNMP days, we actually learned that using RFC numbers in labels is not always a good idea because definitions sometimes get replaced or moved to other RFCs. If the idea is to further scope IETF defined tags (there may be multiple 'element' tags), why does this additional scoping need not apply to ietf:routing? So bottom line, should the tags _all_ be of the form - ietf:rfcxxxx:label or - ietf:rfcxxxx-label or - ietf:scope-label or - ietf:scope:label or - ietf:label where scope indicates the topic of the RFC defining the label (avoiding the embedding of the RFC number). I think it will be good if the ietf: namespace is somewhat organized from the start and it is not so good if the initial document is already using different forms. /js PS: I also wonder why this document defines ietf:lmp or more precisely what exactly this is. When do I use ietf:protocol? When does it apply and when not? Does it apply to ietf-system.yang since it among other things sets parameters for ntp? I also wonder what the life cycle management of these tag definitions is. If it turns out that tags are underspecified, can I deprecate or obsolete them? -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <https://www.jacobs-university.de/>
- [netmod] Publication has been requested for draft… Joel Jaeggli
- Re: [netmod] Publication has been requested for d… Juergen Schoenwaelder
- Re: [netmod] Publication has been requested for d… Christian Hopps
- Re: [netmod] Publication has been requested for d… Juergen Schoenwaelder
- Re: [netmod] Publication has been requested for d… Christian Hopps
- Re: [netmod] Publication has been requested for d… Juergen Schoenwaelder
- Re: [netmod] Publication has been requested for d… Christian Hopps
- Re: [netmod] Publication has been requested for d… Juergen Schoenwaelder
- Re: [netmod] Publication has been requested for d… Robert Wilton
- Re: [netmod] Publication has been requested for d… Christian Hopps
- Re: [netmod] Publication has been requested for d… Juergen Schoenwaelder
- Re: [netmod] Publication has been requested for d… Martin Bjorklund
- Re: [netmod] Publication has been requested for d… Christian Hopps
- Re: [netmod] Publication has been requested for d… Martin Bjorklund