**Session Date/Time:** 26 Jul 2023 00:00

# manet

## Summary
The MANET working group meeting covered document status updates, presentations on potential new work items, and initial discussions on rechartering the group.  Two presentations were given: one on a generic topology update mechanism ("stoop") and another on the possibility of using Babel as a routing protocol within 802.11 mesh networks. There was significant discussion on the applicability and scope of these proposals.

## Key Discussion Points
*   **Credit-Based Flow Control Documents:** The four credit-based flow control drafts have been in the working group for an extended period. The Shepard write-up is almost complete, and the main sticking point was the lack of a rationale for having four documents. The working group is aiming to move these documents forward quickly and request routing directorate review in parallel with TSVART review.
*   **Layer 1.5 Drafts:**  Three Layer 1.5 drafts will be put through a working group adoption call following the meeting.  The chair expressed support for adopting these.
*   **Generic Topology Update Mechanism ("stoop"):** David Ru presented a new draft proposing a generic topology update mechanism aimed at improving efficiency in MANETs.  The mechanism triggers updates based on changes in communication relations rather than topology changes themselves.  Discussions focused on integration with existing routing protocols (e.g., OLSRv2), handling triangle topologies, sequence number management, and how the proposed mechanism would be combined with existing routing tables. The consensus was the discussion should be continued on the mailing list.
*   **Babel for 802.11 Mesh:** Donald Eastlake presented the possibility of using Babel as the routing protocol within 802.11 mesh networks. This would involve creating an RFC specifying how to use Babel in this context, and potentially using Babel link metrics. Discussions centered on whether the IETF should be working on a data plane protocol for 802.11, the lack of a clear use case or implementer interest, and the potential complexities involved.
*   **Rechartering:**  Brief discussion about rechartering the working group. Current work items were listed. Suggestions were made about the process for rechartering and need for and interim meeting.  There was mention of potential new work related to satellite routing from the RTGWG.

## Decisions and Action Items
*   **Shepherd:** Louis will complete the shepherd write-up for the credit-based flow control documents.
*   **Chair:** Request routing directorate review for the credit-based flow control drafts.
*   **Working Group Adoption Call:** The three Layer 1.5 drafts will be put through a working group adoption call.
*   **Continue Discussions on Mailing List:** Discussions on "stoop" and "Babel for 802.11 Mesh" will continue on the mailing list.
*   **Rechartering Interim Meeting:**  Set up an interim meeting to continue rechartering discussions

## Next Steps
*   Complete shepherd write-up and request routing directorate review for credit-based flow control documents.
*   Hold a working group adoption call for the Layer 1.5 drafts.
*   Continue discussions on the mailing list regarding the proposed "stoop" and "Babel for 802.11 Mesh" drafts.
*   Schedule an interim meeting to discuss rechartering and a time to push out Loose's documents.
*   The chairs will have a conversation with the RTG WG chairs to discuss possible requirements for satellite routing.