IETF Logo Mail Archive

Re: [dhcwg] DHCP interconnected to RADIUS for AAA

Ralph Droms <rdroms@cisco.com> Thu, 13 March 2003 18:34 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 NAA12027; Thu, 13 Mar 2003 13:34:51 -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 h2DIn8O19901; Thu, 13 Mar 2003 13:49:08 -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 h2DImnO19879 for <dhcwg@optimus.ietf.org>; Thu, 13 Mar 2003 13:48:49 -0500
Received: from rtp-core-2.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12005 for <dhcwg@ietf.org>; Thu, 13 Mar 2003 13:33:45 -0500 (EST)
Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79]) by rtp-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h2DIZpvD028532; Thu, 13 Mar 2003 13:35:51 -0500 (EST)
Received: from rdroms-w2k.cisco.com (dhcp-161-44-149-248.cisco.com [161.44.149.248]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id NAA23379; Thu, 13 Mar 2003 13:35:50 -0500 (EST)
Message-Id: <4.3.2.7.2.20030313133433.01fce288@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 13 Mar 2003 13:35:50 -0500
To: Erik Nordmark <Erik.Nordmark@sun.com>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] DHCP interconnected to RADIUS for AAA
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>, "Chen, Weijing" <wchen@tri.sbc.com>
In-Reply-To: <Roam.SIMC.2.0.6.1047415508.1051.nordmark@bebop.france>
References: <"Your message with ID" <3E6E0DDF.260B2394@net.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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>

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

v2.29.0 | Report a Bug | By Email | System Status