From ron.even.tlv@gmail.com Thu Oct 4 16:36:40 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74D7E21F8668 for ; Thu, 4 Oct 2012 16:36:40 -0700 (PDT) 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.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hj0+aMR94Bt3 for ; Thu, 4 Oct 2012 16:36:40 -0700 (PDT) Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8393A21F8667 for ; Thu, 4 Oct 2012 16:36:39 -0700 (PDT) Received: by mail-wg0-f44.google.com with SMTP id dr13so636907wgb.13 for ; Thu, 04 Oct 2012 16:36:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=SIO74GYm8HtyWvUnlL4ifCGiVziwsiDN2cnxaoJ1xA4=; b=exYedg58y8HxSeaxEucpC8Fmfr1dLwaR/rBc33ofFLWLyudQCzcXcIEJzl5lx4WFQN BSKtWt7XZz/ZWGzTNPfhA03bQDCbHwLDc1WtVl5pUkcawLLHj2l0kItDPk2OT0q0074K +DfJUVQWnFn+napVtLc1SYIYWDjDIGfWzKFo3WTibUFgcGQ8+1RIEAXN9bCqcfqMSjVA lya2WejW26VoRZmg9Hafn0Qb0nGuqExKEijEPZu0gNtKNWcg2HaF0J+5UNzSqB2jtTUk TV5cHr4kQqNdlAGJ62J5NTLbalmO7Kjk7Gtl687q1/umuUbyd6uFttA4BuRyEmIBMmTE ykTQ== Received: by 10.180.87.42 with SMTP id u10mr16322633wiz.0.1349393798394; Thu, 04 Oct 2012 16:36:38 -0700 (PDT) Received: from RoniE (bzq-79-176-243-9.red.bezeqint.net. [79.176.243.9]) by mx.google.com with ESMTPS id b7sm34917813wiz.3.2012.10.04.16.36.36 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 04 Oct 2012 16:36:37 -0700 (PDT) From: "Roni Even" To: Date: Fri, 5 Oct 2012 01:34:41 +0200 Message-ID: <01ac01cda288$d5a5d780$80f18680$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01AD_01CDA299.992FB8F0" X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac2iiDEZp2J1FjiqTFmpvwnKWZuZLw== Content-Language: en-us Cc: Magnus Westerlund Subject: [AVTCORE] avtcore -session for IETF85 -requests for agenda time X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Oct 2012 23:36:40 -0000 This is a multipart message in MIME format. ------=_NextPart_000_01AD_01CDA299.992FB8F0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, This is the schedule for AVTcore. Note that the agenda is not final and can change. Final meeting agenda will be published on October 10th . avtcore Session 1 (2:00:00) Monday November 5th , Afternoon Session I 1300-1500 Room Name: Grand Ballroom D --------------------------------------------- avtcore Session 2 (1:00:00) Thursday November 8th , Afternoon Session III 1730-1830 Room Name: Salon D --------------------------------------------- If you wish to have agenda time at the upcoming meeting in Atlanta regarding AVTcore work, please send an agenda request to the AVTcore chairs. We are trying to prepare the agenda early and not wait for the last minute. Payload WG is not meeting in Paris and we may allocate some time to resolve open issues regarding payload drafts time permitting. Note the document submission deadline are October 15th for initial document (00 drafts) and October 22nd is the final submission date. Roni Even AVTcore co-chair ------=_NextPart_000_01AD_01CDA299.992FB8F0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 
Hi,
This is =
the schedule for AVTcore.  Note that the agenda is not final and =
can change. Final meeting agenda will be published on October =
10th .
 =

 

    avtcore Session 1 = (2:00:00)

    = Monday November 5th , Afternoon Session I = 1300-1500

    Room = Name: Grand Ballroom D

  =

  ----------------------------------------= -----

    avtcore = Session 2 (1:00:00)

    Thursday November 8th = , Afternoon Session III 1730-1830

    Room Name: Salon = D

    = ---------------------------------------------

 

 

If you = wish to have agenda time at the upcoming meeting in Atlanta regarding = AVTcore work, please send an agenda request to the AVTcore chairs. We = are trying to prepare the agenda early and not wait for the last = minute.

 =

Payload WG = is not meeting in Paris and we may allocate some time to resolve open = issues regarding payload drafts time permitting. =

 =

Note the = document submission deadline are October 15th   for = initial document (00 drafts) and October 22nd  is the = final submission date.

 =

Roni = Even

AVTcore = co-chair

 =

 

------=_NextPart_000_01AD_01CDA299.992FB8F0-- From ron.even.tlv@gmail.com Fri Oct 5 09:42:38 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75C8321F86B5 for ; Fri, 5 Oct 2012 09:42:38 -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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T0RgYk+6ErOt for ; Fri, 5 Oct 2012 09:42:38 -0700 (PDT) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id 8F69521F8692 for ; Fri, 5 Oct 2012 09:42:37 -0700 (PDT) Received: by mail-wi0-f178.google.com with SMTP id hr7so745851wib.13 for ; Fri, 05 Oct 2012 09:42:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=IKXNTPYNhg3NFDgJ6YveDn0Qke9U2zCHz1nSMJEVCZc=; b=QWsYIb58acb6fBtl1jiu7j+UaCseCzpkyCWZpN8UEAIhNVC54nx1NqTU6v9vhSmgb8 6BekGbIdx9UjvAXrgvRf2kwP/sULmwJIWOL3osEQq6NI1G6gsJCv21GvUiy4gJBgOkMo +/Mcj2ClwsJMHmgri78LRR0rZlIr0ZXFOihzLzRl0nNwziYOYmxnnXJ4I/VHp3q959K/ GXp1azGAUxfetBe2JHqmVOecE0rIbTvoAsjIallbj4DsngryX2cCQjq3Q65+0DSl37cl 5Tfm+hKyuuo+kd+vaMiH7Foco+gjqLHvlCQWDZoRHJhcJzRkWKD1i7pbrCfELGHZa2hg 6U/Q== Received: by 10.180.8.161 with SMTP id s1mr4683321wia.0.1349455356733; Fri, 05 Oct 2012 09:42:36 -0700 (PDT) Received: from RoniE (bzq-79-176-243-9.red.bezeqint.net. [79.176.243.9]) by mx.google.com with ESMTPS id ei1sm3289509wid.7.2012.10.05.09.42.33 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 05 Oct 2012 09:42:35 -0700 (PDT) From: "Roni Even" To: Date: Fri, 5 Oct 2012 18:40:39 +0200 Message-ID: <020301cda318$29571d50$7c0557f0$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0204_01CDA328.ECE06280" X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac2jF15uI7KFnm50TJmAOSTIsHNdkA== Content-Language: en-us Cc: Magnus Westerlund , 'Colin Perkins' , 'Jonathan Lennox' Subject: [AVTCORE] draft-westerlund-avtcore-multi-media-rtp-session-00 as a WG document X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Oct 2012 16:42:38 -0000 This is a multipart message in MIME format. ------=_NextPart_000_0204_01CDA328.ECE06280 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, At IETF84 there was a strong consensus to accept http://tools.ietf.org/html/draft-westerlund-avtcore-multi-media-rtp-session- 00 as the initial document to address the support for Multiple Media Types in an RTP Session. This work is required for the RTCweb for multiplexing multiple media and more specifically audio and video in an RTP session. The authors of the individual draft will submit it as a WG document before the deadline for IETF85. Thanks Roni Even AVTcore co-chair ------=_NextPart_000_0204_01CDA328.ECE06280 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

At IETF84 there = was a strong consensus to accept http://tools.ietf.org/html/draft-westerlund-avtcore-multi-= media-rtp-session-00 as the initial document to address  the = support for Multiple Media Types in an RTP Session. This = work is required for the RTCweb for multiplexing multiple media and more = specifically audio and video in an RTP session.

 

The authors of the individual draft = will submit it as a WG document before the deadline for = IETF85.

 

Thanks

Roni Even

AVTcore co-chair

 

 

------=_NextPart_000_0204_01CDA328.ECE06280-- From iesg-secretary@ietf.org Fri Oct 5 11:25:28 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED91621F8799; Fri, 5 Oct 2012 11:25:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.5 X-Spam-Level: X-Spam-Status: No, score=-102.5 tagged_above=-999 required=5 tests=[AWL=0.099, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z1ALEvYmaZa6; Fri, 5 Oct 2012 11:25:28 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E279521F8808; Fri, 5 Oct 2012 11:25:27 -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.34 Message-ID: <20121005182527.30343.32985.idtracker@ietfa.amsl.com> Date: Fri, 05 Oct 2012 11:25:27 -0700 Cc: avtcore chair , avtcore mailing list , RFC Editor Subject: [AVTCORE] Document Action: 'Guidelines for Use of the RTP Monitoring Framework' to Informational RFC (draft-ietf-avtcore-monarch-22.txt) X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Oct 2012 18:25:29 -0000 The IESG has approved the following document: - 'Guidelines for Use of the RTP Monitoring Framework' (draft-ietf-avtcore-monarch-22.txt) as Informational RFC This document is the product of the Audio/Video Transport Core Maintenance Working Group. The IESG contact persons are Robert Sparks and Gonzalo Camarillo. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-avtcore-monarch/ Technical Summary This memo describes the extensible RTP monitoring framework for using RTP Control Protocol (RTCP) with new RTCP Extended Reports (XR) block type to report new metrics regarding media transmission or reception quality. In this framework, any new XR block should contain a single metric or a small number of metrics relevant to a single parameter of interest or concern, rather than containing a number of metrics which attempt to provide full coverage of all those parameters of concern to a specific application. Applications may then "mix and match" to create a set of blocks which covers their set of concerns. Where possible, a specific block should be designed to be re-usable across more than one application, for example, for all of voice, streaming audio and video. Working Group Summary This document was jointly last called with XRBLOCK WG, one of the primary consumer of these architectural considerations. It was significantly rewritten as the result of the AD review as it didn't meet the goals of an architecture specificaiton, and was more focused on the issues which the WG had come to consensus on. The changes has been WG last called and consensus exist for moving forward with these changes. Document Quality There are ongoing usage of the principles for extensions described in this document within the XRBLOCK WG. The document has been reviewed by a number of people in both AVTCORE and XRBLOCK WG. The AD found a significant scope problem which has been resolved. Personnel Magnus Westerlund is the Document Shepherd. The Responsible Area Director is Robert Sparks. From ray.vanbrandenburg@tno.nl Mon Oct 8 04:32:12 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C6CA21F8786 for ; Mon, 8 Oct 2012 04:32:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.503 X-Spam-Level: X-Spam-Status: No, score=-0.503 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fa7nMKrstznP for ; Mon, 8 Oct 2012 04:32:10 -0700 (PDT) Received: from fromintoutb.tno.nl (fromintoutb.tno.nl [134.221.1.27]) by ietfa.amsl.com (Postfix) with ESMTP id 192B021F85D5 for ; Mon, 8 Oct 2012 04:32:09 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.80,553,1344204000"; d="scan'208,217";a="16430991" Received: from unknown (HELO mail.tno.nl) ([134.221.225.221]) by mailhost1b.tno.nl with ESMTP; 08 Oct 2012 13:32:08 +0200 Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.243]) by EXC-CASHUB02.tsn.tno.nl ([134.221.225.221]) with mapi id 14.02.0298.004; Mon, 8 Oct 2012 13:32:08 +0200 From: "Brandenburg, R. (Ray) van" To: "avt@ietf.org" Thread-Topic: Status of IDMS draft Thread-Index: Ac2lReqktVTtxFEUQlKX5TSmYf7Fug== Date: Mon, 8 Oct 2012 11:32:07 +0000 Message-ID: Accept-Language: en-US, nl-NL Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [134.221.225.153] Content-Type: multipart/alternative; boundary="_000_FCC100FC8D6B034CB88CD8173B2DA1581C6C5D13EXCMBX03tsntnon_" MIME-Version: 1.0 Cc: "magnus.westerlund@ericsson.com" Subject: [AVTCORE] Status of IDMS draft X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Oct 2012 11:32:12 -0000 --_000_FCC100FC8D6B034CB88CD8173B2DA1581C6C5D13EXCMBX03tsntnon_ Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Dear chairs, all, It has been some while since you've heard anything about the IDMS draft. Th= e main reason for that is that I've been working behind the scenes on tryin= g to solve some of the open issues that came up in the Vancouver meeting. I will post a new version of the draft somewhere later this week, which hop= efully resolves all of the open points. However, there is one topic which I= have not been able to resolve and which I would like to ask your opinion o= n. This point is related to the discussion we had in Vancouver about the re= lationship with ETSI. As you all know, the current draft references an XR b= lock defined by ETSI. While the current draft does not change the XR block = itself, it does provide some further guidelines for using the block (which = do not conflict with the guidelines in the ETSI document). Based on these f= acts Keith Drage proposed to try to work with ETSI on changing the ETSI doc= ument so that it points to the new guidelines in the IETF document. In the past two months I've both been cooperating with my colleagues who us= ed to participate in ETSI and having a discussion with Keith on how we can = address this request. This topic is however complicated by the fact that th= e ETSI group who created the document no longer exist and the document is n= ow owned by another ETSI group (E2NA). However, attendance and participatio= n in this new group has plummeted to the point where most meeting are only = attended by a handful of people. Given this climate and the lack of activit= y in E2NA in general my colleagues and I feel that it is not possible nor j= ustifiable in practice to try and create a new work item within this group = to try and open up the relevant document and make the requested changes. We therefore propose to leave the ETSI document as is, and include a normat= ive reference to it in the IDMS draft. If anybody has any opinion on this matter, please voice your opinion on the= list. Best regards, Ray van Brandenburg This e-mail and its contents are subject to the DISCLAIMER at http://www.tn= o.nl/emaildisclaimer --_000_FCC100FC8D6B034CB88CD8173B2DA1581C6C5D13EXCMBX03tsntnon_ Content-Type: text/html; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable
Dear chairs, all,
 
It has been some while since you’ve heard anything about the IDM= S draft. The main reason for that is that I’ve been working behind th= e scenes on trying to solve some of the open issues that came up in the Van= couver meeting.
 
I will post a new version of the draft somewhere later this week, whic= h hopefully resolves all of the open points. However, there is one topic wh= ich I have not been able to resolve and which I would like to ask your opin= ion on. This point is related to the discussion we had in Vancouver about the relationship with ETSI. As you= all know, the current draft references an XR block defined by ETSI. While = the current draft does not change the XR block itself, it does provide some= further guidelines for using the block (which do not conflict with the guidelines in the ETSI document). Bas= ed on these facts Keith Drage proposed to try to work with ETSI on changing= the ETSI document so that it points to the new guidelines in the IETF docu= ment.
 
In the past two months I’ve both been cooperating with my collea= gues who used to participate in ETSI and having a discussion with Keith on = how we can address this request. This topic is however complicated by the f= act that the ETSI group who created the document no longer exist and the document is now owned by another ETSI grou= p (E2NA). However, attendance and participation in this new group has plumm= eted to the point where most meeting are only attended by a handful of peop= le. Given this climate and the lack of activity in E2NA in general my colleagues and I feel that it is not poss= ible nor justifiable in practice to try and create a new work item within t= his group to try and open up the relevant document and make the requested c= hanges.
 
We therefore propose to leave the ETSI document as is, and include a n= ormative reference to it in the IDMS draft.
 
If anybody has any opinion on this matter, please voice your opinion o= n the list.
 
Best regards,
 
Ray van Brandenburg
 

This e-mail and its contents are subject to the DISCLAIMER at http://www= .tno.nl/emaildisclaimer

--_000_FCC100FC8D6B034CB88CD8173B2DA1581C6C5D13EXCMBX03tsntnon_-- From roni.even@mail01.huawei.com Mon Oct 8 07:10:18 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9F1721F87BC for ; Mon, 8 Oct 2012 07:10:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9l+PxFkVISwY for ; Mon, 8 Oct 2012 07:10:17 -0700 (PDT) Received: from hwsga02-in.huaweimarine.com (hwsga02-in.huaweimarine.com [119.145.15.224]) by ietfa.amsl.com (Postfix) with ESMTP id 2CB8921F85C3 for ; Mon, 8 Oct 2012 07:10:17 -0700 (PDT) Received: from szxpml203-edg.exmail.huawei.com ([172.17.1.119]) by hwsga02-in.huaweimarine.com (MOS 4.1.3-GA) with ESMTP id ADO76948; Mon, 8 Oct 2012 22:07:56 +0800 X-Mirapoint-Received-SPF: 172.17.1.119 szxpml203-edg.exmail.huawei.com 5 none X-Mirapoint-Received-SPF: 172.17.1.119 szxpml203-edg.exmail.huawei.com 5 none X-Mirapoint-Received-SPF: 172.17.1.119 szxpml203-edg.exmail.huawei.com 5 none X-Mirapoint-Received-SPF: 172.17.1.119 szxpml203-edg.exmail.huawei.com 5 none Received: from SZXPML405-HUB.exmail.huawei.com (10.82.67.69) by szxpml203-edg.exmail.huawei.com (172.24.2.14) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 8 Oct 2012 22:07:50 +0800 Received: from SZXPML504-MBX.exmail.huawei.com ([169.254.3.38]) by szxpml405-hub.exmail.huawei.com ([10.82.67.69]) with mapi id 14.01.0323.003; Mon, 8 Oct 2012 22:07:55 +0800 From: Roni Even To: "Brandenburg, R. (Ray) van" , "avt@ietf.org" Thread-Topic: Status of IDMS draft Thread-Index: Ac2lReqktVTtxFEUQlKX5TSmYf7FugAFteQL Date: Mon, 8 Oct 2012 14:07:55 +0000 Message-ID: <760B7D45D1EFF74988DBF5C2122830C205B44B13@szxpml504-mbx.exmail.huawei.com> References: In-Reply-To: Accept-Language: en-US, zh-CN Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.24.1.61] Content-Type: multipart/alternative; boundary="_000_760B7D45D1EFF74988DBF5C2122830C205B44B13szxpml504mbxexm_" MIME-Version: 1.0 Cc: "magnus.westerlund@ericsson.com" Subject: Re: [AVTCORE] Status of IDMS draft X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Oct 2012 14:10:18 -0000 --_000_760B7D45D1EFF74988DBF5C2122830C205B44B13szxpml504mbxexm_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi Ray, I was OK with the current text in section 12.1 and section 7. I will be OK with any understanding you and Keith can come with to clarify = the status of not havong cross refernces. It may be good to have some text, maybe as an appendix, that will describe = the current status as stated in this email and probably some information ab= out deployment if available. I assume that there may be issues if ETSI will try to update their document= without considering the IETF work but it looks to me from your emeil that = it is low probablity. Roni Even ________________________________ From: avt-bounces@ietf.org [avt-bounces@ietf.org] on behalf of Brandenburg,= R. (Ray) van [ray.vanbrandenburg@tno.nl] Sent: Monday, October 08, 2012 1:32 PM To: avt@ietf.org Cc: magnus.westerlund@ericsson.com Subject: [AVTCORE] Status of IDMS draft Dear chairs, all, It has been some while since you=92ve heard anything about the IDMS draft. = The main reason for that is that I=92ve been working behind the scenes on t= rying to solve some of the open issues that came up in the Vancouver meetin= g. I will post a new version of the draft somewhere later this week, which hop= efully resolves all of the open points. However, there is one topic which I= have not been able to resolve and which I would like to ask your opinion o= n. This point is related to the discussion we had in Vancouver about the re= lationship with ETSI. As you all know, the current draft references an XR b= lock defined by ETSI. While the current draft does not change the XR block = itself, it does provide some further guidelines for using the block (which = do not conflict with the guidelines in the ETSI document). Based on these f= acts Keith Drage proposed to try to work with ETSI on changing the ETSI doc= ument so that it points to the new guidelines in the IETF document. In the past two months I=92ve both been cooperating with my colleagues who = used to participate in ETSI and having a discussion with Keith on how we ca= n address this request. This topic is however complicated by the fact that = the ETSI group who created the document no longer exist and the document is= now owned by another ETSI group (E2NA). However, attendance and participat= ion in this new group has plummeted to the point where most meeting are onl= y attended by a handful of people. Given this climate and the lack of activ= ity in E2NA in general my colleagues and I feel that it is not possible nor= justifiable in practice to try and create a new work item within this grou= p to try and open up the relevant document and make the requested changes. We therefore propose to leave the ETSI document as is, and include a normat= ive reference to it in the IDMS draft. If anybody has any opinion on this matter, please voice your opinion on the= list. Best regards, Ray van Brandenburg This e-mail and its contents are subject to the DISCLAIMER at http://www.tn= o.nl/emaildisclaimer --_000_760B7D45D1EFF74988DBF5C2122830C205B44B13szxpml504mbxexm_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable

Hi Ray,

I was OK with the current text in section 12.1 and section 7.

I will be OK with any understanding you and Keith can come with to clari= fy the status of not havong cross refernces.

It may be good to have some text, maybe as an appendix, that will descri= be the current status as stated in this email and probably some information= about deployment if available. 

I assume that there may be issues if ETSI will try to update their docum= ent without considering the IETF work but it looks to me from your emeil th= at it is low probablity.

 

Roni Even

 

From: avt-bounces@ietf.org [avt-bounces@ie= tf.org] on behalf of Brandenburg, R. (Ray) van [ray.vanbrandenburg@tno.nl]<= br> Sent: Monday, October 08, 2012 1:32 PM
To: avt@ietf.org
Cc: magnus.westerlund@ericsson.com
Subject: [AVTCORE] Status of IDMS draft

Dear chairs, all,
 
It has been some while since you=92ve heard anything about the IDMS dr= aft. The main reason for that is that I=92ve been working behind the scenes= on trying to solve some of the open issues that came up in the Vancouver m= eeting.
 
I will post a new version of the draft somewhere later this week, whic= h hopefully resolves all of the open points. However, there is one topic wh= ich I have not been able to resolve and which I would like to ask your opin= ion on. This point is related to the discussion we had in Vancouver about the relationship with ETSI. As yo= u all know, the current draft references an XR block defined by ETSI. While= the current draft does not change the XR block itself, it does provide som= e further guidelines for using the block (which do not conflict with the guidelines in the ETSI document). Ba= sed on these facts Keith Drage proposed to try to work with ETSI on changin= g the ETSI document so that it points to the new guidelines in the IETF doc= ument.
 
In the past two months I=92ve both been cooperating with my colleagues= who used to participate in ETSI and having a discussion with Keith on how = we can address this request. This topic is however complicated by the fact = that the ETSI group who created the document no longer exist and the document is now owned by another ETSI gro= up (E2NA). However, attendance and participation in this new group has plum= meted to the point where most meeting are only attended by a handful of peo= ple. Given this climate and the lack of activity in E2NA in general my colleagues and I feel that it is no= t possible nor justifiable in practice to try and create a new work item wi= thin this group to try and open up the relevant document and make the reque= sted changes.
 
We therefore propose to leave the ETSI document as is, and include a n= ormative reference to it in the IDMS draft.
 
If anybody has any opinion on this matter, please voice your opinion o= n the list.
 
Best regards,
 
Ray van Brandenburg
 

This e-mail and its contents are subject to the DISCLAIMER at http://www= .tno.nl/emaildisclaimer

--_000_760B7D45D1EFF74988DBF5C2122830C205B44B13szxpml504mbxexm_-- From ray.vanbrandenburg@tno.nl Mon Oct 8 07:23:28 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5417221F8455 for ; Mon, 8 Oct 2012 07:23:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.503 X-Spam-Level: X-Spam-Status: No, score=-0.503 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MaNzzITvRUNl for ; Mon, 8 Oct 2012 07:23:26 -0700 (PDT) Received: from fromintouta.tno.nl (fromintouta.tno.nl [134.221.1.26]) by ietfa.amsl.com (Postfix) with ESMTP id D789221F844C for ; Mon, 8 Oct 2012 07:23:25 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.80,554,1344204000"; d="scan'208,217";a="77064776" Received: from unknown (HELO mail.tno.nl) ([134.221.225.222]) by mailhost1a.tno.nl with ESMTP; 08 Oct 2012 16:23:13 +0200 Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.243]) by EXC-CASHUB03.tsn.tno.nl ([134.221.225.222]) with mapi id 14.02.0298.004; Mon, 8 Oct 2012 16:23:13 +0200 From: "Brandenburg, R. (Ray) van" To: Roni Even , "avt@ietf.org" Thread-Topic: Status of IDMS draft Thread-Index: Ac2lReqktVTtxFEUQlKX5TSmYf7FugAFteQLAADXtMA= Date: Mon, 8 Oct 2012 14:23:12 +0000 Message-ID: References: <760B7D45D1EFF74988DBF5C2122830C205B44B13@szxpml504-mbx.exmail.huawei.com> In-Reply-To: <760B7D45D1EFF74988DBF5C2122830C205B44B13@szxpml504-mbx.exmail.huawei.com> Accept-Language: en-US, nl-NL Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [134.221.225.153] Content-Type: multipart/alternative; boundary="_000_FCC100FC8D6B034CB88CD8173B2DA1581C6C601FEXCMBX03tsntnon_" MIME-Version: 1.0 Cc: "magnus.westerlund@ericsson.com" Subject: Re: [AVTCORE] Status of IDMS draft X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Oct 2012 14:23:28 -0000 --_000_FCC100FC8D6B034CB88CD8173B2DA1581C6C601FEXCMBX03tsntnon_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all, One clarification to my mail below: the 'we' in my sentence 'we therefore p= ropose...' represents the proposal by myself and my TNO colleagues and does= necessarily represent Keith's views. Ray ________________________________ From: avt-bounces@ietf.org [avt-bounces@ietf.o= rg] on behalf of Brandenburg, R. (Ray) van [ray.vanbrandenburg@tno.nl] Sent: Monday, October 08, 2012 1:32 PM To: avt@ietf.org Cc: magnus.westerlund@ericsson.com Subject: [AVTCORE] Status of IDMS draft Dear chairs, all, It has been some while since you've heard anything about the IDMS draft. Th= e main reason for that is that I've been working behind the scenes on tryin= g to solve some of the open issues that came up in the Vancouver meeting. I will post a new version of the draft somewhere later this week, which hop= efully resolves all of the open points. However, there is one topic which I= have not been able to resolve and which I would like to ask your opinion o= n. This point is related to the discussion we had in Vancouver about the re= lationship with ETSI. As you all know, the current draft references an XR b= lock defined by ETSI. While the current draft does not change the XR block = itself, it does provide some further guidelines for using the block (which = do not conflict with the guidelines in the ETSI document). Based on these f= acts Keith Drage proposed to try to work with ETSI on changing the ETSI doc= ument so that it points to the new guidelines in the IETF document. In the past two months I've both been cooperating with my colleagues who us= ed to participate in ETSI and having a discussion with Keith on how we can = address this request. This topic is however complicated by the fact that th= e ETSI group who created the document no longer exist and the document is n= ow owned by another ETSI group (E2NA). However, attendance and participatio= n in this new group has plummeted to the point where most meeting are only = attended by a handful of people. Given this climate and the lack of activit= y in E2NA in general my colleagues and I feel that it is not possible nor j= ustifiable in practice to try and create a new work item within this group = to try and open up the relevant document and make the requested changes. We therefore propose to leave the ETSI document as is, and include a normat= ive reference to it in the IDMS draft. If anybody has any opinion on this matter, please voice your opinion on the= list. Best regards, Ray van Brandenburg This e-mail and its contents are subject to the DISCLAIMER at http://www.tn= o.nl/emaildisclaimer --_000_FCC100FC8D6B034CB88CD8173B2DA1581C6C601FEXCMBX03tsntnon_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi all,

 = ;

One clarif= ication to my mail below: the ‘we’ in my sentence ‘we the= refore propose…’ represents the proposal by myself and my TNO c= olleagues and does necessarily represent Keith’s views.


Ray

 

From: avt-bounces@ietf.org [avt-bounc= es@ietf.org] on behalf of Brandenburg, R. (Ray) van [ray.vanbrandenburg@tno= .nl]
Sent: Monday, October 08, 2012 1:32 PM
To: avt@ietf.org
Cc: magnus.westerl= und@ericsson.com
Subject: [AVTCORE] Status of IDMS draft

Dear chairs, all,

 

It has been some while sinc= e you’ve heard anything about the IDMS draft. The main reason for tha= t is that I’ve been working behind the scenes on trying to solve some of the open issues that came up in the Vancouver meeting. =

 

I will post a new version o= f the draft somewhere later this week, which hopefully resolves all of the = open points. However, there is one topic which I have not been able to resolve and which I would like to ask your opinion on. This p= oint is related to the discussion we had in Vancouver about the relationshi= p with ETSI. As you all know, the current draft references an XR block defi= ned by ETSI. While the current draft does not change the XR block itself, it does provide some further guidelin= es for using the block (which do not conflict with the guidelines in the ET= SI document). Based on these facts Keith Drage proposed to try to work with= ETSI on changing the ETSI document so that it points to the new guidelines in the IETF document. <= /span>

 

In the past two months I= 217;ve both been cooperating with my colleagues who used to participate in = ETSI and having a discussion with Keith on how we can address this request. This topic is however complicated by the fact that the ETSI = group who created the document no longer exist and the document is now owne= d by another ETSI group (E2NA). However, attendance and participation in th= is new group has plummeted to the point where most meeting are only attended by a handful of people. Given t= his climate and the lack of activity in E2NA in general my colleagues and I= feel that it is not possible nor justifiable in practice to try and create= a new work item within this group to try and open up the relevant document and make the requested changes. <= o:p>

 

We therefore propose to lea= ve the ETSI document as is, and include a normative reference to it in the = IDMS draft.

 

If anybody has any opinion = on this matter, please voice your opinion on the list.

 

Best regards,

 

Ray van Brandenburg

 

This e-mail and its contents are subject to = the DISCLAIMER at http://www.tno.nl/emaildiscla= imer

--_000_FCC100FC8D6B034CB88CD8173B2DA1581C6C601FEXCMBX03tsntnon_-- From internet-drafts@ietf.org Thu Oct 11 00:19:01 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14EB921F8514; Thu, 11 Oct 2012 00:19:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -98.52 X-Spam-Level: X-Spam-Status: No, score=-98.52 tagged_above=-999 required=5 tests=[AWL=-3.897, BAYES_00=-2.599, FRT_STOCK1=3.988, FRT_STOCK2=3.988, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SGxoyYLMz7RU; Thu, 11 Oct 2012 00:19:00 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F7F721F84F9; Thu, 11 Oct 2012 00:19:00 -0700 (PDT) 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.34 Message-ID: <20121011071900.24901.9484.idtracker@ietfa.amsl.com> Date: Thu, 11 Oct 2012 00:19:00 -0700 Cc: avt@ietf.org Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-idms-07.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2012 07:19: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 Core Maintenance Wo= rking Group of the IETF. Title : Inter-destination Media Synchronization using the RTP Co= ntrol Protocol (RTCP) Author(s) : Ray van Brandenburg Hans Stokking Oskar van Deventer Fernando Boronat Mario Montagud Kevin Gross Filename : draft-ietf-avtcore-idms-07.txt Pages : 24 Date : 2012-10-11 Abstract: This document gives information on an RTP Control Protocol (RTCP) Packet Type and RTCP Extended Report (XR) Block Type including associated Session Description Protocol (SDP) parameters for Inter- Destination Media Synchronization (IDMS). This document mandates the use of the RTCP XR Block Type 12, which is used to collect media playout information from participants in a group playing out (watching, listening, etc.) a specific RTP media stream. This RTCP XR Block Type is specified and registered with IANA by ETSI. The RTCP packet type specified by this document is used to distribute a common target playout point to which all the distributed receivers, sharing a media experience, can synchronize. Typical use cases in which IDMS is usefull are social TV, shared service control (i.e. applications where two or more geographically separated users are watching a media stream together), distance learning, networked video walls, networked loudspeakers, etc. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avtcore-idms There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-avtcore-idms-07 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-idms-07 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From ray.vanbrandenburg@tno.nl Thu Oct 11 00:24:17 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68A8521F8551 for ; Thu, 11 Oct 2012 00:24:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.098 X-Spam-Level: *** X-Spam-Status: No, score=3.098 tagged_above=-999 required=5 tests=[AWL=-4.374, BAYES_00=-2.599, FRT_STOCK1=3.988, FRT_STOCK2=3.988, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E4-1u-AfpORC for ; Thu, 11 Oct 2012 00:24:16 -0700 (PDT) Received: from fromintoutb.tno.nl (fromintoutb.tno.nl [134.221.1.27]) by ietfa.amsl.com (Postfix) with ESMTP id F37B021F854E for ; Thu, 11 Oct 2012 00:24:12 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.80,570,1344204000"; d="scan'208";a="16465724" Received: from unknown (HELO mail.tno.nl) ([134.221.225.220]) by mailhost1b.tno.nl with ESMTP; 11 Oct 2012 09:24:11 +0200 Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.243]) by EXC-CASHUB01.tsn.tno.nl ([134.221.225.220]) with mapi id 14.02.0298.004; Thu, 11 Oct 2012 09:24:11 +0200 From: "Brandenburg, R. (Ray) van" To: "avt@ietf.org" Thread-Topic: [AVTCORE] I-D Action: draft-ietf-avtcore-idms-07.txt Thread-Index: AQHNp4C7nMu6inEfPEW4UqExDJ0/1JezsuiA Date: Thu, 11 Oct 2012 07:24:11 +0000 Message-ID: References: <20121011071900.24901.9484.idtracker@ietfa.amsl.com> In-Reply-To: <20121011071900.24901.9484.idtracker@ietfa.amsl.com> Accept-Language: en-US, nl-NL Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [134.221.225.191] Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: [AVTCORE] FW: I-D Action: draft-ietf-avtcore-idms-07.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2012 07:24:17 -0000 Hi all, I've just uploaded a new version of the IDMS draft. This new version includ= es the comments received during the WGLC which were not yet included in the= -06 version and a solution to the packet reporting issue that we discussed= in Vancouver. I believe that with this version all WGLC comments have been addressed. = Best regards, Ray van Brandenburg -----Original Message----- From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of inter= net-drafts@ietf.org Sent: donderdag 11 oktober 2012 9:19 To: i-d-announce@ietf.org Cc: avt@ietf.org Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-idms-07.txt 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 Core Maintenance Wo= rking Group of the IETF. Title : Inter-destination Media Synchronization using the RTP Co= ntrol Protocol (RTCP) Author(s) : Ray van Brandenburg Hans Stokking Oskar van Deventer Fernando Boronat Mario Montagud Kevin Gross Filename : draft-ietf-avtcore-idms-07.txt Pages : 24 Date : 2012-10-11 Abstract: This document gives information on an RTP Control Protocol (RTCP) Packet Type and RTCP Extended Report (XR) Block Type including associated Session Description Protocol (SDP) parameters for Inter- Destination Media Synchronization (IDMS). This document mandates the use of the RTCP XR Block Type 12, which is used to collect media playout information from participants in a group playing out (watching, listening, etc.) a specific RTP media stream. This RTCP XR Block Type is specified and registered with IANA by ETSI. The RTCP packet type specified by this document is used to distribute a common target playout point to which all the distributed receivers, sharing a media experience, can synchronize. Typical use cases in which IDMS is usefull are social TV, shared service control (i.e. applications where two or more geographically separated users are watching a media stream together), distance learning, networked video walls, networked loudspeakers, etc. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avtcore-idms There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-avtcore-idms-07 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-idms-07 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ Audio/Video Transport Core Maintenance avt@ietf.org https://www.ietf.org/mailman/listinfo/avt This e-mail and its contents are subject to the DISCLAIMER at http://www.tn= o.nl/emaildisclaimer From magnus.westerlund@ericsson.com Thu Oct 11 04:22:49 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AD2D21F86D1 for ; Thu, 11 Oct 2012 04:22:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.229 X-Spam-Level: X-Spam-Status: No, score=-106.229 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sRdbSM3pRQV2 for ; Thu, 11 Oct 2012 04:22:48 -0700 (PDT) Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 438DA21F865B for ; Thu, 11 Oct 2012 04:22:48 -0700 (PDT) X-AuditID: c1b4fb30-b7f7d6d0000042ea-5b-5076ac07b811 Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 17.CA.17130.70CA6705; Thu, 11 Oct 2012 13:22:47 +0200 (CEST) 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.279.1; Thu, 11 Oct 2012 13:22:47 +0200 Message-ID: <5076AC05.8070309@ericsson.com> Date: Thu, 11 Oct 2012 12:22:45 +0100 From: Magnus Westerlund User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: IETF AVTCore WG X-Enigmail-Version: 1.4.4 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPJMWRmVeSWpSXmKPExsUyM+JvrS77mrIAg7c7xSxe9qxkd2D0WLLk J1MAYxSXTUpqTmZZapG+XQJXxo1Hq5gKnrNXbF21lLWBcS1bFyMnh4SAicTV44+ZIGwxiQv3 1gPFuTiEBE4xSpy438YK4SxnlNh37iYLSBWvgLbEzqsnGUFsFgFViWlfOsAmsQlYSNz80Qhm iwoES0zavwWqXlDi5MwnYLaIgJLEjknbmEFsYYEQifZlO5ghNktKvJkMMZ9ZQE9iytUWRghb XqJ562ywGiGgvQ1NHawTGPlnIRk7C0nLLCQtCxiZVzEK5yZm5qSXm+ulFmUmFxfn5+kVp25i BAbawS2/DXYwbrovdohRmoNFSZxXT3W/v5BAemJJanZqakFqUXxRaU5q8SFGJg5OqQbG1vNd y/jV5v5h62KRPqgjNv2Sre8d90QBeV/BwM1O06pzTbfyBn/+fFuPa+OvSdmb1023Ey2eOTVE f4W3wGSv+TqWM4O9Sud3ugirWbBnZojsEl/1it1+DlNB+iF9r/2+ilOdi26/PCydOVNaSctt 2tI53dLiyjfrtm5bubXAP8z8EKd5T5wSS3FGoqEWc1FxIgAXUY4uAgIAAA== Subject: [AVTCORE] WG adopting Circuit Breaker (draft-perkins-avtcore-rtp-circuit-breakers-01) X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2012 11:22:49 -0000 WG, We had a call regarding adopting circuit breakers at the WG meeting which was very strong for adopting. We had a on the list call in April. They all point towards adopting this document as a WG item. Considering this I don't see any reason for doing another consensus call on the list. If someone thinks such a one is needed please contact the chairs. I will go forward requesting a milestone. To ensure that we have drafts submitted in a timely fashion we will go ahead allow WG versions to be submitted. Cheers 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 internet-drafts@ietf.org Thu Oct 11 15:54:42 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C48F711E80D7; Thu, 11 Oct 2012 15:54:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.504 X-Spam-Level: X-Spam-Status: No, score=-102.504 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ETakc8EZYam4; Thu, 11 Oct 2012 15:54:42 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 019F011E809C; Thu, 11 Oct 2012 15:54:42 -0700 (PDT) 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.34 Message-ID: <20121011225442.25830.42064.idtracker@ietfa.amsl.com> Date: Thu, 11 Oct 2012 15:54:42 -0700 Cc: avt@ietf.org Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-multi-media-rtp-session-00.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2012 22:54:43 -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 Core Maintenance Wo= rking Group of the IETF. Title : Multiple Media Types in an RTP Session Author(s) : Magnus Westerlund Colin Perkins Jonathan Lennox Filename : draft-ietf-avtcore-multi-media-rtp-session-00.txt Pages : 16 Date : 2012-10-08 Abstract: This document specifies how an RTP session can contain media streams with media from multiple media types such as audio, video, and text. This has been restricted by the RTP Specification, and thus this document updates RFC 3550 to enable this behavior for applications that satisfy the applicability for using multiple media types in a single RTP session. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avtcore-multi-media-rtp-session There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-avtcore-multi-media-rtp-session-00 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From internet-drafts@ietf.org Fri Oct 12 01:53:37 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BB2821F8442; Fri, 12 Oct 2012 01:53:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.504 X-Spam-Level: X-Spam-Status: No, score=-102.504 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KRsctimUKjPZ; Fri, 12 Oct 2012 01:53:36 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEA2721F842B; Fri, 12 Oct 2012 01:53:36 -0700 (PDT) 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.34 Message-ID: <20121012085336.20095.91430.idtracker@ietfa.amsl.com> Date: Fri, 12 Oct 2012 01:53:36 -0700 Cc: avt@ietf.org Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circuit-breakers-00.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Oct 2012 08:53:37 -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 Core Maintenance Wo= rking Group of the IETF. Title : RTP Congestion Control: Circuit Breakers for Unicast Ses= sions Author(s) : Colin Perkins Varun Singh Filename : draft-ietf-avtcore-rtp-circuit-breakers-00.txt Pages : 15 Date : 2012-10-12 Abstract: The Real-time Transport Protocol (RTP) is widely used in telephony, video conferencing, and telepresence applications. Such applications are often run on best-effort UDP/IP networks. If congestion control is not implemented in the applications, then network congestion will deteriorate the user's multimedia experience. This document does not propose a congestion control algorithm; rather, it defines a minimal set of "circuit-breakers". Circuit-breakers are conditions under which an RTP flow is expected to stop transmiting media to protect the network from excessive congestion. It is expected that all RTP applications running on best-effort networks will be able to run without triggering these circuit breakers in normal operation. Any future RTP congestion control specification is expected to operate within the envelope defined by these circuit breakers. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-circuit-breakers There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-avtcore-rtp-circuit-breakers-00 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From csp@csperkins.org Fri Oct 12 01:57:28 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F06D21F842B for ; Fri, 12 Oct 2012 01:57:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.599 X-Spam-Level: X-Spam-Status: No, score=-105.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z2dRoqTWb9Xq for ; Fri, 12 Oct 2012 01:57:27 -0700 (PDT) Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [93.93.131.52]) by ietfa.amsl.com (Postfix) with ESMTP id 6729221F8452 for ; Fri, 12 Oct 2012 01:57:27 -0700 (PDT) Received: from [130.209.247.112] (helo=mangole.dcs.gla.ac.uk) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.69) (envelope-from ) id 1TMb2f-0003FE-T9 for avt@ietf.org; Fri, 12 Oct 2012 09:56:26 +0100 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1283) From: Colin Perkins In-Reply-To: <20121012085336.20095.91430.idtracker@ietfa.amsl.com> Date: Fri, 12 Oct 2012 09:56:25 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <64165EFA-EC63-40A3-92E3-0EAC0446B34D@csperkins.org> References: <20121012085336.20095.91430.idtracker@ietfa.amsl.com> To: "avt@ietf.org WG" X-Mailer: Apple Mail (2.1283) X-BlackCat-Spam-Score: -10 X-Mythic-Debug: Threshold = On = Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circuit-breakers-00.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Oct 2012 08:57:28 -0000 Aside from the filename and date, this version is identical to = draft-perkins-avtcore-rtp-circuit-breakers-01. Colin On 12 Oct 2012, at 09:53, Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts = directories. > This draft is a work item of the Audio/Video Transport Core = Maintenance Working Group of the IETF. >=20 > Title : RTP Congestion Control: Circuit Breakers for = Unicast Sessions > Author(s) : Colin Perkins > Varun Singh > Filename : draft-ietf-avtcore-rtp-circuit-breakers-00.txt > Pages : 15 > Date : 2012-10-12 >=20 > Abstract: > The Real-time Transport Protocol (RTP) is widely used in telephony, > video conferencing, and telepresence applications. Such = applications > are often run on best-effort UDP/IP networks. If congestion control > is not implemented in the applications, then network congestion will > deteriorate the user's multimedia experience. This document does = not > propose a congestion control algorithm; rather, it defines a minimal > set of "circuit-breakers". Circuit-breakers are conditions under > which an RTP flow is expected to stop transmiting media to protect > the network from excessive congestion. It is expected that all RTP > applications running on best-effort networks will be able to run > without triggering these circuit breakers in normal operation. Any > future RTP congestion control specification is expected to operate > within the envelope defined by these circuit breakers. >=20 >=20 > The IETF datatracker status page for this draft is: > = https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-circuit-breakers >=20 > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-avtcore-rtp-circuit-breakers-00 >=20 >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > Audio/Video Transport Core Maintenance > avt@ietf.org > https://www.ietf.org/mailman/listinfo/avt --=20 Colin Perkins http://csperkins.org/ From magnus.westerlund@ericsson.com Fri Oct 12 02:54:07 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AE5621F8496 for ; Fri, 12 Oct 2012 02:54:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.223 X-Spam-Level: X-Spam-Status: No, score=-106.223 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id REF69Q2+XSWz for ; Fri, 12 Oct 2012 02:54:07 -0700 (PDT) Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id BE30621F847B for ; Fri, 12 Oct 2012 02:54:00 -0700 (PDT) X-AuditID: c1b4fb2d-b7fea6d000002ccb-a4-5077e8b86631 Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 40.33.11467.8B8E7705; Fri, 12 Oct 2012 11:54:00 +0200 (CEST) Received: from [127.0.0.1] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.279.1; Fri, 12 Oct 2012 11:53:59 +0200 Message-ID: <5077E8B6.4060107@ericsson.com> Date: Fri, 12 Oct 2012 10:53:58 +0100 From: Magnus Westerlund User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: avt@ietf.org References: <20121011225442.25830.42064.idtracker@ietfa.amsl.com> In-Reply-To: <20121011225442.25830.42064.idtracker@ietfa.amsl.com> X-Enigmail-Version: 1.4.4 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpjluLIzCtJLcpLzFFi42KZGfG3VnfHi/IAgzfv+S1e9qxkd2D0WLLk J1MAYxSXTUpqTmZZapG+XQJXxtOL59gKHgtU/Otdyd7A2MPbxcjJISFgIvG18S0jhC0mceHe erYuRi4OIYFTjBJXt/5lgXCWM0o0zvjFAlLFK6AtsfPTV2YQm0VAVaJ5/U9WEJtNwELi5o9G NhBbVCBYYtL+LVD1ghInZz4Bs0UEBCRWbP8LZgsLhEhc2PaCqYuRA2iBI5BtBRLmFHCSWLxn ChvEQZISbybfBCtnFtCTmHK1hRHClpdo3job7AQhoHMamjpYJzAKzkKybRaSlllIWhYwMq9i FM5NzMxJLzfUSy3KTC4uzs/TK07dxAgMy4NbfuvuYDx1TuQQozQHi5I4L1fSfn8hgfTEktTs 1NSC1KL4otKc1OJDjEwcnFINjCyee+0tLzEGK39x9DQpdrvWayfKc7DPwOrt7/9/LdTfzvmw v7A9qZOHad9LHt061qc7pxpHf+8Mbb23VW223s5qj5OHNnLPCC2YMenx01Ubpoa9fNiZmHl7 /dfAif+luDPvV/++vPOI0hcL5eYdb30+mq+/7aUxwXavALdwgaZD3qX9ZznOpCmxFGckGmox FxUnAgB1fA6ZGQIAAA== Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-multi-media-rtp-session-00.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Oct 2012 09:54:07 -0000 WG, This version has no changes compared to the draft-westerlund-avtcore-multi-media-rtp-session-00 An update is planned. Cheers Magnus On 2012-10-11 23:54, internet-drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Audio/Video Transport Core Maintenance Working Group of the IETF. > > Title : Multiple Media Types in an RTP Session > Author(s) : Magnus Westerlund > Colin Perkins > Jonathan Lennox > Filename : draft-ietf-avtcore-multi-media-rtp-session-00.txt > Pages : 16 > Date : 2012-10-08 > > Abstract: > This document specifies how an RTP session can contain media streams > with media from multiple media types such as audio, video, and text. > This has been restricted by the RTP Specification, and thus this > document updates RFC 3550 to enable this behavior for applications > that satisfy the applicability for using multiple media types in a > single RTP session. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-avtcore-multi-media-rtp-session > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-avtcore-multi-media-rtp-session-00 > > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > Audio/Video Transport Core Maintenance > avt@ietf.org > https://www.ietf.org/mailman/listinfo/avt > > -- 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 ron.even.tlv@gmail.com Sat Oct 13 10:52:04 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 099B921F850B for ; Sat, 13 Oct 2012 10:52:04 -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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KmxOmXKoMJyy for ; Sat, 13 Oct 2012 10:52:03 -0700 (PDT) Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 30BF421F8508 for ; Sat, 13 Oct 2012 10:52:03 -0700 (PDT) Received: by mail-wg0-f44.google.com with SMTP id dr13so2165182wgb.13 for ; Sat, 13 Oct 2012 10:52:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=vo3bbodL8KM+Ci/L2BCINd9ziib9M/gWObB4KhXlWu0=; b=zMsN14R3nTas/GPDLv1O22mGXC2XJ+gygykTtCcKNDVydtmkg0djuXi/aLQ76UNHYE +krX17M202VQFLv1SzLYAZfi7G6l+ChdU7ua8zjBpnMHEvRy4/JWrvpAGaFygwCltU7y lXiJndmygm30xLIDIlyoBnQGo0qUaJ/95sOfhZpa8HT1mwNqSEZG2pR2XmfB6dDchhCG 0mKBQiPzfaGdTT5EfiBtHvTxu2EJFlsbZ+aPOkfvSblZ5Y3C+TZ/0dOsLOG14AzFi1oe oNd8Mq1hAZIGDfTDlPtgV2AOShhfVg9tgbqFfxRLkVKY1Vx6qvbqxtjxcgd3c5w0eTD1 sGrg== Received: by 10.180.90.201 with SMTP id by9mr13344872wib.5.1350150722343; Sat, 13 Oct 2012 10:52:02 -0700 (PDT) Received: from RoniE (bzq-79-176-243-9.red.bezeqint.net. [79.176.243.9]) by mx.google.com with ESMTPS id b7sm4245855wiz.3.2012.10.13.10.52.00 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 13 Oct 2012 10:52:01 -0700 (PDT) From: "Roni Even" To: Date: Sat, 13 Oct 2012 19:49:54 +0200 Message-ID: <022f01cda96b$295518d0$7bff4a70$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0230_01CDA97B.ECDE8510" X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac2pawOOlbBRVEfaTIuXXspMvQVZKA== Content-Language: en-us Cc: Magnus Westerlund Subject: [AVTCORE] Request for agenda time - IETF85 X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Oct 2012 17:52:04 -0000 This is a multipart message in MIME format. ------=_NextPart_000_0230_01CDA97B.ECDE8510 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, The AVTcore WG will have two sessions in Atlanta. avtcore Session 1 (2:00:00) Monday, Afternoon Session I 1300-1500 Room Name: Grand Ballroom D --------------------------------------------- avtcore Session 2 (1:00:00) Thursday, Afternoon Session III 1730-1830 Room Name: Salon D --------------------------------------------- Please send agenda requests to the WG chairs Thanks Roni Even ------=_NextPart_000_0230_01CDA97B.ECDE8510 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

The AVTcore WG = will have two sessions in Atlanta.

 

   avtcore Session 1 = (2:00:00)

    = Monday, Afternoon Session I 1300-1500

    Room Name: Grand Ballroom = D

    = ---------------------------------------------

    avtcore Session 2 = (1:00:00)

    = Thursday, Afternoon Session III 1730-1830

    Room Name: Salon = D

    = ---------------------------------------------

 

Please = send agenda requests to the WG chairs

Thanks

Roni = Even

 

 

------=_NextPart_000_0230_01CDA97B.ECDE8510-- From abegen@cisco.com Sat Oct 13 19:33:00 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CA1E21F848B for ; Sat, 13 Oct 2012 19:33:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.316 X-Spam-Level: X-Spam-Status: No, score=-10.316 tagged_above=-999 required=5 tests=[AWL=0.283, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9GWv+ObSL0IW for ; Sat, 13 Oct 2012 19:32:59 -0700 (PDT) Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id B49BE21F8484 for ; Sat, 13 Oct 2012 19:32:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2211; q=dns/txt; s=iport; t=1350181979; x=1351391579; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=EuCRwAoZtReW6o6CX5zdBuyI3yJglivWYllQqNCnqtQ=; b=MZ7cDkq32oSWg1C4bUA9dkwLJHPDAj9u7vFjPHJAK9ZQ0B/aJ6K/vw+8 JnHDFUHSbTuh0ogh6MAZ8QyMourT049yIMQ80z7nKAJTvbWWP1SZbqWKA KXBtqakudoHMVNHHbmWNezxqjtZpA09T0V+0iihJSyFew3HYs7P36XraO k=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av8EAIQjelCtJXG+/2dsb2JhbABEgm69AoEIgiABAQEEEgEnPQ4GAQgRAwECCxRCGwEBBQMCBBMIARmHYgEKm0iBKJ8Xi1mFXWADlwGNMIFrgm2CFw X-IronPort-AV: E=Sophos;i="4.80,580,1344211200"; d="scan'208";a="131125431" Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-1.cisco.com with ESMTP; 14 Oct 2012 02:32:59 +0000 Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id q9E2Wxoc024453 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Sun, 14 Oct 2012 02:32:59 GMT Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-rcd-x04.cisco.com ([173.37.183.78]) with mapi id 14.02.0318.001; Sat, 13 Oct 2012 21:32:59 -0500 From: "Ali C. Begen (abegen)" To: "avt@ietf.org" Thread-Topic: New Version Notification for draft-rescorla-avtcore-6222bis-00.txt Thread-Index: AQHNqbPzDESOY6uX60uCchMrTLBMoZe47vUA Date: Sun, 14 Oct 2012 02:32:58 +0000 Message-ID: In-Reply-To: <20121014023052.25416.50131.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.4.120824 x-originating-ip: [10.21.118.60] x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19268.004 x-tm-as-result: No--38.937200-8.000000-31 x-tm-as-user-approved-sender: No x-tm-as-user-blocked-sender: No Content-Type: text/plain; charset="us-ascii" Content-ID: <79EF215D6AF2344EAC2E3FAF68B0D635@cisco.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [AVTCORE] FW: New Version Notification for draft-rescorla-avtcore-6222bis-00.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Oct 2012 02:33:00 -0000 We have submitted a draft to replace 6222. This document is a new version of 6222 and has the fixes proposed by Eric in the last meeting. Comments are welcome. -acbegen -----Original Message----- From: "internet-drafts@ietf.org" Date: Saturday, October 13, 2012 10:30 PM To: "Ali C. Begen" Cc: "Eric com>" Subject: New Version Notification for draft-rescorla-avtcore-6222bis-00.txt > >A new version of I-D, draft-rescorla-avtcore-6222bis-00.txt >has been successfully submitted by Ali Begen and posted to the >IETF repository. > >Filename: draft-rescorla-avtcore-6222bis >Revision: 00 >Title: Guidelines for Choosing RTP Control Protocol (RTCP) Canonical >Names (CNAMEs) >Creation date: 2012-10-14 >WG ID: Individual Submission >Number of pages: 10 >URL: =20 >http://www.ietf.org/internet-drafts/draft-rescorla-avtcore-6222bis-00.txt >Status: =20 >http://datatracker.ietf.org/doc/draft-rescorla-avtcore-6222bis >Htmlized: =20 >http://tools.ietf.org/html/draft-rescorla-avtcore-6222bis-00 > > >Abstract: > The RTP Control Protocol (RTCP) Canonical Name (CNAME) is a > persistent transport-level identifier for an RTP endpoint. While the > Synchronization Source (SSRC) identifier of an RTP endpoint may > change if a collision is detected or when the RTP application is > restarted, its RTCP CNAME is meant to stay unchanged, so that RTP > endpoints can be uniquely identified and associated with their RTP > media streams. > > For proper functionality, RTCP CNAMEs should be unique within the > participants of an RTP session. However, the existing guidelines for > choosing the RTCP CNAME provided in the RTP standard are insufficient > to achieve this uniqueness. RFC 6222 was published to update those > guidelines to allow endpoints to choose unique RTCP CNAMEs. > Unfortunately, later investigations showed that some parts of the new > algorithms were unnecessarily complicated and/or ineffective. This > document specifies a replacement for those parts. > > =20 > =20 > > >The IETF Secretariat > From magnus.westerlund@ericsson.com Mon Oct 15 07:24:00 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C83821F867E for ; Mon, 15 Oct 2012 07:24:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.224 X-Spam-Level: X-Spam-Status: No, score=-106.224 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zKJC-xfQ2WhC for ; Mon, 15 Oct 2012 07:24:00 -0700 (PDT) Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 4806E21F8672 for ; Mon, 15 Oct 2012 07:23:59 -0700 (PDT) X-AuditID: c1b4fb30-b7f7d6d0000042ea-28-507c1c7d08b1 Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 5B.8E.17130.D7C1C705; Mon, 15 Oct 2012 16:23:58 +0200 (CEST) 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.279.1; Mon, 15 Oct 2012 16:23:57 +0200 Message-ID: <507C1C7C.8080007@ericsson.com> Date: Mon, 15 Oct 2012 16:23:56 +0200 From: Magnus Westerlund User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: IETF AVTCore WG References: <20121015142026.6075.9386.idtracker@ietfa.amsl.com> In-Reply-To: <20121015142026.6075.9386.idtracker@ietfa.amsl.com> X-Enigmail-Version: 1.4.4 X-Forwarded-Message-Id: <20121015142026.6075.9386.idtracker@ietfa.amsl.com> Content-Type: multipart/mixed; boundary="------------090508030407050903050804" X-Brightmail-Tracker: H4sIAAAAAAAAA1WSfUhTURiHObt323UoXj/S1w9IJkJpLsVKoUgNpEhoWhASZA696nCZbPYB ZajENKdgbqa7LBQybZJINs0cpi4z0zQttAaVmK3M8jPCxMy2exbYf8+55/0977nvORThOcv3 p+S5+YwyV6YQC0SkPmWjIPxq4JWkCPUSFfO13CiMQ0caGtZ4SeiU6EAGo5BfYJS7D6aJsl9Z B4i88ZhLEx0aVIgGI8uQCwX0Hng63C/E7ANjH1oFDvakhxCYLXQZEtm5CUHNrTrCseFGh8Ht lVaeg0k6BMwvLVxYQMeA9VcRF95Gn4CqHhOJ6z3guf4Tx960GDqrOjiPFy2F3t8jBG4WC/0L zZzHhY6D2eUyEh/ID75rrU5OhJXuP5yfoJPAaGvk4WwYFBaX8iuRB7ulHbulDLMEdBPXEObt 8HDeQGBWwOJPNf//7yI7qxGM6FaELNc7DaxdVpLlhtGF4N7oMh8v7iOYu6khWecoF+qXeXjD jKBqtVqAF9UIah9NcmKS3iCgZu0LD0dCoWnoDcckvRM2B9ROrwlBXYkN4aIdUGscszNlZ3do sQSzztu6Y2h0HtANhnXPBJgvg+FjJcIeK4IV25xT2oZAVzXD/auADoK5ZaPQIfWmA2DY5s5y t3IUSjvL+VjkDQsT08S/Ztdta0I84lhY/KzhOaKOF9BvSMclYthUa4X1KKoZeZ2VyRVZF6Ml jFKerlKdy5WomDZkf619pvWITtQ25WNBARQp9nWThPRIPeksWT6TwzB5jPKM8ryCUVkQj3Lx L0TdN/Zmvk72pDQlhSlMs/Zu8dRwkuB4r6GvvTp+KebBzKHTg35p5vepo9LM1cfRNfumK55o fdd2UaLD1nbXtydb8obWE9ozpKz/O+GmpLTIB0XtX/hRMJffmzieeqwnoaFiMscoDw/eNMeH h00H6V3nTd8iW1KSfYdemDRR+kBWTKqyZZGhhFIl+wt5YwOeewMAAA== Subject: [AVTCORE] Fwd: I-D Action: draft-westerlund-avtcore-rtp-topologies-update-01.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Oct 2012 14:24:00 -0000 --------------090508030407050903050804 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit WG, As individual We have submitted two versions of this draft. The 00 is an XML2RFC generated version from the text present in RFC 5117. The 01 version is a first update. This focus on the RTP topologies present in the draft. The text is kind of rough, so I would suggest that you focus on the questions: - Are this the topologies the document should describe? Missing, redundant etc. - What do you think a topology discussion should contain. There will be variations over the different topologies in this document. Cheers Magnus Westerlund --------------090508030407050903050804 Content-Type: message/rfc822; name="I-D Action: draft-westerlund-avtcore-rtp-topologies-update-01_txt.eml" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename*0="I-D Action: draft-westerlund-avtcore-rtp-topologies-update-0"; filename*1="1_txt.eml" X-Mozilla-Keys: Received: from esessmw0184.eemea.ericsson.se (153.88.115.81) by ESESSHC008.ericsson.se (153.88.183.42) with Microsoft SMTP Server (TLS) id 14.2.318.1; Mon, 15 Oct 2012 16:21:00 +0200 Received: from sesbmg10.ericsson.net (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.83) with Microsoft SMTP Server id 8.3.279.1; Mon, 15 Oct 2012 16:20:58 +0200 X-AuditID: c1b4fb3c-b7f716d0000068ad-ae-507c1bc9b741 Received: from mail.ietf.org (mail.ietf.org [64.170.98.30]) by sesbmg10.ericsson.net (Symantec Mail Security) with SMTP id 5A.6E.26797.9CB1C705; Mon, 15 Oct 2012 16:20:58 +0200 (CEST) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99DD811E808A; Mon, 15 Oct 2012 07:20:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1350310829; bh=aDv5JeqX1g+GHDGDTUorSOsZ15aV2fmTbnZQTYWNgUM=; h=MIME-Version:From:To:Subject:Message-ID:Date:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=wxfxCj8DVDf91LPmOSIwkwAsRwAWz71ZIQ5rPxR46lRfG3j8ucz4hvKYWCDrnZ+Y8 PK4WOTAEENVhwOu/ZtKfNBpcFltFuprDNKU4SEeFZ3p2AQnAud5V4DcJp3RN7oLiq+ EXhibxh1jpA6BA/uNU41FCwl1IYWMJl8WWzZTwRY= X-Original-To: i-d-announce@ietfa.amsl.com Delivered-To: i-d-announce@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 926F511E80D1 for ; Mon, 15 Oct 2012 07:20:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.535 X-Spam-Level: X-Spam-Status: No, score=-102.535 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E6VgkQZNSViC for ; Mon, 15 Oct 2012 07:20:27 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2FAD1F0429 for ; Mon, 15 Oct 2012 07:20:26 -0700 (PDT) From: To: Subject: I-D Action: draft-westerlund-avtcore-rtp-topologies-update-01.txt X-Test-IDTracker: no X-IETF-IDTracker: 4.34 Message-ID: <20121015142026.6075.9386.idtracker@ietfa.amsl.com> Date: Mon, 15 Oct 2012 07:20:26 -0700 X-BeenThere: i-d-announce@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: List-Id: Internet Draft Announcements only List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: Errors-To: i-d-announce-bounces@ietf.org X-Brightmail-Tracker: H4sIAAAAAAAAA1WSe0hTYRjG/c6Z23HtrK9p+jrN6ERgkTdQOYGZJWT0l/RHkBG16WlbbVN2 ZmgZ2LqvJEnYzOaNLM2yLCQV6WZ3CTJFQipJMzM1u9Bllpd2dmbWf7+P53mf533ho0jVDama 4vKsnMWsMTJSuSSlXhsR1RFWkB7bMqVkba+bZOyBV28J9oCNZy+9S2W7rvYR7JBjUsq+rHgl Y0tdEzLWeXg162677J8i3/Dre480HWXIk7I4o2EPZ4lJ3iHXX3E4Uc61eXmnPzSThaguwI4C KMDxMF71hRA5GDr7rkoFVuFWBA8cnB3JPexE0ODoJoWHBE+R4Jx475tYAbUdL7wswcth5uER f3G6CUHtowTREwmlFzuRHVEeng8N7Utny867LshEVsLzYbcvch+4BoqRWPwSweNzt0nxcR3B rYEv3gkaL4AnZwYlAktxBFwacSCBg3AolD0t93oC8UY41nLSX0wNgvGefnK2+fi7CV/OGvg0 dIIQlpPgZXDflSlaGJg5UuJbLhTsRYNexhhDRU0rId7IgMPR661V4HVQPt5HCHsq8EEEtrIK fyFTgdfCod+bRc9y6H1W4fMnQ72zSVaMlpX9c43AJF4JVW1fpSIvhuaPLrIKkfVoIc/xWpMu LjaasxgyeT7bHG3mrNeR57Pcbfqd1IL6B+PaUShFMAvpN+qCdJVSm52Vr9fw+u2WXCPHt6Mw SsKE0KbR+HQV1mms3G6Oy+Ess2o4RTFAm4TJBRZOx+XtNBitczJBBbQjoBRMEF0ieGg+R2Pi DTpR70BL1CG0URCwIOhzzX9nZ79zF1qkDqSRn5+fSuHpNRms/+sjKIRCTCBdJ6QoDGbr3/QR TzHhKba37ROKrZo5SV2INKNFqTU79pf+TLxweJttOGp6b2N5ancGE+nOrewYLU2rnlw6wwTH F5lncqOG2NQk7TdJwXhjz5j91GL39tba7mZn449NR+uStzasSpjecnNN6FMl82zXrrFTlpLE mGsDlSkZwfcOtjVv1qVFTpytnrStb1DmDyT/1H8euhOuVX8qZiS8XhO3grTwmj9LYnf5yQMA AA== Return-Path: i-d-announce-bounces@ietf.org X-MS-Exchange-Organization-AVStamp-Mailbox: MSFTFF;1;0;0 0 0 X-MS-Exchange-Organization-AuthSource: esessmw0184.eemea.ericsson.se X-MS-Exchange-Organization-AuthAs: Anonymous MIME-Version: 1.0 A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : RTP Topologies Author(s) : Magnus Westerlund Stephan Wenger Filename : draft-westerlund-avtcore-rtp-topologies-update-01.txt Pages : 33 Date : 2012-10-15 Abstract: This document discusses multi-endpoint topologies used in Real-time Transport Protocol (RTP)-based environments. In particular, centralized topologies commonly employed in the video conferencing industry are mapped to the RTP terminology. This document is updated with additional topologies and are intended to replace RFC 5117. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-westerlund-avtcore-rtp-topologies-update There's also a htmlized version available at: http://tools.ietf.org/html/draft-westerlund-avtcore-rtp-topologies-update-01 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-westerlund-avtcore-rtp-topologies-update-01 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt --------------090508030407050903050804-- From csp@csperkins.org Mon Oct 15 09:05:48 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 638CE21F8723 for ; Mon, 15 Oct 2012 09:05:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.742 X-Spam-Level: X-Spam-Status: No, score=-105.742 tagged_above=-999 required=5 tests=[AWL=0.857, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GakkVYffyUg3 for ; Mon, 15 Oct 2012 09:05:47 -0700 (PDT) Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [93.93.130.6]) by ietfa.amsl.com (Postfix) with ESMTP id BF78C21F8714 for ; Mon, 15 Oct 2012 09:05:47 -0700 (PDT) Received: from [130.209.247.112] (helo=mangole.dcs.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.69) (envelope-from ) id 1TNnAn-0003WQ-Sw; Mon, 15 Oct 2012 17:05:46 +0100 Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Colin Perkins In-Reply-To: <201203062316.q26NGXvZ018119@mtv-core-4.cisco.com> Date: Mon, 15 Oct 2012 17:05:45 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <65CCF0E0-7074-4138-90E6-1DEFCEF29420@csperkins.org> References: <20120305201759.24406.49431.idtracker@ietfa.amsl.com> <766FE318-7DE3-4481-B3C4-C45F2A94C881@csperkins.org> <4F55C25A.9010407@alvestrand.no> <201203062316.q26NGXvZ018119@mtv-core-4.cisco.com> To: James M. Polk X-Mailer: Apple Mail (2.1283) X-BlackCat-Spam-Score: -11 X-Mythic-Debug: Threshold = On = Cc: "avt@ietf.org WG" Subject: Re: [AVTCORE] rtp-circuit-breakers-00 when not using BE? X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Oct 2012 16:05:48 -0000 James, On 6 Mar 2012, at 23:16, James M. Polk wrote: > Colin >=20 > I'm curious about this RTP extension for the cases in which DiffServ = is actually used, but there's more load than capacity to serve the DS = node(s)? >=20 > What happens then? I'm not familiar with DiffServ deployments, but my assumption would be = that over capacity traffic is delivered in a best effort manner, and is = potentially subject to packet loss. That loss could potentially trigger = the circuit breaker, if implemented. > Also, in the fairly rare case that reservations are used, many times = RTCP feedback will be used to invoke or cause a source to reduce = resolution or to otherwise change audio codecs, which can be planned for = *without* the need for this circuit breaker mode of just cease = transmitting. Sure. > Would you be relying on the application at each end to know the = difference as to whether that endpoint is within a BE network, a DS = network that's congested or a network that uses (say) reservations, but = still experiences problems? The application can potentially do something smarter if it knows about = the underlying network, but I think the circuit breaker is less subtle = than that. I expect the circuit breaker to only fire as a last resort, = and after the application would have had chance to perform congestion = control or reestablish a reservation. Colin > James >=20 > At 01:52 AM 3/6/2012, Harald Alvestrand wrote: >> On 03/06/2012 12:32 AM, Colin Perkins wrote: >>>=20 >>> Here's our initial attempt at a "circuit breakers" draft for RTCWeb. = Comments welcome - this is very much a straw-man for discussion, rather = than a final solution. >>>=20 >>> Colin ... --=20 Colin Perkins http://csperkins.org/ From albrecht.schwarz@alcatel-lucent.com Tue Oct 16 08:02:18 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7046E21F8980 for ; Tue, 16 Oct 2012 08:02:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.849 X-Spam-Level: X-Spam-Status: No, score=-9.849 tagged_above=-999 required=5 tests=[AWL=0.400, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9y3ljJUsJsCb for ; Tue, 16 Oct 2012 08:02:16 -0700 (PDT) Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id 7E56021F898A for ; Tue, 16 Oct 2012 08:02:16 -0700 (PDT) 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 q9GF1i5v025892 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 16 Oct 2012 17:02:12 +0200 Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.50]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Tue, 16 Oct 2012 17:02:00 +0200 From: "Schwarz, Albrecht (Albrecht)" To: Magnus Westerlund , IETF AVTCore WG Date: Tue, 16 Oct 2012 17:01:58 +0200 Thread-Topic: [AVTCORE] Fwd: I-D Action: draft-westerlund-avtcore-rtp-topologies-update-01.txt Thread-Index: Ac2q4MerKFRlpa+7RcaE1mZY8DBNtgAyY8EQ Message-ID: <5F7BCCF5541B7444830A2288ABBEBC96218D0E7C54@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> References: <20121015142026.6075.9386.idtracker@ietfa.amsl.com> <507C1C7C.8080007@ericsson.com> In-Reply-To: <507C1C7C.8080007@ericsson.com> Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE, 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: Re: [AVTCORE] Fwd: I-D Action: draft-westerlund-avtcore-rtp-topologies-update-01.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Oct 2012 15:02:18 -0000 Dear All! RFC 5117 was already a good progress wrt RFC 1889/3550, but is still at som= e areas too high-level in my opinion. Thus, I support any update activity of RFC 5117. BTW: this was also recently discussed in ITU-T SG16 Q3; there's a work item= on "RTP topology dependent RTCP handling by H.248 Media Gateways with IP T= erminations", called H.248.RTPTOPO. The latest draft may be downloaded via=20 http://wftp3.itu.int/av-arch/avc-site/2009-2012/1209_Bri/TD-21.zip=20 Concerning > - What do you think a topology discussion should contain. There will be v= ariations over the different topologies in this document. 1) Terminology What's still missing is an explicit definition for "RTP topology". Should b= e added in section 2. The definition should answer the question "what constitutes exactly an RTP = topology"? There are different interpretations, such as "number and type of media inte= rfaces" towards a characterization of an RTP topology based on the six prop= erties of section 4.1. But even such properties should be made more precise in my opinion. 2) RTP topology dependent RTP media packet handling Comprehensive summary=20 - which RTP header elements may or may not be modified under a particular R= TP topology - whether RTP payload may or may not be modified under a particular RTP top= ology 3) RTP topology dependent RTCP packet handling Comprehensive summary=20 - which RTCP elements may or may not be modified under a particular RTP top= ology The existing text provides partial information, sometimes too high level. It's also fairly difficult or even impossible to consider all possible RTCP= information types under a particular topology, leading to (4): 4) Introduction of an RTCP service concept Well known problem: a RTP transport translator shall be also used as measur= ement and reporting point of RTCP XR type of performance metrics. =3D> Cont= radiction: different handling of RTCP basic and extension reports, SSRC usa= ge, ...:-( Possible solution: define different levels of RTCP services, such as a) basic RTCP service (given by RFC 3550 core protocol) b) RTP profile dependent RTCP service (given by RTP profile specification) = and c) supplementary RTCP service (such as RFC 3611, 5760, 6051, ...) Above problem could be then solved by coupling (a) and (b) type of RTCP ser= vices with the RTP topology, and consider (c) as "overlay" (and topology in= dependent). See also Draft H.248.RTPTOPO. 5) Missing RTP topologies There are two further topologies, which we've observed in middle boxes, SBC= s, H.323 gateways, H.248 IP-IP gateways, but missing in RFC 5117: a) Back-to-Back RTP Endsystem (B2BRE): e.g. a topology within the end-to-en= d path of the PtP topology. Please note that clause 3.1 does not describe t= he B2BRE topology. E.g., RTP end-to-end path between A - MB - B (with MB as middle box) A =3D RTP topology "RTP endsystem" (RFC 3550 notation; now perhaps "endpo= int") B =3D ditto MB =3D RTP topology "B2BRE" The MP separates the e2e RTP network in two domains, e.g. a separation of t= he SSRC space. b) Topology "transparent forwarding" e.g. required for SRTP-to-SRTP forwarding see definition in H.248.RTPTOPO Just some initial thoughts, Albrecht -----Original Message----- From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Magnu= s Westerlund Sent: Montag, 15. Oktober 2012 16:24 To: IETF AVTCore WG Subject: [AVTCORE] Fwd: I-D Action: draft-westerlund-avtcore-rtp-topologies= -update-01.txt WG, As individual We have submitted two versions of this draft. The 00 is an XML2RFC generate= d version from the text present in RFC 5117. The 01 version is a first upda= te. This focus on the RTP topologies present in the draft. The text is kind= of rough, so I would suggest that you focus on the questions: - Are this the topologies the document should describe? Missing, redundant = etc. - What do you think a topology discussion should contain. There will be var= iations over the different topologies in this document. Cheers Magnus Westerlund From wwwrun@rfc-editor.org Tue Oct 16 15:56:34 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E74911E80F9 for ; Tue, 16 Oct 2012 15:56:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.31 X-Spam-Level: X-Spam-Status: No, score=-102.31 tagged_above=-999 required=5 tests=[AWL=0.290, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UEtNr131Yq1f for ; Tue, 16 Oct 2012 15:56:30 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id B54731F0CB4 for ; Tue, 16 Oct 2012 15:56:22 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id EC75072F402; Tue, 16 Oct 2012 15:51:07 -0700 (PDT) To: csp@csperkins.org, magnus.westerlund@ericsson.com, gonzalo.camarillo@ericsson.com, rjsparks@nostrum.com, keith.drage@alcatel-lucent.com, even.roni@huawei.com From: RFC Errata System Message-Id: <20121016225107.EC75072F402@rfc-editor.org> Date: Tue, 16 Oct 2012 15:51:07 -0700 (PDT) Cc: martin@martin.st, avt@ietf.org, rfc-editor@rfc-editor.org Subject: [AVTCORE] [Technical Errata Reported] RFC5761 (3380) X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Oct 2012 22:56:35 -0000 The following errata report has been submitted for RFC5761, "Multiplexing RTP Data and Control Packets on a Single Port". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5761&eid=3380 -------------------------------------- Type: Technical Reported by: Martin Storsjö Section: 4 Original Text ------------- o RTP payload type 80 conflicts with Receiver Summary Information (RSI) packets defined in "RTCP Extensions for Single-Source Multicast Sessions with Unicast Feedback" [6]. Corrected Text -------------- o RTP payload type 81 conflicts with Receiver Summary Information (RSI) packets defined in "RTCP Extensions for Single-Source Multicast Sessions with Unicast Feedback" [6]. Notes ----- Reference [6], RFC 5760 (IANA likewise), specifies that RTCP RSI has the RTCP packet type number 209, which means that it would conflict with RTP payload type 81, not 80 as stated. Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5761 (draft-ietf-avt-rtp-and-rtcp-mux-07) -------------------------------------- Title : Multiplexing RTP Data and Control Packets on a Single Port Publication Date : April 2010 Author(s) : C. Perkins, M. Westerlund Category : PROPOSED STANDARD Source : Audio/Video Transport Area : Real-time Applications and Infrastructure Stream : IETF Verifying Party : IESG From kevin.gross@avanw.com Fri Oct 19 13:04:07 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FC9B21F842B for ; Fri, 19 Oct 2012 13:04:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.647 X-Spam-Level: *** X-Spam-Status: No, score=3.647 tagged_above=-999 required=5 tests=[AWL=-2.686, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, FRT_STOCK1=3.988, FRT_STOCK2=3.988, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yNXzSkS6iQ6V for ; Fri, 19 Oct 2012 13:04:05 -0700 (PDT) Received: from oproxy7-pub.bluehost.com (oproxy7-pub.bluehost.com [67.222.55.9]) by ietfa.amsl.com (Postfix) with SMTP id F3A8821F879D for ; Fri, 19 Oct 2012 13:03:05 -0700 (PDT) Received: (qmail 30157 invoked by uid 0); 19 Oct 2012 20:02:37 -0000 Received: from unknown (HELO host291.hostmonster.com) (74.220.215.91) by oproxy7.bluehost.com with SMTP; 19 Oct 2012 20:02:37 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=avanw.com; s=default; h=Content-Type:To:From:Subject:Message-ID:Date:References:In-Reply-To:MIME-Version; bh=36TPuz/ET/JFaWQ2mI2IVNWeFRoL7QLrJLCOP2UObdY=; b=FKFEbrM/qDuB7odklZgmxG9fo4MAsLlGlPzp14CjivsR49LfEcWOOjYV+tF0FtAMJEVqD2nqcGOGtM4aI30fvNF00ytRCLywZVzDjgg87KERfdj29DhOvRxPDxs99U/i; Received: from [74.125.82.172] (port=49675 helo=mail-we0-f172.google.com) by host291.hostmonster.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1TPImD-0000rT-EH for avt@ietf.org; Fri, 19 Oct 2012 14:02:37 -0600 Received: by mail-we0-f172.google.com with SMTP id u46so505486wey.31 for ; Fri, 19 Oct 2012 13:02:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.180.101.230 with SMTP id fj6mr5369704wib.16.1350676956149; Fri, 19 Oct 2012 13:02:36 -0700 (PDT) Received: by 10.223.152.201 with HTTP; Fri, 19 Oct 2012 13:02:36 -0700 (PDT) In-Reply-To: References: <20121011071900.24901.9484.idtracker@ietfa.amsl.com> Date: Fri, 19 Oct 2012 14:02:36 -0600 Message-ID: From: Kevin Gross To: "avt@ietf.org" Content-Type: multipart/alternative; boundary=f46d0442879e2d77aa04cc6efc0a X-Identified-User: {1416:host291.hostmonster.com:avanwcom:avanw.com} {sentby:smtp auth 74.125.82.172 authed with kevin.gross@avanw.com} Subject: Re: [AVTCORE] FW: I-D Action: draft-ietf-avtcore-idms-07.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Oct 2012 20:04:07 -0000 --f46d0442879e2d77aa04cc6efc0a Content-Type: text/plain; charset=ISO-8859-1 Ray has asked me to add to his comments and assure AVTCORE members that in preparing this revision the authors also considered the following issues discussed at IETF 84: Which packet to report on - We decided to allow flexibility in which RTP packet is used to report network delay. Flexibility allows implementations to optimize reporting to get the most useful information to the MSAS quickly. We do not believe interoperability or performance is compromised by this flexibility. draft-wu-xrblock-rtcp-xr-one-way-delay - We considered whether this proposal could be used instead of the application-specific reporting mechanism proposed in our draft. We found this unsuitable for the following reasons. 1. The IDMS proposal directly reports one-way delay of the RTP packets of the stream under control by IDMS. The one-way-delay proposal measures one-way delay using RTCP packets. RTP delay is what we care about for proper IDMS operation. RTCP packets are likely to experience different (shorter) delay due to their different (smaller) size. 2. The one-way-delay proposal does not include a Media Stream Correlation Identifier. The MSAS requires this information to do its job. If it is not included in the XR, it will need to be signaled through another means significantly altering and complicating the system. 3. The one-way-delay proposal does not include a presentation timestamp making the precise synchronization required by some IDMS applications difficult or impossible. Kevin Gross +1-303-447-0517 Media Network Consultant AVA Networks - www.AVAnw.com , www.X192.org On Thu, Oct 11, 2012 at 1:24 AM, Brandenburg, R. (Ray) van < ray.vanbrandenburg@tno.nl> wrote: > Hi all, > > I've just uploaded a new version of the IDMS draft. This new version > includes the comments received during the WGLC which were not yet included > in the -06 version and a solution to the packet reporting issue that we > discussed in Vancouver. > > I believe that with this version all WGLC comments have been addressed. > > Best regards, > > Ray van Brandenburg > > > > -----Original Message----- > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of > internet-drafts@ietf.org > Sent: donderdag 11 oktober 2012 9:19 > To: i-d-announce@ietf.org > Cc: avt@ietf.org > Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-idms-07.txt > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Audio/Video Transport Core Maintenance > Working Group of the IETF. > > Title : Inter-destination Media Synchronization using > the RTP Control Protocol (RTCP) > Author(s) : Ray van Brandenburg > Hans Stokking > Oskar van Deventer > Fernando Boronat > Mario Montagud > Kevin Gross > Filename : draft-ietf-avtcore-idms-07.txt > Pages : 24 > Date : 2012-10-11 > > Abstract: > This document gives information on an RTP Control Protocol (RTCP) > Packet Type and RTCP Extended Report (XR) Block Type including > associated Session Description Protocol (SDP) parameters for Inter- > Destination Media Synchronization (IDMS). This document mandates the > use of the RTCP XR Block Type 12, which is used to collect media > playout information from participants in a group playing out > (watching, listening, etc.) a specific RTP media stream. This RTCP > XR Block Type is specified and registered with IANA by ETSI. The > RTCP packet type specified by this document is used to distribute a > common target playout point to which all the distributed receivers, > sharing a media experience, can synchronize. > > Typical use cases in which IDMS is usefull are social TV, shared > service control (i.e. applications where two or more geographically > separated users are watching a media stream together), distance > learning, networked video walls, networked loudspeakers, etc. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-avtcore-idms > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-avtcore-idms-07 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-idms-07 > > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > Audio/Video Transport Core Maintenance > avt@ietf.org > https://www.ietf.org/mailman/listinfo/avt > This e-mail and its contents are subject to the DISCLAIMER at > http://www.tno.nl/emaildisclaimer > > _______________________________________________ > Audio/Video Transport Core Maintenance > avt@ietf.org > https://www.ietf.org/mailman/listinfo/avt > --f46d0442879e2d77aa04cc6efc0a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Ray has asked me to add to his comments and assure AVTCORE members tha= t in preparing this revision the authors also considered the following issu= es discussed at IETF 84:

Which packet to report on= - We decided to allow flexibility in which RTP packet is used to report ne= twork delay. Flexibility allows implementations to optimize=A0reporting=A0t= o get the most useful information to the MSAS quickly. We do not=A0believe= =A0interoperability or performance is compromised by this flexibility.

draft-wu-xrblock-rtcp-xr-one-way-delay - We considered wheth= er this proposal could be used=A0instead=A0of the=A0application-specific re= porting mechanism proposed in our draft. We found this unsuitable for the f= ollowing reasons.
  1. The IDMS proposal directly reports one-way delay of the RTP packets= of the stream under control by IDMS. The one-way-delay proposal measures o= ne-way delay using RTCP packets. RTP delay is what we care about for proper= IDMS operation. RTCP packets are likely to experience different (shorter) = delay due to their different (smaller) size.
  2. The one-way-delay proposal does not include a Media Stream Correlation = Identifier. The MSAS requires this information to do its job. If it is not = included in the XR, it will need to be signaled through another means=A0sig= nificantly=A0altering and complicating the system.
  3. The one-way-delay proposal=A0does not include a=A0presentation timestam= p making the precise synchronization required by some IDMS applications dif= ficult or impossible.

Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks -= =A0www.AVAnw.com,= =A0www.X192.org
=



On Thu, Oct 11, 2012 at 1:24 AM, Branden= burg, R. (Ray) van <ray.vanbrandenburg@tno.nl> wrote= :
Hi all,

I've just uploaded a new version of the IDMS draft. This new version in= cludes the comments received during the WGLC which were not yet included in= the -06 version and a solution to the packet reporting issue that we discu= ssed in Vancouver.

I believe that with this version all WGLC comments have been addressed.

Best regards,

Ray van Brandenburg



-----Original Message-----
From: avt-bounces@ietf.org [mai= lto:avt-bounces@ietf.org] On Be= half Of internet-drafts@ietf.or= g
Sent: donderdag 11 oktober 2012 9:19
To: i-d-announce@ietf.org
Cc: avt@ietf.org
Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-idms-07.txt


A New Internet-Draft is available from the on-line Internet-Drafts director= ies.
=A0This draft is a work item of the Audio/Video Transport Core Maintenance = Working Group of the IETF.

=A0 =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : Inter-destination Media Synchro= nization using the RTP Control Protocol (RTCP)
=A0 =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : Ray van Brandenburg
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Hans Stokking
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Oskar van Deventer
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Fernando Boronat
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Mario Montagud
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Kevin Gross
=A0 =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-ietf-avtcore-idms-07.txt =A0 =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 24
=A0 =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2012-10-11

Abstract:
=A0 =A0This document gives information on an RTP Control Protocol (RTCP) =A0 =A0Packet Type and RTCP Extended Report (XR) Block Type including
=A0 =A0associated Session Description Protocol (SDP) parameters for Inter-<= br> =A0 =A0Destination Media Synchronization (IDMS). =A0This document mandates = the
=A0 =A0use of the RTCP XR Block Type 12, which is used to collect media
=A0 =A0playout information from participants in a group playing out
=A0 =A0(watching, listening, etc.) a specific RTP media stream. =A0This RTC= P
=A0 =A0XR Block Type is specified and registered with IANA by ETSI. =A0The<= br> =A0 =A0RTCP packet type specified by this document is used to distribute a<= br> =A0 =A0common target playout point to which all the distributed receivers,<= br> =A0 =A0sharing a media experience, can synchronize.

=A0 =A0Typical use cases in which IDMS is usefull are social TV, shared
=A0 =A0service control (i.e. applications where two or more geographically<= br> =A0 =A0separated users are watching a media stream together), distance
=A0 =A0learning, networked video walls, networked loudspeakers, etc.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-avtcore-idms
There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-avtcore-idms-07

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-idms= -07


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp= .ietf.org/internet-drafts/

_______________________________________________
Audio/Video Transport Core Maintenance
avt@ietf.org
htt= ps://www.ietf.org/mailman/listinfo/avt
This e-mail and its contents are subject to the DISCLAIMER at <= a href=3D"http://www.tno.nl/emaildisclaimer" target=3D"_blank">http://www.t= no.nl/emaildisclaimer

_______________________________________________
Audio/Video Transport Core Maintenance
avt@ietf.org
htt= ps://www.ietf.org/mailman/listinfo/avt

--f46d0442879e2d77aa04cc6efc0a-- From internet-drafts@ietf.org Fri Oct 19 17:28:03 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA12721F8861; Fri, 19 Oct 2012 17:28:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.525 X-Spam-Level: X-Spam-Status: No, score=-102.525 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EgPBYki9Ff1h; Fri, 19 Oct 2012 17:28:03 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 354F821F884D; Fri, 19 Oct 2012 17:28:03 -0700 (PDT) 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.34 Message-ID: <20121020002803.30962.90644.idtracker@ietfa.amsl.com> Date: Fri, 19 Oct 2012 17:28:03 -0700 Cc: avt@ietf.org Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-leap-second-01.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Oct 2012 00:28:03 -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 Core Maintenance Wo= rking Group of the IETF. Title : RTP and Leap Seconds Author(s) : Kevin Gross Ray van Brandenburg Filename : draft-ietf-avtcore-leap-second-01.txt Pages : 7 Date : 2012-10-19 Abstract: This document discusses issues that arise when RTP sessions span Universal Coordinate Time (UTC) leap seconds. It updates RFC 3550 to describe how RTP senders and receivers should behave in the presence of leap seconds. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avtcore-leap-second There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-avtcore-leap-second-01 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-leap-second-01 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From kevin.gross@avanw.com Fri Oct 19 17:39:21 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6725C21F8778 for ; Fri, 19 Oct 2012 17:39:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.642 X-Spam-Level: X-Spam-Status: No, score=-1.642 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dAPXIypV7-Lo for ; Fri, 19 Oct 2012 17:39:17 -0700 (PDT) Received: from oproxy7-pub.bluehost.com (oproxy7-pub.bluehost.com [67.222.55.9]) by ietfa.amsl.com (Postfix) with SMTP id B284B21F8748 for ; Fri, 19 Oct 2012 17:39:17 -0700 (PDT) Received: (qmail 18405 invoked by uid 0); 20 Oct 2012 00:38:55 -0000 Received: from unknown (HELO host291.hostmonster.com) (74.220.215.91) by oproxy7.bluehost.com with SMTP; 20 Oct 2012 00:38:55 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=avanw.com; s=default; h=Content-Type:To:From:Subject:Message-ID:Date:References:In-Reply-To:MIME-Version; bh=7LsEVzyJ/5NovDJveOdBEkYGWZDVkbOKXOVNH0CWtIg=; b=er98OaBk5wkaBPtKKLryAy/mBuwVoXLVQjB/1YUk3w/YFEI2GWaAys7ftsCrnDGqOECOTlIVFS27+iFpkvaUshDrk9LDqPFb/aEZOzg8G2DabXAp09I7CFa1w7vKNLTJ; Received: from [209.85.212.178] (port=53535 helo=mail-wi0-f178.google.com) by host291.hostmonster.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1TPN5b-0001zP-8g for avt@ietf.org; Fri, 19 Oct 2012 18:38:55 -0600 Received: by mail-wi0-f178.google.com with SMTP id hr7so675634wib.13 for ; Fri, 19 Oct 2012 17:38:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.180.82.35 with SMTP id f3mr6486853wiy.6.1350693533947; Fri, 19 Oct 2012 17:38:53 -0700 (PDT) Received: by 10.223.152.201 with HTTP; Fri, 19 Oct 2012 17:38:53 -0700 (PDT) In-Reply-To: <20121020002803.30962.90644.idtracker@ietfa.amsl.com> References: <20121020002803.30962.90644.idtracker@ietfa.amsl.com> Date: Fri, 19 Oct 2012 18:38:53 -0600 Message-ID: From: Kevin Gross To: avt@ietf.org Content-Type: multipart/alternative; boundary=f46d044304824a969704cc72d807 X-Identified-User: {1416:host291.hostmonster.com:avanwcom:avanw.com} {sentby:smtp auth 209.85.212.178 authed with kevin.gross@avanw.com} Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-leap-second-01.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Oct 2012 00:39:21 -0000 --f46d044304824a969704cc72d807 Content-Type: text/plain; charset=ISO-8859-1 This draft has been updated with general document improvements. There are no technical changes to the proposal. 1. Added some background material about UTC and TAI 2. Added leap-second example from the presentation I prepared for IETF 84 but ran out of time and will give at IETF 85 - http://tools.ietf.org/agenda/84/slides/slides-84-avtcore-8.pdf 3. Spelling corrections 4. Changed reference style from labeled to numbered 5. Added reference for leap-second elimination question Kevin Gross On Fri, Oct 19, 2012 at 6:28 PM, wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Audio/Video Transport Core Maintenance > Working Group of the IETF. > > Title : RTP and Leap Seconds > Author(s) : Kevin Gross > Ray van Brandenburg > Filename : draft-ietf-avtcore-leap-second-01.txt > Pages : 7 > Date : 2012-10-19 > > Abstract: > This document discusses issues that arise when RTP sessions span > Universal Coordinate Time (UTC) leap seconds. It updates RFC 3550 to > describe how RTP senders and receivers should behave in the presence > of leap seconds. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-avtcore-leap-second > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-avtcore-leap-second-01 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-leap-second-01 > > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > Audio/Video Transport Core Maintenance > avt@ietf.org > https://www.ietf.org/mailman/listinfo/avt > --f46d044304824a969704cc72d807 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
This draft has been updated with general document improvements. There = are no technical changes to the proposal.
  1. Added some back= ground material about UTC and TAI
  2. Added leap-second example from th= e presentation I prepared for IETF 84 but ran out of time and will give at = IETF 85 -=A0http://tools.ietf.org/agenda/84/slides/slides-84-avtcore-8.pdf<= /a>
  3. Spelling corrections
  4. Changed reference style from=A0labeled=A0t= o numbered
  5. Added reference for leap-second=A0elimination=A0question=


On Fri, Oct 19, 2012 at 6:28 PM, <internet-drafts@ietf.org>= wrote:

A New Internet-Draft is available from the on-line Internet-Drafts director= ies.
=A0This draft is a work item of the Audio/Video Transport Core Maintenance = Working Group of the IETF.

=A0 =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : RTP and Leap Seconds
=A0 =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : Kevin Gross
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Ray van Brandenburg
=A0 =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-ietf-avtcore-leap-second-01= .txt
=A0 =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 7
=A0 =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2012-10-19

Abstract:
=A0 =A0This document discusses issues that arise when RTP sessions span
=A0 =A0Universal Coordinate Time (UTC) leap seconds. =A0It updates RFC 3550= to
=A0 =A0describe how RTP senders and receivers should behave in the presence=
=A0 =A0of leap seconds.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-avtcore-leap= -second

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-avtcore-leap-second-0= 1

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtco= re-leap-second-01


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp= .ietf.org/internet-drafts/

_______________________________________________
Audio/Video Transport Core Maintenance
avt@ietf.org
htt= ps://www.ietf.org/mailman/listinfo/avt

--f46d044304824a969704cc72d807-- From bill.wu@huawei.com Sun Oct 21 18:35:15 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 077A221F891F for ; Sun, 21 Oct 2012 18:35:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.392 X-Spam-Level: X-Spam-Status: No, score=-0.392 tagged_above=-999 required=5 tests=[AWL=-4.407, BAYES_00=-2.599, FRT_STOCK1=3.988, FRT_STOCK2=3.988, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z0BDLmJSnLCt for ; Sun, 21 Oct 2012 18:35:12 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7C1E021F87B1 for ; Sun, 21 Oct 2012 18:35:11 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ALW44545; Mon, 22 Oct 2012 01:35:10 +0000 (GMT) Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 22 Oct 2012 02:35:07 +0100 Received: from SZXEML401-HUB.china.huawei.com (10.82.67.31) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 22 Oct 2012 02:35:10 +0100 Received: from w53375 (10.138.41.149) by szxeml401-hub.china.huawei.com (10.82.67.31) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 22 Oct 2012 09:34:57 +0800 Message-ID: From: Qin Wu To: Kevin Gross , References: <20121011071900.24901.9484.idtracker@ietfa.amsl.com> Date: Mon, 22 Oct 2012 09:34:56 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0349_01CDB038.7F61B7A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109 X-Originating-IP: [10.138.41.149] X-CFilter-Loop: Reflected Subject: Re: [AVTCORE] FW: I-D Action: draft-ietf-avtcore-idms-07.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 01:35:15 -0000 ------=_NextPart_000_0349_01CDB038.7F61B7A0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: base64 SGksIEtldmluOg0KSSBhZ3JlZSB3dGggeW91ciBjb21wYXJpc2lvbiBhbmFseXNpcyBiZXR3ZWVu IGRyYWZ0LXd1LXhyYmxvY2stcnRjcC14ci1vbmUtd2F5LWRlbGF5IGFuZCBkcmFmdC1pZXRmLWF2 dGNvcmUtaWRtcy0wNy4NClRoYW5rIGZvciB5b3VyIGNsYXJpZmljYXRpb24uDQoNClJlZ2FyZHMh DQotUWluDQogIC0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0gDQogIEZyb206IEtldmluIEdy b3NzIA0KICBUbzogYXZ0QGlldGYub3JnIA0KICBTZW50OiBTYXR1cmRheSwgT2N0b2JlciAyMCwg MjAxMiA0OjAyIEFNDQogIFN1YmplY3Q6IFJlOiBbQVZUQ09SRV0gRlc6IEktRCBBY3Rpb246IGRy YWZ0LWlldGYtYXZ0Y29yZS1pZG1zLTA3LnR4dA0KDQoNCiAgUmF5IGhhcyBhc2tlZCBtZSB0byBh ZGQgdG8gaGlzIGNvbW1lbnRzIGFuZCBhc3N1cmUgQVZUQ09SRSBtZW1iZXJzIHRoYXQgaW4gcHJl cGFyaW5nIHRoaXMgcmV2aXNpb24gdGhlIGF1dGhvcnMgYWxzbyBjb25zaWRlcmVkIHRoZSBmb2xs b3dpbmcgaXNzdWVzIGRpc2N1c3NlZCBhdCBJRVRGIDg0Og0KDQoNCiAgV2hpY2ggcGFja2V0IHRv IHJlcG9ydCBvbiAtIFdlIGRlY2lkZWQgdG8gYWxsb3cgZmxleGliaWxpdHkgaW4gd2hpY2ggUlRQ IHBhY2tldCBpcyB1c2VkIHRvIHJlcG9ydCBuZXR3b3JrIGRlbGF5LiBGbGV4aWJpbGl0eSBhbGxv d3MgaW1wbGVtZW50YXRpb25zIHRvIG9wdGltaXplIHJlcG9ydGluZyB0byBnZXQgdGhlIG1vc3Qg dXNlZnVsIGluZm9ybWF0aW9uIHRvIHRoZSBNU0FTIHF1aWNrbHkuIFdlIGRvIG5vdCBiZWxpZXZl IGludGVyb3BlcmFiaWxpdHkgb3IgcGVyZm9ybWFuY2UgaXMgY29tcHJvbWlzZWQgYnkgdGhpcyBm bGV4aWJpbGl0eS4NCg0KDQogIGRyYWZ0LXd1LXhyYmxvY2stcnRjcC14ci1vbmUtd2F5LWRlbGF5 IC0gV2UgY29uc2lkZXJlZCB3aGV0aGVyIHRoaXMgcHJvcG9zYWwgY291bGQgYmUgdXNlZCBpbnN0 ZWFkIG9mIHRoZSBhcHBsaWNhdGlvbi1zcGVjaWZpYyByZXBvcnRpbmcgbWVjaGFuaXNtIHByb3Bv c2VkIGluIG91ciBkcmFmdC4gV2UgZm91bmQgdGhpcyB1bnN1aXRhYmxlIGZvciB0aGUgZm9sbG93 aW5nIHJlYXNvbnMuDQogICAgMS4uIFRoZSBJRE1TIHByb3Bvc2FsIGRpcmVjdGx5IHJlcG9ydHMg b25lLXdheSBkZWxheSBvZiB0aGUgUlRQIHBhY2tldHMgb2YgdGhlIHN0cmVhbSB1bmRlciBjb250 cm9sIGJ5IElETVMuIFRoZSBvbmUtd2F5LWRlbGF5IHByb3Bvc2FsIG1lYXN1cmVzIG9uZS13YXkg ZGVsYXkgdXNpbmcgUlRDUCBwYWNrZXRzLiBSVFAgZGVsYXkgaXMgd2hhdCB3ZSBjYXJlIGFib3V0 IGZvciBwcm9wZXIgSURNUyBvcGVyYXRpb24uIFJUQ1AgcGFja2V0cyBhcmUgbGlrZWx5IHRvIGV4 cGVyaWVuY2UgZGlmZmVyZW50IChzaG9ydGVyKSBkZWxheSBkdWUgdG8gdGhlaXIgZGlmZmVyZW50 IChzbWFsbGVyKSBzaXplLiANCiAgICAyLi4gVGhlIG9uZS13YXktZGVsYXkgcHJvcG9zYWwgZG9l cyBub3QgaW5jbHVkZSBhIE1lZGlhIFN0cmVhbSBDb3JyZWxhdGlvbiBJZGVudGlmaWVyLiBUaGUg TVNBUyByZXF1aXJlcyB0aGlzIGluZm9ybWF0aW9uIHRvIGRvIGl0cyBqb2IuIElmIGl0IGlzIG5v dCBpbmNsdWRlZCBpbiB0aGUgWFIsIGl0IHdpbGwgbmVlZCB0byBiZSBzaWduYWxlZCB0aHJvdWdo IGFub3RoZXIgbWVhbnMgc2lnbmlmaWNhbnRseSBhbHRlcmluZyBhbmQgY29tcGxpY2F0aW5nIHRo ZSBzeXN0ZW0uIA0KICAgIDMuLiBUaGUgb25lLXdheS1kZWxheSBwcm9wb3NhbCBkb2VzIG5vdCBp bmNsdWRlIGEgcHJlc2VudGF0aW9uIHRpbWVzdGFtcCBtYWtpbmcgdGhlIHByZWNpc2Ugc3luY2hy b25pemF0aW9uIHJlcXVpcmVkIGJ5IHNvbWUgSURNUyBhcHBsaWNhdGlvbnMgZGlmZmljdWx0IG9y IGltcG9zc2libGUuDQoNCg0KICBLZXZpbiBHcm9zcw0KDQogICsxLTMwMy00NDctMDUxNw0KICBN ZWRpYSBOZXR3b3JrIENvbnN1bHRhbnQNCg0KICBBVkEgTmV0d29ya3MgLSB3d3cuQVZBbncuY29t LCB3d3cuWDE5Mi5vcmcNCg0KDQoNCg0KICBPbiBUaHUsIE9jdCAxMSwgMjAxMiBhdCAxOjI0IEFN LCBCcmFuZGVuYnVyZywgUi4gKFJheSkgdmFuIDxyYXkudmFuYnJhbmRlbmJ1cmdAdG5vLm5sPiB3 cm90ZToNCg0KICAgIEhpIGFsbCwNCg0KICAgIEkndmUganVzdCB1cGxvYWRlZCBhIG5ldyB2ZXJz aW9uIG9mIHRoZSBJRE1TIGRyYWZ0LiBUaGlzIG5ldyB2ZXJzaW9uIGluY2x1ZGVzIHRoZSBjb21t ZW50cyByZWNlaXZlZCBkdXJpbmcgdGhlIFdHTEMgd2hpY2ggd2VyZSBub3QgeWV0IGluY2x1ZGVk IGluIHRoZSAtMDYgdmVyc2lvbiBhbmQgYSBzb2x1dGlvbiB0byB0aGUgcGFja2V0IHJlcG9ydGlu ZyBpc3N1ZSB0aGF0IHdlIGRpc2N1c3NlZCBpbiBWYW5jb3V2ZXIuDQoNCiAgICBJIGJlbGlldmUg dGhhdCB3aXRoIHRoaXMgdmVyc2lvbiBhbGwgV0dMQyBjb21tZW50cyBoYXZlIGJlZW4gYWRkcmVz c2VkLg0KDQogICAgQmVzdCByZWdhcmRzLA0KDQogICAgUmF5IHZhbiBCcmFuZGVuYnVyZw0KDQoN Cg0KDQogICAgLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCiAgICBGcm9tOiBhdnQtYm91bmNl c0BpZXRmLm9yZyBbbWFpbHRvOmF2dC1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgaW50 ZXJuZXQtZHJhZnRzQGlldGYub3JnDQogICAgU2VudDogZG9uZGVyZGFnIDExIG9rdG9iZXIgMjAx MiA5OjE5DQogICAgVG86IGktZC1hbm5vdW5jZUBpZXRmLm9yZw0KICAgIENjOiBhdnRAaWV0Zi5v cmcNCiAgICBTdWJqZWN0OiBbQVZUQ09SRV0gSS1EIEFjdGlvbjogZHJhZnQtaWV0Zi1hdnRjb3Jl LWlkbXMtMDcudHh0DQoNCg0KICAgIEEgTmV3IEludGVybmV0LURyYWZ0IGlzIGF2YWlsYWJsZSBm cm9tIHRoZSBvbi1saW5lIEludGVybmV0LURyYWZ0cyBkaXJlY3Rvcmllcy4NCiAgICAgVGhpcyBk cmFmdCBpcyBhIHdvcmsgaXRlbSBvZiB0aGUgQXVkaW8vVmlkZW8gVHJhbnNwb3J0IENvcmUgTWFp bnRlbmFuY2UgV29ya2luZyBHcm91cCBvZiB0aGUgSUVURi4NCg0KICAgICAgICAgICAgVGl0bGUg ICAgICAgICAgIDogSW50ZXItZGVzdGluYXRpb24gTWVkaWEgU3luY2hyb25pemF0aW9uIHVzaW5n IHRoZSBSVFAgQ29udHJvbCBQcm90b2NvbCAoUlRDUCkNCiAgICAgICAgICAgIEF1dGhvcihzKSAg ICAgICA6IFJheSB2YW4gQnJhbmRlbmJ1cmcNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAg IEhhbnMgU3Rva2tpbmcNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIE9za2FyIHZhbiBE ZXZlbnRlcg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgRmVybmFuZG8gQm9yb25hdA0K ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgTWFyaW8gTW9udGFndWQNCiAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgIEtldmluIEdyb3NzDQogICAgICAgICAgICBGaWxlbmFtZSAgICAg ICAgOiBkcmFmdC1pZXRmLWF2dGNvcmUtaWRtcy0wNy50eHQNCiAgICAgICAgICAgIFBhZ2VzICAg ICAgICAgICA6IDI0DQogICAgICAgICAgICBEYXRlICAgICAgICAgICAgOiAyMDEyLTEwLTExDQoN CiAgICBBYnN0cmFjdDoNCiAgICAgICBUaGlzIGRvY3VtZW50IGdpdmVzIGluZm9ybWF0aW9uIG9u IGFuIFJUUCBDb250cm9sIFByb3RvY29sIChSVENQKQ0KICAgICAgIFBhY2tldCBUeXBlIGFuZCBS VENQIEV4dGVuZGVkIFJlcG9ydCAoWFIpIEJsb2NrIFR5cGUgaW5jbHVkaW5nDQogICAgICAgYXNz b2NpYXRlZCBTZXNzaW9uIERlc2NyaXB0aW9uIFByb3RvY29sIChTRFApIHBhcmFtZXRlcnMgZm9y IEludGVyLQ0KICAgICAgIERlc3RpbmF0aW9uIE1lZGlhIFN5bmNocm9uaXphdGlvbiAoSURNUyku ICBUaGlzIGRvY3VtZW50IG1hbmRhdGVzIHRoZQ0KICAgICAgIHVzZSBvZiB0aGUgUlRDUCBYUiBC bG9jayBUeXBlIDEyLCB3aGljaCBpcyB1c2VkIHRvIGNvbGxlY3QgbWVkaWENCiAgICAgICBwbGF5 b3V0IGluZm9ybWF0aW9uIGZyb20gcGFydGljaXBhbnRzIGluIGEgZ3JvdXAgcGxheWluZyBvdXQN CiAgICAgICAod2F0Y2hpbmcsIGxpc3RlbmluZywgZXRjLikgYSBzcGVjaWZpYyBSVFAgbWVkaWEg c3RyZWFtLiAgVGhpcyBSVENQDQogICAgICAgWFIgQmxvY2sgVHlwZSBpcyBzcGVjaWZpZWQgYW5k IHJlZ2lzdGVyZWQgd2l0aCBJQU5BIGJ5IEVUU0kuICBUaGUNCiAgICAgICBSVENQIHBhY2tldCB0 eXBlIHNwZWNpZmllZCBieSB0aGlzIGRvY3VtZW50IGlzIHVzZWQgdG8gZGlzdHJpYnV0ZSBhDQog ICAgICAgY29tbW9uIHRhcmdldCBwbGF5b3V0IHBvaW50IHRvIHdoaWNoIGFsbCB0aGUgZGlzdHJp YnV0ZWQgcmVjZWl2ZXJzLA0KICAgICAgIHNoYXJpbmcgYSBtZWRpYSBleHBlcmllbmNlLCBjYW4g c3luY2hyb25pemUuDQoNCiAgICAgICBUeXBpY2FsIHVzZSBjYXNlcyBpbiB3aGljaCBJRE1TIGlz IHVzZWZ1bGwgYXJlIHNvY2lhbCBUViwgc2hhcmVkDQogICAgICAgc2VydmljZSBjb250cm9sIChp LmUuIGFwcGxpY2F0aW9ucyB3aGVyZSB0d28gb3IgbW9yZSBnZW9ncmFwaGljYWxseQ0KICAgICAg IHNlcGFyYXRlZCB1c2VycyBhcmUgd2F0Y2hpbmcgYSBtZWRpYSBzdHJlYW0gdG9nZXRoZXIpLCBk aXN0YW5jZQ0KICAgICAgIGxlYXJuaW5nLCBuZXR3b3JrZWQgdmlkZW8gd2FsbHMsIG5ldHdvcmtl ZCBsb3Vkc3BlYWtlcnMsIGV0Yy4NCg0KDQogICAgVGhlIElFVEYgZGF0YXRyYWNrZXIgc3RhdHVz IHBhZ2UgZm9yIHRoaXMgZHJhZnQgaXM6DQogICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9y Zy9kb2MvZHJhZnQtaWV0Zi1hdnRjb3JlLWlkbXMNCg0KICAgIFRoZXJlJ3MgYWxzbyBhIGh0bWxp emVkIHZlcnNpb24gYXZhaWxhYmxlIGF0Og0KICAgIGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1s L2RyYWZ0LWlldGYtYXZ0Y29yZS1pZG1zLTA3DQoNCiAgICBBIGRpZmYgZnJvbSB0aGUgcHJldmlv dXMgdmVyc2lvbiBpcyBhdmFpbGFibGUgYXQ6DQogICAgaHR0cDovL3d3dy5pZXRmLm9yZy9yZmNk aWZmP3VybDI9ZHJhZnQtaWV0Zi1hdnRjb3JlLWlkbXMtMDcNCg0KDQogICAgSW50ZXJuZXQtRHJh ZnRzIGFyZSBhbHNvIGF2YWlsYWJsZSBieSBhbm9ueW1vdXMgRlRQIGF0Og0KICAgIGZ0cDovL2Z0 cC5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvDQoNCiAgICBfX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fXw0KICAgIEF1ZGlvL1ZpZGVvIFRyYW5zcG9ydCBDb3Jl IE1haW50ZW5hbmNlDQogICAgYXZ0QGlldGYub3JnDQogICAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcv bWFpbG1hbi9saXN0aW5mby9hdnQNCg0KICAgIFRoaXMgZS1tYWlsIGFuZCBpdHMgY29udGVudHMg YXJlIHN1YmplY3QgdG8gdGhlIERJU0NMQUlNRVIgYXQgaHR0cDovL3d3dy50bm8ubmwvZW1haWxk aXNjbGFpbWVyDQoNCg0KICAgIF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fDQogICAgQXVkaW8vVmlkZW8gVHJhbnNwb3J0IENvcmUgTWFpbnRlbmFuY2UNCiAg ICBhdnRAaWV0Zi5vcmcNCiAgICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv L2F2dA0KDQoNCg0KDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQoNCiAgX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCiAgQXVkaW8vVmlkZW8gVHJhbnNw b3J0IENvcmUgTWFpbnRlbmFuY2UNCiAgYXZ0QGlldGYub3JnDQogIGh0dHBzOi8vd3d3LmlldGYu b3JnL21haWxtYW4vbGlzdGluZm8vYXZ0DQo= ------=_NextPart_000_0349_01CDB038.7F61B7A0 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWlz by04ODU5LTEiIGh0dHAtZXF1aXY9Q29udGVudC1UeXBlPg0KPE1FVEEgbmFtZT1HRU5FUkFUT1Ig Y29udGVudD0iTVNIVE1MIDguMDAuNjAwMS4xOTI5OCI+DQo8U1RZTEU+PC9TVFlMRT4NCjwvSEVB RD4NCjxCT0RZIGJnQ29sb3I9I2ZmZmZmZj4NCjxESVY+SGksIEtldmluOjwvRElWPg0KPERJVj5J IGFncmVlIHd0aCB5b3VyIGNvbXBhcmlzaW9uIGFuYWx5c2lzIGJldHdlZW4gDQpkcmFmdC13dS14 cmJsb2NrLXJ0Y3AteHItb25lLXdheS1kZWxheSBhbmQgZHJhZnQtaWV0Zi1hdnRjb3JlLWlkbXMt MDcuPC9ESVY+DQo8RElWPlRoYW5rIGZvciB5b3VyIGNsYXJpZmljYXRpb24uPC9ESVY+DQo8RElW PjxGT05UIHNpemU9MiBmYWNlPSYjMjM0MzU7JiMyMDMwNzs+PC9GT05UPiZuYnNwOzwvRElWPg0K PERJVj5SZWdhcmRzITwvRElWPg0KPERJVj4tUWluPC9ESVY+DQo8QkxPQ0tRVU9URSANCnN0eWxl PSJCT1JERVItTEVGVDogIzAwMDAwMCAycHggc29saWQ7IFBBRERJTkctTEVGVDogNXB4OyBQQURE SU5HLVJJR0hUOiAwcHg7IE1BUkdJTi1MRUZUOiA1cHg7IE1BUkdJTi1SSUdIVDogMHB4Ij4NCiAg PERJViBzdHlsZT0iRk9OVDogOXB0ICYjMjM0MzU7JiMyMDMwNzsiPi0tLS0tIE9yaWdpbmFsIE1l c3NhZ2UgLS0tLS0gPC9ESVY+DQogIDxESVYgc3R5bGU9IkZPTlQ6IDlwdCAmIzIzNDM1OyYjMjAz MDc7OyBCQUNLR1JPVU5EOiAjZTRlNGU0OyBmb250LWNvbG9yOiBibGFjayI+PEI+RnJvbTo8L0I+ IA0KICA8QSB0aXRsZT1rZXZpbi5ncm9zc0BhdmFudy5jb20gaHJlZj0ibWFpbHRvOmtldmluLmdy b3NzQGF2YW53LmNvbSI+S2V2aW4gDQogIEdyb3NzPC9BPiA8L0RJVj4NCiAgPERJViBzdHlsZT0i Rk9OVDogOXB0ICYjMjM0MzU7JiMyMDMwNzsiPjxCPlRvOjwvQj4gPEEgdGl0bGU9YXZ0QGlldGYu b3JnIA0KICBocmVmPSJtYWlsdG86YXZ0QGlldGYub3JnIj5hdnRAaWV0Zi5vcmc8L0E+IDwvRElW Pg0KICA8RElWIHN0eWxlPSJGT05UOiA5cHQgJiMyMzQzNTsmIzIwMzA3OyI+PEI+U2VudDo8L0I+ IFNhdHVyZGF5LCBPY3RvYmVyIDIwLCAyMDEyIDQ6MDIgDQpBTTwvRElWPg0KICA8RElWIHN0eWxl PSJGT05UOiA5cHQgJiMyMzQzNTsmIzIwMzA3OyI+PEI+U3ViamVjdDo8L0I+IFJlOiBbQVZUQ09S RV0gRlc6IEktRCBBY3Rpb246IA0KICBkcmFmdC1pZXRmLWF2dGNvcmUtaWRtcy0wNy50eHQ8L0RJ Vj4NCiAgPERJVj48QlI+PC9ESVY+DQogIDxESVY+UmF5IGhhcyBhc2tlZCBtZSB0byBhZGQgdG8g aGlzIGNvbW1lbnRzIGFuZCBhc3N1cmUgQVZUQ09SRSBtZW1iZXJzIHRoYXQgDQogIGluIHByZXBh cmluZyB0aGlzIHJldmlzaW9uIHRoZSBhdXRob3JzIGFsc28gY29uc2lkZXJlZCB0aGUgZm9sbG93 aW5nIGlzc3VlcyANCiAgZGlzY3Vzc2VkIGF0IElFVEYgODQ6PC9ESVY+DQogIDxESVY+PEJSPjwv RElWPg0KICA8RElWPldoaWNoIHBhY2tldCB0byByZXBvcnQgb24gLSBXZSBkZWNpZGVkIHRvIGFs bG93IGZsZXhpYmlsaXR5IGluIHdoaWNoIFJUUCANCiAgcGFja2V0IGlzIHVzZWQgdG8gcmVwb3J0 IG5ldHdvcmsgZGVsYXkuIEZsZXhpYmlsaXR5IGFsbG93cyBpbXBsZW1lbnRhdGlvbnMgdG8gDQog IG9wdGltaXplJm5ic3A7cmVwb3J0aW5nJm5ic3A7dG8gZ2V0IHRoZSBtb3N0IHVzZWZ1bCBpbmZv cm1hdGlvbiB0byB0aGUgTVNBUyANCiAgcXVpY2tseS4gV2UgZG8gbm90Jm5ic3A7YmVsaWV2ZSZu YnNwO2ludGVyb3BlcmFiaWxpdHkgb3IgcGVyZm9ybWFuY2UgaXMgDQogIGNvbXByb21pc2VkIGJ5 IHRoaXMgZmxleGliaWxpdHkuPC9ESVY+DQogIDxESVY+PEJSPjwvRElWPmRyYWZ0LXd1LXhyYmxv Y2stcnRjcC14ci1vbmUtd2F5LWRlbGF5IC0gV2UgY29uc2lkZXJlZCB3aGV0aGVyIA0KICB0aGlz IHByb3Bvc2FsIGNvdWxkIGJlIHVzZWQmbmJzcDtpbnN0ZWFkJm5ic3A7b2YgdGhlJm5ic3A7YXBw bGljYXRpb24tc3BlY2lmaWMgDQogIHJlcG9ydGluZyBtZWNoYW5pc20gcHJvcG9zZWQgaW4gb3Vy IGRyYWZ0LiBXZSBmb3VuZCB0aGlzIHVuc3VpdGFibGUgZm9yIHRoZSANCiAgZm9sbG93aW5nIHJl YXNvbnMuDQogIDxESVY+DQogIDxPTD4NCiAgICA8TEk+VGhlIElETVMgcHJvcG9zYWwgZGlyZWN0 bHkgcmVwb3J0cyBvbmUtd2F5IGRlbGF5IG9mIHRoZSBSVFAgcGFja2V0cyBvZiANCiAgICB0aGUg c3RyZWFtIHVuZGVyIGNvbnRyb2wgYnkgSURNUy4gVGhlIG9uZS13YXktZGVsYXkgcHJvcG9zYWwg bWVhc3VyZXMgDQogICAgb25lLXdheSBkZWxheSB1c2luZyBSVENQIHBhY2tldHMuIFJUUCBkZWxh eSBpcyB3aGF0IHdlIGNhcmUgYWJvdXQgZm9yIHByb3BlciANCiAgICBJRE1TIG9wZXJhdGlvbi4g UlRDUCBwYWNrZXRzIGFyZSBsaWtlbHkgdG8gZXhwZXJpZW5jZSBkaWZmZXJlbnQgKHNob3J0ZXIp IA0KICAgIGRlbGF5IGR1ZSB0byB0aGVpciBkaWZmZXJlbnQgKHNtYWxsZXIpIHNpemUuIA0KICAg IDxMST5UaGUgb25lLXdheS1kZWxheSBwcm9wb3NhbCBkb2VzIG5vdCBpbmNsdWRlIGEgTWVkaWEg U3RyZWFtIENvcnJlbGF0aW9uIA0KICAgIElkZW50aWZpZXIuIFRoZSBNU0FTIHJlcXVpcmVzIHRo aXMgaW5mb3JtYXRpb24gdG8gZG8gaXRzIGpvYi4gSWYgaXQgaXMgbm90IA0KICAgIGluY2x1ZGVk IGluIHRoZSBYUiwgaXQgd2lsbCBuZWVkIHRvIGJlIHNpZ25hbGVkIHRocm91Z2ggYW5vdGhlciAN CiAgICBtZWFucyZuYnNwO3NpZ25pZmljYW50bHkmbmJzcDthbHRlcmluZyBhbmQgY29tcGxpY2F0 aW5nIHRoZSBzeXN0ZW0uIA0KICAgIDxMST5UaGUgb25lLXdheS1kZWxheSBwcm9wb3NhbCZuYnNw O2RvZXMgbm90IGluY2x1ZGUgYSZuYnNwO3ByZXNlbnRhdGlvbiANCiAgICB0aW1lc3RhbXAgbWFr aW5nIHRoZSBwcmVjaXNlIHN5bmNocm9uaXphdGlvbiByZXF1aXJlZCBieSBzb21lIElETVMgDQog ICAgYXBwbGljYXRpb25zIGRpZmZpY3VsdCBvciBpbXBvc3NpYmxlLjwvTEk+PC9PTD48L0RJVj4N CiAgPERJVj4NCiAgPERJVj48QlI+PC9ESVY+S2V2aW4gR3Jvc3M8QlI+DQogIDxESVY+KzEtMzAz LTQ0Ny0wNTE3PC9ESVY+DQogIDxESVY+TWVkaWEgTmV0d29yayBDb25zdWx0YW50PEJSPg0KICA8 RElWPkFWQSBOZXR3b3JrcyAtJm5ic3A7PEEgaHJlZj0iaHR0cDovL3d3dy5hdmFudy5jb20vIiAN CiAgdGFyZ2V0PV9ibGFuaz53d3cuQVZBbncuY29tPC9BPiwmbmJzcDs8QSBocmVmPSJodHRwOi8v d3d3LlgxOTIub3JnIiANCiAgdGFyZ2V0PV9ibGFuaz53d3cuWDE5Mi5vcmc8L0E+PC9ESVY+PC9E SVY+PEJSPjxCUj48QlI+DQogIDxESVYgY2xhc3M9Z21haWxfcXVvdGU+T24gVGh1LCBPY3QgMTEs IDIwMTIgYXQgMToyNCBBTSwgQnJhbmRlbmJ1cmcsIFIuIChSYXkpIA0KICB2YW4gPFNQQU4gZGly PWx0cj4mbHQ7PEEgaHJlZj0ibWFpbHRvOnJheS52YW5icmFuZGVuYnVyZ0B0bm8ubmwiIA0KICB0 YXJnZXQ9X2JsYW5rPnJheS52YW5icmFuZGVuYnVyZ0B0bm8ubmw8L0E+Jmd0OzwvU1BBTj4gd3Jv dGU6PEJSPg0KICA8QkxPQ0tRVU9URSANCiAgc3R5bGU9IkJPUkRFUi1MRUZUOiAjY2NjIDFweCBz b2xpZDsgTUFSR0lOOiAwcHggMHB4IDBweCAwLjhleDsgUEFERElORy1MRUZUOiAxZXgiIA0KICBj bGFzcz1nbWFpbF9xdW90ZT5IaSBhbGwsPEJSPjxCUj5JJ3ZlIGp1c3QgdXBsb2FkZWQgYSBuZXcg dmVyc2lvbiBvZiB0aGUgDQogICAgSURNUyBkcmFmdC4gVGhpcyBuZXcgdmVyc2lvbiBpbmNsdWRl cyB0aGUgY29tbWVudHMgcmVjZWl2ZWQgZHVyaW5nIHRoZSBXR0xDIA0KICAgIHdoaWNoIHdlcmUg bm90IHlldCBpbmNsdWRlZCBpbiB0aGUgLTA2IHZlcnNpb24gYW5kIGEgc29sdXRpb24gdG8gdGhl IHBhY2tldCANCiAgICByZXBvcnRpbmcgaXNzdWUgdGhhdCB3ZSBkaXNjdXNzZWQgaW4gVmFuY291 dmVyLjxCUj48QlI+SSBiZWxpZXZlIHRoYXQgd2l0aCANCiAgICB0aGlzIHZlcnNpb24gYWxsIFdH TEMgY29tbWVudHMgaGF2ZSBiZWVuIGFkZHJlc3NlZC48QlI+PEJSPkJlc3QgDQogICAgcmVnYXJk cyw8QlI+PEJSPlJheSB2YW4gQnJhbmRlbmJ1cmc8QlI+DQogICAgPERJVj4NCiAgICA8RElWIGNs YXNzPWg1PjxCUj48QlI+PEJSPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tPEJSPkZyb206IDxB IA0KICAgIGhyZWY9Im1haWx0bzphdnQtYm91bmNlc0BpZXRmLm9yZyI+YXZ0LWJvdW5jZXNAaWV0 Zi5vcmc8L0E+IFttYWlsdG86PEEgDQogICAgaHJlZj0ibWFpbHRvOmF2dC1ib3VuY2VzQGlldGYu b3JnIj5hdnQtYm91bmNlc0BpZXRmLm9yZzwvQT5dIE9uIEJlaGFsZiBPZiA8QSANCiAgICBocmVm PSJtYWlsdG86aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIj5pbnRlcm5ldC1kcmFmdHNAaWV0Zi5v cmc8L0E+PEJSPlNlbnQ6IA0KICAgIGRvbmRlcmRhZyAxMSBva3RvYmVyIDIwMTIgOToxOTxCUj5U bzogPEEgDQogICAgaHJlZj0ibWFpbHRvOmktZC1hbm5vdW5jZUBpZXRmLm9yZyI+aS1kLWFubm91 bmNlQGlldGYub3JnPC9BPjxCUj5DYzogPEEgDQogICAgaHJlZj0ibWFpbHRvOmF2dEBpZXRmLm9y ZyI+YXZ0QGlldGYub3JnPC9BPjxCUj5TdWJqZWN0OiBbQVZUQ09SRV0gSS1EIA0KICAgIEFjdGlv bjogZHJhZnQtaWV0Zi1hdnRjb3JlLWlkbXMtMDcudHh0PEJSPjxCUj48QlI+QSBOZXcgSW50ZXJu ZXQtRHJhZnQgaXMgDQogICAgYXZhaWxhYmxlIGZyb20gdGhlIG9uLWxpbmUgSW50ZXJuZXQtRHJh ZnRzIGRpcmVjdG9yaWVzLjxCUj4mbmJzcDtUaGlzIGRyYWZ0IA0KICAgIGlzIGEgd29yayBpdGVt IG9mIHRoZSBBdWRpby9WaWRlbyBUcmFuc3BvcnQgQ29yZSBNYWludGVuYW5jZSBXb3JraW5nIEdy b3VwIA0KICAgIG9mIHRoZSBJRVRGLjxCUj48QlI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7 IFRpdGxlICZuYnNwOyAmbmJzcDsgJm5ic3A7IA0KICAgICZuYnNwOyAmbmJzcDsgOiBJbnRlci1k ZXN0aW5hdGlvbiBNZWRpYSBTeW5jaHJvbml6YXRpb24gdXNpbmcgdGhlIFJUUCANCiAgICBDb250 cm9sIFByb3RvY29sIChSVENQKTxCUj4mbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgQXV0aG9y KHMpICZuYnNwOyANCiAgICAmbmJzcDsgJm5ic3A7IDogUmF5IHZhbiBCcmFuZGVuYnVyZzxCUj4m bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IA0KICAgICZuYnNwOyAmbmJzcDsgJm5i c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgSGFucyANCiAgICBTdG9ra2lu ZzxCUj4mbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i c3A7ICZuYnNwOyANCiAgICAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgT3NrYXIgdmFuIERl dmVudGVyPEJSPiZuYnNwOyAmbmJzcDsgJm5ic3A7IA0KICAgICZuYnNwOyAmbmJzcDsgJm5ic3A7 ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyANCiAgICBG ZXJuYW5kbyBCb3JvbmF0PEJSPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i c3A7ICZuYnNwOyAmbmJzcDsgDQogICAgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw OyBNYXJpbyBNb250YWd1ZDxCUj4mbmJzcDsgJm5ic3A7ICZuYnNwOyANCiAgICAmbmJzcDsgJm5i c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz cDsgS2V2aW4gDQogICAgR3Jvc3M8QlI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IEZpbGVu YW1lICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOzogDQogICAgZHJhZnQtaWV0Zi1hdnRjb3Jl LWlkbXMtMDcudHh0PEJSPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBQYWdlcyAmbmJzcDsg DQogICAgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IDogMjQ8QlI+Jm5ic3A7ICZuYnNwOyAm bmJzcDsgJm5ic3A7IERhdGUgJm5ic3A7IA0KICAgICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw OyAmbmJzcDs6IDIwMTItMTAtMTE8QlI+PEJSPkFic3RyYWN0OjxCUj4mbmJzcDsgDQogICAgJm5i c3A7VGhpcyBkb2N1bWVudCBnaXZlcyBpbmZvcm1hdGlvbiBvbiBhbiBSVFAgQ29udHJvbCBQcm90 b2NvbCANCiAgICAoUlRDUCk8QlI+Jm5ic3A7ICZuYnNwO1BhY2tldCBUeXBlIGFuZCBSVENQIEV4 dGVuZGVkIFJlcG9ydCAoWFIpIEJsb2NrIFR5cGUgDQogICAgaW5jbHVkaW5nPEJSPiZuYnNwOyAm bmJzcDthc3NvY2lhdGVkIFNlc3Npb24gRGVzY3JpcHRpb24gUHJvdG9jb2wgKFNEUCkgDQogICAg cGFyYW1ldGVycyBmb3IgSW50ZXItPEJSPiZuYnNwOyAmbmJzcDtEZXN0aW5hdGlvbiBNZWRpYSBT eW5jaHJvbml6YXRpb24gDQogICAgKElETVMpLiAmbmJzcDtUaGlzIGRvY3VtZW50IG1hbmRhdGVz IHRoZTxCUj4mbmJzcDsgJm5ic3A7dXNlIG9mIHRoZSBSVENQIFhSIA0KICAgIEJsb2NrIFR5cGUg MTIsIHdoaWNoIGlzIHVzZWQgdG8gY29sbGVjdCBtZWRpYTxCUj4mbmJzcDsgJm5ic3A7cGxheW91 dCANCiAgICBpbmZvcm1hdGlvbiBmcm9tIHBhcnRpY2lwYW50cyBpbiBhIGdyb3VwIHBsYXlpbmcg b3V0PEJSPiZuYnNwOyANCiAgICAmbmJzcDsod2F0Y2hpbmcsIGxpc3RlbmluZywgZXRjLikgYSBz cGVjaWZpYyBSVFAgbWVkaWEgc3RyZWFtLiAmbmJzcDtUaGlzIA0KICAgIFJUQ1A8QlI+Jm5ic3A7 ICZuYnNwO1hSIEJsb2NrIFR5cGUgaXMgc3BlY2lmaWVkIGFuZCByZWdpc3RlcmVkIHdpdGggSUFO QSBieSANCiAgICBFVFNJLiAmbmJzcDtUaGU8QlI+Jm5ic3A7ICZuYnNwO1JUQ1AgcGFja2V0IHR5 cGUgc3BlY2lmaWVkIGJ5IHRoaXMgZG9jdW1lbnQgDQogICAgaXMgdXNlZCB0byBkaXN0cmlidXRl IGE8QlI+Jm5ic3A7ICZuYnNwO2NvbW1vbiB0YXJnZXQgcGxheW91dCBwb2ludCB0byB3aGljaCAN CiAgICBhbGwgdGhlIGRpc3RyaWJ1dGVkIHJlY2VpdmVycyw8QlI+Jm5ic3A7ICZuYnNwO3NoYXJp bmcgYSBtZWRpYSBleHBlcmllbmNlLCANCiAgICBjYW4gc3luY2hyb25pemUuPEJSPjxCUj4mbmJz cDsgJm5ic3A7VHlwaWNhbCB1c2UgY2FzZXMgaW4gd2hpY2ggSURNUyBpcyANCiAgICB1c2VmdWxs IGFyZSBzb2NpYWwgVFYsIHNoYXJlZDxCUj4mbmJzcDsgJm5ic3A7c2VydmljZSBjb250cm9sIChp LmUuIA0KICAgIGFwcGxpY2F0aW9ucyB3aGVyZSB0d28gb3IgbW9yZSBnZW9ncmFwaGljYWxseTxC Uj4mbmJzcDsgJm5ic3A7c2VwYXJhdGVkIA0KICAgIHVzZXJzIGFyZSB3YXRjaGluZyBhIG1lZGlh IHN0cmVhbSB0b2dldGhlciksIGRpc3RhbmNlPEJSPiZuYnNwOyANCiAgICAmbmJzcDtsZWFybmlu ZywgbmV0d29ya2VkIHZpZGVvIHdhbGxzLCBuZXR3b3JrZWQgbG91ZHNwZWFrZXJzLCANCiAgICBl dGMuPEJSPjxCUj48QlI+VGhlIElFVEYgZGF0YXRyYWNrZXIgc3RhdHVzIHBhZ2UgZm9yIHRoaXMg ZHJhZnQgaXM6PEJSPjxBIA0KICAgIGhyZWY9Imh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcv ZG9jL2RyYWZ0LWlldGYtYXZ0Y29yZS1pZG1zIiANCiAgICB0YXJnZXQ9X2JsYW5rPmh0dHBzOi8v ZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtYXZ0Y29yZS1pZG1zPC9BPjxCUj48 QlI+VGhlcmUncyANCiAgICBhbHNvIGEgaHRtbGl6ZWQgdmVyc2lvbiBhdmFpbGFibGUgYXQ6PEJS PjxBIA0KICAgIGhyZWY9Imh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtYXZ0 Y29yZS1pZG1zLTA3IiANCiAgICB0YXJnZXQ9X2JsYW5rPmh0dHA6Ly90b29scy5pZXRmLm9yZy9o dG1sL2RyYWZ0LWlldGYtYXZ0Y29yZS1pZG1zLTA3PC9BPjxCUj48QlI+QSANCiAgICBkaWZmIGZy b20gdGhlIHByZXZpb3VzIHZlcnNpb24gaXMgYXZhaWxhYmxlIGF0OjxCUj48QSANCiAgICBocmVm PSJodHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1pZXRmLWF2dGNvcmUtaWRt cy0wNyIgDQogICAgdGFyZ2V0PV9ibGFuaz5odHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJs Mj1kcmFmdC1pZXRmLWF2dGNvcmUtaWRtcy0wNzwvQT48QlI+PEJSPjxCUj5JbnRlcm5ldC1EcmFm dHMgDQogICAgYXJlIGFsc28gYXZhaWxhYmxlIGJ5IGFub255bW91cyBGVFAgYXQ6PEJSPjxBIA0K ICAgIGhyZWY9ImZ0cDovL2Z0cC5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvIiANCiAgICB0YXJn ZXQ9X2JsYW5rPmZ0cDovL2Z0cC5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvPC9BPjxCUj48QlI+ X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188QlI+QXVkaW8v VmlkZW8gDQogICAgVHJhbnNwb3J0IENvcmUgTWFpbnRlbmFuY2U8QlI+PEEgDQogICAgaHJlZj0i bWFpbHRvOmF2dEBpZXRmLm9yZyI+YXZ0QGlldGYub3JnPC9BPjxCUj48QSANCiAgICBocmVmPSJo dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2F2dCIgDQogICAgdGFyZ2V0PV9i bGFuaz5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2F2dDwvQT48QlI+PC9E SVY+PC9ESVY+VGhpcyANCiAgICBlLW1haWwgYW5kIGl0cyBjb250ZW50cyBhcmUgc3ViamVjdCB0 byB0aGUgRElTQ0xBSU1FUiBhdCA8QSANCiAgICBocmVmPSJodHRwOi8vd3d3LnRuby5ubC9lbWFp bGRpc2NsYWltZXIiIA0KICAgIHRhcmdldD1fYmxhbms+aHR0cDovL3d3dy50bm8ubmwvZW1haWxk aXNjbGFpbWVyPC9BPjxCUj4NCiAgICA8RElWIGNsYXNzPUhPRW5aYj4NCiAgICA8RElWIA0KICAg IGNsYXNzPWg1PjxCUj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fXzxCUj5BdWRpby9WaWRlbyANCiAgICBUcmFuc3BvcnQgQ29yZSBNYWludGVuYW5jZTxCUj48 QSANCiAgICBocmVmPSJtYWlsdG86YXZ0QGlldGYub3JnIj5hdnRAaWV0Zi5vcmc8L0E+PEJSPjxB IA0KICAgIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vYXZ0IiAN CiAgICB0YXJnZXQ9X2JsYW5rPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v YXZ0PC9BPjxCUj48L0RJVj48L0RJVj48L0JMT0NLUVVPVEU+PC9ESVY+PEJSPjwvRElWPg0KICA8 UD4NCiAgPEhSPg0KDQogIDxQPjwvUD5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXzxCUj5BdWRpby9WaWRlbyANCiAgVHJhbnNwb3J0IENvcmUgDQogIE1haW50 ZW5hbmNlPEJSPmF2dEBpZXRmLm9yZzxCUj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp c3RpbmZvL2F2dDxCUj48L0JMT0NLUVVPVEU+PC9CT0RZPjwvSFRNTD4NCg== ------=_NextPart_000_0349_01CDB038.7F61B7A0-- From csp@csperkins.org Mon Oct 22 04:37:45 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBE4721F8BB6 for ; Mon, 22 Oct 2012 04:37:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.848 X-Spam-Level: X-Spam-Status: No, score=-105.848 tagged_above=-999 required=5 tests=[AWL=0.750, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w1LTDe3T1qlm for ; Mon, 22 Oct 2012 04:37:44 -0700 (PDT) Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [93.93.130.6]) by ietfa.amsl.com (Postfix) with ESMTP id 7BC6521F8BB0 for ; Mon, 22 Oct 2012 04:37:44 -0700 (PDT) Received: from [130.209.247.112] (helo=mangole.dcs.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.69) (envelope-from ) id 1TQGKF-00033l-3t; Mon, 22 Oct 2012 12:37:43 +0100 Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: multipart/alternative; boundary="Apple-Mail=_68F96868-F70B-432B-BCAD-93A31DDF2153" From: Colin Perkins In-Reply-To: Date: Mon, 22 Oct 2012 12:37:42 +0100 Message-Id: <89C3B25E-7970-46DE-A26E-CABA6C1BB6EC@csperkins.org> References: To: "Brandenburg, R. (Ray) van" X-Mailer: Apple Mail (2.1283) X-BlackCat-Spam-Score: -12 X-Mythic-Debug: Threshold = On = Cc: Magnus Westerlund , "avt@ietf.org" Subject: Re: [AVTCORE] Comments on draft-ietf-avt-srtp-not-mandatory-09 X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 11:37:45 -0000 --Apple-Mail=_68F96868-F70B-432B-BCAD-93A31DDF2153 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Ray, Thank you for your comments. These all look very reasonable. I'm about = to submit a -10 version of the draft that should hopefully address them. Colin On 3 Aug 2012, at 03:22, Brandenburg, R. (Ray) van wrote: > Hi Colin/Magnus, >=20 >=20 > This is my review of draft-ietf-avt-srtp-not-mandatory-09. Since I'm = not a security expert, I can't say anything about the security = implications of the document. That said, I do have some other comments. = I've not been following the discussion on this topic very closely on the = list, so please excuse me if any topics I bring up have already been = discussed on list earlier. >=20 >=20 > 1) The page-header of the draft is 'SRTP is not the only RTP Security = Option'. Although I understand that this header summarizes the rationale = for writing the draft in the first place, from reading the abstract and = introduction of the draft, this header seems a little out of place. I = would suggest to either more clearly describe its relevance in the = abstract or introduction (where SRTP is not mentioned), or choose a = different header.=20 >=20 >=20 > 2) Section 3, paragraph 3 states that SRTP is not suitable for some = scenarios and applications. I completely agree with this, but the text = could use at least one example of such an application or scenario, and = reasons for SRTP not being applicable to that application, especially = since it is fundamental to the argument being made in the draft (that = there is no individual RTP security methods which is suitable for all = applications). Basically, the draft spends a lot of time explaining why = RTP is a framework and it is therefore not possible to mandate any = single security mechanism, however, it doesn't explain why the most-used = security mechanism (SRTP) is not suitable for this.=20 >=20 >=20 > 3) Section 6 describes the actual guidelines for future security = extensions for RTP that are mentioned in the abstract, and in that sense = forms a important part of the draft. It might be useful to more clearly = indicate/highlight them in that way (e.g. by changing the section title = to include the word 'guidelines').=20 >=20 >=20 > 4) The conclusion (section 7) states 'it is hoped that this memo = explains why SRTP is not mandatory as the media security solution for = RTP-based systems'. This conclusion could be supported by more = substantial arguments in the rest of the document, especially related to = SRTP, which is not mentioned apart from the brief mention in section 3, = where no actual arguments are given. See also comment 2).=20 >=20 >=20 > 5) And some nits: >=20 > - Section 7: comon -> common >=20 > - Section 7: important consider -> important to consider >=20 > - Section 7: applications -> application >=20 >=20 > Best regards, >=20 >=20 > Ray >=20 >>=20 >=20 > This e-mail and its contents are subject to the DISCLAIMER at = http://www.tno.nl/emaildisclaimer >=20 > _______________________________________________ > Audio/Video Transport Core Maintenance > avt@ietf.org > https://www.ietf.org/mailman/listinfo/avt --=20 Colin Perkins http://csperkins.org/ --Apple-Mail=_68F96868-F70B-432B-BCAD-93A31DDF2153 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii Hi Ray,

Thank you for your comments. These all look very reasonable. I'm about to submit a -10 version of the draft that should hopefully address them.

Colin


On 3 Aug 2012, at 03:22, Brandenburg, R. (Ray) van wrote:

Hi Colin/Magnus,


This is my review of draft-ietf-avt-srtp-not-mandatory-09. Since I'm not a security expert, I can't say anything about the security implications of the document. That said, I do have some other comments. I've not been following the discussion on this topic very closely on the list, so please excuse me if any topics I bring up have already been discussed on list earlier.


1) The page-header of the draft is 'SRTP is not the only RTP Security Option'. Although I understand that this header summarizes the rationale for writing the draft in the first place, from reading the abstract and introduction of the draft, this header seems a little out of place. I would suggest to either more clearly describe its relevance in the abstract or introduction (where SRTP is not mentioned), or choose a different header. 


2) Section 3, paragraph 3 states that SRTP is not suitable for some scenarios and applications. I completely agree with this, but the text could use at least one example of such an application or scenario, and reasons for SRTP not being applicable to that application, especially since it is fundamental to the argument being made in the draft (that there is no individual RTP security methods which is suitable for all applications). Basically, the draft spends a lot of time explaining why RTP is a framework and it is therefore not possible to mandate any single security mechanism, however, it doesn't explain why the most-used security mechanism (SRTP) is not suitable for this. 


3) Section 6 describes the actual guidelines for future security extensions for RTP that are mentioned in the abstract, and in that sense forms a important part of the draft. It might be useful to more clearly indicate/highlight them in that way (e.g. by changing the section title to include the word 'guidelines'). 


4) The conclusion (section 7) states 'it is hoped that this memo explains why SRTP is not mandatory as the media security solution for RTP-based systems'. This conclusion could be supported by more substantial arguments in the rest of the document, especially related to SRTP, which is not mentioned apart from the brief mention in section 3, where no actual arguments are given. See also comment 2). 


5) And some nits:

- Section 7: comon -> common

- Section 7: important consider -> important to consider

- Section 7: applications -> application


Best regards,


Ray

This e-mail and its contents are subject to the DISCLAIMER at http://www.tno.nl/emaildisclaimer

_______________________________________________
Audio/Video Transport Core Maintenance
avt@ietf.org
https://www.ietf.org/mailman/listinfo/avt



-- 
Colin Perkins



--Apple-Mail=_68F96868-F70B-432B-BCAD-93A31DDF2153-- From internet-drafts@ietf.org Mon Oct 22 04:40:35 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 741B221F8BC8; Mon, 22 Oct 2012 04:40:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.532 X-Spam-Level: X-Spam-Status: No, score=-102.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pX5eTTn1U6Ck; Mon, 22 Oct 2012 04:40:34 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF8E621F8BC0; Mon, 22 Oct 2012 04:40:34 -0700 (PDT) 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.34 Message-ID: <20121022114034.11909.84117.idtracker@ietfa.amsl.com> Date: Mon, 22 Oct 2012 04:40:34 -0700 Cc: avt@ietf.org Subject: [AVTCORE] I-D Action: draft-ietf-avt-srtp-not-mandatory-10.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 11:40:35 -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 Core Maintenance Wo= rking Group of the IETF. Title : Securing the RTP Protocol Framework: Why RTP Does Not Ma= ndate a Single Media Security Solution Author(s) : Colin Perkins Magnus Westerlund Filename : draft-ietf-avt-srtp-not-mandatory-10.txt Pages : 9 Date : 2012-10-22 Abstract: This memo discusses the problem of securing real-time multimedia sessions, and explains why the Real-time Transport Protocol (RTP), and the associated RTP control protocol (RTCP), do not mandate a single media security mechanism. Guidelines for designers and reviewers of future RTP extensions are provided, to ensure that appropriate security mechanisms are mandated, and that any such mechanisms are specified in a manner that conforms with the RTP architecture. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avt-srtp-not-mandatory There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-avt-srtp-not-mandatory-10 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avt-srtp-not-mandatory-10 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From internet-drafts@ietf.org Mon Oct 22 06:18:30 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7819A21F8B90; Mon, 22 Oct 2012 06:18:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.536 X-Spam-Level: X-Spam-Status: No, score=-102.536 tagged_above=-999 required=5 tests=[AWL=0.063, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GIXmFvToQrVE; Mon, 22 Oct 2012 06:18:29 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB46E21F8BC5; Mon, 22 Oct 2012 06:18:29 -0700 (PDT) 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.34 Message-ID: <20121022131829.4538.28233.idtracker@ietfa.amsl.com> Date: Mon, 22 Oct 2012 06:18:29 -0700 Cc: avt@ietf.org Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-security-options-01.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 13:18:30 -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 Core Maintenance Wo= rking Group of the IETF. Title : Options for Securing RTP Sessions Author(s) : Magnus Westerlund Colin Perkins Filename : draft-ietf-avtcore-rtp-security-options-01.txt Pages : 28 Date : 2012-10-22 Abstract: The Real-time Transport Protocol (RTP) is used in a large number of different application domains and environments. This hetrogeneity implies that different security mechanisms are needed to provide services such as confidentiality, integrity and source authentication of RTP/RTCP packets suitable for the various environments. The range of solutions makes it difficult for RTP-based application developers to pick the most suitable mechanism. This document provides an overview of a number of security solutions for RTP, and gives guidance for developers on how to choose the appropriate security mechanism. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-security-options There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-avtcore-rtp-security-options-01 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-rtp-security-options-= 01 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From magnus.westerlund@ericsson.com Mon Oct 22 06:19:59 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98D9E21F8B32 for ; Mon, 22 Oct 2012 06:19:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.226 X-Spam-Level: X-Spam-Status: No, score=-106.226 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2xnk9n3W-qPo for ; Mon, 22 Oct 2012 06:19:59 -0700 (PDT) Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 8241D21F8A21 for ; Mon, 22 Oct 2012 06:19:58 -0700 (PDT) X-AuditID: c1b4fb30-b7f7d6d0000042ea-e1-508547fdbd8d Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 51.65.17130.DF745805; Mon, 22 Oct 2012 15:19:57 +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.279.1; Mon, 22 Oct 2012 15:19:56 +0200 Message-ID: <508547FC.4020205@ericsson.com> Date: Mon, 22 Oct 2012 15:19:56 +0200 From: Magnus Westerlund User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: avt@ietf.org References: <20121022131829.4538.28233.idtracker@ietfa.amsl.com> In-Reply-To: <20121022131829.4538.28233.idtracker@ietfa.amsl.com> X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmplluLIzCtJLcpLzFFi42KZGfG3Vveve2uAwdOLShYve1ayOzB6LFny kymAMYrLJiU1J7MstUjfLoEr42nfEfaCXcIVp86/YWlg3MffxcjJISFgIjFx5WImCFtM4sK9 9WxdjFwcQgKnGCVa5jcyQTjLGSVOndjNBlLFK6At8eLFEmYQm0VAVeL+o5csIDabgIXEzR+N QDUcHKICwRLPO4ohygUlTs58AlYiIiAgsWL7XzBbWCBQ4kjbFHaQciEBB4mW73YgYU4BR4kd t46xQ9wjKfH2/SuwTcwCehJTrrYwQtjyEs1bZ4PFhYCuaWjqYJ3AKDgLybZZSFpmIWlZwMi8 ilE4NzEzJ73cXC+1KDO5uDg/T684dRMjMCgPbvltsINx032xQ4zSHCxK4rx6qvv9hQTSE0tS s1NTC1KL4otKc1KLDzEycXBKNTAyRaVetD691ueyaelByYMvUhr+bgspvXxtWtF8jluNwQaH Ni72urLF93LiH/OM7wce3pjwbtmBN3nHTKqEmyqfGR+oWuUULqfes9OzeLrS5W2PUhb+5u8X m2p2Z6LSisKTa/4DDQpxEJtknnJ66qPVEh1n0rxYGZ6wvF9eYbKk55qiNcvZ+d+UWIozEg21 mIuKEwH2SfZaGAIAAA== Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-security-options-01.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 13:19:59 -0000 Hi WG, This version contains only minor editorial updates. The authors would appreciate a review with comments. Cheers Magnus On 2012-10-22 15:18, internet-drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Audio/Video Transport Core Maintenance Working Group of the IETF. > > Title : Options for Securing RTP Sessions > Author(s) : Magnus Westerlund > Colin Perkins > Filename : draft-ietf-avtcore-rtp-security-options-01.txt > Pages : 28 > Date : 2012-10-22 > > Abstract: > The Real-time Transport Protocol (RTP) is used in a large number of > different application domains and environments. This hetrogeneity > implies that different security mechanisms are needed to provide > services such as confidentiality, integrity and source authentication > of RTP/RTCP packets suitable for the various environments. The range > of solutions makes it difficult for RTP-based application developers > to pick the most suitable mechanism. This document provides an > overview of a number of security solutions for RTP, and gives > guidance for developers on how to choose the appropriate security > mechanism. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-security-options > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-avtcore-rtp-security-options-01 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-rtp-security-options-01 > > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > Audio/Video Transport Core Maintenance > avt@ietf.org > https://www.ietf.org/mailman/listinfo/avt > > -- 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 internet-drafts@ietf.org Mon Oct 22 08:08:26 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 544CF21F8C4D; Mon, 22 Oct 2012 08:08:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.532 X-Spam-Level: X-Spam-Status: No, score=-102.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I9UzZDxxP9ao; Mon, 22 Oct 2012 08:08:25 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0CEF21F8C52; Mon, 22 Oct 2012 08:08:25 -0700 (PDT) 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.34 Message-ID: <20121022150825.29482.25024.idtracker@ietfa.amsl.com> Date: Mon, 22 Oct 2012 08:08:25 -0700 Cc: avt@ietf.org Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-multi-media-rtp-session-01.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 15:08:26 -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 Core Maintenance Wo= rking Group of the IETF. Title : Multiple Media Types in an RTP Session Author(s) : Magnus Westerlund Colin Perkins Jonathan Lennox Filename : draft-ietf-avtcore-multi-media-rtp-session-01.txt Pages : 19 Date : 2012-10-22 Abstract: This document specifies how an RTP session can contain media streams with media from multiple media types such as audio, video, and text. This has been restricted by the RTP Specification, and thus this document updates RFC 3550 and RFC 3551 to enable this behavior for applications that satisfy the applicability for using multiple media types in a single RTP session. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avtcore-multi-media-rtp-session There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-avtcore-multi-media-rtp-session-01 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-multi-media-rtp-sessi= on-01 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From magnus.westerlund@ericsson.com Mon Oct 22 08:14:18 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04D9921F8894 for ; Mon, 22 Oct 2012 08:14:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.227 X-Spam-Level: X-Spam-Status: No, score=-106.227 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VhCM5i+pukVP for ; Mon, 22 Oct 2012 08:14:17 -0700 (PDT) Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id C3FA221F87DF for ; Mon, 22 Oct 2012 08:14:16 -0700 (PDT) X-AuditID: c1b4fb25-b7f956d0000011c3-c0-508562c7ed20 Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 32.B0.04547.7C265805; Mon, 22 Oct 2012 17:14:15 +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.279.1; Mon, 22 Oct 2012 17:14:14 +0200 Message-ID: <508562C6.4040902@ericsson.com> Date: Mon, 22 Oct 2012 17:14:14 +0200 From: Magnus Westerlund User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: avt@ietf.org References: <20121022150825.29482.25024.idtracker@ietfa.amsl.com> In-Reply-To: <20121022150825.29482.25024.idtracker@ietfa.amsl.com> X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpiluLIzCtJLcpLzFFi42KZGfG3Vvd4UmuAwfELahYve1ayOzB6LFny kymAMYrLJiU1J7MstUjfLoEro//MAZaCt0IVjdfXsjcw3uXrYuTkkBAwkbg27wE7hC0mceHe erYuRi4OIYFTjBLfFv5mgXCWM0p8ev8UKMPBwSugLXG/wRrEZBFQldiyNBWkl03AQuLmj0aw ClGBYInnHcUgYV4BQYmTM5+wgNgiAgISK7b/ZQEpERYIkZj2LxYkLCTgKHHiaQdYmFPASWJX tzPEMZISb9+/YgaxmQX0JKZcbWGEsOUlmrfOZoZo1ZZoaOpgncAoOAvJsllIWmYhaVnAyLyK UTg3MTMnvdxIL7UoM7m4OD9Przh1EyMwHA9u+a26g/HOOZFDjNIcLErivNZb9/gLCaQnlqRm p6YWpBbFF5XmpBYfYmTi4JRqYDQPOHr266q0Cxvz1u7YevZraf+KrX5859TnHNIxF194trrK KyHJOK8r03HnSts9Pg9XbJux3VrX5+K8C2HnfDUWvVhz9M7VU9anC2vmuHzfYfXhu3ntuuUN vv7T9I9pz9bXaFu96+bKCLE9upIpFtqt0rPunIkNnXU9yvd5q/GVmnNagaYz391UYinOSDTU Yi4qTgQAUV2LvBUCAAA= Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-multi-media-rtp-session-01.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 15:14:18 -0000 WG, (As author) This updates makes three significant changes: - Updates also RFC 3551 - Expandes on the RTCP bandwidth issues * Note solution is still an open issue - Add a proposal for XOR based FEC handling in this context. Cheers Magnus On 2012-10-22 17:08, internet-drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Audio/Video Transport Core Maintenance Working Group of the IETF. > > Title : Multiple Media Types in an RTP Session > Author(s) : Magnus Westerlund > Colin Perkins > Jonathan Lennox > Filename : draft-ietf-avtcore-multi-media-rtp-session-01.txt > Pages : 19 > Date : 2012-10-22 > > Abstract: > This document specifies how an RTP session can contain media streams > with media from multiple media types such as audio, video, and text. > This has been restricted by the RTP Specification, and thus this > document updates RFC 3550 and RFC 3551 to enable this behavior for > applications that satisfy the applicability for using multiple media > types in a single RTP session. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-avtcore-multi-media-rtp-session > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-avtcore-multi-media-rtp-session-01 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-multi-media-rtp-session-01 > > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > Audio/Video Transport Core Maintenance > avt@ietf.org > https://www.ietf.org/mailman/listinfo/avt > > -- 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 magnus.westerlund@ericsson.com Mon Oct 22 08:31:36 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FF7B21F8697 for ; Mon, 22 Oct 2012 08:31:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.227 X-Spam-Level: X-Spam-Status: No, score=-106.227 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WjPlQArlMGeG for ; Mon, 22 Oct 2012 08:31:33 -0700 (PDT) Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 5DF8821F8C12 for ; Mon, 22 Oct 2012 08:31:30 -0700 (PDT) X-AuditID: c1b4fb2d-b7fea6d000002ccb-c3-508566d0d82b Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 8D.F2.11467.0D665805; Mon, 22 Oct 2012 17:31:29 +0200 (CEST) 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.279.1; Mon, 22 Oct 2012 17:31:29 +0200 Message-ID: <508566CF.3010503@ericsson.com> Date: Mon, 22 Oct 2012 17:31:27 +0200 From: Magnus Westerlund User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: IETF AVTCore WG References: <20121022152200.10065.7482.idtracker@ietfa.amsl.com> In-Reply-To: <20121022152200.10065.7482.idtracker@ietfa.amsl.com> X-Enigmail-Version: 1.4.5 X-Forwarded-Message-Id: <20121022152200.10065.7482.idtracker@ietfa.amsl.com> Content-Type: multipart/mixed; boundary="------------040309010009090903020106" X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrBKsWRmVeSWpSXmKPExsUyM+Jvre7FtNYAgxmtnBYve1ayOzB6LFny kymAMYrLJiU1J7MstUjfLoEr49maK+wFD7Qqdr+cwtTAeFmli5GTQ0LAROL10qOMELaYxIV7 69lAbCGBU4wSC/fwdDFyAdnLGSX+rT/GCpLgFdCWaDn8lB3EZhFQlVg9q5sJxGYTsJC4+aMR qJmDQ1QgWOJ5RzFEuaDEyZlPWEBsEQEliR2TtjGD2MICiRLvrn5hh9jlIHH3znWw8ZwCjhId n7+zQtwjKfH2/StmCNtHYueU7WBzmAUCJGYcv8YI0ast0dDUwTqBUXAWknWzkJRB2JoSrdt/ s0PY8hLb385hhrDrJDr+3WTBFJ/BKPHymu4ssPd3MUpcOraEBcLZyCix98pvplnQwHt6uxfM FhLYzSixbK0URNEERomlb1axQxRpSMxYeYERIrEdGJL9n1ggOqYySrR98JwFDDGQ+9bv0odY rS2xbOFrsDPYBBQkXn1cCTZHREBF4tGxx6wQNeISNz7+BRsjLBAnsWPRWUaIXSLAUH3IPAsa m51Pf7JDgsVBovHYazAbFGkNy09C1XSzS2xs4YA4R1Xiw+WDUDfbSNw9egjKdpG4+nk5lK0j 8WbibCbkoF7AKL+KUTg3MTMnvdxQL7UoM7m4OD9Przh1EyMwdR7c8lt3B+OpcyKHGKU5WJTE ebmS9vsLCaQnlqRmp6YWpBbFF5XmpBYfYmTi4JRqYFQLiTx+W64qz7tq+27960kCZvFX9ph3 if7Tjrk8qaP47f32/HnyyysDrlwW8f/yN+WG6eSD4isjPyQ3B+1TERS6vW/x0gq2FcfjfRp1 fNkY72heZqh0+7++z734lhOnWWv8tqX87LYPH3HsTm1wrWf7+PasU5zDFda8XwzrJtfF+5ff nD5plhJLcUaioRZzUXEiAJe3CU1rAwAA Subject: [AVTCORE] Fwd: New Version Notification for draft-westerlund-avtcore-transport-multiplexing-04.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 15:31:36 -0000 --------------040309010009090903020106 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit WG, (As individual) We have now submitted an update to the multiplexing of multiple RTP sessions over a single transport (SHIM). The changes in this version are: - Making the SHIM 2 bytes, pre-fixed and it include a fixed pattern for STUN and DTLS separation. - Propose that we do some key-derivation for different RTP sessions so that a single key-management sequence can key all the session when doing DTLS-SRTP. The signaling solution in this draft has not been improved yet, we are awaiting resolution of the BUNDLE discussion in MMUSIC to better understand what path is selected and how to interact with that solution and take the raised concerns into account. We have now discussed this proposal for some time and it appears clear that it targets a useful combination of trade-offs. We authors would like to request WG adoption of this proposal. Cheers Magnus --------------040309010009090903020106 Content-Type: message/rfc822; name="New Version Notification for draft-westerlund-avtcore-transport-multiplexing-04_txt.eml" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename*0="New Version Notification for draft-westerlund-avtcore-transp"; filename*1="ort-multiplexing-04_txt.eml" Received: from esessmw0247.eemea.ericsson.se (153.88.115.93) by ESESSHC013.ericsson.se (153.88.183.57) with Microsoft SMTP Server (TLS) id 14.2.318.1; Mon, 22 Oct 2012 17:22:11 +0200 Received: from sesbmg10.ericsson.net (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.95) with Microsoft SMTP Server id 8.3.279.1; Mon, 22 Oct 2012 17:22:03 +0200 X-AuditID: c1b4fb3c-b7f716d0000068ad-1d-5085649a4482 Received: from mail.ietf.org (mail.ietf.org [64.170.98.30]) by sesbmg10.ericsson.net (Symantec Mail Security) with SMTP id B9.2B.26797.A9465805; Mon, 22 Oct 2012 17:22:02 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A386A21F8C11; Mon, 22 Oct 2012 08:22:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZunkXrOpQr8P; Mon, 22 Oct 2012 08:22:01 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFAC621F8C3A; Mon, 22 Oct 2012 08:22:00 -0700 (PDT) Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: To: CC: Subject: New Version Notification for draft-westerlund-avtcore-transport-multiplexing-04.txt X-Test-IDTracker: no X-IETF-IDTracker: 4.34 Message-ID: <20121022152200.10065.7482.idtracker@ietfa.amsl.com> Date: Mon, 22 Oct 2012 08:22:00 -0700 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrIIsWRWlGSWpSXmKPExsXisCpJTndWSmuAwc5TBhaX1t9jcmD0+PX1 KlsAYxSXTUpqTmZZapG+XQJXxptde5kLdnFVnGn9xtrA2MHRxcjJISFgIvH0di8ThC0mceHe erYuRi4OIYGdjBJTJj1kgXAmMUq8erSXEaJKQ2LGygtgtpDAdkaJjcsLIezpjBLvPhWB2LwC ghInZz4BaubgYBbQlFi/Sx8kzCygLbFs4WtmEJtNQE5i9atpYGNEBJQkbrc8gCoXlejcwgUS FhaIk9ix6CzUVhGJd1cfMsPc2fn0JzvEJgeJxmOvwWwWAVWJhuUnmScwCs1CcsQshCNmITli ASPzKkbR4tTipNx0QwO91KLM5OLi/Dy9vNSSTYzAcD245bfNDsaHTwwPMUpyMCmJ8goktAYI 8SXlp1RmJBZnxBeV5qQWH2KU5mBREufNfW0SICSQnliSmp2aWpBaBJOV4eBQkuBdkwzUKViU mp5akZaZU4KQZuLgPMQowcGjJMK7FKSGt7ggMbc4Mx0if4pRUUqc9wJIQgAkkVGaB9cLi/lL jLJSwryMDAwMQjxAe3MzS1DlXzGKczAqCUOcwJOZVwI3/RXQYiagxeY8YItLEhFSUg2MtvpP Xf8mNrTGf5q+QNra1v6U8Oc60yMiBleKr7YrakU93a92R9a1wiolLiEhrFjN1915yevyEmZB 13vc05TOb733+Xwrn87HW3dSJXw8Np3M6S2oOub6xbuZ67vRn7ebP6c+2Fqm23NIUGpH+Gon 3R31Vf9W5q1a8zrrsV1Lx0SeUxbPow2VWIozEg21mIuKEwEvRSBF9AIAAA== Return-Path: internet-drafts@ietf.org X-MS-Exchange-Organization-AVStamp-Mailbox: MSFTFF;1;0;0 0 0 X-MS-Exchange-Organization-AuthSource: esessmw0247.eemea.ericsson.se X-MS-Exchange-Organization-AuthAs: Anonymous MIME-Version: 1.0 A new version of I-D, draft-westerlund-avtcore-transport-multiplexing-04.tx= t has been successfully submitted by Magnus Westerlund and posted to the IETF repository. Filename: draft-westerlund-avtcore-transport-multiplexing Revision: 04 Title: Multiple RTP Sessions on a Single Lower-Layer Transport Creation date: 2012-10-22 WG ID: Individual Submission Number of pages: 42 URL: http://www.ietf.org/internet-drafts/draft-westerlund-avtco= re-transport-multiplexing-04.txt Status: http://datatracker.ietf.org/doc/draft-westerlund-avtcore-t= ransport-multiplexing Htmlized: http://tools.ietf.org/html/draft-westerlund-avtcore-transp= ort-multiplexing-04 Diff: http://www.ietf.org/rfcdiff?url2=3Ddraft-westerlund-avtcor= e-transport-multiplexing-04 Abstract: This document specifies how multiple RTP sessions are to be multiplexed on the same lower-layer transport, e.g. a UDP flow. It discusses various requirements that have been raised and their feasibility, which results in a solution with a certain applicability. A solution is recommended and that solution is provided in more detail, including signalling and examples. = =20 The IETF Secretariat --------------040309010009090903020106-- From internet-drafts@ietf.org Mon Oct 22 14:29:12 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 238EB21F8482; Mon, 22 Oct 2012 14:29:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -98.388 X-Spam-Level: X-Spam-Status: No, score=-98.388 tagged_above=-999 required=5 tests=[AWL=-4.121, BAYES_00=-2.599, FRT_STOCK1=3.988, FRT_STOCK2=3.988, SARE_SUB_6CONS_WORD=0.356, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ewna2Fei6Lzm; Mon, 22 Oct 2012 14:29:11 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C221021F84C2; Mon, 22 Oct 2012 14:29:11 -0700 (PDT) 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.34 Message-ID: <20121022212911.14822.99642.idtracker@ietfa.amsl.com> Date: Mon, 22 Oct 2012 14:29:11 -0700 Cc: avt@ietf.org Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-clksrc-01.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 21:29:12 -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 Core Maintenance Wo= rking Group of the IETF. Title : RTP Clock Source Signalling Author(s) : Aidan Williams Kevin Gross Ray van Brandenburg Hans Stokking Filename : draft-ietf-avtcore-clksrc-01.txt Pages : 21 Date : 2012-10-22 Abstract: NTP timestamps are used by several RTP protocols for synchronisation and statistical measurement. This memo specifies SDP signalling identifying NTP timestamp clock sources and SDP signalling identifying the media clock sources in a multimedia session. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avtcore-clksrc There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-avtcore-clksrc-01 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-clksrc-01 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From gunnar.hellstrom@omnitor.se Mon Oct 22 15:15:31 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6790111E809C for ; Mon, 22 Oct 2012 15:15:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.999 X-Spam-Level: X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f0D-apaKMJxz for ; Mon, 22 Oct 2012 15:15:30 -0700 (PDT) Received: from vsp-authed-02-02.binero.net (vsp-authed02.binero.net [195.74.38.226]) by ietfa.amsl.com (Postfix) with SMTP id E518411E808D for ; Mon, 22 Oct 2012 15:15:29 -0700 (PDT) Received: from smtp01.binero.se (unknown [195.74.38.28]) by vsp-authed-02-02.binero.net (Halon Mail Gateway) with ESMTP for ; Tue, 23 Oct 2012 00:15:17 +0200 (CEST) Received: from [192.168.50.38] (h79n2fls31o933.telia.com [212.181.137.79]) (Authenticated sender: gunnar.hellstrom@omnitor.se) by smtp-04-01.atm.binero.net (Postfix) with ESMTPA id 327CD3A15D for ; Tue, 23 Oct 2012 00:15:17 +0200 (CEST) Message-ID: <5085C578.4040705@omnitor.se> Date: Tue, 23 Oct 2012 00:15:20 +0200 From: =?ISO-8859-1?Q?Gunnar_Hellstr=F6m?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: avt@ietf.org References: <20121022150825.29482.25024.idtracker@ietfa.amsl.com> <508562C6.4040902@ericsson.com> In-Reply-To: <508562C6.4040902@ericsson.com> Content-Type: multipart/alternative; boundary="------------030407080200050407000305" Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-multi-media-rtp-session-01.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 22:15:31 -0000 This is a multi-part message in MIME format. --------------030407080200050407000305 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit This looks good. A couple of questions: 1. In 5.6, XOR-based FEC, it is said: "unless the FEC data is carried in RTP Payload for Redundant Audio Data [RFC2198] which has another set of restrictions." I assume that it is the restrictions described in section 7.2, last paragraph you mean. I suggest that you add that reference so that the sentence becomes: " unless the FEC data is carried in RTP Payload for Redundant Audio Data [RFC2198] which has another set of restrictions described in section 7.2." It also takes a bit of analyzing if the restrictions are valid for plain original use of RFC 2198 with simple redundancy of one codec payload type, or if it is just for the FEC data carried by RFC 2198 redundancy. ( The "which" after RFC2198 can refer to either RFC2198 or the combination). My deduction is that it is only the FEC-RFC2198 combination that has restrictions. I suggest that that is made more clear by further modification of the same sentence to become: "unless the FEC data is carried in RTP Payload for Redundant Audio Data [RFC2198]. That case has another set of restrictions described in section 7.2." 2. This sentence in section 5.1 is very limiting for the usability of this draft: "The second important consideration is that all media flows to be sent within a single RTP session need to have similar bandwidth." It is further discussed in section 6.4. I have no hint on this. I just hope that you can find a good solution to release this limitation. Very few multimedia session have similar bandwidth requirements for video, audio and text. /Gunnar On 2012-10-22 17:14, Magnus Westerlund wrote: > WG, > > (As author) > > This updates makes three significant changes: > > - Updates also RFC 3551 > - Expandes on the RTCP bandwidth issues > * Note solution is still an open issue > - Add a proposal for XOR based FEC handling in this context. > > Cheers > > Magnus > > > On 2012-10-22 17:08, internet-drafts@ietf.org wrote: >> A New Internet-Draft is available from the on-line Internet-Drafts directories. >> This draft is a work item of the Audio/Video Transport Core Maintenance Working Group of the IETF. >> >> Title : Multiple Media Types in an RTP Session >> Author(s) : Magnus Westerlund >> Colin Perkins >> Jonathan Lennox >> Filename : draft-ietf-avtcore-multi-media-rtp-session-01.txt >> Pages : 19 >> Date : 2012-10-22 >> >> Abstract: >> This document specifies how an RTP session can contain media streams >> with media from multiple media types such as audio, video, and text. >> This has been restricted by the RTP Specification, and thus this >> document updates RFC 3550 and RFC 3551 to enable this behavior for >> applications that satisfy the applicability for using multiple media >> types in a single RTP session. >> >> >> The IETF datatracker status page for this draft is: >> https://datatracker.ietf.org/doc/draft-ietf-avtcore-multi-media-rtp-session >> >> There's also a htmlized version available at: >> http://tools.ietf.org/html/draft-ietf-avtcore-multi-media-rtp-session-01 >> >> A diff from the previous version is available at: >> http://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-multi-media-rtp-session-01 >> >> >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >> >> _______________________________________________ >> Audio/Video Transport Core Maintenance >> avt@ietf.org >> https://www.ietf.org/mailman/listinfo/avt >> >> > --------------030407080200050407000305 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
This looks good.

A couple of questions:

1. In 5.6, XOR-based FEC, it is said:
"unless the FEC data is carried in RTP Payload for Redundant Audio Data [RFC2198] which has another set of restrictions."
I assume that it is the restrictions described in section 7.2, last paragraph you mean. I suggest that you add that reference so that the sentence becomes:

" unless the FEC data is carried in RTP Payload for Redundant Audio Data [RFC2198] which has another set of restrictions described in section 7.2."

It also takes a bit of analyzing if the restrictions are valid for plain original use of RFC 2198 with simple redundancy of one codec payload type, or if it is just for the FEC data carried by RFC 2198 redundancy. ( The "which" after RFC2198 can refer to either RFC2198 or the combination).  My deduction is that it is only the FEC-RFC2198 combination that has restrictions.
I suggest that that is made more clear by further modification of the same sentence to become:
 
"unless the FEC data is carried in RTP Payload for Redundant Audio Data [RFC2198]. That case has another set of restrictions described in section 7.2."


2. This sentence in section 5.1 is very limiting for the usability of this draft:
"The second important consideration is that all media flows to be sent within a single RTP
 session need to have similar bandwidth."
It is further discussed in section 6.4. 
I have no hint on this. I just hope that you can find a good solution to release this limitation. 
Very few multimedia session have similar bandwidth requirements for video, audio and text.

/Gunnar

On 2012-10-22 17:14, Magnus Westerlund wrote:
WG,

(As author)

This updates makes three significant changes:

- Updates also RFC 3551
- Expandes on the RTCP bandwidth issues
   * Note solution is still an open issue
- Add a proposal for XOR based FEC handling in this context.

Cheers

Magnus


On 2012-10-22 17:08, internet-drafts@ietf.org wrote:

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Audio/Video Transport Core Maintenance Working Group of the IETF.

	Title           : Multiple Media Types in an RTP Session
	Author(s)       : Magnus Westerlund
                          Colin Perkins
                          Jonathan Lennox
	Filename        : draft-ietf-avtcore-multi-media-rtp-session-01.txt
	Pages           : 19
	Date            : 2012-10-22

Abstract:
   This document specifies how an RTP session can contain media streams
   with media from multiple media types such as audio, video, and text.
   This has been restricted by the RTP Specification, and thus this
   document updates RFC 3550 and RFC 3551 to enable this behavior for
   applications that satisfy the applicability for using multiple media
   types in a single RTP session.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-avtcore-multi-media-rtp-session

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-avtcore-multi-media-rtp-session-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-multi-media-rtp-session-01


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
Audio/Video Transport Core Maintenance
avt@ietf.org
https://www.ietf.org/mailman/listinfo/avt

--------------030407080200050407000305-- From internet-drafts@ietf.org Mon Oct 22 15:16:25 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44AAB1F0C59; Mon, 22 Oct 2012 15:16:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x8B9c8IY0gFU; Mon, 22 Oct 2012 15:16:24 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEEC21F042B; Mon, 22 Oct 2012 15:16:24 -0700 (PDT) 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.34 Message-ID: <20121022221624.7138.24306.idtracker@ietfa.amsl.com> Date: Mon, 22 Oct 2012 15:16:24 -0700 Cc: avt@ietf.org Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circuit-breakers-01.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 22:16:25 -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 Core Maintenance Wo= rking Group of the IETF. Title : RTP Congestion Control: Circuit Breakers for Unicast Ses= sions Author(s) : Colin Perkins Varun Singh Filename : draft-ietf-avtcore-rtp-circuit-breakers-01.txt Pages : 16 Date : 2012-10-22 Abstract: The Real-time Transport Protocol (RTP) is widely used in telephony, video conferencing, and telepresence applications. Such applications are often run on best-effort UDP/IP networks. If congestion control is not implemented in the applications, then network congestion will deteriorate the user's multimedia experience. This document does not propose a congestion control algorithm; rather, it defines a minimal set of "circuit-breakers". Circuit-breakers are conditions under which an RTP flow is expected to stop transmitting media to protect the network from excessive congestion. It is expected that all RTP applications running on best-effort networks will be able to run without triggering these circuit breakers in normal operation. Any future RTP congestion control specification is expected to operate within the envelope defined by these circuit breakers. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-circuit-breakers There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-avtcore-rtp-circuit-breakers-01 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-rtp-circuit-breakers-= 01 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From internet-drafts@ietf.org Mon Oct 22 15:27:15 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99BCE11E80DF; Mon, 22 Oct 2012 15:27:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iKrH52JXlfwR; Mon, 22 Oct 2012 15:27:15 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EE5C11E80BA; Mon, 22 Oct 2012 15:27:15 -0700 (PDT) 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.34 Message-ID: <20121022222715.28412.59035.idtracker@ietfa.amsl.com> Date: Mon, 22 Oct 2012 15:27:15 -0700 Cc: avt@ietf.org Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-srtp-encrypted-header-ext-03.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 22:27:15 -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 Core Maintenance Wo= rking Group of the IETF. Title : Encryption of Header Extensions in the Secure Real-Time = Transport Protocol (SRTP) Author(s) : Jonathan Lennox Filename : draft-ietf-avtcore-srtp-encrypted-header-ext-03.txt Pages : 15 Date : 2012-10-22 Abstract: The Secure Real-Time Transport Protocol (SRTP) provides authentication, but not encryption, of the headers of Real-Time Transport Protocol (RTP) packets. However, RTP header extensions may carry sensitive information for which participants in multimedia sessions want confidentiality. This document provides a mechanism, extending the mechanisms of SRTP, to selectively encrypt RTP header extensions in SRTP. This document updates RFC 3711, the Secure Real-Time Transport Protocol specification, to require that all SRTP encryption transforms specify how RTP header extensions are to be encrypted. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avtcore-srtp-encrypted-header-e= xt There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-avtcore-srtp-encrypted-header-ext-03 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-srtp-encrypted-header= -ext-03 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From jonathan@vidyo.com Mon Oct 22 15:33:26 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C741921F8566 for ; Mon, 22 Oct 2012 15:33:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.499 X-Spam-Level: X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zy4d2eBYH7Pv for ; Mon, 22 Oct 2012 15:33:26 -0700 (PDT) Received: from mxout.myoutlookonline.com (mxout.myoutlookonline.com [64.95.72.241]) by ietfa.amsl.com (Postfix) with ESMTP id 3E50921F8203 for ; Mon, 22 Oct 2012 15:33:26 -0700 (PDT) Received: from mxout.myoutlookonline.com (localhost [127.0.0.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id 979D68BEBF0 for ; Mon, 22 Oct 2012 18:33:25 -0400 (EDT) X-Virus-Scanned: by SpamTitan at mail.lan Received: from HUB012.mail.lan (unknown [10.110.2.1]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mxout.myoutlookonline.com (Postfix) with ESMTPS id 522FB8BEB1F for ; Mon, 22 Oct 2012 18:33:25 -0400 (EDT) Received: from BE235.mail.lan ([10.110.32.235]) by HUB012.mail.lan ([10.110.17.12]) with mapi; Mon, 22 Oct 2012 18:33:21 -0400 From: Jonathan Lennox To: IETF AVTCore WG Date: Mon, 22 Oct 2012 18:33:24 -0400 Thread-Topic: [AVTCORE] I-D Action: draft-ietf-avtcore-srtp-encrypted-header-ext-03.txt Thread-Index: Ac2wpT3O0erfF/fJSGKmGz/3OWJP6g== Message-ID: References: <20121022222715.28412.59035.idtracker@ietfa.amsl.com> In-Reply-To: <20121022222715.28412.59035.idtracker@ietfa.amsl.com> 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 Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-srtp-encrypted-header-ext-03.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 22:33:26 -0000 This version incorporates the changes suggested to the draft by David McGre= w during the second WGLC. All known outstanding comments have now been res= olved. On Oct 22, 2012, at 6:27 PM, wrote: >=20 > A New Internet-Draft is available from the on-line Internet-Drafts direct= ories. > This draft is a work item of the Audio/Video Transport Core Maintenance W= orking Group of the IETF. >=20 > Title : Encryption of Header Extensions in the Secure Real-Tim= e Transport Protocol (SRTP) > Author(s) : Jonathan Lennox > Filename : draft-ietf-avtcore-srtp-encrypted-header-ext-03.txt > Pages : 15 > Date : 2012-10-22 >=20 > Abstract: > The Secure Real-Time Transport Protocol (SRTP) provides > authentication, but not encryption, of the headers of Real-Time > Transport Protocol (RTP) packets. However, RTP header extensions may > carry sensitive information for which participants in multimedia > sessions want confidentiality. This document provides a mechanism, > extending the mechanisms of SRTP, to selectively encrypt RTP header > extensions in SRTP. >=20 > This document updates RFC 3711, the Secure Real-Time Transport > Protocol specification, to require that all SRTP encryption > transforms specify how RTP header extensions are to be encrypted. >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-avtcore-srtp-encrypted-header= -ext >=20 > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-avtcore-srtp-encrypted-header-ext-0= 3 >=20 > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-srtp-encrypted-head= er-ext-03 >=20 >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > Audio/Video Transport Core Maintenance > avt@ietf.org > https://www.ietf.org/mailman/listinfo/avt >=20 -- Jonathan Lennox jonathan@vidyo.com From rjsparks@nostrum.com Tue Oct 23 13:15:27 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6324D21F865E for ; Tue, 23 Oct 2012 13:15:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.6 X-Spam-Level: X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vKDTs1ghh2qn for ; Tue, 23 Oct 2012 13:15:24 -0700 (PDT) Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 82E2C21F8646 for ; Tue, 23 Oct 2012 13:15:21 -0700 (PDT) Received: from unnumerable.local (pool-173-57-93-208.dllstx.fios.verizon.net [173.57.93.208]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id q9NKFGOO039066 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 23 Oct 2012 15:15:16 -0500 (CDT) (envelope-from rjsparks@nostrum.com) Message-ID: <5086FAD4.8070301@nostrum.com> Date: Tue, 23 Oct 2012 15:15:16 -0500 From: Robert Sparks User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: draft-ietf-avt-rtp-evrc-nw@tools.ietf.org, avt@ietf.org, avtcore-chairs@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Received-SPF: pass (nostrum.com: 173.57.93.208 is authenticated by a trusted mechanism) Subject: [AVTCORE] AD Review: draft-ietf-avt-rtp-evrc-nw-07 X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Oct 2012 20:15:27 -0000 Summary: The document should be revised before IETF LC. Primary Concern: - This document needs to point to RFC6562, at least in the security considerations section and possibly in section 11. I think the reference needs to be normative. Minor Concerns and Nits: - Section 8 refers backto a "mapping" in Section 4, but it's not clear that there's a mapping there. I suggest adding a note that ToC values are taken from the value column in the table of section 4. - This sentence from Section 6.1 does not parse well: The EVRC-NW interleaved/bundled format defines an encoding capability identification flag, which is used to signal the far end of a communication session of the instantaneous local EVRC-NW wideband/ narrowband encoding capability. Would this replacement work? The EVRC-NW interleaved/bundled format defines an encoding capability identification flag, which is used to signal the current local EVRC-NW wideband/narrowband encoding capability to the far end of a communication session. - in Section 9.1.1: When this media type is used in the context of transfer over RTP, the RTP payload format specified in Section 4.1 of RFC 3558 [6] SHALL be used. In all other contexts, the file format defined in Section 8 SHALL be used. See Section 6 for details for EVRC-NW. It needs to be clearer that you are talking about Section 7 and 6 of _this_ document. I suggest saying "Section 8 of RFCXXXX" and "Section 6 of RFCXXXX" and add a note to the RFC Editor asking them to replace XXXX with the RFC number of this document. - Section 5 paragraph 1: Suggest s/in a manner consistent with/as specified in/ From bill.wu@huawei.com Wed Oct 24 03:03:06 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38E9321F8AC0 for ; Wed, 24 Oct 2012 03:03:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.758 X-Spam-Level: X-Spam-Status: No, score=-4.758 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZB9kaI7W+98u for ; Wed, 24 Oct 2012 03:03:05 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2B72521F8A6B for ; Wed, 24 Oct 2012 03:03:05 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AKX01558; Wed, 24 Oct 2012 10:03:04 +0000 (GMT) Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 24 Oct 2012 11:02:48 +0100 Received: from SZXEML402-HUB.china.huawei.com (10.82.67.32) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 24 Oct 2012 11:02:58 +0100 Received: from w53375 (10.138.41.149) by szxeml402-hub.china.huawei.com (10.82.67.32) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 24 Oct 2012 18:02:42 +0800 Message-ID: <2F72E610D19942C7936E0535A6C6791F@china.huawei.com> From: Qin Wu To: References: <20121022093101.6784.28942.idtracker@ietfa.amsl.com> Date: Wed, 24 Oct 2012 18:02:41 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: base64 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109 X-Originating-IP: [10.138.41.149] X-CFilter-Loop: Reflected Subject: Re: [AVTCORE] I-D Action: draft-wu-avtcore-multisrc-endpoint-adver-02.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2012 10:03:06 -0000 SGksIGZvbGtzOg0KV2UgaGF2ZSBzdWJtaXR0ZWQgb25lIG5ldyBkcmFmdCB0byBkaXNjdXNzIGhv dyB0byBpbmRpY2F0ZSB3aGljaCBtZWRpYQ0KIHNvdXJjZShzKSBpbiBvbmUgZ3JvdXAgb2YgbWVk aWEgc291cmNlcyBvcmlnaW5hdGluZyBmcm9tIGEgc2luZ2xlIGVuZHBvaW50IA0KaXMgcmVzcG9u c2libGUgZm9yIHNlbmRpbmcgcmVjZXB0aW9uIHJlcG9ydC4gDQpodHRwOi8vdG9vbHMuaWV0Zi5v cmcvaHRtbC9kcmFmdC13dS1hdnRjb3JlLW11bHRpc3JjLWVuZHBvaW50LWFkdmVyLTAyDQoNClRo ZSBiYXNpYyBpZGVhIGlzIHRvIA0KbyBEZWZpbmUgb25lIG5ldyBTREVTIGl0ZW0gYW5kIHVzZSBT U1JDL0NTUkMgaWRlbnRpZmllciBpbmNsdWRlZCBhdCB0aGUgYmVnaW5uaW5nIG9mIHRoZSBjaHVu aw0KdG8gaW5kaWNhdGUgdGhlIGFjdGl2ZSByZXBvcnQgc291Y2UsIA0KbyBJZiBhbHRlcm5hdGl2 ZSByZXBvcnQgc291cmNlIGlzIG5lZWRlZCwgYSBsaXN0IG9mIENhbmRpZGF0ZSByZXBvcnQgc291 cmNlIFNTUkNzIGNhbiBiZSBjYXJyaWVkIGluIHRoZSBwYXlsb2FkIG9mIHRoaXMgU0RFUyBpdGVt Lg0KbyBXaGljaCBncm91cCBvZiBtZWRpYSBzb3VyY2VzIG9yaWdpbmF0ZSBmcm9tIGEgc2luZ2xl IGVuZHBvaW50cyBjYW4gYmUgaW5kaWNhdGVkIA0KYnkgcmVxdWlyaW5nIHRoaXMgaXRlbSBzZW50 IHRvZ2V0aGVyIHdpdGggQ05BTUUgU0RFUyBpdGVtLg0KDQpSZWdhcmRzIQ0KLVFpbg0KLS0tLS0g T3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCkZyb206IDxpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmc+ DQpUbzogPGktZC1hbm5vdW5jZUBpZXRmLm9yZz4NClNlbnQ6IE1vbmRheSwgT2N0b2JlciAyMiwg MjAxMiA1OjMxIFBNDQpTdWJqZWN0OiBJLUQgQWN0aW9uOiBkcmFmdC13dS1hdnRjb3JlLW11bHRp c3JjLWVuZHBvaW50LWFkdmVyLTAyLnR4dA0KDQoNCj4gDQo+IEEgTmV3IEludGVybmV0LURyYWZ0 IGlzIGF2YWlsYWJsZSBmcm9tIHRoZSBvbi1saW5lIEludGVybmV0LURyYWZ0cyBkaXJlY3Rvcmll cy4NCj4gDQo+IA0KPiBUaXRsZSAgICAgICAgICAgOiBBZHZlcnRpc2VtZW50IGZvciBtdWx0aS1z b3VyY2UgZW5kcG9pbnQgbXVsdGlwbGV4aW5nIG11bHRpcGxlIG1lZGlhIHR5cGUgaW4gdGhlIHNh bWUgUlRQIHNlc3Npb24NCj4gQXV0aG9yKHMpICAgICAgIDogUWluIFd1DQo+ICAgICAgICAgICAg ICAgICAgICAgICAgICBSb25pIEV2ZW4NCj4gRmlsZW5hbWUgICAgICAgIDogZHJhZnQtd3UtYXZ0 Y29yZS1tdWx0aXNyYy1lbmRwb2ludC1hZHZlci0wMi50eHQNCj4gUGFnZXMgICAgICAgICAgIDog MTINCj4gRGF0ZSAgICAgICAgICAgIDogMjAxMi0xMC0yMg0KPiANCj4gQWJzdHJhY3Q6DQo+ICAg V2hlbiB0d28gZW5kcG9pbnRzIHdpdGggbXVsdGlwbGUgbWVkaWEgc291cmNlcyBhcmUgaW4gY29t bXVuaWNhdGlvbiwNCj4gICBlYWNoIG1lZGlhIHNvdXJjZSBvciBlYWNoIHJlY2VpdmVyIHdpdGhp biBlaXRoZXIgZW5kcG9pbnQgbWF5IHNlbmQgb3INCj4gICByZWNlaXZlIHJlY2VwdGlvbiByZXBv cnQgaW5kZXBlbmRlbnRseS4gIFRoaXMgbWF5IGluY3VyIGEgbG90IG9mDQo+ICAgZHVwbGljYXRl ZCByZWNlcHRpb24gcmVwb3J0IHRvIGFuZCBmcm9tIHRoZSBlbmRwb2ludCB3aXRoIG11bHRpcGxl DQo+ICAgc291cmNlcy4gIFRoaXMgZG9jdW1lbnQgZGlzY3Vzc2VzIGhvdyB0byB0YWNrbGUgdGhl c2UgcHJvYmxlbXMgYW5kDQo+ICAgcHJvcG9zZSB0aHJlZSBwaGFzZXMgZm9yIHN1cHByZXNzaW5n IHJlY2VwdGlvbiByZXBvcnRzLg0KPiANCj4gDQo+IFRoZSBJRVRGIGRhdGF0cmFja2VyIHN0YXR1 cyBwYWdlIGZvciB0aGlzIGRyYWZ0IGlzOg0KPiBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3Jn L2RvYy9kcmFmdC13dS1hdnRjb3JlLW11bHRpc3JjLWVuZHBvaW50LWFkdmVyDQo+IA0KPiBUaGVy ZSdzIGFsc28gYSBodG1saXplZCB2ZXJzaW9uIGF2YWlsYWJsZSBhdDoNCj4gaHR0cDovL3Rvb2xz LmlldGYub3JnL2h0bWwvZHJhZnQtd3UtYXZ0Y29yZS1tdWx0aXNyYy1lbmRwb2ludC1hZHZlci0w Mg0KPiANCj4gQSBkaWZmIGZyb20gdGhlIHByZXZpb3VzIHZlcnNpb24gaXMgYXZhaWxhYmxlIGF0 Og0KPiBodHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC13dS1hdnRjb3JlLW11 bHRpc3JjLWVuZHBvaW50LWFkdmVyLTAyDQo+IA0KPiANCj4gSW50ZXJuZXQtRHJhZnRzIGFyZSBh bHNvIGF2YWlsYWJsZSBieSBhbm9ueW1vdXMgRlRQIGF0Og0KPiBmdHA6Ly9mdHAuaWV0Zi5vcmcv aW50ZXJuZXQtZHJhZnRzLw0KPiANCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX18NCj4gSS1ELUFubm91bmNlIG1haWxpbmcgbGlzdA0KPiBJLUQtQW5ub3Vu Y2VAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pLWQt YW5ub3VuY2UNCj4gSW50ZXJuZXQtRHJhZnQgZGlyZWN0b3JpZXM6IGh0dHA6Ly93d3cuaWV0Zi5v cmcvc2hhZG93Lmh0bWwNCj4gb3IgZnRwOi8vZnRwLmlldGYub3JnL2lldGYvMXNoYWRvdy1zaXRl cy50eHQ= From bill.wu@huawei.com Wed Oct 24 03:06:32 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EC3021F8953 for ; Wed, 24 Oct 2012 03:06:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.759 X-Spam-Level: X-Spam-Status: No, score=-4.759 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XM8sHiQxc2zd for ; Wed, 24 Oct 2012 03:06:27 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id CBE6F21F8916 for ; Wed, 24 Oct 2012 03:06:23 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AKX01995; Wed, 24 Oct 2012 10:06:22 +0000 (GMT) Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 24 Oct 2012 11:06:11 +0100 Received: from SZXEML410-HUB.china.huawei.com (10.82.67.137) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 24 Oct 2012 11:06:21 +0100 Received: from w53375 (10.138.41.149) by szxeml410-hub.china.huawei.com (10.82.67.137) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 24 Oct 2012 18:05:25 +0800 Message-ID: <97ED0013B98A45CB8AC714949B0FC107@china.huawei.com> From: Qin Wu To: References: <20121022093311.4397.72857.idtracker@ietfa.amsl.com> Date: Wed, 24 Oct 2012 18:05:24 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: base64 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109 X-Originating-IP: [10.138.41.149] X-CFilter-Loop: Reflected Subject: Re: [AVTCORE] I-D Action: draft-wu-avtcore-multiplex-multisource-endpoint-01.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2012 10:06:32 -0000 SGksDQpXZSBoYXZlIHBvc3RlZCBvbmUgbmV3IGRyYWZ0IHRvIGRpc2N1c3MgQmFuZHdpZHRoIGFu ZCBSVENQIHRpbWluZyBpc3N1ZXMgZm9yIG11bHRpLXNvdXJjZSBlbmRwb2ludC4NCmh0dHA6Ly90 b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXd1LWF2dGNvcmUtbXVsdGlwbGV4LW11bHRpc291cmNl LWVuZHBvaW50LTAxDQoNCllvdXIgY29tbWVudHMgYW5kIHJldmlldyBhcmUgYXBwcmVjaWF0ZWQu DQoNClJlZ2FyZHMhDQotUWluDQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTog PGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZz4NClRvOiA8aS1kLWFubm91bmNlQGlldGYub3JnPg0K U2VudDogTW9uZGF5LCBPY3RvYmVyIDIyLCAyMDEyIDU6MzMgUE0NClN1YmplY3Q6IEktRCBBY3Rp b246IGRyYWZ0LXd1LWF2dGNvcmUtbXVsdGlwbGV4LW11bHRpc291cmNlLWVuZHBvaW50LTAxLnR4 dA0KDQoNCj4gDQo+IEEgTmV3IEludGVybmV0LURyYWZ0IGlzIGF2YWlsYWJsZSBmcm9tIHRoZSBv bi1saW5lIEludGVybmV0LURyYWZ0cyBkaXJlY3Rvcmllcy4NCj4gDQo+IA0KPiBUaXRsZSAgICAg ICAgICAgOiBCYW5kd2lkdGggYW5kIFJUQ1AgdGltaW5nIGlzc3VlcyBmb3IgbXVsdGktc291cmNl IGVuZHBvaW50DQo+IEF1dGhvcihzKSAgICAgICA6IFFpbiBXdQ0KPiAgICAgICAgICAgICAgICAg ICAgICAgICAgUm9uaSBFdmVuDQo+IEZpbGVuYW1lICAgICAgICA6IGRyYWZ0LXd1LWF2dGNvcmUt bXVsdGlwbGV4LW11bHRpc291cmNlLWVuZHBvaW50LTAxLnR4dA0KPiBQYWdlcyAgICAgICAgICAg OiAxNw0KPiBEYXRlICAgICAgICAgICAgOiAyMDEyLTEwLTIyDQo+IA0KPiBBYnN0cmFjdDoNCj4g ICBUaGlzIGRvY3VtZW50IGRpc2N1c3NlcyBiYW5kd2lkdGggaXNzdWVzIGFuZCBSVENQIHRpbWlu ZyBydWxlIGlzc3Vlcw0KPiAgIHRoYXQgYXJpc2Ugd2hlbiB0aGUgbXVsdGktc291cmNlIGVuZHBv aW50IG11bHRpcGxleGluZyBhbGwgdGhlIG1lZGlhDQo+ICAgdHlwZSBpbiBvbmUgUlRQIHNlc3Np b24gYW5kIGZvbGxvd3MgUkZDMzU1MCB0aW1pbmcgcnVsZXMuICBJdA0KPiAgIHByb3ZpZGVzIHJl Y29tbWVuZGF0aW9ucyBmb3IgbXVsdGktc291cmNlIGhvc3Qgc2VuZGluZyBtdWx0aXBsZSBtZWRp YQ0KPiAgIHR5cGVzIGluIHRoZSBzYW1lIHNlc3Npb24uDQo+IA0KPiANCj4gVGhlIElFVEYgZGF0 YXRyYWNrZXIgc3RhdHVzIHBhZ2UgZm9yIHRoaXMgZHJhZnQgaXM6DQo+IGh0dHBzOi8vZGF0YXRy YWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LXd1LWF2dGNvcmUtbXVsdGlwbGV4LW11bHRpc291cmNl LWVuZHBvaW50DQo+IA0KPiBUaGVyZSdzIGFsc28gYSBodG1saXplZCB2ZXJzaW9uIGF2YWlsYWJs ZSBhdDoNCj4gaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtd3UtYXZ0Y29yZS1tdWx0 aXBsZXgtbXVsdGlzb3VyY2UtZW5kcG9pbnQtMDENCj4gDQo+IEEgZGlmZiBmcm9tIHRoZSBwcmV2 aW91cyB2ZXJzaW9uIGlzIGF2YWlsYWJsZSBhdDoNCj4gaHR0cDovL3d3dy5pZXRmLm9yZy9yZmNk aWZmP3VybDI9ZHJhZnQtd3UtYXZ0Y29yZS1tdWx0aXBsZXgtbXVsdGlzb3VyY2UtZW5kcG9pbnQt MDENCj4gDQo+IA0KPiBJbnRlcm5ldC1EcmFmdHMgYXJlIGFsc28gYXZhaWxhYmxlIGJ5IGFub255 bW91cyBGVFAgYXQ6DQo+IGZ0cDovL2Z0cC5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvDQo+IA0K PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBJLUQt QW5ub3VuY2UgbWFpbGluZyBsaXN0DQo+IEktRC1Bbm5vdW5jZUBpZXRmLm9yZw0KPiBodHRwczov L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ktZC1hbm5vdW5jZQ0KPiBJbnRlcm5ldC1E cmFmdCBkaXJlY3RvcmllczogaHR0cDovL3d3dy5pZXRmLm9yZy9zaGFkb3cuaHRtbA0KPiBvciBm dHA6Ly9mdHAuaWV0Zi5vcmcvaWV0Zi8xc2hhZG93LXNpdGVzLnR4dA0KPg== From ron.even.tlv@gmail.com Wed Oct 24 05:15:34 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8BB821F8874 for ; Wed, 24 Oct 2012 05:15:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.666 X-Spam-Level: X-Spam-Status: No, score=-2.666 tagged_above=-999 required=5 tests=[AWL=-0.932, BAYES_00=-2.599, FORGED_OUTLOOK_TAGS=0.001, HTML_MESSAGE=0.001, HTML_TAG_BALANCE_BODY=1.263, J_CHICKENPOX_83=0.6, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wm+vHXSsalii for ; Wed, 24 Oct 2012 05:15:30 -0700 (PDT) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2A1D821F886D for ; Wed, 24 Oct 2012 05:15:30 -0700 (PDT) Received: by mail-wi0-f172.google.com with SMTP id hq12so3952203wib.13 for ; Wed, 24 Oct 2012 05:15:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:mime-version:content-type:x-mailer :thread-index:content-language; bh=pbl/XWCw+Pcv39tWBB0VF3Rw+9UycN+8IF6tHrWUoqQ=; b=Oc1cl4gD5CDKnHReuDWL5MBf/s/rVWOuG9iDcK0U1O+UnYdC318vWLTgjdw6+ZMqNl DW8+2/TfpwJ6Ch/8eGQFyCdBZeJ4lXifVyM8JoOkJvLlhUOH3hEQGM7rGltddj0xBi1N 8nLrbeQuClZp7IOce54IFonaW0+dL3rqhsny00R5oBE8TF8FkdyLLn7MsepqJ0TbI/Yu bLfh6BIGYvnBoBy3wx8FrQPX2wiFpQgzOJLha56pTMF8MOGRrMbGwkHPY5mte1wA6ym8 H/QBC0hWhu5CBEg64cLf2Ajn1sSu0Wg5UZY7k6YJmI6aIPjfnZ6A7+H7GWc4pwXDBgTy ac4w== Received: by 10.180.95.97 with SMTP id dj1mr5553368wib.3.1351080928969; Wed, 24 Oct 2012 05:15:28 -0700 (PDT) Received: from RoniE (bzq-79-176-243-9.red.bezeqint.net. [79.176.243.9]) by mx.google.com with ESMTPS id di7sm4612917wib.11.2012.10.24.05.15.27 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 24 Oct 2012 05:15:28 -0700 (PDT) From: "Roni Even" To: Date: Wed, 24 Oct 2012 14:13:16 +0200 Message-ID: <050401cdb1e0$f455b260$dd011720$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0505_01CDB1F1.B7DEF790" X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac2x37QpQiyojompSoudLib2NWF/gg== Content-Language: en-us Subject: [AVTCORE] draft agenda for IETF85 X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2012 12:15:34 -0000 This is a multipart message in MIME format. ------=_NextPart_000_0505_01CDB1F1.B7DEF790 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0506_01CDB1F1.B7DEF790" ------=_NextPart_001_0506_01CDB1F1.B7DEF790 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, We uploaded the draft agenda (attached here). Please review and send any comments to the chairs. Thanks, Magnus and Roni AVTCore chairs ------=_NextPart_001_0506_01CDB1F1.B7DEF790 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

We uploaded the = draft agenda (attached here). Please review and send any comments to the = chairs.

 

Thanks,

 

Magnus and = Roni

AVTCore chairs

 

 

 

------=_NextPart_001_0506_01CDB1F1.B7DEF790-- ------=_NextPart_000_0505_01CDB1F1.B7DEF790 Content-Type: text/html; name="avtcore agenda.html" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="avtcore agenda.html" Audio/Video Transport Core Maintenance (AVTCore) Working Group = Agenda

Audio/Video Transport Core Maintenance = (AVTCore) Working Group Agenda

Chairs: Magnus Westerlund , Roni = Even

Monday, 5 November 2012 at 13:00-15:00 (Grand Ballroom D)

13:00 AVTCore Status UpdateChairs
13:20 Multiple Media type in an RTP sessionColin Perkins=20
draft-ietf-avtcore-multi-media-rtp-session-01
13:40 RTP Considerations for Endpoints sending multiple = media streamsJonathan Lennox
draft-lennox-avtcore-rtp-multi-stream-01
14:00 Multi-source endpoint RTCP duplicationQin Wu
draft-wu-avtcore-multisrc-endpoint-adver-02
14:10 Bandwidth and RTCP timing issues for multi-source = endpointQin Wu
draft-wu-avtcore-multiplex-multisource-endpoint-01
14:20 Circuit Breakers for Unicast SessionsColin Perkins=20
draft-ietf-avtcore-rtp-circuit-breakers-01
14:35 Update to Recommended Codecs for the AVP RTP = ProfileTimothy Terriberry
draft-te= rriberry-avp-codecs-00
14:45 End

Thursday, 8 November 2012 at 17:30-18:30 (Salon D)

17:30 Media Multiplexing with RTP subsessionsRichard Ejzak
= draft-ejzak-avtcore-rtp-subsessions-02
17:45 RTP Clock Source SignallingKevin = Gross
draft-ietf= -avtcore-clksrc-01
17:55 RTP and Leap SecondKevin Gross
draft= -ietf-avtcore-leap-second-01
18:05 End
------=_NextPart_000_0505_01CDB1F1.B7DEF790 Content-Type: text/plain; name="avtcore agenda.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="avtcore agenda.txt" Audio/Video Transport Core Maintenance (AVTCore) Working Group =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D CHAIRS: Magnus Westerlund Roni Even AGENDA Monday, 5 November 2012 at 13:00-15:00 (Grand Ballroom D) --------------------------------------------------------- 13:00 AVTCore Status Update (Chairs, 20) 13:20 Multiple Media type in an RTP session (Colin Perkins , 20) draft-ietf-avtcore-multi-media-rtp-session-01 13:40 RTP Considerations for Endpoints sending multiple media = streams(Jonathan Lennox, 20) draft-lennox-avtcore-rtp-multi-stream-01 14:00 Multi-source endpoint RTCP duplication (Qin Wu, 10) draft-wu-avtcore-multisrc-endpoint-adver-02 14:10 Bandwidth and RTCP timing issues for multi-source endpoint(Qin = Wu, 10) draft-wu-avtcore-multiplex-multisource-endpoint-01 14:20 Circuit Breakers for Unicast Sessions (Colin Perkins , 15) draft-ietf-avtcore-rtp-circuit-breakers-01 14:35 Update to Recommended Codecs for the AVP RTP Profile(Timothy = Terriberry, 10) draft-terriberry-avp-codecs-00 14:45 End Thursday, 8 November 2012 at 17:30-18:30 (Salon D) -------------------------------------------------- 17:30 Media Multiplexing with RTP subsessions (Richard Ejzak, 15) draft-ejzak-avtcore-rtp-subsessions-02 17:45 RTP Clock Source Signalling (Kevin Gross, 10) draft-ietf-avtcore-clksrc-01 17:55 RTP and Leap Second (Kevin Gross, 10) draft-ietf-avtcore-leap-second-01 18:05 End ------=_NextPart_000_0505_01CDB1F1.B7DEF790-- From ron.even.tlv@gmail.com Wed Oct 24 15:32:55 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD00A1F0425 for ; Wed, 24 Oct 2012 15:32:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.627 X-Spam-Level: X-Spam-Status: No, score=-2.627 tagged_above=-999 required=5 tests=[AWL=-0.893, BAYES_00=-2.599, FORGED_OUTLOOK_TAGS=0.001, HTML_MESSAGE=0.001, HTML_TAG_BALANCE_BODY=1.263, J_CHICKENPOX_83=0.6, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YNy+BbMC7EQH for ; Wed, 24 Oct 2012 15:32:55 -0700 (PDT) Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by ietfa.amsl.com (Postfix) with ESMTP id D461B1F0419 for ; Wed, 24 Oct 2012 15:32:54 -0700 (PDT) Received: by mail-wi0-f170.google.com with SMTP id hm2so4760179wib.1 for ; Wed, 24 Oct 2012 15:32:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=AzAUemjCWUZa/JQdpJsgCdRRVu4RxFNHAkEfyYHpDl4=; b=S28C2reOquDNQJGbXcaRcOpUHmiJnY37c/G72pvhf/K/Qr/RIZRnuwocL7DmjJxcSN QD52bn9F8nm2KYCekDxkajehZIKqwd9JVMC4OlUdf0FFpmPamsoQ/CTXmlHezyqPHsRm 7sbzqGiBpXIEo+nCboXnVzrb6wNZtWcX3ZW/gXw2v3PgmXGKUWDW9w3/6H6UnOXif1tM VtAV3a+qnNGOF1zJ+w6J6deVQyLM71dn1jCdyTjO/r9ihEXbHKZz7+i3DS/eENxUkkRo z2QJAP7hqvR6t77/mCi55reKzvpOCgiZSlWPhPYzy1ZZj2b1BJlXpEioCp9qMa4dcR8H q8Iw== Received: by 10.180.19.73 with SMTP id c9mr5626670wie.8.1351117973925; Wed, 24 Oct 2012 15:32:53 -0700 (PDT) Received: from RoniE (bzq-79-176-243-9.red.bezeqint.net. [79.176.243.9]) by mx.google.com with ESMTPS id fp6sm6678163wib.0.2012.10.24.15.32.51 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 24 Oct 2012 15:32:52 -0700 (PDT) From: "Roni Even" To: References: In-Reply-To: Date: Thu, 25 Oct 2012 00:30:40 +0200 Message-ID: <05bd01cdb237$344f73a0$9cee5ae0$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_05BE_01CDB247.F7D906F0" X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac2x37QpQiyojompSoudLib2NWF/ggAV1q7Q Content-Language: en-us Subject: Re: [AVTCORE] draft agenda for IETF85 X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2012 22:32:56 -0000 This is a multipart message in MIME format. ------=_NextPart_000_05BE_01CDB247.F7D906F0 Content-Type: multipart/alternative; boundary="----=_NextPart_001_05BF_01CDB247.F7D906F0" ------=_NextPart_001_05BF_01CDB247.F7D906F0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, This is an updated agenda based on comments we got. Thanks Roni Even AVTCore co-chair From: Roni Even [mailto:ron.even.tlv@gmail.com] Sent: 24 October, 2012 2:13 PM To: avt@ietf.org Subject: draft agenda for IETF85 Hi, We uploaded the draft agenda (attached here). Please review and send any comments to the chairs. Thanks, Magnus and Roni AVTCore chairs ------=_NextPart_001_05BF_01CDB247.F7D906F0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

This is an updated = agenda based on comments we got.

Thanks

Roni = Even

AVTCore co-chair

 

From:= = Roni Even [mailto:ron.even.tlv@gmail.com]
Sent: 24 October, = 2012 2:13 PM
To: avt@ietf.org
Subject: draft agenda = for IETF85

 

Hi,

We uploaded the = draft agenda (attached here). Please review and send any comments to the = chairs.

 

Thanks,

 

Magnus and = Roni

AVTCore chairs

 

 

 

------=_NextPart_001_05BF_01CDB247.F7D906F0-- ------=_NextPart_000_05BE_01CDB247.F7D906F0 Content-Type: text/plain; name="avtcore agenda v2.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="avtcore agenda v2.txt" Audio/Video Transport Core Maintenance (AVTCore) Working Group =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D CHAIRS: Magnus Westerlund Roni Even AGENDA Monday, 5 November 2012 at 13:00-15:00 (Grand Ballroom D) --------------------------------------------------------- 13:00 AVTCore Status Update (Chairs, 20) 13:20 Multiple Media type in an RTP session (Colin Perkins , 20) draft-ietf-avtcore-multi-media-rtp-session-01 13:40 RTP Considerations for Endpoints sending multiple media = streams(Jonathan Lennox, 20) draft-lennox-avtcore-rtp-multi-stream-01 14:00 Multi-source endpoint RTCP duplication (Qin Wu, 10) draft-wu-avtcore-multisrc-endpoint-adver-02 14:10 Bandwidth and RTCP timing issues for multi-source endpoint(Qin = Wu, 10) draft-wu-avtcore-multiplex-multisource-endpoint-01 14:20 Circuit Breakers for Unicast Sessions (Colin Perkins , 15) draft-ietf-avtcore-rtp-circuit-breakers-01 14:35 Guidelines for Choosing RTP CNAMEs (Eric Rescorla, 10) draft-rescorla-avtcore-6222bis-00 14:45 End Thursday, 8 November 2012 at 17:30-18:30 (Salon D) -------------------------------------------------- 17:30 Media Multiplexing with RTP subsessions (Richard Ejzak, 15) draft-ejzak-avtcore-rtp-subsessions-02 17:45 Multiple RTP Session on a Single Lower-Layer Transport(Magnus = Westerlund , 5) draft-westerlund-avtcore-transport-multiplexing-04 17:50 RTP Clock Source Signalling (Kevin Gross, 10) draft-ietf-avtcore-clksrc-01 18:00 RTP and Leap Second (Kevin Gross, 10) draft-ietf-avtcore-leap-second-01 18:10 Update to Recommended Codecs for the AVP RTP Profile(Timothy = Terriberry, 10) draft-terriberry-avp-codecs-00 18:20 End ------=_NextPart_000_05BE_01CDB247.F7D906F0 Content-Type: text/html; name="avtcore agenda v2.html" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="avtcore agenda v2.html" Audio/Video Transport Core Maintenance (AVTCore) Working Group = Agenda

Audio/Video Transport Core Maintenance = (AVTCore) Working Group Agenda

Chairs: Magnus Westerlund , Roni = Even

Monday, 5 November 2012 at 13:00-15:00 (Grand Ballroom D)

13:00 AVTCore Status UpdateChairs
13:20 Multiple Media type in an RTP sessionColin Perkins=20
draft-ietf-avtcore-multi-media-rtp-session-01
13:40 RTP Considerations for Endpoints sending multiple = media streamsJonathan Lennox
draft-lennox-avtcore-rtp-multi-stream-01
14:00 Multi-source endpoint RTCP duplicationQin Wu
draft-wu-avtcore-multisrc-endpoint-adver-02
14:10 Bandwidth and RTCP timing issues for multi-source = endpointQin Wu
draft-wu-avtcore-multiplex-multisource-endpoint-01
14:20 Circuit Breakers for Unicast SessionsColin Perkins=20
draft-ietf-avtcore-rtp-circuit-breakers-01
14:35 Guidelines for Choosing RTP CNAMEsEric Rescorla
draft= -rescorla-avtcore-6222bis-00
14:45 End

Thursday, 8 November 2012 at 17:30-18:30 (Salon D)

17:30 Media Multiplexing with RTP subsessionsRichard Ejzak
= draft-ejzak-avtcore-rtp-subsessions-02
17:45 Multiple RTP Session on a Single Lower-Layer = TransportMagnus Westerlund=20
draft-westerlund-avtcore-transport-multiplexing-04
17:50 RTP Clock Source SignallingKevin = Gross
draft-ietf= -avtcore-clksrc-01
18:00 RTP and Leap SecondKevin Gross
draft= -ietf-avtcore-leap-second-01
18:10 Update to Recommended Codecs for the AVP RTP = ProfileTimothy Terriberry
draft-te= rriberry-avp-codecs-00
18:20 End
------=_NextPart_000_05BE_01CDB247.F7D906F0-- From ron.even.tlv@gmail.com Thu Oct 25 06:02:21 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFDA021F8A2E for ; Thu, 25 Oct 2012 06:02:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.524 X-Spam-Level: X-Spam-Status: No, score=-3.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EHi2ae9iYSKt for ; Thu, 25 Oct 2012 06:02:21 -0700 (PDT) Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id DDCF621F8A2B for ; Thu, 25 Oct 2012 06:02:20 -0700 (PDT) Received: by mail-wg0-f44.google.com with SMTP id dr13so890615wgb.13 for ; Thu, 25 Oct 2012 06:02:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :content-language; bh=LMUwHyajsC2E+9VT2Nj7JHHd9NvYPGRez6/0Y7T8Rkg=; b=yB3RmD+6qqQWJxn7dnHWqLmQ+smlAJiwWpgFWVbXTGGwO4/Q6WixWM7yxBMmLG9Xxy Ghpy1djaHF4m5JV6fUUNv9yjVE0FkRwkMvZJO2TOJKASKjybBeS2cYhfDunGHtIwpeVO Ho8ldrfEafzE0szUxd5HQ6TtuoBm1FgVLdXyCeJgGUCE2xme9Z+gxFbV5DSCsHTiUMDL prjK70PILphU+iwtTbKLPoPZ5rxcMBqHh9qCZycwk6MOWUcGeanSglXzZeZgrjsP3Tff s22hJAHvrbaR3atWs3Mzo1PtdmvbH579vt1prvn92GXw93kdNC4SpMV7yM3ufm64sTJU dagw== Received: by 10.216.27.141 with SMTP id e13mr11801456wea.33.1351170140078; Thu, 25 Oct 2012 06:02:20 -0700 (PDT) Received: from RoniE (bzq-79-176-243-9.red.bezeqint.net. [79.176.243.9]) by mx.google.com with ESMTPS id m14sm9834124wie.8.2012.10.25.06.02.17 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 25 Oct 2012 06:02:18 -0700 (PDT) From: "Roni Even" To: "'Magnus Westerlund'" , "'IETF AVTCore WG'" References: <20121015142026.6075.9386.idtracker@ietfa.amsl.com> <507C1C7C.8080007@ericsson.com> In-Reply-To: <507C1C7C.8080007@ericsson.com> Date: Thu, 25 Oct 2012 15:00:07 +0200 Message-ID: <060c01cdb2b0$aa047720$fe0d6560$@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQI6M32XKA6s02PZ58yRt8G6WrWWbwJTqOa0lt5Z1yA= Content-Language: en-us Subject: Re: [AVTCORE] Fwd: I-D Action: draft-westerlund-avtcore-rtp-topologies-update-01.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Oct 2012 13:02:21 -0000 Hi Magnus, I read the draft so to answer the questions 1. I think the document need also to discuss the SDES behavior (CNAME must be forwarded to support the CSRC) specified in 7.2 and 7.3 of RFC 3550 for the different topologies (we had recently a discussion about using SDES messages). 2. I did not fully understand the SSRC behavior for source projecting middlebox and how it is different from the topologies in 3.5. In general the document is good starting point, the SSRC issues are discussed but need more review. I have some other comments but they are more topology specific. Roni Even As individual -----Original Message----- From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Magnus Westerlund Sent: 15 October, 2012 4:24 PM To: IETF AVTCore WG Subject: [AVTCORE] Fwd: I-D Action: draft-westerlund-avtcore-rtp-topologies-update-01.txt WG, As individual We have submitted two versions of this draft. The 00 is an XML2RFC generated version from the text present in RFC 5117. The 01 version is a first update. This focus on the RTP topologies present in the draft. The text is kind of rough, so I would suggest that you focus on the questions: - Are this the topologies the document should describe? Missing, redundant etc. - What do you think a topology discussion should contain. There will be variations over the different topologies in this document. Cheers Magnus Westerlund From Bing.He@alcatel-sbell.com.cn Mon Oct 29 22:57:17 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D064A21F8551 for ; Mon, 29 Oct 2012 22:57:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.816 X-Spam-Level: X-Spam-Status: No, score=0.816 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HTML_MESSAGE=0.001, J_BACKHAIR_51=1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LVIhSSXXtln9 for ; Mon, 29 Oct 2012 22:57:17 -0700 (PDT) Received: from cnshjsmin03.alcatel-sbell.com.cn (cnshjsmin03.alcatel-sbell.com.cn [211.144.215.47]) by ietfa.amsl.com (Postfix) with ESMTP id 1ED2621F853B for ; Mon, 29 Oct 2012 22:57:15 -0700 (PDT) X-AuditID: ac189297-b7fc36d0000051ff-57-508f6a7d236b Received: from CNSHJCASHUB03.ad4.ad.alcatel.com (Unknown_Domain [135.251.50.73]) by cnshjsmin03.alcatel-sbell.com.cn (Symantec Messaging Gateway) with SMTP id B1.D6.20991.D7A6F805; Tue, 30 Oct 2012 13:49:49 +0800 (HKT) Received: from CNSHJMBX03.ad4.ad.alcatel.com ([169.254.3.119]) by CNSHJCASHUB03.ad4.ad.alcatel.com ([135.251.50.73]) with mapi id 14.02.0283.003; Tue, 30 Oct 2012 13:57:11 +0800 From: HE Bing To: "avt@ietf.org" Thread-Topic: SRTP: Retransmission or replay attacking? How to discriminate in e2ae environment? Thread-Index: Ac22Y2h71kEi4I8zTAa8RBawufogKQ== Date: Tue, 30 Oct 2012 05:57:11 +0000 Message-ID: Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.24.143.123] Content-Type: multipart/alternative; boundary="_000_DE315914FFC19345B99B2A4B7F595ED00E426885CNSHJMBX03ad4ad_" MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupikeLIzCtJLcpLzFFi42Jp/60opVub1R9g0NVkbvGyZyW7A6PHkiU/ mQIYo7hsUlJzMstSi/TtErgybs9dz1jwRLLiQcsmxgbGe6JdjJwcEgImEt83XGWHsMUkLtxb z9bFyMUhJHCHUeLkl3nsEM5WRok356eDVbEJ6Eh0Pm9jA7FFBBQlWq99ZgSxhQViJfYuaYaK J0k0X78EZetJ7Hj8BayGRUBVYveNF0wgNq9AiMS8j/0sIDajgKzEtEf3weLMAuISt57MZ4K4 SEBiyZ7zzBC2qMTLx/9YIWwlid5bP9kg6vMlZvw8wQYxU1Di5MwnLBA1khIHV9xgmcAoPAvJ 2FlIWmYhaYGI60gs2P2JDcLWlli28DUzjH3mwGMmZPEFjOyrGBWS84ozsopzM/MMDPUSc5IT S1JzdIuTUnNy9JLzc/WS8zYxAmNojcSk6TsYd+23PMQowMGoxMO7YU1fgBBrYllxZe4hRgkO ZiUR3nzv/gAh3pTEyqrUovz4otKc1OJDjNIcLErivJmbiwOEBNKBZmenphakFsFkmTg4pRoY 1a9Ouu/zXLnko+FUrS282kLT49/P8xHa5rDzeP+fv8VPCybGxTFPWbdNXTbuKLezbpYxW2q6 +Ie/3F5qHxQUf8qlu3AHamU9XlO3KiAvqibfY49K+xomDsbNZ4J/2n9Un9i+22Cf/bmbvjb7 V5h/8TbafzzOq81c6dbT7vdJUi6v9qh+Kn2jxFKckWioxVxUnAgAAK7frJ0CAAA= Subject: [AVTCORE] SRTP: Retransmission or replay attacking? How to discriminate in e2ae environment? X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2012 05:57:17 -0000 --_000_DE315914FFC19345B99B2A4B7F595ED00E426885CNSHJMBX03ad4ad_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear all, RTP/SAVTF is adopted in WebRTC. For video stream, SRTP sender will do retransmission for the SRTP packets i= ndicated by RTCP FB NACK packets. The retransmitted SRTP packets are exactl= y identical to the original packets (one exception is Google Chrome WebRTC = use RTP header extension per RFC 5450 so that every retransmitted SRTP pack= et has different header extension from the original one) Now we see a problem in valid e2ae environment that can be simplified as be= low: A (Browser)<---(SRTP, SRTCP)--->IMS boder<---((RTP, RTCP)--->B (IMS client) Where IMS border works in RTP transparent forwarding mode with additional e= ncryption/decryption on browser side. If an A party originated packet was lost on the way from IM border to B par= ty, this packet will be marked as received in IMS border SRTP replay-check = list. Upon receipt of the RTCP FB NACK packet originated by B party, A will= resend the packet which will be discarded by IMS border when doing replay = checking job. Is there any way to resolve this issue? Thanks and best regards! He Bing --_000_DE315914FFC19345B99B2A4B7F595ED00E426885CNSHJMBX03ad4ad_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear all,
 
RTP/SAVTF is adopted in WebRTC.
For video stream, SRTP sender will do retransmission for the SRTP pack= ets indicated by RTCP FB NACK packets. The retransmitted SRTP packets are e= xactly identical to the original packets (one exception is Google Chrome We= bRTC use RTP header extension per RFC 5450 so that every retransmitted SRTP packet has different header exten= sion from the original one)
 
Now we see a problem in valid e2ae environment that can be simplified = as below:
A (Browser)<---(SRTP, SRTCP)--->IMS boder<---((= RTP, RTCP)--->B (IMS client)
Where IMS border works in RTP transparent forwarding mode with additio= nal encryption/decryption on browser side.
 
If an A party originated packet was lost on the way from IM border to = B party, this packet will be marked as received in IMS border SRTP <= b>replay-check list. Upon receipt of the RTCP FB NACK packet originated= by B party, A will resend the packet which will be discarded by IMS border when doing replay checking job= .
 
Is there any way to resolve this issue?
 
Thanks and best regards!
He Bing
 
 --_000_DE315914FFC19345B99B2A4B7F595ED00E426885CNSHJMBX03ad4ad_-- From magnus.westerlund@ericsson.com Tue Oct 30 02:06:45 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 951E921F84A5 for ; Tue, 30 Oct 2012 02:06:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.249 X-Spam-Level: X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dL9UrOiOAmaM for ; Tue, 30 Oct 2012 02:06:44 -0700 (PDT) Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id D423821F849A for ; Tue, 30 Oct 2012 02:06:37 -0700 (PDT) X-AuditID: c1b4fb2d-b7f1e6d000002d2c-af-508f989bc3d4 Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 96.C7.11564.B989F805; Tue, 30 Oct 2012 10:06:35 +0100 (CET) Received: from [127.0.0.1] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.279.1; Tue, 30 Oct 2012 10:06:34 +0100 Message-ID: <508F9899.5000102@ericsson.com> Date: Tue, 30 Oct 2012 10:06:33 +0100 From: Magnus Westerlund User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: avt@ietf.org References: In-Reply-To: X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrBJMWRmVeSWpSXmKPExsUyM+Jvre7sGf0BBj09KhYve1ayOzB6LFny kymAMYrLJiU1J7MstUjfLoErY+mG8oLP/BXPps5jamB8x9PFyMkhIWAi0d20kRnCFpO4cG89 WxcjF4eQwElGid2T7rBDOMsZJR7PvcgCUsUroC3R9X4VI4jNIqAqsf7YTjYQm03AQuLmj0Yg m4NDVCBY4nlHMUS5oMTJmU/AWkUEBCRWbP8LZgsLZEscXLKPFcQWEgiROHLqGCNIK6dAqMS5 eUoQ90hKvH3/Cuw2ZgE9iSlXWxghbHmJ5q2zmSFatSUamjpYJzAKzkKybRaSlllIWhYwMq9i ZM9NzMxJLzfcxAgMvYNbfuvuYDx1TuQQozQHi5I4L1fSfn8hgfTEktTs1NSC1KL4otKc1OJD jEwcnFINjAH7GO62lFXOeTZb5Xbj/4MNK4uFrucs/6k1g/GnMM/dpqOyGQJsty+t0Ip8KcR3 1WHh+hunZnjyxl9kk2VbH3yXIXyDWfTz/sl3VirsMThixnb2kF7JywlsDPG51gVV39qk99px nvR3lHNRn5x6NonNTotjZcSEe57zN+Tl5bz76dOmw7e9UImlOCPRUIu5qDgRAAblrdwLAgAA Subject: Re: [AVTCORE] SRTP: Retransmission or replay attacking? How to discriminate in e2ae environment? X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2012 09:06:45 -0000 On 2012-10-30 06:57, HE Bing wrote: > Dear all, > > RTP/SAVTF is adopted in WebRTC. > For video stream, SRTP sender will do retransmission for the SRTP > packets indicated by RTCP FB NACK packets. The retransmitted SRTP > packets are exactly identical to the original packets (one exception is > Google Chrome WebRTC use RTP header extension per RFC 5450 so that every > retransmitted SRTP packet has different header extension from the > original one) I would like to point out that for RTP retransmission it is expected that RFC 4588 is used for the retransmitted packets. That specification exist to address the issue that retransmitting an RTP packet as an identical copy doesn't work as it destroys all the statistics and tracking of packets as well as the below SRTP replay issue. > > Now we see a problem in valid e2ae environment that can be simplified as > below: > *A* (Browser)<---(SRTP, SRTCP)--->*IMS boder*<---((RTP, RTCP)--->*B* > (IMS client) > Where IMS border works in RTP transparent forwarding mode with > additional encryption/decryption on browser side. > > If an A party originated packet was lost on the way from IM border to B > party, this packet will be *marked as received in* IMS border SRTP > *replay-check list*. Upon receipt of the RTCP FB NACK packet originated > by B party, A will resend the packet which will be *discarded* by IMS > border when doing replay checking job. > > Is there any way to resolve this issue? Use RFC 4588 retransmission payload and this issue goes away. Cheers 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 csp@csperkins.org Tue Oct 30 08:05:34 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7792E21F8582 for ; Tue, 30 Oct 2012 08:05:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.599 X-Spam-Level: X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZMts0aztMepU for ; Tue, 30 Oct 2012 08:05:33 -0700 (PDT) Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [93.93.130.6]) by ietfa.amsl.com (Postfix) with ESMTP id 96C1821F8526 for ; Tue, 30 Oct 2012 08:05:33 -0700 (PDT) Received: from [130.209.247.112] (helo=mangole.dcs.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1TTDNj-000849-Qp for avt@ietf.org; Tue, 30 Oct 2012 15:05:32 +0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1283) From: Colin Perkins In-Reply-To: <20121022221624.7138.24306.idtracker@ietfa.amsl.com> Date: Tue, 30 Oct 2012 15:05:30 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20121022221624.7138.24306.idtracker@ietfa.amsl.com> To: "avt@ietf.org WG" X-Mailer: Apple Mail (2.1283) X-BlackCat-Spam-Score: -12 X-Mythic-Debug: Threshold = On = Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circuit-breakers-01.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2012 15:05:34 -0000 A summary of the changes in this version is as follows: - Clarify that multicast congestion control is outside the scope of this = memo. - Clarify what it means for an implementation to cease transmission when = the circuit breaker fires. Specifically, the intention is that the = application will stop sending RTP data packets until the user makes an = explicit attempt to restart the call. The draft notes that RTP flows = halted by the circuit breaker should not be restarted automatically = unless the sender has received information that the congestion has = dissipated. - Add an explicit RTCP Timeout circuit breaker in Section 4.2 (this is a = revised and extended version of Section 8 of the -00 draft). Unlike the = media timeout in Section 4.1, which fires when returning RTCP RR packets = show that media isn't reaching the receiver, this circuit breaker is = triggered if RTCP packets are no longer returning to the sender. - In section 4.3, clarify when high-rate senders can back-off to a lower = rate when the circuit breaker is triggered, and when they need to cease = transmission. - Expand and clarify Section 5 about RTP circuit breakers for systems = using the RTP/AVPF profile. A sender needs to process early RTCP reports = that contain an SR/RR packet as-if they were regular RTCP reports, but = ignore early non-compound RTCP packets without an SR/RR. This allows the = use of low-overhead early RTP/AVPF feedback without triggering the RTP = circuit breaker, and so is suitable for RTP congestion control = algorithms that need to quickly report loss events in between regular = RTCP reports. - Expand and clarify Section 6 about the impact of RTCP XR, to note that = RTCP XR packets are ignored by the circuit breaker algorithm. - Expand and clarify Section 7 about the impact of ECN, to note that = reports of ECN-CE marks are treated as packet loss for the congestion = based circuit breaker, but ignored for the media timeout and RTCP = timeout circuit breakers. - Expand and clarify Section 8 on the security considerations to discuss = authentication requirements. I believe this draft is on the agenda for the AVTCORE meeting in = Atlanta, but feedback via the list is also welcome.=20 Colin On 22 Oct 2012, at 23:16, Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts = directories. > This draft is a work item of the Audio/Video Transport Core = Maintenance Working Group of the IETF. >=20 > Title : RTP Congestion Control: Circuit Breakers for = Unicast Sessions > Author(s) : Colin Perkins > Varun Singh > Filename : draft-ietf-avtcore-rtp-circuit-breakers-01.txt > Pages : 16 > Date : 2012-10-22 >=20 > Abstract: > The Real-time Transport Protocol (RTP) is widely used in telephony, > video conferencing, and telepresence applications. Such = applications > are often run on best-effort UDP/IP networks. If congestion control > is not implemented in the applications, then network congestion will > deteriorate the user's multimedia experience. This document does = not > propose a congestion control algorithm; rather, it defines a minimal > set of "circuit-breakers". Circuit-breakers are conditions under > which an RTP flow is expected to stop transmitting media to protect > the network from excessive congestion. It is expected that all RTP > applications running on best-effort networks will be able to run > without triggering these circuit breakers in normal operation. Any > future RTP congestion control specification is expected to operate > within the envelope defined by these circuit breakers. >=20 >=20 > The IETF datatracker status page for this draft is: > = https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-circuit-breakers >=20 > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-avtcore-rtp-circuit-breakers-01 >=20 > A diff from the previous version is available at: > = http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-rtp-circuit-breakers= -01 >=20 >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > Audio/Video Transport Core Maintenance > avt@ietf.org > https://www.ietf.org/mailman/listinfo/avt --=20 Colin Perkins http://csperkins.org/ From Bing.He@alcatel-sbell.com.cn Tue Oct 30 23:59:50 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B51B21F84F2 for ; Tue, 30 Oct 2012 23:59:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.892 X-Spam-Level: X-Spam-Status: No, score=-0.892 tagged_above=-999 required=5 tests=[AWL=1.708, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2W7SWD09l8px for ; Tue, 30 Oct 2012 23:59:49 -0700 (PDT) Received: from cnshjsmin03.alcatel-sbell.com.cn (cnshjsmin03.alcatel-sbell.com.cn [211.144.215.47]) by ietfa.amsl.com (Postfix) with ESMTP id B996321F84AF for ; Tue, 30 Oct 2012 23:59:48 -0700 (PDT) X-AuditID: ac189297-b7fc36d0000051ff-9f-5090ca96d37d Received: from CNSHJCASHUB03.ad4.ad.alcatel.com (Unknown_Domain [135.251.50.73]) by cnshjsmin03.alcatel-sbell.com.cn (Symantec Messaging Gateway) with SMTP id E1.F5.20991.69AC0905; Wed, 31 Oct 2012 14:52:07 +0800 (HKT) Received: from CNSHJMBX03.ad4.ad.alcatel.com ([169.254.3.119]) by CNSHJCASHUB03.ad4.ad.alcatel.com ([135.251.50.73]) with mapi id 14.02.0283.003; Wed, 31 Oct 2012 14:59:36 +0800 From: HE Bing To: Magnus Westerlund , "avt@ietf.org" Thread-Topic: [AVTCORE] SRTP: Retransmission or replay attacking? How to discriminate in e2ae environment? Thread-Index: AQHNtn3boMnPAFkVd0mJkvifgXo73JfS+5RQ Date: Wed, 31 Oct 2012 06:59:34 +0000 Message-ID: References: <508F9899.5000102@ericsson.com> In-Reply-To: <508F9899.5000102@ericsson.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.24.143.123] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprMIsWRmVeSWpSXmKPExsXS/ltRSnf6qQkBBpvuclq87FnJbnFp/T0m ByaPX1+vsnksWfKTKYApissmJTUnsyy1SN8ugStj27LzzAXPRSp+T37M1MA4RbCLkYNDQsBE 4tmfqC5GTiBTTOLCvfVsXYxcHEICdxgl9u97wQLhbGWUOPruOxtIFZuAjkTn8zYwW0QgXGL9 pR52EFtYIFti6dnJzBDxHIkjvw6xQNhGEu9mTASrZxFQldg09QMTiM0rECLx8cpWsHohgTKJ y1v7WEFsTqD551tXgdmMArIS0x7dB6tnFhCXuPVkPhPEpQISS/acZ4awRSVePv7HCmErSfTe +skGUa8ncWPqFChbW2LZwtfMEHsFJU7OfMICUS8pcXDFDZYJjGKzkKyYhaR9FpL2WUjaFzCy rGJUSM4rzsgqzs3MMzDUS8xJTixJzdEtTkrNydFLzs/VS87bxAiMqjUSk6bvYNy13/IQowAH oxIPb9Wn/gAh1sSy4srcQ4wSHMxKIrwlMyYECPGmJFZWpRblxxeV5qQWH2KU5mBREufN3Fwc ICSQDjQ7OzW1ILUIJsvEwSnVwBjc9lrPr12Ocx/HofuM3Gxtq+qtD7PH7Tj148TD7N3Pt55d JbeY8+HycxVWZRdndWby51Ztdd99XmGTu0nKWcEHF15/SbHXEWZ6815Irp2teFVbQ4JmT9Dt Tj69tRZV05QDVm+7fnhaItuqBCMz3USVQqufoTZ7vzaX7W071G1xQo/r7FkmXyWW4oxEQy3m ouJEAB7Sw6imAgAA Subject: Re: [AVTCORE] SRTP: Retransmission or replay attacking? How to discriminate in e2ae environment? X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2012 06:59:50 -0000 Thank Magnus for your quick help!=20 I found relevant statement in draft-ietf-rtcweb-rtp-usage-04.txt too. Best regards! HE Bing -----Original Message----- From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Magnu= s Westerlund Sent: Tuesday, October 30, 2012 5:07 PM To: avt@ietf.org Subject: Re: [AVTCORE] SRTP: Retransmission or replay attacking? How to dis= criminate in e2ae environment? On 2012-10-30 06:57, HE Bing wrote: > Dear all, > =20 > RTP/SAVTF is adopted in WebRTC. > For video stream, SRTP sender will do retransmission for the SRTP=20 > packets indicated by RTCP FB NACK packets. The retransmitted SRTP=20 > packets are exactly identical to the original packets (one exception=20 > is Google Chrome WebRTC use RTP header extension per RFC 5450 so that=20 > every retransmitted SRTP packet has different header extension from=20 > the original one) I would like to point out that for RTP retransmission it is expected that R= FC 4588 is used for the retransmitted packets. That specification exist to = address the issue that retransmitting an RTP packet as an identical copy do= esn't work as it destroys all the statistics and tracking of packets as wel= l as the below SRTP replay issue. > =20 > Now we see a problem in valid e2ae environment that can be simplified=20 > as > below: > *A* (Browser)<---(SRTP, SRTCP)--->*IMS boder*<---((RTP, RTCP)--->*B*=20 > (IMS client) Where IMS border works in RTP transparent forwarding mode=20 > with additional encryption/decryption on browser side. > =20 > If an A party originated packet was lost on the way from IM border to=20 > B party, this packet will be *marked as received in* IMS border SRTP=20 > *replay-check list*. Upon receipt of the RTCP FB NACK packet=20 > originated by B party, A will resend the packet which will be=20 > *discarded* by IMS border when doing replay checking job. > =20 > Is there any way to resolve this issue? Use RFC 4588 retransmission payload and this issue goes away. 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 ---------------------------------------------------------------------- _______________________________________________ Audio/Video Transport Core Maintenance avt@ietf.org https://www.ietf.org/mailman/listinfo/avt From ron.even.tlv@gmail.com Wed Oct 31 07:32:51 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F10E721F8476 for ; Wed, 31 Oct 2012 07:32:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.515 X-Spam-Level: X-Spam-Status: No, score=-3.515 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CQDyYAgetREE for ; Wed, 31 Oct 2012 07:32:50 -0700 (PDT) Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 504B221F8475 for ; Wed, 31 Oct 2012 07:32:50 -0700 (PDT) Received: by mail-ee0-f44.google.com with SMTP id d4so902835eek.31 for ; Wed, 31 Oct 2012 07:32:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:mime-version:content-type:x-mailer :thread-index:content-language; bh=OFqsuG7sS0IT6swHmU8vHWHaL6MIdsT13cJkRoAoOOM=; b=QGJmZXhVBYq2091/+3F8q4Xqwq9VE7Q4lIedcwvSe3dGS2R3sMpoIoV5m87gmjIm3Z 0CRdJUvpex4w1nDUhPZv08cdAI/c28IlPlnSAbNGz1iq5jbT48JUGxSiEH9k1IXUDStz yymzN8jMCEWlrgbig0hINIQfGvtAqesgc7lxz/gxzyeBSZhuP/JvO76kWMvOBadxNiVK MdK05HbAP7oh7wJIKN7AdhplOvNONFYFq8bY45NB1D/SKxt2+xOcVxOskXPKtEU07Gm+ HQ/oOH13f1YfOekM6vC8eKL9sJ1VIy/+EmUuraRg8Fnfr90Z3yBhGQ2vsw7pmZe5xXc9 Cqcg== Received: by 10.14.173.137 with SMTP id v9mr72894124eel.41.1351693969567; Wed, 31 Oct 2012 07:32:49 -0700 (PDT) Received: from RoniE (bzq-79-182-208-105.red.bezeqint.net. [79.182.208.105]) by mx.google.com with ESMTPS id g47sm8225133eeo.6.2012.10.31.07.32.47 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 31 Oct 2012 07:32:48 -0700 (PDT) From: "Roni Even" To: Date: Wed, 31 Oct 2012 16:30:37 +0200 Message-ID: <021801cdb774$4d4d18c0$e7e74a40$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0219_01CDB785.10D65DF0" X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac23dC1h2rArXrueSy6vaNAd2Fasqw== Content-Language: en-us Subject: [AVTCORE] presentations for AVTcore session X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2012 14:32:51 -0000 This is a multipart message in MIME format. ------=_NextPart_000_0219_01CDB785.10D65DF0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, Our first session is on Monday, 5 November 2012 at 13:00-15:00 (Grand Ballroom D) The chairs will be happy to get all presentations for Monday no later than Sunday (November 6th) evening so that they can upload them before our session. Thanks Roni Even AVTcore co-chair ------=_NextPart_000_0219_01CDB785.10D65DF0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

Our first session is on = Monday, 5 November 2012 at 13:00-15:00 (Grand Ballroom = D)

 <= /p>

The chairs will be happy = to get all presentations for Monday no later than Sunday (November = 6th) evening so that they can upload them before our = session.

 <= /p>

Thanks<= /p>

Roni = Even

AVTcore = co-chair

 =

 =

------=_NextPart_000_0219_01CDB785.10D65DF0-- From roni.even@mail01.huawei.com Wed Oct 31 23:16:08 2012 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40F2C21F8514; Wed, 31 Oct 2012 23:16:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.714 X-Spam-Level: X-Spam-Status: No, score=-0.714 tagged_above=-999 required=5 tests=[AWL=1.885, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i2xBpFUDhKZ1; Wed, 31 Oct 2012 23:16:07 -0700 (PDT) Received: from hwsga02-in.huaweimarine.com (hwsga02-in.huaweimarine.com [119.145.15.224]) by ietfa.amsl.com (Postfix) with ESMTP id F2AC321F8512; Wed, 31 Oct 2012 23:16:06 -0700 (PDT) Received: from szxpml203-edg.exmail.huawei.com ([172.17.1.119]) by hwsga02-in.huaweimarine.com (MOS 4.1.3-GA) with ESMTP id ADY21888; Thu, 1 Nov 2012 14:15:57 +0800 X-Mirapoint-Received-SPF: 172.17.1.119 szxpml203-edg.exmail.huawei.com 5 none X-Mirapoint-Received-SPF: 172.17.1.119 szxpml203-edg.exmail.huawei.com 5 none Received: from SZXPML404-HUB.exmail.huawei.com (10.82.67.165) by szxpml203-edg.exmail.huawei.com (172.24.2.14) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 1 Nov 2012 14:15:51 +0800 Received: from SZXPML504-MBS.exmail.huawei.com ([169.254.4.23]) by szxpml404-hub.exmail.huawei.com ([10.82.67.165]) with mapi id 14.01.0323.003; Thu, 1 Nov 2012 14:15:57 +0800 From: Roni Even To: "avt@ietf.org" Thread-Topic: Help the NomCom: Community Feedback Thread-Index: AQHNt97j4JrgNy9bZEyKGtuNqTSwvZfUgOR/ Date: Thu, 1 Nov 2012 06:15:56 +0000 Message-ID: <760B7D45D1EFF74988DBF5C2122830C205B62262@szxpml504-mbs.exmail.huawei.com> References: <20121101031318.29487.88368.idtracker@ietfa.amsl.com> In-Reply-To: <20121101031318.29487.88368.idtracker@ietfa.amsl.com> Accept-Language: en-US, zh-CN Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.24.1.63] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "payload@ietf.org" Subject: [AVTCORE] FW: Help the NomCom: Community Feedback X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2012 06:16:08 -0000 fyi ________________________________________ From: wgchairs-bounces@ietf.org [wgchairs-bounces@ietf.org] on behalf of No= mCom Chair [nomcom-chair@ietf.org] Sent: Thursday, November 01, 2012 5:13 AM To: Working Group Chairs Subject: Help the NomCom: Community Feedback The IETF Nominations Committee (NomCom) continues to seek input from the IETF Community. The NomCom would greatly appreciate any help you could provide in making members of your working group aware of ways in which they can provide valuable feedback to the NomCom. In order to ensure that your input is received in time to be useful, the NomCom needs to receive community feedback on or before Sunday, November 4. The final list of candidates (as per RFC 5680) that the NomCom is considering for open positions can be found at: https://www.ietf.org/group/nomcom/2012/input/ The NomCom will be holding office hours during IETF 85, Monday- Thursday from 1:00pm to 3:00pm in Room 305. The NomCom welcomes comments on specific individuals, as well as general feedback related to any of the positions that NomCom is considering. Note: A list of leadership positions that the NomCom is considering can be found at: https://www.ietf.org/group/nomcom/2012/ If the NomCom office hours are inconvenient for you or if you cannot attend IETF 85, the NomCom is happy to take community input via email to nomcom12@ietf.org. Additionally, the NomCom is happy to arrange a meeting outside of office hours, just send us email and we can set something up. Comments on specific candidates can also be provided to the NomCom via the web feedback tool: https://www.ietf.org/group/nomcom/2012/input/ Thank you for your help, - Matt Lepinski nomcom-chair@ietf.org=