Re: [Iot-onboarding] [Mud] Some new stuff for mudmaker.org

"M. Ranganathan" <mranga@gmail.com> Tue, 24 March 2020 22:40 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 5BCEE3A0768; Tue, 24 Mar 2020 15:40:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 h44qmJuGpDcj; Tue, 24 Mar 2020 15:40:34 -0700 (PDT)
Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (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 D80253A05E2; Tue, 24 Mar 2020 15:40:34 -0700 (PDT)
Received: by mail-io1-xd2a.google.com with SMTP id n21so306785ioo.10; Tue, 24 Mar 2020 15:40:34 -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 :cc; bh=itwN1Qs3JAlK+vROzVY2MJwVFzuehjpNMNuWB2LGM3c=; b=nzTxEU1WLNA9h9A53AOjj89Gi0Cx6cXgiK27bOBSx/k1lwechMa9TX04cy+h9d9I7D QBItiK2SQ6Sm2g0MuyG84sDpG1+PKZvpNF0wWZ2Qvo1Q+BH0TXCC/3Hs7B4ePkfhyZcM LnP4J5YnifgSoMmuLT+9utAk7wbYHMrOjU0tSqHw8ABIjSZWFh9TyWv4cTHd53nE4kXi 9nuo7NL0cXI6HhsKzbaT37BtmiFgJyKOB3/LXI/wbsABFiG7ngM0n7SlzvA5FaL9Q1Mb LyrOXTbAByjdI9pIxf/JOTYAGrMQD+2dMDKY8bVx6gNsKhWGoMqC2lF5mEI5rFCnH98w fUgw==
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:cc; bh=itwN1Qs3JAlK+vROzVY2MJwVFzuehjpNMNuWB2LGM3c=; b=OBhWudFoncmJcELEEXHMEHRq3mgGW9th33AeorsnxOl+VCnxE2IMcDd+aMZHkWeS88 I0f+kGzL/4D8neLKauY9aPEeApzEc9ceimih3402Zauwf9S6hExX9qIG3n2YSNH27Fme lvkWg29Uj4CJeq/7377h3r9aF9ZK+Pt4pJ6Wae0HMcC8VDo+3CLjQvCeWyH5OmxGpdHW bNl+df/Q6dJthaKgeQsGHq/mgyJpuPa/j4TmAO7sejI7bnTm3t1ths4xYpP8jSd6z0fa 2uX4phIFJrC4FWwGjp+IoNnxagVGfkFvlJgH5/hnAtr3vcxzmR4dqUamOm4wbPRZ4pab 1iDQ==
X-Gm-Message-State: ANhLgQ1bI9K7130CuaWxG22WQNuw3Xo/SXtMxK8/ljLXcEZULWWyjxM5 m4Js0fdSvZ+j1aRMmsEdzKk6GPMCXA7U96FjCGA=
X-Google-Smtp-Source: ADFU+vtWVrQqc8R+NjaF6j9tfy+kLp6ViMyKxRY+FoqO8fUHuIPVxmpsMgG7MFJVoV5texlQ4z9MIDIEZpNk2qH/kyE=
X-Received: by 2002:a5e:9e0a:: with SMTP id i10mr266191ioq.173.1585089633850; Tue, 24 Mar 2020 15:40:33 -0700 (PDT)
MIME-Version: 1.0
References: <0DE46278-4708-42B6-8DFF-A8BC67B23F7E@cisco.com> <CAHiu4JPqXd2emEFCRK2dq0L6OFOcr-UdNkhJ2W+Cx5TUCLrprA@mail.gmail.com> <17397.1585086427@localhost>
In-Reply-To: <17397.1585086427@localhost>
From: "M. Ranganathan" <mranga@gmail.com>
Date: Tue, 24 Mar 2020 18:39:57 -0400
Message-ID: <CAHiu4JNfWBBMZV0bO41Emdo4GO2EFmicw+E=np_Xey_xG4JsKA@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>, iot-onboarding@ietf.org, mud@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-onboarding/uPljR0FHYC5E8ZBwJDbq5uy4miI>
Subject: Re: [Iot-onboarding] [Mud] Some new stuff for mudmaker.org
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: Tue, 24 Mar 2020 22:40:37 -0000

On Tue, Mar 24, 2020 at 5:47 PM Michael Richardson
<mcr+ietf@sandelman.ca> wrote:

>     > I have a very basic question about the whole notion of mixing SBOM with
>     > MUD. MUD was intended for network access control whereas SBOM is more for
>     > ensuring software integrity. Should this be part of the MUD file or
>     > included (for example) as a pointer in the device certificate so it can be
>     > independent of MUD? Why include this as part of the MUD file?  I'd just
>     > like to understand the motivation.
>
> For the same reason that the MUD file pointer in the IDevID presents update
> problems.  The SBOM is directly connected to the firmware revision, while the
> IDevID ought to live across firmware versions (and be hard to replace).

Makes sense now. Still wondering what the network would do with the
SBOM but that is a different thread.

Thanks,
Ranga

-- 
M. Ranganathan