IPv6 RADIUS attributes for IPv6 access networks draft-lourdelet-radext-ipv6-access-02 Glen Zorn, Benoit Lourdelet Wojciech Dec, Behcet Sarikaya, David Miles Radext WG group Pre IETF 77 Interim Call, 02/23/2008 Issues (with previous drafts) • Issue 317: Datatypes and naming • Issue 321: Relationship to IPv6 address allocation models • Issue 322: Unclear Service Definition • In general: Deployment/use context of the proposed extensions Deployment context: Multi-edge broadband access Radius AAA BNG BNG Embedded DHCPv6 Server BNG Routed RG Ethernet or DSL Access Node BNG Embedded DHCPv6 Server • Defined in Broadband Forum’s TR-101 and follow-on documents • Widely deployed • Dual BNG set-up is optional • When used 2nd BNG is typically application specific eg IPTV. • DHCP server may be standalone • But embedded case is pictured to explain how DHCP applies to this draft Requirements 1. IPv6 DNS resolver address needs to be needs to be configured on a per subscriber basis in AAA and conveyed at authorization • Interface between BNG and CPE can be: – DHCPv6: RFC3646 – Recursive DNS Option – ICMPv6: RFC5006 2. Subscriber CPE’s IPv6 address needs to be fully specified (128 bits) and statefully assigned during AAA and/or passed in accounting info • Interface between BNG and CPE can be: – DHCPv6: RFC3315 3. More specific IP routes towards application systems should be transmitted to the subscriber’s CPE • Interface between BNG and CPE can be: • ICMPv6: RFC4191 • (draft-dec-dhcpv6-route-option. Work in progress) Deployment context: PPP access with authorization + DHCP BNG Radius BNG Embedded AAA Routed RG Ethernet or DSL Access Node DHCPv6 Server PPPoE PPP LCP RADIUS "user1“ Access-Request Line-id RADIUS Framed-Protocol PPP User-Name “user1” Access-Accept Service-Type Framed Internal (Optional) Framed-IPv6- Preconfigured Address API DHCP parameters (Optional) IPv6-DNS-Server- Address PPP IPv6CP (Optional) IPv6-Route- Information ICMPv6 Router Advertisement (with Optional attributes)* DHCPv6 Solicit (Optional attributes)* DHCPv6 Reply* (Optional Attributes)* * A deployment may use one, both or neither. Issues • 317 - Datatypes and naming: • Current draft does not define any new datatypes (all re- used from rfc3162). • “IPv6-Address” name changed to “Framed-IPv6- Address”. • Other attributes removed from the draft • 321, 322 – Usage and address allocation methods • Explained on preceding slides • Attributes do not rely on any exotic “allocation” methods. How to move forward • Adopt as a WG item ? Thank You ! .