Subject: [Asdf] Consensus call to adopt draft-ietf-asdf-sdf-03 and mark it as Implementation Draft (SDF 1.1)

From: Niklas Widell <[email-masked]>
Date: Tue, 23 Feb 2021 21:01:57 +0000

Two weeks ago, the authors have submitted draft-ietf-asdf-sdf-02 that addressed the open issues on the previous draft.  So far, the only feedback to -02 apart from address corrections was the intended status, which led to -03 yesterday.

https://datatracker.ietf.org/doc/draft-ietf-asdf-sdf/

The chairs intend to adopt the -03 version and mark it as an Implementation Draft, to be identified as SDF 1.1. The intent of the Implementation Draft status is to identify a stable intermediate specification that implementations and toolchains can be targeted at, while work on the specification continues for additional required features.

We are looking for substantive objections to the technical content of the document. Please note that the document is still an internet-draft, and is therefore very open to all manners of feedback related to understandability, such as editorial comments, clarifications and similar. Nits and tyops are welcome, but the main question is:
Is this draft ready to be used as a stable Implementation Draft for SDF 1.1?

At this point no new features will be added to the SDF 1.1 scope.  That doesn’t mean that we don’t want to hear about them.  Instead, all proposals for new features will be added to the backlog for handling after SDF 1.1, including potential discussion at IETF 110.

This mail starts the consensus call on draft-ietf-asdf-sdf-03 as the SDF 1.1 Implementation Draft. The call ends on March 9th, and consensus, if we have it, will be finalized at the ASDF meeting on March 11th.

Michael and Niklas