Re: [Cacao] [EXT] Re: [EXT] RE: Charter

[Bret Jordan <[e-mail]>]

Agreed.

Here are some current screen shots of the proposed changes to the charter text.




Thanks,
Bret
PGP Fingerprint: 63B4 FC53 680A 6B7D 1447  F2C0 74F8 ACAE 7415 0050
"Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg."

> On Jun 19, 2019, at 12:02 PM, Allan Thomson <[e-mail]> wrote:
> 
> Action Validation as a function and part of the process *is* considered part of the architectural functional requirements however given that we are explicitly stating that individual atomic actions that can be referenced by the playbooks are *out* of scope then it by design that the determination of validity of an individual action can also not be in scope.
>  
> Data Model: You seem to be suggesting that this work must use YANG for modelling. We are not excluding that option but we are also not mandating it either. I assume you are encouraging use of YANG. I think that’s a reasonable suggestion but I don’t see why it must be the case. There are many projects that have successfully been achieved without YANG being used for data modelling.
>  
> Allan Thomson
> CTO ([phone])
> LookingGlass Cyber Solutions <http://www.lookingglasscyber.com/>
>  
> From: Cacao <[e-mail] <mailto:[e-mail]>> on behalf of "[e-mail] <mailto:[e-mail]>" <[e-mail] <mailto:[e-mail]>>
> Date: Wednesday, June 19, 2019 at 1:40 AM
> To: Bret Jordan <[e-mail] <mailto:[e-mail]>>
> Cc: "[e-mail] <mailto:[e-mail]>" <[e-mail] <mailto:[e-mail]>>
> Subject: Re: [Cacao] [EXT] Re: [EXT] RE: Charter
>  
> Re-,
>  
> Great!
>  
> I interpret “addressed” as you made the proposed changes to address the issues.
>  
> Do you confirm that you updated the text to address the following items:
>  
> (1) Action validation:
>  
> [Med] An action may be flawed because the proposed action is not adequate for a threat or it is missing a mandatory clause to be actionable. Such objects need to be detected and discarded somehow/somewhere. Things may be complicated when actions are chained/augmented by an intermediate function. Some (consistency) validation will be needed. The question is whether this is part of the work or not.
> 
> (2) Which data model?
>  
> ===
> [Med] This is one is conflicting with the sentence citing reusing YANG. I would cite YANG here especially that converting YANG to JSON and vice versa is well documented (RFC7951). 
> [BRET] - Then maybe we need to delete YANG for now.  We need to focus on simple things that the eco-system can implement and use very quickly. Most Web2.0 developers are very familiar with JSON.  This is why we picked it for version 1.
> [Med] We need to separate data modelling vs. application encoding. It is perfectly fine to use YANG for the modelling, but use JSON encoding for the application.  
> ===
>  
> Cheers,
> Med
>  
> De : Cacao [mailto:[e-mail] <mailto:[e-mail]>] De la part de Bret Jordan
> Envoyé : mercredi 19 juin 2019 10:01
> À : BOUCADAIR Mohamed TGI/OLN
> Cc : [e-mail] <mailto:[e-mail]>
> Objet : Re: [Cacao] [EXT] Re: [EXT] RE: Charter
>  
> Mohamed,
>  
> All comments and suggestions have been addressed at this point.  Suggested changes to the charter are currently in the charter text in suggestion mode. 
>  
>  
> Thanks,
> Bret
> PGP Fingerprint: 63B4 FC53 680A 6B7D 1447  F2C0 74F8 ACAE 7415 0050
> "Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg."
> 
> 
> 
> On Jun 19, 2019, at 9:24 AM, <[e-mail] <mailto:[e-mail]>> <[e-mail] <mailto:[e-mail]>> wrote:
>  
> Bret,
>  
> What is really important from where I sit is to be able to track efficiently the issues. This can be done by email or using github. Tooling (and logistic matters in general) is the kind of decision to be taken by the group once (hopefully) formed. It is too early to make a decision at this stage. So, let’s not spend cycles on this right now.   
>  
> Back to the initial technical discussion, can you please share which comments you have taken into account and which ones are still pending. You can use separate threads for pending issues. Thank you.
>  
> Cheers,
> Med
>  
> De : Cacao [mailto:[e-mail] <mailto:[e-mail]>] De la part de Bret Jordan
> Envoyé : mercredi 19 juin 2019 08:46
> À : Michael Richardson
> Cc : [e-mail] <mailto:[e-mail]>; Bret Jordan
> Objet : Re: [Cacao] [EXT] Re: [EXT] RE: Charter
>  
> Thanks Michael.  Yes, I misunderstood the comments.  We agree that we need this to be inclusive.  There are a large number of security analysts that know and understand how this needs to work.  It is critical that we design it and build it in a way that they and the rest of the market can use. 
>  
> I am very familiar with editing documents in Google docs for large technical committees.  While there are some things I like about github, I find the automatic always on change tracking in google docs to be sufficient.  
>  
> We can also take regular snapshots and push to github for longer term archival if people would like that.  I would not be against that.  
>  
> As you can see there are comments in the charter text right now, and comments on the comments.  Things that can be very difficult or non-intuitive to do in github.  
>  
> Google docs is not perfect.  But if anyone from google is here and needs some ideas for how you could make it the ideal solution for this kind of work, I have some ideas for you. 
>  
> Bret 
> 
> Sent from my Commodore 128D 
> 
> 
> 
> 
> PGP Fingerprint: 63B4 FC53 680A 6B7D 1447  F2C0 74F8 ACAE 7415 0050
> 
> On Jun 19, 2019, at 12:19 AM, Michael Richardson <[e-mail] <mailto:[e-mail]>> wrote:
> 
>> 
>> (why am I top-quoting?)
>> Bret, Carsten is not objecting to Google Docs.
>> 
>> Carsten is asking you to be explicit in saying that including people who
>> can't/won't do github is important.
>> Google Docs suffers from a lack of attribution for the text after the
>> "suggestion" is accepted.
>> Github suffers from way too much attribution.
>> 
>> I don't object to using Google Docs, but please make sure you know how to use
>> it well.  If you are editing an Internet Draft in Markdown format, then some
>> stuff will look weird, and people will make suggestion that can not be
>> implemented.
>> 
>> I don't think having it on etherpad is helpful, btw.
>> 
>> Bret Jordan <[e-mail] <mailto:[e-mail]>> wrote:
>> 
>> 
>> 
>> That is an option. Just so you know, Google Docs does not require
>>> anything other than a web browser. If you go this url, just like an
>>> ether pad, you will see the document and suggestions and comments.
>> 
>> 
>> 
>> 
>> https://clicktime.symantec.com/3JAf65ZJwTfeqxVfAPTGXMp7Vc?u=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1fTN0uilpBVx6CwaGxj8SBKG4PqG7DceInU9RgLz9pRo%2Fedit%23heading%3Dh.wh8etuclav2g <https://clicktime.symantec.com/3JAf65ZJwTfeqxVfAPTGXMp7Vc?u=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1fTN0uilpBVx6CwaGxj8SBKG4PqG7DceInU9RgLz9pRo%2Fedit%23heading%3Dh.wh8etuclav2g>
>> 
>> 
>> 
>> 
>> Thanks, Bret PGP Fingerprint: 63B4 FC53 680A 6B7D 1447 F2C0 74F8 ACAE
>>> 7415 0050 "Without cryptography vihv vivc ce xhrnrw, however, the only
>>> thing that can not be unscrambled is an egg."
>> 
>> 
>> 
>> 
>>    On Jun 18, 2019, at 4:26 PM, Amelia Andersdotter
>>> <[e-mail] <mailto:[e-mail]>> wrote:
>> 
>> 
>> 
>> 
>> 
>> 
>>    On 2019-06-18 16:05, Bret Jordan wrote:
>> 
>> 
>> 
>> 
>> 
>>        Carsten,
>> 
>> 
>> 
>> 
>> 
>>        I appreciate your comments. However, from our experience, with
>>> a large group of people that are in both camps, editing specs in Google
>>> docs proves to be the easiest solution for all. So it is not about
>>> preferring one group over another. It is about what proves to be the
>>> easiest and fastest to enable as many people as possible to get work
>>> done quickly and efficiently.
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>    How about making it temporarily available on some form of etherpad?
>>> They are normally accessible to everyone and rely only on browser
>>> functions.
>> 
>> 
>> 
>> 
>> 
>>    best regards,
>> 
>> 
>> 
>> 
>>    amelia
>> 
>> 
>> 
>> 
>> 
>>        Bret
>> 
>> 
>> 
>> 
>> 
>>        ------------------------------------------------------------------------
>> 
>> 
>> 
>> 
>>        *From:* Carsten Bormann <[e-mail] <mailto:[e-mail]>> *Sent:* Tuesday, June
>>> 18, 2019 7:41:20 AM *To:* Bret Jordan *Cc:*
>>> [e-mail] <mailto:[e-mail]>; [e-mail] <mailto:[e-mail]> *Subject:* [EXT] Re:
>>> [Cacao] [EXT] RE: Charter
>> 
>> 
>> 
>> 
>>        On Jun 18, 2019, at 14:24, Bret Jordan
>>> <Bret_Jordan=[e-mail] <mailto:Bret_Jordan=[e-mail]>> wrote:
>> 
>> 
>> 
>> 
>> 
>>            Using Github will prevent people from helping, or will
>>> limit people
>> 
>> 
>> 
>> 
>> 
>>        to only those that understand how to use Github and have access
>>> to Github. Resolving comments and suggestions via Github is
>>> significantly harder than Google Docs.
>> 
>> 
>> 
>> 
>>        My comment here is kind of off-topic, but… The statement you
>>> are making here is that one group of contributors (those that can stand
>>> collaborating on a document with the limited means Google Docs) is more
>>> important than another group of contributors (those that are used to
>>> software development workflows).  While that may very well be, I think
>>> it is important to make decisions like this explicitly.  (I personally
>>> believe that this effort could benefit from strong participation by
>>> people who write code.)
>> 
>> 
>> 
>> 
>>        Grüße, Carsten
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>    --
>>>    Amelia Andersdotter Technical Consultant, Digital Programme Chair,
>>> RCM TIG, IEEE 802.11
>> 
>> 
>> 
>> 
>>    ARTICLE19 https://clicktime.symantec.com/33D3oaMYVStXDNQHd3evAL27Vc?u=www.article19.org <https://clicktime.symantec.com/33D3oaMYVStXDNQHd3evAL27Vc?u=www.article19.org>
>> 
>> 
>> 
>> 
>>    PGP: 3D5D B6CA B852 B988 055A 6A6F FEF1 C294 B4E8 0B55
>> 
>> 
>> 
>> 
>>    --
>>>    Cacao mailing list [e-mail] <mailto:[e-mail]>https://clicktime.symantec.com/36NaSMAoRn4patyVkcWPUUX7Vc?u=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fcacao <https://clicktime.symantec.com/36NaSMAoRn4patyVkcWPUUX7Vc?u=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fcacao>
>> 
>> 
>> 
>> 
>> 
>> 
>> ----------------------------------------------------
>>> Alternatives:
>> 
>> 
>> 
>> 
>> ----------------------------------------------------
>>> --
>>> Cacao mailing list [e-mail] <mailto:[e-mail]>https://clicktime.symantec.com/36NaSMAoRn4patyVkcWPUUX7Vc?u=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fcacao <https://clicktime.symantec.com/36NaSMAoRn4patyVkcWPUUX7Vc?u=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fcacao>
>> --
>> Michael Richardson <[e-mail] <mailto:[e-mail]>>, Sandelman Software Works
>> -= IPv6 IoT consulting =-
>> 
>> 
>> 
>> 
>> -- 
>> Cacao mailing list
>> [e-mail] <mailto:[e-mail]>
>> https://clicktime.symantec.com/36NaSMAoRn4patyVkcWPUUX7Vc?u=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fcacao <https://clicktime.symantec.com/36NaSMAoRn4patyVkcWPUUX7Vc?u=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fcacao>