Re: [netmod] Draft IETF 119 NETMOD Agenda posted

Andy Bierman <andy@yumaworks.com> Tue, 12 March 2024 17:31 UTC

Return-Path: <andy@yumaworks.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 91727C14F61E for <netmod@ietfa.amsl.com>; Tue, 12 Mar 2024 10:31:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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=yumaworks.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 GXQcS3gnauzv for <netmod@ietfa.amsl.com>; Tue, 12 Mar 2024 10:31:06 -0700 (PDT)
Received: from mail-pj1-x102d.google.com (mail-pj1-x102d.google.com [IPv6:2607:f8b0:4864:20::102d]) (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 33E39C14F690 for <netmod@ietf.org>; Tue, 12 Mar 2024 10:31:06 -0700 (PDT)
Received: by mail-pj1-x102d.google.com with SMTP id 98e67ed59e1d1-29b7caa88c6so4286302a91.0 for <netmod@ietf.org>; Tue, 12 Mar 2024 10:31:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks.com; s=google; t=1710264665; x=1710869465; 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=NgZAHbsDRFaEEMNUTm1OfDdA7gsqoi1IyYdaouLweKY=; b=NdctiIfNwGIXSqsv5X/bSHYJhE71Vc2qty/NNyqnFZQLVhe8VTkVmL5xzDRv5/5AFT Y9gMP7tVo5enhkihc1kK+X7smdanrtKumH4GCHf7EIc2FOWEP/hviTAhVwAaeT5felkH I1krSwXpn4udqAMJtb+BV89Rj+SysQs9MbCxkeBdb2FYuydX6NFPu/P+tNQWY2CkyPfx GMedZ65JRkPwut8kNiWWUQYwQx+zHNXuS6SaOio4ul5pTVmiPel9LxLyu3thP8okRYEo dDhUL+syyLBCGPyoWd4nvd9EEKhq552ppdE3LqUu8CUsiX1y91VS3BIXZ9uXyUc+aK/t nugQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710264665; x=1710869465; 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=NgZAHbsDRFaEEMNUTm1OfDdA7gsqoi1IyYdaouLweKY=; b=ew+7yiBkJIza+RYDLD0xGUHbuDINLtOB1XNmxAPek4nbNlwBx7IUF7EvGc3RaYsMlZ RWR5L5atOBIM98XOeNl2Nn9+Nm4jUJmZr00sMB/f7pldwfvK1T/5b5GRtOMWp7Epbdm1 hrQb3pX5YwaBfGFJj5AS4o9W0dzYDsQzih9/P+FPR+MngKEOgAn1PVG1ym+aDA8ld4fM eXy/RN8e7vkFIKl4QNjiZM1qma6y65zHeYNNx8xLL/TIfWyql0AZEcA9xX2ZPe5cDFEj UqMLOz4PZl/BDLbi4ZPWDZnijuWvPOY4blDXpBsCEgV43t2k9a4TR2z+AVGmCdHyNRyY G74w==
X-Forwarded-Encrypted: i=1; AJvYcCXCb+bsGXgIdGYLoFF8k9iHrHEKuQOdxw/bp0s8x5ANM+3EIpkfJzrY5OJ1QvzVIXethtJEfq15PWsZg9DlZH0=
X-Gm-Message-State: AOJu0YxfAkD39mt5SOYXiio4KXi+YkEuWJuxtl1mLcOjW2kgRO0iZKto Nmkiexi0XktnyLMbp+1nRXaOWJzNbgyQH/0rCffV7Lt0svl3+WhvCiXe2AosElPDMWdXmDp/nV2 qX16dzDnDmJbXF9oXi2LSQNwZ9t13DqC804JyOj7yf0Vd+C5x
X-Google-Smtp-Source: AGHT+IGs0aZ7jXifEt6l/kelOm8ix9nO11Lfon5TGGfTO2vhFc7QBlDaQG8GERn/rxiUE1Uh/5eNZ0MuFsHRV71ZcsI=
X-Received: by 2002:a17:90a:4607:b0:29b:7244:c4eb with SMTP id w7-20020a17090a460700b0029b7244c4ebmr8000023pjg.42.1710264664749; Tue, 12 Mar 2024 10:31:04 -0700 (PDT)
MIME-Version: 1.0
References: <SN6PR08MB48476A8A05B9D29691CE4A939B202@SN6PR08MB4847.namprd08.prod.outlook.com> <87a54464-97a3-4fbb-bff3-5bfbdd9775a3@labn.net> <2187a0c7e0544e729130ef8d26f8a686@huawei.com> <2A107F4D-E1A7-4638-848F-BBB5FE030768@cisco.com>
In-Reply-To: <2A107F4D-E1A7-4638-848F-BBB5FE030768@cisco.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Tue, 12 Mar 2024 10:30:53 -0700
Message-ID: <CABCOCHQW+PyNpvq62n5C-Ewm65Msmv9hG9WuO=Ht-UCh221KTg@mail.gmail.com>
To: "Jan Lindblad (jlindbla)" <jlindbla=40cisco.com@dmarc.ietf.org>
Cc: "maqiufang (A)" <maqiufang1=40huawei.com@dmarc.ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d0987806137a05ae"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/lYBCTFed4tLVPOT4X0pfIV4Qwec>
Subject: Re: [netmod] Draft IETF 119 NETMOD Agenda posted
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 12 Mar 2024 17:31:10 -0000

On Tue, Mar 12, 2024 at 9:15 AM Jan Lindblad (jlindbla) <jlindbla=
40cisco.com@dmarc.ietf.org> wrote:

> Qiufang,
>
> I'm sorry to say I'm strongly against WGLC at this time because of point
> #2 below.
>
> One of the great contributions to network automation that YANG has brought
> is that clients now have a fair chance at computing a desired configuration
> change for a network element. Maybe we need to develop a more elaborate
> model for configuration consistency relative today's "The running
> configuration datastore MUST always be valid", but have I trouble with us
> stirring up multiple interpretations and then staying silent. That's not
> the way to build interoperability.
>
> IMO we need to sort out what the rules are before we come close to WGLC,
> or else the grief outweighs the gain.
>
>

The WG does not think NMDA is too complicated or too difficult for clients
to use. I disagree.
Adding more datastores and interactions between datastores will make NMDA
even worse.
Retrieval of multiple datastores so they can be compared for transient
differences is a very complex
way to convey this state information to the client.

NMDA is too server-centric already. Maximum flexibility for the server
developer means
minimum consistency for the client developer.


Best Regards,
> /jan
>

Andy


>
> On 12 Mar 2024, at 03:44, maqiufang (A) <maqiufang1=
> 40huawei.com@dmarc.ietf.org> wrote:
>
> Hi, chairs,
>
> For system-config draft (
> https://datatracker.ietf.org/doc/draft-ietf-netmod-system-config/), the
> authors have submitted a new version to reflect the outcome of the interim,
> the main updates are following:
> 1.      Address the "origin" issue
> a.       The current document explicitly states that system configuration
> copied from <system> into <running> have its origin value being reported as
> "intended" and update the examples accordingly
> b.      Also, update the definition of "intended" origin identity in 8342
> to allow a subset of configuration in <intended> to use "system" as origin
> value
> c.       The current document states data migration is out-of-scope
> except that gives a couple of implementation examples in section 4.2
> (please feel free to propose text if you have better suggestion)
> 2.      validity of <running> alone
> a.       The current document is silent on this point. Related statements
> which requires referenced system nodes must be copied into <running> are
> removed.
> 3.      Other updates
> a.       Usage examples refinement, e.g., fix validation errors, remove
> redundancy for conciseness
>
> There is currently no open issues, thus the authors believe this draft is
> ready for WGLC, but this might be worth a broad review on the mailing list.
>
> Best Regards,
> Qiufang
> *From:* netmod [mailto:netmod-bounces@ietf.org] *On Behalf Of *Lou Berger
> *Sent:* Friday, March 8, 2024 9:44 PM
> *To:* NETMOD WG <netmod@ietf.org>
> *Cc:* netmod-chairs@ietf.org
> *Subject:* Re: [netmod] Draft IETF 119 NETMOD Agenda posted
>
>
> **IMPORTANT**
>
> Authors of WG documents,
>
> If your document has not yet been submitted to the IESG for publication
> *and* your draft is not on the agenda, please either:
> (a) request to present status or
> (b) send email to the list summarizing status by end of day (any TZ)
> Friday, March 15.
>
> In either case, please include recent changes, open issues, plan to
> resolve open issues/complete the document.
>
> Thank you!
>
> Lou (and Kent)
> On 3/7/2024 3:53 PM, Jason Sterne (Nokia) wrote:
>
> Hello NETMOD WG,
>
> A draft NETMOD agenda for IETF 119 has been published. Please review and
> let the chairs know if any changes are needed or additional topics should
> be covered.
>
> The agenda is pasted below, but here's the link to the always-current
> version:
> https://datatracker.ietf.org/meeting/119/materials/agenda-119-netmod
>
> Presenters: please provide slides to netmod-chairs@ietf.org no later than
> Sunday March 17 (any time zone).
>
> Thanks,
> Jason (+ chairs Kent and Lou)
>
> Draft Agenda for the NETMOD 119 WG Session
>
> https://datatracker.ietf.org/meeting/119/materials/agenda-119-netmod
> https://datatracker.ietf.org/meeting/119/session/netmod
> Session:
>
> Thursday, March 21, 2024
> 13:00-15:00 Brisbane (Australia - Eastern Time)
> 03:00-05:00 UTC
> 23:00-01:00 Wednesday March 20 America - Eastern Time
>
> https://www.timeanddate.com/worldclock/converter.html?iso=20240321T030000&p1=47
>
> Room: M2 https://datatracker.ietf.org/meeting/119/floor-plan?room=m2
> WG Chairs:
>
> Lou Berger (lberger at labs dot net)
> Kent Watsen (kent plus ietf at watsen dot net)
> WG Secretary
>
> Jason Sterne (jason dot sterne at nokia dot com)
> Available During Session:
>
> MeetEcho: https://meetings.conf.meetecho.com/ietf119/?session=31987
> Onsite tool: https://meetings.conf.meetecho.com/onsite119/?session=31987
> Audio Only: https://mp3.conf.meetecho.com/ietf119/31987.m3u
> Available During and After Session:
>
> Notes: https://notes.ietf.org/notes-ietf-119-netmod?both
> Slides: https://datatracker.ietf.org/meeting/119/session/netmod
> Zulip (chat):
> https://zulip.ietf.org/#narrow/stream/126-netmod/topic/ietf-119
> Drafts (TGZ):
> https://datatracker.ietf.org/meeting/119/agenda/netmod-drafts.tgz
> Drafts (PDF):
> https://datatracker.ietf.org/meeting/119/agenda/netmod-drafts.pdf
> Datatracker: https://datatracker.ietf.org/group/netmod/about/
> ICS: https://datatracker.ietf.org/meeting/119/session/31987.ics
> Available After Session:
>
> Recording: http://www.meetecho.com/ietf119/recordings#NETMOD
> Jabber Logs: https://www.ietf.org/jabber/logs/netmod
> 1) Session Intro & WG Status (10 min)
>
> Presenter: Chairs
> Chartered items: 2) YANG Versioning Update (40 min)
>
> Presenter: Rob Wilton and Joe Clarke
> Draft:
> https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-module-versioning-11
> Draft: https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-semver-14
> Non-Chartered items: 3) Validating anydata in YANG Library context (10
> min)
>
> Presenter: Ahmed Elhassany
> Draft:
> https://datatracker.ietf.org/doc/draft-aelhassany-anydata-validation-00
> 4) Philatelist and YANG time-series db (10 min)
>
> Presenter: Jan Lindblad
> Draft: https://datatracker.ietf.org/doc/draft-lindblad-tlm-philatelist-00
> Draft: https://datatracker.ietf.org/doc/draft-kll-yang-label-tsdb-00
> 5) A YANG model for Device Power Management (10 min)
>
> Presenter: Tony Li
> Draft: https://datatracker.ietf.org/doc/draft-li-ivy-power-01
> 6) YANG Full Embed (10 min)
>
> Presenter: Jean Quilbeuf or Benoir Claise
> Draft:
> https://datatracker.ietf.org/doc/draft-jouqui-netmod-yang-full-include-01
> 7) Applying COSE Signatures for YANG Data Provenance (10 min)
>
> Presenter: Diego R. Lopez
> Draft:
> https://datatracker.ietf.org/doc/draft-lopez-opsawg-yang-provenance-02
> Unallocated time: 20 min
>
>
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>