Re: [OPSAWG] [Mud] Declaring something to be a controller in MUD

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 26 June 2019 21:26 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE6FD120188; Wed, 26 Jun 2019 14:26:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 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, URIBL_BLOCKED=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 mHjcPmi4dHOw; Wed, 26 Jun 2019 14:26:28 -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 0C09E1203AE; Wed, 26 Jun 2019 14:26:27 -0700 (PDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id 5D9A13808A; Wed, 26 Jun 2019 17:24:42 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 297E2E68; Wed, 26 Jun 2019 17:26:26 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 28194E37; Wed, 26 Jun 2019 17:26:26 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Eliot Lear <lear@cisco.com>
cc: opsawg@ietf.org, mud@ietf.org
In-Reply-To: <7DDDF804-8171-4E1E-91C5-CBE4D2965939@cisco.com>
References: <1FDE5A58-569B-47FD-8C24-435D78F8A3B2@cisco.com> <1547.1561492346@localhost> <BE16542E-7383-4006-A00F-5000BEC4E68B@cisco.com> <11505.1561563275@localhost> <7DDDF804-8171-4E1E-91C5-CBE4D2965939@cisco.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: Wed, 26 Jun 2019 17:26:26 -0400
Message-ID: <13929.1561584386@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/rhTbmXs_18Dos772fjrVqrvl7fA>
Subject: Re: [OPSAWG] [Mud] Declaring something to be a controller in MUD
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jun 2019 21:26:30 -0000

Eliot Lear <lear@cisco.com> wrote:
    >>> There will ALWAYS be a need for an administrator in the enterprise
    >>> case.  But maybe with the options above we can ease the consumer burden
    >>> over time.  In the consumer case, you might want an app for initial
    >>> device admission control anyway, no?  Can we not rely on that
    >>> interaction as an approval step in this instance?
    >>
    >> I think we'd all like to have a generic app (with an RFC standard API) that
    >> can onboard any device and can do admission control for any controller.
    >> I think this is what you are saying as well.

    > Yes, but I was saying a bit more.  Do you expect to fully automate the
    > inclusion of a controller into a controller class in the home?  How do
    > you envision the full flow looking like?

I expect to fully automate the inclusion of a controller into that class,
yes.   I'd like to automate the device into the class too.

Perhaps your point is that since the controller has to onboard (at the
layer-7) the device in anyway: can we leverage that?

    >> yes, this is exactly what I was thinking about.
    >>
    >> Would "mud-urls" / "include" be mutually exclusive?

    > I don’t see why it would have to be.  But now let’s back up, just to
    > make sure we’re not digging too deep a hole for the application case
    > that Ranga wants to get to.  If the MUD protected device is declaring
    > MUD URLs for MUD controllers and that is what all of this would boil
    > down to, then the app case is really a completely separate mechanism,
    > because apps don’t have MUD-URLs.

    > If we do a two-stage, then we need a completely separate draft for apps
    > anyway, but I was hoping for some commonality.

Hmm.

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