1 / 17

User Network Interface - auto-configuration mechanism -

This study focuses on the auto-configuration mechanism for ISP-to-customer network interfaces in IPv6. The goal is to define the minimum requirements for IPv6 access services for non-technical customers. The study covers various interfaces and addresses in the network and addresses challenges in the IPv6 world.

dfouts
Télécharger la présentation

User Network Interface - auto-configuration mechanism -

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. User Network Interface- auto-configuration mechanism - Toshi Yamasaki IPv6 Operation Study Group / NTT Communications

  2. Goal • IPv6 access services for everyone (non-technical customers) in 2002 • ex) DSL, FTTH, D-up, CATV, etc. • Make a rough consensus for “what are minimum requirements for ISP-to-Customer auto-configuration?” • No absolute conclusion, but need a current conclusion to start businesses

  3. Scope Host Host Host Service Service Service • ISP-to-Customer Environment • PE-to-CPE Interface • CPE-to-Host Interface ISP Here Here POI PE CPE access media LAN

  4. Auto-configured Parameters • Site Address Prefix / Host Address • DNS Cache Address

  5. Typical model in IPv4 world Host Host Host Service Service Service POI ISP PE CPE access media LAN Primary DNS Secondary DNS Physical NAS PSTN/DSL L3Router Ethernet PC Scope of Address Global Global Private Private Site Address / Host Address } IPCP DHCP DNS Cache Address

  6. Challenges for IPv6 world... • universality • should be applicable for various medias • shouldn’t assume PPP(IPv6CP) • “third-party-serverless” auto-configuration • should be auto-configured by the service entity itself, only when it is alive • Site-Prefix by who provide the routing service for the prefix, DNS Cache Address by who provide DNS Cache service • non-PC • Hosts are not always powerful • no heavy requirements

  7. Our Current Conclusion...

  8. Logical model subnet Host Host subnet Host Host subnet Host Host Service Service Service POI PE L3R model CPE subnet ISP POI CPE subnet MSR model

  9. Site model Host Host Host Host subnet subnet Host Host Host Host subnet subnet Host Host Host Host subnet subnet Service Service Service Customer site • SHOULD-BE model is Model-A • Usually ISP doesn’t assign nor route site-local addresses, especially well-known addresses, to customer nodes CPE L3R model-A subnet PE ISP site ISP CPE L3R model-B subnet CPE MSR model-A subnet CPE MSR model-B subnet

  10. Site Prefix / Host Address (L3R) Host subnet Host subnet Host subnet • Standard Status • Draft Standard (RFC2461) • Implementation • - Many! • Alternatives • None PE CPE subnet Scope of Address Link Local Link Local Global Global APD RA Site Address / Host Address • Standard Status • Draft Standard (RFC2462) • Implementation • - Many! • Alternatives • Privacy extension (RFC3041) • DHCPv6 (draft-ietf-dhc-dhcpv6-23.txt ) Stateless • Standard Status • I-D (draft-haberman-ipngwg-auto-prefix-01.txt, -02.txt) • Implementation • - KAME(PE, CPE), YAMAHA(PE, CPE) • Alternatives • Router Renumbering (RFC2894) • a new DHCPv6 option proposed after our last discussion (draft-troan-dhcpv6-opt-prefix-delegation-00.txt )

  11. DNS Cache Address (L3R) Host subnet Host subnet Host subnet • SHOULD-BE model is Model-A • CPE, only the node belongs to both sites, must work as a DNS proxy Service PE CPE subnet ISP site Customer site Model-A • Standard Status • I-D (draft-ietf-ipngwg-dns-discovery-03.txt ) • Implementation • - KAME • Alternatives • Level2 (draft-ietf-ipngwg-dns-discovery-03.txt ) • DHCPv6 information request (draft-ietf-dhc-dhcpv6-23.txt ) Level1 Compliance Level1 Proxy ISP site Level1 Compliance Model-B

  12. Site Prefix / Host Address (MSR) Host subnet Host subnet Host subnet • Standard Status • Draft Standard (RFC2461) • Implementation • - Many! • Alternatives • None PE CPE subnet Scope of Address Link Local Global RA Site Address / Host Address • Standard Status • Draft Standard (RFC2462) • Implementation • - Many! • Alternatives • Privacy extension (RFC3041) • DHCPv6 (draft-ietf-dhc-dhcpv6-23.txt ) Stateless

  13. DNS Cache Address (MSR) Host Host Host • SHOULD-BE model is Model-A • PE, only the node belongs to both sites, must work as a DNS proxy Service PE CPE subnet Customer site ISP site Model-A • Standard Status • I-D (draft-ietf-ipngwg-dns-discovery-03.txt ) • Implementation • - KAME • Alternatives • Level2 (draft-ietf-ipngwg-dns-discovery-03.txt ) • DHCPv6 information request (draft-ietf-dhc-dhcpv6-23.txt ) Level1 Level1 Compliance Proxy ISP site Level1 Compliance Model-B

  14. TBD • Name Registration Mechanism • Monitoring Issues • Security Issues

  15. backups

  16. Level1 Compliance Details Level1 response dest : global unicast src : global or site-local unicast response srct : site-local dest : global Level1 query dest : site-local anycast src : global unicast level1 query dest : site-local src : global POI model-B CPE Host ISP DNS Cache PE Server POI X CPE Host model-A Level1 response (failure) dest : site-local(Customer) unicast NO ROUTE! src : global or site-local(ISP) unicast Level1 query dest : site-local(ISP) anycast src : site-local(Customer) unicast

  17. DNS Cache at Customer site Level1 query dest : site-local anycast src : global or site-local unicast DNS Cache Level1 response dest : global or site-local unicast srct : global or site-local unicast POI model-B CPE Host ISP PE Server POI CPE Host model-A

More Related