Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp493673ybe; Thu, 5 Sep 2019 00:55:06 -0700 (PDT) X-Google-Smtp-Source: APXvYqxtvqRS9N1KOxvEwNTKO80PD2QcUOMqYbRCJYTIEzvG0kQ0BpVkRRC08L6EJdfgDbF0zjIb X-Received: by 2002:a17:902:e593:: with SMTP id cl19mr2015851plb.220.1567670106377; Thu, 05 Sep 2019 00:55:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567670106; cv=none; d=google.com; s=arc-20160816; b=h2ywO6woaYpYZ+pk5hMGE8mlsrES24x7GeIfs3TCZV+XVVq7nz3AD6FFXRvTkr5lCT kQtKLYzYPI5AyjCSyrkTZMxtosAtOUwQqFVcYbawtr1LMYRw6RFO22JHhJBSd1AO5NyB PVY5FU8M9ELGwjq10uprhp/35EcZTRodQaVCdKQkIzARL3zFJTI7Q7RgDEJqdmbTZYEq SmctwBUwjX0lz9OcweZoHFyYy37vFW2CBWlSdef4NNRIDRm2lOJXwQfNqjojDwcN05wa MD4A4ptNcr/r3dKIaBMHZX5tBHRwi/E2S82Mv0iufXM1CVJBx2lXSAH9PaU/AGI0Da3V u7jg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:mail-followup-to:message-id:subject:cc:to:from:date :dkim-signature; bh=a/LbM5DPkxpSyrzrkgXmY0H1sRUr/jc8zJFioM5t4I0=; b=IX3w74mZCiP4KJaM5IvPwDiuc+ZvsMWm4P2hsaEzz6syitVdxexGmqSc3Ls8+PYZgh QDq9lPMM3y+wqJU5PDd71qa5WQbaXiUZfFvo/LuvgGPW+RaEjYxHQyIySpgzBPZNP59C LzxsLDdq9vm2cfdU6GKz3rOe+aS+fVZYin88YmsOU+3259l5BWzobRYZIQLp31Yzalt2 sZHKOGK1SnDY1GK/Yui+CMiwYYGGLaPtOXWqURrk8ATFzOZV1z4On3Y+O1infw0qF4Eb 686mbIwW99+RVIy+GvQ5sVF4bbKuM5a4UfocogzQuc8O0IUSO6bY50/2GCt0STe8KpK2 1T8Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@silvair-com.20150623.gappssmtp.com header.s=20150623 header.b="Q/GlH6ML"; spf=pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g3si1366895pjs.21.2019.09.05.00.54.25; Thu, 05 Sep 2019 00:55:06 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@silvair-com.20150623.gappssmtp.com header.s=20150623 header.b="Q/GlH6ML"; spf=pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730659AbfIEH3m (ORCPT + 99 others); Thu, 5 Sep 2019 03:29:42 -0400 Received: from mail-lj1-f171.google.com ([209.85.208.171]:41672 "EHLO mail-lj1-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730074AbfIEH3l (ORCPT ); Thu, 5 Sep 2019 03:29:41 -0400 Received: by mail-lj1-f171.google.com with SMTP id a4so1304904ljk.8 for ; Thu, 05 Sep 2019 00:29:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=silvair-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=a/LbM5DPkxpSyrzrkgXmY0H1sRUr/jc8zJFioM5t4I0=; b=Q/GlH6MLWuGEBFkqGPragKLorURSgRXTS2fJgKPVwhbHsSbaNH4jaebfl08kUgcWb/ rovy+MEMaOxldzzGNb8hw0DC18O6YLNuCxO05GzFO4OEGwKI8AGSNLHpWoBSbXW+lxW7 F+f51r/8pntNf4Hi8Qxm1pN+JrWKgFi51Crs33aVE5/4T5IJSzESsIbNqjCS/HmwslSY BLtux20rLMCyqF34zdzW5wnG4K6BNA6Di5zmRmrG5X8h/P6fSTXfS3pdU9ukxwyaqrme AbdWh6xg7kF2cP9BvpZLSHWeteqy+52pxFScF6cngUXYJFJjf3d6oHrdY/0z3zpgDrTL qemg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=a/LbM5DPkxpSyrzrkgXmY0H1sRUr/jc8zJFioM5t4I0=; b=A4rt5BsbJBjjVSv/HPHnIn7eFj+k1ovcSDIopYvdngw1saCL64GI5656q1gHmCueo/ VdXSAgLWIGm9juAEgvvLbF59lWbiOZt2oe5VtgKyQpZ90b9tleZlwHe6bCUxhfuUffro 3+gsmLHo0xHhFqGhmw45vC64gr2F+uN/c+IiESM+QFMtfRQeO1oU0AmZF1UWzidxZmRW Cto0kVyLTiFnd7m4Py3M/YYWyPLq//L3jNkZXIwEqZiAFdF/z0FxsV+nksYTN8iSajqt 2kmuMs+42ROSuao0eiE7hXwYa8Pboj9WfOqdWDohBC90rBYrqEwqggXK2qRQg0I9krBx WQfA== X-Gm-Message-State: APjAAAX1j8XbpoC6h5XXTtlVZOE9zBPvZWyjuXRg1m2jaCgXDqi2EMiF UrNjVNfckhiwJgbKvmYt31WqnQ== X-Received: by 2002:a2e:9dd5:: with SMTP id x21mr1035532ljj.182.1567668579446; Thu, 05 Sep 2019 00:29:39 -0700 (PDT) Received: from mlowasrzechonek2133 ([217.153.94.18]) by smtp.gmail.com with ESMTPSA id h2sm214408ljl.21.2019.09.05.00.29.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 05 Sep 2019 00:29:38 -0700 (PDT) Date: Thu, 5 Sep 2019 09:29:37 +0200 From: "michal.lowas-rzechonek@silvair.com" To: "Stotland, Inga" Cc: "linux-bluetooth@vger.kernel.org" , "Gix, Brian" , "simon@silvair.com" Subject: Re: mesh: org.bluez.mesh.Element.MessageReceived method does not provide destination address Message-ID: <20190905072937.m4ag4wtecfevsvij@mlowasrzechonek2133> Mail-Followup-To: "Stotland, Inga" , "linux-bluetooth@vger.kernel.org" , "Gix, Brian" , "simon@silvair.com" References: <20190830184301.zd3zaqrw7mv6r252@kynes> <20190904192525.2dqyihabxmigb54m@kynes> <20190904194808.nu2cy4vp6uh64m4z@kynes> <7de19e37e75bf2759b654c3a98e00b5b0e37aa0e.camel@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <7de19e37e75bf2759b654c3a98e00b5b0e37aa0e.camel@intel.com> User-Agent: NeoMutt/20180716 Sender: linux-bluetooth-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org Hi Inga, On 09/04, Stotland, Inga wrote: > > > > - a combined server/client sitting on element 1 that receives > > > > onoff messages and, depending on the destination address, sends > > > > a different onoff messages to a "regular" onoff server sitting > > > > on element 0, allowing efficient control over switching scenes > > > > involving large number of nodes > This sounds like something a vendor model mechanism should handle: > the "mapping" should be understood on both ends: client and server. Well, yes, I've described a vendor model... one that uses destination group addresses to 'understand' the mapping. I don't get what other mechanism do you have in mind? -- Michał Lowas-Rzechonek Silvair http://silvair.com Jasnogórska 44, 31-358 Krakow, POLAND