[olsr-dev] OLSRv2

Sat Dec 30 20:11:24 CET 2006

Hi 

I have a question too,
- Is OLSR-2 the followup of OLSR or just a paraphrase of OLSR ? what are the differences between all three?
- I read about the new Ieee 802s or what it was called and it was stated, that a routning on a MAC-Level is better than a routing on a IP level. Why is OLSR then not switching?
- The "Auto-Discover-Feature" (flooding the network and knowing all IP/mac adresses) means as well to sign all IP adresses, why not or which of the three protocols is integrating this? As I read in the wikipedia, both draft standards for the 802.s for 2008 would contain this. As well the OLPC Meshing driver from marvell will include this.
- Marvell could be open source, just needs a porting: see the threadstart here: http://mailman.laptop.org/pipermail/devel/2006-December/003390.html

Wouldn´t it be cool, to have an open source meshing network on the www.laptop.org ?

tom
-------- Original-Nachricht --------
Datum: Sat, 30 Dec 2006 15:57:39 -0300
Von: "Weverton Cordeiro" <(spam-protected)>
An: "OLSR development" <(spam-protected)>
Betreff: Re: [olsr-dev] OLSRv2

> Hi all,
> 
> The last message sent in the list brought me some doubts about the
> technical
> details of olsrd.
> 
> First: in http://www.olsr.org/docs/README-Link-Quality.html it is
> discussed
> about the Link Quality Extension to OLSR and how it is implemented in
> olsrd.
> But according to the text mentioned by Andreas in his last message (the
> one
> posted by Elektra about the history of olsr), I believe the document that
> talks about the link quality extension is a little outdated, because it
> makes mention of MPR as being part of olsrd. Maybe the documentation has
> wrong information about olsrd. My question is: was the MPR concept
> completely banned from olsrd (I mean, when olsrd does not work just as
> specified by RFC 3626)? Since which version of olsrd was the MPR concept
> banned?
> 
> Second: making a search in the message archive of the OLSR.ORG mailing
> lists
> I found the message at
> http://www.olsr.org/pipermail/olsr-users/2004-November/000317.html that
> also
> mentions about MPRs. That e-mail refers about the 0.4.8 version of olsrd,
> which I believe is not too far from the current version. Where I could
> find
> documentation that really describes the technical details of olsrd in a
> broader view?
> 
> Third: how does olsrd calculate the link quality values and the ETX for a
> given path? The e-mail I have mentioned earlier contradicts the Link
> Quality
> documentation of olsrd. For example, while the e-mail says the ETX value
> for
> a given path is the multiplication of the ETX value for every hop along
> the
> path, the Link Quality extension document says the total ETX value for a
> given path is the sum of the ETX calculated at every hop along the path.
> Needless to say that ETX values for each hop in the path are calculated
> far
> different.
> 
> Once and again talking about MPRs, what was the heuristic used to
> calculate
> the MPR set in olsrd, when using the Link Quality extension? Have you seen
> at IEEE digital library papers that discuss new methods of calculating the
> MPR set? Some of them are quite interesting, I think, as they discuss ways
> of making nodes with good conectivity or low delay to their neighbors
> being
> selected as MPRs by the current node. The best proposal I have seen so far
> as the QOLSR and QOLSR+. Do you have any words about it? Or could someone
> even point me the thread in which this subject was previously discussed in
> the list.
> 
> Thanks in advance,
> 
> On 12/27/06, Andreas Tønnesen <(spam-protected)> wrote:
> >
> >
> > Without having read the draft, I belive OLSRv2 is still based on
> > the concept of MPRs. Real life experience has shown that this
> > concept is not a very successfully one. As olsrd has moved along
> > from a more or less theoretical test implementation to a real-life
> > experiment it has become something very different from RFC3626.
> >
> > So even though OLSRv2 is definetly something to have an eye on,
> > I do not believe it will be implemented as part of olsrd. Read more
> > about the real-life experiments and the extensions needed for
> > olsrd to work properly in real-life meshes at:
> >
> >
> https://www.open-mesh.net/optimized-link-state-routing-deamon/olsr-story.txt/view
> >
> > My guess is that B.A.T.M.A.N. will have taken over for olsrd by
> > the time OLSRv2 reaches RFC :-)
> >
> > Anyway, that is my $0.02...
> >
> > - Andreas
> >
> > Zeus Gómez Marmolejo wrote:
> > > Hi,
> > >
> > > Although it's still an IETF draft -not an RFC-, OLSR version 2 is
> > > already submitted. Should it be considered to be included in olsrd?!
> > > It has some major improvements about the network-wide broadcast of
> > > link-state information and mantaining partial link-state information
> > > on each node.
> > >
> > > I think you should have an eye on the draft:
> > >
> > > http://www.ietf.org/internet-drafts/draft-ietf-manet-olsrv2-02.txt
> > >
> > > What do you think about??
> > >
> > >
> > >
> > > Zeus.
> > >
> > > _______________________________________________
> > > olsr-dev mailing list
> > > (spam-protected)
> > > https://www.olsr.org/mailman/listinfo/olsr-dev
> >
> >
> > _______________________________________________
> > olsr-dev mailing list
> > (spam-protected)
> > https://www.olsr.org/mailman/listinfo/olsr-dev
> >
> 
> 
> 
> -- 
> Weverton Luis da Costa Cordeiro
> Undergraduating in Computer Science
> Federal University of Para - UFPA
> http://www.labes.ufpa.br/weverton

-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer