[Manet-dt] Question and Comment on OLSRv2-03

mase <mase@ie.niigata-u.ac.jp> Sat, 31 March 2007 04:33 UTC

Return-path: <manet-dt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HXVH9-00009A-Od; Sat, 31 Mar 2007 00:33:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HXVH6-00008q-Nr for manet-dt@ietf.org; Sat, 31 Mar 2007 00:33:12 -0400
Received: from ccmail.cc.niigata-u.ac.jp ([133.35.23.1] helo=mxav03.cc.niigata-u.ac.jp) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HXVH3-0001Ff-66 for manet-dt@ietf.org; Sat, 31 Mar 2007 00:33:12 -0400
Received: from mxav03.cc.niigata-u.ac.jp (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id CC0B22905D2 for <manet-dt@ietf.org>; Sat, 31 Mar 2007 13:32:52 +0900 (JST)
Received: from mxav03.cc.niigata-u.ac.jp (localhost.localdomain [127.0.0.1]) by mxav03.cc.niigata-u.ac.jp (Postfix) with SMTP id B9AE12905C1 for <manet-dt@ietf.org>; Sat, 31 Mar 2007 13:32:52 +0900 (JST)
Received: (qmail 3263 invoked from network); 31 Mar 2007 13:32:52 +0900
Received: from unknown (HELO chamame.ie.niigata-u.ac.jp) (133.35.169.34) by mxav03.cc.niigata-u.ac.jp with SMTP; 31 Mar 2007 13:32:52 +0900
Received: (qmail 11927 invoked from network); 31 Mar 2007 13:32:50 +0900
Received: from unknown (HELO neccomputer.ie.niigata-u.ac.jp) (133.35.156.66) by chamame.ie.niigata-u.ac.jp with SMTP; 31 Mar 2007 13:32:50 +0900
Message-Id: <7.0.0.16.2.20070331112019.040385c8@ie.niigata-u.ac.jp>
X-Mailer: QUALCOMM Windows Eudora Version 7J rev1.0
Date: Sat, 31 Mar 2007 13:33:01 +0900
To: manet <manet@ietf.org>, manet-dt@ietf.org
From: mase <mase@ie.niigata-u.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc:
Subject: [Manet-dt] Question and Comment on OLSRv2-03
X-BeenThere: manet-dt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: MANET Design Team <manet-dt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet-dt>, <mailto:manet-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/manet-dt>
List-Post: <mailto:manet-dt@ietf.org>
List-Help: <mailto:manet-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet-dt>, <mailto:manet-dt-request@ietf.org?subject=subscribe>
Errors-To: manet-dt-bounces@ietf.org

Dear Thomas and all,

I have some questions and comments on OLSRv2-03 and NHDP-02.

1. Local interface block in NHDP
The following description
"The first address block of the Local Interface Block MUST contain 
the used address of the interface over which theHELLO message is 
transmitted." was deleted in the -02 draft.

Does this mean that the address must be included in the same order in 
all copies of a given HELLO message, regardless of which OLSRv2 
nterface it is transmitted on?

If so, the description in 9.2 of OLSRv2 -03 should be modified 
because there is now no clear distinction in terms of the order of 
addresses in the first address block between HELLO and TC messages.

2. Attached networks in OLSRv2

One of the main changes from -02 to -03 is "Local attached network 
advertisement may be delegated to MPRs."

To do this, information on local attached network of a node is 
advertised in the Local  Interface Block of the HELLO messages. 
However, it is not clear which information base is poplulated  when 
this information is received by a MPR of this node. It is also not 
clear how this information is carried by TC messages of the MPR. Does 
the first address block or other address block of TC messages carry 
this information? If the latter, It is also needed to modifiy 13.1.3 
of OLSRv2-03 since the gateway to the attached network is not the MPR 
itself but the original node with the attaced network.

Am I missing something?

I also have a question with reagard to attached network advertisement 
in HELLO messages. Why may attached networks with dist>0 not be 
advertized in HELLO messages?


3. "Local Attached Neighbor Tuple" in 12 of OLSRv2-03 should be 
"Local Attached Nework Tuple".

Thanks,
Kenichi





  



_______________________________________________
Manet-dt mailing list
Manet-dt@ietf.org
https://www1.ietf.org/mailman/listinfo/manet-dt