[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

To: radiusext@ops.ietf.org
Subject: Re: RADEXT WG last call on RADIUS attributes for IPv6 Access Networks
From: Peter Deacon <peterd@iea-software.com>
Date: Mon, 1 Mar 2010 12:12:20 -0800 (Pacific Standard Time)
In-reply-to: <BLU137-DS10984B808F980DCD000E11933C0@phx.gbl>
References: <BLU137-DS10984B808F980DCD000E11933C0@phx.gbl>
User-agent: Alpine 2.00 (WNT 1167 2008-08-23)

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 adifference between IPv6-Framed-Address and Framed-IPv6-Prefix of /128?


regards,
Peter

Follow-Ups:
- RE: RADEXT WG last call on RADIUS attributes for IPv6 Access Networks
  - From: "Bernard Aboba" <bernard_aboba@hotmail.com>
- Re: RADEXT WG last call on RADIUS attributes for IPv6 Access Networks
  - From: Behcet Sarikaya <behcetsarikaya@yahoo.com>

References:
- RADEXT WG last call on RADIUS attributes for IPv6 Access Networks
  - From: "Bernard Aboba" <bernard_aboba@hotmail.com>

Prev by Date: RADEXT WG last call on RADIUS attributes for IPv6 Access Networks
Next by Date: Re: RADEXT WG last call on RADIUS attributes for IPv6 Access Networks
Previous by thread: RADEXT WG last call on RADIUS attributes for IPv6 Access Networks
Next by thread: Re: RADEXT WG last call on RADIUS attributes for IPv6 Access Networks
Index(es):
- Date
- Thread