Hi Roman, Now that the COSE charter has been updated to bring the TSA-TST document in scope, I believe this DISCUSS could be cleared.
cheers, thanks! On Fri, 2 May 2025 at 17:33, Roman Danyliw via Datatracker <[email protected]> wrote: > > Roman Danyliw has entered the following ballot position for > draft-ietf-cose-tsa-tst-header-parameter-05: Discuss > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > Please refer to > https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ > for more information about how to handle DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/draft-ietf-cose-tsa-tst-header-parameter/ > > > > ---------------------------------------------------------------------- > DISCUSS: > ---------------------------------------------------------------------- > > For the responsible AD and WG chairs -- this document is not in scope for the > current WG charter. My understanding of its substance is that it defines two, > new COSE attributes. The approved -03 charter explicitly says: > > “The WG will produce documents for new attributes only if they are in the > list of deliverables below. A re-charter will be required to expand that list. > The WG is expected as part of normal processing to review and comment on > attributes that are not in charter but are of general public interest.” > > There is no subsequent reference to work about specifying timestamp related > attributes in the work items section of the charter (or any other place). > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > Thank you to Linda Dunbar for the GENART review. > > > _______________________________________________ COSE mailing list -- [email protected] To unsubscribe send an email to [email protected]
