jonas-schievink/rubble

Implement (G)ATT on top of L2CAP

Open

#29 opened on Mar 31, 2019

View on GitHub
 (6 comments) (3 reactions) (0 assignees)Rust (58 forks)user submission
area: (G)ATThelp wantedstatus: needs codestatus: needs designtype: enhancement

Repository metrics

Stars
 (403 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

GATT is not it's own protocol, but means Generic Attribute Profile (even though the spec sometimes calls it Generic Attribute Protocol - I'm not making this shit up!). We have to implement whatever parts of ATT are needed by GATT.

Contributor guide

Research direction
Study the Bluetooth Core Specification for GATT and ATT, then implement the necessary ATT procedures (e.g., Read By Group Type, Read By Type) in the rubble crate, focusing on the L2CAP layer integration.
Tech stack
rust
Domain
embedded iotnetworking
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
RustBluetooth LE specification knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30