Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp5909706ybl; Tue, 27 Aug 2019 11:24:36 -0700 (PDT) X-Google-Smtp-Source: APXvYqw5qVhnY3MRwwUuHbyul3uSTBvN7zoudUG/Z9WOPZi6FxsXZOW3Sk2ySfSNA6XR8y9I1/3t X-Received: by 2002:aa7:8a86:: with SMTP id a6mr18153850pfc.76.1566930275946; Tue, 27 Aug 2019 11:24:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566930275; cv=none; d=google.com; s=arc-20160816; b=jK0MPa5snnqoCfla1ksa4p8/f4g3dD6S3Bms5eVn9sKg8eVyLCa8vHIdXMpZvc9C5N 8OR4P7g3/22LBBUa4sFHR72v+JpULvqyqPUEEgJEUgtwJE/SHgg9rB1qlLtnk+D3CMNu kF7nJoxnt1gRxmZqT3wjtq/bdb2zn3rJwoVVjY6u9qpbC7c/o4uMZiNkYrWY5uDou9gL 10cm2CTdtAP757zz57fhxAWz3RCq/3d4AUxR3QC7Jfht45cfi6ngyT/42Cvx0MSJASn/ GQ83nJJX5Bs1GaVWffXjaUCOc1BBT1HBCyWVdOtB7A44Vww6SAf3AovV2i7lhxsz32Hl SSOw== 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=k8kpShRA3BYL5xzw2Lq8pZfbrji63IOaSI+Vk43FOCs=; b=PrfOAed8G5YKEv6sxw6jNH/PeGdKZFTy0T5x9h/wouM5bk2BnAqh+PGJboo9acs6DA t6iJBwLYVszDramMj2aNfKCm3WoQeHAVrgralxPEOegHVcyzwHVsW6YeNRRCsGPSjDC1 ReqVQyAfw3QjRfm0/zfSj2wzuyNaeklWydPvbkc9VWf0W+Dp5ZqillawJ1Mt+X5i8KSA Wp5YXAiHN5Cg2A+lO98VdM5VdPxYJn2rx7Y+bTb/E2GZRuSGhR4tzKS6r7X+0FNaWmV8 reFRWrnTnvcKAOtG4gqEGaG++kvpRsZz27igr0dCk0K89qBfR7xVWm7vzRCvrJc0LJKq d05g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@silvair-com.20150623.gappssmtp.com header.s=20150623 header.b=tTxjKYiV; 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 q9si86581pjv.72.2019.08.27.11.24.05; Tue, 27 Aug 2019 11:24:35 -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=tTxjKYiV; 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 S1729626AbfH0SYB (ORCPT + 99 others); Tue, 27 Aug 2019 14:24:01 -0400 Received: from mail-lf1-f49.google.com ([209.85.167.49]:34500 "EHLO mail-lf1-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727064AbfH0SYB (ORCPT ); Tue, 27 Aug 2019 14:24:01 -0400 Received: by mail-lf1-f49.google.com with SMTP id z21so7492375lfe.1 for ; Tue, 27 Aug 2019 11:23:59 -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=k8kpShRA3BYL5xzw2Lq8pZfbrji63IOaSI+Vk43FOCs=; b=tTxjKYiVniKCgM47IGCcOBOZUGBri2g+GZZq3R8ilgPMTUxd43RCke5KuBfzGuNxdn ngta2F4S7tLozvk3ZkTDzXSmbwlUoovSJLCAxQBJwf9PlaM5vuUFat80T9cKSBTOdKoj nC7MdkdfLEKIVHon6Q0IIvhG02kiTR/UhOS/TeBmSDQnnjmYwfy65Eci/6xrOx4RSUBR F2e+5n7VDyZ5T2k8pLWZ3/KAc7NXsM9VqmWZ+xuhw6/oXao16XwZYCyCNvT3mUFsIUwC GRg9nJKngX8YZPi8siKTLwj1vCefVtaSpQbyMHSsRBOCoBIIpwD5tUsaH//REjl23TUi Mu2w== 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=k8kpShRA3BYL5xzw2Lq8pZfbrji63IOaSI+Vk43FOCs=; b=q5YzAbWDyqmFGYf5WTwFvdimFfF/ndk+hTnD9cJuqul4ayO/0t2s4IlbyHycrZa2Y5 e3mqMN6RAmFH0KrqxZbLPHagpEltZQIZXOLHDebn7tYmdMOkSJMV7pTH3SjIMWbX0SV4 nLvhcW500SIsiwQ+DFCc0hrvRFEOBws8OzIVKby+2NlrnAi8CplV1X1RzVV7ykDwHHzV lg2fDs8AtayHeoGyuQ1D7L/9PIpKF7wrkmderfl0aJaAWVIUag05o40pMqKZIV2HpNox VD9RFqED10eQWKWD5YgHDSZSo5Q0U4/kWaADPXd4o6r7Xvgjy/zsM+RUtxp+okicSWwL 15lQ== X-Gm-Message-State: APjAAAUsFaR5igMmRKtv+vGe+lDwUaN50I1BEzll3qtpXNSmHPqeF/pz tBDe0UdNc4rd3ELDJ2z+ZfPeqg== X-Received: by 2002:ac2:5c1d:: with SMTP id r29mr13931228lfp.72.1566930238813; Tue, 27 Aug 2019 11:23:58 -0700 (PDT) Received: from kynes (apn-37-7-28-223.dynamic.gprs.plus.pl. [37.7.28.223]) by smtp.gmail.com with ESMTPSA id y15sm6828lfg.12.2019.08.27.11.23.57 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 27 Aug 2019 11:23:58 -0700 (PDT) Date: Tue, 27 Aug 2019 20:23:56 +0200 From: "michal.lowas-rzechonek@silvair.com" To: "Stotland, Inga" Cc: "linux-bluetooth@vger.kernel.org" Subject: Re: [PATCH BlueZ 0/2] mesh: Implement org.bluez.mesh.Node1 properties Message-ID: <20190827182356.2pbseooolxfazg3g@kynes> Mail-Followup-To: "Stotland, Inga" , "linux-bluetooth@vger.kernel.org" References: <20190827090844.21394-1-michal.lowas-rzechonek@silvair.com> <4f4cc80d57738604b3b38049a1aecb6b75e57be2.camel@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4f4cc80d57738604b3b38049a1aecb6b75e57be2.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, On 08/27, Stotland, Inga wrote: > > adds two additional properties: list of unicast addresses > > claimed by the node and the current sequence number value. > Could you please explain the justification for adding these two new > properties? Sure thing. The address part is useful when application would like to talk to its own node's Config or Health Server. At the moment the address is known when calling Import or CreateNetwork (even though the application would then need to store it somewhere, so we end up with two sources of truth), but after Join() the application won't know the address assigned to it. As for sequence number part, reading is mostly for debugging and verification. A few our users had trouble identifying a problem in their setup when their node was listed in other nodes' RPL. In the end I would like to make it writable (increment-only) to enable address reuse, but as this stage I'm still looking for a way to implement this without causing a race condition, so I left it readonly for now. regards -- Michał Lowas-Rzechonek Silvair http://silvair.com Jasnogórska 44, 31-358 Krakow, POLAND