RE: RADEXT WG last call on RADIUS attributes for IPv6 Access Networks

["Bernard Aboba" <bernard_aboba@hotmail.com>]

Yes, there is a difference.  Framed-IPv6-Prefix is specifically for use within a Router Advertisement. 
So if the RADIUS server were to send a Framed-IPv6-Prefix of /128 to the NAS, this would be inserted
in the RA by the NAS (which is probably not what you want). 

An IPv6-Framed-Address on the other hand, is for use within the NAS's embedded DHCPv6 server.  

Note that it is possible for a NAS to support *both* stateless autoconfig and DHCPv6, so that both
attributes could be present in the same Access-Accept.    This is yet another reason why distinct
attributes are required -- how else could the NAS figure out which attribute is to be used for what
purpose?

-----Original Message-----
From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] On Behalf Of Peter Deacon
Sent: Monday, March 01, 2010 12:12 PM
To: radiusext@ops.ietf.org
Subject: Re: RADEXT WG last call on RADIUS attributes for IPv6 Access Networks

On Mon, 1 Mar 2010, Bernard Aboba wrote:

> This is an announcement of RADEXT WG last call on âRADIUS attributes for IPv6
> Access Networksâ before sending the document off to the IESG for
> consideration as a Proposed Standard.  A copy of the document is available
> for inspection here:

> http://tools.ietf.org/html/draft-ietf-radext-ipv6-access

3.1.

I'm confused on IPv6-Framed-Address and Framed-IPv6-Prefix from RFC 3162. 
It looks as if both attributes accomplish the same goal.  Is there a 
difference between IPv6-Framed-Address and Framed-IPv6-Prefix of /128?

regards,
Peter


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>