IETF Logo Mail Archive

Re: [manet] On Forwarding-and-regeneration

Charlie Perkins <charles.perkins@earthlink.net> Tue, 03 May 2016 16:06 UTC

Return-Path: <charles.perkins@earthlink.net>
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 8447912D55A for <manet@ietfa.amsl.com>; Tue, 3 May 2016 09:06:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.716
X-Spam-Level:
X-Spam-Status: No, score=-3.716 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (384-bit key) header.from=charles.perkins@earthlink.net header.d=earthlink.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Phb12ksE1cmp for <manet@ietfa.amsl.com>; Tue, 3 May 2016 09:06:53 -0700 (PDT)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by ietfa.amsl.com (Postfix) with ESMTP id 13DFC12D9C4 for <manet@ietf.org>; Tue, 3 May 2016 09:06:52 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=eI3i6stE7KRYzhj3AoPxIZq1MprsStXu/AFrdTSNeCclfukqDCFj5bDHcbMavQYs; h=Received:Subject:To:References:Cc:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [99.51.72.196] (helo=[192.168.1.67]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1axcqQ-0005b5-HT; Tue, 03 May 2016 12:06:42 -0400
To: Jiazi YI <ietf@jiaziyi.com>
References: <8C311D85-5C5A-4155-9705-6B09D0AA588B@thomasclausen.org> <B31EEDDDB8ED7E4A93FDF12A4EECD30D923B0CBD@GLKXM0002V.GREENLNK.net> <A5260E25-0551-4620-9A78-6014170A5A43@fu-berlin.de> <B31EEDDDB8ED7E4A93FDF12A4EECD30D923B0DFF@GLKXM0002V.GREENLNK.net> <5C8505F1-6938-46D1-AFAF-85AE58270181@thomasclausen.org> <B31EEDDDB8ED7E4A93FDF12A4EECD30D923B0E28@GLKXM0002V.GREENLNK.net> <CA+-pDCd9Wr4JJO++-vA0Y3820_i9gs=QMv7sdTnbAEtPwQbdaw@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D923B0E81@GLKXM0002V.GREENLNK.net> <EA2F2049-E3F6-447B-9F58-9789F742F96F@fu-berlin.de> <D04F0E76-72D0-4D70-8CFD-A4124CBC8F0E@fu-berlin.de> <60BD2E9C-64D7-4444-B3A9-8D207EB4A86F@gmail.com> <144C7397-F19E-4FB0-959A-B5A030BD7A8A@fu-berlin.de> <CAN1bDFwnHOM1A=4Y-xiOp1LDyeUtD01S6JOXT433zhwr4GvKGA@mail.gmail.com> <CA+-pDCe9mHQFMph5=JkYxrLomy5kSJjy8F+QfZEkZ3dJuaZ7Ug@mail.gmail.com> <883f2cf1-ffc7-9910-d80b-e3b610353273@earthlink.net> <CAN1bDFxhCsSxiEDAP3ab4UQ0zHssMa3Myo4S26ckoz0i3fO24Q@mail.gmail.com>
From: Charlie Perkins <charles.perkins@earthlink.net>
Message-ID: <dd4c3ed1-a882-2fff-1d04-b48f429e790c@earthlink.net>
Date: Tue, 03 May 2016 09:06:37 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <CAN1bDFxhCsSxiEDAP3ab4UQ0zHssMa3Myo4S26ckoz0i3fO24Q@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac7b9e664ead5de227537de7b27e635a7bb350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.72.196
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/RwwDZGfdVkTHB73YKOJ6vrVaSBo>
Cc: Mobile Ad Hoc Networks mailing list <manet@ietf.org>
Subject: Re: [manet] On Forwarding-and-regeneration
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 03 May 2016 16:06:55 -0000

Hello Jiazi,

Follow-up below...

On 4/28/2016 5:14 AM, Jiazi YI wrote:
> I think it will make the specification complex, and hard to extend.
>
> What about if I need to define a new TLV field for my extension? The 
> field would either be unprotected, or the extension won't be 
> interoperable with old implementations.

RFC 7182 has the following language:

>    The rationale for removing any ICV Message TLVs already present prior
>    to calculating the ICV is that several ICV TLVs may be added to the
>    same message, e.g., using different ICV cryptographic and/or hash
>    functions. 

So you could use another ICV for the new purpose, and handling for 
previous ICVs is already specified.

I don't think it's necessary to discourage mutable fields in reactive 
route discovery.  There have been many variations on AODV route 
discovery, and I can't think of any that didn't change the control 
messages as they were passed hop by hop from source to destination and back.

Regards,
Charlie P.

v2.23.0 | Report a Bug | By Email