Re: [cti-cybox] Update on the CybOX 3.0 effort

[Jerome Athias <athiasjerome@gmail.com>]

Hi,

quickly...
I can't remember where the Datatypes or Data Types are, but in case it
could help
https://datatracker.ietf.org/doc/rfc7012/?include_text=1



On Tue, Jul 19, 2016 at 9:45 PM, Paul Patrick <Paul.Patrick@fireeye.com> wrote:
> I’ve actually done some of the mappings already that I could contribute, but had questions on a few others.
>
>
>
> Paul
>
>
>
> On 7/19/16, 8:58 AM, "Trey Darley" <trey@kingfisherops.com> wrote:
>
>     On 18.07.2016 17:43:51, Paul Patrick wrote:
>     >
>     > One suggestion that I might make is that we add a section similar to
>     > what is in the TAXII spec that describes a basic mapping between the
>     > capabilities found in the CybOX 2.1 spec. This would help people use
>     > the patterning approach more consistently and provide help to those
>     > familiar with STIX 1.2 and CybOX 2.1 in making the transition.
>     >
>
>     Hey, Paul -
>
>     Great catch! Ivan and I have created an open issues table at the top
>     of the CybOX Playground doc where we're capturing valuable feedback
>     which we may not have time to address by 29 July. I've just dropped
>     your comment in there.
>
>     Again, thanks for the feedback, Paul! We definitely need to do this
>     and will get to it ASAP.
>
>     --
>     Cheers,
>     Trey
>     ++--------------------------------------------------------------------------++
>     Kingfisher Operations, sprl
>     gpg fingerprint: 85F3 5F54 4A2A B4CD 33C4  5B9B B30D DD6E 62C8 6C1D
>     ++--------------------------------------------------------------------------++
>     --
>     "There are only two hard things in Computer Science: cache
>     invalidation and naming things." --Phil Karlton
>
>
> This email and any attachments thereto may contain private, confidential, and/or privileged material for the sole use of the intended recipient. Any review, copying, or distribution of this email (or any attachments thereto) by others is strictly prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete the original and any copies of this email and any attachments thereto.