1 / 50

Broadband Forum Focus: IPv6 Home Network

Broadband Forum Focus: IPv6 Home Network. David Miles david.miles@alcatel-lucent.com. The views in this presentation do not represent the opinion of the Broadband Forum or its members. All document are Work In Progress. Disclaimer. 1. What is the Broadband Forum?.

jirair
Download Presentation

Broadband Forum Focus: IPv6 Home Network

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Broadband ForumFocus: IPv6 Home Network David Milesdavid.miles@alcatel-lucent.com

  2. The views in this presentation do notrepresent the opinion of the Broadband Forumor its members. All document are Work In Progress. Disclaimer

  3. 1 What is theBroadband Forum?

  4. The Broadband Forum Vision Develop the full potential of broadband around the world. Mission The Broadband Forum is a worldwide organization committed to rapidly creating specifications for communication service providers and vendors that - Accelerate the development and deployment of broadband networks, Foster successful interoperability, Manage and deliver advanced IP services to the customer. http://www.broadband-forum.org/about/mission.php Forum History The Broadband Forum is a global consortium of nearly 200 leading industry players covering telecommunications, equipment, computing, networking and service provider companies. Established in 1994, originally as the ADSL Forum and later the DSL Forum, the Broadband Forum continues its drive for a global mass market for broadband, to deliver the benefits of this technology to end users around the world over existing copper telephone wire infrastructures. http://www.broadband-forum.org/about/forumhistory.php

  5. 2 IPv6 for Consumer Deployment Options

  6. Native IPv6 IPv6HomeNetwork IPv6Internet IPv6Gateway

  7. Softwires from Client in the Home Network IPv6HomeNetwork IPv4Internet IPv6Internet L2TP Tunnel DSL Router(Existing) Softwire Client SoftwireConcentrator

  8. Native IPv6 using L2TP IPv6HomeNetwork IPv6Internet L2TP PPPoA IPv6Gateway LAC IPv6 LNS

  9. Host Access using PPPoE IPv6Internet L2TP PPPoE Bridge LAC IPv6 LNS

  10. Host Access using Softwires IPv4Internet IPv6Internet L2TP Tunnel PPPoE IPv4 Router SoftwireConcentrator

  11. 3 IPv6 for ConsumerBroadband WT-177 and WT-187

  12. Routing Home Network Internet Subnet A Subnet B NAT Function TCP UDP UDP TCP IPoE IWF IPv4 IPv4 IPv4 IPv4 802.1ad Ethernet 802.1ad Ethernet Ethernet Ethernet Ethernet RFC 2684 ATM 802.3 PHY 802.3 PHY DSL Routing IPoE IWF IPv6 IPv6 IPv6 802.1ad Ethernet 802.1ad Ethernet Ethernet Ethernet Ethernet RFC 2684 ATM 802.3 PHY 802.3 PHY DSL

  13. Routed Gateway with PPPoE WAN (1) Subnet A Subnet B Routed Gateway BNG RADIUS PPPoEPADI – PADO – PADR - PADS PPP LCP ConfReqConfReq: MRU, Magic Number PPP LCP ConfReqConfReq: MRU, Magic Number, Auth=PAP PPP LCP ConfAckConfReq: MRU, Magic Number, Auth=PAP PPP LCP ConfAckConfReq: MRU, Magic Number PAP Authenticate-RequestUsername (Peer-ID)+ Password RADIUS Access-RequestUser-Name, Password, Service-Name VSAService-Type=Framed, Framed-Protocol=PPP RADIUS Access-AcceptDelegated-IPv6-Prefix, IPv6-DNS, (IPv6-Address/Framed-IPv6-Pool)

  14. Routed Gateway with PPPoE WAN (2) Subnet A Subnet B Routed Gateway BNG RADIUS PAP Authenticate-Ack PPPPhase IPv6CP ConfReqInterface-Id= 64-bit Interface ID/Client IPv6CP ConfAck Interface-Id= 64-bit Interface ID/Client IPv6CP ConfReq Interface-Id= 64-bit Interface ID/BNG IPv6CP ConfAckInterface-Id= 64-bit Interface ID/Client RADIUS Accounting-RequestStart, User-Name, Service-Name VSAService-Type=Framed, Framed-Protocol=PPP

  15. Routed Gateway with PPPoE WAN (3) Subnet A Subnet B Routed Gateway BNG RADIUS Multicast Router AdvertisementNumbered: M=1,O=0, No PIOUn-numbered: M=0, O=1, No PIO DHCPv6 SOLICITIA_PD-Option, (IA_NA-Option), DNS-Servers Option DHCPv6Phase DHCPv6 ADVERTISEIA_PD-Option + Prefix, (IA_NA) DHCPv6 REQUESTIA_PD-Option, (IA_NA-Option), DNS-Servers Option DHCPv6 REPLYIA_PD-Option + Prefix, (IA_NA)

  16. Routed Gateway with Ethernet WAN (1) Subnet A Subnet B Routed Gateway BNG RADIUS Multicast Router AdvertisementNumbered: M=1,O=0, No PIOUn-numbered: M=0, O=1, No PIO DHCPv6 SOLICITIA_PD-Option, (IA_NA-Option), DNS-Servers Option DHCPv6Phase RADIUS Access-RequestUser-Name, Password, Service-Name VSAService-Type=Framed RADIUS Access-AcceptDelegated-IPv6-Prefix, IPv6-DNS, (IPv6-Address/Framed-IPv6-Pool) DHCPv6 ADVERTISEIA_PD-Option + Prefix, (IA_NA) DHCPv6 REQUESTIA_PD-Option, (IA_NA-Option), DNS-Servers Option DHCPv6 REPLYIA_PD-Option + Prefix, (IA_NA)

  17. Bridged Home with PPPoE Host Internet IPv4 PPPoE Bridge IPv4 802.1ad Ethernet 802.1ad Ethernet Ethernet Ethernet RFC 2684 ATM 802.3 PHY 802.3 PHY DSL IPv6 PPPoE Bridge IPv6 802.1ad Ethernet 802.1ad Ethernet Ethernet Ethernet RFC 2684 ATM 802.3 PHY 802.3 PHY DSL

  18. Bridged Home with PPPoE Host (1) PPPoEClient Bridge BNG RADIUS PPPoEPADI – PADO – PADR - PADS PPP LCP ConfReqConfReq: MRU, Magic Number PPP LCP ConfReqConfReq: MRU, Magic Number, Auth=PAP PPP LCP ConfAckConfReq: MRU, Magic Number, Auth=PAP PPP LCP ConfAckConfReq: MRU, Magic Number PAP Authenticate-RequestUsername (Peer-ID)+ Password RADIUS Access-RequestUser-Name, Password, Service-Name VSAService-Type=Framed, Framed-Protocol=PPP RADIUS Access-AcceptIPv6-DNS, Framed-IPv6-Prefix

  19. Bridged Home with PPPoE Host (2) PPPoEClient Bridge BNG RADIUS PPPPhase PAP Authenticate-Ack IPv6CP ConfReqInterface-Id= 64-bit Interface ID/Client IPv6CP ConfAck Interface-Id= 64-bit Interface ID/Client IPv6CP ConfReq Interface-Id= 64-bit Interface ID/BNG IPv6CP ConfAckInterface-Id= 64-bit Interface ID/Client RADIUS Accounting-RequestStart, User-Name, Service-Name VSAService-Type=Framed, Framed-Protocol=PPP

  20. Bridged Home with PPPoE Host (3) PPPoEClient Bridge BNG RADIUS Anti-SpoofingInstalled Multicast Router AdvertisementM=0, O=1Prefix Information Option: from Framed-IPv6-Prefix OptionalDHCPv6StatelessPhase DHCPv6 INFORMATION-REQUESTDNS-Servers Option DHCPv6 REPLYDNS-Servers Option

  21. 4 Prefix Size Broadband Subscribers

  22. IPv4 and IPv6 Routing Gateways Internet NAT Function TCP UDP UDP TCP IPoE IWF IPv4 IPv4 IPv4 IPv4 802.1ad Ethernet 802.1ad Ethernet Ethernet Ethernet Ethernet RFC 2684 ATM 802.3 PHY 802.3 PHY DSL Routing IPoE IWF IPv6 IPv6 IPv6 802.1ad Ethernet 802.1ad Ethernet Ethernet Ethernet Ethernet RFC 2684 ATM 802.3 PHY 802.3 PHY DSL

  23. IPv4 and IPv6 Routing Gateways Internet NAT Function Network Address TranslationCustomer-selected addresses on LAN TCP UDP UDP TCP IPoE IWF IPv4 IPv4 IPv4 IPv4 802.1ad Ethernet 802.1ad Ethernet Ethernet Ethernet Ethernet RFC 2684 ATM 802.3 PHY 802.3 PHY DSL IPv6 RoutedProvider-assigned addresses on the LAN Routing IPoE IWF IPv6 IPv6 IPv6 802.1ad Ethernet 802.1ad Ethernet Ethernet Ethernet Ethernet RFC 2684 ATM 802.3 PHY 802.3 PHY DSL

  24. IPv6 Prefix Delegation • Allows the routing gateway to receive a range of IPv6 addresses (a prefix) that are valid for that subscriber. The gateway must manage the assignment of individual addresses to hosts outside the scope of Prefix Delegation. BNG RoutingGateway DHCPv6 SolicitIA_PD Option DHCPv6 AdvertiseIA_PD: Prefix Option: <prefix> DHCPv6 Request IA_PD: Prefix Option: <prefix> DHCPv6 ReplyIA_PD: Prefix Option: <prefix>

  25. Contents of the Prefix Delegation Option 0 16 32 Option IA_PD option-length IAID Timer 1 Timer 2 Option IAPREFIX option-length Preferred Lifetime Valid Lifetime prefix-length IPv6 Prefix IPv6 Prefix

  26. Contents of the Prefix Delegation Option 0 16 32 Option IA_PD option-length IAID Contact the delegating router at this time to extend Contact _any_ delegating router at this time to extend Option IAPREFIX option-length Preferred Lifetime of addresses derived from this prefix Valid Lifetime of addresses derived from this prefix prefix-length IPv6 Prefix IPv6 Prefix

  27. How Small? • If Stateless Address Auto-Configuration (SLAAC) is to be supported, the prefix-length of any IPv6 link must be exactly 64-bits • ::/64 • RFC 4862:“If the sum of the prefix length [in the PIO] and the interface identifier length is not equal to 128 bits, the Prefix Information option MUST be ignored” • RFC 2464: IPv6 over EthernetThe Interface Identifier is 64-bits and is based on the EUI-64 format.

  28. How Big? Single Subnet Internet Subnet A Two Subnets Internet Subnet A Subnet B Cascading Routers Internet Subnet A Subnet C Subnet B

  29. The views • http://www.apnic.net/policy/ipv6-guidelines.html • An LIR can assign a /64 to /48 to an end site customer network based on their requirements. The following guidelines may be useful: • /64 where it is known that only one subnet is required. • /56 for small sites where it is expected only a few subnets will be required within the next two years. Subscribers can receive a /56 when connecting through on-demand or always-on connections such as small office and home office enterprises. • /48 for larger sites, or if an end site is expected to grow into a large network. • An LIR must submit a second opinion request to APNIC if it plans to assign more than a /48 to a single end site • Assignments for networks equal to or greater than /48 must be registered.

  30. What is the impact? • Using a prefix longer than a ::/56 does not affect your allocation. HD-Ratio is calculated against ::/56 prefixes. • The use of a shorter prefix does not increase the number of routes or FIB entries in Service Provider infrastructure. • In the minimum /32 LIR allocation, there are: • 16,777,216 ::/56 • 6,183,533 ::/56 at HD-Ratio 0.94

  31. How many subnets is enough? • With cascading routers we must support at least two subnets. • The closest nibble is a /60, with 16 subnets. • WT-187 and WT-177 Requirement: • R-xx: A minimum delegation of a ::/60 to a Routing Gateway. • R-xx: A recommended delegation of a ::/56 to a Routing Gateway.

  32. 5 IPv6 Addressing Importance of Persistent Addresses

  33. Impact of Valid & Preferred Lifetimes 0:00:00 Host links can come up before the broadband connection.

  34. Impact of Valid & Preferred Lifetimes 0:01:00 DHCPv6 Prefix Delegation T1: 30 min T2: 48 min IA_PD: 2001:db8:1::/64Preferred: 3600 Valid: 43200 Router Advertisement PIO: 2001:db8:1::/64Preferred: 3600 Valid: 43200Autonomous, On-Link DHCPv6-PD options used in Router Advertisements.

  35. Impact of Valid & Preferred Lifetimes 0:01:30 Lifetimes are tracked by the Host and decremented.

  36. Impact of Valid & Preferred Lifetimes 0:01:35 Router Advertisement PIO: 2001:db8:1::/64Preferred: 3565 Valid: 43165Autonomous, On-Link And the RG also tracks lifetimes so that any RAare accurate.

  37. Impact of Valid & Preferred Lifetimes 0:01:40 Router AdvertisementROUTER LIFETIME: 0 PIO: 2001:db8:1::/64Preferred: 3560 Valid: 43160Autonomous, On-Link If the Broadband Link goes down, set Router Lifetimeto zero (0) so that the RG is not used as default router.

  38. Impact of Valid & Preferred Lifetimes 0:02:40 Router AdvertisementROUTER LIFETIME: 0 PIO: 2001:db8:1::/64Preferred: 3500 Valid: 43100Autonomous, On-Link Prefixes are still valid even when link is down.RA continue to be sent.

  39. Impact of Valid & Preferred Lifetimes 1:02:40

  40. Impact of Valid & Preferred Lifetimes 1:05:00 DHCPv6 Prefix Delegation T1: 30 min T2: 48 min IA_PD: 2001:db8:1::/64Preferred: 3600 Valid: 43200 Router Advertisement PIO: 2001:db8:1::/64Preferred: 3600 Valid: 43200Autonomous, On-Link Whenever DHCPv6-PD provides the RG new lifetimesthese are reflected in the RA

  41. Impact of Changing Prefixes 1:06:00

  42. Impact of Changing Prefixes 1:07:00 DHCPv6 Prefix Delegation T1: 30 min T2: 48 min IA_PD: 2001:db8:2::/64Preferred: 3600 Valid: 43200 Router Advertisement PIO: 2001:db8:2::/64Preferred: 3600 Valid: 43200Autonomous, On-Link Source Address Selection is NOT deterministic, however theBroadband Network Gateway is only expecting trafficsourced from 2001:db8:2::/64

  43. Better Behaviour 1:07:00 DHCPv6 Prefix Delegation T1: 30 min T2: 48 min IA_PD: 2001:db8:2::/64Preferred: 3600 Valid: 43200 On-Link Router Advertisement PIO: 2001:db8:1::/64PREFERRED: 0 Valid: 43080Autonomous, On-Link PIO: 2001:db8:2::/64Preferred: 3600 Valid: 43200Autonomous, On-Link Instead, let us Deprecate the old addresses. We cannot invalidate because of DoS-protection rules.

  44. Better Behaviour 1:07:30 Router Advertisement PIO: 2001:db8:2::/64Preferred: 3540 Valid: 43140Autonomous, On-Link Source Address Selection will now prefer the new address space.

  45. 6 IPv6 Addressing Minimising Prefix Changes

  46. Address Hierarchy @ BNG – Day 2 Route table------------------------------------------------------------2001:db8::/39 aggregate lo02001:db8:0:0::/56 subscriber eth12001:db8:0:100::/56 subscriber eth1... 2001:db8:0:0::/56 2001:db8:0:100::/56 2001:db8:0:200::/56 2001:db8:0:300::/56 2001:d8b::/39 2001:db8:0:400::/56 Route table------------------------------------------------------------2001:db8:200:/39 aggregate lo02001:db8:200:0::/56 subscriber eth12001:db8:200:100::/56 subscriber eth1... 2001:db8:0:500::/56 2001:db8:200:0::/56 2001:db8:200:100::/56 2001:db8:200:200::/56 2001:d8b:200:/39

  47. Address Hierarchy @ DSLAM – Day 1 2001:db8:0:0::/56 Route table------------------------------------------------------------2001:db8::/46 aggregate lo02001:db8:4::/46 aggregate lo02001:db8:8::/46 aggregate lo02001:db8:0:0::/56 subscriber eth12001:db8:0:100::/56 subscriber eth1... 2001:db8:0:100::/56 2001:db8:0:200::/56 2001:d8b::/46 2001:db8:4:0::/56 2001:db8:4:100::/56 2001:db8:4:200::/56 2001:d8b:4::/46 2001:db8:8:0::/56 2001:db8:8:100::/56 2001:db8:8:200::/56 2001:d8b:8::/46

  48. Address Hierarchy @ DSLAM – Day 2 Route table------------------------------------------------------------2001:db8::/46 aggregate lo02001:db8:4::/46 aggregate lo02001:db8:0:0::/56 subscriber eth12001:db8:0:100::/56 subscriber eth1... 2001:db8:0:0::/56 2001:db8:0:100::/56 2001:db8:0:200::/56 2001:d8b::/46 2001:db8:4:0::/56 2001:db8:4:100::/56 Route table------------------------------------------------------------2001:db8:8:/46 aggregate lo02001:db8:8:0::/56 subscriber eth12001:db8:8:100::/56 subscriber eth1... 2001:db8:4:200::/56 2001:d8b:4::/46 2001:db8:8:0::/56 2001:db8:8:100::/56 2001:db8:8:200::/56 2001:d8b:8::/46

  49. Address Hierarchy • Prefix Delegation • The BNG should aggregate subscriber /56 prefixes into supernets within the service provider domain. The aim is to reduce the size of the service provider routing table. • Logically group prefixes by the largest logical device (switch, DSLAM, etc) that is persistent regardless of normal network rearrangement. Recommend: Each access node should be represented by its own unique prefix-pool when DHCPv6 PD is in use

  50. Thank You www.alcatel-lucent.com

More Related