[Autoconf] Fwd: New Version Notification for draft-baccelli-multi-hop-wireless-communication-04

"Charles E. Perkins" <charles.perkins@earthlink.net> Mon, 24 May 2010 22:42 UTC

Return-Path: <charles.perkins@earthlink.net>
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 C2A613A67AB for <autoconf@core3.amsl.com>; Mon, 24 May 2010 15:42:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.073
X-Spam-Level:
X-Spam-Status: No, score=-0.073 tagged_above=-999 required=5 tests=[AWL=-0.074, BAYES_50=0.001]
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 6WD-ByYdi++y for <autoconf@core3.amsl.com>; Mon, 24 May 2010 15:42:37 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) by core3.amsl.com (Postfix) with ESMTP id E12483A63C9 for <autoconf@ietf.org>; Mon, 24 May 2010 15:42:36 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=Q2+rYtTC78ZHoIAKp3UYtse5RNT00ollspS+eEPVYzrbNrGoGWj542PkAmv8loGa; h=Received:Message-ID:Date:From:Organization:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [12.204.153.98] (helo=[10.166.254.135]) by elasmtp-galgo.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1OGgLs-0001f7-E1 for autoconf@ietf.org; Mon, 24 May 2010 18:42:29 -0400
Message-ID: <4BFB00CF.7040701@earthlink.net>
Date: Mon, 24 May 2010 15:42:23 -0700
From: "Charles E. Perkins" <charles.perkins@earthlink.net>
Organization: Wichorus Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: "autoconf@ietf.org" <autoconf@ietf.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956abb457f1b4332f52d073de0c5d3ffb71fd672be4528574ee350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 12.204.153.98
Subject: [Autoconf] Fwd: New Version Notification for draft-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: Mon, 24 May 2010 22:42:37 -0000

Hello folks,

We have submitted a revised version of the draft
with some significant corrections.  Here is a URL
for the revision:
	http://www.ietf.org/internet-drafts/draft-baccelli-multi-hop-wireless-communication-04.txt

Would there be interest in the working group to
accept this as a working group document?

Regards,
Charlie P.


-------- Original Message --------
Subject: New Version Notification for 
draft-baccelli-multi-hop-wireless-communication-04
Date: Mon, 24 May 2010 17:38:38 -0500
From: IETF I-D Submission Tool <idsubmission@ietf.org>
To: Perkins, Charles <charliep@wichorus.com>
CC: <Emmanuel.Baccelli@inria.fr>


A new version of I-D, 
draft-baccelli-multi-hop-wireless-communication-04.txt has been 
successfully submitted by Charles Perkins and posted to the IETF repository.

Filename:	 draft-baccelli-multi-hop-wireless-communication
Revision:	 04
Title:		 Multi-hop Ad Hoc Wireless Communication
Creation_date:	 2010-05-24
WG ID:		 Independent Submission
Number_of_pages: 9

Abstract:
This document describes some important characteristics of
communication between nodes in a multi-hop ad hoc wireless network.
These are not requirements in the sense usually understood as
applying to formulation of a requirements document.  Nevertheless,
protocol engineers and system analysts involved with designing
solutions for ad hoc networks must maintain awareness of these
characteristics.
 



The IETF Secretariat.