[OLPC-devel] Re: [One Laptop Per Child] #7: Server and client IPv6 autoconfiguration

[Zarro Boogs per Child]

#7: Server and client IPv6 autoconfiguration
----------------------------+-----------------------------------------------
 Reporter:  jg              |        Owner:            
     Type:  task            |       Status:  new       
 Priority:  high            |    Milestone:  rev1 final
Component:  infrastructure  |   Resolution:            
 Keywords:                  |  
----------------------------+-----------------------------------------------
Comment (by ksankar):

 * Interesting and valid proposition. We can go v6 native and have the
 v4-v6 layers as needed

  * Ecstasies
   * The local network formation (address allocation, communication) is
 much simpler and robust in IPv6
   * Multicast semantics are better in v6 than in v4
   * Eventually our substrate needs to be v6 anyway
   * v6 has more traction in many countries outside US

  * Agonies
   * Apps need to be aware of v6 – mundane things like the addr structure,
 address string length et al
   * Infrastructure needs to be v6 aware as well
   * Mesh driver should support v6 primitives

  * Questions
   * Not having been in the discussions, what is our current thoughts on
 this ? Should we spend efforts on v6 ? At least we should make sure the
 mesh layer is v6 capable.
   * Are there v6 efforts going on ?
   * This also relates to Ivan's ticket of school server configuration
   * If we assume v4, are we planning on mDNS and a bonjour-like substrate
 ?

-- 
Ticket URL: <http://dev.laptop.org/ticket/7#comment:4>
One Laptop Per Child <http://laptop.org/>