Should Section 7 be a part of THIS specification or a separate specification?

[elear]

There is the CSAF format and then there are procedures for those who are sharing CSAF files. These matters seem rather distinct. Also, the format seems to me a bit more baked than this section.

[sthagen]

@elear Thank you so much for your feedback. Please kindly perform another step to enable the TC to consider (please see below excerpt from the invitation to comment at https://www.oasis-open.org/2021/08/13/invitation-to-comment-on-common-security-advisory-framework-v2-0/ in case the following suggestions are not clear).

For non-Tc-members it is well possible to submit the feedback as a list of URLs pointing to this issue and its siblings, but please kindly either provide the feedback per colleagues being members of this TC or go once through the process of registering with the mailing list manager of the comments list (cf. below).

I think the set of titles and URLs for now to include in such an email could be:

• Section 7.1.6: Redirects - Section 7.1.6: Redirects #342
• Section 5.1 filename - Section 5.1 filename #343
• Should Section 7 be a part of THIS specification or a separate specification? - Should Section 7 be a part of THIS specification or a separate specification? #344
• Section 7.1.19: OpenPGP signatures? - Section 7.1.19: OpenPGP signatures? #345

Sorry for any inconvenience and thanks for the feedback. When submitted to the comments list or per a TC member the TC will greatly appreciate and of course consider.

How to Provide Feedback during Public Review

OASIS and the CSAF TC value your feedback. We solicit input from developers, users and others, whether OASIS members or not, for the sake of improving the interoperability and quality of our technical work.

The public review starts 14 August 2021 at 00:00 UTC and ends 12 September 2021 at 23:59 UTC.

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be used by following the instructions on the TC’s “Send A Comment” page (https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=csaf).

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:
https://lists.oasis-open.org/archives/csaf-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review, we call your attention to the OASIS IPR Policy [1] applicable especially [2] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.

Additional information about the specification and the CSAF TC can be found at the TC’s public home page:
https://www.oasis-open.org/committees/csaf/

[sthagen]

@elear thanks a lot - received per email to the csaf comments mailing list at https://lists.oasis-open.org/archives/csaf-comment/202108/msg00001.html @santosomar, @tschmidtb51

[santosomar]

Thank you for the feedback and input. During the TC monthly meeting on Sep 29, 2021, the OASIS Common Security Advisory Framework (CSAF) TC has reviewed your feedback and has voted not to making any changes at this time in CSAF 2.0. This could be considered at a later time as a separate specification, but not a change in the current CSAF 2.0 spec.