Revisit Data Model Cardinality (Single vs. Multiple Services)

[garyillyes]

Martin has questioned the utility of defining multiple services within a single JAFAR file (service tag).

While large operators share infrastructure, it may be cleaner to either copy identical content or have different files for different services (e.g., "googlebot" vs others). The current draft structure might be "over-engineered" compared to the reality where a crawler operates a logical service from IP ranges.

Proposed Structure:
Martin suggested a simplified structure that focuses on a single service definition:

{
  "service": "googlebot",
  "description": "https://some.url/for/googlebot",
  "notes": "...",
  "lastUpdated": "2026-01-01T11:00Z",
  "ipv4": ["192.0.2/8", "..."],
  "ipv6": ["2404:6800:4006::/56", "..."]
}

Proposed Action:
Discuss changing the cardinality rules to support one service per file to reduce complexity for consumers.

Reference:
https://mailarchive.ietf.org/arch/msg/web-bot-auth/UXpJMWkKTNCk_5OD2j01b782n3w/