IPv6 New RFCs. LACNIC 29 - Panamá May Jordi Palet

Transcription

1 New RFCs LACNIC 29 - Panamá May 2018 Jordi Palet (jordi.palet@theipcompany.com) -1

2 Happy Eyeballs 2 RFC8305 (see preious LACNOG LT) -2

3 Unique Prefix per Host RFC8273-3

4 RFC8273 RFC8273: Unique Prefix per Host Not a new protocol, so already widely supported Use existing protocols to allow a unique prefix (instead of a unique address from a shared prefix) to be assigned to a host interface Allows improed host isolation and enhances subscriber management on shared network segments, such as Wireless networks, data centres, among others Proides a ery simple mechanism for a single host or interface, to be able to run 24 irtual machines, with their own global address, not requiring to share a single one -4

5 How To First-hop router is a L3 edge router UE connects to the shared-access network and starts configuration with SLAAC RS First-hop router sends solicited RA response ONLY to the requesting UE Instead of using the link-layer multicast address (all-nodes group), using the link-layer unicast address of the requesting UE The solicited RA contains the unique prefix (4) and flags (to indicate if SLAAC andor DHCP should be used, etc.) Prefix from locallycentrally managed pool, aggregate block, Flags, best practices: 4. M-flag = 0 (address not managed with DHCP, 1 for DHCP prefix delegation) O-flag = 1 (DHCP used for other configuration information) A-flag = 1 (UE can configure itself using SLAAC) L-flag = 0 (prefix is not an on-link prefix, eerything sent to the gateway) Periodically unsolicited RAs follow same approach -5

6 Usage Scenarios We are already doing in cellular: 4 per PDP context Prefix sharing with other deices (tethering) Facilitate -only access (and 4-as-a-serice) Allows extending same concept to other scenarios: Hot-Spot WiFi Calling: Secured Voice oer WiFi oer untrusted connection 4 or sec tunnels to the epdg (eoled Packet Data Gateway) Corporate networks Data Center Allows also -only access and 4-as-a-serice Same concept as aboe for WiFi Calling VPN on demand in own network for 4 serices No need for NAT44 (lowers logging costs and fragmentation issues) -

7 Hot-Spot Usage WiFi shared-access L2 network Proide isolation between user deices either due to legal requirements or to aoid potential abuse By using unique prefix per host, deices only can communicate thru the first-hop router Automatically aoids attacks based on link-local ICMP: DAD reply spoofing ND cache exhaustion Malicious redirects Rogue RAs Better scalability and robustness than DAD proxy, forced forwarding, ND snooping, etc. -7

8 Hot-Spot Example AP 1 5 Hot-Spot Proider Router AP n ISP 8 4-8

9 Data Centre Usage How to same as for the Hot-Spot case The UE serer may need multiple addresses from the same unique prefix (VMs, containers), so just need to configure them The first-hop router must be able to handle the presence and use of those -9

10 Data Center Example Serer n Serer 1 Serer n ISP 5 Serer 2 Rack Serer 2 48 Data Center Router Serer Rack n - 10

11 Enterprise Example On-Demand VPN 4 Switch 1 ISP 5 5 Enterprise Router Switch n -o nly 4 N A ly VL n o 4 4 N LA N V A y l L n V -o y l on P I 4 N 4 -only VLA 4 N A VL y l n o 4 N LA V nly o VL AN -o nly VL AN

12 Conclusions RFC8273 Stable and secure -only experience No performance impact Secure host-to-host communication managed by first-hop router Each unique prefix can function as a control-plane anchor point to ensure that each deice receies expected subscriber policy and serice leels Throughput QoS Security Parental control Other alue-added-serices - 12

13 Thanks! Contact: Jordi Palet: 4 addresses needed for your transition? Contact - (reference The Company ) - 13