IETF Logo Mail Archive

Re: [Iot-onboarding] OPC and BRSKI

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 06 August 2019 15:55 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: iot-onboarding@ietfa.amsl.com
Delivered-To: iot-onboarding@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 128D21202ED for <iot-onboarding@ietfa.amsl.com>; Tue, 6 Aug 2019 08:55:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id psTWIdjHO3go for <iot-onboarding@ietfa.amsl.com>; Tue, 6 Aug 2019 08:55:46 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96EF51202AF for <iot-onboarding@ietf.org>; Tue, 6 Aug 2019 08:55:32 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 3CA103818C; Tue, 6 Aug 2019 11:54:56 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 4E44970D; Tue, 6 Aug 2019 11:55:31 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Randy Armstrong (OPC)" <randy.armstrong@opcfoundation.org>
cc: "iot-onboarding@ietf.org" <iot-onboarding@ietf.org>
In-Reply-To: <BYAPR08MB4903F02A37ED9AE092A59B8EFAD50@BYAPR08MB4903.namprd08.prod.outlook.com>
References: <BYAPR08MB4903F02A37ED9AE092A59B8EFAD50@BYAPR08MB4903.namprd08.prod.outlook.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Tue, 06 Aug 2019 11:55:31 -0400
Message-ID: <17467.1565106931@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-onboarding/eKmpCnVeUTkjjlcr4pVN2xhoe1o>
Subject: Re: [Iot-onboarding] OPC and BRSKI
X-BeenThere: iot-onboarding@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of IoT onboarding mechanisms <iot-onboarding.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iot-onboarding>, <mailto:iot-onboarding-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iot-onboarding/>
List-Post: <mailto:iot-onboarding@ietf.org>
List-Help: <mailto:iot-onboarding-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iot-onboarding>, <mailto:iot-onboarding-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2019 15:55:48 -0000

Randy Armstrong (OPC) <randy.armstrong@opcfoundation.org> wrote:
    > I work with the OPC Foundation and we are currently trying to solve a
    > problem similar to what BRSKI is trying to solve for industrial
    > automation devices. However, there are a number of unique requirements
    > in our space which appear to create impedance mismatches between what
    > BRKSI assumes and what we need. I would like to start a discussion on
    > those differences and see if they can be resolved in a way to allow OPC
    > Specifications to incorporate BRSKI.

Understood.

    > Is this the right forum for such discussions?

Yes, you are most welcome to explain things here.
The base document is pretty much done; but it is also explicitely defined for
ANIMA ANI applicability, and it may be that you just need an applicability
statement.  If you need more than that, then bringing it up before the end of
August would be timely.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email