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.