Re: [Iot-onboarding] [Mud] Side meeting at the IETF Montreal - call for agenda items

"M. Ranganathan" <mranga@gmail.com> Mon, 01 July 2019 11:52 UTC

Return-Path: <mranga@gmail.com>
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 BDD9B12022A; Mon, 1 Jul 2019 04:52:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 1i0iaeeSrCoN; Mon, 1 Jul 2019 04:52:24 -0700 (PDT)
Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CF1012008D; Mon, 1 Jul 2019 04:52:24 -0700 (PDT)
Received: by mail-io1-xd2d.google.com with SMTP id j6so28121478ioa.5; Mon, 01 Jul 2019 04:52:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=nAsGyo/ohAFHnjdrqk/X4fhq6HCnDW6F7AbxKf7dsZA=; b=tcb4gKCitOggljb69cdD13t1Rfr75Nfg9mtxe3395JgKWmOuUWml69H9DJBXINNVQ0 RXn7KYzq2HbfwmNBUuF0nry8sUWqzgY0gA58SfMAbe0tZwro46ljEsTD+/iWodWE/Cr9 glsW/RtHmn7XBd1Vqxy8kBmcRW/6R8zg4z1HKfj/nHlGgAF5l12Jl+j7cZxhoD653Hbs lTUkSEM8H4FJY9kilOdqFK8JTwePOllpGLP+7mLSFf7tbMRFjsb10slx1iW3jAJ9XH/E 1OevLVO9H8QsOTJ2naY9jBrQpaxRFwFXNl8bDI9rj5EnomusH/eE26fhCZMNx3p0CH78 YWDg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=nAsGyo/ohAFHnjdrqk/X4fhq6HCnDW6F7AbxKf7dsZA=; b=YQnOG/85Kaa0Vt3WSrcKk0CnUTpfkn5yNTEP7JAhFekzYbFQMlbI0pyCu+X4CCtk/x MH0wTDo4h//s8JU787aBTyQ6L9oVZZgiwDk87xDzBb2gGglzKT53e5BfZ9SaxNk4lbaM 6RI9Qmi6wAwFoD1G3iOOGS+8F1cOFeEzvVNZPREfjib48wFSV1tu0PwQZWw7PGRHbAVy cbygM2jAFQAPEJvXEE6NI3g9cNjp4P1xOjdnYItUOMF4O565hjRmuIh94TtDH/Lu6uGw ImagOWt+VSJfD1DlHzf96bD2ti5OD72zsyKiOjzCklQ4cltDnA4ajVaOhYUuFiQRTaah wNgw==
X-Gm-Message-State: APjAAAWXUoNTj+Ro9Hbl2zjh96xRJtKcbwCk8qTQtERWbifS3rnO2rLs FEMDV+E8+B1XCDWY65p7+daHEQb18t5zDJoNk447ECnBwvo=
X-Google-Smtp-Source: APXvYqwKv7PufIB+m0/Y8naPEkpOky2yypQl/k+KGAtV2SiayRLN21u1wZlihP6FgOiaG8JmrOinp1c7BcTKkoGT5Ks=
X-Received: by 2002:a05:6638:5:: with SMTP id z5mr29129225jao.58.1561981943104; Mon, 01 Jul 2019 04:52:23 -0700 (PDT)
MIME-Version: 1.0
References: <E060C2EE-56C8-4A4D-9EE7-F6C09D3C172A@cisco.com> <29188.1561913378@localhost>
In-Reply-To: <29188.1561913378@localhost>
From: "M. Ranganathan" <mranga@gmail.com>
Date: Mon, 01 Jul 2019 07:51:50 -0400
Message-ID: <CAHiu4JN0Jqcs--Wxb_+MMnTh2qdudq6-JwVVenZBF=jEe1Gntw@mail.gmail.com>
To: iot-onboarding@ietf.org, mud@ietf.org
Content-Type: multipart/alternative; boundary="000000000000dd468f058c9d4274"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-onboarding/IKGtIHRhutwkv_vSZ4A1GxoAUoM>
Subject: Re: [Iot-onboarding] [Mud] Side meeting at the IETF Montreal - call for agenda items
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: Mon, 01 Jul 2019 11:52:27 -0000

 The following draft looks interesting:

https://tools.ietf.org/html/draft-lear-opsawg-mud-bw-profile-00

Are there any plans for follow-on work?

(I'd like to bring it up for discussion during the side meeting ).

Regards

On Sun, Jun 30, 2019 at 12:49 PM Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Eliot Lear <lear@cisco.com> wrote:
>     > A number of people have contacted me about meeting in Montreal, and
>     > that they wouldn’t be available after Tuesday.  Conveniently, Monday
>     > morning is reserved for side meetings.  I propose we take advantage
> of
>     > this from 9:00 - 10:30 (yes, this bleeds into the 1st session).
>
> It bleeds into teep, and I'm curious about the loops BOF, so I probably
> take
> off at the appointed time.
>
>     > I’ve combined MUD and IoT Onboarding, just to save time, as there is
>     > substantial community overlap.  That’s because the spaces are clearly
>     > related, one being authentication of the device the other being
> network
>     > authorization.
>
> Agreed.
>
>     > This, then, is a call for agenda items.  I have a few of my own, but
>     > would prefer to hear from others first.  Also, are you ok with the
>     > Monday morning time slot and keeping these activities together?
>
>     > Ps: reminder: side meetings are not “official” anything.  Just a
>     > gathering of people with a common interest.  However, the meeting
> will
>     > run under the IPR rules of the IETF, regardless.  All are invited.
>
> So, I'm not sure if you are asking for BRSKI items, or IoT onboarding
> items in general.
>
> 1) Under BRSKI for non-ANIMA ACP uses, there is the question about
> open/closed
>    registrars, and operational considerations of total sales channel
> integration
>    (MASA knows the customers), vs retail integration (no knowledge of
>    customers).  There are probably areas of grey in between that might be
>    worth enumerating.
>
> 2) There is a similar question for MUD, which is how does the MUD
> controller
>    arrive at trust criteria for the signatures.  This is the
>    enterprise/customer side of the above story: do you know who you are
>    buying from?
>    This relates to the discussion we have had about controllers: I think if
>    we could pin down the quality of the signatures, we could say more.
>
> 3) MUD Operational considerations for devices that can grow "skills"
>
> Not really a topic exactly: but how do we get towards the point where we
> can test
> MUD/BRSKI integration.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
> --
> Mud mailing list
> Mud@ietf.org
> https://www.ietf.org/mailman/listinfo/mud
>


-- 
M. Ranganathan