1. Planning RETF Meeting1 Planning RETF Presentation Problem Statement Problem Statement Solution Solution Proposal Proposal Next Steps Next Steps

2. Planning RETF Meeting2 Problem Lack of robotics building blocks is hindering a greater acceptance of mobile robot systems. Lack of robotics building blocks is hindering a greater acceptance of mobile robot systems. Most roboticists cannot leverage existing systems and software developments due to incompatible elements. Most roboticists cannot leverage existing systems and software developments due to incompatible elements. Hardware and software inconsistencies between systems providers create issues for developers. Hardware and software inconsistencies between systems providers create issues for developers. Standard robotics building blocks are not readily available. Standard robotics building blocks are not readily available.

3. Planning RETF Meeting3 Solution Create Specifications Create Specifications APIs and operational specifications for sensors, actuators, architectures, systems, networks, messaging systems, etc. APIs and operational specifications for sensors, actuators, architectures, systems, networks, messaging systems, etc. Create Open Source Software Create Open Source Software Working code with documented APIs and operation. Working code with documented APIs and operation.

4. Planning RETF Meeting4 Proposal Model the specification creation after IETF Model the specification creation after IETF Create Robotics Engineering Task Force - RETF Create Robotics Engineering Task Force - RETF RETF would produce specifications with a maturity level assigned to the spec. RETF would produce specifications with a maturity level assigned to the spec. Model software creation is open source Model software creation is open source RETF would not develop software. RETF would not develop software. RETF would list open source efforts and provide pointers to projects. RETF would list open source efforts and provide pointers to projects. RETF would encourage open source projects to go through GNU or Source Forge. RETF would encourage open source projects to go through GNU or Source Forge. Non-open source efforts would be aware of open source efforts. Non-open source efforts would be aware of open source efforts.

5. Planning RETF Meeting5 RETF Organizational Methods Collaboration is key. Collaboratively: Collaboration is key. Collaboratively: Develop reliable, interoperable robotics building blocks – components within a robot. Develop reliable, interoperable robotics building blocks – components within a robot. Develop meaningful systems in which robots operate reliably – robot within a ubiquitous computing environment. Develop meaningful systems in which robots operate reliably – robot within a ubiquitous computing environment. Create documented open source software and/or specifications. Create documented open source software and/or specifications. Rough consensus and working code drive adoption/acceptance of solutions. Rough consensus and working code drive adoption/acceptance of solutions.

6. Planning RETF Meeting6 Steering Committee RETF Organization Co- Presidents Area A Co-directors Work Group 2 Co-Chairs Work Group 1 Co-Chairs Area B Co-Directors Work Group 3 Co-Chairs Area C Co-Directors Work Group 5 Co-Chairs Work Group 4 Co-Chairs Steering Committee elects Co-Presidents every 2 years with stagger terms. Steering Committee elects ADs every 2 years with stagger terms. WG exists for 2-4 years. WGs are dynamically created as needed.

7. Planning RETF Meeting7 Steering Committee Areas Co- Presidents ArchitectureNavigation Distributed Systems SensorsSystems Mapping & Localization NetworkingVision Are these the correct Areas? Are they clear? IETF-Like

8. Planning RETF Meeting8 Roles and Responsibilities Co-Presidents Co-Presidents Travel to N (N=2 or 3) meetings per year. Travel to N (N=2 or 3) meetings per year. Ensure WGs and SC operate within their charters and within their defined procedures. Ensure WGs and SC operate within their charters and within their defined procedures. Area Director Area Director Travel to N (N=2 or 3) meetings per year. Travel to N (N=2 or 3) meetings per year. Email/phone conversations to filter WG proposals and submit good proposals to Steering Committee for approval/denial. Email/phone conversations to filter WG proposals and submit good proposals to Steering Committee for approval/denial. Ensure WGs and SC operate within their charters and within their defined procedures. Ensure WGs and SC operate within their charters and within their defined procedures. WG Chair WG Chair Make WG proposals to ADs to get an approved charter. Make WG proposals to ADs to get an approved charter. Lead the WG to produce deliverables as defined by the approved charter of the WG. Lead the WG to produce deliverables as defined by the approved charter of the WG. Travel to N meetings per year and preside over WG meetings. Travel to N meetings per year and preside over WG meetings. Ensure rough consensus and working code drive the deliverables. Ensure rough consensus and working code drive the deliverables. Individual Contributor Individual Contributor Individual Contributor (IC) may, or may not, be WG co-chair, WG co-chair of another WG or on the SC. Individual Contributor (IC) may, or may not, be WG co-chair, WG co-chair of another WG or on the SC. IC contributes to the production of deliverables. IC contributes to the production of deliverables. IC joins a WG by simply joining the WG mail list. IC joins a WG by simply joining the WG mail list. Once IC joins mail list, IC is RETF member. Once IC joins mail list, IC is RETF member. IC will confirm they have received copyright and IPR statements before being added to list. IC will confirm they have received copyright and IPR statements before being added to list.

9. Planning RETF Meeting9 Summarize Problem: no robotics building blocks. Problem: no robotics building blocks. Solution: create specs and open source software for robotics building blocks. Solution: create specs and open source software for robotics building blocks. Create RETF for specification production. Create RETF for specification production. Encourage open source software development. Encourage open source software development.

10. Planning RETF Meeting10 Status, Next Steps Status Status The organization listed in these slides is ideal. However, we are building up to that ideal from the bottom-up by forming working groups first. The organization listed in these slides is ideal. However, we are building up to that ideal from the bottom-up by forming working groups first. Had January meeting with about 40 people, discussion for working groups focused on API and protocols. Had January meeting with about 40 people, discussion for working groups focused on API and protocols. RETF mail list is created to discuss API and protocol work. Currently 15 subscribers. To subscribe send mail to listserv@mailbag.intel.com, no subject, one line message: subscribe RETF RETF mail list is created to discuss API and protocol work. Currently 15 subscribers. To subscribe send mail to listserv@mailbag.intel.com, no subject, one line message: subscribe RETF listserv@mailbag.intel.com Next steps Next steps Charter for RETF. Charter for RETF. Need initial proposals for APIs and protocols Need initial proposals for APIs and protocols Look into long-term funding from DARPA or other organization. Look into long-term funding from DARPA or other organization.