[Madinas] questions on draft-henry-madinas-framework
Joey S <joeysalazar@article19.org> Thu, 02 December 2021 17:09 UTC
Return-Path: <joeysalazar@article19.org>
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 596973A1282 for <madinas@ietfa.amsl.com>; Thu, 2 Dec 2021 09:09:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, RCVD_IN_MSPIKE_H2=-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=article19.org
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 SZTx5NwMdZty for <madinas@ietfa.amsl.com>; Thu, 2 Dec 2021 09:09:16 -0800 (PST)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BD233A1283 for <Madinas@ietf.org>; Thu, 2 Dec 2021 09:09:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=article19.org; s=mail; h=Content-Type:MIME-Version:Date:Message-ID:Subject: From:To:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=2kcqomlukJe7KMGy4E2Qq89ns+xClJtnd26v35OEezE=; b=NwoNnSRuKyWQ2NBWpQ4C+WZ5vT 7OZzt2TsP8GUQV29d1fRG7GU1ky4k1sBy9ZM4IF6PI1WdrDk8n1lXkKRsRyZURpkRTsi+/eqiHmAF K4qfWmADDQAcTFc126QzM8NyoSZ8AzCZlqkd5evxIhUgsXlCfvYV0Y+x1lvCsMN7KN3Y=;
To: Madinas@ietf.org
From: Joey S <joeysalazar@article19.org>
Message-ID: <a5bd7d02-9f18-5c0f-a396-2338243bf11a@article19.org>
Date: Thu, 02 Dec 2021 18:11:34 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="ydTsnfmau642rcduAGD2EG9rSzHw7BYBu"
X-Authenticated-As-Hash: 3c8a76879922505f22521320ab57e3bbe25ea7cc
X-Virus-Scanned: by clamav at smarthost1.greenhost.nl
X-Scan-Signature: f0d5e446bfc5bbd6ce781899a390d841
Archived-At: <https://mailarchive.ietf.org/arch/msg/madinas/gNHMaBYK_5UidQEFOTFQN7VM1dc>
Subject: [Madinas] questions on draft-henry-madinas-framework
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: Thu, 02 Dec 2021 17:09:21 -0000
Following up on the IETF 111 session, I would like to request clarification on 2 points regarding 'REQ8 Identify a secure mechanism for the device to notify the network prior to update the MAC address' prior to supporting adoption of draft-henry-madinas-framework;
- what are the expected constrains of such mechanism?
- what is its expected use?
- Is there a risk for this mechanism to become a means for flagging a device using randomized MACs and/or for it to turn into a new type of UUID?
Additionally, reiterating from the 11 session discussion, I oppose the text
'All devices in the home network trust each other. Privacy
within the
Layer 2 domain is not a major concern.'
and look forward to the upcoming changes on the 'Trust Degree'
mapping.
Thank you,
-- Joey Salazar