[netmod] JSON encoding of events in draft-ietf-netconf-https-notif

Kent Watsen <kent+ietf@watsen.net> Tue, 07 April 2020 12:08 UTC

Return-Path: <01000171548a786b-6a9c7e4d-37f1-4a0f-a1a3-8b25a3ac8b7b-000000@amazonses.watsen.net>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 572593A0538; Tue, 7 Apr 2020 05:08:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.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 xRZX9kYvOG4O; Tue, 7 Apr 2020 05:08:15 -0700 (PDT)
Received: from a8-31.smtp-out.amazonses.com (a8-31.smtp-out.amazonses.com [54.240.8.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 999783A0529; Tue, 7 Apr 2020 05:08:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1586261293; h=Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:From:In-Reply-To:Cc:Date:Message-Id:References:To:Feedback-ID; bh=juSNCq1CZbrMFzkH7A2pHX7UDJiKRIEz3E1u50nESOY=; b=kHBvfohwHlkYmrBd70yY2ZbBe/SGl/5bInxvKGHsBuWpmrbn0piIg0BH0oBt6ABd Ez9idIJLxg0rxMVIdqbXyA40Qpo8r6ik01EXHwj7b0h90LMmMgQl/YPAS/5sHzxuknq khPmOlAlaB6tH15uFjV/ngOITXbVTT3lRcwcpjxM=
Content-Type: multipart/alternative; boundary=Apple-Mail-A9E3B5E9-190A-4623-B4D4-A15C381D7403
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
From: Kent Watsen <kent+ietf@watsen.net>
In-Reply-To: <DB7PR07MB40113F464CD53B14FA74DC6DF0C30@DB7PR07MB4011.eurprd07.prod.outlook.com>
Cc: Oskar Malm <oskar.malm@ericsson.com>, "netconf@ietf.org" <netconf@ietf.org>
Date: Tue, 7 Apr 2020 12:08:13 +0000
Message-ID: <01000171548a786b-6a9c7e4d-37f1-4a0f-a1a3-8b25a3ac8b7b-000000@email.amazonses.com>
References: <DB7PR07MB40113F464CD53B14FA74DC6DF0C30@DB7PR07MB4011.eurprd07.prod.outlook.com>
To: =?utf-8?Q?Bal=C3=A1zs_Lengyel?= <balazs.lengyel=40ericsson.com@dmarc.ietf.org>
X-Mailer: iPhone Mail (17D50)
X-SES-Outgoing: 2020.04.07-54.240.8.31
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/Dz9_05hqCo-LHB449FkwqqI7VnE>
X-Mailman-Approved-At: Tue, 07 Apr 2020 06:29:31 -0700
Subject: [netmod] JSON encoding of events in draft-ietf-netconf-https-notif
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2020 12:08:16 -0000

Moving to “netconf” (“netmod” in BCC)

K. 




Sent from my iPhone
>> On Apr 7, 2020, at 4:35 AM, Balázs Lengyel <balazs.lengyel=40ericsson.com@dmarc.ietf.org> wrote:
> 
> Hello Mahesh, Kent,
> I was wondering how the JSON encoding of event would look like in your draft. (I intend to propose something similar to 3GPP so I am most interested.)
> The part below push-update or push-change-update is well defined in YANG however the part outside is not. In Restconf (https://trac.tools.ietf.org/html/rfc8040#section-6.4) I see the following example:
>  
> {
> "ietf-restconf:notification" : {
>   "eventTime" : "2013-12-21T00:01:00Z",
>   "example-mod:event" : {
>     "event-class" : "fault",
>     "reporting-entity" : { "card" : "Ethernet0" },
>     "severity" : "major"
>   } } }
>  
> However how would the first 2 lines look here? IMHO keeping restconf as a module name seems wrong.
> So maybe we should define it here in this draft :
> {
>  "json-yang-notification:notification" : {
>   "eventTime" : "2013-12-21T00:01:00Z",
>   "push-change-update" : {
>     ...
>   } } }
>  
> How to define this wrapper (the first 2 lines, I am unsure. As far as I know it is not possible to describe this in YANG.  Maybe just some text like:
> The YANG encoding of the notification SHALL be wrapped in a JSON object as illustrated below
>  
> "json-yang-notification:notification" : {
>   "eventTime" : "2013-12-21T00:01:00Z",
>  
>  
> Also I would definitely need an example of a notification sent.
> Regards Balazs
>  
> --
> Balazs Lengyel                    Senior Specialist                       Ericsson Hungary Ltd.
> Mobile: +36-70-330-7909              email: Balazs.Lengyel@ericsson.com