RE: SLPF Public Review Comment: SLPF-8

["Considine, Toby" <Toby.Considine@unc.edu>]

The answer to this is somewhat subordinate to the JADN conversation.

As noted elsewhere, there is little useful description of JADN on the web, and the best resource on finding what JADN is and how it works is in the OpenC2 JADN GIT. If JADN were normatively defined elsewhere, then it would have all the normative references, and this specification would incorporate them by reference to the JADN spec. 

As it is, things are somewhat undefined.

The TC could OPT (with appropriate administrative work) to create a normative description of JADN based on current work. This would likely require some time delays to create a JADN TC, which then could receive a donation of all JADN stuff from this TC, and we could reference that specification in flight, with direction to OASIS that we wish that spec to be normative in its final form... (This is similar in some ways to how MQTT came to OASIS)

Or those that want to could firm up the somewhat inchoate JADN material in some other forum, say pushing it into an RFC.  That path is no longer as informal as it once was, and can itself take years...

Not every normatively referenced specification is a formal specification. One of the most frequently referenced works in recent times is the doctoral thesis "Architectural Styles and the Design of Network-based Software Architectures" (Fielding), which defined REST. The problem here is that there does not appear to be any equivalent free-standing document for JADN.

(Anyway, not one that I have successfully found with successive search strings).

If the TC decides it is useful, but it doesn't actually fit, we could opt to put it is a non-normative reference. That does not seem to fit for this, though.

tc



-----Original Message-----
From: openc2-actuator@lists.oasis-open.org <openc2-actuator@lists.oasis-open.org> On Behalf Of Brule, Joseph M
Sent: Wednesday, December 12, 2018 9:49 AM
To: 'openc2-actuator@lists.oasis-open.org' <openc2-actuator@lists.oasis-open.org>
Subject: [openc2-actuator] SLPF Public Review Comment: SLPF-8

All, 

A comment stating that some of the normative references were not actually referenced in the body of the doc .  (Knight)

I created a Github issue number 28.  (https://github.com/oasis-tcs/openc2-apsc-stateless-packet-filter/issues issue number 28) 

I am going to need some help on this one.  Some of the normative references involve JSON formatting or other related standards, and the SLPF has normative requirements that are related (must support json serialization) but we do not directly say RFC 8259 or whatever.  

How do I fix this?  


VR

Joe Brule 


Joe Brule
Engineering (Y2D122)
FNX-3, B4A335
410.854.4045
'Adnius ad retinedam puritem noster peciosus corporalis fluidorum...'
I welcome VSRE emails.  Learn more at http://vsre.info/ 



---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php