Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-radius-opt-01.txt

Just two questions after a quick reading...

Is there any particular reason for including Framed-Pool instead of 
Framed-IPv6-Pool?
What about Framed-IPv6-Prefix?
Generally, what's the criteria for choosing which attributes to include?

Your draft states:

>     The option-data of OPTION_RADIUS is one or a list of RADIUS
>     attributes received in the Access-Accept message from the RADIUS
>     server.  As the same method in [RFC4014  <http://tools.ietf.org/html/rfc4014>], only the attributes listed
>     in the table below may be included in the OPTION_RADIUS.

RFC 4014 states:

>     To avoid dependencies between the address allocation and other state
>     information between the RADIUS server and the DHCP server, the DHCP
>     relay agent SHOULD include only the attributes in the table below in
>     an instance of the RADIUS Attributes suboption.  The table, based on
>     the analysis inRFC 3580  <http://tools.ietf.org/html/rfc3580>  [8  <http://tools.ietf.org/html/rfc4014#ref-8>], lists attributes that MAY be included:

I'm trying to understand if RFC 4014 refers to DHCPv4 only and if your 
draft refers to DHCPv6 only, and if yes, why a DHCPv4 server should know 
about an IPv6 attribute and vice versa.

--
Tassos

On 29/7/2012 8:02 ??, Leaf yeh wrote:
> Dear DHC folks,
>
> The draft-ietf (ver.-01) & the proposed (OPTION_RADIUS) on the agenda of IETF84 DHC session, is waiting for your review and comments.
>
>
> Best Regards,
> Leaf
>
> PS. (https://datatracker.ietf.org/meeting/84/agenda/dhc/ )
>
>
> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
> Sent: Monday, July 30, 2012 9:58 AM
> To: i-d-announce@ietf.org
> Cc: dhcwg@ietf.org
> Subject: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-radius-opt-01.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>   This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.
>
> 	Title           : RADIUS Option for DHCPv6 Relay Agents on Broadband Access Server
> 	Author(s)       : Leaf Y. Yeh
>                            Mohamed Boucadair
>                            Ted Lemon
> 	Filename        : draft-ietf-dhc-dhcpv6-radius-opt-01.txt
> 	Pages           : 9
> 	Date            : 2012-07-29
>
> Abstract:
>     The DHCPv6 RADIUS option provides a communication mechanism between
>     relay agent and the server.  This mechanism can help the centralized
>     DHCPv6 server to select the right configuration for the client based
>     on the authorization information received from a separate RADIUS
>     server which is not located at the same place of DHCPv6 server in the
>     cases where the NAS acts as DHCPv6 relay agent and RADIUS client
>     simultaneously.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-radius-opt
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-radius-opt-01
>
> A diff from previous version is available at:
> http://tools.ietf.org/rfcdiff?url2=draft-ietf-dhc-dhcpv6-radius-opt-01
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>