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

Eliot Lear <lear@cisco.com> Mon, 23 March 2020 14:41 UTC

Return-Path: <lear@cisco.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 9DFC63A08A3; Mon, 23 Mar 2020 07:41:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.59
X-Spam-Level:
X-Spam-Status: No, score=-9.59 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_SPF_HELO_TEMPERROR=0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 wQ1xWCWmpAxp; Mon, 23 Mar 2020 07:41:33 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1E913A0898; Mon, 23 Mar 2020 07:41:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4191; q=dns/txt; s=iport; t=1584974493; x=1586184093; h=from:mime-version:subject:message-id:date:to; bh=Mi1OkN6cNVeRO0uDkiQ3ljBJEbagt767XyjGdf6RMtU=; b=I8iIxxsv06i/dWaho/Lgj64sb576Wa2PqG0ZKxgp/PxE3FLKTAPcj4XL zBBoyQQb6yAU+b8ayccquDHht/wcHlOkGCoo+kkgP0bui7Id39BX1imSY /bRve13iRHAy74KVWhKqMqWk/425VVNPOFh0xlV7Ny3g3VkFXR0b7Ueqh g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AHKgBByXhe/xbLJq1mHgELHIF9AYE9AgGBUlQBIBIqhBiIJF6HcZNfhhETgWcJAQEBDAEBHxAEAQGBUYVBPAINAgMBAQsBAQUBAQECAQUEbYVWDEIWAYU0dT4CYIM4AYJ8qzEaNXWBMoVLhQeBNgIBAQGMRoIAgREnDBSHF4NQMoIsBLBNgkYEglKFCI8pHYNOi1eMNIReii+HcYEchwuIJYM0AgQGBQIVggALN4EhMxoIGxVlAYJBCTUSGA2ObYg3hUJAAzCMRIJSAQE
X-IronPort-AV: E=Sophos; i="5.72,296,1580774400"; d="scan'208,217"; a="24676478"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 23 Mar 2020 14:41:30 +0000
Received: from [10.61.164.61] ([10.61.164.61]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id 02NEfTsD018207 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 23 Mar 2020 14:41:30 GMT
From: Eliot Lear <lear@cisco.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_376F253B-4055-43E1-99D8-5B3FD27793C3"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
Message-Id: <0DE46278-4708-42B6-8DFF-A8BC67B23F7E@cisco.com>
Date: Mon, 23 Mar 2020 15:41:29 +0100
To: mud@ietf.org, iot-onboarding@ietf.org
X-Mailer: Apple Mail (2.3608.60.0.2.5)
X-Outbound-SMTP-Client: 10.61.164.61, [10.61.164.61]
X-Outbound-Node: aer-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-onboarding/7rzt7YHG1B9WWQsnxfMt_mYRBB8>
Subject: [Iot-onboarding] 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: Mon, 23 Mar 2020 14:41:39 -0000

Hi everyone,

As part of mudding, I’ve been talking to the SBOM people.  These are the folk who are looking to produce a software bill of materials for IOT devices.  The question: how to find it?  Well, MUD to the rescue.  I’ve added a very simple extension (no draft yet but working on it) that would describe just how to get the SBOM.

While I was at it…

I also made some changes as to what happens when you click on the “download” button.  Not only do you get a MUD file, but you also get a DEMO CMS signature file as well.  If you trust this signature for anything other than demonstration purposes, well…

I also have now a demonstration QR code that contains the MUDURL alone.  This would be suitable for sticking on a box or otherwise providing legacy equipment folk.  I have some issues with this.  The first is that just scanning it on your iPhone gets you a JSON file.  From a tooling perspective… that’s not slick.  Also, it’s sometimes unnecessary, given what Michael is planning, and what is going into DPP.  Also, I’m currently using a questionable Google API to generate the QR code.  But as I am a questionable guy, and this is really for demonstration purposes, I think this is ok.

You can try all of this out at https://mudmaker.org/sbom.

I am NOT quite ready to roll any of this out onto the main mudmaker page, but would very much appreciate your comments.

Eliot