[Mud] Hackathon topics for IETF 105
"M. Ranganathan" <mranga@gmail.com> Wed, 05 June 2019 16:26 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 4D57312018C for <mud@ietfa.amsl.com>; Wed, 5 Jun 2019 09:26:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=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 dpxUPoVCvTW1 for <mud@ietfa.amsl.com>; Wed, 5 Jun 2019 09:26:04 -0700 (PDT)
Received: from mail-it1-x12f.google.com (mail-it1-x12f.google.com [IPv6:2607:f8b0:4864:20::12f]) (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 90B2F1201D5 for <mud@ietf.org>; Wed, 5 Jun 2019 09:26:04 -0700 (PDT)
Received: by mail-it1-x12f.google.com with SMTP id j204so4458098ite.4 for <mud@ietf.org>; Wed, 05 Jun 2019 09:26:04 -0700 (PDT)
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=ixojY3u7IeqKyHEIzc4QrPjY78D8u98IF0H5HT3dO9A=; b=Ga7ZG2eEI+YBqumG9iuaBvy98HsA798kMsMe2lQaHD+gWBAaf7aia0q2OG6hPtG3L8 HTqbfPVkirhTSiad88+hGTMhjYBO45xiZHEHnBh368Upiu5uodoLVmh1b18eH4TEkmSV S9DZ4BsEAc8B7sLMPXC/DK8GNu06YrEQCNo6hW6Lzio60X8wAEZQjx/+P7nC9iV2wyro AHNSqhPsocI9FD+P9ZBZDhRSRdTezSfxW48ekEobKqc1sytBD/gHiGo+sXIhnQMzyCg4 DGeuFxacMdvCDqVrRpsKTn3AIxD0JdCTvMiLdLqf40jodTaxfj01BWiv2xqT9JT6hDa5 9DkQ==
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=ixojY3u7IeqKyHEIzc4QrPjY78D8u98IF0H5HT3dO9A=; b=abzbVjehH9I9Nq0+9AC3a4EZF5619JOpCBW36smXMjRxq5zW2It/6r1fJ4Z6g5QcZZ pxkaA4FdeaXbbyn5a6lTGGHVw+OdROuvE0Z0DcNXBkohco0lHZg5dsme9Ko+0hCw3moM kQEqI6G6t51F5l70wFuezV0cchcwMeEPrYFJYSzDe2yOFiltRFXL+T5K3mPi7SwE0EZH HYmzpSU1MiyzKsm+dAYzhMZIjyOZaRYnoCXvl4r3QaPTyX5MDfYZNmxZY94dFXDyzqmI 4Ve+Djfu3u1u/W1/T1ZYYqE4iYo3izT2l0kHXnUkgZvvLzRgLT3Cj0YeKd0gp1y9kSfe yrtw==
X-Gm-Message-State: APjAAAUp0XKrur7Qki6flXDaSEWPXSsRL1m0O4dqmCe67n70N2QFluCY nY7uGYYdORNY9O5BQLwMvmux+AWqm2dd892awySnUQ==
X-Google-Smtp-Source: APXvYqyjq3Z9PGNBlwx1W5M8OxsZO6IktNaJI5MthIOLDZ0aZzcdZXZ+cYxg11PQld5/RyTGb/y6P1PTXYNFRDpyYDY=
X-Received: by 2002:a24:4344:: with SMTP id s65mr13414020itb.137.1559751963409; Wed, 05 Jun 2019 09:26:03 -0700 (PDT)
MIME-Version: 1.0
From: "M. Ranganathan" <mranga@gmail.com>
Date: Wed, 05 Jun 2019 12:25:27 -0400
Message-ID: <CAHiu4JMS51oB3Wu1ZDkXsk2_M4F_RivV9VpdoBJRmWV0FAwwng@mail.gmail.com>
To: mud@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b781f6058a960dd3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mud/fCWgHwFo4nhjBa6sclAPvVS2WvY>
Subject: [Mud] Hackathon topics for IETF 105
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: Wed, 05 Jun 2019 16:26:13 -0000
There is going to be a "hackathon table" for IETF 105. Here are some ideas that occurred to me: - Quarantine : Mechanisms to isolate devices that violate MUD-specified ACEs. - Logging and Event notifications : If a MUD-enable device violates its allowed behavior, one approach is to summarize the violations and send event notifications to some centralized event-gathering point. What to report and to whom? Should we incorporate rate specifications so excessive connections or packet rates can be logged and notified. Any other candidates? -- M. Ranganathan
- [Mud] Hackathon topics for IETF 105 M. Ranganathan
- Re: [Mud] Hackathon topics for IETF 105 Eliot Lear
- Re: [Mud] Hackathon topics for IETF 105 M. Ranganathan