Re: [netconf] draft-ietf-netconf-udp-notif-10

Andy Bierman <andy@yumaworks.com> Mon, 07 August 2023 17:31 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 4408AC151081 for <netconf@ietfa.amsl.com>; Mon, 7 Aug 2023 10:31:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.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_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=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 KHA7_69NPEEW for <netconf@ietfa.amsl.com>; Mon, 7 Aug 2023 10:30:58 -0700 (PDT)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (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 24AD8C14CE4A for <netconf@ietf.org>; Mon, 7 Aug 2023 10:30:58 -0700 (PDT)
Received: by mail-lf1-x130.google.com with SMTP id 2adb3069b0e04-4fe28e4671dso7741254e87.0 for <netconf@ietf.org>; Mon, 07 Aug 2023 10:30:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks.com; s=google; t=1691429456; x=1692034256; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=2PLaT4u/PSILO/Ut1Cze+9xzQTt7ZOpXGtBr9VXK0/o=; b=vQlgVS8QLL7lKYcucjSw3j3mmG2XiC3obDLY8pGZGK3zpJZ/AvF0qWfak0JB0EAYOv 6sSRGqmqOKw1/eCDi4fDmoDLT7OGjcSv87ZDigzLAq4Yy5gO7/jeeYZkeZr0Eqv5DcP4 m1bEmORcgU+czh8iNax9tB6786CJ3oFNnAEprIMkECIPUdmJXJkInF9oXKrEC0wFSdPv ObxbPTjhxdK2nean2hrQY1B474b8rZDJbVRKuabVej1tUmEov3YGoomqm2BBPPwUXGdc LfFK6f0D8LjEbel5Urz0A1hTVn1hNwkljr6MbCBgSleHaNwSLRT2PIQg9D6wF5UWdzIM F18Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691429456; x=1692034256; 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=2PLaT4u/PSILO/Ut1Cze+9xzQTt7ZOpXGtBr9VXK0/o=; b=AuDtZRYqsPdoAZosD+MDm1e/nfg6WCTFrah2DGckBnE8I3jjumI7QMZ6rqN+cWnqUC 8QWXrMidGZKLp0rYMS+zPkHBaO/AL6HknGXO5lX0IPn8Yuo1iFwlEv7WkY7JySOAlcD2 vWjmtnj+bAnV4i/wY9q65JDKeLNtl9WmeTUUIVYnngRO1hUL+dZCLgOpHmPyVgAzRSlb FJfMKih6FhJR5mYyBiVBKfMGIRFffZgFNpjHCExCzZx6dQJqSNqFBNMxD5sXvaoJDgVy /9JUr+B0eOPY2oScwYmoPlOPahM/ZAs6DfODmZkEg+3dNzCfwXyyI7rKAvO2nysNBGQ2 vfIA==
X-Gm-Message-State: AOJu0YxZi+bGTGSdYU7cj3U+CTCHAcCQjSdLO55o49nAllPN9VioK5BC d+Em5PaxjaChqA1oUlApwnCIqiavNdBVlB5KgItlFQ==
X-Google-Smtp-Source: AGHT+IGneQn4hLJtP5mVMngjI5WumYMx26HiPJoKDA0AzkRMwcAFat/Pbdyl8UKmAlaivM3YaVPku94NZgXu7wGhHds=
X-Received: by 2002:a05:6512:2149:b0:4fd:faa2:884c with SMTP id s9-20020a056512214900b004fdfaa2884cmr6143547lfr.29.1691429456142; Mon, 07 Aug 2023 10:30:56 -0700 (PDT)
MIME-Version: 1.0
References: <8f78607ffe354a09b5bd5c84d4bcd95d@huawei.com> <akrn4urqwqhv4gtyvi26mqoi4qidhzwhss6y5cgcrdhi5bwk65@4my3rjryaazu> <16c3471f7a5c409cbd6ca60ed252609d@huawei.com> <xx32p3wmcfnc5jhyzccieskuirnnnrqjm4lczudcddsssyr2wl@boucgytivgpb> <CABCOCHRw1m2ASyPoEQZp-mxtTmG_pThQc7qvXqkYhqyhLwcUsQ@mail.gmail.com> <tbvxe7kuwh2wevudssdiikeptiny6jl573zah2i73zk2p2lmpm@oq2n4nvvt5mz> <58bc1d6d-31a2-5b9d-15fb-8e6f8120babd@huawei.com>
In-Reply-To: <58bc1d6d-31a2-5b9d-15fb-8e6f8120babd@huawei.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Mon, 07 Aug 2023 10:30:45 -0700
Message-ID: <CABCOCHSKxzt5xsku3VasUApcsb74PMr=zinjfTWiaqs_efpzFg@mail.gmail.com>
To: Benoit Claise <benoit.claise@huawei.com>
Cc: Tianran Zhou <zhoutianran@huawei.com>, netconf <netconf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e5b6d90602589b8f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/Trm6UHATfsWsQY2cp8rgHUlkWsM>
Subject: Re: [netconf] draft-ietf-netconf-udp-notif-10
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Aug 2023 17:31:02 -0000

On Mon, Aug 7, 2023 at 12:13 AM Benoit Claise <benoit.claise@huawei.com>
wrote:

>
>
> On 8/7/2023 8:50 AM, Jürgen Schönwälder wrote:
>
> On Sat, Aug 05, 2023 at 08:44:16AM -0700, Andy Bierman wrote:
>
> Perhaps the scope of the draft should be narrowed so it is only intended to
> YANG Push or server events that do not need reliable delivery.
>
>
> So there needs to be at least a very tight applicability statement.
>
> Well, isn't obvious from the title and abstract? "UDP-based protocol for
> YANG notifications to collect data from networking devices"
> Is there really a need to say "the target of this draft is unreliable
> delivery of YANG Push b/c UDP is unreliable"
>
>
I think the segmentation issue ignores the fact that even a single segment
message may not get through.
There is no reliability at all if UDP is used. There is only a high
probability that a 1 segment message will be delivered.

Configured notifications can be for event stream or datastore subscriptions.
Event stream notifications are almost always small in size, but infrequent
so cannot be lost.
It would not hurt to discuss the use-cases in the draft and mention how
non-reliable delivery
would affect the use-case.  E.g. frequent datastore updates for telemetry
data are less sensitive
to message loss than normal network management (e.g. fault monitoring)


Regards, Benoit
>

Andy