OASIS OpenEoX TC

 View Only
Expand all | Collapse all

Motion to Approve the End of Security Support Definition in PR #73

  • 1.  Motion to Approve the End of Security Support Definition in PR #73

    Posted 12 days ago
    Dear TC members,
     
    I,  Omar Santos, hereby move for the OpenEoX TC to approve the "End of Security Support (EoSS)" definition, as introduced in pull request https://github.com/oasis-tcs/openeox/pull/73 
     
    I hereby request that, if seconded, and no objection received per this list before one week has passed on 2025-04-17 19:00 UTC to automatically carry.
     
    A notice of approval will be communicated to all committee members and stakeholders.


    ------------------------------
    Best regards,

    Omar Santos
    ------------------------------


  • 2.  RE: Motion to Approve the End of Security Support Definition in PR #73

    Posted 11 days ago
    Hello TC Members,

    This morning I talked with Langley and it seems that "EoSS" acronym can cause some acronyms conflict and potential misunderstandings.
    I would like to propose to keep the "End of Security Support" definition but change the acronym to "EoSecS".

    Therefore, I object the acronym and thus the motion.

    Best,
    Rogue

    Przemyslaw Roguski

    Principal Product Security Engineer

    Red Hat

    email: proguski@redhat.com
    nickname: Rogue







  • 3.  RE: Motion to Approve the End of Security Support Definition in PR #73

    Posted 11 days ago
    TC Members, just to avoid any confusion and wrong feelings about "EoSecS", we can use the "EoSSec" acronym for the "End of Security Support" definition.

    Best,
    Rogue

    Przemyslaw Roguski

    Principal Product Security Engineer

    Red Hat

    email: proguski@redhat.com
    nickname: Rogue







  • 4.  RE: Motion to Approve the End of Security Support Definition in PR #73

    Posted 11 days ago

    Thank you, Rogue!

    Dear TC members,
    I will withdraw my original. The following is my new motion:
     
    I,  Omar Santos, hereby move for the OpenEoX TC to approve the "End of Security Support (EoSSec)" definition, as addressed in pull request https://github.com/oasis-tcs/openeox/pull/73 
     
    I hereby request that, if seconded, and no objection received per this list before one week has passed on 2025-04-18 18:00 UTC to automatically carry.
     
    A notice of approval will be communicated to all committee members and stakeholders.


    ------------------------------
    Best regards,

    Omar Santos
    ------------------------------



  • 5.  RE: Motion to Approve the End of Security Support Definition in PR #73

    Posted 11 days ago
    Hi all,

    Is it really a big concern for the users on OpenEoX users to get
    confused by EoSS?

    It seems not to me for the users on OpenEoX. EoSSec seems confusing too.

    Can we have a vote for determining the name for it? Like, EoSS, EofSS,
    EoSecS, EoSSec, ...

    Thanks,

    --Feng


    On 4/10/2025 12:37 PM, Omar Santos via OASIS wrote:
    > Thank you, Rogue! Dear TC members, I will withdraw my original. The
    > following is my new motion: I, Omar Santos, hereby move for the
    > OpenEoX... -posted to the "OASIS OpenEoX TC" community
    >
    >
    > OASIS OpenEoX TC <https: urldefense.com v3 __https:></https:>
    > open.org/communities/community-home/digestviewer?
    > CommunityKey=26350f39-9c7b-4bf2-a422-018dc7d3f5aa__;!!ACWV5N9M2RV99hQ!
    > MJSZcs-EHpL5q6RHht0icOlMXsU06NCkJZ58cFd4peTMfSnBZ5kfSIs-
    > d9994LYkfjA3k8-bcjexc2KoimIwHdC7$>
    >
    > Post New Message <mailto:oasis-openeox@connectedcommunity.org>
    >
    > Re: Motion to Approve the End of Security Support Definition in PR #73
    > <https: urldefense.com v3 __https: groups.oasis-open.org discussion></https:>
    > motion-to-approve-the-end-of-security-support-definition-in-
    > pr-73*bm6dca631c-4849-472e-8cfc-0196213143bb__;Iw!!ACWV5N9M2RV99hQ!
    > MJSZcs-EHpL5q6RHht0icOlMXsU06NCkJZ58cFd4peTMfSnBZ5kfSIs-d9994LYkfjA3k8-
    > bcjexc2KoiqQqskBq$>
    > Reply to Group
    > <mailto:oasis_openeox_6dca631c-4849-472e-8cfc-0196213143bb@connectedcommunity.org?subject=re: motion to approve the end of security support definition in pr #73> Reply to Sender via Email <mailto:osantos@cisco.com?subject=re: motion to approve the end of security support definition in pr #73>
    >
    > Omar Santos <https: urldefense.com v3 __https: groups.oasis-open.org></https:>
    > profile?UserKey=b5a4e963-cf09-4924-ae00-018dc8ee0f8d__;!!
    > ACWV5N9M2RV99hQ!MJSZcs-EHpL5q6RHht0icOlMXsU06NCkJZ58cFd4peTMfSnBZ5kfSIs-
    > d9994LYkfjA3k8-bcjexc2Kois5Ise3I$>
    > Apr 10, 2025 3:37 PM
    > Omar Santos <https: urldefense.com v3 __https: groups.oasis-open.org></https:>
    > profile?UserKey=b5a4e963-cf09-4924-ae00-018dc8ee0f8d__;!!
    > ACWV5N9M2RV99hQ!MJSZcs-EHpL5q6RHht0icOlMXsU06NCkJZ58cFd4peTMfSnBZ5kfSIs-
    > d9994LYkfjA3k8-bcjexc2Kois5Ise3I$>
    >
    > Thank you, Rogue!
    >
    > Dear TC members,
    > I will withdraw my original. The following is my new motion:
    > I,  Omar Santos, hereby move for the OpenEoX TC to approve the "End of
    > Security Support (EoSSec)" definition, as addressed in pull request
    > github.com/oasis-tcs/openeox/pull/73 <https: urldefense.com v3></https:>
    > __https://github.com/oasis-tcs/openeox/pull/73__;!!ACWV5N9M2RV99hQ!
    > MJSZcs-EHpL5q6RHht0icOlMXsU06NCkJZ58cFd4peTMfSnBZ5kfSIs-d9994LYkfjA3k8-
    > bcjexc2KoihUbjLIf$>
    > I hereby request that, if seconded, and no objection received per this
    > list before one week has passed on 2025-04-18 18:00 UTC to automatically
    > carry.
    > A notice of approval will be communicated to all committee members and
    > stakeholders.
    >
    >
    > ------------------------------
    > Best regards,
    >
    > Omar Santos
    > ------------------------------
    >
    > *Reply to Group via Email
    > <mailto:oasis_openeox_6dca631c-4849-472e-8cfc-0196213143bb@connectedcommunity.org?subject=re: motion to approve the end of security support definition in pr #73>* *Reply to Sender via Email <mailto:osantos@cisco.com?subject=re: motion to approve the end of security support definition in pr #73>* *View Thread <https: urldefense.com v3 __https: groups.oasis-open.org discussion motion-to-approve-the-end-of-security-support-definition-in-pr-73*bm6dca631c-4849-472e-8cfc-0196213143bb__;iw!!acwv5n9m2rv99hq!mjszcs-ehpl5q6rhht0icolmxsu06nckjz58cfd4petmfsnbz5kfsis-d9994lykfja3k8-bcjexc2koiqqqskbq$>* *Recommend <https: urldefense.com v3 __https: groups.oasis-open.org:443 discussion motion-to-approve-the-end-of-security-support-definition-in-pr-73?messagekey=6dca631c-4849-472e-8cfc-0196213143bb&cmd=rate&cmdarg=add*bm6dca631c-4849-472e-8cfc-0196213143bb__;Iw!!ACWV5N9M2RV99hQ!MJSZcs-EHpL5q6RHht0icOlMXsU06NCkJZ58cFd4peTMfSnBZ5kfSIs-d9994LYkfjA3k8-bcjexc2Koioj0eA4b$>* *Forward <https: urldefense.com v3 __https: groups.oasis-open.org communities all-discussions forwardmessages?messagekey=6dca631c-4849-472e-8cfc-0196213143bb&ListKey=ea1c4c7d-8889-47e5-ba75-018dce2e601d__;!!ACWV5N9M2RV99hQ!MJSZcs-EHpL5q6RHht0icOlMXsU06NCkJZ58cFd4peTMfSnBZ5kfSIs-d9994LYkfjA3k8-bcjexc2KoijBmdEch$>*
    > -------------------------------------------
    > Original Message:
    > Sent: 04-10-2025 15:18
    > From: Przemyslaw Roguski
    > Subject: Motion to Approve the End of Security Support Definition in PR #73
    >
    > TC Members, just to avoid any confusion and wrong feelings about
    > "EoSecS", we can use the "EoSSec" acronym for the "End of Security
    > Support" definition.
    >
    > Best,
    > Rogue
    >
    > Przemyslaw Roguski
    >
    > Principal Product Security Engineer
    >
    > Red Hat <https: urldefense.com v3 __https: www.redhat.com __;!!></https:>
    > ACWV5N9M2RV99hQ!MJSZcs-EHpL5q6RHht0icOlMXsU06NCkJZ58cFd4peTMfSnBZ5kfSIs-
    > d9994LYkfjA3k8-bcjexc2KoijWTmpUu$>
    >
    > email: proguski@redhat.com <mailto:proguski@redhat.com>
    > nickname: Rogue
    >
    > <https: urldefense.com v3 __https: red.ht sig__;!!acwv5n9m2rv99hq!></https:>
    > MJSZcs-EHpL5q6RHht0icOlMXsU06NCkJZ58cFd4peTMfSnBZ5kfSIs-d9994LYkfjA3k8-
    > bcjexc2KoiqIJTZcV$>
    >
    >
    >
    > Original Message:
    > Sent: 4/10/2025 3:06:00 PM
    > From: Przemyslaw Roguski
    > Subject: RE: Motion to Approve the End of Security Support Definition in
    > PR #73
    >
    > Hello TC Members,
    >
    > This morning I talked with Langley and it seems that "EoSS" acronym can
    > cause some acronyms conflict and potential misunderstandings.
    > I would like to propose to keep the "End of Security Support" definition
    > but change the acronym to "EoSecS".
    >
    > Therefore, I object the acronym and thus the motion.
    >
    > Best,
    > Rogue
    >
    > Przemyslaw Roguski
    >
    > Principal Product Security Engineer
    >
    > Red Hat <https: urldefense.com v3 __https: www.redhat.com __;!!></https:>
    > ACWV5N9M2RV99hQ!MJSZcs-EHpL5q6RHht0icOlMXsU06NCkJZ58cFd4peTMfSnBZ5kfSIs-
    > d9994LYkfjA3k8-bcjexc2KoijWTmpUu$>
    >
    > email: proguski@redhat.com <mailto:proguski@redhat.com>
    > nickname: Rogue
    >
    > <https: urldefense.com v3 __https: red.ht sig__;!!acwv5n9m2rv99hq!></https:>
    > MJSZcs-EHpL5q6RHht0icOlMXsU06NCkJZ58cFd4peTMfSnBZ5kfSIs-d9994LYkfjA3k8-
    > bcjexc2KoiqIJTZcV$>
    >
    >
    >
    > Original Message:
    > Sent: 4/9/2025 6:45:00 PM
    > From: Omar Santos
    > Subject: Motion to Approve the End of Security Support Definition in PR #73
    >
    > Dear TC members,
    > I,  Omar Santos, hereby move for the OpenEoX TC to approve the "End of
    > Security Support (EoSS)" definition, as introduced in pull request
    > github.com/oasis-tcs/openeox/pull/73 <https: urldefense.com v3></https:>
    > __https://github.com/oasis-tcs/openeox/pull/73__;!!ACWV5N9M2RV99hQ!
    > MJSZcs-EHpL5q6RHht0icOlMXsU06NCkJZ58cFd4peTMfSnBZ5kfSIs-d9994LYkfjA3k8-
    > bcjexc2KoihUbjLIf$>
    > I hereby request that, if seconded, and no objection received per this
    > list before one week has passed on 2025-04-17 19:00 UTC to automatically
    > carry.
    > A notice of approval will be communicated to all committee members and
    > stakeholders.
    >
    >
    > ------------------------------
    > Best regards,
    >
    > Omar Santos
    > ------------------------------
    >
    >
    >
    >
    > You are subscribed to "OASIS OpenEoX TC" as feng.cao@oracle.com. To
    > change your subscriptions, go to My Subscriptions <https:></https:>
    > urldefense.com/v3/__http://oasis.connectedcommunity.org/preferences?
    > section=Subscriptions__;!!ACWV5N9M2RV99hQ!MJSZcs-
    > EHpL5q6RHht0icOlMXsU06NCkJZ58cFd4peTMfSnBZ5kfSIs-d9994LYkfjA3k8-
    > bcjexc2KoihF3hozt$>. To unsubscribe from this community discussion, go
    > to Unsubscribe <https: urldefense.com v3 __https:></https:>
    > oasis.connectedcommunity.org/HigherLogic/eGroups/Unsubscribe.aspx?
    > UserKey=c1de98ab-99b9-4108-
    > b7f8-018dc7f80c96&sKey=KeyRemoved&GroupKey=ea1c4c7d-8889-47e5-
    > ba75-018dce2e601d__;!!ACWV5N9M2RV99hQ!MJSZcs-
    > EHpL5q6RHht0icOlMXsU06NCkJZ58cFd4peTMfSnBZ5kfSIs-d9994LYkfjA3k8-
    > bcjexc2Koiv9odt5g$>.
    >




  • 6.  RE: Motion to Approve the End of Security Support Definition in PR #73

    Posted 11 days ago
    Feng the EoSS acronym is used also to cover End of the Standard Support lifecycle phase, which is pretty commonly used in the industry. It will be better to avoid confusion.

    Best,
    Rogue

    Przemyslaw Roguski

    Principal Product Security Engineer

    Red Hat

    email: proguski@redhat.com
    nickname: Rogue







  • 7.  RE: Motion to Approve the End of Security Support Definition in PR #73

    Posted 11 days ago
    Dear TC members, I second this motion for the "End of Security Support (EoSSec)" definition, as addressed in pull request github.com/oasis-tcs/openeox/pull/73 

    Best,
    Rogue

    Przemyslaw Roguski

    Principal Product Security Engineer

    Red Hat

    email: proguski@redhat.com
    nickname: Rogue







  • 8.  RE: Motion to Approve the End of Security Support Definition in PR #73

    Posted 10 days ago

    I believe EoSSec is more confusing than EoSecS.  I therefore object.


    Internal Use - Confidential






  • 9.  RE: Motion to Approve the End of Security Support Definition in PR #73

    Posted 10 days ago

    I think we are all adults, so EoSecS shouldn't be an issue (we have been using that for years without a single mention of what it sounds like).

     


    Internal Use - Confidential






  • 10.  RE: Motion to Approve the End of Security Support Definition in PR #73

    Posted 10 days ago

    I believe that the ongoing debates over acronym selection, while well-intentioned, are ultimately impeding productivity and innovation rather than contributing meaningful return on investment to the broader discussion. While it's true that some acronyms may overlap with existing terms (such as EoS, which can refer both to End-of-Sales and Arista's Extensible Operating System (EOS)) these overlaps are manageable. As long as we provide clear definitions, contextual references, and proper documentation within the standard, such overlaps should not present a substantive issue. 

    If we continue revisiting and revising acronyms repeatedly in search of perfect uniqueness, we risk falling into analysis paralysis. This constant churn not only delays progress but also detracts from the more strategic objectives we are trying to achieve. It's important that we prioritize forward momentum and focus on delivering value, rather than getting bogged down by terminology debates that offer diminishing returns.



    ------------------------------
    Best regards,

    Omar Santos
    ------------------------------



  • 11.  RE: Motion to Approve the End of Security Support Definition in PR #73

    Posted 10 days ago
    I agree wholeheartedly.

    Denny

    > On Apr 11, 2025, at 20:16, Omar Santos via OASIS <mail@mail.groups.oasis-open.org> wrote:
    >
    > It's important that we prioritize forward momentum and focus on delivering value, rather than getting bogged down by terminology debates that offer diminishing returns.




  • 12.  RE: Motion to Approve the End of Security Support Definition in PR #73

    Posted 7 days ago

    If we cannot agree on acronyms, how about we just remove all of them?


    Internal Use - Confidential






  • 13.  RE: Motion to Approve the End of Security Support Definition in PR #73

    Posted 7 days ago
    People will use acronyms regardless. 

    So better to define them in the standard, even if not all are perfect, but at least we will avoid confusion that people start using random acronyms for the same thing.

    Best,
    Rogue

    Przemyslaw Roguski

    Principal Product Security Engineer

    Red Hat

    email: proguski@redhat.com
    nickname: Rogue







  • 14.  RE: Motion to Approve the End of Security Support Definition in PR #73

    Posted 7 days ago

    Doesn't a standard require compliance?  Specifying acronyms that are not compatible will force organizations to change those that they use when they are non-conformant.  Thus the recommendation to remove outright.

     

     


    Internal Use - Confidential






  • 15.  RE: Motion to Approve the End of Security Support Definition in PR #73

    Posted 7 days ago
    Using acronyms like it's specified in the standard makes you compliant with that standard.
    Using many standards in the organization, which is pretty normal, is not a problem here as long as you follow best practices and before you use an acronym you always explain the full term and the associated acronym. If you don't follow best practices then any acronym can be misleading, even saying "IMHO" (which is "in my humble opinion" in this email) can be misunderstood :)

    Best,
    Rogue

    Przemyslaw Roguski

    Principal Product Security Engineer

    Red Hat

    email: proguski@redhat.com
    nickname: Rogue