1 / 16

MEDIACTRL.IETF.70 - Vancouver, BC

Stay updated with the latest discussions and progress in the MEDIACTRL working group at IETF 70 in Vancouver, BC. Find meeting materials, agenda, notes, and more.

malcolml
Télécharger la présentation

MEDIACTRL.IETF.70 - Vancouver, BC

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. MEDIACTRL – IETF 70 Eric Burger eburger@bea.com Spencer Dawkins spencer@mcsr-labs.org

  2. Remote Logistics • mp3 Feed: SPEAK INTO THE MICROPHONE!!! • http://videolab.uoregon.edu/events/ietf/ietf706.m3u • Jabber • Server: jabber.ietf.org • Room: mediactrl • Logs: http://www.ietf.org/meetings/ietf-logs/mediactrl/ • Meeting Materials (Presentations, Agenda, etc.) • https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=70 • Supplemental Web Site • http://www.standardstrack.com/ietf/mediactrl MEDIACTRL IETF 70 - Vancouver, BC

  3. Scribes and Transcribes • Jabber Scribe • ??? • Note Taker • ??? MEDIACTRL IETF 70 - Vancouver, BC

  4. 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 3978 (updated by RFC 4748) and RFC 3979. 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 3978 (and RFC 4748) 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. MEDIACTRL IETF 70 - Vancouver, BC

  5. Agenda • Agenda Bash – (chairs) - 5 minutes • Chair Status - (chairs) - 30 minutes • Finishing Architecture - (Lorenzo) - 15 minutes • Discussion of ESCS – (Simon Romano) - 15 minutes • IVR Package – (Scott McGlashan) - 15 minutes • Next Steps – (all) - 10 minutes • IVR Design Team Meeting - (open) - remaining time MEDIACTRL IETF 70 - Vancouver, BC

  6. Getting a document published • The nits • Review inside the working group • Review outside the working group MEDIACTRL IETF 70 - Vancouver, BC

  7. Nits • Not just automatic checking • http://tools.ietf.org/tools/idnits/ • http://www.ietf.org/ID-Checklist.html • Because RFCs live forever • Don’t reference WGs – they go away • ID references are dependencies • Mandatory sections • Abstract, IANA considerations, • Realistic security • Normative/Informative References • Expand acronyms MEDIACTRL IETF 70 - Vancouver, BC

  8. Working Group review • Working Group Last Call • Optional, but we’re using them • Expect two-week WGLC for our docs • Expect some comments • Working Group Chair review • One chair as “document shepherd” • Shepherding checklist • Expect some comments MEDIACTRL IETF 70 - Vancouver, BC

  9. External review • AD review before IESG balloting • IETF Last Call • Sets off several area review teams • Comments not blocking unless ADs agree • IESG Balloting • Ballot positions (yes, no-obj, DISCUSS) • IESG comments – please be responsive • RFC Editor interaction • AUTH48 – please be responsive • Please keep WG and chairs in the loop! MEDIACTRL IETF 70 - Vancouver, BC

  10. Document Status • VoiceXML shepherd write-up • Mediactrl Requirements • AD Evaluation resulted in some comments • Transport independence for control channel • Put examples, e.g., not IPv4 addresses, not requiring disabling Nagle Algorithm, allowing SCTP, etc. • Need reasoning for multiple control channels • MSCML/MSML • Redundant data paths: why not just use SCTP? • Others? MEDIACTRL IETF 70 - Vancouver, BC

  11. Finishing Architecture Lorenzo Miniero

  12. Discussion of ESCS Simon Romano

  13. IVR Package Scott McGlashan

  14. Goals and Milestones MEDIACTRL IETF 70 - Vancouver, BC

  15. Next Steps • Do we need an interim? • IETF scheduling requirements means can only do it in January • 30 day notice means not December • 30 day blackout means not February • Maybe next time? MEDIACTRL IETF 70 - Vancouver, BC

  16. Thank You(and see you in Philadelphia) MEDIACTRL

More Related