OASIS Cyber Threat Intelligence (CTI) TC

 View Only

  • 1.  Minor spec question: minimum characters for custom property/object names

    Posted 06-01-2018 13:10




    Hi all,
     
    We discussed a minor topic on this past working call and I wanted to summarize the discussion and see if anyone else had any thoughts. Notes from the working call are here:

    https://www.oasis-open.org/committees/download.php/63164/OASIS-CTI-TC_WorkingCall_May29_2018.pdf
     
    The specific text is in Part 1, Sections 8.1.1 [1] and 8.2.1 [2]. Currently, we have a normative MUST requirement that all custom property names and custom object names be at least three characters long. This
    was set in place when, in the specification, we also had a normative MUST for the dictionary type to require properties be longer than two characters. In developing support for internationalization, though, Emmanuelle noticed a bug [3] where this conflicted
    with the property names required by i18n, ISO language codes, which can be only two characters long. So, we changed the requirement in the text for dictionary to allow for two-character key names in dictionaries.
     
    Custom properties and objects are a separate topic, but since the text was originally the same we wanted to bring it up for discussion. We talked about it on the working call this past week and the discussion
    seemed to land on it not being a huge deal and that we should leave the text as-is. This would mean that, though you can use keys in a dictionary that are only 1 or 2 characters long (including ISO language codes), custom property and object names would still
    have to be three characters long.
     
    Does anybody object to keeping this as-is, per the working call discussion? The other options would be to either change the requirement to a minimum of two characters (effectively allowing everything except
    one character names) or to remove the requirements altogether.
     
    Thanks for your feedback,
    John
     
    [1]:
    https://docs.google.com/document/d/1ShNq4c3e1CkfANmD9O--mdZ5H0O_GLnjN28a_yrEaco/edit#heading=h.3a2x3jdr23tq
    [2]:
    https://docs.google.com/document/d/1ShNq4c3e1CkfANmD9O--mdZ5H0O_GLnjN28a_yrEaco/edit#heading=h.u7ks5xud8vj0

    [3]:
    https://github.com/oasis-tcs/cti-stix2/issues/35






  • 2.  RE: Minor spec question: minimum characters for custom property/object names

    Posted 06-01-2018 13:19
      |   view attached




    I’m fine keeping it as-is.

     

    Sarah Kelley
    Lead Cybersecurity Engineer, T8B2
    Defensive Operations
    The MITRE Corporation
    703-983-6242
    skelley@mitre.org


     



    From: cti@lists.oasis-open.org [mailto:cti@lists.oasis-open.org]
    On Behalf Of Wunder, John A.
    Sent: Friday, June 1, 2018 9:09 AM
    To: cti@lists.oasis-open.org
    Subject: [cti] Minor spec question: minimum characters for custom property/object names


     
    Hi all,
     
    We discussed a minor topic on this past working call and I wanted to summarize the discussion and see if anyone else had any thoughts. Notes from the working call are here:

    https://www.oasis-open.org/committees/download.php/63164/OASIS-CTI-TC_WorkingCall_May29_2018.pdf
     
    The specific text is in Part 1, Sections 8.1.1 [1] and 8.2.1 [2]. Currently, we have a normative MUST requirement that all custom property names and custom object names be at least three characters long. This
    was set in place when, in the specification, we also had a normative MUST for the dictionary type to require properties be longer than two characters. In developing support for internationalization, though, Emmanuelle noticed a bug [3] where this conflicted
    with the property names required by i18n, ISO language codes, which can be only two characters long. So, we changed the requirement in the text for dictionary to allow for two-character key names in dictionaries.
     
    Custom properties and objects are a separate topic, but since the text was originally the same we wanted to bring it up for discussion. We talked about it on the working call this past week and the discussion
    seemed to land on it not being a huge deal and that we should leave the text as-is. This would mean that, though you can use keys in a dictionary that are only 1 or 2 characters long (including ISO language codes), custom property and object names would still
    have to be three characters long.
     
    Does anybody object to keeping this as-is, per the working call discussion? The other options would be to either change the requirement to a minimum of two characters (effectively allowing everything except
    one character names) or to remove the requirements altogether.
     
    Thanks for your feedback,
    John
     
    [1]:
    https://docs.google.com/document/d/1ShNq4c3e1CkfANmD9O--mdZ5H0O_GLnjN28a_yrEaco/edit#heading=h.3a2x3jdr23tq
    [2]:
    https://docs.google.com/document/d/1ShNq4c3e1CkfANmD9O--mdZ5H0O_GLnjN28a_yrEaco/edit#heading=h.u7ks5xud8vj0

    [3]:
    https://github.com/oasis-tcs/cti-stix2/issues/35






  • 3.  Re: [cti] RE: Minor spec question: minimum characters for custom property/object names

    Posted 06-01-2018 15:37
    On 01.06.2018 13:18:36, Kelley, Sarah E. wrote: > I’m fine keeping it as-is. > Ditto - we have much bigger fish to fry. -- Cheers, Trey ++--------------------------------------------------------------------------++ Director of Standards Development, New Context gpg fingerprint: 3918 9D7E 50F5 088F 823F 018A 831A 270A 6C4F C338 ++--------------------------------------------------------------------------++ -- "One size never fits all." --RFC 1925 Attachment: signature.asc Description: PGP signature


  • 4.  Re: [EXT] Re: [cti] RE: Minor spec question: minimum characters for custom property/object names

    Posted 06-01-2018 20:42
    So long as the fish are Sole and cooked  meunière, it is all good. From: cti@lists.oasis-open.org <cti@lists.oasis-open.org> on behalf of Trey Darley <trey@newcontext.com> Sent: Friday, June 1, 2018 9:36:52 AM To: Kelley, Sarah E. Cc: Wunder, John A.; cti@lists.oasis-open.org Subject: [EXT] Re: [cti] RE: Minor spec question: minimum characters for custom property/object names   On 01.06.2018 13:18:36, Kelley, Sarah E. wrote: > I’m fine keeping it as-is. > Ditto - we have much bigger fish to fry. -- Cheers, Trey ++--------------------------------------------------------------------------++ Director of Standards Development, New Context gpg fingerprint: 3918 9D7E 50F5 088F 823F  018A 831A 270A 6C4F C338 ++--------------------------------------------------------------------------++ -- "One size never fits all." --RFC 1925


  • 5.  Re: [EXT] [cti] Minor spec question: minimum characters for custom property/object names

    Posted 06-01-2018 20:38
    In the absence of a compelling reason to change, I say just keep it.  Having good boundaries is a good thing, imo. Bret From: cti@lists.oasis-open.org <cti@lists.oasis-open.org> on behalf of Wunder, John A. <jwunder@mitre.org> Sent: Friday, June 1, 2018 7:09:26 AM To: cti@lists.oasis-open.org Subject: [EXT] [cti] Minor spec question: minimum characters for custom property/object names   Hi all,   We discussed a minor topic on this past working call and I wanted to summarize the discussion and see if anyone else had any thoughts. Notes from the working call are here: https://www.oasis-open.org/committees/download.php/63164/OASIS-CTI-TC_WorkingCall_May29_2018.pdf   The specific text is in Part 1, Sections 8.1.1 [1] and 8.2.1 [2]. Currently, we have a normative MUST requirement that all custom property names and custom object names be at least three characters long. This was set in place when, in the specification, we also had a normative MUST for the dictionary type to require properties be longer than two characters. In developing support for internationalization, though, Emmanuelle noticed a bug [3] where this conflicted with the property names required by i18n, ISO language codes, which can be only two characters long. So, we changed the requirement in the text for dictionary to allow for two-character key names in dictionaries.   Custom properties and objects are a separate topic, but since the text was originally the same we wanted to bring it up for discussion. We talked about it on the working call this past week and the discussion seemed to land on it not being a huge deal and that we should leave the text as-is. This would mean that, though you can use keys in a dictionary that are only 1 or 2 characters long (including ISO language codes), custom property and object names would still have to be three characters long.   Does anybody object to keeping this as-is, per the working call discussion? The other options would be to either change the requirement to a minimum of two characters (effectively allowing everything except one character names) or to remove the requirements altogether.   Thanks for your feedback, John   [1]: https://docs.google.com/document/d/1ShNq4c3e1CkfANmD9O--mdZ5H0O_GLnjN28a_yrEaco/edit#heading=h.3a2x3jdr23tq [2]: https://docs.google.com/document/d/1ShNq4c3e1CkfANmD9O--mdZ5H0O_GLnjN28a_yrEaco/edit#heading=h.u7ks5xud8vj0 [3]: https://github.com/oasis-tcs/cti-stix2/issues/35


  • 6.  Re: Minor spec question: minimum characters for custom property/object names

    Posted 06-08-2018 16:45




    Hi all,
     
    Since only one person spoke up on this issue and he seemed OK to move on if it was the only comment, I think our action can be to keep this as-is. I’ll document that we had this discussion but there are no
    specification changes as a result.
     
    With this and the labels issue resolved I believe we have everything we need to produce STIX 2.1 CSD01. Please stay tuned over the next couple weeks for review of a working draft prior to a ballot on the CSD.
     
    Thanks,
    John
     

    From: John Wunder <jwunder@mitre.org>
    Date: Friday, June 1, 2018 at 9:09 AM
    To: "cti@lists.oasis-open.org" <cti@lists.oasis-open.org>
    Subject: Minor spec question: minimum characters for custom property/object names


     

    Hi all,
     
    We discussed a minor topic on this past working call and I wanted to summarize the discussion and see if anyone else had any thoughts. Notes from the working call are here:

    https://www.oasis-open.org/committees/download.php/63164/OASIS-CTI-TC_WorkingCall_May29_2018.pdf
     
    The specific text is in Part 1, Sections 8.1.1 [1] and 8.2.1 [2]. Currently, we have a normative MUST requirement that all custom property names and custom object names be at least three characters long. This
    was set in place when, in the specification, we also had a normative MUST for the dictionary type to require properties be longer than two characters. In developing support for internationalization, though, Emmanuelle noticed a bug [3] where this conflicted
    with the property names required by i18n, ISO language codes, which can be only two characters long. So, we changed the requirement in the text for dictionary to allow for two-character key names in dictionaries.
     
    Custom properties and objects are a separate topic, but since the text was originally the same we wanted to bring it up for discussion. We talked about it on the working call this past week and the discussion
    seemed to land on it not being a huge deal and that we should leave the text as-is. This would mean that, though you can use keys in a dictionary that are only 1 or 2 characters long (including ISO language codes), custom property and object names would still
    have to be three characters long.
     
    Does anybody object to keeping this as-is, per the working call discussion? The other options would be to either change the requirement to a minimum of two characters (effectively allowing everything except
    one character names) or to remove the requirements altogether.
     
    Thanks for your feedback,
    John
     
    [1]:
    https://docs.google.com/document/d/1ShNq4c3e1CkfANmD9O--mdZ5H0O_GLnjN28a_yrEaco/edit#heading=h.3a2x3jdr23tq
    [2]:
    https://docs.google.com/document/d/1ShNq4c3e1CkfANmD9O--mdZ5H0O_GLnjN28a_yrEaco/edit#heading=h.u7ks5xud8vj0

    [3]:
    https://github.com/oasis-tcs/cti-stix2/issues/35






Related Content