Re: [Netconf] two-week review of drafts related to notifications and subscriptions

"Eric Voit (evoit)" <evoit@cisco.com> Tue, 24 October 2017 16:43 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 E5CBD139672 for <netconf@ietfa.amsl.com>; Tue, 24 Oct 2017 09:43:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level:
X-Spam-Status: No, score=-14.52 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 9srwbPZ6-EMI for <netconf@ietfa.amsl.com>; Tue, 24 Oct 2017 09:43:49 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 268051394EB for <netconf@ietf.org>; Tue, 24 Oct 2017 09:43:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4340; q=dns/txt; s=iport; t=1508863429; x=1510073029; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=jzkV+2VOQKq1hJSp/SvjW8cf5YpnYP7dlDQQrXHEWNQ=; b=f2fGPLKLQXItMIjRwiHs/fybiC/Zl2Dyg1ES55eF2qH2KTbks1buuK+2 AgaZckuj26FI/W7pOXvOZO54vj0ylOX36GwRvfzCD4wWO864S207kXbZU +Y7taMhI1oFKL55ZHl/V60H16S2pjM0hFdu36MY3/99b+VhgUDJsc4RRg Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CbAACFbe9Z/5ldJa1bGQEBAQEBAQEBAQEBBwEBAQEBg19kbicHg3OKH49JgXqWOoIRChgLhElPAhqERz8YAQIBAQEBAQEBayiFHQEBAQECAQEBIRE6CQIFCwIBCA4HBQIJHQICAiULFRACBAENBQiKEAgQqAOCJ4shAQEBAQEBAQEBAQEBAQEBAQEBAQEBGAWBD4IfggeBUIFpgyqDMoRngmEFh0+aHgKHY4dHhUCCHoV6iUCBVooliy0CERkBgTgBHziBW3oVSYJkgxGBTnaKYIERAQEB
X-IronPort-AV: E=Sophos;i="5.43,428,1503360000"; d="scan'208";a="309882402"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Oct 2017 16:43:48 +0000
Received: from XCH-RTP-011.cisco.com (xch-rtp-011.cisco.com [64.101.220.151]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v9OGhl7U030707 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 24 Oct 2017 16:43:48 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-011.cisco.com (64.101.220.151) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 24 Oct 2017 12:43:47 -0400
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.1320.000; Tue, 24 Oct 2017 12:43:47 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Kent Watsen <kwatsen@juniper.net>, "netconf@ietf.org" <netconf@ietf.org>
CC: "Mahesh Jethanandani (mahesh)" <mahesh@cisco.com>
Thread-Topic: [Netconf] two-week review of drafts related to notifications and subscriptions
Thread-Index: AQHTTFLE2+KEwzxeaUmOUUOjdzqfBKLzLbJQ
Date: Tue, 24 Oct 2017 16:43:47 +0000
Message-ID: <836bcee815bc47e983aaf94b9c9f0933@XCH-RTP-013.cisco.com>
References: <1FC7C28B-5F6B-46ED-BAC4-92340A9291F5@juniper.net>
In-Reply-To: <1FC7C28B-5F6B-46ED-BAC4-92340A9291F5@juniper.net>
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.228]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/YhOsxPzU3drEvhuqDC3_o5lCcPI>
Subject: Re: [Netconf] two-week review of drafts related to notifications and subscriptions
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: Tue, 24 Oct 2017 16:43:51 -0000

Hi Kent,
Hi Mahesh,

> From: Netconf, October 23, 2017 7:01 PM
> 
> Thank you to all those who participated in the review of the drafts related to
> event notifications.  Recall that our interest was to get a heartbeat from the
> working group regarding the readiness of these drafts to progress to Last Call.
> As we see it, most of the discussion centered on the subscribed-notifications
> draft, and we're optimistic that the next update of that draft could be in
> shooting distance to a Last Call.  Assuming that is true, would it make sense to
> do that, or should we look at including other drafts in a combo Last Call.  We
> understand that there is an interest to take a vertical slice (yang-push,
> subscribed-notifications, and netconf-notif) to Last Call together, but maybe it
> would make more sense to do subscribed-notifications, netconf-notif, and
> restconf-notif together, as the latter two drafts provide the instance examples
> for the first draft.

From my perspective, the vertical slice makes more sense:
- YANG subscriptions has more industry activity, and early implementations needing interoperability guidance
- YANG-Push defines a notification which places the subscription-id within the notification message (something you don't get right away with subscribed-notifications).  This makes is more useful.
- the instance examples in the transport drafts also include examples of yang-push subscriptions (i.e., the horizontal slice also has vertical elements).
- restconf-notif's HTTP2 configured subscriptions are less complex if they use only the new notification message format

Eric 

> What are your thoughts?
> 
> Thanks,
> Kent and Mahesh
> 
> 
> --
> 
> We’d like to direct the WG attention to the set of drafts related to notifications
> and subscriptions, with the goal of getting a pulse on if the WG thinks they are
> ready to progress now.
> 
> To enable you get an overview and to see how the documents relate to each
> other, this draft is a good place to start:  https://tools.ietf.org/html/draft-voit-
> netconf-subscription-and-notif-overview-00.
> 
> The drafts related to this review are:
> 
>    -  draft-ietf-netconf-subscribed-notifications
>    -  draft-ietf-netconf-yang-push
>    -  draft-ietf-netconf-netconf-event-notifications
>    -  draft-ietf-netconf-restconf-notif
>    -  draft-ietf-netconf-notification-messages
> 
> While this is not an official WGLC, we will issue one if the response is positive.
> Please provide comments within two weeks.
> 
> Thanks,
> Mahesh and Kent
> 
> 
> 
> 
> 
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mailman_listinfo_netconf&d=DwIGaQ&c=HAkYuh63rsuhr6
> Scbfh0UjBXeMK-
> ndb3voDTXcWzoCI&r=9zkP0xnJUvZGJ9EPoOH7Yhqn2gsBYaGTvjISlaJdcZo&m=6
> EmQf9DJN6gYrH_xCp3oiMMsgNpXCh7lN3VAHxwuG-
> 4&s=vrMmzT7gkE3A2xzCWX5U8WjjxlRtLR137nXwhyPqO3Q&e=
> 
> 
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf