Real-Time Streaming Protocol draft-ietf-mmusic-rfc2326bis-01.txt Magnus Westerlund.

Slides:



Advertisements
Similar presentations
1 © 2001, Cisco Systems, Inc. All rights reserved. © 2004, Cisco Systems, Inc. All rights reserved. Location Conveyance in SIP draft-ietf-sipping-location-requirements-02.
Advertisements

CST Computer Networks NAT CST 415 4/10/2017 CST Computer Networks.
MUTE and UNMUTE Extension to RTSP draft-sergent-rtsp-mute-00.txt Aravind Narasimhan
RTSP revision for Draft Standard Rob Lanphier – RealNetworks Magnus Westerlund - Ericsson March 20, 2002.
Internet Networking Spring 2006 Tutorial 12 Web Caching Protocols ICP, CARP.
Hypertext Transfer Protocol Kyle Roth Mark Hoover.
RTSP NAT Traversal Update Magnus Westlund (Ericsson) Thomas Zeng (PVNS, an Alcatel company) IETF-60 MMUSIC WG draft-ietf-mmusic-rtsp-nat-03.txt.
1 Spring Semester 2007, Dept. of Computer Science, Technion Internet Networking recitation #13 Web Caching Protocols ICP, CARP.
12/05/2000CS590F, Purdue University1 Sip Implementation Protocol Presented By: Sanjay Agrawal Sambhrama Mundkur.
From Extensibility to Evolvability Once upon a time, HTTP was simple – what happened?
July 30, 2010SIPREC WG1 SIP Call Control - Recording Extensions draft-johnston-siprec-cc-rec-00 Alan Johnston Andrew Hutton.
1 © NOKIA Web Service Reliability NOKIA. 2 © NOKIA Content What is reliability ? Guaranteed Delivery Duplicate Elimination Ordering Crash tolerance State.
27.1 Chapter 27 WWW and HTTP Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
Update of RTSP draft-ietf-mmusic-rfc2326bis-03.txt Authors: Henning Schulzrinne / Columbia University Robert Lanphier / Real Networks Magnus Westerlund.
Session Initiation Protocol (SIP). What is SIP? An application-layer protocol A control (signaling) protocol.
ISER on SCTP & IB draft-hufferd-ips-iser-sctp-ib-00.txt Generalizations to iSER specification John Hufferd Mike Ko Yaron Haviv.
July 27, 2009IETF NEA Meeting1 NEA Working Group IETF 75 Co-chairs: Steve Hanna
IETF 60 – San Diegodraft-ietf-mmusic-rfc2326bis-07 Magnus Westerlund Real-Time Streaming Protocol draft-ietf-mmusic-rfc2326bis-07 Magnus Westerlund Aravind.
FIMS v1.1 Version numbers in schema Richard Cartwright Quantel July 2013.
Session Peering Protocol over SOAP I-D ( draft-ietf-drinks-spp-over-soap-01) draft-ietf-drinks-spp-over-soap-01 0 Presenter: Vikas Bhatia (On behalf of.
1 Diameter SIP application draft-ietf-aaa-diameter-sip-app-03.txt 60 th IETF meeting August 3 rd, 2004 Status.
SHIM6 Protocol Drafts Overview Geoff Huston, Marcelo Bagnulo, Erik Nordmark.
Exposing Source IP Address Type Requirements with DHCPv6 D. Moses, A. Yegin draft-moses-dmm-dhcp-ondemand-mobility-00.
A SIP Event Package for DTMF Event Monitoring draft-zebarth-sipping-dtmfad-00.txt IETF 58 Joe Zebarth, Vice Chair T1S1.7.
Slide title In CAPITALS 50 pt Slide subtitle 32 pt RTSP 2.0 TLS handling Magnus Westerlund draft-ietf-mmusic-rfc2326bis-12.
Security, NATs and Firewalls Ingate Systems. Basics of SIP Security.
RTSP to Draft Standard draft-ietf-mmusic-rfc2236bis-02.txt Authors: Henning Schulzrinne, Anup Rao, Robert Lanphier, Magnus Westerlund.
Session Initiation Protocol (SIP) Chapter 5 speaker : Wenping Zhang data :
CDNI Requirements (draft-lefaucheur-cdni-requirements-02) CDNI Working Group IETF 81 Quebec City, Canada July 28, 2011 Kent Leung Yiu.
SIP INFO Event Framework (draft-kaplan-sip-info-events-00) Hadriel Kaplan Christer Holmberg 70th IETF, Vancouver, Canada.
SIP working group IETF#70 Essential corrections Keith Drage.
Chapter 17 BOOTP and DHCP.
CSIT 220 (Blum)1 ARP Based on Computer Networks and Internets (Comer)
All Rights Reserved © Alcatel-Lucent 2006, ##### 2G IMS CAVE Based Security Replay Protection Zhibi Wang January, 2007.
1 Requirements for Internet Routers (Gateways) and Hosts Relates to Lab 3. (Supplement) Covers the compliance requirements of Internet routers and hosts.
Support Shared Mesh Protection in MPLS-TP March 27, 2011 Ping Pan (Infinera) Sam Aldrin (Huawei) Luyuan Fang (Cisco)
Draft-ietf-fecframe-config-signaling-02 1 FEC framework Configuration Signaling draft-ietf-fecframe-config-signaling-02.txt IETF 76 Rajiv Asati.
Caller Prefs and Friends Jonathan Rosenberg dynamicsoft.
Abierman-netconf-mar07 1 NETCONF WG 68 th IETF Prague, CZ March 19, 2007.
SIP-H.323 Interworking Group RRR-1 IETF-48 SIP-H.323 Interworking Requirements draft-agrawal-sip-h323-interworking-reqs-00.txt Hemant.
Magnus Westerlund 1 The RTSP Core specification draft-ietf-mmusic-rfc2326bis-06.txt Magnus Westerlund Aravind Narasimhan Rob Lanphier Anup Rao Henning.
Open issues from SIP list Jonathan Rosenberg dynamicsoft.
New Revision of the Interactive Connectivity Establishment (ICE) IETF 85, Atlanta November 6 th, 2012 Ari Keränen.
IETF #65 Network Discovery and Selection Problem draft-ietf-eap-netsel-problem-04 Farooq Bari Jouni Korhonen.
Slide title In CAPITALS 50 pt Slide subtitle 32 pt RTSP draft-ietf-mmusic-rfc2396bis-10 Magnus Westerlund Co-auhtors: Henning Schulzrinne, Rob Lanphier,
MSRP Again! draft-ietf-simple-message- session-09.
SIP Events: Changes and Open Issues IETF 50 / SIP Working Group Adam Roach
A RTCP-based Retransmission Protocol for Unicast RTP Streaming Multimedia draft-podolsky-avt-rtprx-00.txt Matthew Podolsky, Koichi Yano, and Steven McCanne.
TLS Renegotiation Vulnerability IETF-76 Joe Salowey Eric Rescorla
RFC 2716bis Wednesday, July 12, 2006 Draft-simon-emu-rfc2716bis-02.txt Dan Simon Bernard Aboba IETF 66, Montreal, Canada.
Slide #1 Nov 6 -11, 2005SIP WG IETF64 Feature Tags with SIP REFER draft-ietf-sip-refer-feature-param-00 Orit
Diameter SIP Application
Draft-ietf-p2psip-base-08 Cullen Jennings Bruce Lowekamp Eric Rescorla Salman Baset Henning Schulzrinne March 25, 2010.
Towards Lemonade Profile Version 2 August 3, 2005 IETF 63 - Lemonade 1 Lemonade New Drafts Towards Version 2 of Lemonade Profile Stéphane H. Maes,
Nokia Internal Use Only Outline Status of the PAWS protocol document Open Issues – Review extensibility and IANA registries.
1 Kyung Hee University Chapter 16 Host Configuration : BOOTP and DHCP.
SIP wg Items Jonathan Rosenberg dynamicsoft Caller Preferences: Changes Discussion of Redirects –Previous draft only proxy –Nothing different for redirect.
Session-Independent Policies draft-ietf-sipping-session-indep-policy-02 Volker Hilt Jonathan Rosenberg Gonzalo.
draft-ietf-simple-message-session-09
Request-URI Param Delivery
Session Initiation Protocol (SIP)
HTTP Protocol.
Internet Networking recitation #12
A SIP Event Package for DTMF Event Monitoring
Balazs Lengyel, Ericsson
Joe Clarke (presenting)
RTSP - Core Magnus Westerlund / Ericsson Rob Lanphier / Real Networks
Real Time Streaming Protocol
SIP Session Timer Glare Handling
IETF 87 DHC WG Berlin, Germany Thursday, 1 August, 2013
Presentation transcript:

Real-Time Streaming Protocol draft-ietf-mmusic-rfc2326bis-01.txt Magnus Westerlund

draft-ietf-mmusic-rfc2326bis-01.txt New in draft…-01 Header table in chapter 12 Updated all HTTP references to RFC 2616 State machine chapter totally rewritten Added PING method IANA section created Clarified usage of range with open start time Clarified usage of pause point

draft-ietf-mmusic-rfc2326bis-01.txt Issues to Discuss Feature discovery Protocol extensions: IANA Section Persistent connections Redirect Connection related feature tags OPTIONS method implementation requirements

draft-ietf-mmusic-rfc2326bis-01.txt Extensibility and feature discovery 1/2 The existing method with three headers: –Require and Proxy-require: Puts conditions on the request that the given features must be supported and used or the request shall not be performed. –Unsupported: In a response to a request with require this header gives the missing features. The current require headers can not be used to check if the other party does support a feature.

draft-ietf-mmusic-rfc2326bis-01.txt Extensibility and feature discovery 2/2 The new proposed addition for feature discovery –Supported: Taken from SIP. Requester includes all supported feature tags. Responder replies with all his supported tags. The definition may not be what we want for RTSP due to possible message sizes. Proposed to create new header with other syntax: –Requester includes feature tags he wants to know if the responder supports. The responder removes any that it does not support. Which solution is desired? In which methods are the header allowed to be used?

draft-ietf-mmusic-rfc2326bis-01.txt Extensibility - IANA section New IANA section sets up four repositories: –Methods: Requires IETF standards action –Headers: Requires specification –Parameters: Done on first come, first served basis –Feature tags (option-tags): Done on first come, first served basis The chapter also defines rules what such a registration and possible specification must contain. Unregistered headers shall start with “X-”. Is these requirement levels the desired ones?

draft-ietf-mmusic-rfc2326bis-01.txt Persistent connections Needs backwards compatible solution Try to allow client maximum freedom Having simple rule for servers Should support non-persistent connections. Proposed Solution: Servers are not allowed to close connection until connection timeout (>= RTSP timeout). Clients may close connection at any time. Clients are strongly recommended to keep connections open, to allow Server to send requests. Closing connection may result in server closing session on old servers (feature tag).

draft-ietf-mmusic-rfc2326bis-01.txt REDIRECT Issues Two ways of doing redirect: –3xx response: Should be used before session is established. –REDIRECT method: Used to redirect already established sessions. The REDIRECT method does not work unless a persistent connection is used. Shall the server directly upon receiving the response for a REDIRECT remove the session? The REDIRECT MUST or SHOULD contain a session header? How to use Range header in REDIRECT?

draft-ietf-mmusic-rfc2326bis-01.txt Two connection related feature tags It is proposed that we define two feature tags: –ping-b4-session-timeout –ping-b4-connection-timeout If these features are supported the server is required to ping the client before closing either the RTSP session or the persistent connection. The server will then close the session or connection if fails to ping the client with one timeout period. It requires the client to use a persistent connection. Should this be in the base spec or a extension?

draft-ietf-mmusic-rfc2326bis-01.txt OPTIONS method implementation requirements Minimal client implementations are not required to implement OPTIONS Server implementations MUST implement it Should also clients be required to implement it?

draft-ietf-mmusic-rfc2326bis-01.txt The nearest future of RTSP Update the draft significantly to version 02. Includes getting rid of all known contradictions and fix the resolved bugs. Continue the work on interoperability tests preparations.