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

I read the NHDP and OLSv2 documents and found out the intention of not
specifying C in timetlv.
C is really a constant and a protocol defines it for a particular usage.
Multiple protocols or different timetlv usages are free to define their own
constant.
But this constant shall be fixed and there is no need for signaling. Nor
configuration. It shall be hard coded.
Maybe adding some text to circumvent any misunderstanding, explaining there
is no need for signaling?

Maybe a protocol has a need for a variable V, replacing the constant C.
Then, that protocol shall implement signaling for V.

Teco.

> -----Oorspronkelijk bericht-----
> Van: Ian Chakeres [mailto:ian.chakeres@gmail.com]
> Verzonden: zondag 18 november 2007 10:56
> Aan: manet@ietf.org
> CC: chris.dearlove@baesystems.com; T.Clausen@computer.org
> Onderwerp: Re: [manet] New Version Notification for draft-ietf-manet-
> timetlv-03
> 
> 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

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