OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

openc2 message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: HTTPS Spec Section 1

I would trim trim trim.


Even if it were to beat the new architecture spec out, it could reference the old.



That then moves to the more significant question: what remains to be done to advance the next version of the Architecture spec?


From: openc2@lists.oasis-open.org <openc2@lists.oasis-open.org> On Behalf Of Lemire, Dave (HII-TSD)
Sent: Tuesday, August 31, 2021 10:18 AM
To: TC OpenC2 <openc2@lists.oasis-open.org>
Subject: [openc2] HTTPS Spec Section 1


Work Product Editors & TC members,


What’s our current thinking WRT the content of section 1 of Actuator Profiles and Transfer Specs? The original three specs had a mostly common section 1 for accessibility purposes. In contrast the new MQTT transfer spec’s section 1 is extremely concise. The current PF AP draft is more like the originals, but I’m guessing mostly because it descends from the SLPF AP. In prepping the HTTPS spec toward a v1.1, should I trim section 1 down so it looks more like the MQTT spec?


I guess a related question is where do we stand on making the Architecture Spec a reality?




David Lemire

IA Systems Engineer

Technical Solutions


302 Sentinel Drive | Annapolis Junction, MD 20701

Work (301) 575-5190 | Mobile (240) 938-9350


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]