RE: [dhcwg] DHCP interconnected to RADIUS for AAA

"Chen, Weijing" <wchen@tri.sbc.com> Thu, 13 March 2003 19:37 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14473; Thu, 13 Mar 2003 14:37:04 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DJpaO25081; Thu, 13 Mar 2003 14:51:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DJoNO25001 for <dhcwg@optimus.ietf.org>; Thu, 13 Mar 2003 14:50:23 -0500
Received: from howler.tri.sbc.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14386 for <dhcwg@ietf.org>; Thu, 13 Mar 2003 14:35:08 -0500 (EST)
Received: from sbctri.tri.sbc.com (mayhem-web-dmz.tri.sbc.com [144.60.9.137]) by howler.tri.sbc.com (8.12.8/8.12.5) with ESMTP id h2DJalTq006305; Thu, 13 Mar 2003 13:36:48 -0600 (CST)
Received: from TRIMAIL2.ad.tri.sbc.com (localhost [127.0.0.1]) by sbctri.tri.sbc.com (8.11.6+Sun/8.9.3) with ESMTP id h2DJalr16723; Thu, 13 Mar 2003 13:36:47 -0600 (CST)
Received: by trimail2 with Internet Mail Service (5.5.2653.19) id <GP097W2D>; Thu, 13 Mar 2003 13:36:46 -0600
Message-ID: <905A1C4ABF353F4C8CC16FA9F53DD0D6322812@trimail2>
From: "Chen, Weijing" <wchen@tri.sbc.com>
To: 'Ralph Droms' <rdroms@cisco.com>, Erik Nordmark <Erik.Nordmark@sun.com>
Cc: Prakash Jayaraman <prakash_jayaraman@net.com>, Erik Nordmark <Erik.Nordmark@sun.com>, Shankar Agarwal <shankar_agarwal@net.com>, rbhibbs@pacbell.net, Dhcwg <dhcwg@ietf.org>
Subject: RE: [dhcwg] DHCP interconnected to RADIUS for AAA
Date: Thu, 13 Mar 2003 13:36:45 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>

Apparently I felt the same way after I read the PANA charter and
requirements.  I think this limitation (or assumption if you prefer) will
keep PANA from deployed in real world.  Regardless, we are investigating of
802.1x coupled with DHCP now.


Weijing Chen


-----Original Message-----
From: Ralph Droms [mailto:rdroms@cisco.com] 
Sent: Thursday, March 13, 2003 12:36 PM
To: Erik Nordmark
Cc: Prakash Jayaraman; Erik Nordmark; Shankar Agarwal; rbhibbs@pacbell.net;
Dhcwg; Chen, Weijing
Subject: Re: [dhcwg] DHCP interconnected to RADIUS for AAA

I don't understand how PANA can be used first - the requirements doc says:

    PANA does not perform any address assignment functions
    but MUST only be invoked after the client has a usable
    IP address (e.g., a link-local address in IPv6 or a
    DHCP-learned address in IPv4)

- Ralph

At 09:45 PM 3/11/2003 +0100, Erik Nordmark wrote:
> > Is there work currently in progress on such an alternative? (triggering
a
> > PANA transaction upon a DHCP message from the client or something
similar).
> > Would this be an appropriate forum to start a discussion?
>
>The simplest thing would be to have them operate independently
>e.g. PANA authentication first then DHC address assignment etc.
>That doesn't allow you to assign different addresses for different classes
>of authenticated devices though.
>
>   Erik
>
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/dhcwg
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg