[
https://issues.apache.org/jira/browse/MYNEWT-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438352#comment-15438352
]
William San Filippo commented on MYNEWT-86:
-------------------------------------------
The controller still does not ask the peer controller for its supported
features. As I mentioned in the ticket, the spec does not require this but I do
think it is something that should be done. It is not hard to do; just needs to
get implemented and tested. In fact, it is quite easy to implement; was just
low on the priority list.
> Controller should ask peer controller for supported features before
> attempting certain control procedures
> ---------------------------------------------------------------------------------------------------------
>
> Key: MYNEWT-86
> URL: https://issues.apache.org/jira/browse/MYNEWT-86
> Project: Mynewt
> Issue Type: Improvement
> Components: Nimble
> Affects Versions: v0_8_0_beta1
> Reporter: William San Filippo
> Assignee: William San Filippo
> Priority: Trivial
> Labels: controller
> Fix For: v1_0_0_beta1
>
>
> It was noted by some at the unplugfest that our controller was initiating
> control procedures with a peer controller without asking that peer controller
> for its supported features. While this is not 100% necessary per the
> specification, it is probably something our controller should implement.
> Specifically, they questioned the connection parameter request procedure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
