S Sivavakeesar | 6 Jan 2010 00:22

A Special Book on MANET QoS

For those who are interested in pursuing research on MANET QoS, a special book is now made available in amazon. Please check the following link for more details:

 

Short Blurb:

 

Mobile Ad hoc NETworks (MANETs) are going to change the way humans communicate and interact with each other. In the new era of ubiquitously present communication and computing facilities creating smart-spaces, mobile ad hoc networking will play a fundamental role to enable any-time, anywhere and anyone networking. QoS provisioning in such networks is important in order to reap the real-benefits of this new class of networking. QoS is a multi-layer problem in MANETs and hence, it needs to be analysed in multiple dimensions by taking a holistic approach. This monograph therefore delves into this QoS issue step-by-step with a view to explain the complex problem in a very simple way. In this respect, this monograph will become a vital asset for any body to really understand this evolving communication and computing system.
 
Thanks and sorry for the wide circulation.
 
Dr Siva Vakeesar


_______________________________________________
manet mailing list
manet <at> ietf.org
https://www.ietf.org/mailman/listinfo/manet
Ian Chakeres | 29 Jan 2010 20:28
Picon

NHDP Plan

Within the next few weeks I plan to submit the writeup for NHDP. Although, I have voiced some concerns about
NHDP, I believe that the group has reached consensus on the document.

I look forward to moving this document forward to the IESG, and seeing you all in Anaheim.

Thanks.
Ian Chakeres
Ian Chakeres | 29 Jan 2010 20:30
Picon

My DYMO Plan

I am planning to refresh the DYMO draft. My goal is prepare the draft for WGLC and IESG. I aim to tie up any loose
ends, and ensure that that the packet format diagrams conform to the PacketBB RFC.

I intend to retain the DYMO identifier (DID) to help ensure consistent configuration among participating
DYMO nodes. I had hoped that the several of the MANET protocols would incorporate an ID field for this
purpose, but I have not seen strong support for adding this concept into the other MANET protocols.

If you have any feedback on the existing DYMO draft, please feel free to email me your comments/suggestions.

Thanks.
Ian Chakeres
Justin Dean | 29 Jan 2010 22:17
Picon
Picon

Re: My DYMO Plan

Have you thought about using moving/merging the DID into the security TLV
document (currently personal draft) which does key exchanges also.
Basically use it as a fancy pants identifier.  Although I think that would
be a good spot for a DID type of behavior to live.  Giving a basic or
fallback mode of operation to the security TLV document when keys aren't
available or processing isn't up to the task to do simple ID behaviors would
be a good thing IMO.  It doesn't distinguish between DYMO "areas" but it
could be used for network wide configuration and the DymoID could then be
used as well.

Justin

> -----Original Message-----
> From: manet-bounces <at> ietf.org [mailto:manet-bounces <at> ietf.org] On Behalf
> Of Ian Chakeres
> Sent: Friday, January 29, 2010 2:30 PM
> To: MANET IETF
> Subject: [manet] My DYMO Plan
> 
> I am planning to refresh the DYMO draft. My goal is prepare the draft
> for WGLC and IESG. I aim to tie up any loose ends, and ensure that that
> the packet format diagrams conform to the PacketBB RFC.
> 
> I intend to retain the DYMO identifier (DID) to help ensure consistent
> configuration among participating DYMO nodes. I had hoped that the
> several of the MANET protocols would incorporate an ID field for this
> purpose, but I have not seen strong support for adding this concept
> into the other MANET protocols.
> 
> If you have any feedback on the existing DYMO draft, please feel free
> to email me your comments/suggestions.
> 
> Thanks.
> Ian Chakeres
> _______________________________________________
> manet mailing list
> manet <at> ietf.org
> https://www.ietf.org/mailman/listinfo/manet
Ian Chakeres | 29 Jan 2010 23:35
Picon

Re: My DYMO Plan

I support the security TLV concept, but I feel that the DID concept
needs to be part of the base protocol document. Implementing DID as an
extension reduces its usability because one implementation could not
depend on another implementation/configuration to take the proper
action.

As you mentioned, I believe both the security-TLV and DID are
complementary tools.

Thanks.
Ian Chakeres

On Fri, Jan 29, 2010 at 4:17 PM, Justin Dean <jdean <at> itd.nrl.navy.mil> wrote:
> Have you thought about using moving/merging the DID into the security TLV
> document (currently personal draft) which does key exchanges also.
> Basically use it as a fancy pants identifier.  Although I think that would
> be a good spot for a DID type of behavior to live.  Giving a basic or
> fallback mode of operation to the security TLV document when keys aren't
> available or processing isn't up to the task to do simple ID behaviors would
> be a good thing IMO.  It doesn't distinguish between DYMO "areas" but it
> could be used for network wide configuration and the DymoID could then be
> used as well.
>
> Justin
>
>> -----Original Message-----
>> From: manet-bounces <at> ietf.org [mailto:manet-bounces <at> ietf.org] On Behalf
>> Of Ian Chakeres
>> Sent: Friday, January 29, 2010 2:30 PM
>> To: MANET IETF
>> Subject: [manet] My DYMO Plan
>>
>> I am planning to refresh the DYMO draft. My goal is prepare the draft
>> for WGLC and IESG. I aim to tie up any loose ends, and ensure that that
>> the packet format diagrams conform to the PacketBB RFC.
>>
>> I intend to retain the DYMO identifier (DID) to help ensure consistent
>> configuration among participating DYMO nodes. I had hoped that the
>> several of the MANET protocols would incorporate an ID field for this
>> purpose, but I have not seen strong support for adding this concept
>> into the other MANET protocols.
>>
>> If you have any feedback on the existing DYMO draft, please feel free
>> to email me your comments/suggestions.
>>
>> Thanks.
>> Ian Chakeres
>> _______________________________________________
>> manet mailing list
>> manet <at> ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>
>
>

Gmane