mmusic wg
play

MMUSIC WG 47th IETF 30 March 2000 - Adelaide 30 March 2000 MMUSIC - PowerPoint PPT Presentation

MMUSIC WG 47th IETF 30 March 2000 - Adelaide 30 March 2000 MMUSIC WG 1 MMUSIC Agenda 1530 Agenda Bashing & Status Update (chair, 5) 1535 SAPv2 Review -06 (Perkins, 15) draft-ietf-mmusic-sap-v2-06.txt 1550 Issue: SAP Server Access


  1. MMUSIC WG 47th IETF 30 March 2000 - Adelaide 30 March 2000 MMUSIC WG 1

  2. MMUSIC Agenda 1530 Agenda Bashing & Status Update (chair, 5) 1535 SAPv2 Review -06 (Perkins, 15) draft-ietf-mmusic-sap-v2-06.txt 1550 Issue: SAP Server Access Protocol (chair, 5) 1555 SDP Directory Type (Finlayson, 15) draft-ietf-mmusic-sdp-directory-type-00.txt 1610 SDP Source Filter List (Thaler, 20) 1630 ATM QoS in SDP (Taylor, 10) draft-rajeshkumar-mmusic-sdp-atm-00.txt 1640 SDP Codec Capability Attribute (Beser, 10) draft-beser-mmusic-capabilities-00.txt 30 March 2000 MMUSIC WG 2

  3. MMUSIC Agenda 1650 RTSP Fixes & Clarifications (Rao, 10) RFC 2326 1700 RTSP Extensions (10) draft-sheedy-mmusic-rtsp-ext-00.txt 1710 RTSP Caching (15) draft-periyannan-rtsp-caching-06.txt 1725 Moving forward with RTSP (chair, 5) 1730 Wrap up 30 March 2000 MMUSIC WG 3

  4. WG Status Update • Mailing list is about to move – mmusic@informatik.uni-bremen.de – Majordomo administered list • Please subscribe to the new list – there will be no automatic transfer – mails will be forwarded from confctrl@isi.edu for some time to come • Details to be announced after IETF 30 March 2000 MMUSIC WG 4

  5. MMUSIC Charter Well, we should have a new charter by now… But: Scope may be perceived too broad. Right now… Working with IESG to sort this out. More to be seen on the list shortly. 30 March 2000 MMUSIC WG 5

  6. SAP Issue: Server Access • SAP is really a Server-Server protocol – SAP announcements infrequently – takes time to learn about sessions – announcements often depend on eg SDR processes to stay around • SAP Server Access Protocol needed – allow client to initiate announcement – receive (selected) SAP announcements • unsolicited or on-demand – support for directories?, security, ... 30 March 2000 MMUSIC WG 6

  7. RTSP (1) • Cleaning up the spec (for draft?) – Fix inconsistencies – Fix bugs – Provide clarifications where needed • Overview of implementations – What is really implemented? • Remove unnecessary parts from the spec – Demonstrate interoperability – Satisfy preconditions to go to Draft 30 March 2000 MMUSIC WG 7

  8. RTSP (2) How many documents? • Base spec for Draft? – Limits requiring a cycle in Proposed? • Extensions for other Transports – Generalization needed – Necessary fixes to go into base spec – Remaining stuff: separate doc (if any) • Caching – keep as separate spec 30 March 2000 MMUSIC WG 8

Recommend


More recommend