Re: [Iotops] Side meeting on Operations and Control Networks (OCN) (25th Jul, 12:30 pm)

Kiran M <kiran.ietf@gmail.com> Wed, 20 July 2022 05:17 UTC

Return-Path: <kiran.ietf@gmail.com>
X-Original-To: iotops@ietfa.amsl.com
Delivered-To: iotops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E760EC13C51F for <iotops@ietfa.amsl.com>; Tue, 19 Jul 2022 22:17:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.106
X-Spam-Level:
X-Spam-Status: No, score=-1.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id in55Ze_Dl5kV for <iotops@ietfa.amsl.com>; Tue, 19 Jul 2022 22:17:44 -0700 (PDT)
Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75F93C13485A for <iotops@ietf.org>; Tue, 19 Jul 2022 22:17:26 -0700 (PDT)
Received: by mail-pj1-x1031.google.com with SMTP id gn24so2365215pjb.3 for <iotops@ietf.org>; Tue, 19 Jul 2022 22:17:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to; bh=E7oWVcwhHEWc1vTbzIa+fNMhgH1BR/34LK8n7w0GgSQ=; b=DeoB1Fk5K+1IDYtpE/hbMKnFgq4+og+cChm0fAtWQ1eL46fkKLuQC+a6vN9aOKS0tC aGPv6z6jxOAOeNCBTMe7CFQPd0555ktqOb9JlFimLmPi3VAWCthAwuz5IsUaGdxB2RL2 K/sSlATXyR0NwBBP0bGUbp/m2c1dwPSdUp1Hh6Jf+D1Rg07v8F3OqcGBH3MzY2VjiSAQ CO7R/ysGh94T5PDrfMyjrf5rsdSnaF79JY+gZHeHs9xk53UGJNuhec6tHal/0U36nLIS NHlVbkVRUnrh9QtgSPkg58dT2VYIupD3QVh608F5UlwA9kYbS7Bfc73dSSFMn0ish5LE 0oWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to; bh=E7oWVcwhHEWc1vTbzIa+fNMhgH1BR/34LK8n7w0GgSQ=; b=K0VS+drtCEVMSSKYUgVl8OoLwSMzXkeHbZattsgW32G4zv5kpCw/YNMJk2sUAeaBYQ MoojwXPJzWvpMzTS70zSPDEMJq7a8RVh/i7pAyC0Ay/fZIUPrj2L8Ga0Fzk8BL9cacgj 30p/WRuqpR6AvipMxS6Yw7j6zSWuWb17O0cRAtMZ04f5ejAOXl4WE6s1xZyr9ll5US7O Q7vaspE+eUSmYTRIxPXRpUk3L7WUKEuRitNTv5KahyHp8wJ2NK541lvIwzoabLQbEfEO yPkpebdP1ZqDt3gCOSL8pJRwhYJHFoyj+QKHiYLgwtJNdJFb5djJ3myLbGX/d3n02bEp hu5g==
X-Gm-Message-State: AJIora8YKtHsoBcnav30SIBgr8XdeWMp1J9VuG4pukl4Xyjom9qnMYdZ sg5FYMpkPMS91wEwCl+6nTs=
X-Google-Smtp-Source: AGRyM1vjLCinLHiI2GalwXqigQySZRS0PyhrJvRuDUdxt+WleKP6eqtsJNLjxLKoHrxu5Rdmj19ueA==
X-Received: by 2002:a17:902:f683:b0:16c:3752:e332 with SMTP id l3-20020a170902f68300b0016c3752e332mr36789620plg.18.1658294245619; Tue, 19 Jul 2022 22:17:25 -0700 (PDT)
Received: from [192.168.1.69] (c-73-202-182-183.hsd1.ca.comcast.net. [73.202.182.183]) by smtp.gmail.com with ESMTPSA id b18-20020aa78ed2000000b00525302fe9c4sm12408332pfr.190.2022.07.19.22.17.24 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 19 Jul 2022 22:17:25 -0700 (PDT)
Content-Type: multipart/alternative; boundary="------------805I903ZyZduvDtbf4Puc6Iu"
Message-ID: <1e8ccb70-dcf8-7228-4892-4185c9984d42@gmail.com>
Date: Tue, 19 Jul 2022 22:17:23 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
Content-Language: en-US
To: brian.e.carpenter@gmail.com, iotops@ietf.org
References: <60e20dd9-2148-4957-69a1-0fb001d7f691@gmail.com> <1fc9e736-9625-00a2-e019-b0e2ec407940@gmail.com>
From: Kiran M <kiran.ietf@gmail.com>
In-Reply-To: <1fc9e736-9625-00a2-e019-b0e2ec407940@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/iotops/ZyJz5F-tcCeQcvnmKgE3GnyjuUQ>
Subject: Re: [Iotops] Side meeting on Operations and Control Networks (OCN) (25th Jul, 12:30 pm)
X-BeenThere: iotops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IOT Operations <iotops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iotops>, <mailto:iotops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iotops/>
List-Post: <mailto:iotops@ietf.org>
List-Help: <mailto:iotops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iotops>, <mailto:iotops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2022 05:17:49 -0000

Hi Brian,

Thank you for taking time to read through the documents. I hope you can 
attend the meeting remotely.

My comments inline with [KM].

Cheers,
Kiran


------------------------------------------------------------------------
*From:* Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
*Sent:* Tuesday, July 19, 2022, 2:45 PM
*To:* Kiran M; iotops@ietf.org
*Subject:* [Iotops] Side meeting on Operations and Control Networks 
(OCN) (25th Jul, 12:30 pm)

> Hi,
>
> I will not be in the meeting, and I haven't worked in process control
> for many years, but from glancing through the drafts I am not sure that
> I understand what the IETF has to offer on this topic. Yes, certainly we
> offer many technology components such as DETNET and (I hope) ANIMA, but
> is it the IETF's role to offer a reference model or an architecture?

[KM] Maybe (maybe not). The idea behind this is a generalized "network 
model" which from our observation has  a common structure to cover a 
majority of automaton/OT/control systems use cases. The focus will be on 
specific description and characteristics of the interfaces in the model 
where IETF technologies apply, and how they will work.

> There's 50 years of history behind current computerized control systems.
> There's also an emerging industry standard, described at
> https://www.opengroup.org/forum/open-process-automation-forum
[KM] I agree, this does require a close coordination with other SDOs. 
But if it is about IETF technologies, the work should start here. I was 
not aware of this one. Will certainly look up. I am familiar with work 
done in other SDOs - they  generate requirements but not  communication 
standards.
> and
> https://doi.org/10.1016/j.conengprac.2021.105034 **
>
> I can't really tell from the problem statement draft exactly what
> the IETF has to offer that will be different from that work.

[KM] in addition to above, we could figure out if current IETF 
technologies are sufficient, are there pain-points, or we need to 
enhance. With 5G/B5G use cases, there are so many machine to machine 
type communication scenarios, that have specific needs to implement 
remote feedback control loops and precise command delivery mechanisms. 
OCN could describe how will that happen from controller to device when 
there's a network between them. Side meeting is there to specifically 
argue this question.

[KM] BTW, if IETF chooses to take up this work - an approach to 
motivations below will be a great outcome.

>
> I see that the IETF does not currently have a liaison to the Open
> Group, but certainly if we did anything, we would need some liaison.

> [KM] agreed.

Thanks, Kiran

> Regards
>    Brian Carpenter
>
> ** That's behind a paywall, unfortunately. But its motivations are
> very apposite:
>
> "• lack of peer-to-peer interoperability between systems from different
> suppliers
> • inability to reuse user-written configurations or applications between
> systems from different suppliers, and sometimes between
> different generations of one supplier’s products
> • closed, proprietary couplings among components that result in
> whole-system, instead of modular, upgrades or replacements to
> manage obsolescence
> • barriers to business value generation via innovations from the
> insertion of third-party software or hardware technology
> • absence of designed-in cybersecurity mechanisms"
>
> On 20-Jul-22 03:20, Kiran M wrote:
>> Hello IoTOPS,
>>
>> I hope the group finds this interesting.
>>
>> I have talked about industrial operations networks quite a bit last few
>> times. Many thanks for all the feedback I have received so far. It is
>> clear that a certain level of scoping and an informal discussion will be
>> useful. In that regard, we are organizing a side-meeting for discussion
>> on OCNs. Please join us in-person or remotely. Also refer to the 00
>> version documents below that cover use-cases, problem stmt, reference
>> model for discussion.
>>
>> ====Meeting Information====
>>
>> Date:  Monday 25 July
>> Time:  12:30 to 1:30 pm (+/-50 minutes)
>> Room:  Philadelphia South (Mezzanine Level)
>> Webex:
>> https://futurewei.my.webex.com/futurewei.my/j.php?MTID=m8482bdb06635d5ef021e6dcc11d1cd29 
>>
>>
>> Agenda etc. at: https://github.com/kiranmak/meetings-ocn-ietf-114
>>
>> Reference Documents:
>>
>>     [1] https://datatracker.ietf.org/doc/draft-km-intarea-ocn/
>>     [2] https://datatracker.ietf.org/doc/draft-tf-ocn-ps/
>>     [3] 
>> https://datatracker.ietf.org/doc/draft-dong-remote-driving-usecase/
>>     [4] https://datatracker.ietf.org/doc/draft-wmdf-ocn-use-cases/
>>
>>
>> Please reach out to me for further details.
>> See you there!
>> Kiran
>>