IETF Logo Mail Archive

Re: [radext] Liaison to government agencies

Behcet Sarikaya <sarikaya2012@gmail.com> Mon, 05 December 2022 16:17 UTC

Return-Path: <sarikaya2012@gmail.com>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6673C1524C3 for <radext@ietfa.amsl.com>; Mon, 5 Dec 2022 08:17:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.844
X-Spam-Level:
X-Spam-Status: No, score=-1.844 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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=gmail.com
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 caZ4yIhtdey3 for <radext@ietfa.amsl.com>; Mon, 5 Dec 2022 08:17:12 -0800 (PST)
Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (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 B2AEFC1524C1 for <radext@ietf.org>; Mon, 5 Dec 2022 08:17:12 -0800 (PST)
Received: by mail-wr1-x42a.google.com with SMTP id q7so19377754wrr.8 for <radext@ietf.org>; Mon, 05 Dec 2022 08:17:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=or5v5OEfTTzzx3eDnUsTObnlmqIKNm9d30QfcXP4EMc=; b=kOGbDdL8x49v/IuI2t1GIq8agrRQ/M1VKrdqF+ekKUs5PBO6/twTgpyMqfWwUBuO9C tyT9nDfphWNiDcgolvN+tsfcHlEHmKilzuck/9HqSrvj4iXfXWhZ3VKJOIdMRfhlepdF BDF1ja2NA1IodEIK51Y7z4UCoF5WTJTi/HUW6gFli9Q+UiofoVmgh9hCC2/SNFSOwC4U EP9NEtZUXdoxksy5CgxBKLtTpfQHDWlKNANS19dDvljyXze96acblfPFKYqTmlqlwWtu qxQABvNODsSEVdjtoRth4em41PxwD+rm8QGA2xSIvQ7+QOfD8PlZmiH5jhPoXUu08h/6 g1tg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=or5v5OEfTTzzx3eDnUsTObnlmqIKNm9d30QfcXP4EMc=; b=ryF7d4t5XAVRIdpYNSb2OOdfQq0+XOq7ZflIdztdwZ+urXo5Bv/+oNVnBQezCVmp3c 8UlS9bmndkBvn55XuljmjGXYGNnF3Uo2MoSUWwr6ZKYjQNJsn4chrJfMfQu587pjmu/q /qAaHugl9ouyNe8dJW+F+zMmsWazza2wxBJZiA6lU3HmyINuR7amX9VNW/Gf+00wupeT CuHtEmPajQxnjEA3yICtOkawRvY3NSLta3oVT3Atl9yfMQw5u9iiDCDdmEGz5msOJDR5 fLj2+EdjFDm0FdhowMF2NPEaKt7KB4LGCiYwOktoauvJwGEki3k9NBW7m/PuS4FqwYmo VWoQ==
X-Gm-Message-State: ANoB5pl3ZO9HBpGp5pQoD/sk54q82JeARWVHz2Vq6sOVUFizo9vZ64ZG vZSeQE2gmNg0SMkaBDIqQdYk6XfreNmP4iD/lPJGALyPxTQ=
X-Google-Smtp-Source: AA0mqf5vm38wx/DuepswNdSGgV3XDdrxfh96Gmx769MqUNNi+Bdntx2xBZGBjlIqtX3mKhORqNti0mhcw2V7fJ1qmIM=
X-Received: by 2002:a05:6000:987:b0:22e:4629:d4c0 with SMTP id by7-20020a056000098700b0022e4629d4c0mr41262577wrb.164.1670257030470; Mon, 05 Dec 2022 08:17:10 -0800 (PST)
MIME-Version: 1.0
References: <4ce6d292-bb34-5dd7-7b8b-d43c282658f1@iea-software.com> <329FE6EA-C1E6-4E16-8D0C-A68C32B67FB9@gmail.com> <FC5C81F9-FEB5-4F9C-9A02-36837B7ABC09@deployingradius.com> <CAOW+2dtANzJDbAjmhHiz_m1pkk+SyfHu5uZ_ddp4PPMi17=0-A@mail.gmail.com> <E59F655C-ADC3-465A-BC9E-4445135BFE97@deployingradius.com> <2f8a0921-2e9e-751e-4f5d-42c5c9c3cb8a@dfn.de> <b96210fb-8a59-2606-bb0c-7cf365fb23e0@iea-software.com> <81A7763B-B2AE-4FBE-9A5E-1234C87393AE@deployingradius.com> <CAOW+2dvg2z9e_X0QzB+gnxDRK9wMdZy=S4x1LbsXzfP6AxrwtA@mail.gmail.com> <b036f5fd-60fc-352e-bf91-d832adba2545@cs.tcd.ie> <CAOW+2dvbercDhpHGhud8wbTOzVem+=CZ3qY2cat9Wno6G7VgjQ@mail.gmail.com> <ac383e60-b8b4-f46c-4b3c-4834fc4c827d@cs.tcd.ie> <CAOW+2dvkaHgjMPkA4J4hC2NsC=VqEJFOs2a0WPiP2Y4HQ7ppig@mail.gmail.com> <30e717f9-5d7d-2846-c87d-42b59b7f5b25@cs.tcd.ie> <F6961506-FDDF-4A22-A480-ABF4179A5366@gmail.com> <78B99A3A-A436-41C9-9E05-67CDDF7C80A0@gmail.com> <CAOW+2dtzAZAYr5prKPzQf1XgFXW20_VFSP7FL5FcjLqLmCLqNg@mail.gmail.com>
In-Reply-To: <CAOW+2dtzAZAYr5prKPzQf1XgFXW20_VFSP7FL5FcjLqLmCLqNg@mail.gmail.com>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Mon, 05 Dec 2022 10:16:58 -0600
Message-ID: <CAC8QAcc-rLe-PyDg3nLBSt=0hevCBfDbiz=JU=Tx0QAfO=ofQw@mail.gmail.com>
To: Bernard Aboba <bernard.aboba@gmail.com>
Cc: radext@ietf.org
Content-Type: multipart/alternative; boundary="000000000000fc1e5305ef1704f4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/Tb4vnqcLBnWYzCh4wEoa_bYXUts>
Subject: Re: [radext] Liaison to government agencies
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/radext/>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Dec 2022 16:17:17 -0000

+1



On Thu, Dec 1, 2022 at 9:46 PM Bernard Aboba <bernard.aboba@gmail.com>
wrote:

> Margaret said:
>
> "And., no, I am not suggesting we call anything “FADIUS”.  :-)
>
> [BA]  Actually, it's quite catchy!
>
> In the hallowed tradition of IETF acronyms, FADIUS could stand for
> "F(P)hase out insecure RADIUS!".
>
> Example usage: "Still using RADIUS? Join the FADIUS movement!"
>
> On Thu, Dec 1, 2022 at 12:00 PM Margaret Cullen <mrcullen42@gmail.com>
> wrote:
>
>>
>>
>> On Dec 1, 2022, at 2:58 PM, Margaret Cullen <mrcullen42@gmail.com> wrote:
>>
>>
>>
>> On Nov 23, 2022, at 6:26 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie>
>> wrote:
>> On 23/11/2022 23:06, Bernard Aboba wrote:
>>
>> Stephen said:
>> "Perhaps the charter text you'd like added would say that the WG needs to
>> establish what protocol requirements need to be met for FIPS-140
>> compliance
>> before defining anything?"
>> [BA] That seems like a good way to go about it.
>>
>>
>> Cool. Next step there would be for someone to propose
>> concrete wording for that, then our AD can decide to
>> update the draft charter or not. I can give it a shot
>> tomorrow if that's useful, and if nobody else does it
>> first:-)
>>
>>
>> How about replacing this bullet:
>>
>> - Defining a secure variant of RADIUS which can be used in a FIPS-140
>>   compliant environment.
>>
>> With this:
>>
>> - Determine what protocol requirements need to be met for FIPS-140
>> compliance and deployment, consulting with NIST staff and/or operators of
>> FIPS-140 evironments, as needed.  If those protocol requirements are not
>> met by the current RADIUS specifications, define a secure variant of FADIUS
>> which can be used in a FIPS-140 compliant environment.
>>
>>
>> And., no, I am not suggesting we call anything “FADIUS”.  :-)
>>
>> s/FADIUS/RADIUS
>>
>> Margaret
>>
>>
>> Thoughts?
>> Margaret
>>
>>
>>
>> _______________________________________________
> radext mailing list
> radext@ietf.org
> https://www.ietf.org/mailman/listinfo/radext
>

v2.23.0 | Report a Bug | By Email