Skimming quickly, I see now the direction to go to a cloud registrar to be
redirected to a local registrar. I feel compelled to point out that this is
exactly what SZTP (RFC 8572) does, or at least, supports. Actually, as a more
general statement, it was originally said that the two WG's
FYI, Its up on github now:
https://github.com/upros/brski-cloud
From: Anima On Behalf Of Owen Friel (ofriel)
Sent: 06 August 2019 14:05
To: Rifaat Shekh-Yusef ; anima@ietf.org;
iot-onboard...@ietf.org
Subject: Re: [Anima] [Iot-onboarding] Device Certificate Deployment Automation
with ACME
Hi guys,
After the meeting and from corridor conversations with Toerless, I had actually
already started on such a draft.
What I have started so far is attached. Its not on a public repo yet, but will
put it there. You are already named on it Rifaat, happy to add you too Michael
and you can
I read draft-ietf-anima-grasp-api from the expired drafts list.
I think that the event-loop architecture is different than a
polling architecture. I agree that given an event-loop architecture,
that one can build a polled architecture, but the converse is not true.
The event-loop mechanism
Kent Watsen wrote:
> Skimming quickly, I see now the direction to go to a cloud registrar to
> be redirected to a local registrar. I feel compelled to point out that
> this is exactly what SZTP (RFC 8572) does, or at least, supports.
> Actually, as a more general statement, it
On Tue, Aug 06, 2019 at 03:01:18PM +, Kent Watsen wrote:
> Skimming quickly, I see now the direction to go to a cloud registrar to be
> redirected to a local registrar. I feel compelled to point out that this is
> exactly what SZTP (RFC 8572) does, or at least, supports. Actually, as a
>
On Tue, Aug 06, 2019 at 09:32:45PM +, Randy Armstrong (OPC) wrote:
> OPC is layered to separate the application from the choice of network
> protocol. TLS/WebSockets is an option but the primary protocol that will be
> used by low end devices is UA TCP which provides complete message based
Push should be "Certificate Manager initiated"
From: Iot-onboarding On Behalf Of Randy
Armstrong (OPC)
Sent: August 6, 2019 4:17 PM
To: Toerless Eckert
Cc: iot-onboard...@ietf.org; anima@ietf.org; Eliot Lear
Subject: Re: [Iot-onboarding] OPC and BRSKI
Hi
1) Sure, need to understand how
Hi Toerless,
> I ranted about the need to better describe the common architecture
> already in prior emails to the anima list.
Good.
> Complexity is in the eye of the beholder.
True, but it seems that getting a domain certificate and getting an initial
configuration are at least two
Thanks very much Michael. Some partial responses below.
On 07-Aug-19 05:24, Michael Richardson wrote:
>
> I read draft-ietf-anima-grasp-api from the expired drafts list.
Right, the -03 draft expired while we were in Montreal. Our plan
is to make the next update after the two promised reviews
10 matches
Mail list logo
