[Mud] MUD server discovery?

"M. Ranganathan" <mranga@gmail.com> Tue, 14 January 2020 20:04 UTC

Return-Path: <mranga@gmail.com>
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 14FCE120A03 for <mud@ietfa.amsl.com>; Tue, 14 Jan 2020 12:04:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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 b0DTpUL_Bg0n for <mud@ietfa.amsl.com>; Tue, 14 Jan 2020 12:04:29 -0800 (PST)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (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 4D1D312093D for <mud@ietf.org>; Tue, 14 Jan 2020 12:04:29 -0800 (PST)
Received: by mail-io1-xd32.google.com with SMTP id n11so15243842iom.9 for <mud@ietf.org>; Tue, 14 Jan 2020 12:04:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=FDPoHhnBFb3snEaDbBjuHKZHDQF2vsDg7ovKh8toDis=; b=HMq7OcWNxjBwo6FQeuE3NDU9nrUupZBjTMCFomXP6BL//L3phAkPQjuQFQ7jAxkyq9 mGbRZjSGcljCCU7zkOcxJ9eCJlizvVgUXuo/bLVcLD3FhF65ClWlOv4ZeTQNy5KW7Bku XSAxMBQIGm4kUdSFdnxi1QxCAsjIKWeXUI6Kc5+GMnF420k2tpG6OtkizA1TTykCk6ne 9WVyhvx3AU48162B1Ar9sNKsHs8H24l0aZAnMsjvDr1O6irdgFi/xyDHDd1P1ZqqrOXW 91O4lYB7lV4fmP66OLs6Fo4cmJkPqRFp0jcBhyVj73m9dacOn0fck9tIoshIKu/XLChY QrIg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=FDPoHhnBFb3snEaDbBjuHKZHDQF2vsDg7ovKh8toDis=; b=VdKBrIx7Ss3xXEQlVZTRucaHIM6+aeabztdMn52DPw2YSc81JuMfKtBQpKQgjAFgbl uWKUdGHnQPCxIWik/3Gj7e3GrCb43A/2ju4JWDQ/CqaLn4+5JYu/e4c0QwfDkJwlDvVT bmuToLuOS1hURUpnlWCojEGnVLUWOKIjyqgsbOHYVO2oiuGtHJv8m1r7wBT8YMGm9Kf6 CBV3pGQh85FqquZNcTQUKd+bEB8IZgK1ahmzv+AFn6kE7qEV7OfRuSviVxmyo4IH82bX 1bDP1YnAYqxC1PoNQIwFNRUhxaz0cC7nw0T9flm575/0GbM67PnSyZf1fUjysvHRu/u1 264Q==
X-Gm-Message-State: APjAAAXttITpM97KkwdBya2NaimNBoW0EWQ//jbqYAzWTmVIqdZk1e3x Bo/+RU7yo5QjeMaGeWboLd3T3jKvoxtZoLE1i1gR6ZT19kQ=
X-Google-Smtp-Source: APXvYqyZtYmuO0Eutno50f4hLuyAGEs88SVcckjvk54lKrQz3cXbal6jdkxYrLRZeG2JORXiPpylO+jdFhNC+eri1P8=
X-Received: by 2002:a5d:8cce:: with SMTP id k14mr19351918iot.294.1579032268077; Tue, 14 Jan 2020 12:04:28 -0800 (PST)
MIME-Version: 1.0
From: "M. Ranganathan" <mranga@gmail.com>
Date: Tue, 14 Jan 2020 15:03:52 -0500
Message-ID: <CAHiu4JNBJ2YrO8a6usMvS1ku1iGkgZCD5zwFrvVEF4AAn8jc4w@mail.gmail.com>
To: mud@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mud/JpyKADmYLv8WxOdZu7Y2qjmQzyY>
Subject: [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 20:04:36 -0000

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.

Is there a use case for the MUD server address to be published so it
can be discovered by such applications?

If yes, then should there be a REST API for such use cases? Are there
better ways of doing this?

Thanks

Ranga



-- 
M. Ranganathan