Markdown Version | Session Recording

Session Date/Time: 21 May 2025 13:00

ARTAREA

Summary

The ARTAREA interim meeting covered several key topics: an experimental approach by the Area Directors (ADs) to use GitHub for administrative tasks and community collaboration; a status update and charter proposal for a potential new working group on Domain Connect (decon); a presentation on "JSON Structure" as a new data definition language; and a proposal to update the AS2 protocol (RFC 4130). The meeting concluded with a brief discussion on the stalled progress of the emailcore working group and a proposal to consolidate its work into Mailmate.

Key Discussion Points

• Usage of GitHub in the ARTAREA:
  • ARTAREA ADs are experimentally using a GitHub repository (IETF art area) for internal issue tracking, administrative processes (e.g., balloting templates, ISG review prep), and documenting guidance for future ADs.
  • The intent is to provide a visible footprint and facilitate collaboration, while explicitly stating that the mailing list and data tracker remain the source of truth for IETF processes.
  • Initial feedback cautioned about potential challenges with GitHub's activity level discouraging participation, particularly for intermittent contributors, and the need for a careful balance with mailing list communication.
  • The ADs confirmed the repository would also be used for community feedback on documents like Area and AD Job Descriptions for NOMCOM, allowing for version control and community input on these evolving artifacts.
  • The experiment is specific to the current AD term and not binding for future ADs.
• Domain Connect (decon) Status Update:
  • Pablo presented Domain Connect, an application-level protocol for simplified DNS zone record setup between application and DNS providers, featuring template-based configuration, synchronous/asynchronous flows, and conflict resolution.
  • The protocol has gained adoption since its first proposal in 2016 but has struggled to find a suitable IETF working group.
  • An AD-sponsored draft initially, it was suggested the document required more polishing, leading to the creation of a dedicated mailing list and a proposal for a new working group.
  • A draft charter proposes a focused working group to precisely specify the protocol, resolve ambiguities, and make it suitable for a Standard Track RFC.
  • An open discussion point in the charter refers to RFC 7021 regarding the strictness of protecting the installed base versus allowing changes.
• JSON Structure:
  • Clemens presented JSON Structure (json-structure.org), a proposed data definition language aimed at improving type safety, data quality, and code generation for messaging and API scenarios.
  • It addresses perceived limitations of JSON Schema, which is seen as a data validation language rather than a data definition language, making it difficult for consistent code generation.
  • Key features include required and named types, an extended set of primitive data types with native JSON mappings, explicit namespaces, controlled external imports, and a model for type reuse (abstract extends).
  • Companion specifications are proposed for internationalization, scientific units/currencies, and the reintroduction of validation constraints and conditional composition as optional add-ins.
  • The goal is to provide a stable foundation (ideally an RFC) for defining data structures in HTTP APIs, messaging, and eventing.
  • Discussion highlighted its divergence from JSON Schema towards approaches seen in ASN.1 or Protobuff, focusing on programmatic interoperability.
• Update RFC 4130 (AS2):
  • Deborah presented a proposal to update RFC 4130, the 20-year-old specification for AS2, a critical B2B data exchange protocol.
  • The current RFC references outdated security algorithms (e.g., SHA-1, 3DES) and lacks modern ones (SHA-2, AES), guidance for automation (certificate exchange), and documentation for commonly used features (multi-part attachments, filename preservation).
  • Drummond Group, with deep experience in AS2 interoperability testing and certification, is leading the effort to modernize the standard to align with current security best practices, maintain industry trust, and ensure backward compatibility.
  • The proposal aims to clarify ambiguous behaviors, define optional profiles, and incorporate test-derived best practices.
• Email Core / Mailmate Discussion:
  • John Clenson raised concerns about the stalled progress of the emailcore working group in revising fundamental email protocol documents (specifically 321 BIS), citing issues with IANA and the Security Area, and a lack of energy and consensus in the working group.
  • The mailmate working group was initially created for smaller, focused tasks.

Decisions and Action Items

• Agenda Item Deferral: The discussion on "allocation of email tasks" (Email Core / Mailmate) was deferred to the end of the meeting due to time constraints.
• ARTAREA GitHub Experiment: The ARTAREA ADs will continue their experiment with GitHub for administrative tasks and community-facing documentation, with the understanding that the mailing list remains the source of truth and the experiment is not mandatory for future ADs.
• Domain Connect Charter: The ARTAREA AD will continue to refine the Domain Connect (decon) charter on the decon mailing list. Once agreement is reached, the charter will be uploaded to the data tracker for the formal chartering process.
• Email Core / Mailmate Consolidation: The ARTAREA AD (Andy Newton) will investigate the scope of outstanding work from the emailcore working group (particularly for the 321 BIS document) and propose consolidating this work into the mailmate working group. This will involve emailing both mailing lists to confirm consensus for the move.

Next Steps

• Domain Connect:
  • The community is encouraged to provide further feedback on the decon charter (especially regarding the RFC 7021 reference) on the decon mailing list or directly to the ADs.
  • Pablo is invited to consider presenting the Domain Connect proposal at the Dispatch WG during IETF 123 in Madrid to gain broader visibility.
• JSON Structure:
  • Clemens encourages feedback and discussion on json-structure.org and the relevant mailing lists to refine the specifications.
• Update RFC 4130 (AS2):
  • Deborah will present the proposal to update RFC 4130 at the Dispatch WG.
  • Community feedback, including discussions on potentially reopening the historical ED working group, is welcomed on the art mailing list. Jim offered to assist with defining clear next steps.
• Email Core / Mailmate:
  • The ARTAREA AD will engage with the emailcore and mailmate working groups via their mailing lists to propose and facilitate the consolidation of email protocol revision work.
  • The AD will work to re-energize efforts on email protocol updates.
• General: Participants are encouraged to send any comments on the interim meeting itself to the ARTAREA mailing list.