IETF AI drafts, RDAP, and deep-space addressing

IETF working groups spent the day on AI-generated draft quality, RDAP contact formats, deep-space IPv6 allocation, and power-aware traffic engineering. Side threads covered RPKI terminology adoption and a Spamhaus listing affecting Cloudflare addresses.

AI-generated Internet-Draft flood draws heated IETF debate

An absurd submission prompted discussion on the IETF list about controlling AI-generated Internet-Drafts. Participants disagreed over whether commenters need practical LLM experience to weigh in on process fixes. The exchange underscores how generative tools are already stressing traditional document intake and review norms.

RDAP JSContact draft raises compatibility questions

The REGEXT working group examined draft-ietf-regext-rdap-jscontact-26, which would replace jCard. Members flagged technical issues around signaling and compatibility with RFC 9083. The outcome will shape how registration data is represented in RDAP responses going forward.

Deep-space IPv6 address space draft opens architecture debate

A new merged draft proposes dedicated IPv6 space for celestial bodies and transit craft. The deepspace list discussed aggregation architecture against existing NRO policy constraints. Readers tracking non-terrestrial networking will want to watch how address management principles scale beyond Earth.

Distributed power-aware TE feasibility challenged

The TEAS working group continued its adoption call for draft-many-teas-power-steering while questioning whether distributed power-aware path computation is practical. Technical objections focused on the limits of local knowledge for energy-aware steering. The debate matters for operators trying to reduce network power draw without centralized control.

SIDROPS weighs RPKI terminology draft adoption

SIDROPS opened a call for adoption of the informational draft-yan-sidrops-rpki-terminology-05. Discussion centered on definition precision, ongoing maintenance, and appropriate scope. Clear shared vocabulary would reduce ambiguity across RPKI implementations and documents.

Spamhaus DROP listing of Cloudflare addresses

A NANOG thread noted Cloudflare IP ranges appearing on the Spamhaus DROP list. Participants debated where responsibility for hosted abuse properly sits between network operators and their customers. The exchange highlights ongoing friction in large-scale abuse mitigation.