Transcript Duplicate Address Detection in IPv6 Mobile Ad Hoc Network

IP Autoconfiguration for MANET
Wireless Access Network and NS-2 Workshop
Jaehoon Paul Jeong, ETRI
[email protected]
http://www.adhoc.6ants.net/~paul
1
Contents










Introduction
Unicast Address Autoconfiguration
Multicast Address Allocation
Multicast DNS
Service Discovery
Internet Connectivity
MANET Testbed
Conclusion
References
Reference Website
2
Introduction

Mobile Ad Hoc Network (MANET)

MANET has dynamically changing network topology.

MANET partition and mergence may happen.


There is no network administrator.


In MANET, there are many points to consider unlike the
Internet.
The current Internet services, such as address
autoconfigation and DNS, are difficult to adopt.
So, Auto-configuration is necessary in MANET!!
3
MANET Auto-configuration



Internet Connectivity
for MANET
Multicast DNS

Unicast Address Autoconfiguration
Multicast Address Allocation
Multicast DNS
Service Discovery
Unicast Address Autoconfiguration
Internet Connectivity
Service Discovery

Multicast Address Allocation
4
Protocol Stack supporting
MANET Autoconfiguration
Unicast
Address
Autoconf
Multicast
Address
Allocation
Multicast
DNS
Service
Discovery
Internet
Connectivity
Application
TCP/UDP
ICMPv6
IPv6
Network
Interface
Transport
MLD
Network
Link
Wireless Link
5
Unicast Address Autoconfiguration
6
Introduction

Configuration of Unicast Address in Network Interface
 Precedent step for IP networking
 Methods of IP address configuration in network interface




Manual configuration
Automatic configuration
Consideration of IP address configuration
 A unique address should be assigned.
 Automatic configuration is needed for user’s convenience.
Addressing in MANET
 Each mobile node is necessary to autoconfigure its IP address
through Duplicate Address Detection (DAD).


An arbitrary address is selected.
The uniqueness of the address is verified though DAD.
7
Problem of IP Address Conflict - 1/2
IP address = a
A
F
B
C
E
D
G
H
K
IP address = a
8
Problem of IP Address Conflict - 2/2
IP address = a
A
F
B
C
E
D
G
H
K
IP address = a
9
Requirements for MANET
Address Autoconfiguration

Base Document


draft-jeong-manet-addr-autoconf-reqts-01.txt
Three Classes of Requirements



Join and Departure of Mobile Nodes
Network Partitioning and Merging
Internet Connectivity
10
Join and Departure of Mobile Nodes
[R1] Address autoconf protocol MUST support timely
autoconfiguration of IP address for a mobile node.
[R2] Address autoconf protocol MAY support mechanisms to
probe whether a mobile node moves into another MANET.
[R3] Mobile nodes using address autoconf protocol MUST
validate allocated IP addresses when powering up or
rebooting.
[R4] Mobile nodes using address autoconf protocol MAY
validate allocated IP addresses when moving into a new
network.
11
Network Partitioning and Merging
[R5] Ad hoc address autoconf protocol MUST detect and resolve
address conflicts in a timely manner and on an ongoing basis.
[R6] Ad hoc address autoconf protocol MUST allow conflicted
address replaced with another.
[R7] Ad hoc address autoconf protocol SHOULD minimize the
damage, such as loss of delivered packets, due to address
replacement.
[R8] Addresses SHOULD be allocated or autoconfigured in a
way that minimizes the probability that two or more nodes
will have the same address.
[R9] In order to detect duplicate addresses, ad hoc address
autoconf protocol MAY get the aid of ad hoc routing protocol.
12
Internet Connectivity
[R10] MANET MAY allow configuration of one or more
gateways for the global connectivity to the Internet.
[R11] Mobile node that desires Internet connectivity MAY
have a globally routable IP address.
13
Strong DAD

Definition



Ai(t) : Address assigned to node i at time t.
For each address a != undefined,
Sa(t) = {j | Aj(t) = a}.
Condition of Strong DAD

Within a finite bounded time interval after t,
at least one node in Sa(t) will detect that
|Sa(t)| > 1.
14
Example of Strong DAD
1st Try of Host A
 MAC Address - a9:bb:cc:dd:ee:ff
 IPv6 Address - fec0:0:0:ffff:abbb:ccff:fedd:eeff
MANET Prefix
EUI-64
2nd Try of Host A
 64-bit Random Number – 1111:2222:3333:4444
 IPv6 Address - fec0:0:0:ffff:1111:2222:3333:4444
MAC & IPv6 Address of Host C
 MAC Address – a9:bb:cc:dd:ee:ff
 IPv6 Address - fec0:0:0:ffff:abbb:ccff:fedd:eeff
Host C
Random Number
Host B
Host A
AREQ message
AREP message
Router
Wireless Link
Where AREQ : Address Request message,
AREP : Address Reply message
15
Limitation of Strong DAD

Simple Observation


If partitions can occur for unbounded intervals of
time, then strong DAD is impossible.
Limitation of Strong DAD

When partitions merge, addresses of all nodes
must be checked for duplicates.


This DAD does not indicate how merging of
partitions should be detected.
This does not suggest how the congestion caused by
DAD messages may be reduced.
16
Procedure of Strong DAD
Generation of 32-bit Random Number
and 64-bit Random Number
Generation of Temporary address with
MANET_INIT_PREFIX and 32-bit Number
MANET_INIT_PREFIX
Generation of Tentative address with
MANET_PREFIX and 64-bit Number
 FEC0:0:0:FFFF::/96
MANET_PREFIX
Transmission of AREQ message
This iteration is
performed by
predefined
retry-number.
FEC0:0:0:FFFF::/64
Was any extended
AREP message received
from any other node?
YES
Generation of 64-bit
Random Number
NO
Reconfiguration of
Unicast address in NIC
17
Weak DAD

Motivation


Handling address duplication due to MANET partitioning
and merging
Requirements


Correct Delivery
 Packets meant for one node must not be routed to
another node, even if the two nodes have chosen the
same address.
Relaxed DAD
 It does not require detection of all duplicate addresses.

The duplication of addresses can not be detected in
partitioned networks.
18
Resolution of Address Conflict
by Weak DAD
(IP address, Key) = (a, K_A)
A
F
B
C
G
Partition 1
Partition 2
E
D
H
Address
Duplication
Report
K
(IP address, Key) = (a, K_K)
E detects the duplication
of address a with key
information
(IP address, Key) = (b, K_K)
19
MANET Address Autoconfiguration
draft-jeong-adhoc-ip-addr-autoconf-02.txt, discussed at IETF-57

Step 1: Address selection


Step 2: Duplicate address detection


How to select one of IP addresses in the address space?
How to detect a duplicate address?
Step 3: Address change negotiation

Which node should perform a reallocation procedure?


Victim node selection problem
Step 4: Maintenance of upper-layer sessions

How to let an upper-layer session avoid a connection breakage?
20
MANET Address Autoconf for AODV
draft-jeong-manet-aodv-addr-autoconf-00.txt, discussed at IETF-59

Step 1: IP address selection


Random address selection
Step 2: Duplicate address detection

Hybrid DAD


Step 3: Address change negotiation

Simple victim node selection


Strong DAD + Weak DAD
Node that is performing route discovery is selected as victim node.
Step 4: Maintenance of upper-layer sessions

Notification of address change


Address Mapping Cache management


Address change indication similar to MIP binding update
It is similar to MIP binding cache management
Data delivery through IP tunneling
21
Address Autoconfiguration
Message Format
0
1
2
3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Type
|
Code
|
Checksum
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Identification
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Originator IP Address
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Requested or Duplicate IP Address
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type:
- AREQ: Address Request
- AREP: Address Reply
- AERR: Address Error
Code:
- 0: default
- 1: indication of address change in type AERR
22
Step1: IP Address Selection
- Selection of Random IP Address

IPv4
 IPV4_MANET_PREFIX



+ 16-bit Random Number
169.254/16 is used as IPV4_MANET_PREFIX.
There is a great possibility of address conflicts by Birthday
Paradox.
 Nodes of two to the power eight (= 256) will generate
at least one address collision with a probability of 50%.
IPv6
 IPV6_MANET_PREFIX

+ 64-bit Random Number
fec0:0:0:ffff::/64 is used as IPV6_MANET_PREFIX.
 Because of the deprecation of IPv6 site-local address,
a new local prefix for local networks separated from
the Internet is necessary.
23
Step2: Duplicate Address Detection
- Hybrid DAD = Strong DAD + Weak DAD

Phase 1 : Strong DAD

Time-based DAD



For detecting IP address duplication in a connected MANET
partition within a finite bounded time interval
Strong DAD is performed during the initiation of node’s network
interface.
Phase 2 : Weak DAD

Routing-based DAD




For detecting IP address duplication during ad hoc routing, e.g.,
route discovery in AODV
It can handle the address duplication by MANET partition and
mergence.
Key is used for the purpose of detecting duplicate IP addresses.
Virtual IP Address = IP Address + Interface Key
24
Step3: Address Change Negotiation
- Simple Victim Node Selection

Detection of Duplication Address


When a node performs route discovery with RREQ in order
to communicate with another, address conflict can be
detected by Weak-DAD procedure.
If there is the duplicate IP address,

The detector node sends an AERR (Address Error) message
to the node using duplicate address that is associated with
a different key.
 Victim node is the one which is performing route
discovery.


We can consider the number of on-going sessions and
fairness.
Configuration of a new IP address

The node, receiving the AERR message, auto-configures a
new IP address through Strong DAD
25
Step4: Maintenance of Upper-layer
Sessions – 1/3

Notification of IP Address Change


The node with duplicate address informs its peer
nodes with its IP address change through AERR
message.
AERR message is used.
It contains Duplicate address and New address.
 It plays the same role of Binding Update message of
MIP or MIPv6.


The notified peer node stores address mapping
information in its local Address Mapping Cache.
26
Step4: Maintenance of Upper-layer
Sessions – 2/3

Address Mapping Cache (AMC)
Management



AMC maintains the association of duplicate address
and new announced address.
AMC is similar to MIP binding cache.
AMC is used for tunneling when sending and
receiving data packets.

TCP sessions can be maintained even though IP
address has been changed.
27
Step4: Maintenance of Upper-layer
Sessions – 3/3

Data Delivery through IP Tunneling

After the delivery of AERR message, the peer node
and announced node exchange data packets through
IP tunneling using AMC.
Data Packet
Peer Node
Address : IPpn
Outer IP Header
Inner IP Header
Announced Node
SRC Addr : IPpn
New Address : IPnew
Old Address : IPold
DEST Addr : IPnew
SRC Addr : IPpn
DEST Addr : IPold
Payload
28
Multicast Address Allocation
29
IPv6 Multicast Address Allocation

Role


It allocates a unique IPv6 multicast address to a session
without address allocation server.
Address Format

IPv6 multicast (a) is generated on the basis of Interface ID
of IPv6 unicast address (b).
64-bit
(a)
Network prefix
8-bit 8-bit
(b)
64-bit
FF
Interface ID
16-bit
64-bit
reserved
Interface ID
4-bit
0 0 P T
Flags
32-bit
Group ID
4-bit
0 1 0 1
Scope
30
IPv4 Multicast Address Allocation

Role



It allocates a unique IPv4 multicast address to a session
without address allocation server.
It uses the same idea as IPv6 multicast address allocation.
Address Format

IPv4 multicast (a) is generated on the basis of Host ID
of IPv4 unicast address (b).
16-bit
(a)
Network prefix
4-bit
(b)
16-bit
1110
16-bit
Host ID
Host ID
12-bit
Group ID
31
Procedure of Multicast Address
Allocation
Request of
Multicast Address Allocation
from Application
Generation of Unused Group ID
Generation of a Multicast Address
with Interface ID (or Host ID) and Group ID
Delivery of the Multicast Address
32
Service of Multicast Application
: Allocation of a unique Multicast Address for a new Session
B
C
D
A
A
B
1
2
4
Step
E
C
1
D
1
E
1
1
3
6
5
Action
1
Unicast Address Autoconfiguration
2
Run of Video-conferencing Tool (e.g.,
SDR) and Creation of a new Session
3
Advertisement of Session Information
4
MN A’s join to the new Session
5
MN E’s join to the new Session
6
Transmission of Video/Audio Data by
MN A
7
Transmission of Video/Audio Data by
MN E
7
33
Multicast Address Allocation in SDR
Multicast Addresses of
Audio and Video Sessions
34
Multicast DNS
35
Introduction

Name Service in MANET

MANET has dynamic network topology

Current DNS can not be adopted in MANET!


Because it needs a fixed and well-known name server
Idea of Name Service in MANET

All the mobile nodes take part in name service


Every mobile node administers its own name information
It responds to the other node’s DNS query related to its domain
name and IP address
36
Related Work
: Link-Local Multicast Name Resolution (LLMNR)

Each node performs the role of DNS name server for
its own domain name in link-local scoped network
LLMNR Sender
LLMNR Responder
LLMNR query message (What is IPv6 address of “host.private.local”?)
- It is sent in link-local multicast
LLMNR response message (IPv6 address of “host.private.local”)
- It is sent in link-local unicast
Verification of LLMNR response
- Does the value of the response conform to
the addressing requirements?
- Is hop-limit of IPv6 header 1?
If the result is valid,
then the Sender caches and passes the response
to the application that initiated DNS query.
else the Sender ignores the response and continues
to wait for other responses.
37
Ad Hoc Name Service System
for IPv6 MANET (ANS)

ANS provides Name Service in MANET

MANET DNS Domain


ADHOC.
MANET IPv6 Prefix

IPv6 Site-local Prefix


FEC0:0:0:FFFF::/64
Architecture of ANS System

ANS Responder


ANS Resolver


It performs the role of DNS Name Server
It performs the role of DNS Resolver
ANS API

It provides user applications with DNS resolver functions
38
DNS Name Resolution through
ANS System
Mobile Node A
ANS
Zone DB
Application
ANS
Responder
Mobile Node B
ANS
Zone DB
Application
ANS
Resolver
Application
Application
ANS
Resolver
ANS
Responder
DNS Query
DNS Response
Node
Process
ANS
Responder
ANS
Resolver
Database
UNIX Datagram Socket
ANS
Zone DB
Application
Application
Memory Read / Write
Wireless Link
Mobile Node C
DNS Message
39
Interaction of ANS System Processes
Application
ANS API
ANS Responder
ANS Resolver
Main-Thread
ANS
Zone DB
DNS
Query
DNS Query /
DNS Response
Main-Thread
ANS Cache
Resolv-Thread
Timer-Thread
DUR-Thread
DNS
Response
Process
Memeory Read / Write
Process
UNIX Datagram Socket
Thread
Internal Connection
Thread
Memeory Read / Write
Database
UDP Socket Connection
Cache
Internal Connection
UDP Socket Connection
40
Name Service in ANS

Name Generation


Zone File Generation


generates a unique domain name based on the
network device identifier
generates ANS zone file with the unique domain
name and corresponding IPv6 address
Name Resolution

performs the name-to-address translation
41
Scenario of Name Service
within MANET
MN-A
Request of
Host DNS Name
Resolution
DNS Query Message
is sent in Multicast
MN-C
MN-B
DNS Query Message
(MN-C.ADHOC.)
DNS Query Message
(MN-C.ADHOC.)
Receipt of
DNS Query Message
Receipt and Process
of DNS Query Message
DNS Response Message
(MN-C’s IPv6 Address)
Gain of
DNS Information
DNS Response Message
is sent in Unicast
MN-A tries to connect to
the server on MN-C
The server on MN-C accepts
the request of the connection
from MN-A
42
Authentication of DNS Message



Why is necessary the authentication of DNS message?
 To prevent attacker from informing a DNS querier of wrong DNS
response
How to authenticate DNS message?
 IPsec ESP with a null-transform
 Secret key transaction authentication for DNS, called as TSIG
[RFC2845]
Our Scheme of Authentication
 TSIG message authentication where the trusted nodes share
a group secret key for authenticating DNS messages.
43
DNS Message Format
DNS message header
Header Section
Question for the name server
Question Section
Answer Section:
e.g., AAAA RR
Authority Section
Additional Section:
Resource records answering the question
Resource records pointing toward
an authority (e.g., AAAA resource record)
e.g., TSIG RR
Resource records holding additional
information (e.g., TSIG resource record)
44
Procedure of Secure DNS Resolution
Mobile Node C
(MN-C.ADHOC.)
Mobile Node A
(MN-A.ADHOC.)
DNS Query (What is the IPv6 address of “MN-C.ADHOC.”?)
via site-local multicast and UDP
DNS Response (IPv6 address of “MN-C.ADHOC.”)
via site-local unicast and UDP
Verification of DNS Response
- Does the source address of the response conform to
the ad hoc addressing requirements?
- Is the TSIG resource record valid?
If the Response is valid,
then ANS Resolver delivers the result to application program
else ANS Resolver sends DNS Query again and
waits for another DNS Response by the allowed retry number
45
Service Discovery
46
Service Discovery

Definition


Discovery of the location (IP address, Transport-layer
protocol, Port number) of server that provides some
service.
Methods

Multicast DNS based Service Discovery


Service discovery through Multicast DNS and DNS SRV
resource record, which indicates the location of server or
the multicast address of the service
SLP based Service Discovery

Service discovery through IETF Service Location Protocol (SLP)

RFC 2165, RFC 2608, RFC 3111
47
Considerations for Service Discovery

Limitations of Existing Schemes


Most of current schemes are concerned with service
location for the Internet.
 Such protocols have not taken into account the mobility,
packet loss issues and latency.
Considerations


Some devices are small and have limited computation,
memory, and storage capability.
 They can only act as clients, not servers.
Power constraints
 Service discovery should not incur excessive messaging
over wireless interface.
48
Service Discovery based on
Multicast DNS
ANS Responder’s Zone File
$TTL 20
$ORIGIN ADHOC.
PAUL-1
IN
IPv6 Multicast Address
corresponding to Service Name
AAAA FEC0:0:0:FFFF:3656:78FF:FE9A:BCDE
8
;; DNS SRV Resource Records
; Unicast Service : SERVICE-1
_SERVICE-1._TCP
IN SRV 0 1 3000 PAUL-1.ADHOC.
_SERVICE-1._UDP
IN SRV 0 1 3000 PAUL-1.ADHOC.
FF
Flags
P=0, T=1
; Multicast Service : SERVICE-2
_SERVICE-2._UDP
IN SRV 0 1 4000 @.1.5.
Generation of
IPv6 Multicast
Address
4 4
DNS SRV Resource Record for
Multicast Service
Multicast Service Name
Parsing Function
MD5 Hash Function
Flags label & Scope label
128-bit Digest
16-bit IPv6 Site-local
Multicast Address Prefix
+
112
Group ID
Scope
5
Group ID=Low-order 112 bits of Digest
IPv6 Site-local Multicast Address
49
Scenario of Service Discovery
MN-C
MN-A
MN-B
Request of
Server Information
DNS Query Message
for Service Information
DNS Query Message
is sent in Multicast
DNS Query Message
for Service Information
Receipt of
DNS Query Message
DNS Response Message
with Service Information
Receipt and Process
of DNS Query Message
related to
DNS SRV resource record
Gain of
Service Information
MN-C tries to connect to
the server on MN-A
or
MN-C joins the multicast group
related to MN-A
The server on MN-A accepts the
request of the connection from MN-C
or
The multicast group comprises
MN-A and MN-C
50
Internet Connectivity
51
Internet Connectivity for IPv6 MANET

Why do we need to support the Internet connectivity in
MANET?

When mobile nodes in MANET want to communicate with hosts in
the Internet



Email, Web Server, etc.
Many service providers think that Internet connectivity function is
important for MANET deployment.
What is needed to support the global connectivity?

Internet Gateway Discovery


Global Prefix Information and Default Gateway Address
Global DNS Server Discovery

Recursive DNS Server Address
52
Internet Gateway Discovery (1/2)

Two ways to do Internet Gateway Discovery

Extended Route Discovery


We need to extend RREQ / RREP of IPv6 AODV.
Extended IPv6 Neighbor Discovery (ND)
 We need to extend IPv6 ND.


MANET Route Solicitation (RS)
MANET Router Advertisement (RA)
53
Internet Gateway Discovery
by Extended Route Discovery
Internet
MANET
IGW
RREP
RREQ
RREQ
B
RREQ
RREP
A
Routing Table
default: GW
C
54
Internet Gateway Discovery
by Extended Neighbor Discovery
Internet
MANET
IGW
RA
RS
B
RS
RS
RA
A
Routing Table
default: GW
Global Unicast Address
Autoconfiguration
C
55
Required Operations

Internet Gateway Discovery

Address Resolution


Global IPv6 Address Generation
Default Route Setting

Global DNS Server Discovery

Route Examination



Route Examination at Manet Node
Route Examination at Internet Gateway
Error Handling


ICMPv6 Destination Unreachable Message
ICMPv6 Redirect Message
56
Global DNS Server Discovery

When a MANET Node communicates with
an Internet Node,



Discovery of Internet Gateway


MANET Node should find out Internet Gateway(s).
MANET Node should resolve the Internet Node’s
DNS name into its globally routable IPv6 address.
RREQ/RREP-based Discovery
Discovery of Global DNS Server

Recursive DNS Server (RDNSS) Option within RREP
57
Discovery of Internet Gateway (IGW)
& Recursive DNS Server (RDNSS)
DNS Server
(DNSS)
RREP Message from IGW2
Web Server
(WS)
RREP Header
Internet
Internet Gateway1
(IGW1)
Internet Gateway2
(IGW2)
Prefix Information Option
: IGW2’s Global IPv6 Prefix
RREP
RREQ
RDNSS1
MN1
RDNSS2
RDNSS3
RDNSS Option
: RDNSS3’s MANET Address
MN2
MANET1
MN3
MANET2
58
Procedure of
DNS Name Resolution in MANET
Input a DNS name
Does the DNS name
belong to
Ad-hoc domain?
YES
NO
Resolve the DNS name
through ANS Resolver
Resolve the DNS name
through DNS Resolver
Output IPv6 address(es)
corresponding to the DNS name
59
MANET Testbed
60
Testbed for IPv6 MANET

Motivation


There is much difficulty in managing the topology of MANET
for testing protocols and applications.
Topology Configuration Method

For testing multi-hop network configuration,



We control Tx and Rx power of IEEE 802.11b NIC.
Also, we use MAC-filtering to filter out packets in
other links.
Routing Protocols

We used IPv6 AODV and MAODV as Ad Hoc routing protocols.
61
MANET Testbed
IPv6 Wireless Router
Protocol Test in MANET Testbed
62
Experiment in MANET Testbed
Hub
ping6 R3
R2
R1
R2
R3
- IPv6 Wireless Router: R1, R2, R3
- Control Node: NB
3ffe:2e00:1:a::102
AP
R2
3ffe:2e00:1:a::102
ping6 R3
NB
R1
R3
3ffe:2e00:1:a::101
3ffe:2e00:1:a::103
R1
R3
3ffe:2e00:1:a::101
NB
Mac filter
NB
Ping6 of R1 into R3
3ffe:2e00:1:a::103
Ping6 of R1 into R3 via R2
Demo Scenario
Controlling IPv6 Wireless Routers at NB
Routing Table Update in R1
1hop
1hop
2hop
2hop
Ping6’s Result
63
Conclusion

MANET Autoconfiguration






Unicast Address Autoconfiguration
Multicast Address Allocation
Multicast DNS
Service Discovery
Internet Connectivity
Autoconfiguration Technologies in MANET



They can provide Ad Hoc users with auto-networking.
They must be default functions for the Deployment of MANET.
Also, security in MANET is important issue and should considered
along with auto-networking in MANET.


But it is very difficult.
MANET Networking is a corner stone for Ubiquitous Computing.
64
References
[1] Jaehoon Paul Jeong et al., “Requirements for Ad Hoc IP Address Autoconfiuguration”, draft-jeongmanet-addr-autoconf-reqts-01.txt, February 2004.
[2] Jaehoon Paul Jeong et al., “Ad Hoc IP Address Autoconfiguration”, draft-jeong-adhoc-ip-addrautoconf-02.txt, February 2004.
[3] Jaehoon Paul Jeong et al., “Ad Hoc IP Address Autoconfiguration for AODV”, draft-jeong-manetaodv-addr-autoconf-00.txt, February 2004.
[4] Charles E. Perkins et al., “IP Address Autoconfiguration for Ad Hoc Networks”, draft-ietf-manetautoconf-01.txt, November 2001.
[5] Nitin H. Vaidya, “Weak Duplicate Address Detection in Mobile Ad Hoc Networks”, MobiHoc2002,
June 2002.
[6] Jaehoon Paul Jeong et al., “Auto-Networking Technologies for IPv6 Mobile Ad Hoc Networks”, ICOIN
2004, February 2004.
[7] Jaehoon Paul Jeong et al., “DNS Service for Mobile Ad Hoc Networks”, draft-jeong-manet-dnsservice-00.txt, February 2004.
[8] Jaehoon Paul Jeong et al., “Service Discovery based on Multicast DNS in IPv6 Mobile Ad-hoc
Networks”, VTC2003 Spring, April 2003.
[9] Ryuji Wakikawa et al., “Global connectivity for IPv6 Mobile Ad Hoc Networks”, draft-wakikawamanet-globalv6-03.txt, October 2003.
65
Reference Website
ETRI’s Ad Hoc Autoconfiguration Project
http://www.adhoc.6ants.net
66