A new document circulating through the Internet Engineering Task Force tries to pin down what age verification actually costs. Titled “Age Verification Architecture,” the Internet-Draft sets out a technology-neutral way of describing how online intermediaries gate content and services by age, and it weighs each approach on two axes: how well it works, and how much privacy it consumes.
The draft is careful to separate the ways of establishing age, working through age credentials, age verification, age assurance, and age estimation before turning to how each is enforced across different kinds of platforms. Its authors say the aim is to lay bare the technical difficulties in any age-gating scheme so that it can work without creating security and privacy risks or trampling human rights, and they insist these are engineering questions distinct from, if often driven by, the political goal of protecting children online.
That framing carries the document into territory most technical specifications skip. A long stretch is given to human rights, with sections on free expression, free association, and social, cultural, and economic rights, reflecting a concern that a clumsy age check either shuts people out of services or forces them to reveal far more about themselves than a simple age question should require. Regulators are wrestling with the same tension; Australia’s privacy watchdog has set a proportionality test for age assurance, cautioning that a check should collect no more data than the situation warrants.
The draft is the work of Mallory Knodel of the Social Web Foundation, Gianpaolo Scalone of Vodafone Group, Tom Newton of Qoria, and Audrey Hingle of Exchange Point. It is an Informational Internet-Draft rather than a standard, which means it carries no requirements and will lapse in January 2027 unless it is revised. It enters a field where more formal rulebooks are already taking shape, among them the ISO/IEC 27566-1 framework for age-assurance systems that the International Organization for Standardization published late last year.
Sources: IETF
–
By Cass Kennedy






Follow Us