Re: [manet] New Version Notification for draft-ietf-manet-timetlv-03

"Ian Chakeres" <ian.chakeres@gmail.com> Sun, 18 November 2007 09:55 UTC

Return-path: <manet-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ItgsR-0003JV-T5; Sun, 18 Nov 2007 04:55:43 -0500
Received: from manet by megatron.ietf.org with local (Exim 4.43) id 1ItgsP-0003Ip-TH for manet-confirm+ok@megatron.ietf.org; Sun, 18 Nov 2007 04:55:42 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ItgsO-0003If-Fp for manet@ietf.org; Sun, 18 Nov 2007 04:55:41 -0500
Received: from nf-out-0910.google.com ([64.233.182.184]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ItgsM-0005fk-44 for manet@ietf.org; Sun, 18 Nov 2007 04:55:40 -0500
Received: by nf-out-0910.google.com with SMTP id d21so1023900nfb for <manet@ietf.org>; Sun, 18 Nov 2007 01:55:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=UwPQcA6x8ckqSR4uC9eVscm4gMsSc/f1ln0vqZ2vELQ=; b=R7+Ve/N5iuY5BC2SltjQJDeNcU89TI7ppjQczEOWcYK56LDDPE+kYR8eWHlSIS7a6gdfzj2ttKn4NWWc/POPkQfS5q5MxPxFszkzMbIo/uCCuKP6Z5tdXOAdPc2W3EzYXi4fvHQSNQ5Q8intR4onwciP+RRTBL54dtdKBGVJpjk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=n+L3eNvGR/nI6E4tl+IoxrlUmXUXIEXfGrKpRDG1mIiJrdCeFuuPVlyX2jf89MIc2HV+TSahiXETzxGAxYAZRuA4fk797cKENolSv1R4nsStD3OiZVF+4pNV/srEVPBBSK9V/FLIcw1nv+bDAPYSV2Ts8WOtnlf4fY4ovquOeVw=
Received: by 10.78.134.2 with SMTP id h2mr3725279hud.1195379737120; Sun, 18 Nov 2007 01:55:37 -0800 (PST)
Received: by 10.78.19.9 with HTTP; Sun, 18 Nov 2007 01:55:37 -0800 (PST)
Message-ID: <374005f30711180155h60d58de3mfc2a8feba0479c2d@mail.gmail.com>
Date: Sun, 18 Nov 2007 15:25:37 +0530
From: Ian Chakeres <ian.chakeres@gmail.com>
To: manet@ietf.org
Subject: Re: [manet] New Version Notification for draft-ietf-manet-timetlv-03
In-Reply-To: <E1IshQL-0002f6-Nn@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <E1IshQL-0002f6-Nn@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: chris.dearlove@baesystems.com, T.Clausen@computer.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

I think it would be useful for TimeTLV to specify a method for
carrying 'C'. I understand that normally nodes (or implementations)
might be configured with 'C' for each TimeTLV type. For cases where C
is either unknown or required, I think we should specify a format for
carrying it. I see carrying C as most important when C
misunderstandings could cause routing to fail.

I believe there are several different options for encoding this
information. What do you think would be the best way?

Ian

On Nov 15, 2007 9:48 PM, IETF I-D Submission Tool <idsubmission@ietf.org> wrote:
>
> A new version of I-D, draft-ietf-manet-timetlv-03.txt has been successfuly submitted by Thomas Clausen and posted to the IETF repository.
>
> Filename:        draft-ietf-manet-timetlv
> Revision:        03
> Title:           Representing multi-value time in MANETs
> Creation_date:   2007-11-15
> WG ID:           manet
> Number_of_pages: 18
>
> Abstract:
> This document describes a general and flexible TLV (type-length-value
> structure) for representing time using the generalized MANET packet/
> message format.  It defines two message and two address block TLVs
> for representing validity and interval times for MANET routing
> protocols.
>
>
>
> The IETF Secretariat.
>
>
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
>


_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet