Re: [Mud] what if MUD file is now longer available?

"Marc Blanchet" <marc.blanchet@viagenie.ca> Sun, 12 May 2019 01:19 UTC

Return-Path: <marc.blanchet@viagenie.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 8393E1200FA for <mud@ietfa.amsl.com>; Sat, 11 May 2019 18:19:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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=viagenie-ca.20150623.gappssmtp.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 zf1f29bFERHg for <mud@ietfa.amsl.com>; Sat, 11 May 2019 18:19:17 -0700 (PDT)
Received: from mail-qt1-x82d.google.com (mail-qt1-x82d.google.com [IPv6:2607:f8b0:4864:20::82d]) (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 2195F120092 for <mud@ietf.org>; Sat, 11 May 2019 18:19:17 -0700 (PDT)
Received: by mail-qt1-x82d.google.com with SMTP id d13so3843758qth.5 for <mud@ietf.org>; Sat, 11 May 2019 18:19:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=viagenie-ca.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version; bh=UdwAYH3dWz3mUzDIJv/DvACZyYdUKncVY13Tw1iZ1sE=; b=zlOag2uTeGRznBOkqHY6BUJtSJPF+bAsnP6uIoEGJcUBpt0xKTF1VzEX360ziDgSW5 ANX4C9KICZRS9LK16HQ7gwiIJGc7Ogo2OWMgf2bxOGxRuoRMwcyPwsInQqlvaPUx8Bkj BESTk30umXxNYrrIrDK4IOaFWm7n2cbVMN2OILhyRZw3fktbYMur8Qt6fIfN1/UCdfZo 8udRqf1DH6gTHqkAcisSByvvbwfJFpnhowWf0Q6Pnl07pdKPp5WAL5hoIu5uz7IIc7MU aR7owUoG9pJYSDCra48aafF9S1Hqo5CAxDbiggd9njZBlarYsBg+HiefYQpxqjSN7oIa NKKg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version; bh=UdwAYH3dWz3mUzDIJv/DvACZyYdUKncVY13Tw1iZ1sE=; b=nO0f00Ydy84jY0qQSTq6NJBD5aq6PJt4CgOkjhJwmUeNuYcicSKXEE1YqGsxoE2Rw/ emt5WG272Cm3yVs6QE/BQwOutFW4LuM4Dg/ouwB5trHxS02v3EShi7WtEddb/gPXK0RL X9eXmkSaqXN9fmdexizBNqcJuYsZUz4UzJPMGYp+9EgcJ/dA5c+uBRmAU5BoHOUmyNTt rU27j3k1ltRckrpe/ENh6Mh2EwIZw+cWFJNykFHUdOTqAuFFSh/XxMa1a77OgfWzmUqe uVE/XJtNqbJhjg8v7vCFxjQQPpPliFkCnVIesjvzpY3TI2dEBKtB11O5CH1/5j53g2Dj HK6g==
X-Gm-Message-State: APjAAAVZ4ZT+nwtIfHwq6iT3cKWhLGdp2VYHEhRN+imhE+Kya48910al 6BtVJnTs5GYallLDj30NRMnRLv0LBD31ZA==
X-Google-Smtp-Source: APXvYqzueNodVqtXF9sYeFrOI4csGwh4h5/xrR9uTV1di/cRVYDJ+WQRGtnlN2A3qP5fQiOSGif+XQ==
X-Received: by 2002:aed:3598:: with SMTP id c24mr17415296qte.364.1557623955913; Sat, 11 May 2019 18:19:15 -0700 (PDT)
Received: from [206.123.31.196] (modemcable040.161-162-184.mc.videotron.ca. [184.162.161.40]) by smtp.gmail.com with ESMTPSA id p6sm4945477qkc.13.2019.05.11.18.19.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 11 May 2019 18:19:14 -0700 (PDT)
From: Marc Blanchet <marc.blanchet@viagenie.ca>
To: mud@ietf.org
Cc: mud-discuss@googlegroups.com
Date: Sat, 11 May 2019 21:19:12 -0400
X-Mailer: MailMate (1.12.5r5632)
Message-ID: <E6FCE197-2A19-447D-9AB6-C2CEBCA9C468@viagenie.ca>
In-Reply-To: <17454.1557618668@localhost>
References: <17454.1557618668@localhost>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; markup="markdown"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mud/2dkuVRlXo0zl-IjEtEGPzplsku4>
Subject: Re: [Mud] what if MUD file is now longer available?
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: Sun, 12 May 2019 01:19:19 -0000

On 11 May 2019, at 19:51, Michael Richardson wrote:

> {did the list transition go as intended?}

sorry. just did.

>
> What should a MUD-manager do if a MUD file can no longer be found at 
> the
> provided URL?   Perhaps this is equivalent to the signature not 
> verifying.
>
> I'm thinking specifically of a case where a device is initially 
> created by a
> contractor, they dutifully create a MUD file, provide it to the 
> customer to
> host, and then.. the customer forgets... marketing reorganizes the web 
> site,
> etc.  and so the MUD file goes missing.
>
> Section 13.2 says that the MUD-manager should cease processing at that 
> point.
> I guess at that point, the access should therefore be default-deny.
> I guess the other question is what would the access be if there were 
> no
> MUD URL at all.  We'd all like to be default-deny, but I think that 
> during
> a transition period it can't be that.
>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
> -- 
> You received this message because you are subscribed to the Google 
> Groups "mud-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to mud-discuss+unsubscribe@googlegroups.com.
> To post to this group, send email to mud-discuss@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/mud-discuss/17454.1557618668%40localhost.
> For more options, visit https://groups.google.com/d/optout.