Re: [Netconf] Minutes 14-Dec: NETCONF/RESTCONF/HTTP2 Subscription & Event drafts

"Eric Voit (evoit)" <evoit@cisco.com> Fri, 16 December 2016 17:30 UTC

Return-Path: <evoit@cisco.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 1670B1296E8; Fri, 16 Dec 2016 09:30:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.418
X-Spam-Level:
X-Spam-Status: No, score=-17.418 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.896, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 exHIWYEc2GM2; Fri, 16 Dec 2016 09:30:35 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F3081296CD; Fri, 16 Dec 2016 09:30:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2448; q=dns/txt; s=iport; t=1481909435; x=1483119035; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=IOaMEiWvoGMLeP88C7qi8KUITG10zTDzgfSZjSMm5gc=; b=Ddf//CFObsZZwVi6q04NGzZuLkXgZOhq7m9/iraUQXc7ZOQ8OJF+xjeK 3/s7CBJj2kN4073ynzSuH1NWTNCpGMQ04w16v7rPSMmqCJvpOJZCcUevZ E83mfL0UpaW7JkQj1JHQJy7E54DxoB3rpWS6iDYLJPu3C30CEA8VQvqEx M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AUAQD4I1RY/4UNJK1CGhkBAQEBAQEBAQEBAQcBAQEBAYM3AQEBAQEfWoEGB41HlleSfoIPggkqhXgCghg/FAECAQEBAQEBAWIohGgBAQEDARIoNAsFCwIBCA4HAw0LBgYKMiUBAQQOBQgaiEEIDi6aAwGQHoNYh0cBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYY2hFmBPYFGgguFEwWacAGGUYpagX2FA4lWjhmEDgEfN4EiKYNUHBiBRXIBh2+BDQEBAQ
X-IronPort-AV: E=Sophos;i="5.33,358,1477958400"; d="scan'208";a="182328434"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 16 Dec 2016 17:30:34 +0000
Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id uBGHUXJm021391 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 16 Dec 2016 17:30:34 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-012.cisco.com (64.101.220.152) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 16 Dec 2016 12:30:33 -0500
Received: from xch-rtp-013.cisco.com ([64.101.220.153]) by XCH-RTP-013.cisco.com ([64.101.220.153]) with mapi id 15.00.1210.000; Fri, 16 Dec 2016 12:30:33 -0500
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Martin Bjorklund <mbj@tail-f.com>
Thread-Topic: [Netconf] Minutes 14-Dec: NETCONF/RESTCONF/HTTP2 Subscription & Event drafts
Thread-Index: AdJXEcE9YXnjTzr8TlarA4PrbNqzqAAmlqUAAAOk31A=
Date: Fri, 16 Dec 2016 17:30:33 +0000
Message-ID: <1faa6961013d426291bebc9272a715bf@XCH-RTP-013.cisco.com>
References: <37cf381a875e45b8a9da6639195c3fc9@XCH-RTP-013.cisco.com> <20161216.105306.1840712711228239629.mbj@tail-f.com>
In-Reply-To: <20161216.105306.1840712711228239629.mbj@tail-f.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.56.232]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/1Oerd9ZZoxRJ32EDbrK27blgwCs>
Cc: "netconf@ietf.org" <netconf@ietf.org>, "netconf-subscriptions-dt@voit.org" <netconf-subscriptions-dt@voit.org>, "netconf-chairs@ietf.org" <netconf-chairs@ietf.org>
Subject: Re: [Netconf] Minutes 14-Dec: NETCONF/RESTCONF/HTTP2 Subscription & Event drafts
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 16 Dec 2016 17:30:37 -0000

> From: Martin Bjorklund, December 16, 2016 4:53 AM
> Hi Eric,
>
> "Eric Voit (evoit)" <evoit@cisco.com> wrote:
>> Minutes posted at:
>> https://github.com/netconf-wg/yang-push/wiki/Minutes-2016-12-14
>> 
>> As always, our DezignTM Team is a gathering of individuals providing informal 
>> input to NETCONF. We ask NETCONF WG to comment on our discussion results 
>> as a preparation for the WG consensus. Please approach Eric Voit if you want 
>> to be included directly in these meetings.
>> 
>> 
>> Meeting Materials
>> 
>> Attending
>> 
>> WebEx 
>> Recording<https://cisco.webex.com/ciscosales/lsr.php?RCID=1872c1d6b734
>> 4389bda21c54a1db071d>
>> password: JmnEiji8
>> 
>> Andy Bierman, Alexander Clemm, Ambika Tripathy, Einar Nilsen-Nygaard, 
>> Eric Voit, Tim Jenkins, Balazs Lengyel, Mahesh Jethanandani, Ambika 
>> Tripathy
>> 
>> 5277bis Scope & Naming
> 
> It is great that you publish these minutes, but this topic is an ongoing
> discussion in the WG on the ML.  So could we please continue the discussion on
> the list?

That is the intent.  All official work happens on the mailing list.  These phone conversations are just a way to more quickly get input, feedback, thoughts, new directions, etc.  All NETCONF participants are welcome to join in.

> Hmm, you wrote split between 5277bis and yang-push; maybe this is a new
> issue?  The current discussion is re. the split between 5277bis and event-
> notifications.

Yes, this was the topic.  We were revisiting discussions from the last year on whether the requirements we have been working for yang-push are also needed for an evolved event notifications capability.  The thinking from the call is yes.  This also matches to Andy's requirement list from the Dec 9th Use Case thread.

Beyond this while it is perhaps possible to put band-aids around 5277, this wouldn't be preferable.  For example transport independence would not be achieved, also you would still have to build a parallel control plane for yang-push with its own independent set of operations/diagnostics/troubleshooting/etc.  (As an FYI on each individuals' thinking, there are supplementary details on the WebEx recording from 5:58-16:54.)   

So at this point the authors believe it appropriate to continue down the common control plane approach. 

Eric 

> 
> /martin