Markdown Version | Session Recording

Session Date/Time: 26 Sep 2023 13:00

MANET

Summary

This MANET working group interim virtual meeting was scheduled to continue discussions on potential work items for a new charter, as the previous IETF 117 meeting ran out of time. A key topic was the planned assimilation of the Babel routing protocol's maintenance into the MANET working group. The discussion highlighted a need for renewed community interest and active participation to support any new work items for a re-chartered MANET working group. The AD emphasized that visible support and willingness to drive work on the mailing list are crucial for future progress.

Key Discussion Points

Babel Protocol Assimilation

Donald Eastlake presented on the Babel routing protocol and its potential transfer of maintenance to the MANET working group.

• Babel Overview: Babel is a distance vector algorithm (similar to RIP) with loop and starvation avoidance mechanisms. It's effective in networks with mixed link qualities (wireless/hybrid).
• Current Status:
  • Babel has produced several RFCs (8966 - core protocol, 8967 - MAC authentication, 8968 - DTLS encryption, 9079 - Source Specific Routing, 9229 - IPv4 over IPv6 Babel).
  • It is the mandatory-to-implement routing protocol for HomeNet.
  • Three drafts are currently in progress: a Yang model (pending a security-related Yang component), a MAC reordering relaxation draft (WGLC), and a Round Trip Time extension draft (awaiting IESG review).
  • Once these drafts are published, the Babel working group is expected to be shut down.
• Proposed Transfer to MANET:
  • The Babel working group aims to transfer its maintenance work to MANET.
  • This would require minor wording tweaks in the MANET charter, specifically updating the maintenance responsibility clause and adjusting references to the (soon-to-be-closed) Babel working group.
  • Mailing List: A query on the Babel mailing list will be made regarding the feasibility and desire to merge the Babel mailing list with the MANET mailing list.
• Potential New Babel-related Work in MANET:
  • Multicast Extensions for Babel: The original Babel charter included multicast, with some preliminary work done. This could become a milestone for MANET.
  • Babel for IEEE 802.11 Wi-Fi Mesh: A proposal for adapting Babel for 802.11 Wi-Fi mesh networks, presented at IETF 117, received a liaison from 802.11 indicating support for IETF work in this area. There is some enthusiasm and potential funding on the Babel side, with discussions around suitable development platforms (e.g., OpenWrt).

MANET Charter Review - Existing and Potential Work Items

The chair presented a comprehensive list of past, current, and potential future work items for discussion, emphasizing the need for active contributors for any item to be included in a new charter.

• D-LUR (Dynamic Link Unavailability Reporting):

  • Work on D-LUR (RFC 8075) and its extensions has been a success.
  • Maintenance and extensions should continue.
  • Credit-based flow control extensions are pending. A simpler flow control scheme (RFC 8651) has been devised.
  • Traffic classification and statistics reporting extensions (which could build on flow control concepts) were not picked up, and a sense of those present indicated little interest in pursuing them further.

• Multicast:

  • An intention to pursue multicast work remains, potentially reconciling with Babel's multicast capabilities.
  • Previous work on "shape-room 5 North Coast forwarding" (presented in 2016) did not materialize, but the chair expressed personal interest in a BEER-inspired, best-effort based multicast approach.

• Best Practices for MANET Deployment/Management:

  • This item never materialized due to the highly specific and often proprietary nature of such details from operators. It was suggested to be dropped from a new charter.

• OLSv2 (Optimized Link State Routing Protocol version 2):

  • Maintenance and extensions for OLSv2 (completed in 2014) should remain a charter item.
  • Current open-source implementations: one from NICT (Japan), Fraunhofer (Germany, which also uses the directional airtime metric). A new Go-language implementation is under development by Fraunhofer (likely not open source).
  • Specific OLSv2 Extensions/Tweaks:
    • Restarting nodes: Discussion in Summer 2022 on issues when a single node restarts, potentially leading to inability to rejoin.
    • Directional Airtime Metric: Currently an experimental RFC, used in Fraunhofer's implementation. Question raised about bringing it to Proposed Standard status.
    • Multi-Topology Extension: Currently experimental status. Christopher Doyle confirmed that BAE Systems had implemented and used it previously for environments with low-capacity links, but their implementation is not open source or currently accessible.
    • Source-Specific Routing: Inspired by Babel, an OLSv2 implementation was developed by Antoine Robin at an IETF meeting. The chair plans to consult with him about progressing this as an Internet-Draft.
    • Slow Mode Tweak: Christopher Doyle suggested a minor tweak for OLSv2 in slow mode, allowing response to changes only when a new node joins the network. This could be an informative RFC.

• Potential New Work Items:

  • STURP Protocol: An energy-efficient routing protocol for home-oriented MANETs, presented at IETF 117. Despite four authors, all were from the same company, and critical discussion on the mailing list was not followed up by the authors. The chair will inquire if they wish to continue.
  • DTN Management Architecture: Re-evaluate its suitability for MANET environments, as the latest version (formerly Asynchronous Management Architecture) is with the DTN WG.
  • Reactive/Hybrid Routing Protocols: Historically, efforts like AODV, DAIMON, and AODVv2 faced technical and non-technical issues. LOADng (a simplified AODVv2) was standardized outside the IETF (ITU). Recent mailing list suggestions for hybrid protocols (e.g., Abdul Salam) have occurred. Christopher Doyle mentioned theoretical work on borrowing RACK/RREP from AODV for OLSv2, but needs a driver.
  • Satellite Routing: The current MANET charter is broad enough to accommodate routing between satellites. A ping to interested parties is needed.
  • Federation of MANETs: A need for different MANET origins (potentially proprietary) to interoperate, for both unicast and multicast, possibly using overlay protocols.

AD's Input (Jim Guichard)

Jim Guichard, the Routing Area Director, expressed significant concern about the lack of participation and enthusiasm for new work in the MANET working group.

• He emphasized that for any new charter item, there must be visible support from multiple individuals in the community, not just the authors of a draft.
• He stated that a working group cannot be kept open for a "singular person's pet project" or "one company rubber stamp."
• He stressed the importance of making progress on existing working group documents currently in the publication queue.
• He made it clear that re-chartering a working group solely for maintenance activities is generally not supported, as such work might be moved to the Routing Area Working Group (RTGWG) or handled via other mechanisms if no new work emerges.
• The AD highlighted that the discussion on the mailing list would be "very telling" regarding the future of the working group.

Decisions and Action Items

• Decision: The MANET working group will not proceed with proposing new work items for a re-charter without clear, visible community support and identified drivers willing to undertake the work.
• Action Item: Chair (Dirk-Jan): Initiate a discussion on the MANET mailing list, providing a bullet-point list of potential new charter items (from this meeting) and explicitly asking for expressions of support and willingness to work on them. The discussion should also allow for new suggestions from the community. (Target: ASAP)
• Action Item: Chair (Dirk-Jan): Report on this meeting's discussion, specifically concerning Babel's future and transfer of maintenance, to the Babel mailing list. (Target: ASAP)
• Action Item: Donald Eastlake: Inquire on the Babel mailing list whether there is any perceived problem with potentially merging the Babel and MANET mailing lists. (Target: ASAP)
• Action Item: Christopher Doyle: Write a few lines on the MANET mailing list describing his proposed OLSv2 "slow mode tweak." (Target: Soon)
• Action Item: Chair (Dirk-Jan): Contact the authors of the STURP protocol to ascertain their intent to continue working on the draft. (Target: Soon)
• Action Item: Chair (Dirk-Jan): Ping interested parties regarding satellite routing discussions for MANET. (Target: Soon)

Next Steps

1. The primary next step is to conduct a robust discussion on the MANET mailing list, as outlined in the action items, to gauge community interest and identify potential drivers for future work.
2. Based on the outcome of the mailing list discussion, the chairs and AD will determine the appropriate path forward for the MANET working group, which could include re-chartering with specific, well-supported work items, or considering alternative options if sufficient enthusiasm for new work is not demonstrated.