Re: [CCAMP] [inventory-yang] poll for network inventory base model

Daniele Ceccarelli <daniele.ietf@gmail.com> Fri, 15 September 2023 08:45 UTC

Return-Path: <daniele.ietf@gmail.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 36DEDC14CE4C; Fri, 15 Sep 2023 01:45:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HLKjmBLlgaIF; Fri, 15 Sep 2023 01:45:39 -0700 (PDT)
Received: from mail-qv1-xf2b.google.com (mail-qv1-xf2b.google.com [IPv6:2607:f8b0:4864:20::f2b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C4DFC14CE45; Fri, 15 Sep 2023 01:45:39 -0700 (PDT)
Received: by mail-qv1-xf2b.google.com with SMTP id 6a1803df08f44-656262cd5aeso7617396d6.3; Fri, 15 Sep 2023 01:45:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1694767538; x=1695372338; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=vMFJqWPNOXuc3qM7HNvEKJaVoZvlGjFdOvS/IQFiARE=; b=HBwP8FXrw19Z/X3yojYudTSREPCDNG2yuCBN4fH9Qi8nt+hBdnN9LFulzILlmiLy7J XwgDH3J6UpY8oX8IiEcm3BL2RRuudzZDLpXmQgAei1DRH/HLY1tCHGSeleoFh0al4aOc PSIw0rKl1GUY9UO7VRz7gN7VD9anPyAzP6cfXsntoo838Y+n8cjM+HzoVTQ58g0MhtWE fj4NuS2pyhr5mxlmZ3vGOSEUrl1gfCowWm4QuQ5oyNYIkwRgHKPrYLufGhDFjyrHBNpz XFlM78DplRWQ5iuJ9WdVbtCT/J3gOVm9lqTuLNvczrEavUaZpkZL5TBomwi6yZiRNLxO UYag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694767538; x=1695372338; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=vMFJqWPNOXuc3qM7HNvEKJaVoZvlGjFdOvS/IQFiARE=; b=rmboVsStKnWyC7N/hKaVUSAc4Vjugl6626HEt9niv+GMU7F2T+ae3moRCX1aGvvu1A TWagY086sRrrOzgWiCe6O+r5+zgS1ufzgn1LoDkOWT103B6VdEu+uc3D6eeB7NcNLKjo I8JrfG5yfDXywfPLgg2ek5qqnAXPui3aI2cWl0c5wuUvpUza2raRK6hvfg9e+gt+Y8In 3o8wviTMJzNFWRbOMepIB/mR/HKATfeLcz5aIDAMyB6gaHdjH/XYyuCFmP8dVPHagrO2 AXHUIzn5m5DV/8njsmjv07rJ0mDcwFDrMTXhOImBTtjGy9o+ViCleORTPpoN0AUSpZ+b +C+A==
X-Gm-Message-State: AOJu0Yzv8fuUu09pfutcsWwKMVuYOloUjPIC0PLCYuKKNHEPyUg71c8o UeSFbJ5RtzgAgjuziNaoutElivGkPbH1BiH5VD5Yht6muWM=
X-Google-Smtp-Source: AGHT+IEQn+7a9dEM1p8d2b7Rom51Yk6rWQ8LlX5xPwm0OSUEClX/AVPDo2pRT3EBiroPYQTiQdD/1expC9wWXHZ2lLY=
X-Received: by 2002:a0c:f387:0:b0:655:e219:d4e1 with SMTP id i7-20020a0cf387000000b00655e219d4e1mr1118303qvk.21.1694767537922; Fri, 15 Sep 2023 01:45:37 -0700 (PDT)
MIME-Version: 1.0
References: <7c4effcc6c5d43a6a7ddc4735d370272@huawei.com>
In-Reply-To: <7c4effcc6c5d43a6a7ddc4735d370272@huawei.com>
From: Daniele Ceccarelli <daniele.ietf@gmail.com>
Date: Fri, 15 Sep 2023 10:45:26 +0200
Message-ID: <CAB01kMgjHGGdwJ6pHPyfgKY8Q+OnGPqHXNAAmhnbZ9Tg5Zof+Q@mail.gmail.com>
To: "maqiufang (A)" <maqiufang1=40huawei.com@dmarc.ietf.org>
Cc: "inventory-yang@ietf.org" <inventory-yang@ietf.org>, "ivy-chairs@ietf.org" <ivy-chairs@ietf.org>, opsawg <opsawg@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001325b7060561d166"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/mGnq-s1ilnHNLKh7Pbyi7xM_1x0>
Subject: Re: [CCAMP] [inventory-yang] poll for network inventory base model
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 15 Sep 2023 08:45:40 -0000

Hi working group,

Thanks a lot for all the useful comments on the different drafts.
There seems to be a split of preferences between option 1 and option 3.
Given that the interinm meeting is soon (next week), we suggest to use it
to further discuss suggestions and concerns from the working group and
defer the decision by 1 week (Sep 22nd) immediately after the interim
meeting.

In order to have a fruitful discussion at the interim meeting please
consider the following inputs:


   - Italo made a very good proposal on the split between HW only and HW+SW
   use cases. Is this something we want to pursue? Do you think it makes sense
   to start focusing on e.g. HW and then add SW on top of it?
   - When asking to adopt one draft or the other we were asking (as per
   IETF process) which you consider to be a good starting point for the
   working group to work on, not something that is ready for publication. This
   means that whatever draft we decide to adopt, we can significantly update
   it to properly cover all the different aspects of invently. With this
   regard Alex did a very good analysis in his mail. Maybe we don't need to
   make an hard choice between the draft but take the best of each. For
   example: we can take 30% of one draft and 20% of the other and build a new
   one as per option 3, if on the other side we decide to take 80% from one
   draft, then it makes more sense to start from it and build on top of that.
   - Another good point touched by Alex is the "equipment-room". We are
   supposed to cover also sites and location of the inventory. Are these
   things connected? it seems so. If the WG prefers not to address this in the
   core model and add it on top, that fine, otherwise we would suggest to have
   sites and location added (whetehr in che core model or added on top can be
   discussed).

Again we have a good proposal from Alex on the way forward, which is:

"For example, one could start with draft-ietf-ccamp-network-inventory-yang,
modifying it to remove the network-hardware-inventory container and
splitting the remaining module in two (for equipment-room and
network-elements, both of which will now be top-level containers).
Remaining modifications can be made from there.  I guess this makes me a
proponent of option 3, but with the caveat that this would not need to
restart from scratch - really an option 4 that says merge (for overall
structure and common parts, which in this case is possible) and split the
remaining difference."
We don't really care whether this is called option 1, 3 or 4 but seems to
be the most meaningful one...which is: use ccamp draft as a starting point,
implementing the modifications suggested by Alex and then incorporate the
material from the opsawg draft.

Given this deferral of the polling decision, if anyone else wants to ask
for a 10 mins slot at the interim, please do so now. We will put together
the agenda on Monday.

Thanks you everyone
Daniele & Qiufang


On Mon, Aug 28, 2023 at 8:22 AM maqiufang (A) <maqiufang1=
40huawei.com@dmarc.ietf.org> wrote:

> Hi Working Group,
>
>
>
> It’s now time to start considering how to move forward with the inventory
> base model. We have two different documents that could be used as a
> starting point for our work or, in case the working group believes none of
> them is “good enough”, we can start a brand new ID.
>
> In case the latter option is chosen, Daniele and I will write a -00
> version including just the table of content and what we’d like to be
> covered in each section. The document will then be handed over to a pool of
> authors which will bring it till the WG adoption.
>
>
>
> Hence, we will have a 3 weeks polling starting today. We decided to make
> it a bit longer than usual because this time the working group is requested
> to review two drafts instead of one.
>
>
>
> This mail starts a 3 weeks polling, terminating on September 15th,  where
> we would like the working group to express your preference among:
>
>
>
>    1. Adopt  draft-ietf-ccamp-network-inventory-yang-02 in IVY and evolve
>    it to become the network inventory base model
>    2. Adopt draft-wzwb-opsawg-network-inventory-management-03 in IVY and
>    evolve it to become the network inventory base model
>    3. Start a brand new document from scratch as described above
>
>
>
> In the week after the closure of the polling (between September 18 and 25)
> we will have an IVY interim meeting to discuss the issues/concerns raised
> during the polling ( A separate mail will be sent).
>
>
>
> Thank you,
>
>
>
> Qiufang and Daniele
>
>
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
>