ZERO CONFIGURATION NETWORKING

1
ZERO CONFIGURATION NETWORKING

• PUSPARAJ MOHAPATRA
• SCHOOL OF INFORMATION TECHNOLOGY
• IIT KHARAGPUR

2
TOPICS TO BE COVERED

• Introduction
• Essential network services configuration
• Managing IP host configuration
• Architectural issues of zeroconf
• Status of ongoing work
• Future implication
• Conclusion
• Reference

3
INTRODUCTION

• Todays growing network infrastructure
• Demerits of todays networking
• Zero configuration networking
• --A Boon to Network
• 
  Infrastructure

4
IP CONFIGURATION PARAMETERS

• IP Address
• Subnet mask
• Default router address
• Domain name
• Domain name server

5
IP CONFIGURATION

• Static configuration
• Dynamic configuration
• Automatic configuration
• Figure

6
DESTINATION ADDRESS DISCOVERY

• There are 3 ways
• IP address configuration(self)
• Domain name configuration(DNS)
• Service discovery(DHCP)
• Multicast Address AllocationMADCAP

7
ARCHITECTURAL ISSUES IN ZEROCONF

• Zeroconf constraints are
• Ease of use
• Scalability
• Automatic translation to from configured
  networking
• Secure operation
• Transparency
• Independence

8
ONGOING WORK

• Requirement specification by IETF group
• Zeroconf protocol areas under consideration
• Automatic host configuration
• Service discovery
• Multicast domain name to address resolution
• Automatic multicast address allocation
• Transition to secure operation

9
AUTOMATIC HOST CONFIGURATION

• IPV6 has address auto configuration
• Claim defend protocol is insufficient
• Reclaim will be added
• Link-local address

10
CREATION OF LINK-LOCAL ADDRESS

• Link-local address well known link-local
  prefixinterface identifier
• Interface identifierInterface's link-layer
  address
• Link-local prefixFE800

11
CREATION cont

• Link-local address is created after the following
  events
• Interface is initialized at system startup time
• Interface attaches to a link for the first time
• Interface is reinitiated after a temporary
  interface failure
• Interface becomes enabled by system management
  having been administratively disabled

12
MULTICAST DOMAIN NAME TO ADDRESS RESOLUTION

• Multicast DNS(mdns)
• Claim and defend mechanism
• stub naming service in hosts
• Hosts assign themselves a domain name with
  .local suffix
• Multicast to broadcast address(224.0.0.251)
• Claim defend mechanism applies
• Host can use caches.

13
SERVICE DISCOVERY

• Service allocation protocol(SLP)
• Can use both in IPV4 IPV6
• SLP agent is deployed on each host
• Multicast the message with type of service
  attributes
• 3rd party can also cache this information

14
AUTOMATIC MULTICAST ADDRESS ALLOCATION

• Allows a host to obtain an address allocation for
  a multicast group for the hosts own purposes
• Still in development stage, but there is one
  protocol which will support this
• Zeroconf Multicast allocation protocol
• 
  (ZMAAP)

15
Working of ZMAAP

• Multicast Address Allocation Server (MAAS) A
  node providing multicast address allocation
  services to network clients.
• Mini-MAAS A service providing multicast address
  allocation services to applications running on
  the same host. Mini-MAASs cooperate to provide
  network-wide services in small networks without
  MAASs.It is local to a host.
• Mini-MAAS contacts other Mini-MAAS for address
  allocation

16

• Translation to secure operations
• Future work
• Feasible inside the computers or in emergency
  shelters
• Scale to internet
• Owners operations cannot know the presence of a
  network

17
CONCLUSION
18
REFERENCE

• draft-cheshire-dnsext-multicastdns-05.txt
  Stuart Cheshire, Marc Krochmal, 7th June 2005 
• draft-ietf-zeroconf-zmaap-02.txt Octavian
  Catrina, Dave Thaler, Bernard Aboba, Erik
  Guttman.org/
• http//Zeroconf Zero Configuration
  networking.htm 
• IPv6 Stateless Address Autoconfiguration S.
  Thomson, Bellcore, T.Narten 
• Zero Configuration Networking Erik GUTTMAN 
•  http//zeroconf.org/
• http//www.multicastdns.org/
• http//en.wikipedia.org/wiki/zeroconf
• http//en.wikipedia.org/wiki/service_location_prot
  ocol

19
THANK YOU