1 / 11

presenting for design team Ole Trøan, ot@cisco

IPv6 MHMP (Multi-Homing with Multi-Prefixes) - Status Report - draft-troan-multihoming-without-nat66-01. IETF79 V6OPS WG November 2010. presenting for design team Ole Trøan, ot@cisco.com. 1. Goal. Multiple IPv6 prefixes. IPv6. Internet. Corporate network. Partner networks.

kent
Télécharger la présentation

presenting for design team Ole Trøan, ot@cisco

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. IPv6 MHMP(Multi-Homing with Multi-Prefixes)- Status Report -draft-troan-multihoming-without-nat66-01 IETF79 V6OPS WGNovember 2010 presenting for design team Ole Trøan, ot@cisco.com 1

  2. Goal Multiple IPv6 prefixes IPv6 Internet Corporate network Partner networks • Give host multiple IPv6 prefixes • Belonging to different networks • Host does “The Right Thing” • Source Address Selection • Next-Hop Route Selection • DNS Server Selection • (Identifying Supporting Hosts)

  3. Our proposed items and their discussion results in Maastricht continue discussion in v6ops WG • IPv6 Multiple NSP architecture • draft-troan-ipv6-multihoming-without-ipv6nat-01 July 26, 2010 • O. Troan, D .Wing Cisco Systems, D .Miles Alcatel-lucent,S .Matsushima SOFTBANK TELECOM, T. Okimoto NTT • Address selection policy distribution • draft-ietf-6man-rfc3484-revise-01 Oct 15, 2010 • Things To Be Considered for RFC 3484 Revision • A. Matsumoto, J. Kato, T. Fujisaki NTT • draft-fujisaki-6man-addr-select-opt-00 Jul 8, 2010 • Distributing Address Selection Policy using DHCPv6 • T. Fujisaki, A. Matsumoto NTT, R. Hiromi Intec Netcore • Route information distribution • draft-dec-dhcpv6-route-option-05 Sep 28, 2010 • DHCPv6 Route Option • W. Dec, R. Johnson Cisco Systems, T. Mrugalski Gdansk Univ,A. Matsumoto NTT • DNS selection policy distribution • draft-savolainen-mif-dns-server-selection-04 Sep 17, 2010 • Improved DNS Server Selection for Multi-Homed Nodes • T. Savolainen Nokia, J. Kato NTT adopted to WG item in 6man WG technical individual solutions (1 to 3) continue discussion in 6man WG adopted to chartered item in mif WG

  4. In Beijing • 6man WG on Tuesday • Address selection policy distribution draft-fujisaki-6man-addr-select-opt-00 Jul 8, 2010 adopted to WG item (Thank you!) • mif WG on Thursday • Route information distribution draft-dec-dhcpv6-route-option-05 Sep 28, 2010 • DNS selection policy distribution draft-savolainen-mif-dns-server-selection-04 Sep 17, 2010 New mif charter text including route and DNS issues was already approved. They will be adopted to WG item. • Related works: draft-vandevelde-v6ops-pref-ps-00 draft-hain-ipv6-rpf-icmp-00 draft-wing-v6ops-happy-eyeballs-ipv6-01

  5. Questions? IPv6 MHMP 5

  6. Backup/Reminder Materials Problem: Source Address Selection • Multiple prefixes on one physical interface • Wrong ISP 2001:db8:1000::/36 ISP-A Internet 2001:db8:1000:1::100 2001:db8:8000:1::100 ISP-B 2001:db8:8000::/36 Dropped by ingress filter (RFC2827) 6

  7. Backup/Reminder Materials Problem: Source Address Selection • Multiple prefixes on one physical interface • Disconnected network 2001:db8:a000::1 2001:db8:1000::/36 Internet ISP-A 2001:db8:1000:1::100 2001:db8:8000:1::100 ASP-B 2001:db8:8000::/36 7

  8. Backup/Reminder Materials Problem: Next-Hop Route Selection IPv6 Internet Corporate network Partner network Provide host with routing information of Partner network – so that Address Selection (RFC3484) can choose correct source address. RFC4191 does that (but there is a problem..) 8

  9. Backup/Reminder Materials Problem: DNS Server Selection • DNS Server Selection • Public DNS returns empty answer • Private DNS returns IP address • Solution: host queries proper DNS server • long-existing industry practice Internet Query: cnn.com NSP(Internet) ASP / VPN (myasp.com) Query: myasp.com 9

  10. Problem: Identifying Supporting Hosts Backup/Reminder Materials • Supporting Host: • Chooses proper source address • Accepts next-hop route information • Supports DNS server selection • Network would like to determine: • If ‘supporting host’, give it two prefixes • If ‘non-supporting host’, give it one prefix and NAT66 its traffic will be described in draft-troan-multihoming-without-nat66-01 10

  11. Scope of Our Work Backup/Reminder Materials 11

More Related