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;
Date:   Wed, 29 Jan 2020 13:17:44 +0100
From:   Rafal Gajda <rafal.gajda@silvair.com>
To:     Brian Gix <brian.gix@intel.com>
Cc:     linux-bluetooth@vger.kernel.org, inga.stotland@intel.com
Subject: Re: [PATCH BlueZ v4 5/5] mesh: Add NVM storage of Replay Protection
Message-ID: <20200129121744.zv3jnf6uejjpetud@rgajda2364>
References: <20200129023258.10004-1-brian.gix@intel.com>
 <20200129023258.10004-6-brian.gix@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20200129023258.10004-6-brian.gix@intel.com>
User-Agent: NeoMutt/20180716
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

Hi Brian,

I have a question about the way RPL is stored.

On Tue, Jan 28, 2020 at 06:32:58PM -0800, Brian Gix wrote:                                          
> Mesh specification requires that Replay Protection be preserved
> across node restarts.  This adds that storage in
> <node_uuid>/rpl/<iv_index>/<src>

Wouldn't it be more convinient to keep both iv_index and sequence in a file like this:
  <node_uuid>/rpl/<src>
?

You could store them in bytes instead of hex string 
and it would eliminate the need for cleaning entries from old IV_index.


Regards,
Rafał Gajda

Silvair