IETF Last Call Review of draft-ietf-pim-gaap-18
review-ietf-pim-gaap-18-opsdir-lc-wu-2026-08-04-00

Hi,

I have been selected as the Operational Directorate (opsdir) reviewer for this
Internet-Draft.

The Operational Directorate reviews all operational and management-related
Internet-Drafts to ensure alignment with operational best practices and that
adequate operational considerations are covered.

A complete set of _"Guidelines for Considering Operations and Management in
IETF Specifications"_ can be found at
https://datatracker.ietf.org/doc/draft-ietf-opsawg-rfc5706bis/.

While these comments are primarily for the Operations and Management Area
Directors (Ops ADs), the authors should consider them alongside other feedback
received.

- Document: [draft-ietf-pim-gaap-18]

- Reviewer: [Bo Wu]

- Intended Status: [Experimental]

---
Summary:

GAAP defines a lightweight decentralized multicast address allocation
mechanism. As an Experimental protocol, the Operational Considerations section
provides useful high-level guidance, but the dependencies on existing multicast
protocols and the deployment boundaries could be clarified further.

## Minor Issues

1. Deployment prerequisites and network dependencies
GAAP Claim messages are sent to well-known multicast addresses. This requires
the underlying network to support multicast routing/forwarding (e.g., IGMP,
PIM-SM, or PIM-SSM). It is recommended that the Operational Considerations
section explicitly state these prerequisites. Deployment boundaries

2. Additionally, Section 7 could clarify the intended deployment boundary
(administrative domain scope, expected scale in terms of nodes/groups). For
example, is the scenario defined in I-D.ietf-pim-zeroconf-mcast-addr-alloc-ps
the primary intended use case for GAAP? Is GAAP applicable to PIM-SM
deployments, and what is its relationship to the PIM RP?

---

## Nits

3. Terminology structure in Section 2
The definition of "GAAP Group Address" currently embeds the application
allocation range values (TBD1/10, TBD2/32), which is confusing. It is
recommended to move these to the "Group Address" definition to avoid conflating
the control-plane address with the group allocation pool.

4. Section 4 Group Name definition
The 255-octet maximum length is only stated in "Multi-record parsing". For
consistency, the "Group Name" definition could include: "The string MUST NOT
exceed 255 octets in length (not including the null terminator)."

5. Section 5.1 gaap.init()
s/"a application"/"an application"/

6. Section 6.2
Add a comma after "GAAP node": "When a group address is allocated by a GAAP
node, it will build and send a Claim message."

7. Section 8 Security Considerations
Expand AEAD on first use: "Authenticated Encryption with Associated Data (AEAD)
construction ..."