CLUE WG Interim Meeting San Jose, CA Sept , 2012

Slides:



Advertisements
Similar presentations
IETF Calsify.
Advertisements

DISPATCH WG RTCWEB Adhoc IETF-80. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft.
L2VPN WG “NVO3” Meeting IETF 82 Taipei, Taiwan. Agenda Administrivia Framing Today’s Discussions (5 minutes) Cloud Networking: Framework and VPN Applicability.
CCAMP Working Group Online Agenda and Slides at: Tools start page:
IETF 90: NetExt WG Meeting. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet- Draft.
CLUE WG IETF-89 Mary Barnes (WG co-chair) Paul Kyzivat (WG co-chair)
SIPCLF Working Group Spencer Dawkins Theo Zourzouvillys IETF 76 – November 2009 Hiroshima, Japan.
CLUE WG IETF-91 Paul Kyzivat (WG co-chair) Mary Barnes (WG co-chair)
CLUE WG IETF-84 Mary Barnes (WG co-chair) Paul Kyzivat (WG co-chair)
GROW IETF 78 Maastricht, Netherlands. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft.
SIPREC WG, IETF# , GMT+2 John Elwell (WG co-chair) Brian Rosen (WG co-chair)
CCAMP Working Group Online Agenda and Slides at: Data tracker:
Web Authorization Protocol (oauth) Hannes Tschofenig.
CLUE WG IETF-83 Mary Barnes (WG co-chair) Paul Kyzivat (WG co-chair)
IETF 89, LONDON, UK LISP Working Group. 2 Agenda and slides:  lisp.html Audio Stream 
CLUE WG chair: Mary Barnes RTCWEB WG chair: Ted Hardie CLUE & RTCWEB WGs Adhoc Common (SDP/RTP) building blocks IETF-82.
DMM WG IETF 84 DMM WG Agenda & Status Tuesday, July 31 st, 2012 Jouni Korhonen, Julien Laganier.
Interface to the Routing System (IRS) BOF IETF 85, Atlanta November 2012.
IETF #81 - NETCONF WG session 1 NETCONF WG IETF 81, Quebec City, Canada MONDAY, July 25, Bert Wijnen Mehmet Ersue.
IETF #82 - NETCONF WG session 1 NETCONF WG IETF 82, Taipei, Taiwan TUESDAY, November 15, Afternoon Session III Bert Wijnen Mehmet Ersue.
Agenda Stig Venaas Behcet Sarikaya November 2011 Multimob WG IETF
TSVAREA IETF84 - Vancouver. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft.
CLUE WG IETF-85 Mary Barnes (WG co-chair) Paul Kyzivat (WG co-chair)
Audio/Video Transport Extensions (avtext) Working Group Keith Drage Magnus Westerlund Jabber room:
OPSAWG chairs: Scott Bradner Christopher Liljenstolpe.
Agenda Wednesday, July 29, :00 – 15:00 Congresshall B Please join the Jabber room: LEDBAT WG IETF 75.
Emergency Context Resolution with Internet Technologies (ECRIT) Chairs: Marc Linsner & Roger Marshall Standing In for the Chairs: Brian Rosen IETF 94.
STIR Secure Telephone Identity Revisited
WG Chairs Forum Wednesday 29 March 2017.
LMAP WG IETF 97 – Seoul, SK November 17, 2016 Dan Romascanu Jason Weil
CLUE WG Interim Meeting San Jose, CA Sept , 2012
Agenda Stig Venaas Behcet Sarikaya November 2010
CLUE WG Interim Meeting San Jose, CA Sept , 2012
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.
Chairs: Derek Atkins and Hannes Tschofenig
SIPREC WG, Interim virtual meeting , GMT-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.
TRILL Working Group TRansparent Interconnection of Lots of Links
Extensible Messaging and Presence Protocol (XMPP) WG
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.
Agenda OAuth WG IETF 87 July, 2013.
Mary Barnes (WG co-chair) Paul Kyzivat (WG co-chair)
MODERN Working Group IETF 97 November 14, 2016.
CAPWAP Working Group IETF 73 Minneapolis 18 Nov 2008, 17:10-18:10
Kathleen Moriarty, Trusted Execution Environment Provisioning (TEEP) BoF IETF-100 November 2017 Chairs: Nancy Cam-Winget,
SPRING IETF-98 Tuesday, March 28.
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.
Singapore – IETF 100 – November 2017
Thursday, 20th of July 2017.
Binary Floor Control Protocol BIS (BFCPBIS)
16th November 2016 Gorry Fairhurst (via webrtc) David Black WG chairs
Agenda IETF 82 Taipei November 14, 2011
Multiple Interfaces (MIF) WG
NETMOD Agenda and WG Status
JSON Object Signing and Encryption (JOSE) Working Group
SIPREC WG, Interim Meeting , GMT/UTC
Flexible Ethernet (Side meeting)
IETF DTN Working Group July 17th, 2017 Chairs:
20th July 2017 Gorry Fairhurst Wes Eddy David Black WG chairs
SIPREC WG, Interim virtual meeting , GMT
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.
TEAS CCAMP MPLS PCE Working Groups
James Polk Gorry Fairhurst
SIPBRANDY Chair Slides
Multiple Interfaces (MIF) WG
IETF80.
Scott Bradner & Martin Thomson
NETCONF WG IETF 80, Prague, Czech Republic March 31,
IETF 100 Singapore MBONED.
Audio/Video Transport Extensions (avtext) Working Group
Presentation transcript:

CLUE WG Interim Meeting San Jose, CA Sept. 19-20, 2012 Mary Barnes (WG co-chair) Paul Kyzivat (WG co-chair)

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.

Agenda (day 2) 09:00-9:30 Issue Summary from Wednesday 09:30-10:30 Updated tele-medical call flow based on Paul's new proposal 10:30-10:45 Break (with coffee/snacks) 10:45-12:30 Key Issue Discussion (continued) 12:30-12:45 Break (with coffee/snacks) 12:45-14:00 Discussion of way forward and summary of action items

Issues/items for further discussion Need to decide whether advertisement is complete information "all" or just a "delta" [Note: current framework is "all"] Can the FW explicitly restrict the use of Simulcast? Site Switching: there is an issue when you have multiple captures and do site switching. It needs to be consistent. May need real-time updates (e.g., RTCP, XCON notifications).

Issues/items for further discussion Call Flow: Do we need a way to reject a Configure message? Call Flow: How do we signal support for Clue? Call Flow: What is advantage of not having a 3rd O/A exchange in the session setup? Call Flow: Must the configuration be consistent with the current SDP?

Issues/items for further discussion Ticket #12: What CLUE information is carried in SDP? What CLUE-specific information should be in an initial SDP? What additional CLUE-specific information should be in subsequent SDPs? Ticket #13: What CLUE information is carried in CLUE specific signaling? Ticket #15: What signaling protocol should be used for the CLUE information? General agreement to use XML schema.

Way Forward for work items (afternoon) Agreement on way forward for RTP Agree the data necessary to be exchanged (independent of signaling solution) CLUE Instance model may help to determine when and what signaling is required (e.g., based on user actions) Media stream model will inform signaling solution Agree the basic signaling model, with the following considerations: interworking with non-CLUE endpoints Reusability and interworking with other multi-stream applications (e.g., RTCWEB) Use call flows and data model to understand signaling details.

Going Forward Action items with assignees identified Document authors assigned to produce target WG drafts reflecting consensus to date.