Re: [netconf] Adoption-suitability for draft-unyte-netconf-udp-notif

Mahesh Jethanandani <mjethanandani@gmail.com> Mon, 10 August 2020 21:47 UTC

Return-Path: <mjethanandani@gmail.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 84C643A0D84 for <netconf@ietfa.amsl.com>; Mon, 10 Aug 2020 14:47:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Ko4Ij-7xcS7P for <netconf@ietfa.amsl.com>; Mon, 10 Aug 2020 14:47:17 -0700 (PDT)
Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E09013A0D78 for <netconf@ietf.org>; Mon, 10 Aug 2020 14:47:17 -0700 (PDT)
Received: by mail-pg1-x529.google.com with SMTP id o13so5693390pgf.0 for <netconf@ietf.org>; Mon, 10 Aug 2020 14:47:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=uZPnF56P7zJQfqSAXZTWrV62rPHgEG97SQYgyA5124k=; b=hQf946Q4M6kGxRK54d55PaXRVhSvl3BvHAhVaMaF7evOtG0pkzFCMgzmdbSAxr5eqI lii/CNLgEOscN1WUCjcP1S6vQuvGwNZoGWSkJZqNnwqQDP7rhQeuPfHgD2RH28/jFmzP p2cYV9BCX3ph+/XvQnMBFa65UlKF4Hk58M7ZBz7cOLoJmdUeu143NE4sKNWO0o+kiuKD Qe758YV9rGaR+rI6v+d2VEP+fSEgD1hcYQePPGg24/qTyfyc7PdurjARvflwRiyiWD8P iyz6uWSgkiiLUMgtX6niPzbIRLcQkkuQkB/44tq1KA6oCFjY3v8jg72+HBVtp33vW+cb CcjA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=uZPnF56P7zJQfqSAXZTWrV62rPHgEG97SQYgyA5124k=; b=CpNo9s7/n41STYhjLpV6j0r0SvLKUW1nsN5Kh3Atwip061s3L8N+1dxLv/asFqczs3 9B87/+DrpyJc/qOCH4Lqt4o86Rv2fMbK3EVzrXSxaOTRvGU4VUUXKYvryW5FEaeCqSKf WhYtcls+KSG+IjKFf0VzNeoGrGlJYuBqLwFGrlpga6pNUpQP1Gie7mTjSr2IsRh5BJ1O eDH1A/2t/yXvFXxTXK6eyVOZG0tUl7jv3FSlfDe/ZvMVjVaQIw6O7Qb8JbGkOfPxua+q WuAGKXxsCcXxkOEoVnzV+TLcwpaF2QB0fbdWURycJ8aqxXuVAC9z+aOM2iYdt6lqxIXv n1aw==
X-Gm-Message-State: AOAM530OVwWLCzb4jw/jqOPCDSXhHsRVRH6yKx5Isr7fkTugmwXvkOb/ 7+5AazA9ntmc5/GalztjbSFBZkeF
X-Google-Smtp-Source: ABdhPJz+EIJquowvX0OzT3wwl2XqYEhmhqGxoH8fFeqUM3iezlOQhIDFlFQ4c5U0SdhBjC+ffPcGBQ==
X-Received: by 2002:a62:18ce:: with SMTP id 197mr2969738pfy.85.1597096037207; Mon, 10 Aug 2020 14:47:17 -0700 (PDT)
Received: from ?IPv6:2601:647:5600:5020:89a1:175d:59c8:8fe? ([2601:647:5600:5020:89a1:175d:59c8:8fe]) by smtp.gmail.com with ESMTPSA id 5sm14248986pfw.25.2020.08.10.14.47.15 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Aug 2020 14:47:15 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <BA79D8B5-3173-49FE-AA59-67B77191DC08@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C08F1399-00A6-4CD0-B2C6-E0FE8918BC22"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.6\))
Date: Mon, 10 Aug 2020 14:47:14 -0700
In-Reply-To: <CABCOCHSJDtqcn+=BrW0-+VEXAkbVOUGVK2+9V+f_2akAJBZ0ww@mail.gmail.com>
Cc: "netconf@ietf.org" <netconf@ietf.org>
To: Andy Bierman <andy@yumaworks.com>
References: <01000173c0b039d4-76bb4e31-9f40-4a5d-bdac-39512c8b4e9d-000000@us-east-1.amazonses.com> <CABCOCHSJDtqcn+=BrW0-+VEXAkbVOUGVK2+9V+f_2akAJBZ0ww@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/5dH5kbi85ysMtPTKJqzJD9lfbYM>
Subject: Re: [netconf] Adoption-suitability for draft-unyte-netconf-udp-notif
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
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, 10 Aug 2020 21:47:20 -0000

Hi Andy,

> On Aug 10, 2020, at 12:37 PM, Andy Bierman <andy@yumaworks.com> wrote:
> 
> Hi,
> 
> I am trying to understand the NETCONF WG plan for UDP transport of notifications.
> 
> The WG was developing a UDP draft already I think, and it was dropped.
> https://tools.ietf.org/html/draft-ietf-netconf-udp-pub-channel-05 <https://tools.ietf.org/html/draft-ietf-netconf-udp-pub-channel-05>

In IETF 103, there was extensive discussion on draft-ietf-netconf-udp-pub-channel, with questions raised about the scope of the draft. In IETF 105 and 106, our guidance (see meeting minutes) was to repurpose the draft for a UDP notification channel, which the WG would then ultimately adopt. This draft satisfies that request. To clarify this further, the datatracker marks the new draft as a replacement for the draft-ietf-netconf-udp-pub-channel.

Mahesh & Kent (as co-chair)

> 
> Since the WG dropped this problem and work item already, why should it reverse that decision
> and start over with a new solution?
> 
> 
> Andy
> 
> 
> On Wed, Aug 5, 2020 at 3:14 PM Kent Watsen <kent+ietf@watsen..net <mailto:kent%2Bietf@watsen.net>> wrote:
> NETCONF WG,
> 
> Per the previous email sent moments ago, the chairs would like to solicit input on the following draft:
> 
>    Title: UDP-based Transport for Configured Subscriptions
>    Link: https://tools.ietf.org/html/draft-unyte-netconf-udp-notif <https://tools.ietf.org/html/draft-unyte-netconf-udp-notif>
>    Abstract:
> 
>       This document describes an UDP-based notification mechanism to
>       collect data from networking devices.  A shim header is proposed to
>       facilitate the streaming of data directly from line cards to a
>       collector.  The objective is to rely on a lightweight approach to
>       allow for higher frequency and better transit performance compared to
>       already established notification mechanisms.
> 
> 
> In particular, please discuss adoption-suitability as it regards to the following questions:
> 
>     1) is the problem important for the NETCONF WG to solve?
>     2) is the draft a suitable basis for the work?
> 
> 
> PS: this message is itself not an adoption poll, but rather an attempt to gauge interest/support for a potential future adoption poll.
> 
> NETCONF Chairs
> 
> _______________________________________________
> netconf mailing list
> netconf@ietf.org <mailto:netconf@ietf.org>
> https://www.ietf.org/mailman/listinfo/netconf <https://www.ietf.org/mailman/listinfo/netconf>
> _______________________________________________
> netconf mailing list
> netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf