Summary

  • The IETF’s new broadband list aims to bring together access-protocol work that its announcement describes as scattered across INTAREA or lacking an active working-group home.
  • INTAREA already requires a capable core of contributors and a commitment to timely review before taking on new work. A common address can help find those people; it does not supply their time.

An engineer with a proposed protocol extension needs more than somewhere to send it. Someone must understand the problem, read successive revisions and test whether the proposed solution belongs in a shared specification.

That is the practical challenge behind the 2 September announcement of the IETF broadband list. The new venue covers broadband-access work, with PPPoE, IPoE and ANCP among the examples, alongside IANA allocations outside Broadband Forum’s scope. It is intended to gather interest and contributions, eventually leading to a request for a Birds of a Feather discussion.

The announcement says such drafts currently tend to land in the general Internet Area Working Group, INTAREA, or remain without an active working group. It identifies that fragmentation as a barrier for new contributors. This is the announcement’s diagnosis, not a published measurement of abandoned proposals or review delays.

An existing home has conditions

The approved INTAREA charter makes the problem more precise. Its primary role is discussion and coordination across the Internet Area. Its secondary role accommodates RFC work that lies outside existing groups and does not justify creating a new one.

Admission is not simply a matter of topical fit. The charter requires agreement on wider Internet relevance and the work’s suitability and likely quality. It also requires enough core expertise and energy to advance the item, a group commitment to sufficient timely review, and Area Director agreement, potentially after IESG review.

Those requirements explain why directing a draft to INTAREA is not a complete answer. A forum can have the right remit without having an assembled team for every specialist proposal. The broadband list could make that team easier to find: contributors need not repeatedly discover who knows an access-network problem or where related work is being discussed.

That is a plausible benefit, not yet a demonstrated result. The reviewed sources do not quantify existing review capacity or show that the new list has secured commitments.

Less searching, not less scrutiny

For a newcomer, reducing the search for a knowledgeable audience could be meaningful. An experienced participant may know which group to approach and whom to ask for a review. A first-time contributor may have to reconstruct those relationships before the technical argument is even heard.

A focal list can make that navigation more public. It can collect related questions and help identify whether an issue needs a small extension, existing-group work or a broader discussion. None of those outcomes requires treating more email as better engineering.

The list is expressly a non-working-group venue. IETF guidance allows such lists to support prospective group formation. The announcement does not approve a new working group, transfer Broadband Forum responsibilities or commit to delivering a standard. Those boundaries matter, but the immediate operational question is simpler: who will keep reading after the introductory messages?

As checked on 3 September, the public archive displayed one message, the creation announcement. That is too little history to judge success. It is not a count of subscribers, evidence of absent interest or an inventory of work elsewhere.

The first meaningful gain would be a clearer path from a specific access problem to people prepared to assess it. Creating that path is coordination work. Keeping it useful requires review labour.

Sources

  1. Broadband list announcement
  2. INTAREA charter and active status
  3. Broadband public archive
  4. Non-working-group list guidelines