Re: [Netconf] WG adoption poll draft-zheng-netconf-udp-pub-channel-00
Andy Bierman <andy@yumaworks.com> Thu, 24 August 2017 16:57 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 E962C126BF0 for <netconf@ietfa.amsl.com>; Thu, 24 Aug 2017 09:57:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20150623.gappssmtp.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 acjj4AYNJP6e for <netconf@ietfa.amsl.com>; Thu, 24 Aug 2017 09:57:29 -0700 (PDT)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (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 66131126B6D for <netconf@ietf.org>; Thu, 24 Aug 2017 09:57:29 -0700 (PDT)
Received: by mail-wm0-x236.google.com with SMTP id b189so323181wmd.0 for <netconf@ietf.org>; Thu, 24 Aug 2017 09:57:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=aIbULZEce/m0g9kw+I2O3S9t74NDBIlVvShanvjrPus=; b=Ou+gwM+V0bxvRiO8kEZGG6O8SP5RKuVdgnZlOyiqxaPFYMgO87+6joW/e7rDanQbOE Di2rZeuyhAMm3kNnWJSi1GfiZGCcVVcXETbc4UtQotQesP5zkNOu/ls+aYO5aEWyzTmC wkpfdfcDZf2DOOSXZC1cJ8DQ5wmx40YV+yJfwJfFj0o8Vo5/6A2rnCwS36OTccuvXcfF BAdjL9NdIBiX6l/sfidobNQRn4fYFCTRouf1EXhA/4mPSNskcXHEywD/2odSbCUPKu+l atFMjRrE7Ch+eo/elXmi9qLYLbVrHEK6FPR6C/70tdsrCBdehHOsUSlVpiSngMvEIY7p Hdgg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=aIbULZEce/m0g9kw+I2O3S9t74NDBIlVvShanvjrPus=; b=pR1lxsuKycopOnE9wKd4F1WBj2Z3/eKN6zj5OQeBl0ZlgpnbGmHcvfJBnXuPoJXm6z 1E79sITK5Rkk/ez2L/wBr/Q9AQ6X5kMXmCTL36XGzi8W4zexEI9Rzb5stsCI9NWKPYWW 1rSTZ+xITxkUz8INSsFBYm5ItXyjvF0uSvwQkXkFnch45wJjZ+3y6z4o+hkCPOH5i192 39SJRLV57yAbQJ8IN/K/lc/osfyirmFahZXw5YBUQwZP9hrFeLbjUWgmACeH5Fngvqxb rsEcHIWO5WApXAg5HEqeHVr5EzdMxwzNOOB5rh0/GaMH0O7MtnBPdCR5J8k8ufJjMffX nGzA==
X-Gm-Message-State: AHYfb5hfHuPmMXPUTES9NIyQTMV9R0EiP3HruisG8bQWX3R9fHvR93Mi 74g4s6cmkKv/sgbNXUQSxbQjdz/XYuVX
X-Received: by 10.28.159.141 with SMTP id i135mr511969wme.153.1503593847759; Thu, 24 Aug 2017 09:57:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.164.221 with HTTP; Thu, 24 Aug 2017 09:57:27 -0700 (PDT)
In-Reply-To: <37CC29AB-6487-46EA-ADFE-48C3D29DAF6D@gmail.com>
References: <05545A83-FEB9-486F-9003-8ADD500D5884@juniper.net> <5A5B4DE12C0DAC44AF501CD9A2B01A8D8E8D3F56@dggemm512-mbx.china.huawei.com> <1F38FB23-119A-4E36-8D5F-E43B48DE7110@gmail.com> <BBA82579FD347748BEADC4C445EA0F21A2417C14@NKGEML515-MBX.china.huawei.com> <0E62E635-4708-40D0-A0E5-2850C9567B84@gmail.com> <BBA82579FD347748BEADC4C445EA0F21A2418160@NKGEML515-MBX.china.huawei.com> <37CC29AB-6487-46EA-ADFE-48C3D29DAF6D@gmail.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Thu, 24 Aug 2017 09:57:27 -0700
Message-ID: <CABCOCHT_LbnBMviEqdJqO+dzs4nHWsip2sAvXj7ms_r_iCrtcA@mail.gmail.com>
To: Giles Heron <giles.heron@gmail.com>
Cc: Tianran Zhou <zhoutianran@huawei.com>, "netconf@ietf.org" <netconf@ietf.org>
Content-Type: multipart/alternative; boundary="001a1144e7f62ecaf0055782b970"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/T2vVz_UwTGdRKH_6DSfh8V9smWI>
Subject: Re: [Netconf] WG adoption poll draft-zheng-netconf-udp-pub-channel-00
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Network Configuration WG mailing 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: Thu, 24 Aug 2017 16:57:33 -0000
On Thu, Aug 24, 2017 at 4:35 AM, Giles Heron <giles.heron@gmail.com> wrote: > Hi Tianran, > > even if you’re adapting UDP for publication of YANG-modelled data (note > you’re NOT adapting it for publication or NETCONF/RESTCONF) I suspect you > can still build upon work others have done on reliable UDP mechanisms etc. > Even RTP does most of what you want (as it has sequence numbers, > timestamps, sender IDs, support for different payload encodings etc.) - > through granted it is targeted at a very different application space. > > and if you do persist in trying to define your own transport then it might > be worth thinking about whether you need a length field, whether > reliability and authentication are per-stream (rather than per-packet as > currently defined) and so on... > > I don't understand why we bother to organize the IETF into areas of expertise, if we are just going to ignore that and produce ad-hoc point solutions in any WG. IMO the NETCONF WG does not have the transport area expertise to to a great job on this work. Clearly the transport area has the experts to understand all pre-existing solutions and all pre-existing issues (like congestion). How is the IESG going to ensure that there are sufficient transport area experts involved in the entire development cycle for this standard? Giles > Andy > > > On 24 Aug 2017, at 06:45, Tianran Zhou <zhoutianran@huawei.com> wrote: > > > > Hi Giles, > > > > I just updated the draft submission, so as to answer your question. > Please see: > > https://datatracker.ietf.org/doc/draft-zheng-netconf-udp-pub-channel/ > > > > I tried to make it a complete work with both ps and solution. I also > separate the subscription model from this document. As things progressed, > now maybe a separate ps is not necessary to be published as a support > documents. > > > > We are not going to define a general purpose transport, but to adapt UDP > for publication of NETCONF/RESTCONF. It's highly related to YANG Push work. > > The publication channel behavior will highly depend on the > configuration/subscription. > > So I feel NETCONF is the right place to do this extension. > > And I believe the show-hands on the NETCONF meeting showed this work is > important and can be done in NETCONF. > > > > Thanks, > > Tianran > >> -----Original Message----- > >> From: Giles Heron [mailto:giles.heron@gmail.com] > >> Sent: Wednesday, August 23, 2017 9:57 PM > >> To: Tianran Zhou > >> Cc: netconf@ietf.org > >> Subject: Re: [Netconf] WG adoption poll > >> draft-zheng-netconf-udp-pub-channel-00 > >> > >> Hi Tianran, > >> > >> sure - so maybe it’d be better to split this into 2 drafts (one for the > >> problem statement and one for the solution)? That way you can progress > those > >> separately. > >> > >> Re UDP vs TCP my point was more that it seems strange to define your own > >> transport in a NETCONF draft. Adding reliability to UDP is a solved > problem > >> (many times over) so you should be able to pick one of the existing > solutions. > >> > >> Giles > >> > >>> On 23 Aug 2017, at 09:28, Tianran Zhou <zhoutianran@huawei.com> wrote: > >>> > >>> Hi Giles, > >>> > >>> Thank you very much for your review and comments. > >>> This version we were going to state the problem, raise possible issues > >> that may need to solve, and attract WG interests. So there are some TBDs > >> in the detailed solution part. > >>> We hope the working group can adopt this work, and we can work on the > >> solution together with the community contributions. > >>> Since last meeting, we keep moving forward, and are working on the new > >> revision internally. > >>> In line, please see my reply. > >>> > >>> Thanks, > >>> Tianran > >>> > >>>> -----Original Message----- > >>>> From: Netconf [mailto:netconf-bounces@ietf.org] On Behalf Of Giles > >>>> Heron > >>>> Sent: Tuesday, August 22, 2017 6:39 PM > >>>> To: netconf@ietf.org > >>>> Subject: Re: [Netconf] WG adoption poll > >>>> draft-zheng-netconf-udp-pub-channel-00 > >>>> > >>>> There seem to be a few issues with this draft: > >>>> > >>>> 1) it suggests a 32 bit field for device ID and then suggests > generating > >>>> it from the MAC address. 48 into 32 doesn’t go. Perhaps an EUI-64 > makes > >>>> more sense? Or do you even need this given that UDP packets tend to > >>>> have source IP addresses? > >>> > >>> [ztr] We were to use the device ID to indicate the source of the data. > >> Just as you suggested, the UDP session identifier can be used. So in the > >> new version, we are going to use an message generator id for the device > >> level and plus the src-dst IP as well as port number. > >>> > >>>> Or are you thinking in terms of NAT? > >>> [ztr] The NAT issue is a good catch, which we did not think about. We > >> assumed the device management port/interface and the collector are in > the > >> same private network. Do you have any use case that the NAT will be used > >> when collecting data? > >>> > >>>> Or of correlating > >>>> notifications from different line-cards on the same system that may > >>>> have different source IP addresses? > >>> [ztr] We suggest all the line cards on the same system use the same > source > >> IP address. But the case you mentioned may happen. In this case, I think > >> the collector/subscriber may have the mapping from the source IP to > device. > >>> > >>> > >>>> 2) the timestamp has 32 bits each of seconds and microseconds and > >>>> says those are as per RFC3339. From my reading of RFC3339 it encodes > >>>> dates/times as strings. > >>> [ztr] Yes, it is not a suitable reference. We meant to say the encoding > >> will support the expression in RFC3339. But it seems the timestamp on > message > >> generation is not so important to be accurate. So we tend to modify to: > >>> "The Notification-Time, is the time at which the message leaves the > >>> exporter, expressed in seconds since the UNIX epoch of 1 January > >>> 1970 at 00:00 UTC, encoded as an unsigned 32-bit integer." > >>> > >>>> 3) building your own reliability mechanism on top of UDP seems like a > >>>> strange choice. Why not just use TCP if you want reliable delivery? > >>>> Or re-use existing work on adding reliability to UDP if you see > >>>> issues with TCP? (in which case explain how reliability based on UDP > >> is better than TCP). > >>> [ztr] We are not going to provide the full reliability mechanism for > UDP. > >> We just want to provide necessary support (sequence number) from the > >> transport. Then the application can decide the reaction to the packet > loss/ > >> reordering or so. > >>> In addition, I think the reliability may also have different levels. > The > >> application may not care about any packet loss, or may need to record > the > >> packet loss but not need retransmission, or need retransmission but no > >> ordering requirement from transport,... Simply using TCP seems not a > good > >> option. > >>> > >>>> 4) big chunks of the draft are left TBD (e.g. selecting encodings, > adding > >>>> authentication/encryption options). Again there may be work you can > >> reuse > >>>> there rather than defining your own. > >>> [ztr] Yes, based on the discussion in the community, the coming update > >> will focus on the necessary parts. For example, the subscription model > may > >> move to a separate document. And we are not going to create > authentication > >> algorithms, but to suggest algorithms and how to truncate to fit in the > >> header field. We will reuse existing work as much as possible. > >>> > >>>> sections 1 - 3 are generally ok - but don’t really say anything we > >>>> didn’t know already... > >>>> > >>>> Giles > >>>> > >>>>> On 22 Aug 2017, at 02:46, Lizhenbin <lizhenbin@huawei.com> wrote: > >>>>> > >>>>> Yes/Support. > >>>>> > >>>>> Best Regards, > >>>>> Zhenbin(Robin) > >>>>> > >>>>> > >>>>> > >>>>> -----邮件原件----- > >>>>> 发件人: Netconf [mailto:netconf-bounces@ietf.org] 代表 Kent Watsen > >>>>> 发送时间: 2017年8月22日 6:04 > >>>>> 收件人: netconf@ietf.org > >>>>> 主题: [Netconf] WG adoption poll > >>>>> draft-zheng-netconf-udp-pub-channel-00 > >>>>> > >>>>> All, > >>>>> > >>>>> This is start of a two-week poll on making the following draft a > >>>>> NETCONF > >>>> working group document: > >>>>> > >>>>> draft-zheng-netconf-udp-pub-channel-00 [1] > >>>>> > >>>>> Please send email to the list indicating "yes/support" or "no/do not > >>>> support". If indicating no, please state your reservations with the > >>>> document. If yes, please also feel free to provide comments you'd > >>>> like to see addressed once the document is a WG document. > >>>>> > >>>>> > >>>>> [1] > >>>> https://tools.ietf.org/html/draft-zheng-netconf-udp-pub-channel-00 > >>>>> > >>>>> > >>>>> Thank you, > >>>>> Kent (and Mahesh) > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> Netconf mailing list > >>>>> Netconf@ietf.org > >>>>> https://www.ietf.org/mailman/listinfo/netconf > >>>>> _______________________________________________ > >>>>> Netconf mailing list > >>>>> Netconf@ietf.org > >>>>> https://www.ietf.org/mailman/listinfo/netconf > >>>> > >>>> _______________________________________________ > >>>> Netconf mailing list > >>>> Netconf@ietf.org > >>>> https://www.ietf.org/mailman/listinfo/netconf > > > > _______________________________________________ > Netconf mailing list > Netconf@ietf.org > https://www.ietf.org/mailman/listinfo/netconf >
- [Netconf] WG adoption poll draft-zheng-netconf-ud… Kent Watsen
- [Netconf] 答复: WG adoption poll draft-zheng-netcon… Lizhenbin
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Giles Heron
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Bert Wijnen (IETF)
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Andy Bierman
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Alexander Clemm
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Eric Voit (evoit)
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Tianran Zhou
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Giles Heron
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Tianran Zhou
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Giles Heron
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Andy Bierman
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Alexander Clemm
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Andy Bierman
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Alexander Clemm
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Tianran Zhou
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Giles Heron
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Alexander Clemm
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Qin Wu
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Igor Bryskin
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Henk Birkholz
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Tianran Zhou
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Xufeng Liu
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Susan Hares
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Kent Watsen
- Re: [Netconf] WG adoption poll draft-zheng-netcon… Tianran Zhou