Presentation is loading. Please wait.

Presentation is loading. Please wait.

RUCUS BOF IETF-71 IETF Exploratory Groups Bernard Aboba Microsoft Corporation Laksminath Dondeti Qualcomm, Inc. March 10, 2008 Philadelphia, PA.

Similar presentations


Presentation on theme: "RUCUS BOF IETF-71 IETF Exploratory Groups Bernard Aboba Microsoft Corporation Laksminath Dondeti Qualcomm, Inc. March 10, 2008 Philadelphia, PA."— Presentation transcript:

1 RUCUS BOF IETF-71 IETF Exploratory Groups Bernard Aboba Microsoft Corporation Laksminath Dondeti Qualcomm, Inc. March 10, 2008 Philadelphia, PA

2 What are Exploratory Groups? An RFC 3933 experiment, defined in RFC 5111 Experiment runs until July 2009 IESG may approve as many as 3 EGs. Intermediate step between a BOF and a WG Focused on completion of pre-requisites for WG formation May be created as the first step to WG formation or an intermediate step between an initial BOF and WG creation. Formation of an EG after a second BOF not recommended. Does not alter Working Group formation guidelines or the Internet Standards Process.

3 When To Consider an EG? Demonstrated relevance and interest to the IETF and Internet community. One or more WG formation criteria outlined in RFC 2418 Section 2.1 have not yet been met: Need for good understanding of existing work Need to improve clarity or achievability of goals Need to resolve overlap with existing WGs or standards bodies Need for clarity on status Formal recognition of the effort. Mechanism to track progress toward WG creation. Public IAB and IESG feedback on proposed charter, WG formation criteria.

4 Exploratory Group Milestones EGs have a short life-time with limited opportunities for milestone extension. Recommended initial charter: 6 (default) – 12 months Extensions beyond another 6 months not recommended. Recommended “Basic Milestones” Proposed WG Charter. Document demonstrating fulfillment of the WG formation criteria described in RFC 2418 Section 2.1. Optional milestones Problem statement document. Review of the literature or current practices. Note: should not put basic milestones at risk! Forbidden Milestones relating to development of a standards track protocol specification.

5 Exploratory Groups handled identically to Working Groups No additional burden imposed on IETF Secretariat. Exploratory Group names should include “EG” within the name (example: EXAMPLEEG). Operating rules (openness, meeting requirements, etc.) identical to WGs. Review of EG documents utilizes same tracking tools and processes (including PROTO sheparding). Process for formation of an Exploratory Group identical to that of a WG Review by the IAB and IESG Announcement of potential EG Request for review by the IETF community Exploratory Group Mgmt

6 Success Metrics Progress on basic milestones Completion within the time frame specified in the initial EG charter. Positive feedback from the IESG, IAB and IETF community. Mailing list activity Evidence of continued engagement. WG formation!

7 Tips for a Successful EG Focus on basic milestones Eyes on the prize: WG formation. Plan for completion of basic milestones within the initial 6-12 month time frame. Only add optional milestones if they won’t delay progress on basic milestones. Maintain high energy level Exploratory Groups are a sprint, not a marathon! Do not assume that the IESG will extend basic milestones!

8 Feedback?


Download ppt "RUCUS BOF IETF-71 IETF Exploratory Groups Bernard Aboba Microsoft Corporation Laksminath Dondeti Qualcomm, Inc. March 10, 2008 Philadelphia, PA."

Similar presentations


Ads by Google