Re: [netmod] 答复: FW: a question about ietf-hardware yang module

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Thu, 27 June 2019 20:01 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 2CD0A12017A for <netmod@ietfa.amsl.com>; Thu, 27 Jun 2019 13:01:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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 O5zveEicoYnv for <netmod@ietfa.amsl.com>; Thu, 27 Jun 2019 13:01:23 -0700 (PDT)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AFCA12004E for <netmod@ietf.org>; Thu, 27 Jun 2019 13:01:22 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id C5B7C83E; Thu, 27 Jun 2019 22:01:20 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.198]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id WuRlvs5Uz7Nk; Thu, 27 Jun 2019 22:01:20 +0200 (CEST)
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 "DFN-Verein Global Issuing CA" (verified OK)) by atlas5.jacobs-university.de (Postfix) with ESMTPS; Thu, 27 Jun 2019 22:01:20 +0200 (CEST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by hermes.jacobs-university.de (Postfix) with ESMTP id 6B7542012C; Thu, 27 Jun 2019 22:01:20 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10028) with ESMTP id AB0Dis-w5UHh; Thu, 27 Jun 2019 22:01:20 +0200 (CEST)
Received: from exchange.jacobs-university.de (sxchmb03.jacobs.jacobs-university.de [10.70.0.155]) (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 E2B7920128; Thu, 27 Jun 2019 22:01:19 +0200 (CEST)
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.1713.5; Thu, 27 Jun 2019 22:01:19 +0200
Received: by anna.localdomain (Postfix, from userid 501) id C5EB5300A8CA55; Thu, 27 Jun 2019 22:01:18 +0200 (CEST)
Date: Thu, 27 Jun 2019 22:01:18 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Martin Bjorklund <mbj@tail-f.com>
CC: <frank.fengchong@huawei.com>, <andy@yumaworks.com>, <netmod@ietf.org>
Message-ID: <20190627200118.5el3ih6frka5elmh@anna.jacobs.jacobs-university.de>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Martin Bjorklund <mbj@tail-f.com>, frank.fengchong@huawei.com, andy@yumaworks.com, netmod@ietf.org
References: <20190627054059.a5uqmzlxp4f5nwwp@anna.jacobs.jacobs-university.de> <20190627.165908.69005367729631551.mbj@tail-f.com> <20190627180157.4o7lxzwh6hzt3r6l@anna.jacobs.jacobs-university.de> <20190627.215256.473320173886007836.mbj@tail-f.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20190627.215256.473320173886007836.mbj@tail-f.com>
User-Agent: NeoMutt/20180716
X-ClientProxiedBy: SXCHMB04.jacobs.jacobs-university.de (10.70.0.156) To sxchmb03.jacobs.jacobs-university.de (10.70.0.155)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/Zr6LTQo7hnp8o3aSNASlRg7APVw>
Subject: Re: [netmod] =?utf-8?b?562U5aSNOiAgRlc6IGEgcXVlc3Rpb24gYWJvdXQgaWV0?= =?utf-8?q?f-hardware_yang_module?=
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: Thu, 27 Jun 2019 20:01:25 -0000

On Thu, Jun 27, 2019 at 09:52:56PM +0200, Martin Bjorklund wrote:
> > Yes, good point, I think the phrase "by a different hardware
> > component" should be removed. It seems last-change should change when
> > I unplug a component and I plug it back shortly after, i.e., a
> > component is replaced by itself. So we have:
> > 
> >         "The last time a new hardware component has been added to the
> >          '/hardware/component' list, or a hardware component has been
> >          removed from the '/hardware/component' list, or a hardware
> >          component in the '/hardware/component' list has been
> >          replaced."
> 
> I think that this is still not clear what it means that a component
> has been replaced.  Do you mean "replaced by a different hardware
> component"?
> 
> Otherwise (unplug then plug in the same component), the system either
> detects the removal and thus updates last-change, or it doesn't detect
> the quick removal/insertion, and then it can't do anything.  Thus, I
> don't think this case needs special treatment, and the text could be
> just:
> 
>          "The last time a new hardware component has been added to the
>           '/hardware/component' list, or a hardware component has been
>           removed from the '/hardware/component' list."
>

The question is whether every implementor will figure out that if the
component found in some slot x-y-z is different from what is expected
to be in slot x-y-z, this must be seen as a remove + add combination.
If we include 'replace', then it may be clearer that even in the case
where what is in slot x-y-z has changed, the last-change must be
updated. (That is, the list element with the same name still exists
but it is different from what was there before with the same name.)

/js

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