[GitHub] [mynewt-nimble] rymanluk commented on issue #683: [RFC] nimble/ll: Allow to update resolving list

[GitBox <gi...@apache.org>]

rymanluk commented on issue #683: [RFC] nimble/ll: Allow to update resolving list
URL: https://github.com/apache/mynewt-nimble/pull/683#issuecomment-561126593
 
 
   @sjanc good point and yes this is back to network and I should put it in the comment.
   I also think this is what we want.
   As you know this is already undefined behavior and error code we are sending now is not great as it does not really say nothing valuable to the host what is wrong.
   
   I think the assumption that the only issue on the host side is that they forget to remove old key is good enough. So the controller will just drop old entry and create new one with a new keys. Host need to configure privacy mode
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services