[netconf] Re: FW: New Version Notification for draft-ietf-netconf-yang-notifications-versioning-05.txt

Andy Bierman <andy@yumaworks.com> Sun, 16 June 2024 14:46 UTC

Return-Path: <andy@yumaworks.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEAE8C1519A0 for <netconf@ietfa.amsl.com>; Sun, 16 Jun 2024 07:46:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 taZeB2HRZVYU for <netconf@ietfa.amsl.com>; Sun, 16 Jun 2024 07:46:06 -0700 (PDT)
Received: from mail-pg1-x52d.google.com (mail-pg1-x52d.google.com [IPv6:2607:f8b0:4864:20::52d]) (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 8B14BC14F5EF for <netconf@ietf.org>; Sun, 16 Jun 2024 07:46:06 -0700 (PDT)
Received: by mail-pg1-x52d.google.com with SMTP id 41be03b00d2f7-6bce380eb96so2467501a12.0 for <netconf@ietf.org>; Sun, 16 Jun 2024 07:46:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks.com; s=google; t=1718549166; x=1719153966; 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=oh97yWuT2IACjY6Wcrgb/rDi+QYZtwIMgNZ5f2zpbRw=; b=fR7f2++dwnxtXesDyiuJICkx9IZNA7vF2rAaLeAqtLjQu+HEzVFIrPgCcMQ6SjSNdy SZ4rvYcZLrEESsjfXZfw+J7j2c3kMxRrAhpt78RmAc9uCpOTrTQJjHny90jCPp7mPSLb TB49/yTekLZt2KXiCS5RtxpkmOKnztEuoIOWhOPt8vFUS+dsFeg1G1RCmWX4cAZmaC4j bzlOWtXi4heO8ruWgF4qOztXIlb/AhMA0nLyH81/qc3sgUxVZTnO98IFC3JMXixLOgO5 DD7W/5xxx36SJziRm6VjIkaMBD6SI4jtcO3n0TVUTTu8IMPCagTskTI6pGFumrONO3MR GydQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718549166; x=1719153966; 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=oh97yWuT2IACjY6Wcrgb/rDi+QYZtwIMgNZ5f2zpbRw=; b=Pk7ORw7oZ3e7k+4hiuCzSyPj0x9S9RmlW3Iz+6pZdsmvG/iwASCOyrnA+RhHoAbMGF tI4ZfZHonZDOnol20ebB/zBwWCpY5Os23MV78rDE9snDExs1Lk0Ip3TrQcrVdd0Q2pN7 2gSp22igJ2Ex9h0VlEM3sn4x3OjCNmcQhW8tQwiai8Wdei/vwIaYrYoQZF57IFU8XBIR ydv5Ug6XreqDWGePZ6Dk2DdVtGQPhwcpSD8FiQSE1d1cY2T0I2v8+kDQLbewAdp1q2nX sWxCdewi5krBiokcX0AkxU2NHPGmYR+z/m4heu1LGa2uAaPXDC+aAd8zPovgEIlIWrSq jYEQ==
X-Gm-Message-State: AOJu0YykptyQcCr4t23qX2HdmBe/EL5TntA4yZ44m4k+b+Sn3ZxQKiaW PzoK6go/Jij5+DIFQlgpl0FvDaZzKM5ohMLGXEWwImt8MI5pXloljFyLy1UiIXl8/YIS+q8R+oQ i1tzbEwnXPUkiFhKDOn+Lmx/LwQFzbDmbS2Pkhg==
X-Google-Smtp-Source: AGHT+IErII54AI6abKLk8FAOFemVTK+194GfvUfd7bqiOCBz25Q4nZ8jNw+O4uA5xkc1Vq+7CcDs+Xz9SjcFl6qeZqc=
X-Received: by 2002:a05:6a20:6f88:b0:1b1:ed9d:f92e with SMTP id adf61e73a8af0-1bae82155b8mr8587556637.38.1718549165669; Sun, 16 Jun 2024 07:46:05 -0700 (PDT)
MIME-Version: 1.0
References: <171854650490.47608.1290272422705190827@ietfa.amsl.com> <bce9a04329d7431480b1b0f66d648317@swisscom.com>
In-Reply-To: <bce9a04329d7431480b1b0f66d648317@swisscom.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Sun, 16 Jun 2024 07:45:54 -0700
Message-ID: <CABCOCHSDRK948-sS_eOK5ZHXn1Zq4OM6uh6zVhLqscufRTEB2g@mail.gmail.com>
To: Thomas.Graf@swisscom.com
Content-Type: multipart/alternative; boundary="0000000000008c9a48061b02e8a8"
Message-ID-Hash: QVIZL4EL2JXWMACEXXRPHGJOOSMERC4B
X-Message-ID-Hash: QVIZL4EL2JXWMACEXXRPHGJOOSMERC4B
X-MailFrom: andy@yumaworks.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-netconf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: netconf@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [netconf] Re: FW: New Version Notification for draft-ietf-netconf-yang-notifications-versioning-05.txt
List-Id: NETCONF WG list <netconf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/1jOiRn9mu5Dc2oGtWSXUj1LDOSg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Owner: <mailto:netconf-owner@ietf.org>
List-Post: <mailto:netconf@ietf.org>
List-Subscribe: <mailto:netconf-join@ietf.org>
List-Unsubscribe: <mailto:netconf-leave@ietf.org>

On Sun, Jun 16, 2024 at 7:07 AM <Thomas.Graf@swisscom.com> wrote:

> Dear NETCONF working group,
>
>
>
> We updated the document to version -05 with the following changes:
>
>
>
>    - Resolved YANG modeling issue that within a "case" statement
>    identifiers need to be unique (
>    https://datatracker.ietf.org/doc/html/rfc7950#section-7.9.2)
>
>
>
> Thanks to Jérémie Leska from 6Wind for reporting this issue during
> implementation.
>
>
>
> Implementation will be validated at the next IETF 120 hackathon.
>
>
>
> Feedback and comments welcome.
>
>
>


I do not understand why the Orchestrator (in the message broker diagram)
cannot simply read the YANG library
of the server and check the revision date of the module.

I do not see how a single node (e.e. /foo) is sufficient to check.
In a common use-case, like interface-state, there are many modules that
augment the interface list entry.

The YANG library cannot be broken into some set of sub-contracts.
There is one contract that is described by the correct application of the
data definitions, supported features, and applied deviations.
A [module-name, revision-date] tuple does not even correctly specify a
contract subset.


> Best wishes
>
> Thomas
>

Andy


>
>
> -----Original Message-----
> From: internet-drafts@ietf.org <internet-drafts@ietf.org>
> Sent: Sunday, June 16, 2024 4:02 PM
> To: Alex Feng <alex.huang-feng@insa-lyon.fr>; Alex Huang Feng <
> alex.huang-feng@insa-lyon.fr>; Benoit Claise <benoit.claise@huawei.com>;
> Graf Thomas, INI-NET-VNC-HCS <Thomas.Graf@swisscom.com>
> Subject: New Version Notification for
> draft-ietf-netconf-yang-notifications-versioning-05.txt
>
>
>
>
>
> Be aware: This is an external email.
>
>
>
>
>
>
>
> A new version of Internet-Draft
>
> draft-ietf-netconf-yang-notifications-versioning-05.txt has been
> successfully submitted by Thomas Graf and posted to the IETF repository.
>
>
>
> Name:     draft-ietf-netconf-yang-notifications-versioning
>
> Revision: 05
>
> Title:    Support of Versioning in YANG Notifications Subscription
>
> Date:     2024-06-16
>
> Group:    netconf
>
> Pages:    26
>
> URL:
> https://www.ietf.org/archive/id/draft-ietf-netconf-yang-notifications-versioning-05.txt
>
> Status:
> https://datatracker.ietf.org/doc/draft-ietf-netconf-yang-notifications-versioning/
>
> HTMLized:
> https://datatracker.ietf.org/doc/html/draft-ietf-netconf-yang-notifications-versioning
>
> Diff:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-netconf-yang-notifications-versioning-05
>
>
>
> Abstract:
>
>
>
>    This document extends the YANG notifications subscription mechanism
>
>    to specify the YANG module semantic version at the subscription.
>
>    Then, a new extension with the revision and the semantic version of
>
>    the YANG push subscription state change notification is proposed.
>
>
>
>
>
>
>
> The IETF Secretariat
>
>
>
>
> _______________________________________________
> netconf mailing list -- netconf@ietf.org
> To unsubscribe send an email to netconf-leave@ietf.org
>