[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [openc2-imple] Re: [EXT] [openc2-imple] HTTPS REST API use case
While I like HTTP, I am not sure this is actually going to meet the requirements. I would further state that a short list from 1-2 people is not a list of requirements.
The transport we end up picking may have implications on the information model, so we need to make sure we do this carefully. It is not just a matter of picking something.
Bret
From: Dave Lemire <dave.lemire@g2-inc.com>
Sent: Monday, March 19, 2018 9:27:17 AM To: Bret Jordan Cc: duncan@sfractal.com; openc2-imple@lists.oasis-open.org Subject: Re: [openc2-imple] Re: [EXT] [openc2-imple] HTTPS REST API use case Simply put: It seems pretty obvious to me that an HTTPS transfer solution would be widely applicable.
I'd also agree with Duncan that I think use cases exist. I've been looking back of IC-SC meeting notes, and as Duncan has noted we agreed back in September that HTTPS would be one of the transfer solutions.
Dave
OpenC2 Technical Committee Executive Secretary OpenC2 Implementation Considerations SC Co-chair Contractor support to NSA Email: dave.lemire@g2-inc.com Office: 301-575-5190 / Mobile: 240-938-9350 On Sat, Mar 17, 2018 at 4:40 PM, Bret Jordan
<Bret_Jordan@symantec.com> wrote:
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]