IETF Logo Mail Archive

Re: [radext] Control of RFC 3580. Transfer to RADIUS WG possible?

Bernard Aboba <bernard_aboba@hotmail.com> Thu, 08 October 2015 13:05 UTC

Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83E771B3380 for <radext@ietfa.amsl.com>; Thu, 8 Oct 2015 06:05:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.609
X-Spam-Level:
X-Spam-Status: No, score=-2.609 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 6h3Be2RDvhuO for <radext@ietfa.amsl.com>; Thu, 8 Oct 2015 06:05:22 -0700 (PDT)
Received: from BLU004-OMC1S33.hotmail.com (blu004-omc1s33.hotmail.com [65.55.116.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09AAA1B3379 for <radext@ietf.org>; Thu, 8 Oct 2015 06:05:21 -0700 (PDT)
Received: from BLU181-W75 ([65.55.116.8]) by BLU004-OMC1S33.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Thu, 8 Oct 2015 06:05:21 -0700
X-TMN: [omguUIrmVyqIUz0Q7FDQwamb0ddqb5gL]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU181-W757C8D75C28A059CB9589093350@phx.gbl>
Content-Type: multipart/alternative; boundary="_0c7cdac1-ea52-4fb9-bb13-c9a4abd6561c_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "lionel.morand@orange.com" <lionel.morand@orange.com>, Alan DeKok <aland@deployingradius.com>, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Thu, 08 Oct 2015 06:05:20 -0700
Importance: Normal
In-Reply-To: <11393_1444227411_56152953_11393_5293_1_6B7134B31289DC4FAF731D844122B36E01D3D6BC@OPEXCLILM43.corporate.adroot.infra.ftgroup>
References: <CAGnO3dp-=6cODkAgV7R6vjTYWz0BXoODY3kPO37-iJ9ve-407g@mail.gmail.com>, <5310AA34-D3C1-4B12-A691-1DF427904DF1@deployingradius.com>, <CAHbuEH47h2yk19BR11TaOnnZGR_8FnLgnCf7zJUukRP7GJq4sg@mail.gmail.com>, <451E43F5-44DF-4651-8372-49BC90DFEC5A@deployingradius.com>, <11393_1444227411_56152953_11393_5293_1_6B7134B31289DC4FAF731D844122B36E01D3D6BC@OPEXCLILM43.corporate.adroot.infra.ftgroup>
MIME-Version: 1.0
X-OriginalArrivalTime: 08 Oct 2015 13:05:21.0708 (UTC) FILETIME=[FD1D86C0:01D101C9]
Archived-At: <http://mailarchive.ietf.org/arch/msg/radext/lP4FH0TqNCTyBtN9Osxp0pCntmc>
Cc: Nick Lowe <nick.lowe@lugatech.com>, "radext@ietf.org" <radext@ietf.org>
Subject: Re: [radext] Control of RFC 3580. Transfer to RADIUS WG possible?
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 08 Oct 2015 13:05:25 -0000

So far, the issues discussed relate to accounting, which is a relatively minor aspect of RFC 3580.  
Furthermore, the accounting issues relate largely to IEEE 802.11, rather than to IEEE 802.1X, which was the focus of RFC 3580. 
As a result, it is not at all clear to me why it is necessary to transfer control of this document from IEEE 802 to the IETF, let alone why it is necessary to revise it at all. 
If there is a desire to deal with accounting issues relating to IEEE 802.11, why not create a new document focused on that topic, with review by IEEE 802.11?  If necessary, it can update RFC 3580.

v2.23.0 | Report a Bug | By Email