Re: [Autoconf] draft-clausen-manet-linktype

mase <mase@ie.niigata-u.ac.jp> Sun, 16 November 2008 02:13 UTC

Return-Path: <autoconf-bounces@ietf.org>
X-Original-To: autoconf-archive@megatron.ietf.org
Delivered-To: ietfarch-autoconf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 47BD23A6999; Sat, 15 Nov 2008 18:13:58 -0800 (PST)
X-Original-To: autoconf@core3.amsl.com
Delivered-To: autoconf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4EFA23A6999 for <autoconf@core3.amsl.com>; Sat, 15 Nov 2008 18:13:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level:
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qfyf1hc5mgkJ for <autoconf@core3.amsl.com>; Sat, 15 Nov 2008 18:13:55 -0800 (PST)
Received: from mxav01.cc.niigata-u.ac.jp (mxav01.cc.niigata-u.ac.jp [133.35.17.129]) by core3.amsl.com (Postfix) with ESMTP id 53C883A6951 for <autoconf@ietf.org>; Sat, 15 Nov 2008 18:13:54 -0800 (PST)
Received: from mxav01.cc.niigata-u.ac.jp (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 36B9E4F4242 for <autoconf@ietf.org>; Sun, 16 Nov 2008 11:13:44 +0900 (JST)
Received: from chamame.ie.niigata-u.ac.jp (chamame.ie.niigata-u.ac.jp [133.35.169.34]) by mxav01.cc.niigata-u.ac.jp (Postfix) with SMTP id 2C1D64F41EC for <autoconf@ietf.org>; Sun, 16 Nov 2008 11:13:44 +0900 (JST)
Received: (qmail 16026 invoked from network); 16 Nov 2008 11:13:44 +0900
Received: from unknown (HELO neccomputer.ie.niigata-u.ac.jp) (133.35.156.66) by chamame.ie.niigata-u.ac.jp with SMTP; 16 Nov 2008 11:13:44 +0900
Message-Id: <7.0.0.16.2.20081116103354.086b0bc8@ie.niigata-u.ac.jp>
X-Mailer: QUALCOMM Windows Eudora Version 7J rev1.0
Date: Sun, 16 Nov 2008 11:13:48 +0900
To: Thomas Heide Clausen <Thomas@ThomasClausen.org>, autoconf@ietf.org
From: mase <mase@ie.niigata-u.ac.jp>
In-Reply-To: <B566C80C-8A63-4D59-94AC-3A2C55A1B4EF@ThomasClausen.org>
References: <B566C80C-8A63-4D59-94AC-3A2C55A1B4EF@ThomasClausen.org>
Mime-Version: 1.0
Subject: Re: [Autoconf] draft-clausen-manet-linktype
X-BeenThere: autoconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Ad-Hoc Network Autoconfiguration WG discussion list <autoconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/autoconf>
List-Post: <mailto:autoconf@ietf.org>
List-Help: <mailto:autoconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: autoconf-bounces@ietf.org
Errors-To: autoconf-bounces@ietf.org

Dear Thomas,

I think that your document is very useful to deepen understanding 
about what is MANETs.

I have some commnets.
I think that Sec. 4 MANET Interface discusses more than MANET 
interface, that is, MANET link type. This section may present 
essences of the MANET link type.
I almost agree what are written here, but hope that we could a little 
bit clearer the essence of MANET link type. I would propose the 
following remark to be included in the texts.

The set of neighbors of each MANET interface may be position 
(attachment to a link)- and time-dependent.
The nature of position-dependency in MANETs is clearly described in 
Sec. 4. Time-dependency occurs for example due to interference in 
wireless environment. This is different from things discussed in Sec. 
5. Note that , in the Ethernet-like link, the set of neighbors of 
each MANET interface is position- and time-independent in principle.

The word "position" is used in Sec. 5. So, the remark above also 
contributes to improves consistency.

I also would propose that Sec. 6 is entitled "The MANET link Type 
Characteristics". It should be noted in Sec. 6 that  the most of 
characteristics of MANET link type, listed here, occur as the result 
of the nature of MANET link type proposed above.

Thanks,
Kenichi






At 18:51 08/11/04, Thomas Heide Clausen wrote:
>Folks,
>
>As you know, we need to make progress on the architectural issues,
>before we can hope to make progress on other matters within this WG.
>One of the requests that have been made to us has been to "describe
>the MANET Link Type", and so I have written together a strawman text
>to this effect:
>
>         http://www.ietf.org/internet-drafts/draft-clausen-manet-linktype-00.txt
>
>Feedback is, obviously, welcome -- preferably on the list such that
>we could be prepared spend time on this also in MN.
>
>Note, however, that this is an individual I-D.
>
>I'd also like to draw your collective attention to:
>
>         http://www.ietf.org/internet-drafts/draft-iab-ip-model-evolution-01.txt
>
>Which has served as a source of inspiration for the linktype text.
>
>Thanks,
>
>Thomas
>_______________________________________________
>Autoconf mailing list
>Autoconf@ietf.org
>https://www.ietf.org/mailman/listinfo/autoconf
>


_______________________________________________
Autoconf mailing list
Autoconf@ietf.org
https://www.ietf.org/mailman/listinfo/autoconf