Subject: Re: [manet] Metric TLVs for DLEP

From: Abdussalam Baryun <[email-masked]>
Date: Sat, 19 Jan 2013 14:14:53 +0100

++++++++++++++    First Reminder  +++++++++++++++++

Hi Authors of DLEP, and All

I wish to see your reply/respond in this thread about the proposal,
please note that it has been now 3 months delay with no response from
the editor or authors. Your respond is required in my opinion for
progress, please advise,

*Please note that the DLEP submission milestone is March 2013*

Regards

Abdussalam Baryun
University of Glamorgan, UK
++++++++++++++++++++++++++++++++++++++++++++++++
On 11/20/12, Henning Rogge <[email-masked]> wrote:
> Hi,
>
> as discussed during the IETF, here a few thoughts about additional
> metric TLVs.
>
> I think that including a larger set of metric TLVs (like Relative Link
> Quality, Current/Maximum Datarate, ...) is a good thing, because it
> allows radio/router implementors to choose from a larger set of
> standardized TLVs, which increase the chance of interoperability between
> the products.
>
> There are two kinds of metric TLVs, one of them contain information
> about the network the radio is attached to and one of them contain
> information about the link of the radio to a target.
>
> Network specific metric TLVs
> ----------------------------
>
> * network-id
>
> A binary identifier of the network the radio is attached to (1-16 octets
> binary)
>
> * network-description
>
> A text identifier of the network the radio is attached to (1-80 octects
> ascii)
>
> * supported-rates
>
> An array of datarates supported by the radio on the current network
> (array of 8 octet values in bit/s)
>
> * last-active
>
> Time since the last data was sent or received over the radio (4 octet
> value in milliseconds)
>
> * frequency
>
> Mid-Frequency of the current radio channel (8 octet value in Hz)
>
> * bandwidth
>
> Amount of spectrum a radio channel uses (8 octet value in Hz)
>
>
> Neighbor specific metric TLVs
> -----------------------------
>
> * maximum-datarate
>
> This one already exists in DLEP, but doesn't report both incoming and
> outgoing maximum link speed, which could be different.
>
> * current-datarate
>
> Same as maximum datarate, incoming and outgoing speed can be different.
>
> * traffic
>
> Amount of bytes sent and received with the neighbor (8+8 octet value)
>
> * packets
>
> Amount of IP packet sent and received with the neighbor (8+8 octet value)
>
> * frames
>
> Amount of layer-2 frames sent and received with the neighbor (8+8 octet
> value)
>
> * tx-retries
>
> Number of linklayer retransmissions for IP packets (8 octet value)
>
> * tx-fails
>
> Number of failed linklayer transmissions
>
> * last-active
>
> Time since the last data was sent or received with this neighbor (4
> octet value in milliseconds)
>
> ----------------------
>
> The traffic and packet TLVs become important when you have multiple
> routers of hosts attached to a DLEP capable radio, because they cannot
> track the traffic on their local interface anymore.
>
>
> Henning Rogge
> --
> Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
> Kommunikation, Informationsverarbeitung und Ergonomie FKIE
> Kommunikationssysteme (KOM)
> Fraunhofer Straße 20, 53343 Wachtberg, Germany
> Telefon +49 228 9435-961,   Fax +49 228 9435 685
> mailto:[email-masked] http://www.fkie.fraunhofer.de
>
>