public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
* [B.A.T.M.A.N.] point me to some OSI layer diagrams if possible ?
@ 2009-12-09 20:42 George Sanders
  2009-12-09 23:40 ` L. Aaron Kaplan
  0 siblings, 1 reply; 7+ messages in thread
From: George Sanders @ 2009-12-09 20:42 UTC (permalink / raw)
  To: b.a.t.m.a.n

I am researching meshes/MANETs, and the accompanying 802.11s/HWMP/olsr/etc.

Before asking any specific questions, I wonder if someone could point me to some proper OSI
diagrams that I cannot find - specifically:



- can someone draw, or direct me to, an OSI diagram showing an 802.11a/b/g/n network using 
plain old vanilla 802.11s + HWMP (no OLSR) to support an IP network ?



Then, for comparison:



- can someone draw, or direct me to, an OSI diagram showing an 802.11a/b/g/n network using
ONLY BATMAN (no 802.11s) ... ?



Finally, in my research I came across this very interesting conversation from 2006:

http://www.ietf.org/mail-archive/web/manet/current/msg08218.html

and I wonder, has that question:

"I agree, but we may still be able to pull it off without having to messup the stack."

been answered yet ?  Or is there still argument over whether or not some implementations require "discussion"
between components on different OSI layers ?

Thank you.


      


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2009-12-10  9:41 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-12-09 20:42 [B.A.T.M.A.N.] point me to some OSI layer diagrams if possible ? George Sanders
2009-12-09 23:40 ` L. Aaron Kaplan
2009-12-10  4:00   ` Marek Lindner
2009-12-10  4:28     ` [B.A.T.M.A.N.] [Olsr-users] point me to some OSI layer diagramsif " Bhat, Ishwara
2009-12-10  4:33       ` Marek Lindner
2009-12-10  4:55         ` Bhat, Ishwara
2009-12-10  9:41           ` L. Aaron Kaplan

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox