1 / 8

Local IPv6 Networking March 2000 Adelaide IETF

This document discusses advancements in local IPv6 networking, focusing on autoconfiguration and service discovery mechanisms that work effectively both when connected and disconnected from the Internet. It addresses the limitations of traditional IPv6 in discovering nodes and services without prior configuration, proposing local mechanisms that facilitate automatic discovery of devices like printers and servers. Simple naming conventions for local devices are introduced, along with multicast communication methods. The text highlights the importance of DNS server advertisements for managing local services and resolving names seamlessly within a network.

hien
Télécharger la présentation

Local IPv6 Networking March 2000 Adelaide IETF

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. Local IPv6 NetworkingMarch 2000Adelaide IETF Bob Hinden / Nokia

  2. Introduction • IPv6 • Autoconfiguration works great with Routers • Supports Address related functions • Does not support Names or Services • Address Scoping and Address Selection • IPv6 missing mechanisms to discover nodes and services without configuration or server • Need Local Mechanisms that work • Disconnected from Internet, and/or • Connected to Internet • Simple, Reliable, Automatic

  3. Disconnected Service • Services Discoverable and Reachable without Router or Server • No configuration required • Used when site is disconnected and connected • Smooth transition • Some services are only local

  4. Disconnected Mechanisms • I am "name” Advertisement • Simple default names for service nodes • HP XYZ.1 Printer, Sony XYZ Projector, etc. • <Manufacturer> < Model #> < Type> • User can also configure local names • Send when booting up and periodically (~1 min). • Pick time that is less that node boot time but not too often • Send to All Nodes Multicast Address Site-Scope • Who is "name” • Owner responds w/ "I am name” message

  5. Mechanisms (continued) • Simple "chooser" type of application that shows user what names are available • Filter on some set of types • Printers, file server, etc. • Investigate using existing assignment of standard service types • From service location protocol?

  6. Connected Service • New Router Advertisement option (DNS server option) w/ • Address of DNS server(s) • Default top level domain for link • Ordered list of domains to query for unqualified names • RA Option for scope value to send “I am “name” ” advertisements • Allows site to control range of disconnected mechanisms

  7. How to Resolve Local / Global Names • Define new top level virtual domain • .local (or .private, .invisible, etc.) • Use “DNS server” router advertisement to advertise ".local” as first domain to query • To resolve fully qualified domain names • foo.local uses disconnected mechanisms • foo.* goes to DNS server • To resolve unqualified Domain Names • First try disconnected mechanisms • Then try default global domain and other domains to search • Hidden from application by building into host resolver

  8. Issues • What default scope for advertisements? • Link-Scope, Link < Scope < Site, Site-Scope? • DNS Advertisement • Part of ND Router Advertisement, or • Advertisement sent by DNS server • Security issues? • Relationship to Service Location Protocol?

More Related