[dhcwg] BoF and Non-WG Mailing List: madinas -- MAC Address Device Identification for Network and Application Services

Juan Carlos Zuniga <j.c.zuniga@ieee.org> Sun, 01 November 2020 21:56 UTC

Return-Path: <j.c.zuniga@ieee.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 707973A0994 for <dhcwg@ietfa.amsl.com>; Sun, 1 Nov 2020 13:56:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-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_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 (1024-bit key) header.d=ieee.org
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id c6Dcz2D0nSz8 for <dhcwg@ietfa.amsl.com>; Sun, 1 Nov 2020 13:56:57 -0800 (PST)
Received: from mail-il1-x129.google.com (mail-il1-x129.google.com [IPv6:2607:f8b0:4864:20::129]) (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 715C53A0990 for <dhcwg@ietf.org>; Sun, 1 Nov 2020 13:56:32 -0800 (PST)
Received: by mail-il1-x129.google.com with SMTP id a20so11249502ilk.13 for <dhcwg@ietf.org>; Sun, 01 Nov 2020 13:56:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=EbZ5+8CDBRUfDLGTpqiblsCdSrsOoXOVZriwuoqasFM=; b=PwEegNzqRSPSDdU+jP1PNmu+tzDUmPhUklaGPSisOp/TViua4y/3hyJ9Bldo11ceQz xSJuel04aT+gqa0QM8+vBD24vqUI6E5luDghV5BaeICBKmncrS0+H25eSw9dD6q+oGxj 1NT6F5+kLJKHcNcMLrBcpclmx5boMnsPgE8UM=
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; bh=EbZ5+8CDBRUfDLGTpqiblsCdSrsOoXOVZriwuoqasFM=; b=ThfRgjER4aRB/ETxwPmXQQMiyrHEhuplNBq+Omn2uqvtZOKXXjQr9o4QzTzcM6XqGg 3j230MObWxC9jD3F/2IAYl0I1MPDQGrAjrRXA903+ZXoC3aKxbFwCY5Z1GcJBl8Wi0mY d2WZpiDJC064dpz3T7FDt7kPay+nlXRWz/4Asjz4HugaXBH/svdQpb0ozX946s1j5z3U p+8gszdHKcVinbxSdZ8uGpMY+BRRFt80KlnEJO/Ue+3xKv8nhFQPM5sVXoJAdxFQO4kR 5Q5Ka/RHDrZ3UthZJ+B3T0sW75aWTJpct1OXIiZ5Kc1A5L79wvGx2bdIsLteHFB8pDCC kffA==
X-Gm-Message-State: AOAM530vP6BkJJqUc44jC6SG0PR65MaC8Tvl+3X5HU4ShWrTd3byOjAd xopK7nXvw5soSFyRk6q6srK9c7xXZW8paIhjOpP6p26nACPZYg==
X-Google-Smtp-Source: ABdhPJypPtzPfBTvKijznidh9i5sIHsdTGjrFp8Y96HNN4F3TSFzTCXh9GADa4cV32r6qjwms7GiNHIUCKKuL8DRnMQ=
X-Received: by 2002:a05:6e02:1252:: with SMTP id j18mr8477851ilq.119.1604267791537; Sun, 01 Nov 2020 13:56:31 -0800 (PST)
MIME-Version: 1.0
References: <160407478723.4708.16590139659517606146@ietfa.amsl.com>
In-Reply-To: <160407478723.4708.16590139659517606146@ietfa.amsl.com>
From: Juan Carlos Zuniga <j.c.zuniga@ieee.org>
Date: Sun, 1 Nov 2020 16:56:20 -0500
Message-ID: <CAHLBt83DN3OxhXbkFKPBh7KbPFvKJKjgdf5UfoGVSsTJh6+H=Q@mail.gmail.com>
To: int-area@ietf.org, dhcwg@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d706ff05b312b35b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/eZGtvYBVAd3CwWUc5A8wn63H0IY>
Subject: [dhcwg] BoF and Non-WG Mailing List: madinas -- MAC Address Device Identification for Network and Application Services
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Nov 2020 21:57:00 -0000

Hello all,

At IETF109 there will be a BoF to discuss MAC address randomization and
implications on network and application services.

If you are interested in the topic please join the mailing list.

A draft agenda of the BoF can be found here:



---------- Forwarded message ---------
From: IETF Secretariat <ietf-secretariat@ietf.org>
Date: Fri, Oct 30, 2020 at 12:19 PM
Subject: New Non-WG Mailing List: madinas -- MAC Address Device
Identification for Network and Application Services
To: IETF Announcement List <ietf-announce@ietf.org>
Cc: <madinas@ietf.org>rg>, <j.c.zuniga@ieee.org>rg>, <evyncke@cisco.com>

A new IETF non-working group email list has been created.

List address: madinas@ietf.org
Archive: https://mailarchive.ietf.org/arch/browse/madinas/
To subscribe: https://www.ietf.org/mailman/listinfo/madinas

This list is for discussion of the MAC Address Device Identification for
Network and Application Services (MADINAS) BOF at IETF 109.

Major operating systems have implemented and deployed MAC Address
randomization features to enhance device and user privacy, as randomization
can help avoid device identification. Device identification by MAC address
is often used in ways that do not invade privacy, but that provides useful
services to the device user. These services include network optimization,
access control, usage counting, and security and user protection services.
Some examples are LAN forwarding policy, sticky DHCP IP assignments, static
NAT policy and MAC address ACL for blocking malicious or unwanted devices.
In those situations, the deployment of MAC address randomization results in
unintended and likely unforeseen impacts to the network, systems and
applications external to the device implementing randomization.

This illustrates a potential need for the networking community (OS vendors,
device manufacturers, application developers and network operators) to work
more closely together to solve the needs of the end users. In some cases, a
greater awareness by Network and Application Services to current MAC
address usage may be enough. For other cases, a new solution may need to be
developed and standardized to reach the desired outcome. The proponents of
this BoF are interested in determining if there is sufficient support in
the IETF community to define best practices, update any existing documents
if needed, or potentially develop new protocols or mechanisms for service
continuity in the presence of MAC Address randomization.
This list belongs to IETF area: INT

For additional information, please contact the list administrators.