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

Thomas.Graf@swisscom.com Sun, 16 August 2020 10:27 UTC

Return-Path: <Thomas.Graf@swisscom.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 208033A0B39 for <netconf@ietfa.amsl.com>; Sun, 16 Aug 2020 03:27:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.582
X-Spam-Level:
X-Spam-Status: No, score=-1.582 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, KHOP_HELO_FCRDNS=0.212, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 uM1eqcMR9-wD for <netconf@ietfa.amsl.com>; Sun, 16 Aug 2020 03:27:00 -0700 (PDT)
Received: from mail.swisscom.com (mailout110.swisscom.com [138.188.166.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DD063A0B34 for <netconf@ietf.org>; Sun, 16 Aug 2020 03:26:59 -0700 (PDT)
Received: by mail.swisscom.com; Sun, 16 Aug 2020 12:26:47 +0200
Message-ID: <2090004314.1313658.1597573607302@ss007564>
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="----=_Part_1313656_1346019717.1597573607302"
X-Mailer: Totemo_TrustMail_(Notification)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=cgPflG06WxvkpD9v1g1/5zybwL7R5U9IrYHdgeHk8NkvgX3nswB+FRVtFW4WqJLe7ArFcNfX/iI5n8dOgHmmmypgLKhSmvZ09yGRKo/NwHLChLvUAw7qOxdDFQE/J83S8gAabMtBmXDygXTYmgPaKfo0Y5QXUWx3qIVDVYG0kIwGZ/AkSdxab865TkWygVgc9U1SCuPi0KHtFRrsKNdf5ivVHPT3KRlJrSoaVa4iRn5nE9Mvk+m8vdB5018hicYHs4L/yHx5viN1YUvsNLUxcU6+ITrb0y/nNl2Q3EpruwEjeeFUi2aMcrEn+Vf+pehYhIhWQxRHPDrHFWwicmu7OQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=aIIrMXvlgEKya6lxKRuisDRvQVl6+jDHFBQAhkUEg3c=; b=jmzulTXP32bq+5fPG+Yfki92d9ix99Fz9owl8r/1gvS1Mo/40W7tTugUK6RiottXcraVNdC96GDrEtP+IQjyby9WFDxcf0MMySs7zReBg34ugouHtZ/jhTWzMJ+JUeq1rOmdbSF6fHXWXz5lPq01ILWUPw0Uz+mG7Dmfo3MYphDxCK6SwBN/ByRSRF8xhd/GnqsbrGEtz574y7nSltRFY9534A/dPRK/kQT2Q+n805qINAxdNrxv2FetNb1aSHEykFUFIBviiw/XAb9BPe/hCX7zRdIRJxaiNR6INapgZEMARGfwxa3Mh/lYaltwxVPHVUpBa+GUL8q1r7L83xmW4Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=swisscom.com; dmarc=pass action=none header.from=swisscom.com; dkim=pass header.d=swisscom.com; arc=none
From: <Thomas.Graf@swisscom.com>
To: <andy@yumaworks.com>, <mjethanandani@gmail.com>
CC: <netconf@ietf.org>, <paolo@pmacct.net>, <pierre.francois@insa-lyon.fr>, <zhoutianran@huawei.com>
Thread-Topic: [netconf] Adoption-suitability for draft-unyte-netconf-udp-notif
Thread-Index: AQHWcodX0mBLbRaES02VUjy2aRVTDKk6hC9w
Date: Sun, 16 Aug 2020 10:26:44 +0000
References: <01000173c0b039d4-76bb4e31-9f40-4a5d-bdac-39512c8b4e9d-000000@us-east-1.amazonses.com> <CABCOCHSJDtqcn+=BrW0-+VEXAkbVOUGVK2+9V+f_2akAJBZ0ww@mail.gmail.com> <BA79D8B5-3173-49FE-AA59-67B77191DC08@gmail.com> <CABCOCHS-dFy1yozwCe5=q6fSLG4uH5RJZ+UN+ZgFmP8m0_wqdg@mail.gmail.com>
In-Reply-To: <CABCOCHS-dFy1yozwCe5=q6fSLG4uH5RJZ+UN+ZgFmP8m0_wqdg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_Enabled=True; MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_SiteId=364e5b87-c1c7-420d-9bee-c35d19b557a1; MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_Owner=Thomas.Graf@swisscom.com; MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_SetDate=2020-08-16T10:26:41.7496918Z; MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_Name=C2 General; MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_Application=Microsoft Azure Information Protection; MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_ActionId=1ab03bcf-c501-4175-b4fc-3af110ad81bc; MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_Extended_MSFT_Method=Automatic
authentication-results: yumaworks.com; dkim=none (message not signed) header.d=none; yumaworks.com; dmarc=none action=none header.from=swisscom.com;
x-originating-ip: [178.199.12.228]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d5ed3eb3-d198-40d5-dbce-08d841cedff7
x-ms-traffictypediagnostic: ZR0P278MB0122:
x-microsoft-antispam-prvs: <ZR0P278MB0122C2F449F1F42DDF90F86E895E0@ZR0P278MB0122.CHEP278.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: CUORWp5zcYsilmC5R6JVfHZq/jAoJhFXQmR91NIkdwSdhESmVhrM8/EqhfTuKU//qJfgeCPZE6krXrfwvi+8MVoBmuZHBmcMhEzXaVJjLo6VmOvl8SYKhDLGC3i5h4ykhYAKGL/EFvXyApyuToC1SgB2k1VjjCMPMua3so2+jxChDCY7vXhCXmHl180zeuveqGgT2VI1ZU+KDD+nIkVmTmaEagdUoUGKEaLYUdAFK8RZyXNIrseJDhCkCAnDN+EBPuCgkcDK7cBOqT0KZlRa6Dc+5hrpxGcXnIrg0yVjak/KAU/ADdsbi4MFwj2T0eeafRcHH9sCTzG8neEXZVM2SoLvTJkHQHXp3ugrtcbok1Ik1bkvdNwqgwjUmwR3F4JAHHNH8tYFQ306y+ldNLR4hg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:ZRAP278MB0125.CHEP278.PROD.OUTLOOK.COM; PTR:; CAT:NONE; SFS:(4636009)(376002)(396003)(136003)(39850400004)(366004)(346002)(9686003)(55016002)(8936002)(66476007)(10300500001)(71200400001)(86362001)(52536014)(66556008)(5660300002)(66446008)(64756008)(76116006)(66946007)(8676002)(966005)(316002)(6506007)(53546011)(26005)(4326008)(2906002)(10290500003)(186003)(166002)(33656002)(7696005)(66574015)(83380400001)(478600001)(110136005)(54906003); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: WLqHwSM8Xpql7BHz2dv3WBwd0VRHVMe+KwSYb5/WP2iFANFu6Khzp0irbo1AQ6kFKzRP9DYMMcfg5yCv/BMRoyjx0jWSBWnhFobNf78FsPRJtwZMfcDTjT2LEIiSOkLiC51t0mTpbOQ4yguqh40AvWLAW+ZDeJxyLZiLHvQdGeSyRPiDt8043pDnUTR44xwbLLrOBBB/8vvYteN1TrULLWvdbP010SkI4HEetNouA7mDHA08c0PC9tffQxnwdFeCxlpnwdNkNV29IGe5a9ku8C28cXsvYoyjr6fCF0AxceoDYzLhseo4dsCiou0ZWIgF9f0hxI4Th6IPPwMey/MXumR3qLGKqCHWnKEIRT0t0GlW3j4Fz2aEx/HcisVcPpo38eeVwcoNiv+6IMWx8c/5IvA801R0zuk1g4XU8MX2nGcWuqzlOP2sk53MYgAV3EEtXkQRP800c0qmOYNkDxtfzKwmIrVRVWELO6DAtEOYCzRWztBPHtTP4cqK+lO+E+sxS/qM9kUtPT8M+h3iqV1Jbpqnr+T6Sm4SQ9pyE8ON47z0NaaJSUVHDitaKdlo9rIHZsQ/lblXQj4uzn4zPPhzK6xwqN0DE5c8KSy7l6oaI4EjxyzivjVXTTqK5ydlkxjsc+si3z9XOHVlorGN/6mNzg==
x-ms-exchange-transport-forked: True
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: ZRAP278MB0125.CHEP278.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: d5ed3eb3-d198-40d5-dbce-08d841cedff7
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Aug 2020 10:26:44.8053 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 364e5b87-c1c7-420d-9bee-c35d19b557a1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: YEtagPsiSmFe90S6SbmJS+BLpg401c6azetJAHmDMPvANV+/CpzuYukGR0dsCuM7rh8p56xaZLtvCYYApil9DTdM5oPkY0WSmKKOU8k+OiE=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: ZR0P278MB0122
X-OriginatorOrg: swisscom.com
X-CFilter-Loop: Reflected
X-Trustmail: processed
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/GRkFCwYqasI7FbHdYLnmKgCQbXk>
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: Sun, 16 Aug 2020 10:27:03 -0000

Hi Mahesh,

Thank you very much for the good summarization.

Hi Andy,

Thank you very much for the feedback. I am happy to hear that you will review the document and consider to implement.


  *   Hopefully the authors will add an example of a notification in each encoding soon.
Sure, Pierre François, one of the co-authors and professor at INSA university and his colleagues already started working on an open-source YANG push library for the receiver (data-collection) to support udp-notif and distributed-notif. We planned to integrate this library into the open-source project pmacct at IETF 109 hackathon to showcase a working receiver with a first vendor implementation. Further, we are in the evaluation on what environment to build an example open-source publisher which can be taken as reference for other implementations.

It would be interesting to understand how we could potentially collaborate. I think the IETF 109 hackathon would be a good place to work and validate each other implementation. As we already were doing with BMP (BGP Monitoring protocol) in previous IETF hackathons.
https://www.ietf.org/proceedings/108/slides/slides-108-grow-ietf-108-hackathon-bmp-00. What do you think?

Best Wishes
Thomas

From: netconf <netconf-bounces@ietf.org> On Behalf Of Andy Bierman
Sent: Saturday, August 15, 2020 12:08 AM
To: Mahesh Jethanandani <mjethanandani@gmail.com>
Cc: netconf@ietf.org
Subject: Re: [netconf] Adoption-suitability for draft-unyte-netconf-udp-notif



On Mon, Aug 10, 2020 at 2:47 PM Mahesh Jethanandani <mjethanandani@gmail.com<mailto:mjethanandani@gmail.com>> wrote:
Hi Andy,


On Aug 10, 2020, at 12:37 PM, Andy Bierman <andy@yumaworks.com<mailto: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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-netconf-udp-pub-channel-05&data=02%7C01%7CThomas.Graf%40swisscom.com%7C6d61dd2dd3c3422f6c2d08d8409e8fc9%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637330397053580529&sdata=6YtbXF3DIp%2BJDhoi9flTQjWN92c6qv%2FT6sXqVRjLwCc%3D&reserved=0>

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.


I support adoption of this draft.
I am willing to work on the document, review it, and implement it.
Hopefully the authors will add an example of a notification in each encoding soon.

IMO there really should be 1 RFC that combines these documents:

     draft-unyte-netconf-udp-notif
     draft-unyte-netconf-distributed-notif
     draft-ietf-netconf-notification-messages

The single source vs. multi-source distinction does not really require separate documents.
General one-size-fits-all notification headers are too inefficient to use in
a high performance telemetry system.  Not sure where notification-messages will ever get used.
IMO these 3 documents could be a good protocol, if combined and focused correctly.


Mahesh & Kent (as co-chair)


Andy




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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-unyte-netconf-udp-notif&data=02%7C01%7CThomas.Graf%40swisscom.com%7C6d61dd2dd3c3422f6c2d08d8409e8fc9%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637330397053590475&sdata=m4ogTh90gPL4SVM2tGseQT9j6PY8ufPr5fPfNgvbK0I%3D&reserved=0>
   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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fnetconf&data=02%7C01%7CThomas.Graf%40swisscom.com%7C6d61dd2dd3c3422f6c2d08d8409e8fc9%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637330397053590475&sdata=%2BdVisZkWD%2B9yBiavHLvkYEIwFKwJeOlx7yIu%2BI4gFEU%3D&reserved=0>
_______________________________________________
netconf mailing list
netconf@ietf.org<mailto:netconf@ietf.org>
https://www.ietf.org/mailman/listinfo/netconf<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fnetconf&data=02%7C01%7CThomas.Graf%40swisscom.com%7C6d61dd2dd3c3422f6c2d08d8409e8fc9%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637330397053600443&sdata=bd3zWWkteoRA01MGWVZWAJM2wyCQH3Gs3ye9HNJ5zlU%3D&reserved=0>