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

mase <mase@ie.niigata-u.ac.jp> Tue, 18 November 2008 20:23 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 D639F28C246; Tue, 18 Nov 2008 12:23:44 -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 6D7FE28C241 for <autoconf@core3.amsl.com>; Tue, 18 Nov 2008 12:23:43 -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 pbtBHghMJsg7 for <autoconf@core3.amsl.com>; Tue, 18 Nov 2008 12:23:42 -0800 (PST)
Received: from mxav03.cc.niigata-u.ac.jp (mxav03.cc.niigata-u.ac.jp [133.35.17.131]) by core3.amsl.com (Postfix) with ESMTP id 63AEA28C236 for <autoconf@ietf.org>; Tue, 18 Nov 2008 12:23:42 -0800 (PST)
Received: from mxav03.cc.niigata-u.ac.jp (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id BD3AA2901DC for <autoconf@ietf.org>; Wed, 19 Nov 2008 05:23:36 +0900 (JST)
Received: from chamame.ie.niigata-u.ac.jp (chamame.ie.niigata-u.ac.jp [133.35.169.34]) by mxav03.cc.niigata-u.ac.jp (Postfix) with SMTP id 708FE290201 for <autoconf@ietf.org>; Wed, 19 Nov 2008 05:23:36 +0900 (JST)
Received: (qmail 10804 invoked from network); 19 Nov 2008 05:23:36 +0900
Received: from unknown (HELO neccomputer.ie.niigata-u.ac.jp) (133.35.156.66) by chamame.ie.niigata-u.ac.jp with SMTP; 19 Nov 2008 05:23:36 +0900
Message-Id: <7.0.0.16.2.20081119050635.0880a730@ie.niigata-u.ac.jp>
X-Mailer: QUALCOMM Windows Eudora Version 7J rev1.0
Date: Wed, 19 Nov 2008 05:23:43 +0900
To: Ian Chakeres <ian.chakeres@gmail.com>, autoconf@ietf.org
From: mase <mase@ie.niigata-u.ac.jp>
In-Reply-To: <B4C99090-73A9-4803-804C-9AFC7B85DCC6@gmail.com>
References: <B566C80C-8A63-4D59-94AC-3A2C55A1B4EF@ThomasClausen.org> <B4C99090-73A9-4803-804C-9AFC7B85DCC6@gmail.com>
Mime-Version: 1.0
Cc: Thomas Heide Clausen <thomas@thomasclausen.org>
Subject: Re: [Autoconf] draft-clausen-manet-linktype - naming
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

At 20:57 08/11/18, Ian Chakeres wrote:
>I'd like to start a discussion thread on the naming of this draft/ linktype.
>
>I don't think that MANET should be in the name of the linktype. The
>characteristics and constraints of a linktype are not MANET specific.
>
>(I'd also like to repeat that MANET routing protocols will work quite
>happily over other link types as well.)
>
>I would rather describe these links as "non-reflexive and non- 
>transitive (wireless) links". I'd also be happy with a nice acronym,
>like NBMA or UDLR.

I don't think that the introduction/definition of such a special 
link type is useful for MANET discussions, since MANET protocols can 
work on other link types such as the Ethernet. I rather think that 
it is important to make clear link assumptions or requirements to be 
used for MANET in general.

My sugestions are as follows:

MANET protocols work on any link models,  where each interface has 
at least one other interface to/from which it can send/receive 
packets. These neighbors may change over time.

The link models given above of course inculde the Ethernet model as 
the special case. They also inculde non-reflexive and /or 
non-transitive links you defined.

Kenichi


>I'm interested in your thoughts. How do you think we should refer to
>this linktype?
>
>Ian
>
>On Nov 4, 2008, at 4:51 AM, 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
>


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