jonas-schievink/rubble

Implement (G)ATT on top of L2CAP

Open

#29 建立於 2019年3月31日

在 GitHub 查看
 (6 留言) (3 反應) (0 負責人)Rust (403 star) (58 fork)user submission
area: (G)ATThelp wantedstatus: needs codestatus: needs designtype: enhancement

描述

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.

貢獻者指南

技術棧
rust
領域
backend
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
needs investigation
前置要求
RustBLE protocol knowledgeL2CAP conceptsGATT/ATT specification
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
10
研究方向
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.