[OPSAWG] draft-ietf-opsawg-mud-08: Restricting temporal behavior using MUD.

"M. Ranganathan" <mranga@gmail.com> Fri, 08 September 2017 18:54 UTC

Return-Path: <mranga@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDBC713292A for <opsawg@ietfa.amsl.com>; Fri, 8 Sep 2017 11:54:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, 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 EF0al_Z8Ymfa for <opsawg@ietfa.amsl.com>; Fri, 8 Sep 2017 11:54:45 -0700 (PDT)
Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (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 5D9D513293F for <opsawg@ietf.org>; Fri, 8 Sep 2017 11:54:45 -0700 (PDT)
Received: by mail-wm0-x22b.google.com with SMTP id f199so9759542wme.0 for <opsawg@ietf.org>; Fri, 08 Sep 2017 11:54:45 -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=IDsmRHF9MfsdwtylVCoJ55gHeRwT+pWDKol4Deyku4w=; b=A0SHBdJNB44BR0q8fb+MPKoYapYCQfu8LhhByE3aOzWBhES32uCU9oEae3BCPx1ERJ vcOWGARVJyH4wNoT5+BeXux17A1XFpDlWMOD5awlZBAv1ZccAEGOmlrEgPjrrk63+Vet RjqxK1B666lOlD7FlgQc/rF2Iasi8ur9MiuITSEHHSHjoC4pKQhfnXJsP8fhVwh8Yz4n 6pHWl1kHhoKtdKsRA3v55NOpO7lRln85U0KCdwYQuq6O2JK4gpwaRkwxYYOI/zRlPapU 2GrRCZWlDYJCTiUNuARZdMTIZwXDZiukYnwl8p9XfcULaJSRnVmb3PpuD92cAkOD03Qd 3bmA==
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=IDsmRHF9MfsdwtylVCoJ55gHeRwT+pWDKol4Deyku4w=; b=S+4Dq1Ae3SkFfeDv5omO4NVK3J2TDI+uJoHbyP2MZevTMO1f8BiaFovxsMfpV59gg4 Tww7d8NdsGcQKy86vQ/T19PicJeesfSdteQv9vuMA4nJeTYz4TL7iXc421NIOhuZLuHN +Z36jpcI9jGPS+MHCclUladY8cfW71jD6Nxho1ddb5jIMgO9M6n5PQ65uQG41zeBFQFN 89SmOnhTrxquX+Bt6OpGEoqWlT80oUK+gi/Mk2ePYEkp5UKgvWS0S5z/OJaFoZ+j63B+ 3CW/U2U4uJygSK7Zjr3GNuWQs1HuvL3+PPLdPKnay5AAvrwt+/o0UfVGKiMrestdJosm Ypmg==
X-Gm-Message-State: AHPjjUhTtioKpGLgdmPKAbbLo1msu3iErdy32n7KisCoFvsfhRsg8X28 yKi7Ctc9FeZ/srUuiHIDwIsSdnoeIv91
X-Google-Smtp-Source: AOwi7QCuZ7tNVG9OUuf85Krq6usKye7Vn7ysFpvV0oaJfrQOsSoDuU98uIp3mKhLZGycCdQxeeLvCJKRynHhhEw1HG8=
X-Received: by 10.28.212.212 with SMTP id l203mr2242921wmg.33.1504896883569; Fri, 08 Sep 2017 11:54:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.184.71 with HTTP; Fri, 8 Sep 2017 11:54:02 -0700 (PDT)
From: "M. Ranganathan" <mranga@gmail.com>
Date: Fri, 08 Sep 2017 14:54:02 -0400
Message-ID: <CAHiu4JOrv82dG6=yazk7Lz+1quGnpDqyrc0k1JinpW8TTeDoZA@mail.gmail.com>
To: opsawg@ietf.org
Content-Type: multipart/alternative; boundary="001a11497de82b37810558b21cd0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/uvK50186_fn2yYAzL-3DxL8o2FQ>
Subject: [OPSAWG] draft-ietf-opsawg-mud-08: Restricting temporal behavior using MUD.
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 18:54:46 -0000

Hello!

MUD currently does not enforce restrictions on temporal behavior. For
example, I cannot specify how many times per second a device is allowed to
connect to a remote IP address and port.

Would this be worth considering?

Use case:

DDOS attack mitigation (?)


Ranga

-- 
M. Ranganathan