1 / 17

Yet Another Mail

Working Group IETF 78 July 29, 2010. Yet Another Mail. Note Well.

myles-beck
Download Presentation

Yet Another Mail

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Working Group IETF 78 July 29, 2010 Yet Another Mail

  2. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: the IETF plenary session, any IETF working group or portion thereof, the IESG or any member thereof on behalf of the IESG, the IAB or any member thereof on behalf of the IAB, any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 5378 and RFC 3979 (updated by RFC 4879). Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 5378 and RFC 3979 for details. A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements. A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public.

  3. Pass the blue sheets around We have a secretary to take notes  Need a jabber channeler

  4. Finding Yammerers • Mailing List: • yam@ietf.org • Jabber: • xmpp:yam@jabber.ietf.org • Audio Stream: • http://videolab.uoregon.edu/events/ietf/ietf785.m3u • Meeting Materials: • https://datatracker.ietf.org/meeting/78/materials.html#wg-yam • WG Wiki • http://trac.tools.ietf.org/wg/yam/trac/wiki

  5. Agenda 60 minutes – 15:10 – 16:10 Note well - 1 minute Agenda bashing - 4 minutes Mime Expert Review of image/svg+xml – 10 minutes Two-Track/Plenary Redux – 45 minutes

  6. image/svg+xml • Mime Expert Review

  7. Document Status • Since IETF 77 • Pre-eval IDs published • 4409 (submit) • 5321 (smtp) – reviewed by IESG • 5322 (format) • Additional work sidelined by Two-Track uncertainties

  8. Our WG’s Goals Advance documents to Full Standard Fixing things as needed Process Experiment Experiment on a way to get documents moved to Full Standard Act as a catalyst

  9. “If you don’t know where you are going, you could end up somewhere else.” • – Yogi Berra

  10. Two-Track / Plenary Redux • draft-housley-two-maturity-levels-01 • Only two levels: • Proposed Standard • Internet Standard • 6 month wait no longer required • Existing Draft Standards moved immediately to Full Standard

  11. Plenary Redux • Lots of support for going to two levels at the plenary • Not clear where discussion will continue, when consensus would be called, or when and how the issue would be decided

  12. If Two-Track Goes Through… • We’re done! • Or are we?

  13. If Two-Track Goes Through… • Some of the docs really do need work to be done on them • For example, • Minor clarifications for 4409, 5321, 5322 • MIME • MDN • However, republishing a “Full Standard” doc is sometimes troublesome • Can instead get the update work done by issuing “Update documents” instead

  14. If Two-Track Goes Through… • Yes, if we choose to do this other type of work, it does require a recharter • We’ve also always said that after YAM’s current charter is finished, we would then consider progressing various Proposed Standard docs forward • Is now the time?

  15. “Conditions are never just right. People who delay action until all factors are favorable do nothing.” – William Feather

  16. Where are we? • Two-Track has not been adopted yet • Should indecision there prevent work finishing up 4409bis, 5321bis, 5322bis? • These could be finished long before we get a decision on Two-Track • Or maybe not. How’s your crystal ball?

  17. Open Mike • “It is a paradoxical but profoundly true and important principle…that the most likely way to reach a goal is to be aiming not at that goal itself, but at some more ambitious goal beyond it.” – Arnold Toynbee “It's always too early to quit.” – Dr. Norman Vincent Peale

More Related