IETF Logo Mail Archive

Re: [radext] Start of Call for Adoption for draft-winter-radext-populating-eapidentity-01

Sam Hartman <hartmans@painless-security.com> Tue, 31 March 2015 17:35 UTC

Return-Path: <hartmans@painless-security.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 9531A1A1BF3 for <radext@ietfa.amsl.com>; Tue, 31 Mar 2015 10:35:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 koNf6RrMJRyl for <radext@ietfa.amsl.com>; Tue, 31 Mar 2015 10:35:33 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAF221A1B5D for <radext@ietf.org>; Tue, 31 Mar 2015 10:35:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id B25DD2068F; Tue, 31 Mar 2015 13:33:06 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Z_hp3yQrrv2; Tue, 31 Mar 2015 13:33:06 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Tue, 31 Mar 2015 13:33:06 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 143C681821; Tue, 31 Mar 2015 13:35:02 -0400 (EDT)
From: Sam Hartman <hartmans@painless-security.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>
References: <11856_1427820628_551AD054_11856_4576_1_6B7134B31289DC4FAF731D844122B36EEF6888@PEXCVZYM13.corporate.adroot.infra.ftgroup> <tsllhid84gm.fsf@mit.edu> <BLU181-W6B49664DD504DDAF5CC9F93F40@phx.gbl>
Date: Tue, 31 Mar 2015 13:35:02 -0400
In-Reply-To: <BLU181-W6B49664DD504DDAF5CC9F93F40@phx.gbl> (Bernard Aboba's message of "Tue, 31 Mar 2015 10:30:14 -0700")
Message-ID: <tslego583zt.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <http://mailarchive.ietf.org/arch/msg/radext/xMypukakd6ruAmY96162hnan2hM>
Cc: "radext@ietf.org" <radext@ietf.org>, "radext-chairs@tools.ietf.org" <radext-chairs@tools.ietf.org>, "lionel.morand@orange.com" <lionel.morand@orange.com>
Subject: Re: [radext] Start of Call for Adoption for draft-winter-radext-populating-eapidentity-01
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: <http://www.ietf.org/mail-archive/web/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: Tue, 31 Mar 2015 17:35:34 -0000

>>>>> "Bernard" == Bernard Aboba <bernard_aboba@hotmail.com> writes:

    Bernard>    I agree that this work is important.  However, because
    Bernard> it represents an update of RFC 3748, and the RADEXT WG is
    Bernard> not chartered to handle EAP maintenance, I do not believe
    Bernard> it belongs in this WG.

We're in the middle of doing rechartering of the WG.  It's quite clear
that should we and the IESG choose we can charter this item without
bringing EAP maintinance into this group.

I'd be much more interested in thinking about whether we'll do a good
job with the document and whether there's a better place to send it than
an argument about the current text of the charter.
The charter can be changed.

--Sam

v2.23.0 | Report a Bug | By Email