Re: [Autoconf] Discussion on link types and status of documents

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 20 March 2008 10:40 UTC

Return-Path: <autoconf-bounces@ietf.org>
X-Original-To: ietfarch-autoconf-archive@core3.amsl.com
Delivered-To: ietfarch-autoconf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0BB1028C31D; Thu, 20 Mar 2008 03:40:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.692
X-Spam-Level:
X-Spam-Status: No, score=-100.692 tagged_above=-999 required=5 tests=[AWL=-0.255, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 v+flpsRAT4mQ; Thu, 20 Mar 2008 03:40:34 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9241B28C307; Thu, 20 Mar 2008 03:40:34 -0700 (PDT)
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 0E64428C2FD for <autoconf@core3.amsl.com>; Thu, 20 Mar 2008 03:40:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 wsMDU1q2nJ+r for <autoconf@core3.amsl.com>; Thu, 20 Mar 2008 03:40:33 -0700 (PDT)
Received: from mail128.messagelabs.com (mail128.messagelabs.com [216.82.250.131]) by core3.amsl.com (Postfix) with SMTP id 1DA9328C1CF for <autoconf@ietf.org>; Thu, 20 Mar 2008 03:40:33 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-9.tower-128.messagelabs.com!1206009495!17750815!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [144.189.100.103]
Received: (qmail 12668 invoked from network); 20 Mar 2008 10:38:15 -0000
Received: from motgate3.mot.com (HELO motgate3.mot.com) (144.189.100.103) by server-9.tower-128.messagelabs.com with SMTP; 20 Mar 2008 10:38:15 -0000
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233]) by motgate3.mot.com (8.12.11/Motorola) with ESMTP id m2KAcEQl010134; Thu, 20 Mar 2008 03:38:14 -0700 (MST)
Received: from az10vts04.mot.com (az10vts04.mot.com [10.64.251.245]) by az33exr03.mot.com (8.13.1/Vontu) with SMTP id m2KAcEUW001935; Thu, 20 Mar 2008 05:38:14 -0500 (CDT)
Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117]) by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id m2KAcBWD001922; Thu, 20 Mar 2008 05:38:12 -0500 (CDT)
Message-ID: <47E23E93.6060505@gmail.com>
Date: Thu, 20 Mar 2008 11:38:11 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Shubhranshu <shubranshu@gmail.com>
References: <001501c885e5$da561a20$8f024e60$@nl> <374005f30803170457u1d8f43cenfc3c1fef744602f5@mail.gmail.com> <47DFDF53.3030901@gmail.com> <e9c684940803182048v622da64cna10742e9c0475aff@mail.gmail.com> <47E0E82B.2040900@gmail.com> <e9c684940803192035l57d65247i3de8097d4d56e133@mail.gmail.com>
In-Reply-To: <e9c684940803192035l57d65247i3de8097d4d56e133@mail.gmail.com>
X-Antivirus: avast! (VPS 080319-0, 19/03/2008), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
Cc: autoconf@ietf.org
Subject: Re: [Autoconf] Discussion on link types and status of documents
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: autoconf-bounces@ietf.org
Errors-To: autoconf-bounces@ietf.org

Shubhranshu wrote:
> Alex,
> 
> Please see inline comments
> 
> On 3/19/08, Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>> Shubhranshu wrote:
>>> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>>>> Ian Chakeres wrote:
>>>>> I'd like to chime in on this conversation by saying that "MANET
>>>>> link" is not a good term. MANET's (and the MANET WG protocols)
>>>>> run over lots of kinds of different physical and logical links.
>>>>> It just so happens that they may also often run over links with
>>>>> asymmetric reachability.
>>>> Maybe then trying to describe link-types in the AUTOCONF
>>>> Architecture is actually listing those kinds of different physical
>>>> and logical links on which MANET have been run?
>>>>
>>>> I have not run MANET.  But I ran other IPv6 protocols, and AUTOCONF
>>>> is not limited to MANET, and the list of link-types I used are the
>>>> following:
>>>>
>>>> Ethernet Bluetooth PPP RS232C USB
>>> I agree that defining term "MANET link" is not appropriate but I do
>>> not see any point in listing all the links on which MANET has been
>>> run.
>> How would one otherwise start describing link types?
> 
> I assumed in my previous mail that by link you meant different L2
> technologies since you listed bluetooth, USB, Ethernet, etc. One could
> do that by describing its properties, behavior as seen by the IP.

YEs, that is what I mean by 'link': a certain L2 technology.  I agree 
one would describe its properties and behavior as  seen by IP.

>>> MANET has not been run on any particular L2 technology does not imply
>>> that MANET cannot run on that technology.
>>>
>>> I agree that having "IP Link Model" for MANET explained clearly would
>>>  help here. The challenge is to express precisely, with appropriate
>>> terminologies what the MANET community has been assuming while
>>> designing and running MANET protocols. The current MANET Architecture
>>>  document have text on this but since these questions keep coming, I
>>> am inclined to think that including more specific text would help.
>> Well, the current draft does not describe 'link type', neither 'IP Link
>> Model', can't find.  What do you mean by current MANET Architecture
>> document having text on this?  Which part, thank you.
> 
> I meant section 5.

But section 5 "Addressing & the MANET Prefix Model" does not describe 
link types.

Alex


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________
_______________________________________________
Autoconf mailing list
Autoconf@ietf.org
https://www.ietf.org/mailman/listinfo/autoconf