Re: [core] [Yot] YANG notification within CoMI

Michel Veillette <Michel.Veillette@trilliant.com> Mon, 11 June 2018 19:41 UTC

Return-Path: <Michel.Veillette@trilliant.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84A94130EBF; Mon, 11 Jun 2018 12:41:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=trilliant.onmicrosoft.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 z1Y8MztfVMMD; Mon, 11 Jun 2018 12:41:55 -0700 (PDT)
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-sn1nam01on0092.outbound.protection.outlook.com [104.47.32.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34F15130EBC; Mon, 11 Jun 2018 12:41:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Trilliant.onmicrosoft.com; s=selector1-Trilliant-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=PgxSOjVC5ugE0gwsHanH+xuvxWXW4kPX8POkKmPLiuk=; b=UAtYkgCM0Jm7EPLyTtZYLsQhS30/uyvJhg/VN0lwwR8Wln4VlzyQsxGLlPMBEiBkV19S0Nw+zyM0GNgKYy+CDjE45zmGF3MmOFYUZ8H6qeeKAcv3dpmurXnyW+PzP89ox8MMUez3Z8Yp8V03z8R81ibIf0sfhk67uLEikDwTVfg=
Received: from DM5PR06MB2777.namprd06.prod.outlook.com (10.175.107.139) by DM5PR06MB2443.namprd06.prod.outlook.com (10.168.178.137) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.841.14; Mon, 11 Jun 2018 19:41:52 +0000
Received: from DM5PR06MB2777.namprd06.prod.outlook.com ([fe80::f8bd:cd7c:eb9e:b248]) by DM5PR06MB2777.namprd06.prod.outlook.com ([fe80::f8bd:cd7c:eb9e:b248%10]) with mapi id 15.20.0841.019; Mon, 11 Jun 2018 19:41:52 +0000
From: Michel Veillette <Michel.Veillette@trilliant.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
CC: Peter van der Stok <stokcons@bbhmail.nl>, 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" <yot@ietf.org>, Core <core@ietf.org>
Thread-Topic: [Yot] YANG notification within CoMI
Thread-Index: AdP/UVBv6lm2EKsrSzmsBpb94+0wbgAovs2AAHE5hjA=
Date: Mon, 11 Jun 2018 19:41:52 +0000
Message-ID: <DM5PR06MB277742C8E8CEFD2443859CFF9A780@DM5PR06MB2777.namprd06.prod.outlook.com>
References: <DM5PR06MB2777CAB016D2789C4F1DD67F9A7B0@DM5PR06MB2777.namprd06.prod.outlook.com> <14497.1528550283@localhost>
In-Reply-To: <14497.1528550283@localhost>
Accept-Language: fr-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Michel.Veillette@trilliant.com;
x-originating-ip: [207.96.192.122]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR06MB2443; 7:RFym443nA2NdJYRiJzfAgrPEtkHQB10oJL8Vj0NOyN0QsW6YcKdla6J+uPUwRZ4sZLRDJGAJlNtHnT3xjRuQwzeI8hCQQ4NnKL2MjMjid94r7DSVCnk96snyJi+w81XIQJ4XzmivfFcJFd1UmBcgo3qjrEz8PC36JAnbubKa76rRDnoIIcNcWwWR5Ugvuk213kticEfankBp8Exz8ebzKz0OOQyutjLxT0dnTGQu7PvhCOsZ9GQPRUQncGT8grmc
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:DM5PR06MB2443;
x-ms-traffictypediagnostic: DM5PR06MB2443:
x-microsoft-antispam-prvs: <DM5PR06MB2443D7D7F95BBD41610F98149A780@DM5PR06MB2443.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(131327999870524)(95692535739014);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(3002001)(3231254)(944501410)(52105095)(10201501046)(93006095)(93001095)(149027)(150027)(6041310)(20161123564045)(20161123558120)(20161123560045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011)(7699016); SRVR:DM5PR06MB2443; BCL:0; PCL:0; RULEID:; SRVR:DM5PR06MB2443;
x-forefront-prvs: 070092A9D3
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(346002)(366004)(39380400002)(39850400004)(396003)(199004)(189003)(13464003)(7736002)(86362001)(229853002)(3280700002)(2420400007)(74316002)(26005)(54906003)(33656002)(7696005)(55016002)(106356001)(305945005)(316002)(97736004)(4326008)(186003)(7110500001)(5660300001)(105586002)(102836004)(15650500001)(6246003)(5250100002)(486006)(59450400001)(6506007)(53546011)(966005)(76176011)(3846002)(14454004)(66066001)(25786009)(3660700001)(8936002)(446003)(11346002)(72206003)(476003)(10710500007)(53936002)(81166006)(81156014)(8676002)(99286004)(2906002)(6436002)(2900100001)(68736007)(6116002)(6306002)(9686003)(478600001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR06MB2443; H:DM5PR06MB2777.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: trilliant.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: g5xzGmYdmCtoUpJwCitvc35VeNkT/nbYs1h7K61qDSJ5jCb6sf5vFzlYx1zG14UsqiaCT8p197bYdF7qnKNwGKy5wRz5rvE0qTbNH9glCEPm22+4bF1pMidZw4vDNwVrbun8EGhGfH81aQPjsTNr+SuDnUMwgK66pYXMbr3db5mZYvs8x4mjfX6Yjw2MZgGK
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: f8c85790-8431-44b4-bb1f-08d5cfd36182
X-OriginatorOrg: Trilliant.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f8c85790-8431-44b4-bb1f-08d5cfd36182
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Jun 2018 19:41:52.3018 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4f6fbd13-0dfb-4150-85c3-d43260c04309
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR06MB2443
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/Hqf4Imq2VJ3rWh-D_gjfPQYPc1E>
Subject: Re: [core] [Yot] YANG notification within CoMI
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2018 19:41:59 -0000

Hi Michael

About "Why would a COMI client be behind a load balancer?"

The main target of the CoMI protocol is network management. We typically deploy this protocol between a Network Management System (i.e. CoMI client) and hundreds of thousand or million(s) of constrained network elements (i.e CoMI server). At that scale, the NMS is implemented using a server cluster. The load balancer is used to distribute the load of notifications between the different servers. The load balancer also presents a stable IP address independent of the currently available servers behind it.

This is just a typical NMS configuration, noting special.

Regards,
Michel

-----Original Message-----
From: Michael Richardson [mailto:mcr+ietf@sandelman.ca] 
Sent: Saturday, June 9, 2018 9:18 AM
To: Michel Veillette <Michel.Veillette@trilliant.com>
Cc: Peter van der Stok <stokcons@bbhmail.nl>nl>; Andy Bierman <andy@yumaworks.com>om>; Alexander Pelov <a@ackl.io>io>; Eric Voit (evoit) <evoit@cisco.com>om>; Henk Birkholz <henk.birkholz@sit.fraunhofer.de>de>; yot@ietf.org; Core <core@ietf.org>
Subject: Re: [Yot] YANG notification within CoMI


Why would a COMI client be behind a load balancer?

(I can't understand why some ports on such a machine might be subject to load balancing, but why the CoMI communications?)

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [