IETF discipline, ASN hijack reports, and protocol drafts

IESG process, routing security incidents, and several working-group proposals dominated Internet protocol discussion. Governance action under RFC 3683 drew the most attention, followed by operational reports and architecture debates.

IESG last call on PR-action against Ken Kubota

The IESG opened a last call on an RFC 3683 PR-action that would suspend Ken Kubota's posting rights on the tls, sshm, mod-discuss, and ietf mailing lists. The action cites repeated unprofessional commentary. Participants are weighing the balance between list moderation and community participation norms.

Unauthorized origin reported for AS27421

An operator reported unauthorized announcement of AS27421 originating from Brazil. The NANOG thread examined RPKI validation, ASPA coverage, and escalation through upstream providers. The exchange underscores ongoing reliance on routing security tooling to contain prefix hijacks.

IPv6 address space proposed for celestial bodies

A merged individual draft proposes dedicated IPv6 blocks for celestial bodies under the deepspace discussion. List traffic debated whether the IETF should define the architecture or leave policy to the NRO, along with practical questions of spacecraft renumbering. The proposal tests the boundary between protocol design and address policy.

New DNS RRTYPEs for UNECE and ISO registry codes

An individual draft on DNSOP proposes two new resource record types that would carry UNECE and ISO registry codes verbatim for DIEM use cases. Discussion focused on semantic clarity and the appropriate standards-track process. Operators watching registry integration in DNS will want to track the outcome.

Feasibility disputed for distributed power-aware TE

TEAS working-group traffic questioned whether distributed power-aware traffic-engineering path computation is achievable in draft-many-teas-power-steering. Multiple participants argued the approach is impractical under current constraints. The debate may affect adoption of energy-aware routing mechanisms.

Key-expiry tag floated for DKIM2

Timo Gerke proposed a key-exp tag and a flattened JSON array construct for DKIM2 key validity. Working-group members repeatedly noted that the current draft does not employ JSON for signatures. The exchange clarifies remaining design choices before further DKIM2 revisions.