Subject: [manet] Differences from draft-engelstad-manet-name-resolution-01.txt ? (WAS: Agenda Item Request)

From: [email-masked]
Date: Wed, 25 Feb 2004 11:09:20 +0100

Hi Paul,
 
When I read your address resolution draft that you submitted last year, I spent much time to figure out which aspects differed from the draft by Perkins (draft-perkins-manet-autoconfig-01.txt) which was well known to me. (See for example: http://genie.iitd.ernet.in/~bnj/CS858-Fall-2003-04-GENIE/PapersandRFCs-AdhocNetworks/draft-perkins-manet-autoconf-01.txt) I wish you had explained clearly in your draft the differences between the two approaches. Your key-based twist to address autoconfiguration could have been summarized in half a page. The rest was re-invention of the wheel. A short comparitive summary could have saved me (and probably many of us) much time.
 
Again, I have the same problem. DNS name resolution for MANETs was presented at IETF in Vienna last summer, and we discussed the approach after the meeting. You have recently submitted an alternative approach to name resolution, but after having skimmed through your 11-page draft, I realize I need more time to figure out the main differences. Could you do me the favour of shortly summarizing the main differences between our two approaches?
 
Thank you,
Paal
---------------------------------------------
I assume that your already read our draft, but here is a pointer, just in case:
 
A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title		: Name Resolution in on-demand MANETS and external IP Networks

	Author(s)	: P. Engelstad, G. Egeland, R. Koodli, C. Perkins

	Filename	: draft-engelstad-manet-name-resolution-01.txt

	Pages		: 13

	Date		: 2004-2-2

The most common user applications for data communication (including 

    web browsing and e-mail) lack a method for name resolution in multi-

    hop wireless ad-hoc networks of mobile nodes (MANETs). While the 

    Domain Name System (DNS) works well on the fixed Internet, it 

    represents a centralized approach to name resolution, which is not 

    suitable for MANETs. This document specifies a straightforward 

    solution for name resolution lookup in on-demand MANETs, i.e. MANETs 

    that are routed with a reactive routing protocol, such as DSR [DSR] 

    or AODV [AODV]. Names are resolved locally within the MANET with a 

    mechanism similar to multicast DNS or LLMNR on a link. Although 

    names resolved locally normally will have preference, MANET nodes 

    that have access to external networks may complement the local name 

    resolution by injecting into the MANET lookup results resolved by a 

    conventional DNS server. The proposed solution applies equally well 

    to IPv4 or IPv6.

A URL for this Internet-Draft is:

http://www.ietf.org/internet-drafts/draft-engelstad-manet-name-resolution-01.txt

To remove yourself from the IETF Announcement list, send a message to 

ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username

"anonymous" and a password of your e-mail address. After logging in,

type "cd internet-drafts" and then

	"get draft-engelstad-manet-name-resolution-01.txt".

A list of Internet-Drafts directories can be found in

http://www.ietf.org/shadow.html 

or  ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:

	[email-masked].

In the body type:

	"FILE /internet-drafts/draft-engelstad-manet-name-resolution-01.txt".

NOTE:	The mail server at ietf.org can return the document in

	MIME-encoded form by using the "mpack" utility.  To use this

	feature, insert the command "ENCODING mime" before the "FILE"

	command.  To decode the response(s), you will need "munpack" or

	a MIME-compliant mail reader.  Different MIME-compliant mail readers

	exhibit different behavior, especially when dealing with

	"multipart" MIME messages (i.e. documents which have been split

	up into multiple messages), so check your local documentation on

	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader

implementation to automatically retrieve the ASCII version of the

Internet-Draft.

 <ftp://ftp.ietf.org/internet-drafts/draft-engelstad-manet-name-resolution-01.txt> <ftp://ftp.ietf.org/internet-drafts/draft-engelstad-manet-name-resolution-01.txt> 

-----Opprinnelig melding-----
Fra: [email-masked] [mailto:[email-masked]]På vegne av Jaehoon Paul Jeong
Sendt: 25. februar 2004 05:54
Til: [email-masked]; Joe Macker
Kopi: [email-masked]; [email-masked]
Emne: Re: [manet] Agenda Item Request

Dear MANET Chairs,
 
First of all, thanks for a timeslot for discussing MANET Address Autoconfiguration Issues.
 
I am wondering if MANET DNS can be a candidate of MANET next steps.
When we think MANET address autoconfiguration and Internet connectivity,
MANET DNS has a close relationship with them.
My draft, draft-jeong-manet-dns-service-00.txt <http://www.ietf.org/internet-drafts/draft-jeong-manet-dns-service-00.txt> , deals with the cooperation with the above functions.
Also, in the aspect of manet deployment and application, DNS seems to be indispensable.
 
When considering MANET characteristics, we need to reduce the amount of broadcast messages
and delay in DNS, Service Discovery, P2P, etc.
These applications are inclined to send request message in broadcast and the response is unicast by a correspondent node.
Especially, in reactive routing protocols, such as AODV, if the request message is piggybacked by RREQ message,
it will be beneficial due to the reverse path for a response message.
Therefore, MANET DNS is closely related to MANET routing.
 
I would like to know your opinions on MANET DNS.
Do you think that MANET DNS is manet next item or out of scope?
Thanks.
 
Regards,
Jaehoon Paul Jeong

----- Original Message ----- 
From: [email-masked] 
To: [email-masked] 
Cc: [email-masked] ; [email-masked] 
Sent: Wednesday, February 18, 2004 10:39 AM
Subject: Re: [manet] Agenda Item Request

Dear Scott, 

I'm interested in presenting a draft titled "DNS Service for Mobile Ad Hoc Networks"; http://www.ietf.org/internet-drafts/draft-jeong-manet-dns-service-00.txt

This draft deals with the following things; 
  - DNS Service within a stand-alone MANET 
  - DNS Service within a MANET connected to the Internet 
  - Service Discovery based on Multicast DNS 
  - Interworking between Multicast DNS and IP Address Autoconfiguration 
  - Authentication of DNS Messages 
  - IPv6 Considerations 

I would like to discuss this draft with other experts at this meeting. 
Thanks. 

Best Regards, 
--- 
HyoungJun KIM([email-masked]) 
Director/IPv6 Forum Korea, 
Principle Member of Research Staff, 
Head of NGI Standards Reaserch Team/ 
Protocol Engineering Center/ 
Electronics and Telecommunications Research Institute 
161 Gajung-Dong, Yusung-Gu, Taejon, 305-350, Rep. of KOREA 
Tel: +82 42 860 6576, Fax: +82 42 861 5404 Mobile Phone: 010-3034-6655