Re: [dhcwg] Publication of draft-droms-agentopt-8021x-00.txt

Bernard Aboba <aboba@internaut.com> Fri, 23 November 2001 06:33 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01323 for <dhcwg-archive@odin.ietf.org>; Fri, 23 Nov 2001 01:33:15 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id BAA22399 for dhcwg-archive@odin.ietf.org; Fri, 23 Nov 2001 01:33:05 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA22032; Fri, 23 Nov 2001 01:27:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA22010 for <dhcwg@optimus.ietf.org>; Fri, 23 Nov 2001 01:27:54 -0500 (EST)
Received: from internaut.com ([64.38.134.99]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00580 for <dhcwg@ietf.org>; Fri, 23 Nov 2001 01:27:51 -0500 (EST)
Received: from localhost (aboba@localhost) by internaut.com (8.9.3/8.9.3) with ESMTP id WAA88772; Thu, 22 Nov 2001 22:17:03 -0800 (PST) (envelope-from aboba@internaut.com)
Date: Thu, 22 Nov 2001 22:17:03 -0800
From: Bernard Aboba <aboba@internaut.com>
To: Haines Wolfe <hainesie@hotmail.com>
cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Publication of draft-droms-agentopt-8021x-00.txt
In-Reply-To: <F50s1tIzmQVuRWCy7rj00002be9@hotmail.com>
Message-ID: <Pine.BSF.4.21.0111222144200.88731-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org

> 802.1 WG focus on PAE itself, and DHC WG focus on the broadband access 
> model. 

Last time I looked, defining mechanisms for broadband Internet access is
*not* within the scope of the DHC WG charter. On the other hand, the IEEE
currently has an Ethernet First Mile (EFM) study group, as well as the
IEEE 802.1X revision group. So I would suggest that you are more likely to
have a fruitful discussion of your proposals by taking them to the IEEE. 

> EAPOL_Start is not needed by NAS, it only tell the PAE to send 
> identity_request message. EAPOL_Logoff should cause the PAE to send radius 
> request of accounting or other attribute, which will be obtained by NAS as a 
> radius proxy. For public access, I think that is enough.

It sounds like you would like to propose changes to the IEEE 802.1X
state machine. Since the IEEE 802.1X revision PAR is now active, that is
the best place to take such proposals. Making such proposals to the DHC 
WG is not likely to generate much forward movement. 



_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
http://www1.ietf.org/mailman/listinfo/dhcwg