Skip to main content

Shepherd writeup
draft-ietf-cose-tsa-tst-header-parameter

Document History

Does the working group (WG) consensus represent the strong concurrence of a
few individuals, with others being silent, or did it reach broad agreement?

The specification does one simple thing that has working group support.  Most
of the on-list discussion happened during WGLC, with about 10 people
participating, some providing substantive feedback that was addressed after
WGLC.  The document has working group consensus.

Was there controversy about particular points, or were there decisions where
the consensus was particularly rough?

The was not controversy.  The feedback received was largely about the
exposition.  This is bringing an existing mechanism to COSE.

Has anyone threatened an appeal or otherwise indicated extreme discontent? If
so, please summarize the areas of conflict in separate email messages to the
responsible Area Director. (It should be in a separate email because this
questionnaire is publicly available.)

I am not aware of any threatened appeals or extreme discomfort.

For protocol documents, are there existing implementations of the contents of
the document? Have a significant number of potential implementers indicated
plans to implement? Are any existing implementations reported somewhere,
either in the document itself (as RFC 7942 recommends) or elsewhere
(where)?

C2PA 2.1 uses this specification, and is implemented by Microsoft, Google, and
Trupic.  Measur.io has an implementation.

Additional Reviews

Do the contents of this document closely interact with technologies in other
IETF working groups or external organizations, and would it therefore benefit
from their review? Have those reviews occurred? If yes, describe which
reviews took place.

Not that I'm aware of.

Describe how the document meets any required formal expert review criteria,
such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.

No such criteria apply.

If the document contains a YANG module, has the final version of the module
been checked with any of the recommended validation tools for syntax and
formatting validation? If there are any resulting errors or warnings, what is
the justification for not fixing them at this time? Does the YANG module
comply with the Network Management Datastore Architecture (NMDA) as specified
in RFC 8342?

The document contains no YANG module.

Describe reviews and automated checks performed to validate sections of the
final version of the document written in a formal language, such as XML code,
BNF rules, MIB definitions, CBOR's CDDL, etc.

Document Shepherd Checks

Based on the shepherd's review of the document, is it their opinion that this
document is needed, clearly written, complete, correctly designed, and ready
to be handed off to the responsible Area Director?

This document solves a narrow but useful problem and solves it well.  It is
ready to hand off to our AD.

Several IETF Areas have assembled lists of common issues that their
reviewers encounter. For which areas have such issues been identified
and addressed? For which does this still need to happen in subsequent
reviews?

It doesn't appear that most of the common Security Area issues at
https://wiki.ietf.org/group/sec/typicalSECareaissues apply, other than Thread
Models, which are discussed in the Security Considerations section.

What type of RFC publication is being requested on the IETF stream (Best
Current Practice, Proposed Standard, Internet Standard,
Informational, Experimental or Historic)? Why is this the proper type
of RFC? Do all Datatracker state attributes correctly reflect this intent?

Proposed Standard status is being requested, and is accurately reflected in the
datatracker.  This status seems appropriate for the specification.

Have reasonable efforts been made to remind all authors of the intellectual
property rights (IPR) disclosure obligations described in BCP 79? To
the best of your knowledge, have all required disclosures been filed? If
not, explain why. If yes, summarize any relevant discussion, including links
to publicly-available messages when applicable.

All three authors have responded that they are not aware of any IPR
considerations that apply to the specification.

Has each author, editor, and contributor shown their willingness to be
listed as such? If the total number of authors and editors on the front page
is greater than five, please provide a justification.

Yes, they are willing.

Document any remaining I-D nits in this document. Simply running the idnits
tool is not enough; please review the "Content Guidelines" on
authors.ietf.org. (Also note that the current idnits tool generates
some incorrect warnings; a rewrite is underway.)

I believe that the reference [IANA.cose_header-parameters] should be
informative.  Also, stylistially, it would appear to be better to use either
dash or underscore in the reference, but not both in a mixed fashion.

Should any informative references be normative or vice-versa? See the IESG
Statement on Normative and Informative References.

I believe that the reference [IANA.cose_header-parameters] should be
informative.

List any normative references that are not freely available to anyone. Did
the community have sufficient access to review any such normative
references?

There are no such references.

Are there any normative downward references (see RFC 3967 and BCP
97) that are not already listed in the DOWNREF registry? If so,
list them.

There are no such references.

Are there normative references to documents that are not ready to be
submitted to the IESG for publication or are otherwise in an unclear state?
If so, what is the plan for their completion?

There are no such references.

Will publication of this document change the status of any existing RFCs? If
so, does the Datatracker metadata correctly reflect this and are those RFCs
listed on the title page, in the abstract, and discussed in the
introduction? If not, explain why and point to the part of the document
where the relationship of this document to these other RFCs is discussed.

Publication of this document will not change the status of any existing RFCs.

Describe the document shepherd's review of the IANA considerations section,
especially with regard to its consistency with the body of the document.
Confirm that all aspects of the document requiring IANA assignments are
associated with the appropriate reservations in IANA registries. Confirm
that any referenced IANA registries have been clearly identified. Confirm
that each newly created IANA registry specifies its initial contents,
allocations procedures, and a reasonable name (see RFC 8126).

The IANA Considerations section appears to be consistent with the rest of the
specification.

List any new IANA registries that require Designated Expert Review for
future allocations. Are the instructions to the Designated Expert clear?
Please include suggestions of designated experts, if appropriate.

The specification creates no new IANA registries.
Back