Re: [Madinas] MADINAS - Proposed Charter v2
Donald Eastlake <d3e3e3@gmail.com> Mon, 24 May 2021 18:34 UTC
Return-Path: <d3e3e3@gmail.com>
X-Original-To: madinas@ietfa.amsl.com
Delivered-To: madinas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4CB73A31F5 for <madinas@ietfa.amsl.com>; Mon, 24 May 2021 11:34:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 (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 juWW_gy2UYFp for <madinas@ietfa.amsl.com>; Mon, 24 May 2021 11:34:52 -0700 (PDT)
Received: from mail-il1-x12c.google.com (mail-il1-x12c.google.com [IPv6:2607:f8b0:4864:20::12c]) (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 00B633A31F3 for <madinas@ietf.org>; Mon, 24 May 2021 11:34:51 -0700 (PDT)
Received: by mail-il1-x12c.google.com with SMTP id o10so24856739ilm.13 for <madinas@ietf.org>; Mon, 24 May 2021 11:34:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=U8AQtS04/5rnIixeRpcmaT382Y88mVPfGqs9hWuVWJo=; b=PVJAKjwEc97UucFVJRTKDXKxhY5bW8vJcR+tgCKdlsy7YFaxrMYjcBP7lVkI8aUzlw 5tGofYuuDxBgVf+BscP1voFTZNfHMtUcR8lNV3fHrchrPCbFfedUqrd7QbFpFSjKl7RX CP/MzpN6PgMYIgz/aMo6J7yGCNfeNxzLkBZqiPfDq5I3XrcJTBbOgt1XBTB6wo84TmIc s2pB5Zi7YHIDqqqNqx1o2aQi9tyXUPjbdr4JV4bVPlgC7xMWNLY3rlcpP8FbqpyvXLgb AjaXZ/qZ35sJBjm2QJoGrYDQacw0sMh8uEhstLrT8tjq+CUVmrEXlB4jkgRpbSjrbQ5O 7e1w==
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:cc; bh=U8AQtS04/5rnIixeRpcmaT382Y88mVPfGqs9hWuVWJo=; b=U1/OqqNzT9zVxAV53fAH3r5ur3bApDcU6BivDUf+gQirqG+4Ozx0Zi993sT+FWOGw0 ZOJCV6ACXpVw4r/sFzwdA8rQkMgGcr2VXzG6TGMggBCGOGhlfSgl53xqwEcy9QnHFqrs 6XZm/HuKSYmO1ITJdKIySiXBDjN++Y8jEcwh/OSLkzpZf4FPQrP/rzC6OmZrw2E0311w 6etOpUdPrzQ9gNOHyn05B7XxKBASMU+/R/3xFeaQ7b6su+zswYgIOcKswHGQkL27GjF1 5SqcrXYjtthA+IsPjgtl7X7FjECtBdC8tZ5BXuxJg5XeTvL94E6EmKuGsWUyfkhKJ1kr C67A==
X-Gm-Message-State: AOAM533FaBApXg3Aeslw39NS9+rXHBfIO4vVnRdtSM4879NEfssjQxmJ c4yDqYeDpMHAt7XdQpLqjw1YeTAEDEzRa9OXdug=
X-Google-Smtp-Source: ABdhPJyM/rJdHmvr1diPO+xUP+1CRx/73TqfojBeuP7gh2/zyeJYzqTerDHHemdLw21J/eGnU2Be4MNFcf7jFTW3r5Y=
X-Received: by 2002:a05:6e02:6c8:: with SMTP id p8mr15061571ils.83.1621881290155; Mon, 24 May 2021 11:34:50 -0700 (PDT)
MIME-Version: 1.0
References: <DB7PR08MB3179887A2BF46A536358982A89299@DB7PR08MB3179.eurprd08.prod.outlook.com> <CAC8QAcdXwuSsx6YM-RGXsS59zBw4dkrs7TgqQrmqTbSuushA5w@mail.gmail.com>
In-Reply-To: <CAC8QAcdXwuSsx6YM-RGXsS59zBw4dkrs7TgqQrmqTbSuushA5w@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 24 May 2021 14:34:39 -0400
Message-ID: <CAF4+nEFFYrC0OyLFEZP5w+JjCAjP-w62Es++=Ss0omgRW2Lvnw@mail.gmail.com>
To: sarikaya@ieee.org
Cc: Juan Carlos Zuniga <juancarlos.zuniga@sigfox.com>, "Weil, Jason" <Jason.Weil@charter.com>, "Pascal Thubert (pthubert)" <pthubert@cisco.com>, "madinas@ietf.org" <madinas@ietf.org>, "Jerome Henry (jerhenry)" <jerhenry@cisco.com>, Juan Carlos Zuniga <j.c.zuniga@ieee.org>, "jerryponline@gmail.com" <jerryponline@gmail.com>, CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es>, "simon.ringland@bt.com" <simon.ringland@bt.com>, Erik Kline <ek.ietf@gmail.com>, "Eric Vyncke (evyncke)" <evyncke@cisco.com>, "Lee, Yiu" <Yiu_Lee@comcast.com>
Content-Type: multipart/alternative; boundary="0000000000002aeba705c317aa61"
Archived-At: <https://mailarchive.ietf.org/arch/msg/madinas/_LOTmJKHTEoskOEo4_cGG1a-wT8>
X-Mailman-Approved-At: Mon, 24 May 2021 23:26:39 -0700
Subject: Re: [Madinas] MADINAS - Proposed Charter v2
X-BeenThere: madinas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: MAC Address Device Identification for Network and Application Services <madinas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/madinas>, <mailto:madinas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/madinas/>
List-Post: <mailto:madinas@ietf.org>
List-Help: <mailto:madinas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/madinas>, <mailto:madinas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 May 2021 18:34:57 -0000
On Mon, May 24, 2021 at 12:04 PM Behcet Sarikaya <sarikaya2012@gmail.com> wrote: > Hi all, > ... > Device identity is important in scenarios where the network needs to know >> the device or user identity in order to offer, operate and maintain certain >> services. Currently, many use cases and applications make an implicit >> assumption about the unique association between the device identity and its >> MAC address. This assumption is being used in both control plane and data >> plane functions and protocols. RCM will break this assumption. This >> requires update of the current applications to function across MAC address >> changes. >> >> The MADINAS Working Group will examine the effect of RCM schemes on >> network and application services in several scenarios identified as >> relevant. The group will also evaluate various identifiers (beyond the MAC >> address) that can be used by the network to provide services, as well as >> scenarios where personal device identity is not required. >> >> For scenarios where personal device identity stability is desirable, the >> Working Group will recommend protocols that can be used to protect the request >> and exchange of identifiers between the client and the service provider. >> For scenarios where privacy is paramount, the group will recommend best >> practices to ensure that the privacy achieved with RCM is not compromised >> by the communication of other identifiers. The MADINAS Working Group will >> examine other IETF work that may be applicable. >> >> The Working Group will work together with other IETF WGs (e.g., DHC, >> IntArea), >> > > I thought DHC WG is closed? > DHC is still an active WG: https://datatracker.ietf.org/wg/dhc/about/ Thanks, Donald =============================== Donald E. Eastlake 3rd +1-508-333-2270 (cell) 2386 Panoramic Circle, Apopka, FL 32703 USA d3e3e3@gmail.com Behcet >
- [Madinas] MADINAS - Proposed Charter v2 Juan Carlos Zuniga
- Re: [Madinas] MADINAS - Proposed Charter v2 Bob Hinden
- Re: [Madinas] MADINAS - Proposed Charter v2 Bob Hinden
- Re: [Madinas] MADINAS - Proposed Charter v2 Juan Carlos Zuniga
- Re: [Madinas] MADINAS - Proposed Charter v2 Behcet Sarikaya
- Re: [Madinas] MADINAS - Proposed Charter v2 Bob Hinden
- Re: [Madinas] MADINAS - Proposed Charter v2 Donald Eastlake
- Re: [Madinas] MADINAS - Proposed Charter v2 Juan Carlos Zuniga
- Re: [Madinas] MADINAS - Proposed Charter v2 Bob Hinden
- Re: [Madinas] MADINAS - Proposed Charter v2 Juan Carlos Zuniga
- Re: [Madinas] MADINAS - Proposed Charter v2 Behcet Sarikaya