----- Original Message ----- From: "Philippe Houdoin" <philippe.houdoin@xxxxxxx> To: <openbeosnetteam@xxxxxxxxxxxxx> Sent: Wednesday, April 30, 2003 6:05 PM Subject: [openbeosnetteam] Re: Fw: [ge-talk]Networking futures > > > But, what should be (or would be better if) placed into the stack > > itself? > > > > IMHO nothing :-) It should be a module using network services. > > I don't see why it should be "integrated" at a network level... > > Opinion shared here. > > > For 802.1x or EAP it makes more sense to integrate with the stack but > > I can't see why for LDAP (behalfe for protocol issues...) > > I'm starting to wondering what change may be necessary to current stack design > to include wireless interfaces & protocols. > > > > LDAP support? I'm not LDAP fluent myself, in what's it's can be > > considered similar to DHCP and/or DNS? > > > > Do you mean at a protocol point of view ? or functional ? > > Functionnal. What's a LDAP strong integration into our stack will give us? > I was more inclined to add ZeroConf (aka RendezVous in Apple lingua) support, > which I see a more obvious bonus for a desktop os user. > Not so many have LDAP server(s) on their LAN or WAN yet, no? > Or did I (completly) miss something? Postings on glasselevator are future thoughts, remember? If we want to scale to hunderds or even thousands of users (Im an optimist), we need a way to keep things managable. LDAP would be the most logical way. ZeroConf/RendezVous sounds great indeed, and I too think we should include it. > > -Philippe > > >