From magnus.westerlund@ericsson.com Sun Mar 4 23:53:52 2012 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6537711E8083 for ; Sun, 4 Mar 2012 23:53:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.309 X-Spam-Level: X-Spam-Status: No, score=-110.309 tagged_above=-999 required=5 tests=[AWL=0.290, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rFB4GABrIuaD for ; Sun, 4 Mar 2012 23:53:52 -0800 (PST) Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id A68E111E8079 for ; Sun, 4 Mar 2012 23:53:51 -0800 (PST) X-AuditID: c1b4fb39-b7bf2ae0000069a1-23-4f54710ecddd Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id E0.6D.27041.E01745F4; Mon, 5 Mar 2012 08:53:50 +0100 (CET) Received: from [127.0.0.1] (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.3.213.0; Mon, 5 Mar 2012 08:53:50 +0100 Message-ID: <4F54710D.6060901@ericsson.com> Date: Mon, 5 Mar 2012 08:53:49 +0100 From: Magnus Westerlund User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "avtext@ietf.org" , "DRAGE, Keith (Keith)" X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Brightmail-Tracker: AAAAAA== Subject: [avtext] AVTEXT agenda requests for Paris X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2012 07:53:52 -0000 WG, If you want to request an agenda slot for the AVTEXT WG session in Paris, please send us chairs as soon as possible a response to this message indicating the below information: Subject: Any related drafts: Amount of time requested: Who is the presenter: Please send the request no later than the 12th of March Thanks Magnus Westerlund (as WG chair) ---------------------------------------------------------------------- Multimedia Technologies, Ericsson Research EAB/TVM ---------------------------------------------------------------------- Ericsson AB | Phone +46 10 7148287 Färögatan 6 | Mobile +46 73 0949079 SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com ---------------------------------------------------------------------- From magnus.westerlund@ericsson.com Wed Mar 7 02:43:54 2012 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E31421F86F8 for ; Wed, 7 Mar 2012 02:43:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.34 X-Spam-Level: X-Spam-Status: No, score=-110.34 tagged_above=-999 required=5 tests=[AWL=0.259, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cjlsFpjrC8m4 for ; Wed, 7 Mar 2012 02:43:51 -0800 (PST) Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 3C24721F86DE for ; Wed, 7 Mar 2012 02:43:44 -0800 (PST) X-AuditID: c1b4fb3d-b7bb7ae0000007b2-ec-4f573bde5ca2 Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 1A.AB.01970.EDB375F4; Wed, 7 Mar 2012 11:43:43 +0100 (CET) Received: from [127.0.0.1] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.213.0; Wed, 7 Mar 2012 11:43:42 +0100 Message-ID: <4F573BDD.1080004@ericsson.com> Date: Wed, 7 Mar 2012 11:43:41 +0100 From: Magnus Westerlund User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "avtext@ietf.org" X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Brightmail-Tracker: AAAAAA== Subject: [avtext] Call for editor on "Support for multiple clock rates in an RTP session" X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2012 10:43:54 -0000 WG, The current author of "Support for multiple clock rates in an RTP session" (draft-ietf-avtext-multiple-clock-rates-02) Marc Petit-Huguenin will be unable to continue his work on this document. We thank him for all his work so far. Thus we are looking for an editor that can help complete any remaining work on this document. If you are willing to volunteer please send us chairs a response to this email. Regards Magnus Westerlund ---------------------------------------------------------------------- Multimedia Technologies, Ericsson Research EAB/TVM ---------------------------------------------------------------------- Ericsson AB | Phone +46 10 7148287 Färögatan 6 | Mobile +46 73 0949079 SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com ---------------------------------------------------------------------- From glenzorn@gmail.com Wed Mar 7 04:42:00 2012 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB5A921F86DB for ; Wed, 7 Mar 2012 04:42:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id upMW-SNEMqrK for ; Wed, 7 Mar 2012 04:42:00 -0800 (PST) Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 44A8721F87BA for ; Wed, 7 Mar 2012 04:42:00 -0800 (PST) Received: by ggmi1 with SMTP id i1so3174020ggm.31 for ; Wed, 07 Mar 2012 04:41:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=LRcrYpwUBi3/SV7SaGwOi5/jWSDmkI+a25iMRv4+Ufo=; b=F1LrPSNGqFYmLGsPA9bj52U/4Y1amAVjP2ADTSiTUMkK6Nm7+P94oPpmmjcgEYW6QE GtfcsVCbLTRHTT2hz+HcgcMom78oJ7nCOaw/cIhlSfrcc9cNFADhYCihuSTmO2yXRCaR 2gbn/ZPtfnVYxuCcMv3mhqQR1TQlgLsQyLFbWEJc+gcwxHyESs/G6MCPzWHBs9ENugDd /jOitLGRbRYoNXBxLFlBo9N9mYJRXiQ2hx0rq5yyUYxvbZ4+zRsxVzpSyCOa65H6Gl+9 60nfm4Ck+dcfEXAdUJoeoRIqhhVUX6xWBH6xD9L3ZF16HYQbhNA+wMVZ1NHvyP3gOgV1 2D+w== Received: by 10.60.20.101 with SMTP id m5mr729216oee.5.1331124119592; Wed, 07 Mar 2012 04:41:59 -0800 (PST) Received: from [192.168.1.98] (ppp-115-87-64-205.revip4.asianet.co.th. [115.87.64.205]) by mx.google.com with ESMTPS id h9sm21919306obr.20.2012.03.07.04.41.56 (version=SSLv3 cipher=OTHER); Wed, 07 Mar 2012 04:41:58 -0800 (PST) Message-ID: <4F57578F.9050303@gmail.com> Date: Wed, 07 Mar 2012 19:41:51 +0700 From: Glen Zorn User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: Magnus Westerlund References: <4F573BDD.1080004@ericsson.com> In-Reply-To: <4F573BDD.1080004@ericsson.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: "avtext@ietf.org" Subject: Re: [avtext] Call for editor on "Support for multiple clock rates in an RTP session" X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2012 12:42:00 -0000 On 3/7/2012 5:43 PM, Magnus Westerlund wrote: > WG, > > The current author of "Support for multiple clock rates in an RTP > session" (draft-ietf-avtext-multiple-clock-rates-02) Marc Petit-Huguenin > will be unable to continue his work on this document. We thank him for > all his work so far. > > Thus we are looking for an editor that can help complete any remaining > work on this document. If you are willing to volunteer please send us > chairs a response to this email. I'll be happy to do it. > > Regards > > Magnus Westerlund > > ---------------------------------------------------------------------- > Multimedia Technologies, Ericsson Research EAB/TVM > ---------------------------------------------------------------------- > Ericsson AB | Phone +46 10 7148287 > Färögatan 6 | Mobile +46 73 0949079 > SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com > ---------------------------------------------------------------------- > > _______________________________________________ > avtext mailing list > avtext@ietf.org > https://www.ietf.org/mailman/listinfo/avtext From bo.burman@ericsson.com Thu Mar 8 05:01:00 2012 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81C4021F8592 for ; Thu, 8 Mar 2012 05:01:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.399 X-Spam-Level: X-Spam-Status: No, score=-10.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CBziJpGgLU4L for ; Thu, 8 Mar 2012 05:00:59 -0800 (PST) Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 86B5321F84EE for ; Thu, 8 Mar 2012 05:00:59 -0800 (PST) X-AuditID: c1b4fb3d-b7c6fae0000045c0-dc-4f58ad8add09 Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id F7.3B.17856.A8DA85F4; Thu, 8 Mar 2012 14:00:58 +0100 (CET) Received: from ESESSCMS0361.eemea.ericsson.se ([169.254.1.209]) by esessmw0191.eemea.ericsson.se ([153.88.115.84]) with mapi; Thu, 8 Mar 2012 14:00:57 +0100 From: Bo Burman To: "avtext@ietf.org" Date: Thu, 8 Mar 2012 14:00:56 +0100 Thread-Topic: New draft on controlling codec parameters; draft-westerlund-avtext-codec-operation-point-00 Thread-Index: Acz9K4Bo5U56QMZ7RBec1A5gcjSnWg== Message-ID: <05F760EF51FA6A4F804F9759C239313A3A72087206@ESESSCMS0361.eemea.ericsson.se> Accept-Language: sv-SE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: sv-SE, en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: AAAAAA== Subject: [avtext] New draft on controlling codec parameters; draft-westerlund-avtext-codec-operation-point-00 X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2012 13:01:00 -0000 Hi, My colleagues and I have a proposal for an RTCP extension to AVPF CCM allow= ing a media receiver to dynamically ask the media sender to use a certain c= odec configuration (called a Codec Operation Point, COP). We see this as be= ing used both in WEBRTC (RTCWEB WG) and Video Conferencing / Telepresence (= CLUE WG). Additional applications are expected. The proposal is not intended to replace or conflict with codec negotiation = taking place during SDP Offer / Answer, but rather optimize and fine-tune c= odec usage within the limits established by SDP O/A. The draft defines a set of what is believed generally useful and reasonably= codec-independent set of parameters. Those parameters can be used by a med= ia sender to describe the codec configuration (Codec Operation Point) used = to generate the media stream to the media receiver. The media receiver can = in turn examine the parameter values in the announced Codec Operation Point= and use the same set of defined parameters to ask the media sender to use = other, more suitable values for those parameters. It is the media sender's = responsibility to decide if such request can be honored or not. If the requ= est is accepted, the media sender then changes the media stream accordingly= and sends another Codec Operation Point announcement with the changed para= meter values. One possible example is to let a video media receiver control the encoded v= ideo resolution based on decoded video window display size. https://datatracker.ietf.org/doc/draft-westerlund-avtext-codec-operation-po= int/ This draft is designed to: * Allow for minimal implementation. The media sender need only announce COP= support for the payload types it wishes to make controllable. It is not a = requirement to support all parameter types, and receive support for each pa= rameter type is signaled explicitly in SDP. Unsupported parameter types can= safely be ignored. * Be extensible. It is for example easy to define more parameter types in e= xtensions to this draft. New message types and result codes can also be def= ined as extensions. * Be possible to use both in point-to-point, in multipoint (conferencing), = and even some specific multicast situations. * Be responsive. The user at the media receiver can request and experience = the result of changes in a dynamic and interactive fashion. The codec contr= ol signaling need only traverse the media path and uses the most responsive= RTCP mode available, AVPF. * Support single layer as well as multi-layered (scalable) media streams. A= multi-layered media stream can easily be described and configured by using= multiple, simultaneously active Codec Operation Points. * Be as media and codec agnostic as possible. The defined parameter types a= re chosen to be as generic as possible and should therefore apply to many d= ifferent codecs. Some media type awareness is however included in the chose= n set of parameters. * Be robust. It leaves to the media sender to decide exactly what is change= d. A media sender that receives a request to set a certain value for a para= meter can choose another value that is seen as more appropriate, or even ch= oose to not change anything at all. "Unreasonable" requests can thus safely= be ignored. * Be flexible in what type of parameter value restrictions that can be desc= ribed. A request can use either an exact single value, an open-ended minimu= m or maximum restriction, or a range of values. It is also possible to use = a "target" value, standalone or in combination with a range, to express a p= reference. It is even possible to specify a set of prioritized, alternative= configurations that the media sender can choose from. * Allow for advertised, synchronized configuration changes. The Codec Opera= tion Point notification can be time stamped some time into the future, allo= wing the media receiver some time for informed preparation (if needed) befo= re the actual media stream change occurs. We would like to see this work as WG item in AVTEXT WG. Best Regards Bo Burman ---------------------------------------------------------------------- Multimedia Technologies, Ericsson Research EAB/TVM ---------------------------------------------------------------------- Ericsson AB | Phone +46 10 7141311 F=E4r=F6gatan 6 | Mobile +46 73 0949021 SE-164 80 Stockholm, Sweden | mailto: bo.burman@ericsson.com ---------------------------------------------------------------------- From internet-drafts@ietf.org Fri Mar 9 07:58:01 2012 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D20921F86AB; Fri, 9 Mar 2012 07:58:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.524 X-Spam-Level: X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y0lh8jme8E5c; Fri, 9 Mar 2012 07:58:00 -0800 (PST) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF2EE21F8573; Fri, 9 Mar 2012 07:58:00 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.00 Message-ID: <20120309155800.20776.121.idtracker@ietfa.amsl.com> Date: Fri, 09 Mar 2012 07:58:00 -0800 Cc: avtext@ietf.org Subject: [avtext] I-D Action: draft-ietf-avtext-rams-scenarios-03.txt X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2012 15:58:01 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Audio/Video Transport Extensions Work= ing Group of the IETF. Title : Considerations for Deploying the Rapid Acquisition of Mu= lticast RTP Sessions (RAMS) Method Author(s) : Ali Begen Filename : draft-ietf-avtext-rams-scenarios-03.txt Pages : 11 Date : 2012-03-09 The Rapid Acquisition of Multicast RTP Sessions (RAMS) solution is a method based on RTP and RTP Control Protocol (RTCP) that enables an RTP receiver to rapidly acquire and start consuming the RTP multicast data. Upon a request from the RTP receiver, an auxiliary unicast RTP retransmission session is set up between a retransmission server and the RTP receiver, over which the reference information about the new multicast stream the RTP receiver is about to join is transmitted at an accelerated rate. This often precedes, but may also accompany, the multicast stream itself. When there is only one multicast stream to be acquired, the RAMS solution works in a straightforward manner. However, when there are two or more multicast streams to be acquired from the same or different multicast RTP sessions, care should be taken to configure each RAMS session appropriately. This document provides example scenarios and discusses how the RAMS solution could be used in such scenarios. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-avtext-rams-scenarios-03.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtext-rams-scenarios-03.txt From keith.drage@alcatel-lucent.com Fri Mar 9 10:17:32 2012 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F59B21F8716 for ; Fri, 9 Mar 2012 10:17:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -109.435 X-Spam-Level: X-Spam-Status: No, score=-109.435 tagged_above=-999 required=5 tests=[AWL=0.814, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LzHpW4nMZeQm for ; Fri, 9 Mar 2012 10:17:31 -0800 (PST) Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id 2C5B721E8058 for ; Fri, 9 Mar 2012 10:17:27 -0800 (PST) Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q29IHJfv026907 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Fri, 9 Mar 2012 19:17:26 +0100 Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Fri, 9 Mar 2012 19:17:26 +0100 From: "DRAGE, Keith (Keith)" To: "avtext@ietf.org" Date: Fri, 9 Mar 2012 19:17:22 +0100 Thread-Topic: RAMs scenarios Thread-Index: Acz+IN969OLhbETgQeimsBG5CRB4lg== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80 Subject: [avtext] RAMs scenarios X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2012 18:17:32 -0000 (As WG cochair) I have just requested publication of draft-ietf-avtext-rams-scenarios-03 as= an informational RFC. You will notice that Ali recently (today) produced a new version of this do= cument, which has some very minor editorial changes to it (i.e. none of the= m have any technical impact whatsoever).=20 The writeup follows below. Regards Keith Document shepherd writeup for draft-ietf-avtext-rams-scenarios-03 (1) What type of RFC is being requested (BCP, Proposed Standard, Internet Standard, Informational, Experimental, or Historic)? Why is this the proper type of RFC? Is this type of RFC indicated in the title page header? The document is being requested as an informational RFC. This document provides supporting informational text to RFC 6285 which is t= he=20 related standards track document. It contains no normative material in its = own=20 right. While it contains example scenarios, none of these are a recommended= =20 solution so it is not considered a BCP. The cover page indicates: "Intended status: Informational". (2) The IESG approval announcement includes a Document Announcement Write-Up. Please provide such a Document Announcement Write-Up. Recent examples can be found in the "Action" announcements for approved documents. The approval announcement contains the following sections: Technical Summary Relevant content can frequently be found in the abstract=20 and/or introduction of the document. If not, this may be=20 an indication that there are deficiencies in the abstract=20 or introduction. The Rapid Acquisition of Multicast RTP Sessions (RAMS) solution is a method based on RTP and RTP Control Protocol (RTCP) that enables an RTP receiver to rapidly acquire and start consuming the RTP multicast data. Upon a request from the RTP receiver, an auxiliary unicast RTP retransmission session is set up between a retransmission server and the RTP receiver, over which the reference information about the new multicast stream the RTP receiver is about to join is transmitted at an accelerated rate. This often precedes, but may also accompany, the multicast stream itself. When there is only one multicast stream to be acquired, the RAMS solution works in a straightforward manner. However, when there are two or more multicast streams to be acquired from the same or different multicast RTP sessions, care should be taken to configure each RAMS session appropriately. This document provides example scenarios and discusses how the RAMS solution could be used in such scenarios. Working Group Summary Was there anything in WG process that is worth noting? For=20 example, was there controversy about particular points or=20 were there decisions where the consensus was particularly=20 rough? The document is a product of the AVTEXT working group. All controversial is= sues=20 were issues of the preceding RAMS document already published in RFC 6285, a= nd=20 this document raised no new issues. Document Quality Are there existing implementations of the protocol? Have a=20 significant number of vendors indicated their plan to=20 implement the specification? Are there any reviewers that=20 merit special mention as having done a thorough review,=20 e.g., one that resulted in important changes or a=20 conclusion that the document had no substantive issues? If=20 there was a MIB Doctor, Media Type or other expert review,=20 what was its course (briefly)? In the case of a Media Type=20 review, on what date was the request posted? There are existing implementations of RFC 6285. This document merely gives = some=20 example scenarios of the usage of RFC 6285. Personnel Who is the Document Shepherd? Who is the Responsible Area Director? Keith Drage is the document shepherd. Gonzalo Camarillo is the responsible area director. (3) Briefly describe the review of this document that was performed by the Document Shepherd. If this version of the document is not ready for publication, please explain why the document is being forwarded to the IESG. The document is ready for publication. Brief history of the document: - draft-begen-avt-rams-scenarios-00 was submitted 1st October 2009 and=20 expired 4th April 2009. - draft-begen-avt-rams-scenarios-01 was submitted 15th February 2011 and=20 expired 19th August 2011. - draft-begen-avtext-rams-scenarios-00 was submitted 2nd March 2011 and=20 expired 3rd September 2011. - draft-ietf-avtext-rams-scenarios-00 was submitted 10th June 2011 and=20 expired 12th December 2011. - draft-ietf-avtext-rams-scenarios-01 was submitted 11th October 2011 and=20 expires 13th April 2012. - draft-ietf-avtext-rams-scenarios-02 was submitted 17th January 2012 and=20 expires 20th July 2012. - draft-ietf-avtext-rams-scenarios-03 was submitted 9th March 2012 and=20 expires 10th September 2012. - A consensus call for adoption of the working group text was issued on 10t= h=20 March 2011. - Prior to WGLC an extensive review of the document was performed by Tom Va= n=20 Caenegam - WGLC was initiated on 22nd November 2011 to complete 13th December 2011 a= s=20 an informational document on the -01 version of the document. During WGLC t= he=20 document received review and comments from Colin Perkins, and Kevin Gross. All normal prepublication checks have been performed on the document. (4) Does the document Shepherd have any concerns about the depth or breadth of the reviews that have been performed? =20 There are no concerns. (5) Do portions of the document need review from a particular or from broader perspective, e.g., security, operational complexity, AAA, DNS, DHCP, XML, or internationalization? If so, describe the review that took place. The documents contains some SDP examples. While a formal SDP review has not= been=20 requested, the document has been reviewed by Colin Perkins and no issues we= re=20 identified. (6) Describe any specific concerns or issues that the Document Shepherd has with this document that the Responsible Area Director and/or the IESG should be aware of? For example, perhaps he or she is uncomfortable with certain parts of the document, or has concerns whether there really is a need for it. In any event, if the WG has discussed those issues and has indicated that it still wishes to advance the document, detail those concerns here. There are no specific concerns. (7) Has each author confirmed that any and all appropriate IPR disclosures required for full conformance with the provisions of BCP 78 and BCP 79 have already been filed. If not, explain why. The author is not aware of any IPR disclosures that need to be made in rela= tion=20 to this document. (8) Has an IPR disclosure been filed that references this document? If so, summarize any WG discussion and conclusion regarding the IPR disclosures. No IPR disclosures have been made in respect of this document. It should be noted that there are IPR disclosures on RFC 6285 from Cisco,=20 Microsoft, Alcatel-Lucent and Huawei. In order to implement RFC 6285 to per= form=20 the scenarios in this document, due attention may need to be made to those= =20 disclosures. I do not believe that necessitates a separate disclosure on th= is=20 document. (9) How solid is the WG consensus behind this document? Does it=20 represent the strong concurrence of a few individuals, with others being silent, or does the WG as a whole understand and agree with it? =20 I believe the document has sufficient WG consensus behind it. Key individua= ls=20 have reviewed it and identified that it is in alignment with RFC 6285 which= is=20 the related standards track document. (10) Has anyone threatened an appeal or otherwise indicated extreme=20 discontent? If so, please summarise the areas of conflict in separate email messages to the Responsible Area Director. (It should be in a separate email because this questionnaire is publicly available.)=20 No such objections have been identified. (11) Identify any ID nits the Document Shepherd has found in this document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts Checklist). Boilerplate checks are not enough; this check needs to be thorough. No NITs have been identified. (12) Describe how the document meets any required formal review criteria, such as the MIB Doctor, media type, and URI type reviews. The document contains some example SDP usage. See answer to question (5). (13) Have all references within this document been identified as either normative or informative? This is an informational document, containing no requirements material, and= as=20 such all references are essentially informational. The original RAMs RFC ha= s=20 been identified as normative, but this is primarily from the perspective th= at=20 that document must be read in order to understand this document, rather tha= n any=20 usage in the true meaning of normative reference. (14) Are there normative references to documents that are not ready for advancement or are otherwise in an unclear state? If such normative references exist, what is the plan for their completion? All references, both normative and informative, in this document, have been= =20 published already. (15) Are there downward normative references references (see RFC 3967)? If so, list these downward references to support the Area Director in the Last Call procedure.=20 This document has no downward references. It is an informational document=20 referencing either standards track or informational RFCs. (16) Will publication of this document change the status of any existing RFCs? Are those RFCs listed on the title page header, listed in the abstract, and discussed in the introduction? If the RFCs are not listed in the Abstract and Introduction, explain why, and point to the part of the document where the relationship of this document to the other RFCs is discussed. If this information is not in the document, explain why the WG considers it unnecessary. This document does not change the status of any existing RFCs. (17) Describe the Document Shepherd's review of the IANA considerations section, especially with regard to its consistency with the body of the document. Confirm that all protocol extensions that the document makes are associated with the appropriate reservations in IANA registries. Confirm that any referenced IANA registries have been clearly identified. Confirm that newly created IANA registries include a detailed specification of the initial contents for the registry, that allocations procedures for future registrations are defined, and a reasonable name for the new registry has been suggested (see RFC 5226). This document contains no IANA requirements, and has no need to do so. (18) List any new IANA registries that require Expert Review for future allocations. Provide any public guidance that the IESG would find useful in selecting the IANA Experts for these new registries. This document contains no IANA requirements, and has no need to do so. (19) Describe reviews and automated checks performed by the Document Shepherd to validate sections of the document written in a formal language, such as XML code, BNF rules, MIB definitions, etc. Apart from nit checking, no automated checks have been performed on this=20 document. See answer to question (5) concerning the review of the SDP. From bill.wu@huawei.com Sun Mar 11 18:59:29 2012 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A13BB21F852D for ; Sun, 11 Mar 2012 18:59:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.634 X-Spam-Level: X-Spam-Status: No, score=-4.634 tagged_above=-999 required=5 tests=[AWL=0.212, BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hlcLrpaF0PwV for ; Sun, 11 Mar 2012 18:59:29 -0700 (PDT) Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id CB97321F852B for ; Sun, 11 Mar 2012 18:59:28 -0700 (PDT) Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M0R008JM1IW8C@szxga04-in.huawei.com> for avtext@ietf.org; Mon, 12 Mar 2012 09:59:21 +0800 (CST) Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M0R00FGN1IS6C@szxga04-in.huawei.com> for avtext@ietf.org; Mon, 12 Mar 2012 09:59:20 +0800 (CST) Received: from szxeml213-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AHJ72317; Mon, 12 Mar 2012 09:59:20 +0800 Received: from SZXEML416-HUB.china.huawei.com (10.82.67.155) by szxeml213-edg.china.huawei.com (172.24.2.30) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 12 Mar 2012 09:58:29 +0800 Received: from w53375 (10.138.41.149) by szxeml416-hub.china.huawei.com (10.82.67.155) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 12 Mar 2012 09:59:16 +0800 Date: Mon, 12 Mar 2012 09:59:15 +0800 From: Qin Wu X-Originating-IP: [10.138.41.149] To: Magnus Westerlund , avtext@ietf.org Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109 X-Mailer: Microsoft Outlook Express 6.00.2900.5931 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: base64 X-Priority: 3 X-MSMail-priority: Normal X-CFilter-Loop: Reflected References: <4F573BDD.1080004@ericsson.com> X-Mailman-Approved-At: Mon, 12 Mar 2012 08:05:53 -0700 Subject: Re: [avtext] Call for editor on "Support for multiple clock rates in anRTP session" X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2012 01:59:29 -0000 SGksDQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIk1hZ251cyBXZXN0ZXJs dW5kIiA8bWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tPg0KVG86IDxhdnRleHRAaWV0Zi5v cmc+DQpTZW50OiBXZWRuZXNkYXksIE1hcmNoIDA3LCAyMDEyIDY6NDMgUE0NClN1YmplY3Q6IFth dnRleHRdIENhbGwgZm9yIGVkaXRvciBvbiAiU3VwcG9ydCBmb3IgbXVsdGlwbGUgY2xvY2sgcmF0 ZXMgaW4gYW5SVFAgc2Vzc2lvbiINCg0KDQpXRywNCg0KVGhlIGN1cnJlbnQgYXV0aG9yIG9mICJT dXBwb3J0IGZvciBtdWx0aXBsZSBjbG9jayByYXRlcyBpbiBhbiBSVFANCnNlc3Npb24iIChkcmFm dC1pZXRmLWF2dGV4dC1tdWx0aXBsZS1jbG9jay1yYXRlcy0wMikgTWFyYyBQZXRpdC1IdWd1ZW5p bg0Kd2lsbCBiZSB1bmFibGUgdG8gY29udGludWUgaGlzIHdvcmsgb24gdGhpcyBkb2N1bWVudC4g V2UgdGhhbmsgaGltIGZvcg0KYWxsIGhpcyB3b3JrIHNvIGZhci4NCg0KVGh1cyB3ZSBhcmUgbG9v a2luZyBmb3IgYW4gZWRpdG9yIHRoYXQgY2FuIGhlbHAgY29tcGxldGUgYW55IHJlbWFpbmluZw0K d29yayBvbiB0aGlzIGRvY3VtZW50LiBJZiB5b3UgYXJlIHdpbGxpbmcgdG8gdm9sdW50ZWVyIHBs ZWFzZSBzZW5kIHVzDQpjaGFpcnMgYSByZXNwb25zZSB0byB0aGlzIGVtYWlsLg0KDQpbUWluXTog SXQncyBhbiBpbnRlcmVzdGluZyB3b3JrIGFuZCBJIGNhbiBkbyAgdGhpcy4NCg0KUmVnYXJkcw0K DQpNYWdudXMgV2VzdGVybHVuZA0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpNdWx0aW1lZGlhIFRlY2hub2xv Z2llcywgRXJpY3Nzb24gUmVzZWFyY2ggRUFCL1RWTQ0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KRXJpY3Nzb24g QUIgICAgICAgICAgICAgICAgfCBQaG9uZSAgKzQ2IDEwIDcxNDgyODcNCkbkcvZnYXRhbiA2ICAg ICAgICAgICAgICAgIHwgTW9iaWxlICs0NiA3MyAwOTQ5MDc5DQpTRS0xNjQgODAgU3RvY2tob2xt LCBTd2VkZW58IG1haWx0bzogbWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tDQotLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f DQphdnRleHQgbWFpbGluZyBsaXN0DQphdnRleHRAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYu b3JnL21haWxtYW4vbGlzdGluZm8vYXZ0ZXh0 From keith.drage@alcatel-lucent.com Mon Mar 12 16:41:15 2012 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4C9621E823A for ; Mon, 12 Mar 2012 16:41:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -109.475 X-Spam-Level: X-Spam-Status: No, score=-109.475 tagged_above=-999 required=5 tests=[AWL=0.774, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RiC7F2mhVtLg for ; Mon, 12 Mar 2012 16:41:15 -0700 (PDT) Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id D34E221E823B for ; Mon, 12 Mar 2012 16:41:14 -0700 (PDT) Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q2CNfDIx012135 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Tue, 13 Mar 2012 00:41:13 +0100 Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Tue, 13 Mar 2012 00:41:13 +0100 From: "DRAGE, Keith (Keith)" To: "avtext@ietf.org" Date: Tue, 13 Mar 2012 00:41:12 +0100 Thread-Topic: Agenda for AVTEXT in Paris Thread-Index: Ac0AqZuiyvvVGVIxTpCh6fNEZaS12w== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80 Subject: [avtext] Agenda for AVTEXT in Paris X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2012 23:41:16 -0000 (As WG cochair) I've uploaded an initial agenda for the Paris meeting of AVTEXT and I also = include it below. Note we are hosting a short session of PAYLOAD within our= time. Feel free to bash it now rather than waiting for the start of the meeting i= n Paris. Draft Agenda for AVTEXT Tuesday 27th March 2012 15:20 - 17:00=20 Chairs: Keith Drage Magnus Westerlund (Note we will invite the PAYLOAD chairs to join us at the front when we get= to the PAYLOAD drafts) 15 (15:20 - 15:35) Agenda bash; working group draft status; future work Chairs 5 (15:35 - 15:40) IEEE 1588/802.1AS Synchronisation for RTP Streams Aidan Williams draft-williams-avtext-absync-02 30 (15:40 - 16:10) Codec Operation Point RTCP Extension Bo Burman draft-westerlund-avtext-codec-operation-point-00 [As PAYLOAD working group] 10 (16:10 - 16:20) RTP Payload Format for High Efficiency Video Coding Thomas Schierl draft-schierl-payload-rtp-h265-00 10 (16:20 - 16:30) Offer/Answer Considerations for G.723 Annex A and G.729 Annex B Muthu A M. Perumal draft-muthu-payload-offer-answer-g723-g729-00 (16:30 - 17:00 Unallocated) From keith.drage@alcatel-lucent.com Thu Mar 15 16:32:10 2012 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3B0721F8666 for ; Thu, 15 Mar 2012 16:32:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -109.567 X-Spam-Level: X-Spam-Status: No, score=-109.567 tagged_above=-999 required=5 tests=[AWL=0.682, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eo16hJiO1c11 for ; Thu, 15 Mar 2012 16:32:10 -0700 (PDT) Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by ietfa.amsl.com (Postfix) with ESMTP id 1A56E21F865F for ; Thu, 15 Mar 2012 16:32:09 -0700 (PDT) Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q2FNW8Pc017882 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Fri, 16 Mar 2012 00:32:08 +0100 Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Fri, 16 Mar 2012 00:32:08 +0100 From: "DRAGE, Keith (Keith)" To: "avtext@ietf.org" Date: Fri, 16 Mar 2012 00:32:05 +0100 Thread-Topic: Revised agenda Thread-Index: Ac0DA9SrZNTkQ1fDQJWyxfd/Q0F0Yw== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.69 on 155.132.188.84 Subject: [avtext] Revised agenda X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Mar 2012 23:32:10 -0000 I've just revised the avtext agenda. Correction of typo in the Williams draft name Addition of one more draft to the PAYLOAD WG documents (at the request of t= he PAYLOAD chairs). Regards Keith From magnus.westerlund@ericsson.com Fri Mar 16 08:46:03 2012 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAA9421F866C for ; Fri, 16 Mar 2012 08:46:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.374 X-Spam-Level: X-Spam-Status: No, score=-110.374 tagged_above=-999 required=5 tests=[AWL=0.225, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lNPeCzTcY2SB for ; Fri, 16 Mar 2012 08:46:02 -0700 (PDT) Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 0827E21F86A3 for ; Fri, 16 Mar 2012 08:45:57 -0700 (PDT) X-AuditID: c1b4fb3d-b7c6fae0000045c0-46-4f636034b049 Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id DA.E2.17856.430636F4; Fri, 16 Mar 2012 16:45:57 +0100 (CET) Received: from [127.0.0.1] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.213.0; Fri, 16 Mar 2012 16:45:56 +0100 Message-ID: <4F636034.7060506@ericsson.com> Date: Fri, 16 Mar 2012 16:45:56 +0100 From: Magnus Westerlund User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "avtext@ietf.org" References: <4F635D10.3040607@ericsson.com> In-Reply-To: <4F635D10.3040607@ericsson.com> X-Enigmail-Version: 1.4 Content-Type: multipart/mixed; boundary="------------080100010406010108070807" X-Brightmail-Tracker: AAAAAA== Subject: [avtext] Fwd: [dispatch] Media Stream Related Signaling X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: DISPATCH list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Mar 2012 15:46:03 -0000 --------------080100010406010108070807 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit AVTEXT WG, (As Individual) The Pause and Resume was previously discussed in AVTEXT so I hope their interest from this WG. A reminder to you that this discussion will happen in Paris in the Dispatch WG session, currently scheduled for Tuesday (27th of March) at 1300-1500. If you already now have input in the discussion please send email to the Dispatch WG mailing list. Cheers Magnus --------------080100010406010108070807 Content-Type: message/rfc822; name="[dispatch] Media Stream Related Signaling.eml" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="[dispatch] Media Stream Related Signaling.eml" X-Mozilla-Keys: Received: from sesbmg10.ericsson.net (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.89) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 16 Mar 2012 16:32:40 +0100 Received: from mail.ietf.org (mail.ietf.org [12.22.58.30]) by sesbmg10.ericsson.net (Symantec Mail Security) with SMTP id A3.ED.03823.81D536F4; Fri, 16 Mar 2012 16:32:40 +0100 (CET) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B86EB21F8711; Fri, 16 Mar 2012 08:32:38 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4405C21F8709 for ; Fri, 16 Mar 2012 08:32:35 -0700 (PDT) Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5KcNVfIl1OhU for ; Fri, 16 Mar 2012 08:32:34 -0700 (PDT) Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 5F7C621F86D5 for ; Fri, 16 Mar 2012 08:32:34 -0700 (PDT) Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id C4.11.17856.11D536F4; Fri, 16 Mar 2012 16:32:33 +0100 (CET) Received: from [127.0.0.1] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.213.0; Fri, 16 Mar 2012 16:32:32 +0100 From: Magnus Westerlund To: DISPATCH list Sender: "dispatch-bounces@ietf.org" Date: Fri, 16 Mar 2012 16:32:32 +0100 Subject: [dispatch] Media Stream Related Signaling Thread-Topic: [dispatch] Media Stream Related Signaling Thread-Index: Ac0DigZOdrBIp9HVQ6m5uCDvQ8b40Q== Message-ID: <4F635D10.3040607@ericsson.com> References: <4F635AF9.9020605@ericsson.com> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <4F635AF9.9020605@ericsson.com> Accept-Language: en-US Content-Language: en-US X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-AuthSource: esessmw0197.eemea.ericsson.se X-MS-Has-Attach: X-Auto-Response-Suppress: All X-MS-TNEF-Correlator: x-auditid: c1b4fb3c-b7f126d000000eef-25-4f635d171dd7 x-brightmail-tracker: AAAAAA== dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1331911958; bh=InyQ1CufGR9qkZDp9pnRK+DMwxIXvg5eclqpB6XDScQ=; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=h5Q1xvKpRAVpgVLge5pdbt5xmqCZRVoNRo2Xb0EiC5eP9mkkMxWhR3CtMzttMTGvK sh5FxZy/w+QEJAKSpfpH2uz8GzKe61DEGI3cdXyCOIcA1j0iN9V1qUVXrMscJAmk85 fBjrbqCZd0ypCAlFdW11JrpvEg2dQiABoc+rxvfk= user-agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 errors-to: dispatch-bounces@ietf.org x-virus-scanned: amavisd-new at amsl.com x-mailman-version: 2.1.12 list-post: list-archive: list-id: DISPATCH Working Group Mail List x-beenthere: dispatch@ietf.org x-spam-level: x-spam-status: No, score=-110.368 tagged_above=-999 required=5 tests=[AWL=0.231, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] x-spam-score: -110.368 x-spam-flag: NO delivered-to: dispatch@ietfa.amsl.com x-original-to: dispatch@ietfa.amsl.com x-enigmail-version: 1.4 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Dispatch, With 10 days until the meeting I would like to provide a reminder on the upcoming discussion and some clarification on what we believe to be the high level question that Dispatch needs to resolve for us to be able to make progress. First of all we have not updated our drafts. They are still relevant background material for this discussion: Media Stream Selection: https://datatracker.ietf.org/doc/draft-westerlund-dispatch-stream-selection= / Pause and Resume: https://datatracker.ietf.org/doc/draft-westerlund-avtext-rtp-stream-pause/ The above drafts propose the need for two functionalities: Choose What Content to Receive - A media receiver wants to dynamically choose which media stream to receive, out of many possible, from a certain media sender, out of many possible Request to Pause Sending of a Content - A media receiver wants to ask the media sender to temporarily stop sending a specific media stream, and to resume it with short notice >From our perspective there exist three different high level methods for realizing this functionality: - Using a media control protocol, like BFCP or Media Control Framework - Using the media plane, like RTCP - Using the signaling plane, like SIP/SDP or other SIP carried data What we want out of the Dispatch session is clear indications on what are the most suitable method or methods (as we have two different functionalities) that should be worked out. That indication can then hopefully be turned into a decision pretty quickly to take the work to one or more WG. We want to be able to continue working on this and making progress. Cheers Magnus Westerlund ---------------------------------------------------------------------- Multimedia Technologies, Ericsson Research EAB/TVM ---------------------------------------------------------------------- Ericsson AB | Phone +46 10 7148287 F=E4r=F6gatan 6 | Mobile +46 73 0949079 SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com ---------------------------------------------------------------------- _______________________________________________ dispatch mailing list dispatch@ietf.org https://www.ietf.org/mailman/listinfo/dispatch --------------080100010406010108070807-- From gonzalo.camarillo@ericsson.com Tue Mar 20 02:14:33 2012 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7D9321F885E for ; Tue, 20 Mar 2012 02:14:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.061 X-Spam-Level: X-Spam-Status: No, score=-110.061 tagged_above=-999 required=5 tests=[AWL=-0.062, BAYES_00=-2.599, J_CHICKENPOX_23=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N168Jq4urqOx for ; Tue, 20 Mar 2012 02:14:33 -0700 (PDT) Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id DE84021F8853 for ; Tue, 20 Mar 2012 02:14:32 -0700 (PDT) X-AuditID: c1b4fb3d-b7c6fae0000045c0-32-4f684a77d316 Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 56.7C.17856.77A486F4; Tue, 20 Mar 2012 10:14:32 +0100 (CET) Received: from [131.160.36.191] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.213.0; Tue, 20 Mar 2012 10:14:31 +0100 Message-ID: <4F684A77.6000703@ericsson.com> Date: Tue, 20 Mar 2012 11:14:31 +0200 From: Gonzalo Camarillo User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: avtext@ietf.org References: <4F684A51.3040205@ericsson.com> In-Reply-To: <4F684A51.3040205@ericsson.com> X-Enigmail-Version: 1.3.4 X-Forwarded-Message-Id: <4F684A51.3040205@ericsson.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: AAAAAA== Subject: [avtext] Fwd: SDP review of draft-ietf-avtext-rams-scenarios X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2012 09:14:33 -0000 FYI. -------- Original Message -------- Subject: SDP review of draft-ietf-avtext-rams-scenarios Date: Tue, 20 Mar 2012 11:13:53 +0200 From: Gonzalo Camarillo To: Flemming Andreasen , Miguel Angel Garcia CC: mmusic Flemming, Miguel Angel, I have just requested the publication of the following AVTEXT draft. https://datatracker.ietf.org/doc/draft-ietf-avtext-rams-scenarios/ This draft contains a few SDP examples. Even if it does not define any new SDP extension, I would like somebody from the SDP directorate to have a quick look at it to make sure all SDPs in the draft are correct. Could you please get someone to do this? http://www.ietf.org/iesg/directorate/sdp.html I am cc:ing the MMUSIC list in case somebody else also wants to have a look at the draft. Thanks, Gonzalo From iesg-secretary@ietf.org Tue Mar 20 05:40:16 2012 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 704FA21F8678; Tue, 20 Mar 2012 05:40:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.52 X-Spam-Level: X-Spam-Status: No, score=-102.52 tagged_above=-999 required=5 tests=[AWL=0.079, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v1LLK0B5VC7E; Tue, 20 Mar 2012 05:40:15 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B26F821F8659; Tue, 20 Mar 2012 05:40:15 -0700 (PDT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 4.00 Message-ID: <20120320124015.27203.60470.idtracker@ietfa.amsl.com> Date: Tue, 20 Mar 2012 05:40:15 -0700 Cc: avtext@ietf.org Subject: [avtext] Last Call: (Considerations for Deploying the Rapid Acquisition of Multicast RTP Sessions (RAMS) Method) to Informational RFC X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: ietf@ietf.org List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2012 12:40:16 -0000 The IESG has received a request from the Audio/Video Transport Extensions WG (avtext) to consider the following document: - 'Considerations for Deploying the Rapid Acquisition of Multicast RTP Sessions (RAMS) Method' as an Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2012-04-03. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract The Rapid Acquisition of Multicast RTP Sessions (RAMS) solution is a method based on RTP and RTP Control Protocol (RTCP) that enables an RTP receiver to rapidly acquire and start consuming the RTP multicast data. Upon a request from the RTP receiver, an auxiliary unicast RTP retransmission session is set up between a retransmission server and the RTP receiver, over which the reference information about the new multicast stream the RTP receiver is about to join is transmitted at an accelerated rate. This often precedes, but may also accompany, the multicast stream itself. When there is only one multicast stream to be acquired, the RAMS solution works in a straightforward manner. However, when there are two or more multicast streams to be acquired from the same or different multicast RTP sessions, care should be taken to configure each RAMS session appropriately. This document provides example scenarios and discusses how the RAMS solution could be used in such scenarios. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-avtext-rams-scenarios/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-avtext-rams-scenarios/ballot/ No IPR declarations have been submitted directly on this I-D. From iesg-secretary@ietf.org Tue Mar 20 05:41:17 2012 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B934C21F8732; Tue, 20 Mar 2012 05:41:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.527 X-Spam-Level: X-Spam-Status: No, score=-102.527 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9SpROMZqncHV; Tue, 20 Mar 2012 05:41:17 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34FDE21F8702; Tue, 20 Mar 2012 05:41:17 -0700 (PDT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 4.00 Message-ID: <20120320124117.26613.27257.idtracker@ietfa.amsl.com> Date: Tue, 20 Mar 2012 05:41:17 -0700 Cc: avtext@ietf.org Subject: [avtext] Last Call: (Content Splicing for RTP Sessions) to Informational RFC X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: ietf@ietf.org List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2012 12:41:18 -0000 The IESG has received a request from the Audio/Video Transport Extensions WG (avtext) to consider the following document: - 'Content Splicing for RTP Sessions' as an Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2012-04-03. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This memo outlines RTP splicing. Splicing is a process that replaces the content of the main multimedia stream with other multimedia content, and delivers the substitutive multimedia content to receiver for a period of time. This memo provides some RTP splicing use cases, then we enumerate a set of requirements and analyze whether an existing RTP level middlebox can meet these requirements, at last we provide concrete guidelines for how the chosen middlebox works to handle RTP splicing. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-avtext-splicing-for-rtp/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-avtext-splicing-for-rtp/ballot/ No IPR declarations have been submitted directly on this I-D. From paromitaz@gmail.com Tue Mar 20 23:54:35 2012 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CECC421F84D0 for ; Tue, 20 Mar 2012 23:54:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.598 X-Spam-Level: X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C4UrdR3BTKAr for ; Tue, 20 Mar 2012 23:54:34 -0700 (PDT) Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id B43BE21F84CF for ; Tue, 20 Mar 2012 23:54:34 -0700 (PDT) Received: by ggmi1 with SMTP id i1so765437ggm.31 for ; Tue, 20 Mar 2012 23:54:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=poHYVKqIyoBRnN1iE68anb/AdYU11ynh7F+RvIsngHg=; b=xVgfHqQGonxqtkyM9KJgqUwnwciz1rLf+5Fq83+TgCJtjGtJWg86O4+FfP5fVvqZ7q 9RALHr6tehyCn/4MIbqEzAeGQKKqxdfFZ0cw33XyZdzRRB7iKAfsTaVv8rhAQqzSD9cz k0HaTirnY26Sr71Bk0pIjLvjzmrRat4rmCZdfYe2AIhltoD9jbRD+7eEsoL9UCCdBRMx tZAeLRqyR4G0bvVd3PkwhsZ9MGRUxMFkbbute1Bo2fcXynGSg0uaOZe9SOirKK3+kMJj nN9vzvBSRoyik+dFYsauan1WxKtmYjZ4iqOrxE+uKPyjLKjQWitRqTZLLYT8YypyoX5v 4tww== MIME-Version: 1.0 Received: by 10.236.178.102 with SMTP id e66mr2762169yhm.30.1332312874362; Tue, 20 Mar 2012 23:54:34 -0700 (PDT) Received: by 10.147.168.2 with HTTP; Tue, 20 Mar 2012 23:54:34 -0700 (PDT) Date: Tue, 20 Mar 2012 23:54:34 -0700 Message-ID: From: paromita chowdhury To: avtext@ietf.org Content-Type: multipart/alternative; boundary=20cf303f65ac9b259304bbbb434f X-Mailman-Approved-At: Wed, 21 Mar 2012 00:39:49 -0700 Subject: [avtext] Call flow of SIP protocol to changing media X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2012 06:54:35 -0000 --20cf303f65ac9b259304bbbb434f Content-Type: text/plain; charset=ISO-8859-1 Hi all, I need some help in understanding the SIP protocol in the case when the media parameters need to be changed. 1. Can SIP update message change the SDP media descriptions like Re-INVITE? 2. Under what scenarios does the CSeq field in SIP INVITE change? 3. Which field in the SIP message indicate the NAT traversal in necessary? Hope this is the right form to put forward my questions. Thanks --20cf303f65ac9b259304bbbb434f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi all,

I need some help in understanding the SIP protocol in the c= ase when the media parameters need to be changed.
1. Can SIP update mess= age change the SDP media descriptions like Re-INVITE?
2. Under what scen= arios does the CSeq field in SIP INVITE change?
3. Which field in the SIP message indicate the NAT traversal in necessary?<= br>
Hope this is the right form to put forward my questions.
Thanks<= br> --20cf303f65ac9b259304bbbb434f-- From kpfleming@digium.com Wed Mar 21 07:32:56 2012 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBB9321F86FF for ; Wed, 21 Mar 2012 07:32:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.56 X-Spam-Level: X-Spam-Status: No, score=-106.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0ZZDI7WytSf1 for ; Wed, 21 Mar 2012 07:32:56 -0700 (PDT) Received: from mail.digium.com (mail.digium.com [216.207.245.2]) by ietfa.amsl.com (Postfix) with ESMTP id 4BDC121F86F6 for ; Wed, 21 Mar 2012 07:32:56 -0700 (PDT) Received: from [10.24.55.203] (helo=zimbra.hsv.digium.com) by mail.digium.com with esmtp (Exim 4.69) (envelope-from ) id 1SAMat-0007o8-12 for avtext@ietf.org; Wed, 21 Mar 2012 09:32:55 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.hsv.digium.com (Postfix) with ESMTP id 0CDAFD8010 for ; Wed, 21 Mar 2012 09:32:55 -0500 (CDT) Received: from zimbra.hsv.digium.com ([127.0.0.1]) by localhost (zimbra.hsv.digium.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dth77-Cc2LRW for ; Wed, 21 Mar 2012 09:32:54 -0500 (CDT) Received: from [10.24.250.46] (unknown [10.24.250.46]) by zimbra.hsv.digium.com (Postfix) with ESMTPSA id B8B9ED8002 for ; Wed, 21 Mar 2012 09:32:54 -0500 (CDT) Message-ID: <4F69E696.80203@digium.com> Date: Wed, 21 Mar 2012 09:32:54 -0500 From: "Kevin P. Fleming" Organization: Digium, Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: avtext@ietf.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [avtext] Call flow of SIP protocol to changing media X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2012 14:32:56 -0000 On 03/21/2012 01:54 AM, paromita chowdhury wrote: > Hi all, > > I need some help in understanding the SIP protocol in the case when the > media parameters need to be changed. > 1. Can SIP update message change the SDP media descriptions like Re-INVITE? > 2. Under what scenarios does the CSeq field in SIP INVITE change? > 3. Which field in the SIP message indicate the NAT traversal in necessary? > > Hope this is the right form to put forward my questions. It is not the right forum. You would be better off to post your questions on the sip-implementors mailing list. -- Kevin P. Fleming Digium, Inc. | Director of Software Technologies Jabber: kfleming@digium.com | SIP: kpfleming@digium.com | Skype: kpfleming 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at www.digium.com & www.asterisk.org From magnus.westerlund@ericsson.com Mon Mar 26 08:52:59 2012 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E89D21E80A3 for ; Mon, 26 Mar 2012 08:52:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.391 X-Spam-Level: X-Spam-Status: No, score=-110.391 tagged_above=-999 required=5 tests=[AWL=0.208, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2IKcZMl12m7h for ; Mon, 26 Mar 2012 08:52:58 -0700 (PDT) Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 23B5A21E80C2 for ; Mon, 26 Mar 2012 08:52:54 -0700 (PDT) X-AuditID: c1b4fb39-b7bf2ae0000069a1-a9-4f7090d5f920 Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 87.FD.27041.5D0907F4; Mon, 26 Mar 2012 17:52:54 +0200 (CEST) Received: from [127.0.0.1] (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.3.213.0; Mon, 26 Mar 2012 17:52:53 +0200 Message-ID: <4F7090D4.1090509@ericsson.com> Date: Mon, 26 Mar 2012 17:52:52 +0200 From: Magnus Westerlund User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120312 Thunderbird/11.0 MIME-Version: 1.0 To: avtext@ietf.org References: <4F573BDD.1080004@ericsson.com> In-Reply-To: <4F573BDD.1080004@ericsson.com> X-Enigmail-Version: 1.4 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Brightmail-Tracker: AAAAAA== Subject: Re: [avtext] Call for editor on "Support for multiple clock rates in an RTP session" X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Mar 2012 15:52:59 -0000 WG, Thanks to all that volunteered. We chairs have picked Glen Zorn as the future editor of the draft-ietf-avtext-multiple-clock-rates. Once more thanks for Marc for his work so far. Cheers Magnus Westerlund On 2012-03-07 11:43, Magnus Westerlund wrote: > WG, > > The current author of "Support for multiple clock rates in an RTP > session" (draft-ietf-avtext-multiple-clock-rates-02) Marc Petit-Huguenin > will be unable to continue his work on this document. We thank him for > all his work so far. > > Thus we are looking for an editor that can help complete any remaining > work on this document. If you are willing to volunteer please send us > chairs a response to this email. > > Regards > > Magnus Westerlund > > ---------------------------------------------------------------------- > Multimedia Technologies, Ericsson Research EAB/TVM > ---------------------------------------------------------------------- > Ericsson AB | Phone +46 10 7148287 > Färögatan 6 | Mobile +46 73 0949079 > SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com > ---------------------------------------------------------------------- > > _______________________________________________ > avtext mailing list > avtext@ietf.org > https://www.ietf.org/mailman/listinfo/avtext > -- Magnus Westerlund ---------------------------------------------------------------------- Multimedia Technologies, Ericsson Research EAB/TVM ---------------------------------------------------------------------- Ericsson AB | Phone +46 10 7148287 Färögatan 6 | Mobile +46 73 0949079 SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com ---------------------------------------------------------------------- From keith.drage@alcatel-lucent.com Tue Mar 27 03:04:52 2012 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A01FE21E8134 for ; Tue, 27 Mar 2012 03:04:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -109.619 X-Spam-Level: X-Spam-Status: No, score=-109.619 tagged_above=-999 required=5 tests=[AWL=0.630, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bwi9MT1chzBr for ; Tue, 27 Mar 2012 03:04:46 -0700 (PDT) Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id 0344F21E8132 for ; Tue, 27 Mar 2012 03:04:45 -0700 (PDT) Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q2RA46ws001345 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Tue, 27 Mar 2012 12:04:44 +0200 Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.47]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Tue, 27 Mar 2012 12:04:39 +0200 From: "DRAGE, Keith (Keith)" To: "avtext@ietf.org" Date: Tue, 27 Mar 2012 12:04:38 +0200 Thread-Topic: Slides for AVTEXT session Thread-Index: Ac0MAQU0TNnZ6r6NQ+uuLLm8/yBj1g== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83 Subject: [avtext] Slides for AVTEXT session X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2012 10:04:52 -0000 (As WG cochair) All the slides for the AVTEXT session, except those for " IEEE 1588/802.1AS= Synchronisation for RTP Streams" are now uploaded to the meeting materials= site. I have just revised the chairs status slides to give some more status on th= e multiple clock rates draft. Regards Keith From keith.drage@alcatel-lucent.com Tue Mar 27 05:37:11 2012 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5313C21F8771 for ; Tue, 27 Mar 2012 05:37:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -109.631 X-Spam-Level: X-Spam-Status: No, score=-109.631 tagged_above=-999 required=5 tests=[AWL=0.618, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VZyJPInZpzeK for ; Tue, 27 Mar 2012 05:37:10 -0700 (PDT) Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id 9B90021E8087 for ; Tue, 27 Mar 2012 05:37:10 -0700 (PDT) Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q2RCYwXS016997 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Tue, 27 Mar 2012 14:37:07 +0200 Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.47]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Tue, 27 Mar 2012 14:37:04 +0200 From: "DRAGE, Keith (Keith)" To: "DRAGE, Keith (Keith)" , "avtext@ietf.org" Date: Tue, 27 Mar 2012 14:35:00 +0200 Thread-Topic: Slides for AVTEXT session Thread-Index: Ac0MAQU0TNnZ6r6NQ+uuLLm8/yBj1gAFPfHA Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83 Subject: Re: [avtext] Slides for AVTEXT session X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2012 12:37:11 -0000 All the slides are now there. Keith > -----Original Message----- > From: avtext-bounces@ietf.org [mailto:avtext-bounces@ietf.org] On Behalf > Of DRAGE, Keith (Keith) > Sent: 27 March 2012 11:05 > To: avtext@ietf.org > Subject: [avtext] Slides for AVTEXT session >=20 > (As WG cochair) >=20 > All the slides for the AVTEXT session, except those for " IEEE > 1588/802.1AS Synchronisation for RTP Streams" are now uploaded to the > meeting materials site. >=20 > I have just revised the chairs status slides to give some more status on > the multiple clock rates draft. >=20 > Regards >=20 > Keith > _______________________________________________ > avtext mailing list > avtext@ietf.org > https://www.ietf.org/mailman/listinfo/avtext