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

Ian Chakeres <ian.chakeres@gmail.com> Tue, 18 November 2008 16:39 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 0335A3A6A73; Tue, 18 Nov 2008 08:39:00 -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 8F76E3A6A73 for <autoconf@core3.amsl.com>; Tue, 18 Nov 2008 08:38:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.555
X-Spam-Level:
X-Spam-Status: No, score=-2.555 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044]
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 ke4Ue7MNNlpN for <autoconf@core3.amsl.com>; Tue, 18 Nov 2008 08:38:57 -0800 (PST)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by core3.amsl.com (Postfix) with ESMTP id 6E05F3A69E5 for <autoconf@ietf.org>; Tue, 18 Nov 2008 08:38:57 -0800 (PST)
Received: by yw-out-2324.google.com with SMTP id 3so1663281ywj.49 for <autoconf@ietf.org>; Tue, 18 Nov 2008 08:38:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=RKxrnUSrLlmLb98xYvxbBfuqYpqCYcCYtpJgxyf0Nk0=; b=Xa6jnuuSgYQVd1uZYoOIFuyYR7/ESM4fonqkQzXj+civbETijMJYG8oOsjcwKU6Bvz /bmNHznQdUirZmv4KPv9j4dGUTHFMkoqOyWW47aH/3b+zZyBRTFx2ng0Vs+xDdizgvht SPdTPs4rHIgEw/2rN/R9w9WEhNxTCNB9/hrbw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=DGuSMmmf7Zvy1QboZTV8v+vKLb6J9GqsbR8NIeprTW+i/AWXzMsp7B3XRScLUdnC7D aTlr58KgJkKBq8i8Zx06ro3W7TJGQdm2w3kUu6Li7HXgr5dSbSXMNQpFssycuWtx7ulh Akno7hftgaTLUfMJh2DFiLGnMxw/Uihfazz6g=
Received: by 10.65.189.20 with SMTP id r20mr46709qbp.71.1227026332998; Tue, 18 Nov 2008 08:38:52 -0800 (PST)
Received: from ?192.168.1.124? ([75.146.152.44]) by mx.google.com with ESMTPS id p6sm9650420qbp.17.2008.11.18.08.38.47 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 18 Nov 2008 08:38:52 -0800 (PST)
Message-Id: <B4C99090-73A9-4803-804C-9AFC7B85DCC6@gmail.com>
From: Ian Chakeres <ian.chakeres@gmail.com>
To: autoconf@ietf.org
In-Reply-To: <B566C80C-8A63-4D59-94AC-3A2C55A1B4EF@ThomasClausen.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 18 Nov 2008 06:57:51 -0500
References: <B566C80C-8A63-4D59-94AC-3A2C55A1B4EF@ThomasClausen.org>
X-Mailer: Apple Mail (2.929.2)
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"; DelSp="yes"
Sender: autoconf-bounces@ietf.org
Errors-To: autoconf-bounces@ietf.org

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'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