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 (403 stars) (58 forks)user submission
area: (G)ATThelp wantedstatus: needs codestatus: needs designtype: enhancement

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

Tech stack
rust
Domain
backend
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.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
RustBLE protocol knowledgeL2CAP conceptsGATT/ATT specification
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
Review the existing L2CAP implementation in the rubble repository (likely in src/l2cap.rs or similar). Understand the current BLE stack structure and identify where GATT/ATT should be integrated. Check comments on this issue for any design discussions or pointers to relevant code. There are 6 comments, so read them for additional context. The issue asks to implement parts of ATT needed by GATT on top of L2CAP, so focus on defining the necessary ATT procedures (e.g., MTU exchange, read/write) and their mapping to L2CAP channels.