[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: <peterd@iea-software.com>
Subject: RE: RADEXT WG last call on RADIUS attributes for IPv6 Access Networks
From: Bernard Aboba <bernard_aboba@hotmail.com>
Date: Tue, 2 Mar 2010 02:44:27 -0800
Cc: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
In-reply-to: <alpine.WNT.2.00.1003011339340.2788@littlesmurf>
References: <BLU137-DS10984B808F980DCD000E11933C0@phx.gbl> <alpine.WNT.2.00.1003011200180.2316@SMURF> <BLU137-DS37F6470B23B0440097973933C0@phx.gbl>,<alpine.WNT.2.00.1003011339340.2788@littlesmurf>

> DHCPv6 is capable of assignment of both single addresses and prefixes.

Delegation is addressed in RFC 4818.

> If the /128 prefix approach is used should I expect that an IP would be assigned to the end user?

You should not expect a DHCPv6 address to be assigned. On some NASes I wouldn't expect *any* address to be assigned.

References:
- 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: Peter Deacon <peterd@iea-software.com>
- 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: Peter Deacon <peterd@iea-software.com>

Prev by Date: RE: 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: RE: 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