anism and the DHCPv6 one wins, so now it *is* *the* prefix delegation
mechanism.
If you don't support DHCP6 then IPv6 AAA does not have much use in NAS.
=> I don't understand your argument: the IPv6 AAA in NAS is about access
control, its use for IPv6 prefixes is only a convenient
clients
without using DHCP6 server. If you don't support DHCP6 then IPv6 AAA
does not have much use in NAS.
The point is that there's no specification of addressing assignment
for the prefix usign AAA because that address assignment is performed
by DHCPv6 if necessary, or by Statele
you don't support DHCP6 then IPv6 AAA
does not have much use in NAS.
With Regards
Syed Ajim Hussain
Huawei Technologies Co., Ltd.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Sunday, October 16, 2005 9:35 PM
To: [EMAIL PROTECTED]; [
I agree with Francis on this.
John
>In RADIUS you have Framed-IPv6-Prefix for the PPP link itself
>and Delegated-IPv6-Prefix (defined in an I-D) for prefix
>delegation but PPP can't delegate a prefix, you should use
>DHCPv6 for this job.
>
>Regards
>
>[EMAIL PROTECTED]
>
>PS: the DHCPv6 Relay
In RADIUS you have Framed-IPv6-Prefix for the PPP link itself and
Delegated-IPv6-Prefix (defined in an I-D) for prefix delegation but
PPP can't delegate a prefix, you should use DHCPv6 for this job.
Regards
[EMAIL PROTECTED]
PS: the DHCPv6 Relay RADIUS Attribute Option can bind RADIUS on the NAS
Hi All
I have a
question. If you implement RFC 3162 ( RADIUS for IPv6) in NAS , then
how IPv6 prefix pools maintained
Locally or In a RADIUS
server, is useful for providing PPP based services to Clients sitting in access
site, when no
DHCP6 services
are a
