Re: [manet] MANET Terminology Update

Stan Ratliff <sratliff@cisco.com> Thu, 28 June 2012 16:13 UTC

Return-Path: <sratliff@cisco.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C79621F8526 for <manet@ietfa.amsl.com>; Thu, 28 Jun 2012 09:13:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FgKVx-vHSTHv for <manet@ietfa.amsl.com>; Thu, 28 Jun 2012 09:13:37 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 695A521F8518 for <manet@ietf.org>; Thu, 28 Jun 2012 09:13:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=sratliff@cisco.com; l=5450; q=dns/txt; s=iport; t=1340900017; x=1342109617; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=NKu5w33Mwd484pUAbwFg+nvWvorjY+kskQmdvv9k2hw=; b=eUeYZ27g4/ljJaWx0Sr+FSGTH7KK3IJ7ucoI4jGor93D6M3N89bsTqwO 0lupyaU6jewx85oTYVZbim6DqeFEaOvA7+XKnRzL0m96MSvmt8V/5Acl1 4JhoTz1Zld7LMNSE5tzIiHTQdnyFJY7vlZv5yV3Y7ViMrZEBua5L14wsw I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAH6B7E+tJXG9/2dsb2JhbABFtiuBB4IYAQEBAwEBAQEPAUIZAwMFBQcECxEEAQEBJwcnHwkIBhMih2QFC5hHoGSLNxQOhQhgA5UygRKNC4FmgnuBOgk
X-IronPort-AV: E=Sophos;i="4.77,493,1336348800"; d="scan'208";a="96937221"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-8.cisco.com with ESMTP; 28 Jun 2012 16:13:19 +0000
Received: from dhcp-64-102-54-116.cisco.com (dhcp-64-102-54-116.cisco.com [64.102.54.116]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id q5SGDJdD003225; Thu, 28 Jun 2012 16:13:19 GMT
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset="windows-1252"
From: Stan Ratliff <sratliff@cisco.com>
In-Reply-To: <CADnDZ89=iAiFkYCS-WWGqYai68f5a=gJmXBtYA0nkH8dS7roOA@mail.gmail.com>
Date: Thu, 28 Jun 2012 12:13:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <231272E3-0BD9-441C-9719-36CE8755E7AF@cisco.com>
References: <CADnDZ8_ob_+N8nFFE39Wwweiwhn2CwtHd5G=XwqC5eaHFPb1ug@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D13F270@GLKXM0002V.GREENLNK.net> <CADnDZ89=iAiFkYCS-WWGqYai68f5a=gJmXBtYA0nkH8dS7roOA@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1278)
Cc: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>, manet <manet@ietf.org>
Subject: Re: [manet] MANET Terminology Update
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2012 16:13:38 -0000

Abdussalam, 

On Jun 28, 2012, at 6:57 AM, Abdussalam Baryun wrote:

> I think there is an additional option as I am a MANET-WG memebr so I
> can write a new draft titled [MANET Protocols Terminology] to the
> MANET-WG. So it will seam like an update to the expired, but in the
> same time it is a new proposed (informational RFC),
> new-file-name-draft-00, and with new authors.
> 
> I agree we should avoid unproductive-arguments in any MANET-document.
> So we need to work together in a new-draft of MANET-Terminology so we
> have new productive-arguments directed to improve new deliverable
> documents (e.g. draft authored by MANET editor, and/or most of MANET
> WG members).

Seems to me that you are somewhat defining an "unproductive argument" as "an argument where anyone disagrees with Abdussalam"…. :-/

As a working group member, I'm going to add my voice to Chris Dearlove's - I fail to see the need for this type of effort. 

Regards,
Stan


> 
> AB
> ====
> 
> On 6/28/12, Dearlove, Christopher (UK) <Chris.Dearlove@baesystems.com> wrote:
>> Note that
>> (a) That's a 1998 document. Things can change in 14 years. That includes
>> that the purpose of the document was to aid protocol designers' discussions.
>> We've done that. And we seem to have managed for 14 years without this.
>> (b) You probably don't have permission to update it. That document has no
>> copyright assignment on it, and back then I think copyright remained with
>> the authors (or possibly their employers, which are likely to have changed
>> in 14 years) at least at ID stage. And if you want it to remain as a WG
>> document you would need the WG to agree you take it over. (And the IETF
>> tools won't accept you doing that either without intervention from WG chairs
>> at least.) You could of course avoid that by going back to author status,
>> but see the earlier part of this point.
>> (c) Lots of definitions in that draft aren't used in any MANET WG document.
>> For example we have no protocols using clustering. So why do we need to
>> define them?
>> (d) Experience has shown that several of the definitions in that document
>> are of things that can cause a great deal of unproductive argument. Let's
>> not rehash that.
>> (e) Protocols such as NHDP and OLSRv2 have included their own definitions
>> where these are needed. And even if it were desirable for these protocols to
>> reference an external document, it's too late.
>> 
>> --
>> Christopher Dearlove
>> Senior Principal Engineer, Communications Group
>> Communications, Networks and Image Analysis Capability
>> BAE Systems Advanced Technology Centre
>> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
>> Tel: +44 1245 242194 |  Fax: +44 1245 242124
>> chris.dearlove@baesystems.com | http://www.baesystems.com
>> 
>> BAE Systems (Operations) Limited
>> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre,
>> Farnborough, Hants, GU14 6YU, UK
>> Registered in England & Wales No: 1996687
>> 
>> 
>> -----Original Message-----
>> From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of
>> Abdussalam Baryun
>> Sent: 28 June 2012 10:12
>> To: manet
>> Subject: [manet] MANET Terminology Update
>> 
>> ----------------------! WARNING ! ----------------------
>> This message originates from outside our organisation,
>> either from an external partner or from the internet.
>> Keep this in mind if you answer this message.
>> Follow the 'Report Suspicious Emails' link on IT matters
>> for instructions on reporting suspicious email messages.
>> --------------------------------------------------------
>> 
>> Hi All,
>> 
>> I have seen no draft that defines terminology in MANET WG, which I
>> feel it is a basic RFC that should be in any WG so they agree on
>> terminology within the group. I understand from my experience in this
>> WG that the only RFC agreed on is the RFC2501 as a background for
>> definitions. I want to work on defining terminology which I will
>> update the draft expired below. Is there any one want to join me in
>> authoring, (will first finish update comments on RFC2501 which will
>> post shortly).
>> 
>> draft-ietf-manet-term-01 (Nov 1998)
>> http://trac.tools.ietf.org/html/draft-ietf-manet-term-01
>> 
>> Please note that documents MAY expire but right knowledge/experience
>> NEVER expires :)
>> 
>> Abdussalam Baryun
>> University of Glamorgan, UK
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>> 
>> 
>> ********************************************************************
>> This email and any attachments are confidential to the intended
>> recipient and may also be privileged. If you are not the intended
>> recipient please delete it from your system and notify the sender.
>> You should not copy it or use it for any purpose nor disclose or
>> distribute its contents to any other person.
>> ********************************************************************
>> 
>> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet