Transcript PowerPoint 프레젠테이션

Ad-hoc에서의 Autoconfiguration 기술
안소연, 정재훈
(ICU, ETRI)
[email protected], [email protected]
1
Contents




Introduction
Ad-hoc Routing Protocols
Autoconfiguration Technology for IPv6 MANET
Conclusion
2
Introduction (1/2)

Categories of Wireless Networks

Infrastructured Networks


Infrastructureless Networks


Cellular Networks, Wireless LAN (WLAN)
Ad-hoc Networks
Ad-hoc Networks



유선 기반 망 (Infrastrured Networks) 없이 무선 이동단말로만 구
성된 망
Multi-hop Routing을 위해 각 이동단말이 Router 역할을 수행함
용도

긴급구조, 전쟁, 홈 네트워크, Shopping Mall, 임시 공동작업,
도로에서의 차량 간의 통신, 공항에서의 티켓팅, 사무실 등.
3
Infrastructured N/W vs. Infrastructureless N/W
Internet
WLAN
Cellular
Mobile Ad-hoc Networks
4
Introduction (2/2)

MANET에서의 이슈




Ad-hoc Unicast Routing
Ad-hoc Multicast/Broadcast Routing
Power Saving
Automatic Support of Networking Facility in MANET


Autoconfiguration Technology
Global Connectivity for MANET
5
Ad-hoc Routing Protocols
6
Ad-hoc Unicast Routing Protocols
Ad-hoc routing protocols
Source-initiated
Demand-driven
Table-driven
DSDV
CGSR
WRP
AODV
DSR
LMR
ABR
TORA
SSR
7
Table-driven (Proactive)

Characteristics


Maintenance of consistent, up-to-date routing information
from each node to every other node in the network
Each node



Criterion of Classification of Routing Protocols



maintains one or more tables to store routing information
propagates updates of network topology
Number of necessary routing-related tables
Methods by which changes in network structure are broadcast
Examples

DSDV, CGSR, WRP, TBRPF, OLSR
8
Demand-driven (Reactive)

Characteristics

Creation of routes only when desired by the source node


Route Discovery Process is completed




Until the destination becomes inaccessible along every path
from the source
Until the route is no longer desired
Criterion of Classification of Routing Protocols


Once a route is found
When all possible route permutations have been examined
Maintenance of a Route


By Route Discovery Process
Method by which route finding is performed
Examples

AODV, DSR, LMR, TORA, ABR, SSR
9
AODV (1/3)

AODV is improved DSDV algorithm




Reactive
Provides unicast and multicast communication (MAODV)
AODV doesn’t maintain a complete list of routes as in
DSDV algorithm.
 Nodes that are not on a selected path don’t maintain
routing information or participate in routing table
exchanges
Loop-free

AODV utilizes destination sequence numbers to ensure all
routes are loop-free
10
AODV (2/3)

Route Discovery process


When source node doesn’t already have a valid
route to that destination, it initiates a route
discovery process to locate the other node.
Route Discovery
 broadcasts a route request (RREQ) packet to its
neighbors.
 Neighbors forward the request to their neighbors,
and so on until either the destination or an
intermediate node
with a “fresh enough” route to the destination
is located.
11
AODV (3/3)
a) Propagation of the RREQ
b) Path of the RREP to the source
12
MAODV (1/3)


MAODV works very similarly to PIM-DM.
Builds shared bi-directional tree for multicast groups




Group Leader




Composed of group members and connecting nodes
On-demand creation
Maintained as long as the group exists
Maintains and distributes group sequence number
Not a central point of failure
Provides methods to repair link, tree partition, and to
reconnect tree
Messages


RREQ/RREP message to discover multicast route and add tree
branch as unicast AODV
MACT message to prune tree branch
13
MAODV (2/3)
a) Joining the Group
N2
N5
N8
RREQ
Source N1
N7
N4
N3
b) Path of the RREP to the source
N6
N2
N5
N8
RREP
Source N1
N7
N4
N3
N6
14
MAODV (3/3)
c) Route Activation
N2
N5
N8
MACT
Source N1
N7
N4
N3
N6
d) Leaving the Group
N2
N5
N8
MACT with “P”
Source N1
N7
N4
N3
N6
15
Implementation (1/2)

IPv6 Ad-hoc Unicast Routing Protocol

AODV (Ad-hoc On-demand Distance Vector) Routing
Protocol

AODV for IPv4 has been already implemented by several
organizations including NIST.



AODV draft version 11
Linux Kernel Version 2.4 or later
AODV for IPv6 based on NIST Kernel AODV v2.0.1 has been
implemented by ETRI & ICU.


AODVv6 draft version 01
Tested with 3 nodes in multi-hop
16
Implementation (2/2)

IPv6 Ad-hoc Multicast Routing Protocol

MAODV (Multicast AODV) Routing Protocol

MAODV for IPv4 and IPv6 have been being implemented by
ETRI & ICU.


MAODV draft version 00
Homepage
http://cnlab.icu.ac.kr/project/AdhocProject.html
17
Autoconfiguration Technology
for IPv6 MANET
Autoconfiguration Technology?
 Autoconfiguration Technology for IPv6 MANET

Unicast Address Autoconfiguration
 Multicast Address Autoconfiguration
 Multicast Name Resolution
 Service Discovery

18
Autoconfiguration Technology?

What is Autoconfiguration?


Why is Autoconfiguration needed?




The technology that let IP-enabled devices be able to
communicate one another in infrastructureless environment.
To provide hosts with the automatic configuration related to
networking.
To let it possible for hosts communicate when either dynamic or
static configuration is impossible.
To provide the quick and easy configuration related to the network
facility in MANET environment.|
Issues of IETF Zeroconf Working Group




Unicast Address Autoconfiguration
Multicast Address Allocation
Name Resolution (DNS)
Service Discovery
19
Autoconfiguration Technology for IPv6 MANET

Unicast Address Autoconfiguration
 Automatic configuration of a unique IP address within the scope in
which the address will be used.

Multicast Address Autoconfiguration
 Allocation of a unique multicast address for the application which
needs a new multicast address.

Multicast Name Resolution
 Translation between name and
IPv6 address

Service Discovery
 Discovery of the necessary service
on the network without prior
configuration.
Autoconfiguration
Technology
in IPv6-based MANET
Multicast Address Autoconfiguration
Multicast Name Resolution
Service Discovery
Unicast Address Autoconfiguration
20
Autoconfiguration for IPv6 MANET

Network Configuration

Protocol Stack of Mobile Node
Application
Multicast Name
Ad-hoc
Ad-hoc
Resolution
Unicast Routing Multicast Routing
B
A
C
D
E
TCP / UDP
IPv6
Mobile Node
Unicast Address
Autoconfiguration
Multicast Address
Autoconfiguration
Wireless Link
NIC
21
Unicast Address Autoconfiguration (1/2)
: Extended DAD Procedure in MANET
1st Try of Host A
 MAC Address - a9:bb:cc:dd:ee:ff
 IPv6 Address - fec0:0:0:ffff:abbb:ccff:fedd:eeff
MAC & IPv6 Address of Host C
 MAC Address – a9:bb:cc:dd:ee:ff
 IPv6 Address - fec0:0:0:ffff:abbb:ccff:fedd:eeff
MANET Prefix
EUI-64
The address of Host A conflicts with that of Host C.
Host C sends NA message to Host A.
2nd Try of Host A
 64-bit Random Number – 1111:2222:3333:4444
 IPv6 Address - fec0:0:0:ffff:1111:2222:3333:4444
Random Number
The address of Host A doesn’t conflict with that of any other host.
This address can be used as the unicast address of Host A.
Host B
Host A
NS message
Host C
NA message
Router
Wireless Link
Where NS : Neighbor Solicitation,
NA : Neighbor Advertisement
22
Unicast Address Autoconfiguration (2/2)
: Procedure of Unicast Address Configuration
Generation of Lower 64 bits in EUI-64
Generation of Temporary address with
MANET_INIT_PREFIX and Lower 64 bits
MANET_INIT_PREFIX
 fec0:0:0:fffe::/64
Generation of Tentative address with
MANET_PREFIX and Lower 64 bits
MANET_PREFIX
fec0:0:0:ffff::/64
Transmission of Extended NS message
Was any extended
NA message received
from other node?
YES
Generation of 64-bit
Random Number
NO
Configuration of
Unicast address in NIC
23
Multicast Address Autoconfiguration

(a)
Format of Site-local Unicast Address (a) and
Format of Site-local Multicast Address (b)
16-bit
64-bit
Network Prefix
Subnet
ID
Interface ID
(b)
ff
16
64
Subnet
ID
Interface ID
Procedure of Multicast Address
Allocation
Request of
Multicast Address Allocation
48-bit
8 4,4

32
Generation of Unused Group ID
Group ID
Generation of a multicast address
Flags
P=1, T=1
Scope
5
Random
Number
Delivery of the multicast address
24
Service of Multicast Application
B
A
C
D

E
Multicast Service Scenario
1. Unicast Address Autoconfiguration
Unicast Address
Autoconfiguration
- Booting of each Mobile Node (MN)
- Unicast address configuration in NIC
2. Multicast Address Autoconfiguration
A
B
1
C
1
D
1
E
1
- Run of Video-conferencing Tool
1
& Creation of a new Session
- Allocation of a multicast address
2
3
4
6
5
7
Multicast Address
Autoconfiguration
3. Advertisement of Sesstion information
through multicasting (MAODV)
4. Join to the new Session in MN A
5. Join to the new Session in MN E
6. Transmission of Video/Audio data
of MN A through multicasting
7. Transmission of Video/Audio data
of MN E through multicasting
25
Multicast Name Resolution
Multicast Name Resolution (MNR) is performed by
mDNS (Multicast DNS)

Procedure of the resolution
from domain name to IPv6 address in MNR
Sender
1
2
Responder
MNR query (What is IPv6 address of “host.private.local.”?)
via site-local multicast over UDP
MNR response (IPv6 address of “host.private.local.”)
via unicast over UDP
3 Verification of MNR response
- Does the value of the response conform to
the addressing requirements?
4 If the result is valid,
then the Sender caches and uses the response.
else the Sender ignores the response and continues
to wait for other responses.
26
Service Discovery (1/2)
Service Discovery can be performed by MNR &
DNS SRV Resource Record

Simple Zone File containing DNS SRV resource records
for service discovery
$TTL 3600
;; Name to Address Lookups
localhost IN AAAA ::1
; Localhost with Loopback Address
host.private.local. IN AAAA fec0:0:0:ffff::202:2dff:fe1b:e851
; MN’s Domain Name with Site-Local Address
;; DNS SRV Resource Records
_multimedia1._tcp.private.local. 4000 IN SRV 0 1 3000 host.private.local.
_multimedia2._udp.private.local. 4000 IN SRV 0 1 3001 host.private.local.
_service-name._protocol.domain-name TTL Class SRV Priority Weight Port Target
27
Service Discovery (2/2)

Procedure of the service discovery through
MNR & SRV RR
Client
Server
1
SRV query ( “_service-1._udp.adhoc.”)
via site-local multicast over UDP
2
SRV response (“ttl class type priority weight target”)
via site-local unicast over UDP
3
Verification of SRV response
- Does the value of the response conform to the
addressing requirements?
- Is the service unicast or multicast?
4
If the service is multicast,
then the Sender joins the multicast group.
else the Sender tries to connect the server.
28
Project Homepage for
IPv6 Ad-hoc Autoconfiguration Technology

URL

http://www.adhoc.6ants.net
29
Conclusion

Ad-hoc에서의 라우팅, 서비스, 인터넷 연동에 있
어서 IPv6는 IPv4 보다 유리함.


주소 자동 설정, 멀티캐스트 주소 할당, DNS 서비스, 서
비스 탐색 등.
Ubiquitus Networking


IPv6로 누구나 쉽게 시간과 장소에 관계없이 통신 서비스를
제공 받을 수 있음.
Future Work

Ad-hoc에서의 보안


유선망과 WLAN 같은 무선망보다 네트워크 보안 제공이 어렵
다.
Ad-hoc 라우팅, 서비스 등의 Security 기능이 다른 네트워크 보
다 더욱 필요함.
30
References
[1] Elizabeth M. Royer and Chai-Keong Toh, “A Review of Current Routing Protocols for Ad Hoc Mobile
Wireless Networks”, IEEE Personal Communications, April 1999.
[2] Charles E. Perkins, Elizabeth M. Belding-Royer and Samir R. Das, “Ad hoc On-Demand Distance Vector
(AODV) Routing”, (work in progress) draft-ietf-manet-aodv-10.txt, January 2002.
[3] Elizabeth M. Royer and Charles E. Perkins, “Multicast Ad hoc On-Demand Distance Vector (MAODV)
Routing”, draft-ietf-manet-maodv-00.txt, July 2000.
[4] Erik Guttman, "Autoconfiguration for IP Networking:Enabling Local Communication", IEEE Internet
Computing, May/June 2001.
[5] Jaehoon Jeong and Jungsoo Park, “Autoconfiguration Technologies for IPv6 Multicast Service in Mobile Adhoc Networks”, 10th IEEE International Conference on Networks, Aug. 2002.
[6] Jung-Soo Park and Myung-Ki Shin, “Link Scoped IPv6 Multicast Addresses”, (work in progress) draft-ietfipv6-link-scoped-mcast-02.txt, July 2002.
[7] Levon Esibov, Bernard Aboba and Dave Thaler, “Linklocal Multicast Name Resolution (LLMNR)”, draftietf-dnsext-mdns-11.txt, July 2002.
[8] A. Gulbrandsen, P. Vixie and L. Esibov, “A DNS RR for specifying the location of services (DNS SRV)”,
RFC2782, Feb. 2000.
[9] Ryuji Wakikawa, et al., “Global connectivity for IPv6 Mobile Ad Hoc Networks”, draft-wakikawa-manetglobalv6-01.txt, July 2002.
[10] Thierry Ernst and Hong-Yon Lach, “Network Mobility Support Terminology”, draft-ernst-monetterminology-01.txt, July 2002.
31