IETF Logo Mail Archive

Re: [Autoconf] Fwd: New Version Notification fordraft-baccelli-multi-hop-wireless-communication-04

Paul Lambert <paul@marvell.com> Wed, 26 May 2010 18:31 UTC

Return-Path: <paul@marvell.com>
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 197DF3A69B1 for <autoconf@core3.amsl.com>; Wed, 26 May 2010 11:31:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.67
X-Spam-Level:
X-Spam-Status: No, score=-1.67 tagged_above=-999 required=5 tests=[AWL=-0.930, BAYES_20=-0.74]
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 Ez2fzArmMtTK for <autoconf@core3.amsl.com>; Wed, 26 May 2010 11:31:34 -0700 (PDT)
Received: from dakia2.marvell.com (dakia2.marvell.com [65.219.4.35]) by core3.amsl.com (Postfix) with ESMTP id EF08D3A680C for <autoconf@ietf.org>; Wed, 26 May 2010 11:31:33 -0700 (PDT)
X-ASG-Debug-ID: 1274898684-449d6c000001-tL4nV1
Received: from MSI-MTA.marvell.com (msi-mta.marvell.com [10.68.76.91]) by dakia2.marvell.com with ESMTP id fhHbaQWHhsAOgTLX; Wed, 26 May 2010 11:31:24 -0700 (PDT)
X-Barracuda-Envelope-From: paul@marvell.com
Received: from sc-owa02.marvell.com ([10.93.76.22]) by MSI-MTA.marvell.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 26 May 2010 11:31:24 -0700
Received: from SC-vEXCH2.marvell.com ([10.93.76.134]) by sc-owa02.marvell.com ([10.93.76.22]) with mapi; Wed, 26 May 2010 11:31:24 -0700
From: Paul Lambert <paul@marvell.com>
To: "Charles E. Perkins" <charles.perkins@earthlink.net>
Date: Wed, 26 May 2010 11:31:23 -0700
X-ASG-Orig-Subj: RE: [Autoconf] Fwd: New Version Notification fordraft-baccelli-multi-hop-wireless-communication-04
Thread-Topic: [Autoconf] Fwd: New Version Notification fordraft-baccelli-multi-hop-wireless-communication-04
X-ASG-Orig-Subj: RE: [Autoconf] Fwd: New Version Notification fordraft-baccelli-multi-hop-wireless-communication-04
Thread-Index: Acr8/CAJYnkzmbXjSemiHGGRH+WJHQAAxtgQ
Message-ID: <7BAC95F5A7E67643AAFB2C31BEE662D013D5626F6D@SC-VEXCH2.marvell.com>
References: <4BFB00CF.7040701@earthlink.net> <3F22BBC2-A41A-4A6F-8913-263497810A86@inf-net.nl> <7BAC95F5A7E67643AAFB2C31BEE662D013D5626F13@SC-VEXCH2.marvell.com> <4BFD5FA5.80404@earthlink.net>
In-Reply-To: <4BFD5FA5.80404@earthlink.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 26 May 2010 18:31:24.0433 (UTC) FILETIME=[A558B810:01CAFD01]
X-Barracuda-Connect: msi-mta.marvell.com[10.68.76.91]
X-Barracuda-Start-Time: 1274898684
X-Barracuda-URL: http://10.68.76.222:80/cgi-mod/mark.cgi
X-Barracuda-Spam-Score: -1002.00
X-Barracuda-Spam-Status: No, SCORE=-1002.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=1000.0
Cc: "autoconf@ietf.org" <autoconf@ietf.org>
Subject: Re: [Autoconf] Fwd: New Version Notification fordraft-baccelli-multi-hop-wireless-communication-04
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/mail-archive/web/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>
X-List-Received-Date: Wed, 26 May 2010 18:31:35 -0000

Yes - easily solved with a sentence or two somewhere ... the base terminology and models are useful.  It's just that most shorter distance wireless technologies (like 802.11) have acknowledgment based reliability. 
Wireless links are typically not open-loop, but have feedback with acks that provide reliability and indications of the link connectivity.  

> What about multicast?
There are now reliable multicast mechanisms (802.11aa).  These are not common (yet), but would have the same considerations and would always be symmetric.  

Perhaps a sentence or two that mentions acknowledged versus unacknowledged link layers - and that the asymmetric behavior described is for unacknowledged link layer frames. 

Hope this helps ...

Paul

PS - sorry for the not very timely comment ... I lurk on this list infrequently

> -----Original Message-----
> From: Charles E. Perkins [mailto:charles.perkins@earthlink.net]
> Sent: Wednesday, May 26, 2010 10:52 AM
> To: Paul Lambert
> Cc: Teco Boot; autoconf@ietf.org
> Subject: Re: [Autoconf] Fwd: New Version Notification fordraft-baccelli-
> multi-hop-wireless-communication-04
> 
> 
> Hello Paul
> 
> On 5/26/2010 10:34 AM, Paul Lambert wrote:
> 
> > I find this document misleading and confusing in that it does not
> > mention the use of link layer acknowledgments.  It assumes one
> > particular link layer service type and does not indicate that it
> > is only referring to unacknowledged transmission.
> 
> I don't think this omission causes the entire
> document to be misleading and/or confusing.
> Plus, it is a problem easily solved.
> 
> Would you like to propose some text that would
> (a) mention link-layer acknowledgements, and
> (b) eliminate the confusion that you found?
> I haven't checked with Emmanuel, but speaking
> only for myself I'd be happy to support the update.
> 
> > Radio links that require ACKs are symmetric.
> 
> What about multicast?
> 
> Regards,
> Charlie P.

v2.8.7 | Report a Bug | By Email