Re: [Mud] MUD server discovery?
Michael Richardson <mcr@sandelman.ca> Tue, 14 January 2020 21:53 UTC
Return-Path: <mcr@sandelman.ca>
X-Original-To: mud@ietfa.amsl.com
Delivered-To: mud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DB6F120113 for <mud@ietfa.amsl.com>; Tue, 14 Jan 2020 13:53:27 -0800 (PST)
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 hHEGQOUPT31L for <mud@ietfa.amsl.com>; Tue, 14 Jan 2020 13:53:25 -0800 (PST)
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 7DC5F120059 for <mud@ietf.org>; Tue, 14 Jan 2020 13:53:25 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 8335B3897B; Tue, 14 Jan 2020 16:52:19 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 91EC2108F; Tue, 14 Jan 2020 16:52:45 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: "M. Ranganathan" <mranga@gmail.com>
cc: mud@ietf.org
In-Reply-To: <CAHiu4JNBJ2YrO8a6usMvS1ku1iGkgZCD5zwFrvVEF4AAn8jc4w@mail.gmail.com>
References: <CAHiu4JNBJ2YrO8a6usMvS1ku1iGkgZCD5zwFrvVEF4AAn8jc4w@mail.gmail.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, 14 Jan 2020 16:52:45 -0500
Message-ID: <24846.1579038765@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mud/kP1M9gaQ_OeH185noN1WxiyCqbo>
Subject: Re: [Mud] MUD server discovery?
X-BeenThere: mud@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of Manufacturer Ussage Descriptions <mud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mud>, <mailto:mud-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mud/>
List-Post: <mailto:mud@ietf.org>
List-Help: <mailto:mud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mud>, <mailto:mud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2020 21:53:27 -0000
M. Ranganathan <mranga@gmail.com> wrote: > There are a couple of situations I can think of where a trusted agent > may need to communicate with a MUD server: > 1. Controller Application: A Controller application may need to "tell" > the MUD server when it joins the network and that it is a controller > for a device. Perhaps it presents a signed certificate to assert its > identity to the MUD server. > 2. Onboarding using a third party app (e.g. DPP). The onboarding > application may need to communicate the identity (Device certificate) > to the MUD server. My opinion is that the this should be an extension in the CAPPORT API. MUD controllers need the CAPPORT API to indicate if they have quarantined a device. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | IoT architect [ ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
- [Mud] MUD server discovery? M. Ranganathan
- Re: [Mud] MUD server discovery? Michael Richardson
- Re: [Mud] MUD server discovery? M. Ranganathan
- Re: [Mud] MUD server discovery? M. Ranganathan