[Madinas] About draft-ietf-madinas-use-cases-07 and a potential way forward

CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es> Tue, 20 February 2024 00:03 UTC

Return-Path: <cjbc@it.uc3m.es>
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 5180EC151076 for <madinas@ietfa.amsl.com>; Mon, 19 Feb 2024 16:03:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.005
X-Spam-Level:
X-Spam-Status: No, score=-2.005 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=it.uc3m.es
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rqF0ozUqBVAI for <madinas@ietfa.amsl.com>; Mon, 19 Feb 2024 16:03:21 -0800 (PST)
Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F501C151097 for <madinas@ietf.org>; Mon, 19 Feb 2024 16:03:13 -0800 (PST)
Received: by mail-lj1-x229.google.com with SMTP id 38308e7fff4ca-2d21e2b2245so47036171fa.0 for <madinas@ietf.org>; Mon, 19 Feb 2024 16:03:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=it.uc3m.es; s=google; t=1708387391; x=1708992191; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=Zyusx7iRu9m3mO5aiXMYUIW72L4OZsZZa5o+hAYUoGQ=; b=iIxSXkHP3cG/0UcHHaLvy/mMvuvoG6lEa1xz7FXvAc6J98tSdr1coA77KKLfTJ8tJ9 kziJUgKR66ObofmJ/GJrnpb2VNab4+089thZzq4zXTUKiB4pBY2kv/TNWtj3xc22YDHy DOdgP/r3AMNPuz37knpz4fpwfHKzwLrBaeVnw8awe90P1o+9kVV18QUPJws4Gl38Qm4y hkmu7RPP+9gDTRQZc14bCbTN5LWL+GxYzP/RVrnbdExtThrUQc5mx7jnbbcXM0tetoxN Km5PrHbKjkVI2D1ExKU4PAaORyTJ9Qb5Gc2iWtND/CevukMXuUEwNvnqTtMagoehU8cL 7LQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708387391; x=1708992191; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Zyusx7iRu9m3mO5aiXMYUIW72L4OZsZZa5o+hAYUoGQ=; b=jZLdjAZl2vuHUX13wjtE1mOAOSvyFav0zSys5BHHWKASklHsfUe/85e4/3cUMRI/RR qkZVMI7FsJUMq4/txMSOpsC7LytoeGGboQ8dPnVQPeXPM6w5Y3VetKdhLRovDINJU3Cr wKeBECPZxgw0R4TK11SV6qJuY0BD0GI3QWlkqc1orK7ISI/GJ8IA72gtUJR0tC0DfUMQ R/FxoCBxJzAwu7piLj+5kKcdpmmJcFOs5tOiaZj3OxOLaPu//SOiODSkaDkGKQ3Xetxc EtPdSlj3evH8wYPXcNQlalMcwgRur7Xh8NdEFF7/SL0MZ6kpuf66WLyC5aXq0+zwadbI rXeQ==
X-Gm-Message-State: AOJu0YyWWyq9R7XzcY+C/kInk540OjE97oDOtAxX9f79wnxKcCXUOg5p AoUs8z8ijNUvXAd9Fcfa0ya+pvu9qga3DGgjeeZ4lbXvju6+tmsXdePgfe51bq3n6i+1QmRa32T 0g5QPEmKzSDThNLIjwW+tNxGXahMhxIwKJmITF0QiD1h7eJt2MsAcxQ==
X-Google-Smtp-Source: AGHT+IGyPhxJkOkBze7JFD5lDnFIfXPCSaWQPTcCQgx6xVtGXlHuXPJYkjayzlDLMU8ye0aSV13DCONieWT1s8dhlEk=
X-Received: by 2002:a2e:bb88:0:b0:2d2:317a:4e51 with SMTP id y8-20020a2ebb88000000b002d2317a4e51mr3398599lje.19.1708387391037; Mon, 19 Feb 2024 16:03:11 -0800 (PST)
MIME-Version: 1.0
From: CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es>
Date: Tue, 20 Feb 2024 01:02:55 +0100
Message-ID: <CALypLp_VGY57YH+6tfth39fRmg1sBJpPvAR_KhpjC6UxnZYHpg@mail.gmail.com>
To: madinas@ietf.org
Content-Type: multipart/alternative; boundary="00000000000095341b0611c4ef45"
Archived-At: <https://mailarchive.ietf.org/arch/msg/madinas/14gb1jVCZTkFrVRdwQSrTfw6uZ0>
Subject: [Madinas] About draft-ietf-madinas-use-cases-07 and a potential way forward
X-BeenThere: madinas@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 20 Feb 2024 00:03:26 -0000

Hi,

I've checked one more time draft-ietf-madinas-use-cases-07, and I'd like to
make a proposal to move forward with the document.

I think the document is valuable, and therefore should be published (as the
WG is chartered to do). My personal opinion is that we should remove the
requirements section of the draft, making it less formal (I believe the WG
will probably not recharter to do any protocol work, and therefore there is
no need for "formal" requirements).

Additionally, since it also seems that the WG will not work on the BCP
document that we were originally chartered to do, I think that we can bring
back the text on existing solutions (802.1X, OpenRoaming, etc.) to an
annex, and perhaps refer to the other WBA/OpenRoaming draft(s). I found
this text quite informational.

I'd appreciate feedback from the WG, to help the draft authors
understand what changes are needed in the next revision.

Thanks!

Carlos

-- 
CARLOS J. BERNARDOS https://www.it.uc3m.es/cjbc/
Universidad Carlos III de Madrid
RTS/CTS podcast: https://podcasters.spotify.com/pod/show/rts-cts
YouTube channel: https://www.youtube.com/CacharREDando/