1 / 7

CLUE WG IETF -86

CLUE WG IETF -86. Mary Barnes (WG co-chair ) Paul Kyzivat (WG co-chair ). Day 2 – Thursday, March 14, 2013. Note Well.

bert
Download Presentation

CLUE WG IETF -86

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. CLUE WGIETF-86 Mary Barnes (WG co-chair) Paul Kyzivat (WG co-chair) Day 2 – Thursday, March 14, 2013

  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. Agenda - Thursday (13:00-15:00) 13:00-13:10 Agenda bash(Chairs) 13:10-13:30 Requirements: draft-jennings-mmusic-media-req-00 13:30-14:30 Design Team Readout: Evaluating Proposals (Rob Hansen) 14:30-15:00 Way Forward and Wrap-up(Chairs)

  4. Status • Requirements document: • Need to identify security threats and where the solution will be described. • Need a volunteer (other than a chair) • Use Cases: • needs a keep-alive revision • Needs WG review for readiness for WGLC

  5. Status 3. Framework document (near completion) • Updates based upon WG decisions/consensus on Monday • Chairs need to close relevant issues in tracker • Ready for WGLC after appropriate text moved to other documents • RTP document: draft-ietf-clue-rtp-mapping-00.txt - NeedWG review and feedback (cross WG review?)

  6. Status - solutions 5. Data model: • Need WG review/feedback on -03 • Call for readiness as a WG document 6. Signaling document: • Update to include Option 2 (from draft-hansen-clue-sdp-interaction) • Updates based on discussion in CLUE WG and consideration of any MMUSIC WG decisions on Friday [Note: CLUE should attend joint AVTEXT/MMUSIC WG session on Friday. ]

  7. Way Forward • Need additional volunteers to work on deliverables • Regular design team calls: • Review key issues from WGLCs • Focus will be on signaling solution in particular MMUSIC/AVT key dependencies (may invite other folks working on these solutions) 3. Interim meeting: • Chairs will post a doodle to determine feasibility (virtual or f2f): • contact chairs if you are willing to host

More Related