Re: [Yot] YANG notification within CoMI

Peter van der Stok <stokcons@bbhmail.nl> Mon, 11 June 2018 07:19 UTC

Return-Path: <stokcons@bbhmail.nl>
X-Original-To: yot@ietfa.amsl.com
Delivered-To: yot@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9218C130E13; Mon, 11 Jun 2018 00:19:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham 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 fYA2rWGScs_Z; Mon, 11 Jun 2018 00:19:48 -0700 (PDT)
Received: from smtprelay.hostedemail.com (smtprelay0080.hostedemail.com [216.40.44.80]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E6E5130DFE; Mon, 11 Jun 2018 00:19:48 -0700 (PDT)
Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay06.hostedemail.com (Postfix) with ESMTP id 90BA218224D99; Mon, 11 Jun 2018 07:19:47 +0000 (UTC)
X-Session-Marker: 73746F6B636F6E73406262686D61696C2E6E6C
X-Spam-Summary: 2, 0, 0, , d41d8cd98f00b204, stokcons@bbhmail.nl, :::::::::::::, RULES_HIT:1:41:69:72:152:355:379:582:599:962:967:973:983:988:989:1152:1189:1208:1212:1221:1260:1313:1314:1345:1359:1431:1436:1437:1516:1517:1518:1575:1588:1589:1592:1594:1730:1777:1792:1801:2068:2069:2198:2199:2525:2527:2528:2559:2564:2636:2682:2685:2859:2933:2937:2939:2942:2945:2947:2951:2954:3022:3138:3139:3140:3141:3142:3354:3622:3865:3866:3867:3868:3870:3871:3872:3874:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4250:4321:4361:4362:4470:4605:5007:6117:6261:6657:6678:7875:7903:7974:8603:8957:9025:10004:10234:10848:10946:11232:11658:11914:12043:12683:12740:12895:13139:13439:13972:14095:14096:21060:21080:21212:21324:21433:21451:21627:21660:30022:30054:30070:30083, 0, RBL:216.40.42.5:@bbhmail.nl:.lbl8.mailshell.net-62.8.55.100 66.201.201.201, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:fn, MSBL:0, DNSBL:neutral, Custom_rules:0:1:0, LFtime:27, LUA_SUMMARY:none
X-HE-Tag: frog86_5566e24c24220
X-Filterd-Recvd-Size: 14930
Received: from mail.bbhmail.nl (imap-ext [216.40.42.5]) (Authenticated sender: webmail@stokcons@bbhmail.nl) by omf10.hostedemail.com (Postfix) with ESMTPA; Mon, 11 Jun 2018 07:19:46 +0000 (UTC)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_2d163e3f187f67022f615d58da684374"
Date: Mon, 11 Jun 2018 09:19:46 +0200
From: Peter van der Stok <stokcons@bbhmail.nl>
To: Michel Veillette <Michel.Veillette@trilliant.com>
Cc: Andy Bierman <andy@yumaworks.com>, Alexander Pelov <a@ackl.io>, "Eric Voit (evoit)" <evoit@cisco.com>, Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, yot@ietf.org, Core <core@ietf.org>
Organization: vanderstok consultancy
Reply-To: consultancy@vanderstok.org
Mail-Reply-To: consultancy@vanderstok.org
In-Reply-To: <DM5PR06MB2777CAB016D2789C4F1DD67F9A7B0@DM5PR06MB2777.namprd06.prod.outlook.com>
References: <DM5PR06MB2777CAB016D2789C4F1DD67F9A7B0@DM5PR06MB2777.namprd06.prod.outlook.com>
Message-ID: <cac589a63e8864913ccd4aac6cddbf66@bbhmail.nl>
X-Sender: stokcons@bbhmail.nl
User-Agent: Roundcube Webmail/1.2.7
X-Originating-IP: [90.0.84.153]
Archived-At: <https://mailarchive.ietf.org/arch/msg/yot/X9ajGg4XcL_XyvmAkpr49Q9Yfg0>
Subject: Re: [Yot] YANG notification within CoMI
X-BeenThere: yot@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Yang of Things <yot.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yot>, <mailto:yot-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yot/>
List-Post: <mailto:yot@ietf.org>
List-Help: <mailto:yot-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yot>, <mailto:yot-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2018 07:19:52 -0000

Hi Michel,

Thanks for the message.
I think that load balancers, stable storage for messages, californium
implementation restrictions are all separate subjects, and merit a
solution independent of CoMI.

I recommend to maintain section 5.5, as is, in the comi draft and start
looking at the other subjects separately.

Peter
Michel Veillette schreef op 2018-06-08 20:17:

> Support the YANG notifications in the current CoMI draft (i.e https://www.ietf.org/id/draft-ietf-core-comi-03.txt) is based on the observe option as defined by RFC7641. 
> 
> This solution has the following issues which make it not practical for the targeted use case. 
> 
> 1) This approach in incompatible with load balancers, notifications are directly returned to the specific server within the cluster which have initiated the observe request. 
> 
> 2) Typical CoAP implementation (e.g. Californium) doesn't support the persistence of the observe context. These contexts can't be recovered after a server restart and can't be shared between servers. 
> 
> 3) Registrations to event streams are not resilient, they can terminate unexpectedly upon transmission error or reception of a Reset message. 
> 
> I recommend to delete draft-ietf-core-comi section 5.5 and start a specific effort on this topic. 
> 
> Alignment with the [I-D.ietf-netconf-yang-push] also need to be considered. 
> 
> Those interested to this topic, please send me a email so I can schedule conference calls or a face to face meeting during the next IETF. 
> 
> The following diagram shows a typical deployment scenario. 
> 
> +---------+  +---------+       +---------+ 
> 
> | CoMI    |  | CoMI    |  ...  | CoMI    | 
> 
> | server  |  | server  |       | server  | 
> 
> +---------+  +---------+       +---------+ 
> 
> |            |                 | 
> 
> |            |                 | 
> 
> +----------+-+-----------------+ 
> 
> | 
> 
> | 
> 
> +---------------------------------+ 
> 
> | CoMI         |                  | 
> 
> | client       |                  | 
> 
> |         +----------+            | 
> 
> |         | Load     |            | 
> 
> |         | Balancer |            | 
> 
> |         +----------+            | 
> 
> |              |                  | 
> 
> |        +-----+---------+        | 
> 
> |        |               |        | 
> 
> |   +---------+     +---------+   | 
> 
> |   | Server  | ... | Server  |   | 
> 
> |   +---------+     +---------+   | 
> 
> |        |               |        | 
> 
> |        +-------+-------+        | 
> 
> |                |                | 
> 
> |           +----------+          | 
> 
> |           | Database |          | 
> 
> |           +----------+          | 
> 
> |                                 | 
> 
> +---------------------------------+ 
> 
> Regards, 
> 
> Michel