From mailman-bounces@ietf.org  Mon Nov  1 07:54:08 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27485
	for <avt-archive@ietf.org>; Mon, 1 Nov 2004 07:54:08 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CObwF-0006Xb-G8
	for avt-archive@ietf.org; Mon, 01 Nov 2004 08:09:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COZaY-0000ji-7s
	for avt-archive@ietf.org; Mon, 01 Nov 2004 05:39:02 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: avt-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.21851.1099304155.20557.mailman@lists.ietf.org>
Date: Mon, 01 Nov 2004 05:15:55 -0500
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

**********************************************************************

NOTE WELL:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

o the IETF plenary session, o any IETF working group or portion
thereof, o the IESG, or any member thereof on behalf of the IESG, o
the IAB or any member thereof on behalf of the IAB, o any IETF mailing
list, including the IETF list itself, any working group
  or design team list, or any other list functioning under IETF
auspices,
o the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

*******************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for avt-archive@ietf.org:

List                                     Password // URL
----                                     --------  
avt@ietf.org                             afvueh    
https://www1.ietf.org/mailman/options/avt/avt-archive%40ietf.org


From avt-bounces@ietf.org  Mon Nov  1 11:46:20 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01169
	for <avt-archive@ietf.org>; Mon, 1 Nov 2004 11:46:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COfYn-0003kn-62
	for avt-archive@ietf.org; Mon, 01 Nov 2004 12:01:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COeub-0000Qn-9M; Mon, 01 Nov 2004 11:20:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COeIH-0002ZX-4h
	for avt@megatron.ietf.org; Mon, 01 Nov 2004 10:40:30 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21279
	for <avt@ietf.org>; Mon, 1 Nov 2004 10:40:27 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COeX0-0001Rt-BZ
	for avt@ietf.org; Mon, 01 Nov 2004 10:55:55 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iA1FeFR2031750 for <avt@ietf.org>; Mon, 1 Nov 2004 16:40:15 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 1 Nov 2004 16:40:15 +0100
Received: from [147.214.34.66] (research-1fd0e1.ki.sw.ericsson.se
	[147.214.34.66]) by esealnt612.al.sw.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id VJSM67K3; Mon, 1 Nov 2004 16:40:14 +0100
Message-ID: <418658DE.9080805@ericsson.com>
Date: Mon, 01 Nov 2004 16:40:14 +0100
X-Sybari-Trust: 525c8a54 bfd556f1 fc586638 00000139
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>
Subject: Re: [AVT] Updated AVT agenda for IETF 61 in Washington D.C.
References: <41826447.9060206@ericsson.com>
In-Reply-To: <41826447.9060206@ericsson.com>
Content-Type: multipart/mixed; boundary="------------000500040505080704000908"
X-OriginalArrivalTime: 01 Nov 2004 15:40:15.0040 (UTC)
	FILETIME=[14EBB400:01C4C029]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a

This is a multi-part message in MIME format.
--------------000500040505080704000908
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

Here is the hopefully final agenda for AVT.

Cheers

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com

--------------000500040505080704000908
Content-Type: text/plain;
 name="AVT-Agenda-v3.txt"
Content-Disposition: inline;
 filename="AVT-Agenda-v3.txt"
Content-Transfer-Encoding: 7bit

Audio/Video Transport Working Group

CHAIRS: Colin Perkins     <csp@csperkins.org>
        Magnus Westerlund <magnus.westerlund@ericsson.com>

Monday, 8 November 2004, 15:30-17:30
====================================

Introduction and Status Update                                 (Chairs)
         draft-ietf-avt-rtp-midi-format-06.txt                    20 min
         draft-ietf-avt-rtp-midi-guidelines-06.txt
         draft-ietf-avt-rfc2032-bis-03.txt
         draft-ietf-avt-rfc2429-bis-03.txt
         draft-basso-avt-videoconreq-02.txt
         draft-ietf-avt-audio-t140c-00.txt
         draft-ietf-avt-rfc2793bis-09.txt
         draft-ietf-avt-rfc3119bis-03.txt
         draft-finlayson-avt-mpa-robust-interoperability-01.txt
         

RTCP XR MIB                                         (Clark & Pendleton)
         draft-ietf-avt-rtcp-xr-mib-00.txt                        15 min

Open issues in RFC 2833bis                                     (Taylor)
         draft-ietf-avt-rfc2833bis-05.txt                         15 min

RTP Payload Format for JPEG 2000                                (Leung)
         draft-ietf-avt-jpeg2000-06.txt                           15 min

Far End Camera Control protocol                                  (Even)
         draft-even-avt-h224-00.txt                               15 min
         
        

Thursday, 11 November 2004, 13:00-15:00
======================================

Introduction                                                   (Chairs)
                                                                   5 min

RTP Profile for TCP Friendly Rate Control                      (Gharai)
         draft-ietf-avt-tfrc-profile-03.txt                       25 min

RTP Timestamp Usage for Variable Sample Rate Audio Codecs      (Chairs)
         draft-ietf-avt-variable-rate-audio-00.txt             (Wenger)
         Discussion on mailing list                               30 min

RTP Payload and File Format for VMR-WB                         (Ahmadi)
         draft-ietf-avt-vmr-wb-file-format-00.txt                 15 min
         draft-ietf-avt-rtp-vmr-wb-05.txt

RTP Payload Format for AMR and AMR-WB                      (Westerlund)
         draft-ietf-avt-rtp-amr-bis-00.txt                        15 min


                                 - * - 
--------------000500040505080704000908
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

--------------000500040505080704000908--



From avt-bounces@ietf.org  Tue Nov  2 05:31:47 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04231
	for <avt-archive@ietf.org>; Tue, 2 Nov 2004 05:31:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COwCC-0005t5-0E
	for avt-archive@ietf.org; Tue, 02 Nov 2004 05:47:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COvvJ-0005pZ-K4; Tue, 02 Nov 2004 05:29:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COvgD-0007s4-1f
	for avt@megatron.ietf.org; Tue, 02 Nov 2004 05:14:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03395
	for <avt@ietf.org>; Tue, 2 Nov 2004 05:14:17 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COvvF-0005aR-KM
	for avt@ietf.org; Tue, 02 Nov 2004 05:29:54 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:61556
	helo=[192.168.0.5])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1COvfe-0004pe-Fa for avt@ietf.org; Tue, 02 Nov 2004 10:13:46 +0000
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <545576F4-2868-11D9-8AB3-000A957FC5F2@csperkins.org>
References: <545576F4-2868-11D9-8AB3-000A957FC5F2@csperkins.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <DCC9A8BA-2CB7-11D9-A2E2-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] AVT at IETF 61
Date: Tue, 2 Nov 2004 10:13:37 +0000
To: avt <avt@ietf.org>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit

On 27 Oct 2004, at 23:34, Colin Perkins wrote:
> Note that the latest draft agenda has AVT scheduled for 15:30-17:30 on 
> Monday and 13:00-15:00 on Thursday. This is a change from the 
> previously announced schedule. If this causes significant problems 
> please let the chairs know immediately.

The latest draft agenda moves us back to Wednesday and Thursday 
afternoons, although the secretariat is still working out conflicts so 
this may change again.

Colin


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Tue Nov  2 07:56:51 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16051
	for <avt-archive@ietf.org>; Tue, 2 Nov 2004 07:56:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COySR-0000eV-4d
	for avt-archive@ietf.org; Tue, 02 Nov 2004 08:12:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COy5f-0000B7-Gr; Tue, 02 Nov 2004 07:48:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COy0s-0006hX-30
	for avt@megatron.ietf.org; Tue, 02 Nov 2004 07:43:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14609
	for <avt@ietf.org>; Tue, 2 Nov 2004 07:43:49 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COyFy-0000DM-7e
	for avt@ietf.org; Tue, 02 Nov 2004 07:59:27 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iA2ChlR2019335 for <avt@ietf.org>; Tue, 2 Nov 2004 13:43:47 +0100
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 2 Nov 2004 13:43:47 +0100
Received: from [147.214.34.66] (research-1fd0e1.ki.sw.ericsson.se
	[147.214.34.66]) by esealnt610.al.sw.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id VJQGTXMZ; Tue, 2 Nov 2004 13:43:45 +0100
Message-ID: <41878100.2000008@ericsson.com>
Date: Tue, 02 Nov 2004 13:43:44 +0100
X-Sybari-Trust: b71a0ef8 ad48f3dd 47c08d8f 00000179
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>
Content-Type: multipart/mixed; boundary="------------060607040206090702030907"
X-OriginalArrivalTime: 02 Nov 2004 12:43:47.0380 (UTC)
	FILETIME=[9898BF40:01C4C0D9]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 8a4bcf8f67063cac573319207fe3db35
Subject: [AVT] [Fwd: IETF Training Sessions]
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 3b8eea209b62bd15620865bc4fbef8cd

This is a multi-part message in MIME format.
--------------060607040206090702030907
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

For you attending the meeting in Washington I can recommend that 
newcommers to the IETF attend the newcommers session. Any document 
editor that hasn't pariticpated in the editors training is strongly 
encouraged to do that. For those who like to better understand the role 
and responsibility of the WG chair, gets a good introduction by the 
intro WG chair training session.

Cheers

Magnus Westerlund


--------------060607040206090702030907
Content-Type: message/rfc822;
 name="IETF Training Sessions"
Content-Disposition: inline;
 filename="IETF Training Sessions"

Received: from falcon.ericsson.se (falcon.al.sw.ericsson.se [193.180.251.52])
	by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72) id VSV74A5X;
	Mon, 1 Nov 2004 17:27:11 +0100
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by
	falcon.ericsson.se (8.12.10/8.12.10/WIREfire-1.8) with ESMTP id
	iA1GR9t5018802; Mon, 1 Nov 2004 17:27:11 +0100
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by
	megatron.ietf.org with esmtp (Exim 4.32) id 1COeQg-0007Gu-Jw;
	Mon, 01 Nov 2004 10:49:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by
	megatron.ietf.org with esmtp (Exim 4.32) id 1COcmJ-0005sD-2v;
	Mon, 01 Nov 2004 09:03:23 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C02F.A35D1980"
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org
	(8.9.1a/8.9.1a) with ESMTP id JAA04387;
	Mon, 1 Nov 2004 09:03:20 -0500 (EST)
Received: from mail.thingmagic.com ([207.31.248.245] helo=thingmagic.com) by
	ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COd1D-0007lq-Ng;
	Mon, 01 Nov 2004 09:18:48 -0500
Received: from [24.61.30.237] (account margaret HELO [192.168.2.2]) by
	thingmagic.com (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id
	183914; Mon, 01 Nov 2004 08:57:38 -0500
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
x-sender: margaret@mail.thingmagic.com
errors-to: ietf-bounces@ietf.org
x-spam-score: 0.1 (/)
list-post: <mailto:ietf@ietf.org>
list-id: IETF-Discussion <ietf.ietf.org>
x-beenthere: ietf@ietf.org
x-mailman-version: 2.1.5
Subject: IETF Training Sessions
Date: Mon, 1 Nov 2004 15:03:08 +0100
Message-ID: <p06020406bdabf1b748d6@[192.168.2.2]>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: IETF Training Sessions
Thread-Index: AcTAL6QtkmMob9E3R9G9EU8HnYYbNw==
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
From: "Margaret Wasserman" <margaret@thingmagic.com>
Sender: <ietf-bounces@ietf.org>
To: <ietf@ietf.org>
Cc: <edu-discuss@ietf.org>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4C02F.A35D1980
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Hi All,

As usual, we will be offering a number of training sessions on Sunday=20
afternoon of the upcoming IETF meeting.  These sessions are open to=20
all IETF attendees.

At IETF 61, we will be holding the following training sessions:

Sunday, November 7, 2004
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

1300-1400  Newcomer's Training -- Room TBD (Scott Bradner)

            An introduction to the IETF for new or recent IETF
            attendees.  Covers the IETF document processes, the
            structure of the IETF, and tips for new attendees to
            be successful in the IETF environment.

1300-1500  Editor's Training -- Room TBD  (Paul Hoffman)

            Training for current or aspiring IETF document
            editors.  Covers the roles and responsibilities
            of a document editor, and includes advice on
            producing a high-quality IETF specification.

1500-1700  Intro WG Chairs Training -- Room TBD  (Spencer Dawkins)

            Introductory training for new or aspiring WG
            chairs.  Covers the role and responsibilities of
            a WG chair, and includes advice on how to run a
            WG that is fair, open and productive.  This class
            is open to all IETF attendees.

1500-1700  Security Tutorial -- Room TBD  (Radia Perlman)

            All IETF attendees need to be aware of the security
            implications of our design choices.  This session
            offers a basic primer in protocol security, as well
            as advice on how to write the Security Considerations
            sections required for all IETF documents.

Please check the final agenda for room assignments.

If you have any comments or suggestions regarding these EDU Team=20
sessions, please send them to the EDU Team discussion list --=20
edu-discuss@ietf.org.

Hope to see you all in D.C.!

Margaret




_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

------_=_NextPart_001_01C4C02F.A35D1980
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7226.0">
<TITLE>IETF Training Sessions</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>

<P><FONT SIZE=3D2>Hi All,</FONT>
</P>

<P><FONT SIZE=3D2>As usual, we will be offering a number of training =
sessions on Sunday </FONT>

<BR><FONT SIZE=3D2>afternoon of the upcoming IETF meeting.&nbsp; These =
sessions are open to </FONT>

<BR><FONT SIZE=3D2>all IETF attendees.</FONT>
</P>

<P><FONT SIZE=3D2>At IETF 61, we will be holding the following training =
sessions:</FONT>
</P>

<P><FONT SIZE=3D2>Sunday, November 7, 2004</FONT>

<BR><FONT =
SIZE=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<=
/FONT>
</P>

<P><FONT SIZE=3D2>1300-1400&nbsp; Newcomer's Training -- Room TBD (Scott =
Bradner)</FONT>
</P>

<P><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; An introduction to the IETF for new or recent IETF</FONT>

<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; attendees.&nbsp; Covers the IETF document processes, the</FONT>

<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; structure of the IETF, and tips for new attendees to</FONT>

<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; be successful in the IETF environment.</FONT>
</P>

<P><FONT SIZE=3D2>1300-1500&nbsp; Editor's Training -- Room TBD&nbsp; =
(Paul Hoffman)</FONT>
</P>

<P><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; Training for current or aspiring IETF document</FONT>

<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; editors.&nbsp; Covers the roles and responsibilities</FONT>

<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; of a document editor, and includes advice on</FONT>

<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; producing a high-quality IETF specification.</FONT>
</P>

<P><FONT SIZE=3D2>1500-1700&nbsp; Intro WG Chairs Training -- Room =
TBD&nbsp; (Spencer Dawkins)</FONT>
</P>

<P><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; Introductory training for new or aspiring WG</FONT>

<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; chairs.&nbsp; Covers the role and responsibilities of</FONT>

<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; a WG chair, and includes advice on how to run a</FONT>

<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; WG that is fair, open and productive.&nbsp; This class</FONT>

<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; is open to all IETF attendees.</FONT>
</P>

<P><FONT SIZE=3D2>1500-1700&nbsp; Security Tutorial -- Room TBD&nbsp; =
(Radia Perlman)</FONT>
</P>

<P><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; All IETF attendees need to be aware of the security</FONT>

<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; implications of our design choices.&nbsp; This session</FONT>

<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; offers a basic primer in protocol security, as well</FONT>

<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; as advice on how to write the Security Considerations</FONT>

<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; sections required for all IETF documents.</FONT>
</P>

<P><FONT SIZE=3D2>Please check the final agenda for room =
assignments.</FONT>
</P>

<P><FONT SIZE=3D2>If you have any comments or suggestions regarding =
these EDU Team </FONT>

<BR><FONT SIZE=3D2>sessions, please send them to the EDU Team discussion =
list -- </FONT>

<BR><FONT SIZE=3D2>edu-discuss@ietf.org.</FONT>
</P>

<P><FONT SIZE=3D2>Hope to see you all in D.C.!</FONT>
</P>

<P><FONT SIZE=3D2>Margaret</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>_______________________________________________</FONT>

<BR><FONT SIZE=3D2>Ietf mailing list</FONT>

<BR><FONT SIZE=3D2>Ietf@ietf.org</FONT>

<BR><FONT SIZE=3D2><A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/ietf">https://www1.ietf.or=
g/mailman/listinfo/ietf</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C4C02F.A35D1980--


--------------060607040206090702030907
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

--------------060607040206090702030907--



From avt-bounces@ietf.org  Tue Nov  2 14:10:34 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29744
	for <avt-archive@ietf.org>; Tue, 2 Nov 2004 14:10:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CP4IJ-0002bi-Vk
	for avt-archive@ietf.org; Tue, 02 Nov 2004 14:26:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CP3xU-0000yq-3k; Tue, 02 Nov 2004 14:04:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CP3m1-0004Ge-3g
	for avt@megatron.ietf.org; Tue, 02 Nov 2004 13:52:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28060
	for <avt@ietf.org>; Tue, 2 Nov 2004 13:52:52 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CP417-00027u-C8
	for avt@ietf.org; Tue, 02 Nov 2004 14:08:33 -0500
Received: from alor.dcs.gla.ac.uk ([130.209.247.84]:57097)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1CP3lM-0002BS-Bd; Tue, 02 Nov 2004 18:52:12 +0000
In-Reply-To: <9D277E44D6EF0942B928C6F0DE99BB31330DD1@lan-ex-01.panasonic.de>
References: <9D277E44D6EF0942B928C6F0DE99BB31330DD1@lan-ex-01.panasonic.de>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <4A3C7975-2D00-11D9-9AD6-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: quoted-printable
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Request for WG Last-Call for
	draft-ietf-avt-rtp-3gpp-timed-text-07.txt
Date: Tue, 2 Nov 2004 18:52:05 +0000
To: "Rey Jose" <Rey@panasonic.de>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 24d000849df6f171c5ec1cca2ea21b82
Content-Transfer-Encoding: quoted-printable
Cc: "Magnus Westerlund \(KI/EAB\)" <magnus.westerlund@ericsson.com>,
        avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7118f330e2af0a096ba071c5e99ca10e
Content-Transfer-Encoding: quoted-printable

Jos=E9,

On 25 Oct 2004, at 09:32, Rey Jose wrote:
> The last update of this draft was published by the ID manager on =20
> October 8th:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-3gpp-timed-=20
> text-07.txt
>
> Comments during and after the IETF have been incorporated into -06 (in =
=20
> -07 only editorial nits were corrected using the webtool) and sent to =20=

> the list on September 10th.  No comments have followed.
>
> Additionally, the draft has already passed the 2-week review period by =
=20
> IETF-types (sent to <ietf-types@iana.org> mailing list on September =20=

> 13th).
>
> So I'd like to ask for  WGLC.

This draft is clearly not ready for working group last call. There are =20=

some significant editorial and document quality issues that obviously =20=

need to be addressed, along with a number of technical problems.

The editorial issues relate primarily to document structuring and =20
clarity of explanation. The draft is difficult to follow, confusing =20
introductory material with the payload format specification, and badly =20=

structured. You should start with an introduction, then move onto =20
background, requirements and design rationale, then terminology, then =20=

the payload format and rules for packetization, fragmentation, etc.

You need to write a simple introduction that briefly describes the =20
purpose of the document, introduces the 3GPP timed text format, and =20
outlines how the remainder of the document is structured. This could =20
comprise the first two paragraphs of the current section 2 and much of =20=

section 2.1, followed by an outline of the remainder of the document. =20=

This will be section 1 of the revised draft.

Create a new background, design rationale and requirements section. =20
This will probably have much of the text from the current section 2.1 =20=

and 2.2, and should form section 2 of the revised draft.

Review section 2.3 of the current draft, splitting it into text which =20=

is background and design rationale, and that which specifies behaviour. =20=

The text specifying behaviour should go into the payload format =20
specification section (much of the current section 2.3.3 to 2.3.6 is =20
specification, not background, since it places normative requirements =20=

on implementations). Moving this text into the payload format =20
specification may require you to restructure that section, either =20
splitting it or adding new subsections.

Move the terminology section later in the document, to form section 3 =20=

of the revised draft.

Make sure all figures are numbered and have appropriate captions, and =20=

are cross-referenced by figure number. Ensure that figures are not =20
split across page boundaries.

I believe these are the minimum set of changes needed to bring the =20
document structure into line, and to make it understandable to readers.

Moving onto the technical issues, I recommend you add two new sections =20=

to explain how this draft relates to RFC 2793 and to RFC 3640.

In section 2.2, requirement 1 is to keep the 3GP text sample structure. =20=

This is justified by stating that a receiver SHALL be able to rebuild =20=

the text samples from the received RTP packets. I agree that rebuilding =20=

the text samples is an appropriate goal, but don't see why this =20
requires the payload format to keep the 3GP text sample structure? We =20=

have other payload formats that modify the data format to optimise =20
media transport, but allow reconstruction of the original data.

In section 2.2, requirement 3 states that it may be more appropriate to =20=

send large sample descriptions in-band. What is the justification for =20=

this? In-band transmission would seem inappropriate for large =20
descriptions, since they're more likely to be affected by packet loss =20=

than smaller descriptions that fit into a single packet.

Section 2.3.3 (second bullet point on page 9) ends with "explained =20
further in this document", but doesn't say where. In this, and all =20
other similar cases, please give explicit cross-references to section =20=

or figure numbers.

Section 2.3.3 (last bullet point on page 9) mentions that "it does not =20=

seem reasonable to include such additional headers". What headers are =20=

these? The text preceding talks about intelligent fragmentation, but =20
it's not clear that this needs extra headers.

Section 2.3.4 specifies how packets are formed from samples and =20
modifiers. The rules listed in the numbered list at the start of the =20
sections allow empty packets, but the preceding text specifies that at =20=

least one unit of data must be included. Which is correct?

The first observation in section 2.3.4 (near the end of page 10) states =20=

that type 5 units may be placed anywhere in the aggregate, and SHALL =20
NOT be regarded for calculating the timestamp (indeed, they MUST be =20
ignored when calculating the timestamp). The numbered rules for =20
aggregate payload earlier in the section allow a packet that comprises =20=

only a type 5 unit. What is the RTP timestamp for such a packet, given =20=

that type 5 units MUST be ignored when calculating timestamps?

Figure 1 is unclear, please add a key explaining what is being shown, =20=

and explaining the labels. What are these particular examples chosen?

An unnumbered figure is split across the end of page 11 and the start =20=

of page 12. It's not clear if this relates to the text immediately =20
before it ("For illustrative purposes, three different...") or that =20
following. Please label the figure, and clarify from where it's =20
referenced.

Section 2.3.5 talks about the TOTAL and THIS fields, which have not =20
been defined. This discussion needs to be moved to after the =20
specification of TYPE 2, 3 and 4 headers, where these fields are =20
defined.

Section 3 starts with an unnumbered figure, which needs a figure number =20=

and caption. This shows an RTP packet without payload header which is =20=

confusing  since Figure 2 (in section 3.1) shows the presence of the =20
payload header. I suggest moving Figure 2 to the start of section 3, =20
rather than having near duplicates of the packet diagram.

Section 3 again notes that TYPE 5 units do not make use of the =20
timestamp. All RTP packets need a valid timestamp; if only TYPE 5 units =20=

are included, what value does it take?

Section 3 notes that the RTP timestamp rate is the value of the =20
"timescale" parameter in the Media Header Box. Because the timestamp =20
rate affects the synchronisation accuracy and RTCP statistics, I think =20=

this draft needs to give guidance on how that parameter is chosen when =20=

the file is constructed.

Section 3 notes that "Other timestamp clockrates MAY be used" but =20
doesn't give guidance on what are appropriate other rates. Suggest =20
adding some text to explain that the typical use is to match the 3GPP =20=

timed text clock rate to that used by an associated audio or video =20
stream, not to use some arbitrary value.

Section 3 (last paragraph on page 15) states that "no default sample =20
size of sampling rate is defined for timed text". Four paragraphs =20
earlier the draft states "A default value of 1000 Hz is RECOMMENDED" =20
for the timestamp. Which is correct?

Section 3.1 repeats the payload header format in Figures 2, 3 and 5, =20
with minor differences. A single copy is sufficient.

Section 3.1 talks about improving interoperability with RFC 3640, but =20=

doesn't explain how or why this is desirable. Suggest moving this to =20
the new section on the "Relation to RFC 3640".

In Section 3.1.1, note that the 16 bit LEN field is in network byte =20
order.

Section 3.1.2 (first bullet point) says "U, R and TYPE as defined =20
above", but doesn't say where above. It also doesn't mention LEN.

Section 3.1.2, second bullet, third paragraph mentions that transport =20=

of sample descriptions out of band is "MANDATORY". This is not the =20
right place to specify that - it confuses signalling with the details =20=

of the packet format. The capitalised term "MANDATORY" is not defined =20=

anywhere.

Section 3.1.2 (first paragraph on page 21) states that a maximum of 64 =20=

dynamic SIDX are allowed at any moment, but allows a range of 0-127. =20
Suggest either allowing 127 active values, or reducing the allowable =20
range, or adding an explanatory note to clarify.

In Section 3.1.2, SDUR has 3 bytes, since two bytes gives limited =20
maximum duration. This will be true no matter what: is it appropriate =20=

to place a fixed maximum? Or to define a way in which event duration =20
can be extended by a following packet to allow unlimited duration =20
events?

Section 3.1.2 has an "example that illustrates how units of unknown =20
duration MUST be presented". If there's a rule, it need to be defined =20=

explicitly, not by a single example.

Section 3.1.2 (top of page 22) says that "sample of unknown duration =20
SHALL NOT use features, such as scrolling or karaoke, which =20
require...". This is not sufficient: need a complete list of =20
exclusions, otherwise there's the potential for confusion.

Section 3.1.2 (top of page 22) says that only TYPE 5 units can follow =20=

units of unknown duration otherwise it's not possible to calculate the =20=

timestamp. Which timestamp does that refer to? The RTP timestamp of the =20=

packet or that (implied) for the following unit? Please clarify.

Section 3.1.2 (last two bullets) explains that the TLEN is needed by =20
the decoder to know where the modifiers in the payload start. It's not =20=

clear what this means: does the text string include modifier boxes? I =20=

thought TYPE 1 units transported text samples only, and that any =20
modifiers would be part of a TYPE 5 unit later?

Similar comment for section 3.1.3, where SLEN indicates the size of the =20=

text string plus any modifier boxes. =46rom the description earlier, it =20=

can be read that there are no modifiers and only text here?

These lead to a bigger question: lease clarify the contents of the =20
payload. Is it a single logical block, with the headers giving pointers =20=

to sub-parts of the block? Or is it multiple logical blocks (some text, =20=

some modifiers) stacked after the headers in order?

Section 3.1.3 states that LEN MUST be greater than 9. What is the =20
response to a packet where LEN <=3D 9? (similar comments apply for =20
section 3.1.4, 3.1.5 and 3.1.6)

Section 3.1.3 what should a receiver do if it receives fragments with =20=

differing SLEN values?

Sections 3.1.3, 3.1.4 and 3.1.5, what should a receiver do if it =20
receives units where THIS > TOTAL? Or if TOTAL =3D 0?

Please add some examples of complete RTP packets and their contents, =20
for several combinations of unit types, including all the headers and =20=

data.

Section 6.1 (end of page 26) expand and reference "O/A exchange".

Section 7.1 states that a receiver MUST ignore any "unspecified" =20
parameter. Can you clarify what this means? Did you intend to write =20
"unrecognised"?

Section 7.1: the definition of the "rate" parameter duplicates that =20
from section 3. Suggest referencing that definition, rather than trying =20=

to summarise it.

Section 7.1 defines a number of parameters as "16 bit integers" or as =20=

"16 bit unsigned integers". Does this mean that the parameters are in =20=

binary format? Or do you intend (as in the examples in section 8) that =20=

the decimal representation is used?

Section 8.1, last bullet point says that unknown parameters SHALL be =20
ignored. Does this mean that they're not copied into the SDP (i.e. =20
ignored by the device generating the SDP)? Or are they copied, but =20
ignored by the device that later uses the SDP? Please clarify.

--=20
Colin Perkins
http://csperkins.org/


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Tue Nov  2 14:30:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01592
	for <avt-archive@ietf.org>; Tue, 2 Nov 2004 14:30:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CP4bN-00036e-6x
	for avt-archive@ietf.org; Tue, 02 Nov 2004 14:45:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CP4ET-0001ov-BZ; Tue, 02 Nov 2004 14:22:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CP45F-0005gw-OI
	for avt@megatron.ietf.org; Tue, 02 Nov 2004 14:12:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00134
	for <avt@ietf.org>; Tue, 2 Nov 2004 14:12:44 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CP4KQ-0002eT-DS
	for avt@ietf.org; Tue, 02 Nov 2004 14:28:26 -0500
Received: from alor.dcs.gla.ac.uk ([130.209.247.84]:57236)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1CP44e-0002p5-Fc; Tue, 02 Nov 2004 19:12:08 +0000
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F038A9EEC@is0004avexu1.global.avaya.com>
References: <AAB4B3D3CF0F454F98272CBE187FDE2F038A9EEC@is0004avexu1.global.avaya.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <160F87A0-2D03-11D9-9AD6-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] questions about jitter
Date: Tue, 2 Nov 2004 19:12:06 +0000
To: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
Cc: Randell Jesup <rjesup@wgate.com>, Fangweiwei <fangweiwei@tom.com>,
        Yaakov Stein <yaakov_s@rad.com>, avt <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit

On 28 Oct 2004, at 13:52, Romascanu, Dan ((Dan)) wrote:
>>> Note that RFC 3550 RTCP defines "loss" in a very weird way;
>> it allows
>>> very
>>> late packets to not be considered "lost", and it counts
>> duplicates as
>>> multiple separate packets (so if you lose packet N, and get two of
>>> packet
>>> N+1, that's considered 0 loss!!!)  Also, since loss is based on the
>>> last
>>> packet received (packet N), if the previous packet (N-1) arrives
>>> out-of-order (but in time to be played) after the RTCP is sent, the
>>> RTCP
>>> will show that as a loss, and in the next RTCP an extra packet will
>>> be counted (and yes, this can lead to negative loss rates).
>>>
>>> So for many uses, while amusing, the RTCP data on loss (and probably
>>> jitter) is close to worthless, and certainly has to be
>> taken as at best
>>> fuzzy data.  Post-jitter data (handling late packets,
>> duplicates, etc)
>>> is
>>> more useful in most cases.  I'm sure part of the reason
>> it's defined
>>> this
>>> way is so an RTP stack can calculate the loss & jitter
>> simply without
>>> having to communicate in any way with the jitter buffer.
>>
>> And there's RFC 3611 if you need more detailed statistics.
>
> I've run into similar issues when doing RAQMON and trying to refer RFC 
> 3550 for some of the metrics to measure application QoS. At the end of 
> the day we had to define new or supplementary metrics for jitter, loss 
> and discards, and differentiate between the network and application 
> layer metrics. It looks like RFC 3550 is in need of a revision on this 
> respect.

While I agree with the problems, there's too much deployment to 
redefine the RTCP statistics in RFC 3550 now. Additional metrics can be 
conveyed, much like was done with RFC 3611, if there's a need.

-- 
Colin Perkins
http://csperkins.org/


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Tue Nov  2 14:59:40 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03955
	for <avt-archive@ietf.org>; Tue, 2 Nov 2004 14:59:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CP53p-0003iE-Ux
	for avt-archive@ietf.org; Tue, 02 Nov 2004 15:15:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CP4fG-0006ol-Gb; Tue, 02 Nov 2004 14:49:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CP4Mo-0006H9-8x
	for avt@megatron.ietf.org; Tue, 02 Nov 2004 14:30:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01627
	for <avt@ietf.org>; Tue, 2 Nov 2004 14:30:52 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CP4bx-00036j-Nz
	for avt@ietf.org; Tue, 02 Nov 2004 14:46:35 -0500
Received: from alor.dcs.gla.ac.uk ([130.209.247.84]:57276)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1CP4MH-0003ki-N0; Tue, 02 Nov 2004 19:30:21 +0000
In-Reply-To: <417FF447.90606@8x8.com>
References: <417FF447.90606@8x8.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <9D807F50-2D05-11D9-9AD6-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] draft-ietf-avt-tfrc-profile-03.txt - imbed feedback in RTP?
Date: Tue, 2 Nov 2004 19:30:12 +0000
To: Jim Kleck <jimk@8x8.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit
Cc: ladan@isi.edu, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit

Jim,

On 27 Oct 2004, at 20:17, Jim Kleck wrote:
> The draft-ietf-avt-tfrc-profile-03.txt is specifically restricted to 
> unicast,
> and specifies feedback possibly once per data packet. This can generate
> too much feedback traffic in the case of one-to-one video conferencing
> (which typically operates at 64K - 512K bps). However, this case offers
> a ready feedback path with much less overhead: the data pkts coming 
> from
> the far end. An additional extension to the RTP hdr could possibly add
> the feedback at a small cost. The challenges with this scheme are:
>
> - there is an implicit tie between the Tx and Rx RTP sessions, but in
>  a one-to-one video conference that should not be too hard to formalize
>
> - if the app does not recv any data pkts from the farend for a while 
> then
>  there will be no feedback, that could mean the far end has nothing to 
> send
>  (in which case a noop RTP pkt with the feedback could be specified,
>  see draft-wing-avt-rtp-noop-01.txt, with no worries about using extra
>  bandwidth because the lack of data makes that bandwidth available...
>  or use the suggested Receiver Report extensions), or it could mean 
> that
>  there is some network problem
>
> Does this seem worth further investigation?

It's an interesting idea, but the result is diverging quite far from 
the traditional model of RTP for data transfer, with RTCP providing 
feedback. Ideally, I think we should keep the profile-specific 
extensions to the RTP header as small as possible, keeping this new 
profile as close to standard RTP as we can.

Did you look at DCCP? That should reduce the overheads, since they 
allow ACKs to be piggybacked on data packets.

-- 
Colin Perkins
http://csperkins.org/


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov  3 08:33:36 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08192
	for <avt-archive@ietf.org>; Wed, 3 Nov 2004 08:33:36 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPLVw-0004tp-2C
	for avt-archive@ietf.org; Wed, 03 Nov 2004 08:49:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPLBS-0005lM-3h; Wed, 03 Nov 2004 08:28:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CP59Y-00074m-2a
	for avt@megatron.ietf.org; Tue, 02 Nov 2004 15:21:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06800
	for <avt@ietf.org>; Tue, 2 Nov 2004 15:21:12 -0500 (EST)
Received: from services106.cs.uwaterloo.ca ([129.97.152.164] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CP5Of-0004Gj-Rm
	for avt@ietf.org; Tue, 02 Nov 2004 15:36:55 -0500
Received: from services108.cs.uwaterloo.ca (daemon@services108.cs.uwaterloo.ca
	[129.97.152.165])
	by services106.cs.uwaterloo.ca (8.11.7/8.11.7) with ESMTP id
	iA2KL9207462 for <avt@ietf.org>; Tue, 2 Nov 2004 15:21:09 -0500 (EST)
Received: (from hyh2li@localhost)
	by services108.cs.uwaterloo.ca (8.11.7/8.11.7) id iA2KL8f08172;
	Tue, 2 Nov 2004 15:21:08 -0500 (EST)
Date: Tue, 2 Nov 2004 15:21:08 -0500 (EST)
From: Herman Li <hyh2li@cs.uwaterloo.ca>
To: avt@ietf.org
Message-ID: <Pine.GSO.4.58.0411021521030.7929@services108.cs.uwaterloo.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Miltered: at rhadamanthus by Joe's j-chkmail ("http://j-chkmail.ensmp.fr")!
X-Virus-Scanned: ClamAV 0.80rc3/568/Tue Nov  2 01:43:35 2004
	clamav-milter version 0.80c on localhost
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
X-Mailman-Approved-At: Wed, 03 Nov 2004 08:28:17 -0500
Subject: [AVT] IFIP Networking 2005: Paper submission deadline extended to
 November 15th 2004
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f

Due to numerous requests, the submission due date to the IFIP Networking
Conference has been extended until November 15th 2004

IFIP NETWORKING 2005 -- CALL FOR PAPERS
University of Waterloo, Waterloo Ontario Canada May 2 - 6, 2005

Due date for submissions (Extended): November 15, 2004

Networking 2005 is the fourth event in the series of International
Conferences on Networking, organized by the IFIP Technical Committee on
Communication Systems (TC 6). Previous events were held in Paris
(France) in 2000, Pisa (Italy) in 2002, and Athens (Greece) in 2004.
Based on the success of this biannual event, IFIP TC 6 decided to hold
the Networking conference every year starting in 2005. Networking 2005
will take place between May 2 and 6, at the University of Waterloo,
Ontario, Canada. The conference is organized by the University of
Waterloo and sponsored by the IFIP working groups on Network and
Internetwork Architectures (WG 6.2), Performance of Communication
Systems (WG6.3), Wireless Communications (WG6.8), and Photonic
Networking (WG 6.10).

Networking 2005 will be structured along three tracks:

Networking Technologies, Services and Protocols
Performance of Computer and Communication Networks
Mobile and Wireless Communications Systems

For more information on topics of interest and submission guidelines,
Please visit the conference Web page at:

http://www.cs.uwaterloo.ca/Networking2005/index.html


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov  3 10:11:24 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17088
	for <avt-archive@ietf.org>; Wed, 3 Nov 2004 10:11:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPN2S-0007KH-0m
	for avt-archive@ietf.org; Wed, 03 Nov 2004 10:27:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPMhe-0002PX-V5; Wed, 03 Nov 2004 10:05:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPMb7-0006Wg-CA
	for avt@megatron.ietf.org; Wed, 03 Nov 2004 09:58:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15372
	for <avt@ietf.org>; Wed, 3 Nov 2004 09:58:51 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPMqH-0006yP-2g
	for avt@ietf.org; Wed, 03 Nov 2004 10:14:44 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iA3EweR2001061 for <avt@ietf.org>; Wed, 3 Nov 2004 15:58:40 +0100
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by
	esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 3 Nov 2004 15:58:40 +0100
Received: from [147.214.34.66] (research-1fd0e1.ki.sw.ericsson.se
	[147.214.34.66]) by esealnt613.al.sw.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id WB1ZYLF4; Wed, 3 Nov 2004 15:58:40 +0100
Message-ID: <4188F220.6090906@ericsson.com>
Date: Wed, 03 Nov 2004 15:58:40 +0100
X-Sybari-Trust: 45c6e335 8cefd49f 6486bc69 00000138
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>
Subject: Re: [AVT] Updated AVT agenda for IETF 61 in Washington D.C.
References: <41826447.9060206@ericsson.com> <418658DE.9080805@ericsson.com>
In-Reply-To: <418658DE.9080805@ericsson.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 Nov 2004 14:58:40.0523 (UTC)
	FILETIME=[9AE61DB0:01C4C1B5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Content-Transfer-Encoding: 7bit
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Content-Transfer-Encoding: 7bit

Hi,

Magnus Westerlund (KI/EAB) wrote:
> Here is the hopefully final agenda for AVT.
> 
It wasn't, the secretary seems to have had a real struggle with the
agenda. Even the current version isn't final, but lets hope there is no
more changes.

The AVT agenda has been updated, the Monday was simply moved to Wednesday.

Cheers

Magnus Westerlund

=======================================================================

Audio/Video Transport Working Group

CHAIRS: Colin Perkins     <csp@csperkins.org>
          Magnus Westerlund <magnus.westerlund@ericsson.com>

Wednesday, 10 November 2004, 13:00-15:00
========================================

Introduction and Status Update                                 (Chairs)
                                                                  25 min
     Under developement:
           draft-ietf-avt-rtp-midi-format-06.txt
           draft-ietf-avt-rtp-midi-guidelines-06.txt
           draft-ietf-avt-rfc2032-bis-03.txt
           draft-ietf-avt-rfc2429-bis-03.txt
           draft-ietf-avt-rfc2190-to-historic-00.txt
           draft-basso-avt-videoconreq-02.txt
           draft-ietf-avt-rfc3119bis-03.txt
           draft-finlayson-avt-mpa-robust-interoperability-01.txt
           draft-ietf-avt-profile-savpf-01.txt
           draft-ietf-avt-rtp-bv-01.txt
           draft-ietf-avt-ulp-10.txt
           draft-ietf-avt-uxp-07.txt
           draft-ietf-avt-rtp-atrac-family-01.txt
           draft-ietf-avt-rtcpssm-08.txt
           draft-ietf-avt-3gpp-timed-text-07.txt
           draft-ietf-avt-rtp-amrwbplus-02.txt
           draft-ietf-avt-rtp-framing-contrans-03.txt

     AD or IESG Evaluation
           draft-ietf-avt-audio-t140c-00.txt
           draft-ietf-avt-rfc2793bis-09.txt
           draft-ietf-avt-rtp-h264-10.txt
           draft-ietf-avt-uncomp-video-06
           draft-ietf-avt-rtp-retransmission-10
           draft-ietf-avt-tcrtp-07.txt
           draft-ietf-avt-hc-mpls-reqs-03.txt
           draft-ietf-avt-rtcp-feedback-11.txt
           draft-burmeister-avt-rtcp-feedback-sim-06.txt
           draft-jones-avt-audio-t38-05.txt

     RFC Editor:
           draft-ietf-avt-rtp-clearmode-05.txt
           draft-ietf-avt-rtp-dsr-codecs-03.txt
           draft-ietf-avt-rtp-ilbc-05.txt
           draft-ietf-avt-ilbc-codec-05.txt

     Individual drafts with AVT relation
           draft-lim-mpeg4-mime-02.txt
           draft-garudadri-avt-3gpp2-mime-00.txt
           draft-smundra-avt-rtp-red-non-audio-00.txt
           draft-xie-avt-rtp-anti-shadow-00.txt
           draft-wing-avt-rtp-noop-01.txt
           draft-luby-avt-rtp-generic-fec-00.txt

RTCP XR MIB                                         (Clark & Pendleton)
           draft-ietf-avt-rtcp-xr-mib-00.txt                      15 min

Open issues in RFC 2833bis                                     (Taylor)
           draft-ietf-avt-rfc2833bis-05.txt                       15 min

RTP Payload Format for JPEG 2000                                (Leung)
           draft-ietf-avt-jpeg2000-06.txt                         15 min

Far End Camera Control protocol                                  (Even)
           draft-even-avt-h224-00.txt                             15 min


Thursday, 11 November 2004, 13:00-15:00
=======================================

Introduction                                                   (Chairs)
                                                                   5 min

RTP Profile for TCP Friendly Rate Control                      (Gharai)
           draft-ietf-avt-tfrc-profile-03.txt                     25 min

RTP Timestamp Usage for Variable Sample Rate Audio Codecs      (Chairs)
           draft-ietf-avt-variable-rate-audio-00.txt             (Wenger)
           Discussion on mailing list                             30 min

RTP Payload and File Format for VMR-WB                         (Ahmadi)
           draft-ietf-avt-vmr-wb-file-format-00.txt               15 min
           draft-ietf-avt-rtp-vmr-wb-05.txt

RTP Payload Format for AMR and AMR-WB                      (Westerlund)
           draft-ietf-avt-rtp-amr-bis-00.txt                      15 min

                                   - * -



_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Thu Nov  4 03:18:14 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25676
	for <avt-archive@ietf.org>; Thu, 4 Nov 2004 03:18:14 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPd4R-0005Cg-SO
	for avt-archive@ietf.org; Thu, 04 Nov 2004 03:34:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPcm9-0006zy-3E; Thu, 04 Nov 2004 03:15:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPcca-0005bp-DG
	for avt@megatron.ietf.org; Thu, 04 Nov 2004 03:05:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24397
	for <avt@ietf.org>; Thu, 4 Nov 2004 03:05:24 -0500 (EST)
Received: from 67.110.226.239.ptr.us.xo.net ([67.110.226.239]
	helo=mx.webfountain.com) by ietf-mx.ietf.org with smtp (Exim 4.33)
	id 1CPcry-0004up-JA for avt@ietf.org; Thu, 04 Nov 2004 03:21:26 -0500
Received: (qmail 4882 invoked from network); 4 Nov 2004 08:04:47 -0000
Received: from mail.intranet (HELO mail) (10.1.1.37)
	by 67.110.226.239.ptr.us.xo.net with SMTP; 4 Nov 2004 08:04:47 -0000
Received: by mail (8.12.1/8.12.1/Debian -5) with ESMTP id iA488dsB015954;
	Thu, 4 Nov 2004 00:08:39 -0800
Message-Id: <200411040808.iA488dsB015954@mail>
From: "Mike Luby" <luby@digitalfountain.com>
To: <avt@ietf.org>, <rmt@ietf.org>
Date: Thu, 4 Nov 2004 00:05:24 -0800
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTCRQnPL3uqwYCvQhKrcuemRkjgvg==
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 509eeaf340e89c687918a6101c6def35
Cc: magnus.westerlund@ericsson.com, lorenzo@cisco.com,
        "'Allison Mankin'" <mankin@psg.com>, csp@csperkins.org,
        woja@alum.mit.edu
Subject: [AVT] Other pieces of FEC for streaming in 3GPP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1646907964=="
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 73948e4d005645343fd08e813e5615ef

This is a multi-part message in MIME format.

--===============1646907964==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_002A_01C4C201.FC1F44C0"

This is a multi-part message in MIME format.

------=_NextPart_000_002A_01C4C201.FC1F44C0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Magnus sent an interesting email to the avt list about work going on within
3GPP that is relevant to avt, and Rod Walsh was kind enough to forward this
email to the rmt list since this work is also relevant to rmt.   To complete
the story of what is going on within 3GPP, in addition to the link to
S4-AHP159.zip that Magnus provided in his original email, please also see:

 

http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Ad-hoc_PSM/Docs/S4-AHP181.zip 

This document summarizes the 3GPP agreement made at the meeting, and this
document was approved at the 3GPP meeting.

 

http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Ad-hoc_PSM/Docs/S4-AHP138.zip

http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Ad-hoc_PSM/Docs/S4-AHP166.zip

These two documents describe some considerations in the FEC packet and
source block architecture, and along with S4-AHP159.zip, are referenced in
S4-AHP181.zip.

Mike Luby.

 

 

-----Original Message-----

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]On Behalf Of ext

Magnus Westerlund

Sent: Thursday, October 28, 2004 5:37 PM

To: IETF AVT WG

Subject: [AVT] Work on FEC framework for RTP within 3GPP

 

 

Hi,

 

I would like to make all aware of the work on a FEC framework for RTP 

that is ongoing within the 3GPP SA4. It was agreed in the SA4 ad hoc 

meeting 11-13th of October on a working assumption that is according to:

http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Ad-hoc_PSM/Docs/S4-AHP159.zip

with the following changes:

 

- The FEC stream and the original data stream will be SSRC multiplexed 

instead of session multiplexed.

 

- The FEC payload header (the "FEC Tag") will be moved from last in the 

payload to first in the payload for the original stream format.

 

3GPP SA4 will continue to work in neckbreaking speed on this. A proposal 

for specification text for this FEC framework is expected to be 

available in time for the next SA4 meeting (22-26th Nov). The 

specification text needs to be approved on that meeting to meet the 

current deadline.

 

Comments on the approach is solicited.

 

Cheers

 

Magnus Westerlund 

 


------=_NextPart_000_002A_01C4C201.FC1F44C0
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Magnus sent an interesting email to the avt list about work =
going on
within 3GPP that is relevant to avt, and Rod Walsh was kind enough to =
forward
this email to the rmt list since this work is also relevant to rmt. =
&nbsp;&nbsp;To
complete the story of what is going on within 3GPP, in addition to the =
link to
S4-AHP159.zip that Magnus provided in his original email, please also =
see:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><a
href=3D"http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Ad-hoc_PSM/Docs/S4-AHP18=
1.zip">http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Ad-hoc_PSM/Docs/S4-AHP181=
.zip</a>
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>This document summarizes the 3GPP agreement made at the meeting, =
and
this document was approved at the 3GPP =
meeting.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><a
href=3D"http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Ad-hoc_PSM/Docs/S4-AHP13=
8.zip">http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Ad-hoc_PSM/Docs/S4-AHP138=
.zip</a><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><a
href=3D"http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Ad-hoc_PSM/Docs/S4-AHP16=
6.zip">http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Ad-hoc_PSM/Docs/S4-AHP166=
.zip</a><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>These two documents describe some considerations in the FEC =
packet and
source block architecture, and along with S4-AHP159.zip, are referenced =
in
S4-AHP181.zip.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Mike Luby.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>-----Original Message-----<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]On =
Behalf Of
ext<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Magnus Westerlund<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Sent: Thursday, October 28, 2004 5:37 =
PM<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>To: IETF AVT WG<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Subject: [AVT] Work on FEC framework for RTP within =
3GPP<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Hi,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>I would like to make all aware of the work on a FEC framework =
for RTP <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>that is ongoing within the 3GPP SA4. It was agreed in the SA4 ad =
hoc <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>meeting 11-13th of October on a working assumption that is =
according
to:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Ad-hoc_PSM/Docs/S4-AHP15=
9.zip<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>with the following changes:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- The FEC stream and the original data stream will be SSRC =
multiplexed <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>instead of session multiplexed.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- The FEC payload header (the &quot;FEC Tag&quot;) will be moved =
from
last in the <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>payload to first in the payload for the original stream =
format.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>3GPP SA4 will continue to work in neckbreaking speed on this. A
proposal <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>for specification text for this FEC framework is expected to be =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>available in time for the next SA4 meeting (22-26th Nov). The =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>specification text needs to be approved on that meeting to meet =
the <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>current deadline.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Comments on the approach is =
solicited.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Cheers<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Magnus Westerlund&nbsp;</span><o:p></o:p></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_002A_01C4C201.FC1F44C0--



--===============1646907964==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

--===============1646907964==--




From avt-bounces@ietf.org  Thu Nov  4 05:24:19 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06056
	for <avt-archive@ietf.org>; Thu, 4 Nov 2004 05:24:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPf2U-0008Kg-D3
	for avt-archive@ietf.org; Thu, 04 Nov 2004 05:40:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPeQq-0005MI-PL; Thu, 04 Nov 2004 05:01:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPeAt-0003oA-Lz
	for avt@megatron.ietf.org; Thu, 04 Nov 2004 04:45:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03121
	for <avt@ietf.org>; Thu, 4 Nov 2004 04:44:42 -0500 (EST)
Received: from tiere.net.avaya.com ([198.152.12.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPeQ9-0007TN-AQ
	for avt@ietf.org; Thu, 04 Nov 2004 05:00:46 -0500
Received: from tiere.net.avaya.com (localhost [127.0.0.1])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	iA49gr3i005061
	for <avt@ietf.org>; Thu, 4 Nov 2004 04:42:53 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	iA49gk3i004985
	for <avt@ietf.org>; Thu, 4 Nov 2004 04:42:52 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 4 Nov 2004 11:44:35 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F06E30370@is0004avexu1.global.avaya.com>
Thread-Topic: Comments on draft-ietf-avt-rtcp-xr-mib-00.txt
Thread-Index: AcTCUuSiOrF8FfRITiypLoiXuSVLQw==
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <avt@ietf.org>
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 249cd1efd3d5e0d09114abe826a41235
Subject: [AVT] Comments on draft-ietf-avt-rtcp-xr-mib-00.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0183893406=="
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: c0aa019322dfce838bd8604f5a841b57

This is a multi-part message in MIME format.

--===============0183893406==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C252.E499A4E2"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4C252.E499A4E2
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

I apologize if you get this twice, but my first message did not seem to =
make it to the list.=20

Please find below a set of comments to the latest RTCP XR MIB. It's a =
progress relative to the previous version, but there also is a way to go =
until the document can be proposed for WGLC. One basic issue is that the =
MIB does not yet compile. I did not comment on all syntax problems, but =
I hope I caught many of the obvious ones. I suggest to the authors to =
bring the MIB to a correctly compiled state prior to the submission of =
the next version.=20

Regards,

Dan

1. There are a lot of useless references in the document, including some =
relating to historical versions of the SNMP protocol. See =
http://www.ops.ietf.org/mib-boilerplate.html for the minimal and =
sufficient list of SNMP related references
2. The Overview section speaks about an "RTP System", but RTP is not =
expanded or explained prior to this occurrence.
3. At the last IETF meeting we discussed about the relationship between =
RTCP XR MIB and RAQMON, and decided to include a 'Relationship to =
RAQMON' section, which is now only a place-holder. I suggested to the =
editors the following text:
'The Real-time Application QoS monitoring (RAQMON) Framework =
[RAQMON-FRAMEWORK - provide reference here to =
<http://www.ietf.org/internet-drafts/draft-ietf-rmonmib-raqmon-framework-=
07.txt>] defines an architecture that extends the Remote Monitoring =
(RMON) family of applications for monitoring of application QoS in =
real-time, and an extensible data model with objects carried between =
RAQMON data sources and RAQMON collectors. The RAQMON work is more =
generic, and complementary in concept to RTCP-XR, covering a wider range =
of applications running concurrently, while RTCP-XR focuses on QoS =
monitoring of media traffic in VoIP.=20
The Real-time Application QoS Monitoring (RAQMON) MIB is defined by =
[RAQMON-MIB - provide reference here to =
<http://www.ietf.org/internet-drafts/draft-ietf-rmonmib-raqmon-mib-05.txt=
>] and runs on RAQMON collectors. A more comprehensive performance =
monitoring application may query both RAQMON collectors for RAQMON MIB =
information about the QoS parameters of multiple concurrent applications =
and end-points and gateways for RTCP-XR information about the media QoS =
of VoIP.'
4. paragraph 2.2.3 - it is not clear what case is being presented here. =
How in the RTCP XR architecture does a host system acquire information =
about streams beyond what they are sending and receiving?=20
5. Gathering all monitoring objects in one single table may not be a =
good idea. A table imposes grouping all objects in the same compliance =
group. I believe some low-cost implementation may chose to implement =
only part of the objects, and still claim compliance. I suggest that you =
consider splitting into two or more tables.=20
6. While a MIB module is under development, the RFC number in which it =
will eventually be published is usually unknown and must be filled in by =
the RFC Editor prior to publication. An appropriate form for the =
REVISION clause applying to a version under development would be =
something along the following lines:
 REVISION "200212132358Z" -- December 13, 2002=20
DESCRIPTION "Initial version, published as RFC yyyy."=20
-- RFC Ed.: replace yyyy with actual RFC number & remove this note=20
7. The comment in 2.3 about row creation seems to be out of context. =
There is no row creation in this MIB, as far as I understand
8. The DESCRIPTION clause of rtcpXrVoipEntry includes the following: 'A =
row in this table  is created for each RTP session endpoint =
participating.'. This is both broken syntax, as well as it seems to be =
in conflict with the passive monitoring concept.=20
9. STATUS 'optional' is not valid in SMIv2. This needs to be fixed by =
using compliance clauses
10. MAX-ACCESS clauses are missing
11. Need to use REFERENCE clauses rather than referring to references in =
the DESCRIPTION clauses
12. Need to define Notifications rather than traps
13. CONTACT_INFO is missing in the MIB
14. Need to define compliance clauses
15. rtcpXrVoipEntry in the TABLE definition needs to be capitalized
16. There are many instances where INTEGER is used instead of Integer32 =
(SMIv1 left-overs)
17. rtcpXrVoipCallIdentifier - why is this an OCTET STRING? what is the =
size?
18. rtcpXrVoipCallIdentifier - how is this object defined? Is there a =
RFC 3611 reference? why an OBJECT STRING? what is the size?=20
19. rtcpXrVoipSourceIPaddress and rtcpXrVoipDestinationIPaddress - using =
an OCTET STRING for IP addresses is NOT RECOMMENDED. InetAddressType and =
InetAddress TCs should be used
20. rtcpXrVoipSourceIdentifier - seems to be a SnmpAdminString syntax
21. Missing IANA Considerations section



------_=_NextPart_001_01C4C252.E499A4E2
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6603.0">
<TITLE>Comments on draft-ietf-avt-rtcp-xr-mib-00.txt</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">I apologize if you get this =
twice, but my first message did not seem to make it to the list. =
</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Please find below a set of =
comments to the latest RTCP XR MIB. It's a progress relative to the =
previous version, but there also is a way to go until the document can =
be proposed for WGLC. One basic issue is that the MIB does not yet =
compile. I did not comment on all syntax problems, but I hope I caught =
many of the obvious ones. I suggest to the authors to bring the MIB to a =
correctly compiled state prior to the submission of the next version. =
</FONT></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Regards,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Dan</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">1. There =
are a lot of useless references in the document, including some relating =
to historical versions of the SNMP protocol. See <A =
HREF=3D"http://www.ops.ietf.org/mib-boilerplate.html">http://www.ops.ietf=
.org/mib-boilerplate.html</A> for the minimal and sufficient list of =
SNMP related references</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">2. The =
Overview section speaks about an &quot;RTP System&quot;, but RTP is not =
expanded or explained prior to this occurrence.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">3. At =
the last IETF meeting we discussed about the relationship between RTCP =
XR MIB and RAQMON, and decided to include a 'Relationship to RAQMON' =
section, which is now only a place-holder. I suggested to the editors =
the following text:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B><I><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">'The Real-time Application QoS monitoring (RAQMON) =
Framework [RAQMON-FRAMEWORK - provide reference here to<U> &lt;<A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-ietf-rmonmib-raqmon-fra=
mework-07.txt">http://www.ietf.org/internet-drafts/draft-ietf-rmonmib-raq=
mon-framework-07.txt</A>&gt;</U>] defines an architecture that extends =
the Remote Monitoring (RMON) family of applications for monitoring of =
application QoS in real-time, and an extensible data model with objects =
carried between RAQMON data sources and RAQMON collectors. The RAQMON =
work is more generic, and complementary in concept to RTCP-XR, covering =
a wider range of applications running concurrently, while RTCP-XR =
focuses on QoS monitoring of media traffic in =
VoIP.</FONT></I></B><I></I> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B><I><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">The Real-time Application QoS Monitoring (RAQMON) MIB is =
defined by [RAQMON-MIB - provide reference here =
to</FONT></I></B><B><I><U> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">&lt;<A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-ietf-rmonmib-raqmon-mib=
-05.txt">http://www.ietf.org/internet-drafts/draft-ietf-rmonmib-raqmon-mi=
b-05.txt</A>&gt;</FONT></U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">] and runs on RAQMON collectors. A more comprehensive =
performance monitoring application may query both RAQMON collectors for =
RAQMON MIB information about the QoS parameters of multiple concurrent =
applications and end-points and gateways for RTCP-XR information about =
the media QoS of VoIP.'</FONT></I></B><I></I></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">4. =
paragraph 2.2.3 - it is not clear what case is being presented here. How =
in the RTCP XR architecture does a host system acquire information about =
streams beyond what they are sending and receiving? </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">5. =
Gathering all monitoring objects in one single table may not be a good =
idea. A table imposes grouping all objects in the same compliance group. =
I believe some low-cost implementation may chose to implement only part =
of the objects, and still claim compliance. I suggest that you consider =
splitting into two or more tables. </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">6.</FONT> <FONT FACE=3D"Times New Roman">While a MIB =
module is under development, the RFC number in which it will eventually =
be published is usually unknown and must be filled in by the RFC Editor =
prior to publication. An appropriate form for the REVISION clause =
applying to a version under development would be something along the =
following lines:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New =
Roman">&nbsp;REVISION &quot;200212132358Z&quot; -- December 13, 2002 =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New =
Roman">DESCRIPTION &quot;Initial version, published as RFC yyyy.&quot; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New Roman">-- RFC =
Ed.: replace yyyy with actual RFC number &amp; remove this note =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New Roman">7. The =
comment in 2.3 about row creation seems to be out of context. There is =
no row creation in this MIB, as far as I understand</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New Roman">8. The =
DESCRIPTION clause of rtcpXrVoipEntry includes the following: =
'</FONT><FONT SIZE=3D2 FACE=3D"Courier New">A row in this =
table</FONT>&nbsp;<FONT FACE=3D"Times New Roman"> is created for each =
RTP session endpoint participating.</FONT><FONT FACE=3D"Times New =
Roman">'. This is both broken syntax, as well as it seems to be in =
conflict with the passive monitoring concept. </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New Roman">9. =
STATUS 'optional' is not valid in SMIv2. This needs to be fixed by using =
compliance clauses</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New Roman">10. =
MAX-ACCESS clauses are missing</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New Roman">11. =
Need to use REFERENCE clauses rather than referring to references in the =
DESCRIPTION clauses</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New Roman">12. =
Need to define Notifications rather than traps</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New Roman">13. =
CONTACT_INFO is missing in the MIB</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New Roman">14. =
Need to define compliance clauses</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New =
Roman">15.</FONT> <FONT FACE=3D"Times New Roman">rtcpXrVoipEntry in the =
TABLE definition needs to be capitalized</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New Roman">16. =
There are many instances where INTEGER is used instead of Integer32 =
(SMIv1 left-overs)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New Roman">17. =
rtcpXrVoipCallIdentifier - why is this an OCTET STRING? what is the =
size?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New Roman">18. =
rtcpXrVoipCallIdentifier - how is this object defined? Is there a RFC =
3611 reference? why an OBJECT STRING? what is the size?</FONT> =
</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New =
Roman">19.</FONT> <FONT FACE=3D"Times New =
Roman">rtcpXrVoipSourceIPaddress and rtcpXrVoipDestinationIPaddress - =
using an OCTET STRING for IP addresses is NOT RECOMMENDED. =
InetAddressType and InetAddress TCs should be used</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New Roman">20. =
rtcpXrVoipSourceIdentifier - seems to be a SnmpAdminString =
syntax</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New Roman">21. =
Missing IANA Considerations section</FONT></SPAN></P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C4C252.E499A4E2--


--===============0183893406==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

--===============0183893406==--



From avt-bounces@ietf.org  Thu Nov  4 05:26:26 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06213
	for <avt-archive@ietf.org>; Thu, 4 Nov 2004 05:26:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPf4X-0008Nx-5E
	for avt-archive@ietf.org; Thu, 04 Nov 2004 05:42:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPenn-0000OQ-QM; Thu, 04 Nov 2004 05:25:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPeTc-000659-1k
	for avt@megatron.ietf.org; Thu, 04 Nov 2004 05:04:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04759
	for <avt@ietf.org>; Thu, 4 Nov 2004 05:04:08 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPeix-0007uD-3v
	for avt@ietf.org; Thu, 04 Nov 2004 05:20:11 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:61574
	helo=[192.168.0.5])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1CPeSv-0004Sx-5g for avt@ietf.org; Thu, 04 Nov 2004 10:03:37 +0000
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <4188F220.6090906@ericsson.com>
References: <41826447.9060206@ericsson.com> <418658DE.9080805@ericsson.com>
	<4188F220.6090906@ericsson.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <C908A25D-2E48-11D9-B2AB-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Updated AVT agenda for IETF 61 in Washington D.C.
Date: Thu, 4 Nov 2004 10:03:32 +0000
To: IETF AVT WG <avt@ietf.org>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Content-Transfer-Encoding: 7bit
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Content-Transfer-Encoding: 7bit

Here's another revision to the agenda. This adds discussion of RTP 
Payloads for Anti-shadow Redundancy to Wednesday, but makes no other 
changes.

Colin



Audio/Video Transport Working Group

CHAIRS: Colin Perkins     <csp@csperkins.org>
         Magnus Westerlund <magnus.westerlund@ericsson.com>

Wednesday, 10 November 2004, 13:00-15:00
========================================

Introduction and Status Update                                 (Chairs)
                                                                 25 min
    Under developement:
          draft-ietf-avt-rtp-midi-format-06.txt
          draft-ietf-avt-rtp-midi-guidelines-06.txt
          draft-ietf-avt-rfc2032-bis-03.txt
          draft-ietf-avt-rfc2429-bis-03.txt
          draft-ietf-avt-rfc2190-to-historic-00.txt
          draft-basso-avt-videoconreq-02.txt
          draft-ietf-avt-rfc3119bis-03.txt
          draft-finlayson-avt-mpa-robust-interoperability-01.txt
          draft-ietf-avt-profile-savpf-01.txt
          draft-ietf-avt-rtp-bv-01.txt
          draft-ietf-avt-ulp-10.txt
          draft-ietf-avt-uxp-07.txt
          draft-ietf-avt-rtp-atrac-family-01.txt
          draft-ietf-avt-rtcpssm-08.txt
          draft-ietf-avt-3gpp-timed-text-07.txt
          draft-ietf-avt-rtp-amrwbplus-02.txt
          draft-ietf-avt-rtp-framing-contrans-03.txt

    AD or IESG Evaluation
          draft-ietf-avt-audio-t140c-00.txt
          draft-ietf-avt-rfc2793bis-09.txt
          draft-ietf-avt-rtp-h264-10.txt
          draft-ietf-avt-uncomp-video-06
          draft-ietf-avt-rtp-retransmission-10
          draft-ietf-avt-tcrtp-07.txt
          draft-ietf-avt-hc-mpls-reqs-03.txt
          draft-ietf-avt-rtcp-feedback-11.txt
          draft-burmeister-avt-rtcp-feedback-sim-06.txt
          draft-jones-avt-audio-t38-05.txt

    RFC Editor:
          draft-ietf-avt-rtp-clearmode-05.txt
          draft-ietf-avt-rtp-dsr-codecs-03.txt
          draft-ietf-avt-rtp-ilbc-05.txt
          draft-ietf-avt-ilbc-codec-05.txt

    Individual drafts with AVT relation
          draft-lim-mpeg4-mime-02.txt
          draft-garudadri-avt-3gpp2-mime-00.txt
          draft-smundra-avt-rtp-red-non-audio-00.txt
          draft-wing-avt-rtp-noop-01.txt
          draft-luby-avt-rtp-generic-fec-00.txt


RTCP XR MIB                                         (Clark & Pendleton)
          draft-ietf-avt-rtcp-xr-mib-00.txt                        15 min

Open issues in RFC 2833bis                                     (Taylor)
          draft-ietf-avt-rfc2833bis-05.txt                         15 min

RTP Payload Format for JPEG 2000                                (Leung)
          draft-ietf-avt-jpeg2000-06.txt                           15 min

Far End Camera Control protocol                                  (Even)
          draft-even-avt-h224-00.txt                               15 min

RTP Payloads for Anti-shadow Redundancy                           (Xie)
          draft-xie-avt-rtp-anti-shadow-00.txt                     15 min


Thursday, 11 November 2004, 13:00-15:00
=======================================

Introduction                                                   (Chairs)
                                                                    5 min

RTP Profile for TCP Friendly Rate Control                      (Gharai)
          draft-ietf-avt-tfrc-profile-03.txt                       25 min

RTP Timestamp Usage for Variable Sample Rate Audio Codecs      (Chairs)
          draft-ietf-avt-variable-rate-audio-00.txt             (Wenger)
          Discussion on mailing list                               30 min

RTP Payload and File Format for VMR-WB                         (Ahmadi)
          draft-ietf-avt-vmr-wb-file-format-00.txt                 15 min
          draft-ietf-avt-rtp-vmr-wb-05.txt

RTP Payload Format for AMR and AMR-WB                      (Westerlund)
          draft-ietf-avt-rtp-amr-bis-00.txt                        15 min

                                  - * -


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Thu Nov  4 06:38:52 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11060
	for <avt-archive@ietf.org>; Thu, 4 Nov 2004 06:38:52 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPgCe-0001Ti-AE
	for avt-archive@ietf.org; Thu, 04 Nov 2004 06:54:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPfuF-00057P-I3; Thu, 04 Nov 2004 06:35:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPfrO-0004U2-39
	for avt@megatron.ietf.org; Thu, 04 Nov 2004 06:32:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10562
	for <avt@ietf.org>; Thu, 4 Nov 2004 06:32:55 -0500 (EST)
Received: from mx.cbeyond.net ([66.180.96.58] helo=mx.cbeyond.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPg6j-0001M4-NE
	for avt@ietf.org; Thu, 04 Nov 2004 06:49:00 -0500
Received: from [68.158.13.97] (port=1469 helo=telws116)
	by mx.cbeyond.com with asmtp (Exim 4.34)
	id 1CPfrC-0003zK-4N; Thu, 04 Nov 2004 06:32:46 -0500
From: "Alan Clark" <alan.d.clark@telchemy.com>
To: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, <avt@ietf.org>
Subject: RE: [AVT] Comments on draft-ietf-avt-rtcp-xr-mib-00.txt
Date: Thu, 4 Nov 2004 06:32:44 -0500
Message-ID: <BGEKJNNFCPJKLLMMDMELKEOEFHAA.alan.d.clark@telchemy.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F06E30370@is0004avexu1.global.avaya.com>
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 4c358d334afcd91b425d436ca5722f22
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0781051224=="
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 441f623df000f14368137198649cb083

This is a multi-part message in MIME format.

--===============0781051224==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0048_01C4C238.17D4B6B0"

This is a multi-part message in MIME format.

------=_NextPart_000_0048_01C4C238.17D4B6B0
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: 7bit

Comments on draft-ietf-avt-rtcp-xr-mib-00.txtDan

Thanks for your comments - we are hoping to get a small group together next
week to edit the document and have been saving comments - I hope than you
can join us?

Regards

Alan
  -----Original Message-----
  From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]On Behalf Of
Romascanu, Dan (Dan)
  Sent: Thursday, November 04, 2004 4:45 AM
  To: avt@ietf.org
  Subject: [AVT] Comments on draft-ietf-avt-rtcp-xr-mib-00.txt


  I apologize if you get this twice, but my first message did not seem to
make it to the list.

  Please find below a set of comments to the latest RTCP XR MIB. It's a
progress relative to the previous version, but there also is a way to go
until the document can be proposed for WGLC. One basic issue is that the MIB
does not yet compile. I did not comment on all syntax problems, but I hope I
caught many of the obvious ones. I suggest to the authors to bring the MIB
to a correctly compiled state prior to the submission of the next version.

  Regards,

  Dan

  1. There are a lot of useless references in the document, including some
relating to historical versions of the SNMP protocol. See
http://www.ops.ietf.org/mib-boilerplate.html for the minimal and sufficient
list of SNMP related references

  2. The Overview section speaks about an "RTP System", but RTP is not
expanded or explained prior to this occurrence.

  3. At the last IETF meeting we discussed about the relationship between
RTCP XR MIB and RAQMON, and decided to include a 'Relationship to RAQMON'
section, which is now only a place-holder. I suggested to the editors the
following text:

  'The Real-time Application QoS monitoring (RAQMON) Framework
[RAQMON-FRAMEWORK - provide reference here to
<http://www.ietf.org/internet-drafts/draft-ietf-rmonmib-raqmon-framework-07.
txt>] defines an architecture that extends the Remote Monitoring (RMON)
family of applications for monitoring of application QoS in real-time, and
an extensible data model with objects carried between RAQMON data sources
and RAQMON collectors. The RAQMON work is more generic, and complementary in
concept to RTCP-XR, covering a wider range of applications running
concurrently, while RTCP-XR focuses on QoS monitoring of media traffic in
VoIP.

  The Real-time Application QoS Monitoring (RAQMON) MIB is defined by
[RAQMON-MIB - provide reference here to
<http://www.ietf.org/internet-drafts/draft-ietf-rmonmib-raqmon-mib-05.txt>]
and runs on RAQMON collectors. A more comprehensive performance monitoring
application may query both RAQMON collectors for RAQMON MIB information
about the QoS parameters of multiple concurrent applications and end-points
and gateways for RTCP-XR information about the media QoS of VoIP.'

  4. paragraph 2.2.3 - it is not clear what case is being presented here.
How in the RTCP XR architecture does a host system acquire information about
streams beyond what they are sending and receiving?

  5. Gathering all monitoring objects in one single table may not be a good
idea. A table imposes grouping all objects in the same compliance group. I
believe some low-cost implementation may chose to implement only part of the
objects, and still claim compliance. I suggest that you consider splitting
into two or more tables.

  6. While a MIB module is under development, the RFC number in which it
will eventually be published is usually unknown and must be filled in by the
RFC Editor prior to publication. An appropriate form for the REVISION clause
applying to a version under development would be something along the
following lines:

   REVISION "200212132358Z" -- December 13, 2002

  DESCRIPTION "Initial version, published as RFC yyyy."

  -- RFC Ed.: replace yyyy with actual RFC number & remove this note

  7. The comment in 2.3 about row creation seems to be out of context. There
is no row creation in this MIB, as far as I understand

  8. The DESCRIPTION clause of rtcpXrVoipEntry includes the following: 'A
row in this table  is created for each RTP session endpoint participating.'.
This is both broken syntax, as well as it seems to be in conflict with the
passive monitoring concept.

  9. STATUS 'optional' is not valid in SMIv2. This needs to be fixed by
using compliance clauses

  10. MAX-ACCESS clauses are missing

  11. Need to use REFERENCE clauses rather than referring to references in
the DESCRIPTION clauses

  12. Need to define Notifications rather than traps

  13. CONTACT_INFO is missing in the MIB

  14. Need to define compliance clauses

  15. rtcpXrVoipEntry in the TABLE definition needs to be capitalized

  16. There are many instances where INTEGER is used instead of Integer32
(SMIv1 left-overs)

  17. rtcpXrVoipCallIdentifier - why is this an OCTET STRING? what is the
size?

  18. rtcpXrVoipCallIdentifier - how is this object defined? Is there a RFC
3611 reference? why an OBJECT STRING? what is the size?

  19. rtcpXrVoipSourceIPaddress and rtcpXrVoipDestinationIPaddress - using
an OCTET STRING for IP addresses is NOT RECOMMENDED. InetAddressType and
InetAddress TCs should be used

  20. rtcpXrVoipSourceIdentifier - seems to be a SnmpAdminString syntax

  21. Missing IANA Considerations section



------=_NextPart_000_0048_01C4C238.17D4B6B0
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Comments on draft-ietf-avt-rtcp-xr-mib-00.txt</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1255">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D460223111-04112004><FONT face=3DArial color=3D#0000ff =

size=3D2>Dan</FONT></SPAN></DIV>
<DIV><SPAN class=3D460223111-04112004><FONT color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D460223111-04112004><FONT color=3D#0000ff =
size=3D2>Thanks for your=20
comments - we are hoping to get a small group together next week to edit =
the=20
document and have been saving comments - I hope than you can join=20
us?</FONT></SPAN></DIV>
<DIV><SPAN class=3D460223111-04112004><FONT color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D460223111-04112004><FONT color=3D#0000ff=20
size=3D2>Regards</FONT></SPAN></DIV>
<DIV><SPAN class=3D460223111-04112004><FONT color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D460223111-04112004><FONT color=3D#0000ff=20
size=3D2>Alan</FONT></SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> =
avt-bounces@ietf.org=20
  [mailto:avt-bounces@ietf.org]<B>On Behalf Of </B>Romascanu, Dan=20
  (Dan)<BR><B>Sent:</B> Thursday, November 04, 2004 4:45 =
AM<BR><B>To:</B>=20
  avt@ietf.org<BR><B>Subject:</B> [AVT] Comments on=20
  draft-ietf-avt-rtcp-xr-mib-00.txt<BR><BR></FONT></DIV><!-- Converted =
from text/rtf format -->
  <P dir=3Dltr><FONT face=3DArial size=3D2>I apologize if you get this =
twice, but my=20
  first message did not seem to make it to the list. </FONT></P>
  <P dir=3Dltr><FONT face=3DArial size=3D2>Please find below a set of =
comments to the=20
  latest RTCP XR MIB. It's a progress relative to the previous version, =
but=20
  there also is a way to go until the document can be proposed for WGLC. =
One=20
  basic issue is that the MIB does not yet compile. I did not comment on =
all=20
  syntax problems, but I hope I caught many of the obvious ones. I =
suggest to=20
  the authors to bring the MIB to a correctly compiled state prior to =
the=20
  submission of the next version. </FONT></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>Regards,</FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>Dan</FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial size=3D2>1. There =
are a lot of=20
  useless references in the document, including some relating to =
historical=20
  versions of the SNMP protocol. See <A=20
  =
href=3D"http://www.ops.ietf.org/mib-boilerplate.html">http://www.ops.ietf=
.org/mib-boilerplate.html</A>=20
  for the minimal and sufficient list of SNMP related=20
  references</FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial size=3D2>2. The =
Overview section=20
  speaks about an "RTP System", but RTP is not expanded or explained =
prior to=20
  this occurrence.</FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial size=3D2>3. At the =
last IETF=20
  meeting we discussed about the relationship between RTCP XR MIB and =
RAQMON,=20
  and decided to include a 'Relationship to RAQMON' section, which is =
now only a=20
  place-holder. I suggested to the editors the following =
text:</FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><B><I><FONT face=3DArial =
color=3D#0000ff size=3D2>'The=20
  Real-time Application QoS monitoring (RAQMON) Framework =
[RAQMON-FRAMEWORK -=20
  provide reference here to<U> &lt;<A=20
  =
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-rmonmib-raqmon-fra=
mework-07.txt">http://www.ietf.org/internet-drafts/draft-ietf-rmonmib-raq=
mon-framework-07.txt</A>&gt;</U>]=20
  defines an architecture that extends the Remote Monitoring (RMON) =
family of=20
  applications for monitoring of application QoS in real-time, and an =
extensible=20
  data model with objects carried between RAQMON data sources and RAQMON =

  collectors. The RAQMON work is more generic, and complementary in =
concept to=20
  RTCP-XR, covering a wider range of applications running concurrently, =
while=20
  RTCP-XR focuses on QoS monitoring of media traffic in=20
  VoIP.</FONT></I></B><I></I> </SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><B><I><FONT face=3DArial =
color=3D#0000ff size=3D2>The=20
  Real-time Application QoS Monitoring (RAQMON) MIB is defined by =
[RAQMON-MIB -=20
  provide reference here to</FONT></I></B><B><I><U> <FONT face=3DArial=20
  color=3D#0000ff size=3D2>&lt;<A=20
  =
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-rmonmib-raqmon-mib=
-05.txt">http://www.ietf.org/internet-drafts/draft-ietf-rmonmib-raqmon-mi=
b-05.txt</A>&gt;</FONT></U><FONT=20
  face=3DArial color=3D#0000ff size=3D2>] and runs on RAQMON collectors. =
A more=20
  comprehensive performance monitoring application may query both RAQMON =

  collectors for RAQMON MIB information about the QoS parameters of =
multiple=20
  concurrent applications and end-points and gateways for RTCP-XR =
information=20
  about the media QoS of VoIP.'</FONT></I></B><I></I></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial size=3D2>4. =
paragraph 2.2.3 - it is=20
  not clear what case is being presented here. How in the RTCP XR =
architecture=20
  does a host system acquire information about streams beyond what they =
are=20
  sending and receiving? </FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial size=3D2>5. =
Gathering all=20
  monitoring objects in one single table may not be a good idea. A table =
imposes=20
  grouping all objects in the same compliance group. I believe some =
low-cost=20
  implementation may chose to implement only part of the objects, and =
still=20
  claim compliance. I suggest that you consider splitting into two or =
more=20
  tables. </FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3DArial size=3D2>6.</FONT> =
<FONT=20
  face=3D"Times New Roman">While a MIB module is under development, the =
RFC number=20
  in which it will eventually be published is usually unknown and must =
be filled=20
  in by the RFC Editor prior to publication. An appropriate form for the =

  REVISION clause applying to a version under development would be =
something=20
  along the following lines:</FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Times New =
Roman">&nbsp;REVISION=20
  "200212132358Z" -- December 13, 2002 </FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Times New =
Roman">DESCRIPTION "Initial=20
  version, published as RFC yyyy." </FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Times New Roman">-- RFC =
Ed.: replace=20
  yyyy with actual RFC number &amp; remove this note </FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Times New Roman">7. The =
comment in 2.3=20
  about row creation seems to be out of context. There is no row =
creation in=20
  this MIB, as far as I understand</FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Times New Roman">8. The =
DESCRIPTION=20
  clause of rtcpXrVoipEntry includes the following: '</FONT><FONT=20
  face=3D"Courier New" size=3D2>A row in this table</FONT>&nbsp;<FONT=20
  face=3D"Times New Roman"> is created for each RTP session endpoint=20
  participating.</FONT><FONT face=3D"Times New Roman">'. This is both =
broken=20
  syntax, as well as it seems to be in conflict with the passive =
monitoring=20
  concept. </FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Times New Roman">9. =
STATUS 'optional'=20
  is not valid in SMIv2. This needs to be fixed by using compliance=20
  clauses</FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Times New Roman">10. =
MAX-ACCESS=20
  clauses are missing</FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Times New Roman">11. =
Need to use=20
  REFERENCE clauses rather than referring to references in the =
DESCRIPTION=20
  clauses</FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Times New Roman">12. =
Need to define=20
  Notifications rather than traps</FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Times New Roman">13. =
CONTACT_INFO is=20
  missing in the MIB</FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Times New Roman">14. =
Need to define=20
  compliance clauses</FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Times New =
Roman">15.</FONT> <FONT=20
  face=3D"Times New Roman">rtcpXrVoipEntry in the TABLE definition needs =
to be=20
  capitalized</FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Times New Roman">16. =
There are many=20
  instances where INTEGER is used instead of Integer32 (SMIv1=20
  left-overs)</FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Times New Roman">17.=20
  rtcpXrVoipCallIdentifier - why is this an OCTET STRING? what is the=20
  size?</FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Times New Roman">18.=20
  rtcpXrVoipCallIdentifier - how is this object defined? Is there a RFC =
3611=20
  reference? why an OBJECT STRING? what is the size?</FONT> </SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Times New =
Roman">19.</FONT> <FONT=20
  face=3D"Times New Roman">rtcpXrVoipSourceIPaddress and=20
  rtcpXrVoipDestinationIPaddress - using an OCTET STRING for IP =
addresses is NOT=20
  RECOMMENDED. InetAddressType and InetAddress TCs should be=20
  used</FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Times New Roman">20.=20
  rtcpXrVoipSourceIdentifier - seems to be a SnmpAdminString=20
  syntax</FONT></SPAN></P>
  <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Times New Roman">21. =
Missing IANA=20
  Considerations =
section</FONT></SPAN></P><BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0048_01C4C238.17D4B6B0--



--===============0781051224==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

--===============0781051224==--




From avt-bounces@ietf.org  Fri Nov  5 09:18:32 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15217
	for <avt-archive@ietf.org>; Fri, 5 Nov 2004 09:18:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQ5Am-00048o-1q
	for avt-archive@ietf.org; Fri, 05 Nov 2004 09:34:50 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQ4tR-0005QP-W1; Fri, 05 Nov 2004 09:16:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ4kn-0004S0-CE
	for avt@megatron.ietf.org; Fri, 05 Nov 2004 09:07:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14567
	for <avt@ietf.org>; Fri, 5 Nov 2004 09:07:47 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ50L-0003vr-W8
	for avt@ietf.org; Fri, 05 Nov 2004 09:24:05 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iA5E7ZvD003307
	for <avt@ietf.org>; Fri, 5 Nov 2004 15:07:35 +0100 (MET)
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by
	esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 5 Nov 2004 15:07:34 +0100
Received: from [147.214.97.153] (permit153.er.ki.sw.ericsson.se
	[147.214.97.153]) by esealnt613.al.sw.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id WB15370B; Fri, 5 Nov 2004 15:07:30 +0100
Message-ID: <418B787E.3030806@ericsson.com>
Date: Fri, 05 Nov 2004 13:56:30 +0100
X-Sybari-Trust: 7f2fff4d 8cefd49f 5bc1529a 00000138
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
Subject: Re: [AVT] Comments on draft-ietf-avt-rtcp-xr-mib-00.txt
References: <AAB4B3D3CF0F454F98272CBE187FDE2F06E30370@is0004avexu1.global.avaya.com>
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F06E30370@is0004avexu1.global.avaya.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Nov 2004 14:07:34.0022 (UTC)
	FILETIME=[CBF2B260:01C4C340]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Content-Transfer-Encoding: 7bit
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
Content-Transfer-Encoding: 7bit

Hi Dan,

I have a comment on the below.

Romascanu, Dan (Dan) wrote:
> 
> 3. At the last IETF meeting we discussed about the relationship between 
> RTCP XR MIB and RAQMON, and decided to include a 'Relationship to 
> RAQMON' section, which is now only a place-holder. I suggested to the 
> editors the following text:
> 
> */'The Real-time Application QoS monitoring (RAQMON) Framework 
> [RAQMON-FRAMEWORK - provide reference here to_ 
> <http://www.ietf.org/internet-drafts/draft-ietf-rmonmib-raqmon-framework-07.txt>_] 
> defines an architecture that extends the Remote Monitoring (RMON) family 
> of applications for monitoring of application QoS in real-time, and an 
> extensible data model with objects carried between RAQMON data sources 
> and RAQMON collectors. The RAQMON work is more generic, and 
> complementary in concept to RTCP-XR, covering a wider range of 
> applications running concurrently, while RTCP-XR focuses on QoS 
> monitoring of media traffic in VoIP./*//

Although one of the RTCP XR types has received substantially more 
interest, the RTCP XR is not limited to VoIP. It is a general framework 
which is currently populated with the following different reporting blocks:
        4.1.  Loss RLE Report Block. . . . . . . . . . . . . . . . . .  9
        4.2.  Duplicate RLE Report Block . . . . . . . . . . . . . . . 16
        4.3.  Packet Receipt Times Report Block. . . . . . . . . . . . 18
        4.4.  Receiver Reference Time Report Block . . . . . . . . . . 20
        4.5.  DLRR Report Block. . . . . . . . . . . . . . . . . . . . 21
        4.6.  Statistics Summary Report Block. . . . . . . . . . . . . 22
        4.7.  VoIP Metrics Report Block. . . . . . . . . . . . . . . . 25

Thus, I can also provide some more comments of the document:

MW1: The XR MIB needs to be defined in such a way that it can easily be 
extended if more report types are created.

MW2: THE XR MIB should define structures for all the currently defined 
XR report blocks.

MW3: The security consideration section also seems to be a bit strange, 
is it mostly copy and pasted from the RTP MIB?

MW4: rtcpXrVoipSessionIdentifier OBJECT-TYPE
     SYNTAX OCTET STRING
     STATUS optional
     DESCRIPTION
         "Unique identifier for this session.  Where a billing record
          correlation identifer is not available for a particular call,
          another identifier such as SSRC can be used."
     ::= { rtcpXrVoipEntry 3 }

How can the SSRC be a session identifier?

MW5: How is sessions with more than a single destination handled?

MW6: rtcpXrVoipVocoderType OBJECT-TYPE
     SYNTAX OCTET STRING
     STATUS current
     DESCRIPTION
         "Vocoder type used on this call."
     ::= { rtcpXrVoipEntry 10 }

rtcpXrVoipFrameSize OBJECT-TYPE
     SYNTAX INTEGER
     STATUS current
     DESCRIPTION
         "Companion information to vocoder type.  This represents the
          size of the frames within the RTP packets at the time the
          information is capture."
     ::= { rtcpXrVoipEntry 11 }

First, is multiple instances allowed? A session may consist of multiple 
media codecs and/or configurations of a codec. Also how is the vocoder 
type expressed. What is the string? The RTP payload MIME type with its 
parameters? Maybe one should consider to make this definition a bit more 
generic to fit any media encoding format? Thus it can potentially be 
re-used?

MW7: rtcpXrVoipSampleRate OBJECT-TYPE
     SYNTAX OCTET STRING
     STATUS current
     DESCRIPTION
         "Companion information to vocoder type.  This represents the
          rate at which the frames where sampled.
     ::= { rtcpXrVoipEntry 12 }

Which rate are you talking about here? The audio sample rate, or the 
rate with which frames are produced?

MW8: All references can not be normative, a lot of these must be 
informative ones.

MW9: Run a spellchecker over the description texts.

Cheers

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Fri Nov  5 12:47:26 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02356
	for <avt-archive@ietf.org>; Fri, 5 Nov 2004 12:47:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQ8R9-00006u-6r
	for avt-archive@ietf.org; Fri, 05 Nov 2004 13:03:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQ7sR-00011v-2N; Fri, 05 Nov 2004 12:27:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ7qt-0000Jn-JQ
	for avt@megatron.ietf.org; Fri, 05 Nov 2004 12:26:19 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00519
	for <avt@ietf.org>; Fri, 5 Nov 2004 12:26:17 -0500 (EST)
Received: from tierw.net.avaya.com ([198.152.13.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ86c-00082T-6J
	for avt@ietf.org; Fri, 05 Nov 2004 12:42:38 -0500
Received: from tierw.net.avaya.com (localhost [127.0.0.1])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	iA5HI4wB024331
	for <avt@ietf.org>; Fri, 5 Nov 2004 12:18:05 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	iA5HGdwB022335
	for <avt@ietf.org>; Fri, 5 Nov 2004 12:17:08 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] Comments on draft-ietf-avt-rtcp-xr-mib-00.txt
Date: Fri, 5 Nov 2004 19:24:37 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F038A9F12@is0004avexu1.global.avaya.com>
Thread-Topic: [AVT] Comments on draft-ietf-avt-rtcp-xr-mib-00.txt
Thread-Index: AcTDQM+rdJcljMQcRh6NmKy2/HRmFQAGjtuA
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: quoted-printable
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: quoted-printable

Hi Magnus,

Right. The last phrase in the suggested text would rather be:

The RAQMON work is generic and complementary in concept to RTCP-XR, =
covering a wider range of=20
applications running concurrently, possibly on different protocols, =
while RTCP-XR focuses on QoS=20
monitoring of media traffic of RTP sessions.

Regards,

Dan



> -----Original Message-----
> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> Sent: 05 November, 2004 2:57 PM
> To: Romascanu, Dan (Dan)
> Cc: avt@ietf.org
> Subject: Re: [AVT] Comments on draft-ietf-avt-rtcp-xr-mib-00.txt
>=20
>=20
> Hi Dan,
>=20
> I have a comment on the below.
>=20
> Romascanu, Dan (Dan) wrote:
> >=20
> > 3. At the last IETF meeting we discussed about the=20
> relationship between=20
> > RTCP XR MIB and RAQMON, and decided to include a 'Relationship to=20
> > RAQMON' section, which is now only a place-holder. I=20
> suggested to the=20
> > editors the following text:
> >=20
> > */'The Real-time Application QoS monitoring (RAQMON) Framework=20
> > [RAQMON-FRAMEWORK - provide reference here to_=20
> >=20
> <http://www.ietf.org/internet-drafts/draft-ietf-rmonmib-raqmon
> -framework-07.txt>_]=20
> > defines an architecture that extends the Remote Monitoring=20
> (RMON) family=20
> > of applications for monitoring of application QoS in=20
> real-time, and an=20
> > extensible data model with objects carried between RAQMON=20
> data sources=20
> > and RAQMON collectors. The RAQMON work is more generic, and=20
> > complementary in concept to RTCP-XR, covering a wider range of=20
> > applications running concurrently, while RTCP-XR focuses on QoS=20
> > monitoring of media traffic in VoIP./*//
>=20
> Although one of the RTCP XR types has received substantially more=20
> interest, the RTCP XR is not limited to VoIP. It is a general=20
> framework=20
> which is currently populated with the following different=20
> reporting blocks:

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Fri Nov  5 15:09:50 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12375
	for <avt-archive@ietf.org>; Fri, 5 Nov 2004 15:09:50 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQAew-0002sv-T2
	for avt-archive@ietf.org; Fri, 05 Nov 2004 15:26:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQAEb-0003GA-1a; Fri, 05 Nov 2004 14:58:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQA4m-0001Nn-Ua
	for avt@megatron.ietf.org; Fri, 05 Nov 2004 14:48:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10600
	for <avt@ietf.org>; Fri, 5 Nov 2004 14:48:46 -0500 (EST)
Received: from 10.red-80-33-119.pooles.rima-tde.net ([80.33.119.10]
	helo=savillal.org) by ietf-mx.ietf.org with smtp (Exim 4.33)
	id 1CQAKZ-0002Tk-R4 for avt@ietf.org; Fri, 05 Nov 2004 15:05:08 -0500
Date: Fri, 05 Nov 2004 20:49:45 +0100
To: "Avt" <avt@ietf.org>
From: "Csp" <csp@csperkins.org>
Message-ID: <rcmrvpyfpxdrpzwerqe@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="--------zmwmxsfsrlwkmitmoaka"
X-Spam-Score: 0.9 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Subject: [AVT] Re: Hello
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228

----------zmwmxsfsrlwkmitmoaka
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<html><body>
:))

<br>
</body></html>

----------zmwmxsfsrlwkmitmoaka
Content-Type: application/octet-stream; name="price.cpl"
Content-Disposition: attachment; filename="price.cpl"
Content-Transfer-Encoding: base64



----------zmwmxsfsrlwkmitmoaka
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

----------zmwmxsfsrlwkmitmoaka--




From avt-bounces@ietf.org  Sat Nov  6 02:29:21 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17731
	for <avt-archive@ietf.org>; Sat, 6 Nov 2004 02:29:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQL0p-0000aX-P9
	for avt-archive@ietf.org; Sat, 06 Nov 2004 02:29:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQKuy-0005oF-6u; Sat, 06 Nov 2004 02:23:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQKoA-0002dF-M1
	for avt@megatron.ietf.org; Sat, 06 Nov 2004 02:16:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16529
	for <avt@ietf.org>; Sat, 6 Nov 2004 02:16:20 -0500 (EST)
Received: from web8408.mail.in.yahoo.com ([202.43.219.156])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CQKoC-0000Mr-5u
	for avt@ietf.org; Sat, 06 Nov 2004 02:16:27 -0500
Received: (qmail 27539 invoked by uid 60001); 6 Nov 2004 07:15:42 -0000
Message-ID: <20041106071542.27533.qmail@web8408.mail.in.yahoo.com>
Received: from [203.129.220.115] by web8408.mail.in.yahoo.com via HTTP;
	Sat, 06 Nov 2004 07:15:42 GMT
Date: Sat, 6 Nov 2004 07:15:42 +0000 (GMT)
From: rahul agrawal <voipthesis@yahoo.co.in>
To: avt@ietf.org
MIME-Version: 1.0
X-Spam-Score: 1.8 (+)
X-Scan-Signature: ec7c6dab5a62df223002ae71b5179d41
Subject: [AVT] need some help
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0521145393=="
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 1.8 (+)
X-Scan-Signature: ff0adf256e4dd459cc25215cfa732ac1

--===============0521145393==
Content-Type: multipart/alternative; boundary="0-324935753-1099725342=:26228"

--0-324935753-1099725342=:26228
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit


sir/mam,


        this is request that please you help me.
        I am studying in M.Tech and working on VoIP.
        I am trying to improve voice quality,so for
        this i measure the voice quality, howmuch 
        it will improve, so take  MOS(mean opinion  
        score), i am trying to implement subjective  
        method that is one human listeners panel  
        listen quality, and give their opinion on.  
        for this  i need some persons which know 
        about this.that means i cant implement this  
         method.

        i found first SNR for voice siganland  
        compare , but its not  relaible ao pls tell 
        me another method to measure voice quality 
        that its .


avt-request@ietf.org wrote:Send avt mailing list submissions to
avt@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
https://www1.ietf.org/mailman/listinfo/avt
or, via email, send a message with subject or body 'help' to
avt-request@ietf.org

You can reach the person managing the list at
avt-owner@ietf.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of avt digest..."


Today's Topics:

1. Re: Comments on draft-ietf-avt-rtcp-xr-mib-00.txt
(Magnus Westerlund)


----------------------------------------------------------------------

Message: 1
Date: Fri, 05 Nov 2004 13:56:30 +0100
From: Magnus Westerlund 
Subject: Re: [AVT] Comments on draft-ietf-avt-rtcp-xr-mib-00.txt
To: "Romascanu, Dan \(Dan\)" 
Cc: avt@ietf.org
Message-ID: <418B787E.3030806@ericsson.com>
Content-Type: text/plain; charset=us-ascii; format=flowed

Hi Dan,

I have a comment on the below.

Romascanu, Dan (Dan) wrote:
> 
> 3. At the last IETF meeting we discussed about the relationship between 
> RTCP XR MIB and RAQMON, and decided to include a 'Relationship to 
> RAQMON' section, which is now only a place-holder. I suggested to the 
> editors the following text:
> 
> */'The Real-time Application QoS monitoring (RAQMON) Framework 
> [RAQMON-FRAMEWORK - provide reference here to_ 
> _] 
> defines an architecture that extends the Remote Monitoring (RMON) family 
> of applications for monitoring of application QoS in real-time, and an 
> extensible data model with objects carried between RAQMON data sources 
> and RAQMON collectors. The RAQMON work is more generic, and 
> complementary in concept to RTCP-XR, covering a wider range of 
> applications running concurrently, while RTCP-XR focuses on QoS 
> monitoring of media traffic in VoIP./*//

Although one of the RTCP XR types has received substantially more 
interest, the RTCP XR is not limited to VoIP. It is a general framework 
which is currently populated with the following different reporting blocks:
4.1. Loss RLE Report Block. . . . . . . . . . . . . . . . . . 9
4.2. Duplicate RLE Report Block . . . . . . . . . . . . . . . 16
4.3. Packet Receipt Times Report Block. . . . . . . . . . . . 18
4.4. Receiver Reference Time Report Block . . . . . . . . . . 20
4.5. DLRR Report Block. . . . . . . . . . . . . . . . . . . . 21
4.6. Statistics Summary Report Block. . . . . . . . . . . . . 22
4.7. VoIP Metrics Report Block. . . . . . . . . . . . . . . . 25

Thus, I can also provide some more comments of the document:

MW1: The XR MIB needs to be defined in such a way that it can easily be 
extended if more report types are created.

MW2: THE XR MIB should define structures for all the currently defined 
XR report blocks.

MW3: The security consideration section also seems to be a bit strange, 
is it mostly copy and pasted from the RTP MIB?

MW4: rtcpXrVoipSessionIdentifier OBJECT-TYPE
SYNTAX OCTET STRING
STATUS optional
DESCRIPTION
"Unique identifier for this session. Where a billing record
correlation identifer is not available for a particular call,
another identifier such as SSRC can be used."
::= { rtcpXrVoipEntry 3 }

How can the SSRC be a session identifier?

MW5: How is sessions with more than a single destination handled?

MW6: rtcpXrVoipVocoderType OBJECT-TYPE
SYNTAX OCTET STRING
STATUS current
DESCRIPTION
"Vocoder type used on this call."
::= { rtcpXrVoipEntry 10 }

rtcpXrVoipFrameSize OBJECT-TYPE
SYNTAX INTEGER
STATUS current
DESCRIPTION
"Companion information to vocoder type. This represents the
size of the frames within the RTP packets at the time the
information is capture."
::= { rtcpXrVoipEntry 11 }

First, is multiple instances allowed? A session may consist of multiple 
media codecs and/or configurations of a codec. Also how is the vocoder 
type expressed. What is the string? The RTP payload MIME type with its 
parameters? Maybe one should consider to make this definition a bit more 
generic to fit any media encoding format? Thus it can potentially be 
re-used?

MW7: rtcpXrVoipSampleRate OBJECT-TYPE
SYNTAX OCTET STRING
STATUS current
DESCRIPTION
"Companion information to vocoder type. This represents the
rate at which the frames where sampled.
::= { rtcpXrVoipEntry 12 }

Which rate are you talking about here? The audio sample rate, or the 
rate with which frames are produced?

MW8: All references can not be normative, a lot of these must be 
informative ones.

MW9: Run a spellchecker over the description texts.

Cheers

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB | Phone +46 8 4048287
Torshamsgatan 23 | Fax +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com




------------------------------

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


End of avt Digest, Vol 7, Issue 6
*********************************


Yahoo! India Matrimony: Find your life partneronline.
--0-324935753-1099725342=:26228
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<DIV><BR>sir/mam,<BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; this is request that please you help me.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I am studying in M.Tech and working on VoIP.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I am trying to improve voice quality,so for<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; this i measure the voice quality, howmuch <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; it will improve, so take&nbsp; MOS(mean opinion&nbsp; <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; score), i am trying to implement subjective&nbsp; <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; method that is one human listeners panel&nbsp; <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; listen quality, and give their opinion on.&nbsp; <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for this&nbsp; i need some persons which know <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; about this.that means i cant implement this&nbsp;
 <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; method.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; i found first SNR for voice siganland&nbsp; <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; compare , but its not&nbsp; relaible ao pls tell <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; me another method to measure voice quality <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; that its .<BR><BR><BR><B><I>avt-request@ietf.org</I></B> wrote:
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Send avt mailing list submissions to<BR>avt@ietf.org<BR><BR>To subscribe or unsubscribe via the World Wide Web, visit<BR>https://www1.ietf.org/mailman/listinfo/avt<BR>or, via email, send a message with subject or body 'help' to<BR>avt-request@ietf.org<BR><BR>You can reach the person managing the list at<BR>avt-owner@ietf.org<BR><BR>When replying, please edit your Subject line so it is more specific<BR>than "Re: Contents of avt digest..."<BR><BR><BR>Today's Topics:<BR><BR>1. Re: Comments on draft-ietf-avt-rtcp-xr-mib-00.txt<BR>(Magnus Westerlund)<BR><BR><BR>----------------------------------------------------------------------<BR><BR>Message: 1<BR>Date: Fri, 05 Nov 2004 13:56:30 +0100<BR>From: Magnus Westerlund <MAGNUS.WESTERLUND@ERICSSON.COM><BR>Subject: Re: [AVT] Comments on draft-ietf-avt-rtcp-xr-mib-00.txt<BR>To: "Romascanu, Dan \(Dan\)" <DROMASCA@AVAYA.COM><BR>Cc:
 avt@ietf.org<BR>Message-ID: &lt;418B787E.3030806@ericsson.com&gt;<BR>Content-Type: text/plain; charset=us-ascii; format=flowed<BR><BR>Hi Dan,<BR><BR>I have a comment on the below.<BR><BR>Romascanu, Dan (Dan) wrote:<BR>&gt; <BR>&gt; 3. At the last IETF meeting we discussed about the relationship between <BR>&gt; RTCP XR MIB and RAQMON, and decided to include a 'Relationship to <BR>&gt; RAQMON' section, which is now only a place-holder. I suggested to the <BR>&gt; editors the following text:<BR>&gt; <BR>&gt; */'The Real-time Application QoS monitoring (RAQMON) Framework <BR>&gt; [RAQMON-FRAMEWORK - provide reference here to_ <BR>&gt; <HTTP: draft-ietf-rmonmib-raqmon-framework-07.txt internet-drafts www.ietf.org>_] <BR>&gt; defines an architecture that extends the Remote Monitoring (RMON) family <BR>&gt; of applications for monitoring of application QoS in real-time, and an <BR>&gt; extensible data model with objects carried between RAQMON data sources <BR>&gt; and RAQMON coll!
 ectors.
 The RAQMON work is more generic, and <BR>&gt; complementary in concept to RTCP-XR, covering a wider range of <BR>&gt; applications running concurrently, while RTCP-XR focuses on QoS <BR>&gt; monitoring of media traffic in VoIP./*//<BR><BR>Although one of the RTCP XR types has received substantially more <BR>interest, the RTCP XR is not limited to VoIP. It is a general framework <BR>which is currently populated with the following different reporting blocks:<BR>4.1. Loss RLE Report Block. . . . . . . . . . . . . . . . . . 9<BR>4.2. Duplicate RLE Report Block . . . . . . . . . . . . . . . 16<BR>4.3. Packet Receipt Times Report Block. . . . . . . . . . . . 18<BR>4.4. Receiver Reference Time Report Block . . . . . . . . . . 20<BR>4.5. DLRR Report Block. . . . . . . . . . . . . . . . . . . . 21<BR>4.6. Statistics Summary Report Block. . . . . . . . . . . . . 22<BR>4.7. VoIP Metrics Report Block. . . . . . . . . . . . . . . . 25<BR><BR>Thus, I can also provide some more comments o!
 f the
 document:<BR><BR>MW1: The XR MIB needs to be defined in such a way that it can easily be <BR>extended if more report types are created.<BR><BR>MW2: THE XR MIB should define structures for all the currently defined <BR>XR report blocks.<BR><BR>MW3: The security consideration section also seems to be a bit strange, <BR>is it mostly copy and pasted from the RTP MIB?<BR><BR>MW4: rtcpXrVoipSessionIdentifier OBJECT-TYPE<BR>SYNTAX OCTET STRING<BR>STATUS optional<BR>DESCRIPTION<BR>"Unique identifier for this session. Where a billing record<BR>correlation identifer is not available for a particular call,<BR>another identifier such as SSRC can be used."<BR>::= { rtcpXrVoipEntry 3 }<BR><BR>How can the SSRC be a session identifier?<BR><BR>MW5: How is sessions with more than a single destination handled?<BR><BR>MW6: rtcpXrVoipVocoderType OBJECT-TYPE<BR>SYNTAX OCTET STRING<BR>STATUS current<BR>DESCRIPTION<BR>"Vocoder type used on this call."<BR>::= { rtcpXrVoipEntry 10
 }<BR><BR>rtcpXrVoipFrameSize OBJECT-TYPE<BR>SYNTAX INTEGER<BR>STATUS current<BR>DESCRIPTION<BR>"Companion information to vocoder type. This represents the<BR>size of the frames within the RTP packets at the time the<BR>information is capture."<BR>::= { rtcpXrVoipEntry 11 }<BR><BR>First, is multiple instances allowed? A session may consist of multiple <BR>media codecs and/or configurations of a codec. Also how is the vocoder <BR>type expressed. What is the string? The RTP payload MIME type with its <BR>parameters? Maybe one should consider to make this definition a bit more <BR>generic to fit any media encoding format? Thus it can potentially be <BR>re-used?<BR><BR>MW7: rtcpXrVoipSampleRate OBJECT-TYPE<BR>SYNTAX OCTET STRING<BR>STATUS current<BR>DESCRIPTION<BR>"Companion information to vocoder type. This represents the<BR>rate at which the frames where sampled.<BR>::= { rtcpXrVoipEntry 12 }<BR><BR>Which rate are you talking about here? The audio sample rate, or the <BR>rate !
 with
 which frames are produced?<BR><BR>MW8: All references can not be normative, a lot of these must be <BR>informative ones.<BR><BR>MW9: Run a spellchecker over the description texts.<BR><BR>Cheers<BR><BR>Magnus Westerlund<BR><BR>Multimedia Technologies, Ericsson Research EAB/TVA/A<BR>----------------------------------------------------------------------<BR>Ericsson AB | Phone +46 8 4048287<BR>Torshamsgatan 23 | Fax +46 8 7575550<BR>S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com<BR><BR><BR><BR><BR>------------------------------<BR><BR>_______________________________________________<BR>Audio/Video Transport Working Group<BR>avt@ietf.org<BR>https://www1.ietf.org/mailman/listinfo/avt<BR><BR><BR>End of avt Digest, Vol 7, Issue 6<BR>*********************************<BR></BLOCKQUOTE></DIV><p><font face=arial size=-1>
<a href="http://in.rd.yahoo.com/specials/mailtg/*http://yahoo.shaadi.com/india-matrimony/" target="_blank">
<b>Yahoo! India Matrimony</a>:</b> Find your life partner
<a href="http://in.rd.yahoo.com/specials/mailtg2/*http://yahoo.shaadi.com/india-matrimony/" target="_blank">online</a>.</font>
--0-324935753-1099725342=:26228--


--===============0521145393==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

--===============0521145393==--



From avt-bounces@ietf.org  Sat Nov  6 07:21:21 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01778
	for <avt-archive@ietf.org>; Sat, 6 Nov 2004 07:21:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQPZS-0005G5-2x
	for avt-archive@ietf.org; Sat, 06 Nov 2004 07:21:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQPPG-0005Zh-87; Sat, 06 Nov 2004 07:10:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQPMI-0004rd-J4
	for avt@megatron.ietf.org; Sat, 06 Nov 2004 07:07:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01043
	for <avt@ietf.org>; Sat, 6 Nov 2004 07:07:51 -0500 (EST)
Received: from mx.cbeyond.net ([66.180.96.58] helo=mx.cbeyond.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQPMF-000528-Qy
	for avt@ietf.org; Sat, 06 Nov 2004 07:08:02 -0500
Received: from [68.158.13.97] (port=1182 helo=telws116)
	by mx.cbeyond.com with asmtp (Exim 4.34)
	id 1CQPM4-0004nv-Tv; Sat, 06 Nov 2004 07:07:41 -0500
From: "Alan Clark" <alan.d.clark@telchemy.com>
To: "rahul agrawal" <voipthesis@yahoo.co.in>
Subject: RE: [AVT] need some help
Date: Sat, 6 Nov 2004 07:07:40 -0500
Message-ID: <BGEKJNNFCPJKLLMMDMELEEFFFIAA.alan.d.clark@telchemy.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
In-Reply-To: <20041106071542.27533.qmail@web8408.mail.in.yahoo.com>
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0184382430=="
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 1.0 (+)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba

This is a multi-part message in MIME format.

--===============0184382430==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0049_01C4C3CF.4DA9B270"

This is a multi-part message in MIME format.

------=_NextPart_000_0049_01C4C3CF.4DA9B270
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Rahul

You want to run an ACR subjective listening test?  You can start by
downloading (for free) ITU-T P.800 from the www.itu.int web site.  You would
also need suitable listening material .. you can either purchase this from
the ITU, download for free from the Open Speech Repository (hosted on
www.voiptroubleshooter.com) or record some material yourself.

Regards

Alan

  -----Original Message-----
  From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]On Behalf Of rahul
agrawal
  Sent: Saturday, November 06, 2004 2:16 AM
  To: avt@ietf.org
  Subject: [AVT] need some help



  sir/mam,


          this is request that please you help me.
          I am studying in M.Tech and working on VoIP.
          I am trying to improve voice quality,so for
          this i measure the voice quality, howmuch
          it will improve, so take  MOS(mean opinion
          score), i am trying to implement subjective
          method that is one human listeners panel
          listen quality, and give their opinion on.
          for this  i need some persons which know
          about this.that means i cant implement this
           method.

          i found first SNR for voice siganland
          compare , but its not  relaible ao pls tell
          me another method to measure voice quality
          that its .


------=_NextPart_000_0049_01C4C3CF.4DA9B270
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT color=3D#0000ff size=3D2><SPAN=20
class=3D569100212-06112004>Rahul</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff size=3D2><SPAN=20
class=3D569100212-06112004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff size=3D2><SPAN class=3D569100212-06112004>You =
want to run=20
an ACR subjective listening test?&nbsp; You can start by downloading =
(for free)=20
ITU-T P.800 from the <A href=3D"http://www.itu.int">www.itu.int</A> web=20
site.&nbsp; You would&nbsp;also need suitable listening material =
..&nbsp;you can=20
either purchase this from the ITU, download for free from the Open =
Speech=20
Repository (hosted on <A=20
href=3D"http://www.voiptroubleshooter.com">www.voiptroubleshooter.com</A>=
) or=20
record some material yourself.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff size=3D2><SPAN =
class=3D569100212-06112004>&nbsp;=20
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D569100212-06112004>Regards</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D569100212-06112004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D569100212-06112004>Alan</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D569100212-06112004></SPAN></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> =
avt-bounces@ietf.org=20
  [mailto:avt-bounces@ietf.org]<B>On Behalf Of </B>rahul =
agrawal<BR><B>Sent:</B>=20
  Saturday, November 06, 2004 2:16 AM<BR><B>To:</B>=20
  avt@ietf.org<BR><B>Subject:</B> [AVT] need some =
help<BR><BR></FONT></DIV>
  =
<DIV><BR>sir/mam,<BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
this=20
  is request that please you help=20
  me.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I am studying in =
M.Tech and=20
  working on VoIP.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I am =
trying to=20
  improve voice quality,so =
for<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  this i measure the voice quality, howmuch=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; it will improve, so =
take&nbsp;=20
  MOS(mean opinion&nbsp; <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
score),=20
  i am trying to implement subjective&nbsp;=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; method that is one =
human=20
  listeners panel&nbsp; <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
listen=20
  quality, and give their opinion on.&nbsp;=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for this&nbsp; i need =
some=20
  persons which know <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
about=20
  this.that means i cant implement this&nbsp;=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  method.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; i found =
first SNR=20
  for voice siganland&nbsp; =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  compare , but its not&nbsp; relaible ao pls tell=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; me another method to =
measure=20
  voice quality <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; that its=20
  .<BR><BR></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0049_01C4C3CF.4DA9B270--



--===============0184382430==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

--===============0184382430==--




From avt-bounces@ietf.org  Sun Nov  7 19:45:03 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16167
	for <avt-archive@ietf.org>; Sun, 7 Nov 2004 19:45:02 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQxf3-0000yu-Qo
	for avt-archive@ietf.org; Sun, 07 Nov 2004 19:45:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQxa8-0003uF-8i; Sun, 07 Nov 2004 19:40:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQxUr-00031W-Rj
	for avt@megatron.ietf.org; Sun, 07 Nov 2004 19:35:01 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15232;
	Sun, 7 Nov 2004 19:34:56 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQxVG-0000gQ-JR; Sun, 07 Nov 2004 19:35:27 -0500
Received: from vpn4.dcs.gla.ac.uk ([130.209.254.4]:55697)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1CQxU9-0000Va-IW; Mon, 08 Nov 2004 00:34:17 +0000
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <E9278DE2-311D-11D9-AA30-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Date: Sun, 7 Nov 2004 19:34:11 -0500
To: avt@ietf.org
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Content-Transfer-Encoding: 7bit
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, agenda@ietf.org
Subject: [AVT] Updated AVT agenda
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Content-Transfer-Encoding: 7bit

Audio/Video Transport Working Group

CHAIRS: Colin Perkins     <csp@csperkins.org>
         Magnus Westerlund <magnus.westerlund@ericsson.com>

Wednesday, 10 November 2004, 13:00-15:00
========================================

Introduction and Status Update                                 (Chairs)
                                                                 25 min
    Under developement:
          draft-ietf-avt-rtp-midi-format-06.txt
          draft-ietf-avt-rtp-midi-guidelines-06.txt
          draft-ietf-avt-rfc2032-bis-03.txt
          draft-ietf-avt-rfc2429-bis-03.txt
          draft-ietf-avt-rfc2190-to-historic-00.txt
          draft-basso-avt-videoconreq-02.txt
          draft-ietf-avt-rfc3119bis-03.txt
          draft-finlayson-avt-mpa-robust-interoperability-01.txt
          draft-ietf-avt-profile-savpf-01.txt
          draft-ietf-avt-rtp-bv-01.txt
          draft-ietf-avt-ulp-10.txt
          draft-ietf-avt-uxp-07.txt
          draft-ietf-avt-rtp-atrac-family-01.txt
          draft-ietf-avt-rtcpssm-08.txt
          draft-ietf-avt-3gpp-timed-text-07.txt
          draft-ietf-avt-rtp-amrwbplus-02.txt
          draft-ietf-avt-rtp-framing-contrans-03.txt

    AD or IESG Evaluation
          draft-ietf-avt-audio-t140c-00.txt
          draft-ietf-avt-rfc2793bis-09.txt
          draft-ietf-avt-rtp-h264-10.txt
          draft-ietf-avt-uncomp-video-06
          draft-ietf-avt-rtp-retransmission-10
          draft-ietf-avt-tcrtp-07.txt
          draft-ietf-avt-hc-mpls-reqs-03.txt
          draft-ietf-avt-rtcp-feedback-11.txt
          draft-burmeister-avt-rtcp-feedback-sim-06.txt
          draft-jones-avt-audio-t38-05.txt

    RFC Editor:
          draft-ietf-avt-rtp-clearmode-05.txt
          draft-ietf-avt-rtp-dsr-codecs-03.txt
          draft-ietf-avt-rtp-ilbc-05.txt
          draft-ietf-avt-ilbc-codec-05.txt

    Individual drafts with AVT relation
          draft-lim-mpeg4-mime-02.txt
          draft-garudadri-avt-3gpp2-mime-00.txt
          draft-smundra-avt-rtp-red-non-audio-00.txt
          draft-wing-avt-rtp-noop-01.txt
          draft-luby-avt-rtp-generic-fec-00.txt


RTCP XR MIB                                         (Clark & Pendleton)
          draft-ietf-avt-rtcp-xr-mib-00.txt                        15 min

Open issues in RFC 2833bis                                     (Taylor)
          draft-ietf-avt-rfc2833bis-05.txt                         15 min

RTP Payload Format for JPEG 2000                                (Leung)
          draft-ietf-avt-jpeg2000-06.txt                           15 min

Far End Camera Control protocol                                  (Even)
          draft-even-avt-h224-00.txt                               15 min

RTP Payloads for Anti-shadow Redundancy                           (Xie)
          draft-xie-avt-rtp-anti-shadow-00.txt                     15 min


Thursday, 11 November 2004, 13:00-15:00
=======================================

Introduction                                                   (Chairs)
                                                                    5 min

RTP Profile for TCP Friendly Rate Control                      (Gharai)
          draft-ietf-avt-tfrc-profile-03.txt                       25 min

RTP Timestamp Usage for Variable Sample Rate Audio Codecs      (Chairs)
          draft-ietf-avt-variable-rate-audio-00.txt             (Wenger)
          Discussion on mailing list                               30 min

RTP Payload and File Format for VMR-WB                         (Ahmadi)
          draft-ietf-avt-vmr-wb-file-format-00.txt                 15 min
          draft-ietf-avt-rtp-vmr-wb-05.txt

RTP Payload Format for AMR and AMR-WB                      (Westerlund)
          draft-ietf-avt-rtp-amr-bis-00.txt                        15 min

RTP Payload Format for AMR-WB+                             (Westerlund)
          draft-ietf-avt-rtp-amrwbplus-02.txt                      15 min

                                  - * -



_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov  8 07:54:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00705
	for <avt-archive@ietf.org>; Mon, 8 Nov 2004 07:54:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CR92o-0007aS-Vc
	for avt-archive@ietf.org; Mon, 08 Nov 2004 07:54:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CR8wS-0001lx-PE; Mon, 08 Nov 2004 07:48:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CR8my-0000bx-H2
	for avt@megatron.ietf.org; Mon, 08 Nov 2004 07:38:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28790
	for <avt@ietf.org>; Mon, 8 Nov 2004 07:38:27 -0500 (EST)
Received: from s-utl01-dcpop.stsn.com ([63.240.218.73])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CR8nW-00077d-0a
	for avt@ietf.org; Mon, 08 Nov 2004 07:39:02 -0500
Received: from dcpop.smtp.stsn.com ([127.0.0.1])
	by s-utl01-dcpop.stsn.com (SAVSMTP 3.1.0.29) with SMTP id
	M2004110807380808475
	for <avt@ietf.org>; Mon, 08 Nov 2004 07:38:08 -0500
Received: from vit ([10.67.86.119]) by dcpop.smtp.stsn.com with Microsoft
	SMTPSVC(5.0.2195.6713); Mon, 8 Nov 2004 07:38:07 -0500
From: "Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se>
To: "Colin Perkins" <csp@csperkins.org>, "IETF AVT WG" <avt@ietf.org>
Subject: RE: [AVT] Updated AVT agenda for IETF 61 in Washington D.C.
Date: Mon, 8 Nov 2004 13:38:00 +0100
Message-ID: <GHEPIJKACEKDGLKODIGJCENMDGAA.gunnar.hellstrom@omnitor.se>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
In-Reply-To: <C908A25D-2E48-11D9-B2AB-000A957FC5F2@csperkins.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-OriginalArrivalTime: 08 Nov 2004 12:38:07.0930 (UTC)
	FILETIME=[CCBF49A0:01C4C58F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
Content-Transfer-Encoding: 7bit
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 42e3ed3f10a1d8bef690f09da16f507a
Content-Transfer-Encoding: 7bit

Colin,

I think also 

          draft-ietf-avt-text-red-05.txt 

should appear under AD or IESG evaluation.


Gunnar 
-------------------------------------------
Gunnar Hellstrom
Omnitor AB
Renathvagen 2
SE 121 37 Johanneshov
SWEDEN
+46 8 556 002 03
Mob: +46 708 204 288
www.omnitor.se
Gunnar.Hellstrom@Omnitor.se
-------------------------------------------- 
 

>-----Original Message-----
>From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]On Behalf Of
>Colin Perkins
>Sent: Thursday, November 04, 2004 11:04 AM
>To: IETF AVT WG
>Subject: Re: [AVT] Updated AVT agenda for IETF 61 in Washington D.C.
>
>
>Here's another revision to the agenda. This adds discussion of RTP 
>Payloads for Anti-shadow Redundancy to Wednesday, but makes no other 
>changes.
>
>Colin
>
>
>
>Audio/Video Transport Working Group
>
>CHAIRS: Colin Perkins     <csp@csperkins.org>
>         Magnus Westerlund <magnus.westerlund@ericsson.com>
>
>Wednesday, 10 November 2004, 13:00-15:00
>========================================
>
>Introduction and Status Update                                 (Chairs)
>                                                                 25 min
>    Under developement:
>          draft-ietf-avt-rtp-midi-format-06.txt
>          draft-ietf-avt-rtp-midi-guidelines-06.txt
>          draft-ietf-avt-rfc2032-bis-03.txt
>          draft-ietf-avt-rfc2429-bis-03.txt
>          draft-ietf-avt-rfc2190-to-historic-00.txt
>          draft-basso-avt-videoconreq-02.txt
>          draft-ietf-avt-rfc3119bis-03.txt
>          draft-finlayson-avt-mpa-robust-interoperability-01.txt
>          draft-ietf-avt-profile-savpf-01.txt
>          draft-ietf-avt-rtp-bv-01.txt
>          draft-ietf-avt-ulp-10.txt
>          draft-ietf-avt-uxp-07.txt
>          draft-ietf-avt-rtp-atrac-family-01.txt
>          draft-ietf-avt-rtcpssm-08.txt
>          draft-ietf-avt-3gpp-timed-text-07.txt
>          draft-ietf-avt-rtp-amrwbplus-02.txt
>          draft-ietf-avt-rtp-framing-contrans-03.txt
>
>    AD or IESG Evaluation
>          draft-ietf-avt-audio-t140c-00.txt
>          draft-ietf-avt-rfc2793bis-09.txt
>          draft-ietf-avt-rtp-h264-10.txt
>          draft-ietf-avt-uncomp-video-06
>          draft-ietf-avt-rtp-retransmission-10
>          draft-ietf-avt-tcrtp-07.txt
>          draft-ietf-avt-hc-mpls-reqs-03.txt
>          draft-ietf-avt-rtcp-feedback-11.txt
>          draft-burmeister-avt-rtcp-feedback-sim-06.txt
>          draft-jones-avt-audio-t38-05.txt
>
>    RFC Editor:
>          draft-ietf-avt-rtp-clearmode-05.txt
>          draft-ietf-avt-rtp-dsr-codecs-03.txt
>          draft-ietf-avt-rtp-ilbc-05.txt
>          draft-ietf-avt-ilbc-codec-05.txt
>
>    Individual drafts with AVT relation
>          draft-lim-mpeg4-mime-02.txt
>          draft-garudadri-avt-3gpp2-mime-00.txt
>          draft-smundra-avt-rtp-red-non-audio-00.txt
>          draft-wing-avt-rtp-noop-01.txt
>          draft-luby-avt-rtp-generic-fec-00.txt
>
>
>RTCP XR MIB                                         (Clark & Pendleton)
>          draft-ietf-avt-rtcp-xr-mib-00.txt                        15 min
>
>Open issues in RFC 2833bis                                     (Taylor)
>          draft-ietf-avt-rfc2833bis-05.txt                         15 min
>
>RTP Payload Format for JPEG 2000                                (Leung)
>          draft-ietf-avt-jpeg2000-06.txt                           15 min
>
>Far End Camera Control protocol                                  (Even)
>          draft-even-avt-h224-00.txt                               15 min
>
>RTP Payloads for Anti-shadow Redundancy                           (Xie)
>          draft-xie-avt-rtp-anti-shadow-00.txt                     15 min
>
>
>Thursday, 11 November 2004, 13:00-15:00
>=======================================
>
>Introduction                                                   (Chairs)
>                                                                    5 min
>
>RTP Profile for TCP Friendly Rate Control                      (Gharai)
>          draft-ietf-avt-tfrc-profile-03.txt                       25 min
>
>RTP Timestamp Usage for Variable Sample Rate Audio Codecs      (Chairs)
>          draft-ietf-avt-variable-rate-audio-00.txt             (Wenger)
>          Discussion on mailing list                               30 min
>
>RTP Payload and File Format for VMR-WB                         (Ahmadi)
>          draft-ietf-avt-vmr-wb-file-format-00.txt                 15 min
>          draft-ietf-avt-rtp-vmr-wb-05.txt
>
>RTP Payload Format for AMR and AMR-WB                      (Westerlund)
>          draft-ietf-avt-rtp-amr-bis-00.txt                        15 min
>
>                                  - * -
>
>
>_______________________________________________
>Audio/Video Transport Working Group
>avt@ietf.org
>https://www1.ietf.org/mailman/listinfo/avt
>
>


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov  8 17:23:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09897
	for <avt-archive@ietf.org>; Mon, 8 Nov 2004 17:23:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRHvt-0007yP-81
	for avt-archive@ietf.org; Mon, 08 Nov 2004 17:24:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRHiW-0005Rb-Bp; Mon, 08 Nov 2004 17:10:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRHVc-0002bW-Bl
	for avt@megatron.ietf.org; Mon, 08 Nov 2004 16:57:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07337
	for <avt@ietf.org>; Mon, 8 Nov 2004 16:57:05 -0500 (EST)
Received: from dns.packetdesign.com ([65.192.41.10]
	helo=mailman.packetdesign.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRHWD-0007Fw-KP
	for avt@ietf.org; Mon, 08 Nov 2004 16:57:47 -0500
Received: from packetdesign.com (main-fw-eth1.packetdesign.com [192.168.0.254])
	by mailman.packetdesign.com (8.12.8/8.12.8) with ESMTP id
	iA8LtPCJ021717; Mon, 8 Nov 2004 13:55:25 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Mon, 8 Nov 2004 13:55:54 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: audet@nortelnetworks.com, fluffy@cisco.com
Message-ID: <20041108124517.K54037@oak.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: AVT WG <avt@ietf.org>, ietf-behave@list.sipfoundry.org
Subject: [AVT] RTP in draft-ietf-behave-nat-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac

draft-ietf-behave-nat-00 contains the following statement:

   There is some very unfortunate
   wording in RFC 3550 section 11, which can cause some problematic
   behavior in RTP clients.  The wording could be interpreted as saying
   that if a client receives an odd port for sending RTP, it SHOULD
   change it to the next lower even number.  This would obviously result
   in the loss of RTP/UDP.

The actual text in RFC3550 is:

   For applications that take a single port number as a parameter and
   derive the RTP and RTCP port pair from that number, if an odd number
   is supplied then the application SHOULD replace that number with the
   next lower (even) number to use as the base of the port pair.  For
   applications in which the RTP and RTCP destination port numbers are
   specified via explicit, separate parameters (using a signaling
   protocol or other means), the application MAY disregard the
   restrictions that the port numbers be even/odd and consecutive
   although the use of an even/odd port pair is still encouraged.

The key here is that when a session description specifies only one
port number to convey the RTP+RTCP port pair, then the recipient of
that description needs to know how to determine the second port number
from the first.  It is critical that the sender and receiver (or
receivers plural for multicast) do this the same way.  Since the
convention is to use an even port for RTP and an odd port for RTCP,
the spec says that when the given port number is odd, the RTP SHOULD
be the next lower (even) number, and the odd number SHOULD be the RTCP
port.

However, because of requirements imposed by NATs and other
considerations, the second sentence in the above quote from RFC3550
was added.  All the applications need to do is explicitly state the
two port numbers, and then there is no restriction on the even/odd
condition of the RTP port number.

If your concern is that applications that do not implement RTCP will
only have one number to specify, then I have four responses:

  - If the application uses SDP to specify the session and gives only
    one address, this still implies that RTCP will be sent, so the
    RTCP port needs to be inferred from the single port that is given.
    In this case, I claim it makes sense for the stated rules to
    apply.

  - If you need to be able to use an odd RTP port number in sessions
    specified with SDP, then specify another port for RTCP but don't
    use it.  I believe it would be acceptable for that other port
    number to be zero.

  - If the application will specify its session some other way, and
    intends to specify only a single port with the implicatin that
    RTCP will not be sent, then the specification of that session
    description method can specify that the SHOULD above be
    overridden.

  - Designing out RTCP is bad.


draft-ietf-behave-nat-00 also contains the following statement:

   NATs that use an "IP address pooling" behavior of "arbitrary" can
   cause issues for applications that use multiple ports from the same
   endpoint but have no way to negotiate IP addresses individually
   (e.g., RTP and RTCP ports).

RFC 3605, "Real Time Control Protocol (RTCP) attribute in Session
Description Protocol (SDP)" specifies a means to negotiate an
alternate IP address for RTCP as well as a port number.

                                                        -- Steve

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov  8 18:00:53 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14344
	for <avt-archive@ietf.org>; Mon, 8 Nov 2004 18:00:53 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRIVx-0000fm-KL
	for avt-archive@ietf.org; Mon, 08 Nov 2004 18:01:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRIMO-00083P-Gw; Mon, 08 Nov 2004 17:51:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRI7R-0004JV-5Y
	for avt@megatron.ietf.org; Mon, 08 Nov 2004 17:36:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11213
	for <avt@ietf.org>; Mon, 8 Nov 2004 17:36:10 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRI83-0008Lo-Pd for avt@ietf.org; Mon, 08 Nov 2004 17:36:52 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 08 Nov 2004 14:49:17 -0800
X-BrightmailFiltered: true
Received: from edison.cisco.com (edison.cisco.com [171.71.180.109])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iA8MZccp002858;
	Mon, 8 Nov 2004 14:35:39 -0800 (PST)
Received: from DWINGW2K4 (sjc-vpn1-576.cisco.com [10.21.98.64]) by
	edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with
	SMTP id OAA01064; Mon, 8 Nov 2004 14:35:37 -0800 (PST)
From: "Dan Wing" <dwing@cisco.com>
To: "Stephen Casner" <casner@acm.org>, <audet@nortelnetworks.com>,
        <fluffy@cisco.com>
Date: Mon, 8 Nov 2004 14:35:37 -0800
Message-ID: <LIECKHBKICJFBLOMPHNMOEENNLAA.dwing@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <20041108124517.K54037@oak.packetdesign.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Content-Transfer-Encoding: 7bit
Cc: AVT WG <avt@ietf.org>, ietf-behave@list.sipfoundry.org
Subject: [AVT] RE: [Ietf-behave] RTP in draft-ietf-behave-nat-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Content-Transfer-Encoding: 7bit

Stephen, 

Thanks for reviewing the document.

To your first point,
I believe we resolved this, in a positive way, on the list; -00 doesn't
yet reflect those changes.  We decided to require NATs to preserve
even and odd port numbers when they create their UDP bindings, as this
provides the best interoperability for RTP applications that don't/can't
provide explicit signaling of their RTCP port.

To your second, a reference to RFC3605 will be added to the 'application
behavior' document, which will describe how applications should behave.
The current BEHAVE document just describes how NATs should behave.

-d

> -----Original Message-----
> From: ietf-behave-bounces@list.sipfoundry.org
> [mailto:ietf-behave-bounces@list.sipfoundry.org]On Behalf Of Stephen
> Casner
> Sent: Monday, November 08, 2004 1:56 PM
> To: audet@nortelnetworks.com; fluffy@cisco.com
> Cc: AVT WG; ietf-behave@list.sipfoundry.org
> Subject: [Ietf-behave] RTP in draft-ietf-behave-nat-00
> 
> 
> draft-ietf-behave-nat-00 contains the following statement:
> 
>    There is some very unfortunate
>    wording in RFC 3550 section 11, which can cause some problematic
>    behavior in RTP clients.  The wording could be interpreted as saying
>    that if a client receives an odd port for sending RTP, it SHOULD
>    change it to the next lower even number.  This would obviously result
>    in the loss of RTP/UDP.
> 
> The actual text in RFC3550 is:
> 
>    For applications that take a single port number as a parameter and
>    derive the RTP and RTCP port pair from that number, if an odd number
>    is supplied then the application SHOULD replace that number with the
>    next lower (even) number to use as the base of the port pair.  For
>    applications in which the RTP and RTCP destination port numbers are
>    specified via explicit, separate parameters (using a signaling
>    protocol or other means), the application MAY disregard the
>    restrictions that the port numbers be even/odd and consecutive
>    although the use of an even/odd port pair is still encouraged.
> 
> The key here is that when a session description specifies only one
> port number to convey the RTP+RTCP port pair, then the recipient of
> that description needs to know how to determine the second port number
> from the first.  It is critical that the sender and receiver (or
> receivers plural for multicast) do this the same way.  Since the
> convention is to use an even port for RTP and an odd port for RTCP,
> the spec says that when the given port number is odd, the RTP SHOULD
> be the next lower (even) number, and the odd number SHOULD be the RTCP
> port.
> 
> However, because of requirements imposed by NATs and other
> considerations, the second sentence in the above quote from RFC3550
> was added.  All the applications need to do is explicitly state the
> two port numbers, and then there is no restriction on the even/odd
> condition of the RTP port number.
> 
> If your concern is that applications that do not implement RTCP will
> only have one number to specify, then I have four responses:
> 
>   - If the application uses SDP to specify the session and gives only
>     one address, this still implies that RTCP will be sent, so the
>     RTCP port needs to be inferred from the single port that is given.
>     In this case, I claim it makes sense for the stated rules to
>     apply.
> 
>   - If you need to be able to use an odd RTP port number in sessions
>     specified with SDP, then specify another port for RTCP but don't
>     use it.  I believe it would be acceptable for that other port
>     number to be zero.
> 
>   - If the application will specify its session some other way, and
>     intends to specify only a single port with the implicatin that
>     RTCP will not be sent, then the specification of that session
>     description method can specify that the SHOULD above be
>     overridden.
> 
>   - Designing out RTCP is bad.
> 
> 
> draft-ietf-behave-nat-00 also contains the following statement:
> 
>    NATs that use an "IP address pooling" behavior of "arbitrary" can
>    cause issues for applications that use multiple ports from the same
>    endpoint but have no way to negotiate IP addresses individually
>    (e.g., RTP and RTCP ports).
> 
> RFC 3605, "Real Time Control Protocol (RTCP) attribute in Session
> Description Protocol (SDP)" specifies a means to negotiate an
> alternate IP address for RTCP as well as a port number.
> 
>                                                         -- Steve
> _______________________________________________
> Ietf-behave mailing list
> Ietf-behave@list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/ietf-behave

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov  8 20:42:23 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29751
	for <avt-archive@ietf.org>; Mon, 8 Nov 2004 20:42:23 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRL26-0004ct-PW
	for avt-archive@ietf.org; Mon, 08 Nov 2004 20:43:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRKzB-00077B-0v; Mon, 08 Nov 2004 20:39:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRKqV-0005J8-2K
	for avt@megatron.ietf.org; Mon, 08 Nov 2004 20:30:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28529
	for <avt@ietf.org>; Mon, 8 Nov 2004 20:30:53 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRKqx-0004KQ-SH
	for avt@ietf.org; Mon, 08 Nov 2004 20:31:35 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iA91UfR2032003 for <avt@ietf.org>; Tue, 9 Nov 2004 02:30:41 +0100
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 9 Nov 2004 02:30:41 +0100
Received: from [147.214.97.151] (permit151.er.ki.sw.ericsson.se
	[147.214.97.151]) by esealnt610.al.sw.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id WFZH0PXW; Tue, 9 Nov 2004 02:30:40 +0100
Message-ID: <41901DBF.10905@ericsson.com>
Date: Tue, 09 Nov 2004 02:30:39 +0100
X-Sybari-Trust: b48bfaba ad48f3dd e0f215c2 00000179
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>, Colin Perkins <csp@csperkins.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Nov 2004 01:30:41.0179 (UTC)
	FILETIME=[B96FC6B0:01C4C5FB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
Subject: [AVT] Slides for AVT
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit

Hi,

Anyone having a presentation in AVT MUST send the chairs their slides, 
before 21.30 EST the day before their presentation. Thus the ones having 
agenda time on Wednesday time needs to send the slides before 21.30 on 
Tuesday.

Cheers

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov  8 21:16:53 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03326
	for <avt-archive@ietf.org>; Mon, 8 Nov 2004 21:16:53 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRLZg-0005Rf-JU
	for avt-archive@ietf.org; Mon, 08 Nov 2004 21:17:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRLXC-0005mB-JK; Mon, 08 Nov 2004 21:15:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRLTP-0005Fw-T3
	for avt@megatron.ietf.org; Mon, 08 Nov 2004 21:11:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02754
	for <avt@ietf.org>; Mon, 8 Nov 2004 21:11:05 -0500 (EST)
Received: from dns.packetdesign.com ([65.192.41.10]
	helo=mailman.packetdesign.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRLU3-0005JT-DT
	for avt@ietf.org; Mon, 08 Nov 2004 21:11:48 -0500
Received: from packetdesign.com (main-fw-eth1.packetdesign.com [192.168.0.254])
	by mailman.packetdesign.com (8.12.8/8.12.8) with ESMTP id
	iA92ANCJ035515; Mon, 8 Nov 2004 18:10:28 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Mon, 8 Nov 2004 18:10:54 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: Francois Audet <audet@nortelnetworks.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCFF66368@zrc2hxm0.corp.nortel.com>
Message-ID: <20041108174651.T54245@oak.packetdesign.com>
References: <1ECE0EB50388174790F9694F77522CCFF66368@zrc2hxm0.corp.nortel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: "'fluffy@cisco.com'" <fluffy@cisco.com>,
        "'ietf-behave@list.sipfoundry.org'" <ietf-behave@list.sipfoundry.org>,
        "'AVT WG'" <avt@ietf.org>, "'Dan Wing'" <dwing@cisco.com>
Subject: [AVT] RE: [Ietf-behave] RTP in draft-ietf-behave-nat-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a

On Mon, 8 Nov 2004, Francois Audet wrote:

> Dan is correct.
>
> We are not looking at implementations that don't support RTCP. This is not
> what we were trying to address.

Good.

> We were looking at applications that, upon receiving an
> instruction to send RTP to an odd address would interpret the RFC 3550
> wording to say that it should send it to the the even address that is
> one lower than the one advertized (which would break protocols such
> as SIP/SDP).

If a SIP/SDP application receives instructions to send RTP to an odd
address (that is, port) when the SDP does not include an a=rtcp
attribute (RFC 3605) to specify the RTCP port separately, then indeed,
RFC 3550 does say that the RTP should be sent to the even port that is
one lower.  But, I claim this SIP/SDP application is broken if it was
expecting the application to send RTP on the odd port and RTCP on the
next higher even port (or maybe the next lower even port, or even the
odd port two higher).  Do you disagree?

                                                        -- Steve

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov  8 21:27:32 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04388
	for <avt-archive@ietf.org>; Mon, 8 Nov 2004 21:27:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRLjz-0005fU-AN
	for avt-archive@ietf.org; Mon, 08 Nov 2004 21:28:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRLiO-0001ov-43; Mon, 08 Nov 2004 21:26:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRKfA-0000BU-NO
	for avt@megatron.ietf.org; Mon, 08 Nov 2004 20:19:12 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27456
	for <avt@ietf.org>; Mon, 8 Nov 2004 20:19:10 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRKfm-00044F-Fy
	for avt@ietf.org; Mon, 08 Nov 2004 20:19:53 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iA91Iav01646; Mon, 8 Nov 2004 20:18:36 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WP4QN1XF>; Mon, 8 Nov 2004 20:18:37 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCFF66368@zrc2hxm0.corp.nortel.com>
From: "Francois Audet" <audet@nortelnetworks.com>
To: "'Dan Wing'" <dwing@cisco.com>, "'Stephen Casner'" <casner@acm.org>,
        "'fluffy@cisco.com'" <fluffy@cisco.com>
Date: Mon, 8 Nov 2004 20:18:25 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.8 (/)
X-Scan-Signature: b5216aa5b0df24d46eaed76d4f65aa31
X-Mailman-Approved-At: Mon, 08 Nov 2004 21:26:34 -0500
Cc: "'AVT WG'" <avt@ietf.org>,
        "'ietf-behave@list.sipfoundry.org'" <ietf-behave@list.sipfoundry.org>
Subject: [AVT] RE: [Ietf-behave] RTP in draft-ietf-behave-nat-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1274020656=="
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: fbe0995f04cc21309ef8614a2838e306

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============1274020656==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C5FA.0428D0A3"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C4C5FA.0428D0A3
Content-Type: text/plain

Dan is correct.

We are not looking at implementations that don't support RTCP. This is not
what we were trying to address.

We were looking at applications that, upon receiving an 
instruction to send RTP to an odd address would interpret the RFC 3550 
wording to say that it should send it to the the even address that is 
one lower than the one advertized (which would break protocols such
as SIP/SDP).

> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com] 
> Sent: Monday, November 08, 2004 14:36
> To: Stephen Casner; Audet, Francois [SC100:9T51:EXCH]; 
> fluffy@cisco.com
> Cc: AVT WG; ietf-behave@list.sipfoundry.org
> Subject: RE: [Ietf-behave] RTP in draft-ietf-behave-nat-00
> 
> 
> Stephen, 
> 
> Thanks for reviewing the document.
> 
> To your first point,
> I believe we resolved this, in a positive way, on the list; 
> -00 doesn't yet reflect those changes.  We decided to require 
> NATs to preserve even and odd port numbers when they create 
> their UDP bindings, as this provides the best 
> interoperability for RTP applications that don't/can't 
> provide explicit signaling of their RTCP port.
> 
> To your second, a reference to RFC3605 will be added to the 
> 'application behavior' document, which will describe how 
> applications should behave. The current BEHAVE document just 
> describes how NATs should behave.
> 
> -d
> 
> > -----Original Message-----
> > From: ietf-behave-bounces@list.sipfoundry.org
> > [mailto:ietf-behave-bounces@list.sipfoundry.org]On Behalf 
> Of Stephen 
> > Casner
> > Sent: Monday, November 08, 2004 1:56 PM
> > To: audet@nortelnetworks.com; fluffy@cisco.com
> > Cc: AVT WG; ietf-behave@list.sipfoundry.org
> > Subject: [Ietf-behave] RTP in draft-ietf-behave-nat-00
> > 
> > 
> > draft-ietf-behave-nat-00 contains the following statement:
> > 
> >    There is some very unfortunate
> >    wording in RFC 3550 section 11, which can cause some problematic
> >    behavior in RTP clients.  The wording could be 
> interpreted as saying
> >    that if a client receives an odd port for sending RTP, it SHOULD
> >    change it to the next lower even number.  This would 
> obviously result
> >    in the loss of RTP/UDP.
> > 
> > The actual text in RFC3550 is:
> > 
> >    For applications that take a single port number as a 
> parameter and
> >    derive the RTP and RTCP port pair from that number, if 
> an odd number
> >    is supplied then the application SHOULD replace that 
> number with the
> >    next lower (even) number to use as the base of the port 
> pair.  For
> >    applications in which the RTP and RTCP destination port 
> numbers are
> >    specified via explicit, separate parameters (using a signaling
> >    protocol or other means), the application MAY disregard the
> >    restrictions that the port numbers be even/odd and consecutive
> >    although the use of an even/odd port pair is still encouraged.
> > 
> > The key here is that when a session description specifies only one 
> > port number to convey the RTP+RTCP port pair, then the recipient of 
> > that description needs to know how to determine the second 
> port number 
> > from the first.  It is critical that the sender and receiver (or 
> > receivers plural for multicast) do this the same way.  Since the 
> > convention is to use an even port for RTP and an odd port for RTCP, 
> > the spec says that when the given port number is odd, the 
> RTP SHOULD 
> > be the next lower (even) number, and the odd number SHOULD 
> be the RTCP 
> > port.
> > 
> > However, because of requirements imposed by NATs and other 
> > considerations, the second sentence in the above quote from RFC3550 
> > was added.  All the applications need to do is explicitly state the 
> > two port numbers, and then there is no restriction on the even/odd 
> > condition of the RTP port number.
> > 
> > If your concern is that applications that do not implement 
> RTCP will 
> > only have one number to specify, then I have four responses:
> > 
> >   - If the application uses SDP to specify the session and 
> gives only
> >     one address, this still implies that RTCP will be sent, so the
> >     RTCP port needs to be inferred from the single port 
> that is given.
> >     In this case, I claim it makes sense for the stated rules to
> >     apply.
> > 
> >   - If you need to be able to use an odd RTP port number in sessions
> >     specified with SDP, then specify another port for RTCP but don't
> >     use it.  I believe it would be acceptable for that other port
> >     number to be zero.
> > 
> >   - If the application will specify its session some other way, and
> >     intends to specify only a single port with the implicatin that
> >     RTCP will not be sent, then the specification of that session
> >     description method can specify that the SHOULD above be
> >     overridden.
> > 
> >   - Designing out RTCP is bad.
> > 
> > 
> > draft-ietf-behave-nat-00 also contains the following statement:
> > 
> >    NATs that use an "IP address pooling" behavior of "arbitrary" can
> >    cause issues for applications that use multiple ports 
> from the same
> >    endpoint but have no way to negotiate IP addresses individually
> >    (e.g., RTP and RTCP ports).
> > 
> > RFC 3605, "Real Time Control Protocol (RTCP) attribute in Session 
> > Description Protocol (SDP)" specifies a means to negotiate an 
> > alternate IP address for RTCP as well as a port number.
> > 
> >                                                         -- Steve 
> > _______________________________________________
> > Ietf-behave mailing list
> > Ietf-behave@list.sipfoundry.org 
> > https://list.sipfoundry.org/mailman/listinfo/ietf-behave
> 
> 

------_=_NextPart_001_01C4C5FA.0428D0A3
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>RE: [Ietf-behave] RTP in draft-ietf-behave-nat-00</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Dan is correct.</FONT>
</P>

<P><FONT SIZE=3D2>We are not looking at implementations that don't =
support RTCP. This is not</FONT>
<BR><FONT SIZE=3D2>what we were trying to address.</FONT>
</P>

<P><FONT SIZE=3D2>We were looking at applications that, upon receiving =
an </FONT>
<BR><FONT SIZE=3D2>instruction to send RTP to an odd address would =
interpret the RFC 3550 </FONT>
<BR><FONT SIZE=3D2>wording to say that it should send it to the the =
even address that is </FONT>
<BR><FONT SIZE=3D2>one lower than the one advertized (which would break =
protocols such</FONT>
<BR><FONT SIZE=3D2>as SIP/SDP).</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Dan Wing [<A =
HREF=3D"mailto:dwing@cisco.com">mailto:dwing@cisco.com</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Monday, November 08, 2004 14:36</FONT>
<BR><FONT SIZE=3D2>&gt; To: Stephen Casner; Audet, Francois =
[SC100:9T51:EXCH]; </FONT>
<BR><FONT SIZE=3D2>&gt; fluffy@cisco.com</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: AVT WG; =
ietf-behave@list.sipfoundry.org</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [Ietf-behave] RTP in =
draft-ietf-behave-nat-00</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Stephen, </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Thanks for reviewing the document.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; To your first point,</FONT>
<BR><FONT SIZE=3D2>&gt; I believe we resolved this, in a positive way, =
on the list; </FONT>
<BR><FONT SIZE=3D2>&gt; -00 doesn't yet reflect those changes.&nbsp; We =
decided to require </FONT>
<BR><FONT SIZE=3D2>&gt; NATs to preserve even and odd port numbers when =
they create </FONT>
<BR><FONT SIZE=3D2>&gt; their UDP bindings, as this provides the best =
</FONT>
<BR><FONT SIZE=3D2>&gt; interoperability for RTP applications that =
don't/can't </FONT>
<BR><FONT SIZE=3D2>&gt; provide explicit signaling of their RTCP =
port.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; To your second, a reference to RFC3605 will be =
added to the </FONT>
<BR><FONT SIZE=3D2>&gt; 'application behavior' document, which will =
describe how </FONT>
<BR><FONT SIZE=3D2>&gt; applications should behave. The current BEHAVE =
document just </FONT>
<BR><FONT SIZE=3D2>&gt; describes how NATs should behave.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -d</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; From: =
ietf-behave-bounces@list.sipfoundry.org</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; [<A =
HREF=3D"mailto:ietf-behave-bounces@list.sipfoundry.org">mailto:ietf-beha=
ve-bounces@list.sipfoundry.org</A>]On Behalf </FONT>
<BR><FONT SIZE=3D2>&gt; Of Stephen </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Casner</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sent: Monday, November 08, 2004 1:56 =
PM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; To: audet@nortelnetworks.com; =
fluffy@cisco.com</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Cc: AVT WG; =
ietf-behave@list.sipfoundry.org</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Subject: [Ietf-behave] RTP in =
draft-ietf-behave-nat-00</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; draft-ietf-behave-nat-00 contains the =
following statement:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; There is some very =
unfortunate</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; wording in RFC 3550 =
section 11, which can cause some problematic</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; behavior in RTP =
clients.&nbsp; The wording could be </FONT>
<BR><FONT SIZE=3D2>&gt; interpreted as saying</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; that if a client =
receives an odd port for sending RTP, it SHOULD</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; change it to the next =
lower even number.&nbsp; This would </FONT>
<BR><FONT SIZE=3D2>&gt; obviously result</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; in the loss of =
RTP/UDP.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; The actual text in RFC3550 is:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; For applications that =
take a single port number as a </FONT>
<BR><FONT SIZE=3D2>&gt; parameter and</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; derive the RTP and RTCP =
port pair from that number, if </FONT>
<BR><FONT SIZE=3D2>&gt; an odd number</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; is supplied then the =
application SHOULD replace that </FONT>
<BR><FONT SIZE=3D2>&gt; number with the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; next lower (even) number =
to use as the base of the port </FONT>
<BR><FONT SIZE=3D2>&gt; pair.&nbsp; For</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; applications in which =
the RTP and RTCP destination port </FONT>
<BR><FONT SIZE=3D2>&gt; numbers are</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; specified via explicit, =
separate parameters (using a signaling</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; protocol or other =
means), the application MAY disregard the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; restrictions that the =
port numbers be even/odd and consecutive</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; although the use of an =
even/odd port pair is still encouraged.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; The key here is that when a session =
description specifies only one </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; port number to convey the RTP+RTCP port =
pair, then the recipient of </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; that description needs to know how to =
determine the second </FONT>
<BR><FONT SIZE=3D2>&gt; port number </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; from the first.&nbsp; It is critical that =
the sender and receiver (or </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; receivers plural for multicast) do this =
the same way.&nbsp; Since the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; convention is to use an even port for RTP =
and an odd port for RTCP, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the spec says that when the given port =
number is odd, the </FONT>
<BR><FONT SIZE=3D2>&gt; RTP SHOULD </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; be the next lower (even) number, and the =
odd number SHOULD </FONT>
<BR><FONT SIZE=3D2>&gt; be the RTCP </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; port.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; However, because of requirements imposed =
by NATs and other </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; considerations, the second sentence in the =
above quote from RFC3550 </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; was added.&nbsp; All the applications need =
to do is explicitly state the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; two port numbers, and then there is no =
restriction on the even/odd </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; condition of the RTP port number.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; If your concern is that applications that =
do not implement </FONT>
<BR><FONT SIZE=3D2>&gt; RTCP will </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; only have one number to specify, then I =
have four responses:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; - If the application uses SDP =
to specify the session and </FONT>
<BR><FONT SIZE=3D2>&gt; gives only</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; one address, this =
still implies that RTCP will be sent, so the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; RTCP port needs to =
be inferred from the single port </FONT>
<BR><FONT SIZE=3D2>&gt; that is given.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; In this case, I =
claim it makes sense for the stated rules to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; apply.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; - If you need to be able to =
use an odd RTP port number in sessions</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; specified with =
SDP, then specify another port for RTCP but don't</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; use it.&nbsp; I =
believe it would be acceptable for that other port</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; number to be =
zero.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; - If the application will =
specify its session some other way, and</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; intends to specify =
only a single port with the implicatin that</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; RTCP will not be =
sent, then the specification of that session</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; description method =
can specify that the SHOULD above be</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; overridden.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; - Designing out RTCP is =
bad.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; draft-ietf-behave-nat-00 also contains the =
following statement:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; NATs that use an =
&quot;IP address pooling&quot; behavior of &quot;arbitrary&quot; =
can</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; cause issues for =
applications that use multiple ports </FONT>
<BR><FONT SIZE=3D2>&gt; from the same</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; endpoint but have no way =
to negotiate IP addresses individually</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; (e.g., RTP and RTCP =
ports).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; RFC 3605, &quot;Real Time Control Protocol =
(RTCP) attribute in Session </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Description Protocol (SDP)&quot; specifies =
a means to negotiate an </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; alternate IP address for RTCP as well as a =
port number.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Steve </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Ietf-behave mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Ietf-behave@list.sipfoundry.org </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; <A =
HREF=3D"https://list.sipfoundry.org/mailman/listinfo/ietf-behave" =
TARGET=3D"_blank">https://list.sipfoundry.org/mailman/listinfo/ietf-beha=
ve</A></FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C4C5FA.0428D0A3--


--===============1274020656==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

--===============1274020656==--



From avt-bounces@ietf.org  Mon Nov  8 21:56:15 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06574
	for <avt-archive@ietf.org>; Mon, 8 Nov 2004 21:56:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRMBm-0006Eo-Nf
	for avt-archive@ietf.org; Mon, 08 Nov 2004 21:56:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRM1Q-0006r3-T5; Mon, 08 Nov 2004 21:46:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRLuL-0003o2-AU
	for avt@megatron.ietf.org; Mon, 08 Nov 2004 21:38:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05227
	for <avt@ietf.org>; Mon, 8 Nov 2004 21:38:54 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRLuz-0005r6-UQ
	for avt@ietf.org; Mon, 08 Nov 2004 21:39:38 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iA92cNE07275; Mon, 8 Nov 2004 21:38:23 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WP4QN3ZC>; Mon, 8 Nov 2004 21:38:24 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCFF6638B@zrc2hxm0.corp.nortel.com>
From: "Francois Audet" <audet@nortelnetworks.com>
To: "'Stephen Casner'" <casner@acm.org>
Date: Mon, 8 Nov 2004 21:38:08 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: "'fluffy@cisco.com'" <fluffy@cisco.com>,
        "'ietf-behave@list.sipfoundry.org'" <ietf-behave@list.sipfoundry.org>,
        "'AVT WG'" <avt@ietf.org>, "'Dan Wing'" <dwing@cisco.com>
Subject: [AVT] RE: [Ietf-behave] RTP in draft-ietf-behave-nat-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0460190736=="
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============0460190736==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C605.26E52F0C"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C4C605.26E52F0C
Content-Type: text/plain



> If a SIP/SDP application receives instructions to send RTP to 
> an odd address (that is, port) when the SDP does not include 
> an a=rtcp attribute (RFC 3605) to specify the RTCP port 
> separately, then indeed, RFC 3550 does say that the RTP 
> should be sent to the even port that is one lower.  But, I 
> claim this SIP/SDP application is broken if it was expecting 
> the application to send RTP on the odd port and RTCP on the 
> next higher even port (or maybe the next lower even port, or 
> even the odd port two higher).  Do you disagree?

No, I do not disagree. In fact, I completely agree with you. 
The simple odd/even rule that we are adding does NOT address the port
contiguity rule (and we've added wording on that that you haven't 
seen yet for the next release).

This is one of the many reason why the next thing we do after
the NAT Behavior document (for UDP Unicast, then Multicast and
TCP) is the "Application" document which will explain all this.

I think it will be very important to have a review of
the upcoming Application document from AVT (at least for those
aspects related to RTP/RTCP. We will definitively seek your feedback.

Again, really what we were looking at addressing is the "substract
one to the odd port" statement (which one could read as applying
even if both the RTP and RTCP ports are seperately negotiated).
We are just ensuring that a NAT will not change the parity.


------_=_NextPart_001_01C4C605.26E52F0C
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2658.2">
<TITLE>RE: [Ietf-behave] RTP in draft-ietf-behave-nat-00</TITLE>
</HEAD>
<BODY>
<BR>
<BR>

<P><FONT SIZE=2>&gt; If a SIP/SDP application receives instructions to send RTP to </FONT>
<BR><FONT SIZE=2>&gt; an odd address (that is, port) when the SDP does not include </FONT>
<BR><FONT SIZE=2>&gt; an a=rtcp attribute (RFC 3605) to specify the RTCP port </FONT>
<BR><FONT SIZE=2>&gt; separately, then indeed, RFC 3550 does say that the RTP </FONT>
<BR><FONT SIZE=2>&gt; should be sent to the even port that is one lower.&nbsp; But, I </FONT>
<BR><FONT SIZE=2>&gt; claim this SIP/SDP application is broken if it was expecting </FONT>
<BR><FONT SIZE=2>&gt; the application to send RTP on the odd port and RTCP on the </FONT>
<BR><FONT SIZE=2>&gt; next higher even port (or maybe the next lower even port, or </FONT>
<BR><FONT SIZE=2>&gt; even the odd port two higher).&nbsp; Do you disagree?</FONT>
</P>

<P><FONT SIZE=2>No, I do not disagree. In fact, I completely agree with you. </FONT>
<BR><FONT SIZE=2>The simple odd/even rule that we are adding does NOT address the port</FONT>
<BR><FONT SIZE=2>contiguity rule (and we've added wording on that that you haven't </FONT>
<BR><FONT SIZE=2>seen yet for the next release).</FONT>
</P>

<P><FONT SIZE=2>This is one of the many reason why the next thing we do after</FONT>
<BR><FONT SIZE=2>the NAT Behavior document (for UDP Unicast, then Multicast and</FONT>
<BR><FONT SIZE=2>TCP) is the &quot;Application&quot; document which will explain all this.</FONT>
</P>

<P><FONT SIZE=2>I think it will be very important to have a review of</FONT>
<BR><FONT SIZE=2>the upcoming Application document from AVT (at least for those</FONT>
<BR><FONT SIZE=2>aspects related to RTP/RTCP. We will definitively seek your feedback.</FONT>
</P>

<P><FONT SIZE=2>Again, really what we were looking at addressing is the &quot;substract</FONT>
<BR><FONT SIZE=2>one to the odd port&quot; statement (which one could read as applying</FONT>
<BR><FONT SIZE=2>even if both the RTP and RTCP ports are seperately negotiated).</FONT>
<BR><FONT SIZE=2>We are just ensuring that a NAT will not change the parity.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C4C605.26E52F0C--


--===============0460190736==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

--===============0460190736==--



From avt-bounces@ietf.org  Tue Nov  9 23:49:15 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23112
	for <avt-archive@ietf.org>; Tue, 9 Nov 2004 23:49:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRkQv-0007yU-QS
	for avt-archive@ietf.org; Tue, 09 Nov 2004 23:50:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRkPA-0005DB-6C; Tue, 09 Nov 2004 23:48:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRkL8-0004fW-Gj
	for avt@megatron.ietf.org; Tue, 09 Nov 2004 23:44:14 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22629;
	Tue, 9 Nov 2004 23:44:09 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRkLw-0007pz-0c; Tue, 09 Nov 2004 23:45:07 -0500
Received: from [130.129.135.72] (port=63549 helo=[130.129.135.72])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1CRkKT-0000CE-QZ; Wed, 10 Nov 2004 04:43:33 +0000
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <11C8235B-32D3-11D9-8187-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Date: Tue, 9 Nov 2004 23:43:30 -0500
To: avt@ietf.org
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Content-Transfer-Encoding: 7bit
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, agenda@ietf.org
Subject: [AVT] Updated AVT agenda
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Content-Transfer-Encoding: 7bit

Enclosed is a slightly updated AVT agenda, correcting the draft names  
and version numbers (the previous versions referred to old drafts by  
mistake). Apologies for the trouble.

Colin



======================================================================== 
=====
Audio/Video Transport Working Group

CHAIRS: Colin Perkins     <csp@csperkins.org>
         Magnus Westerlund <magnus.westerlund@ericsson.com>

Wednesday, 10 November 2004, 13:00-15:00
========================================

Introduction and Status Update                                 (Chairs)
                                                                 25 min
    Under developement:
          draft-ietf-avt-rtp-midi-format-06.txt
          draft-ietf-avt-rtp-midi-guidelines-06.txt
          draft-ietf-avt-rfc2032-bis-03.txt
          draft-ietf-avt-rfc2429-bis-03.txt
          draft-ietf-avt-rfc2190-to-historic-00.txt
          draft-basso-avt-videoconreq-02.txt
          draft-ietf-avt-rfc3119bis-03.txt
          draft-finlayson-avt-mpa-robust-interoperability-01.txt
          draft-ietf-avt-profile-savpf-01.txt
          draft-ietf-avt-rtp-bv-01.txt
          draft-ietf-avt-ulp-10.txt
          draft-ietf-avt-uxp-07.txt
          draft-ietf-avt-rtp-atrac-family-01.txt
          draft-ietf-avt-rtcpssm-08.txt
          draft-ietf-avt-rtp-3gpp-timed-text-07.txt
          draft-ietf-avt-rtp-amrwbplus-02.txt
          draft-ietf-avt-rtp-framing-contrans-03.txt

    AD or IESG Evaluation
          draft-ietf-avt-audio-t140c-00.txt
          draft-ietf-avt-rfc2793bis-09.txt
          draft-ietf-avt-rtp-h264-11.txt
          draft-ietf-avt-uncomp-video-06.txt
          draft-ietf-avt-rtp-retransmission-10.txt
          draft-ietf-avt-tcrtp-08.txt
          draft-ietf-avt-hc-mpls-reqs-03.txt
          draft-ietf-avt-rtcp-feedback-11.txt
          draft-burmeister-avt-rtcp-feedback-sim-06.txt
          draft-jones-avt-audio-t38-05.txt
          draft-ietf-avt-text-red-05.txt

    RFC Editor:
          draft-ietf-avt-rtp-clearmode-05.txt
          draft-ietf-avt-rtp-dsr-codecs-03.txt
          draft-ietf-avt-rtp-ilbc-05.txt
          draft-ietf-avt-ilbc-codec-05.txt

    Individual drafts with AVT relation
          draft-lim-mpeg4-mime-02.txt
          draft-garudadri-avt-3gpp2-mime-00.txt
          draft-smundra-avt-rtp-red-non-audio-00.txt
          draft-wing-avt-rtp-noop-01.txt
          draft-luby-avt-rtp-generic-fec-00.txt


RTCP XR MIB                                         (Clark & Pendleton)
          draft-ietf-avt-rtcp-xr-mib-00.txt                        15 min

Open issues in RFC 2833bis                                     (Taylor)
          draft-ietf-avt-rfc2833bis-05.txt                         15 min

RTP Payload Format for JPEG 2000                                (Leung)
          draft-ietf-avt-rtp-jpeg2000-06.txt                       15 min

Far End Camera Control protocol                                  (Even)
          draft-even-avt-h224-00.txt                               15 min

RTP Payloads for Anti-shadow Redundancy                           (Xie)
          draft-xie-avt-rtp-anti-shadow-00.txt                     15 min


Thursday, 11 November 2004, 13:00-15:00
=======================================

Introduction                                                   (Chairs)
                                                                    5 min

RTP Profile for TCP Friendly Rate Control                      (Gharai)
          draft-ietf-avt-tfrc-profile-03.txt                       25 min

RTP Timestamp Usage for Variable Sample Rate Audio Codecs      (Chairs)
          draft-ietf-avt-variable-rate-audio-00.txt             (Wenger)
          Discussion on mailing list                               30 min

RTP Payload and File Format for VMR-WB                         (Ahmadi)
          draft-ietf-avt-vmr-wb-file-format-00.txt                 15 min
          draft-ietf-avt-rtp-vmr-wb-05.txt

RTP Payload Format for AMR and AMR-WB                      (Westerlund)
          draft-ietf-avt-rtp-amr-bis-00.txt                        15 min

RTP Payload Format for AMR-WB+                             (Westerlund)
          draft-ietf-avt-rtp-amrwbplus-02.txt                      15 min

                                  - * -


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 10 12:32:49 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04223
	for <avt-archive@ietf.org>; Wed, 10 Nov 2004 12:32:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRwLy-0008HZ-Kj
	for avt-archive@ietf.org; Wed, 10 Nov 2004 12:33:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRwHa-00085v-R6; Wed, 10 Nov 2004 12:29:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRwAU-0006H9-DS
	for avt@megatron.ietf.org; Wed, 10 Nov 2004 12:22:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02952
	for <avt@ietf.org>; Wed, 10 Nov 2004 12:21:59 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRwBJ-0007yc-Ot
	for avt@ietf.org; Wed, 10 Nov 2004 12:23:04 -0500
Received: from [130.129.135.72] (port=65376 helo=[130.129.135.72])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1CRw9n-0001Dj-R3; Wed, 10 Nov 2004 17:21:19 +0000
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <EC70F7CE-333C-11D9-AA76-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Date: Wed, 10 Nov 2004 12:21:14 -0500
To: avt@ietf.org
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Content-Transfer-Encoding: 7bit
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: [AVT] Slides for AVT on Wednesday
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit

Folks,

Copies of the presentation materials that will be used in AVT this 
afternoon can be found at http://csperkins.org/misc/ietf61-avt-day1.zip

Colin


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 10 14:36:13 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17695
	for <avt-archive@ietf.org>; Wed, 10 Nov 2004 14:36:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRyHM-0002zG-Vl
	for avt-archive@ietf.org; Wed, 10 Nov 2004 14:37:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRy8E-0005Ys-85; Wed, 10 Nov 2004 14:27:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRy1D-0004TN-A1
	for avt@megatron.ietf.org; Wed, 10 Nov 2004 14:20:35 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15672
	for <avt@ietf.org>; Wed, 10 Nov 2004 14:20:33 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRy2D-0002WL-7c
	for avt@ietf.org; Wed, 10 Nov 2004 14:21:38 -0500
Received: from zcard303.ca.nortel.com (zcard303.ca.nortel.com [47.129.242.59])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iAAJJvo11943
	for <avt@ietf.org>; Wed, 10 Nov 2004 14:19:57 -0500 (EST)
Received: from [47.102.177.109] (archt0pc.us.nortel.com [47.102.177.109]) by
	zcard303.ca.nortel.com with SMTP (Microsoft Exchange Internet
	Mail Service Version 5.5.2653.13)
	id W14FPKLX; Wed, 10 Nov 2004 14:19:57 -0500
Message-ID: <419269D9.9090800@nortelnetworks.com>
Date: Wed, 10 Nov 2004 14:19:53 -0500
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: avt@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit
Subject: [AVT] Splitting of RFC 2833bis
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit

At the AVT meeting today, it was agreed that it would be a good idea to split the 
current draft-ietf-avt-rfc2833bis-05.txt.  The idea would be to remove and put 
into a separate draft the codepoints for the less-implemented event types.  This 
proposal was inspired partly by the magnitude of the changes to the trunk 
signalling related events, which raised the suspicion these events have never been 
implemented.

It was generally agreed that the DTMF codepoints should stay with the core 
specification.  Are there any other candidates for this honour, or should all the 
rest go to the new document(s)?

Going further: should there be one new document, or one per class of events (i.e., 
lines, data and FAX, trunks)?

-- 
Tom Taylor
Carrier VoIP Standards Development
Nortel Networks
Phone +1 613 763 1496  (ESN 393-1496)
E-mail: taylor@nortelnetworks.com

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 10 14:58:39 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19802
	for <avt-archive@ietf.org>; Wed, 10 Nov 2004 14:58:39 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRyd3-0003Yt-LK
	for avt-archive@ietf.org; Wed, 10 Nov 2004 14:59:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRya7-00027P-Hb; Wed, 10 Nov 2004 14:56:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRyQC-0000JA-EY
	for avt@megatron.ietf.org; Wed, 10 Nov 2004 14:46:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18609
	for <avt@ietf.org>; Wed, 10 Nov 2004 14:46:22 -0500 (EST)
Received: from zcars04e.nortelnetworks.com ([47.129.242.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRyRD-0003Cj-HD
	for avt@ietf.org; Wed, 10 Nov 2004 14:47:27 -0500
Received: from zcard303.ca.nortel.com (zcard303.ca.nortel.com [47.129.242.59])
	by zcars04e.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iAAJjgE14376
	for <avt@ietf.org>; Wed, 10 Nov 2004 14:45:42 -0500 (EST)
Received: from [47.102.177.109] (archt0pc.us.nortel.com [47.102.177.109]) by
	zcard303.ca.nortel.com with SMTP (Microsoft Exchange Internet
	Mail Service Version 5.5.2653.13)
	id W14FPKTN; Wed, 10 Nov 2004 14:45:38 -0500
Message-ID: <41926FDD.10100@nortelnetworks.com>
Date: Wed, 10 Nov 2004 14:45:33 -0500
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: avt@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit
Subject: [AVT] Undocumented tone events in 2833/2833bis
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit

There are a number of codepoints defined in draft-ietf-avt-rfc2833bis-05.txt 
section 3.4 "Extended Subscriber Line Events" for which descriptions are not 
available.  It was agreed at today's meeting that undocumented codepoints should 
be deleted.  I propose the definitions shown below for some of these events, based 
simply on their names.  I propose to delete the remainder unless someone can 
provide convincing definitions for their use.

Tones for deletion:
- Acceptance tone
- Facilities tone
- Offering tone
- Refusal tone
- Route tone
- Valid tone

Proposed tone definitions:

End of three party service tone
Tone provided to the remaining parties to a call when the call reverts from a 
three-way conference to a two-party call.

Preemption tone
Tone provided to each party to a call which has been terminated due to preemption.

Queue tone
Tone provided to a calling party when the call has been placed into a queue 
awaiting answer.

Waiting tone
Tone provided periodically to a waiting calling party after the call has been 
placed into a queue, until the call has been answered.

Warning tone (end of period)
Tone provided to the paying party for a call to indicate that the period for which 
payment has been credited will soon expire.

Warning Tone (PIP tone)
Tone provided to the paying party for a call to indicate that expiry of the period 
for which payment has been credited is imminent.

Comments?

-- 
Tom Taylor
Carrier VoIP Standards Development
Nortel Networks
Phone +1 613 763 1496  (ESN 393-1496)
E-mail: taylor@nortelnetworks.com

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 10 15:05:19 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20486
	for <avt-archive@ietf.org>; Wed, 10 Nov 2004 15:05:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRyjY-0003jR-0g
	for avt-archive@ietf.org; Wed, 10 Nov 2004 15:06:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRyaF-0002Du-4b; Wed, 10 Nov 2004 14:56:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRyVj-0001HD-Pr
	for avt@megatron.ietf.org; Wed, 10 Nov 2004 14:52:07 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19170
	for <avt@ietf.org>; Wed, 10 Nov 2004 14:52:06 -0500 (EST)
Received: from zcars04e.nortelnetworks.com ([47.129.242.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRyWk-0003N6-0u
	for avt@ietf.org; Wed, 10 Nov 2004 14:53:11 -0500
Received: from zcard303.ca.nortel.com (zcard303.ca.nortel.com [47.129.242.59])
	by zcars04e.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iAAJpYE14955
	for <avt@ietf.org>; Wed, 10 Nov 2004 14:51:34 -0500 (EST)
Received: from [47.102.177.109] (archt0pc.us.nortel.com [47.102.177.109]) by
	zcard303.ca.nortel.com with SMTP (Microsoft Exchange Internet
	Mail Service Version 5.5.2653.13)
	id W14FPKV2; Wed, 10 Nov 2004 14:51:34 -0500
Message-ID: <41927144.40109@nortelnetworks.com>
Date: Wed, 10 Nov 2004 14:51:32 -0500
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: avt@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
Subject: [AVT] Exceptional treatment of E bit for state events in 2833bis
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit

draft-ietf-avt-rfc2833bis-05.txt section 2.5.1.2 contains the following text 
regarding the setting of 'E' (end) bits for events that are states:

       Sending of a packet with the "E" bit set is OPTIONAL if the packet
       reports two events which are defined as mutually exclusive states, or
       if the final packet for one state is immediately followed by a packet
       reporting a mutually exclusive state.  (For events defined as states,
       the appearance of a mutually exclusive state implies the end of the
       previous state.)

This is a small optimization at the potential expense of a bunch of extra code.  I 
really don't see it as worth the effort.  I propose to delete it unless someone 
makes a good case otherwise.

Comments?

-- 
Tom Taylor
Carrier VoIP Standards Development
Nortel Networks
Phone +1 613 763 1496  (ESN 393-1496)
E-mail: taylor@nortelnetworks.com

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 10 16:20:58 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05164
	for <avt-archive@ietf.org>; Wed, 10 Nov 2004 16:20:58 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRzum-0007j7-HT
	for avt-archive@ietf.org; Wed, 10 Nov 2004 16:22:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRzdZ-0005WX-PS; Wed, 10 Nov 2004 16:04:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRzUc-0006pf-2d
	for avt@megatron.ietf.org; Wed, 10 Nov 2004 15:55:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00829
	for <avt@ietf.org>; Wed, 10 Nov 2004 15:54:58 -0500 (EST)
Received: from endeavor.poss.com ([198.70.184.137] helo=smtp.poss.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRzVa-0006XT-O5
	for avt@ietf.org; Wed, 10 Nov 2004 15:56:05 -0500
Received: from KNOLLXPLT (ws-194065.va.rr.com [24.28.194.65])
	by endeavor.poss.com
	(iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
	with ESMTPA id <0I6Z00D70E2QNL@endeavor.poss.com> for avt@ietf.org; Wed,
	10 Nov 2004 15:54:26 -0500 (EST)
Date: Wed, 10 Nov 2004 15:54:26 -0500
From: "Kevin A. Noll" <kevin.noll@perfectorder.com>
Subject: RE: [AVT] Exceptional treatment of E bit for state events in 2833bis
In-reply-to: <41927144.40109@nortelnetworks.com>
To: "'Tom Taylor'" <taylor@nortelnetworks.com>, avt@ietf.org
Message-id: <008f01c4c767$775059d0$6c0315ac@KNOLLXPLT>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook, Build 10.0.6626
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7BIT
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: 7BIT



I agree with removing this paragraph. The optimization doesn't get you
anything considering that you still have to handle the case where the
packet(s) with the E-bit set are lost in transit.

--kan--
--
Kevin A. Noll, KD4WOZ
CCIE, CCDP
Perfect Order, Inc.		
Kevin.Noll@perfectorder.com
717-796-1936


-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Tom
Taylor
Sent: Wednesday, November 10, 2004 2:52 PM
To: avt@ietf.org
Subject: [AVT] Exceptional treatment of E bit for state events in 2833bis


draft-ietf-avt-rfc2833bis-05.txt section 2.5.1.2 contains the following text

regarding the setting of 'E' (end) bits for events that are states:

       Sending of a packet with the "E" bit set is OPTIONAL if the packet
       reports two events which are defined as mutually exclusive states, or
       if the final packet for one state is immediately followed by a packet
       reporting a mutually exclusive state.  (For events defined as states,
       the appearance of a mutually exclusive state implies the end of the
       previous state.)

This is a small optimization at the potential expense of a bunch of extra
code.  I 
really don't see it as worth the effort.  I propose to delete it unless
someone 
makes a good case otherwise.

Comments?

-- 
Tom Taylor
Carrier VoIP Standards Development
Nortel Networks
Phone +1 613 763 1496  (ESN 393-1496)
E-mail: taylor@nortelnetworks.com

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 10 16:22:39 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05548
	for <avt-archive@ietf.org>; Wed, 10 Nov 2004 16:22:39 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRzwP-0007oF-MY
	for avt-archive@ietf.org; Wed, 10 Nov 2004 16:23:45 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRznF-0001nr-Ga; Wed, 10 Nov 2004 16:14:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRzYw-0002Yc-62
	for avt@megatron.ietf.org; Wed, 10 Nov 2004 15:59:30 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01674
	for <avt@ietf.org>; Wed, 10 Nov 2004 15:59:27 -0500 (EST)
Received: from endeavor.poss.com ([198.70.184.137] helo=smtp.poss.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRzZx-0006p2-Cr
	for avt@ietf.org; Wed, 10 Nov 2004 16:00:33 -0500
Received: from KNOLLXPLT (ws-194065.va.rr.com [24.28.194.65])
	by endeavor.poss.com
	(iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
	with ESMTPA id <0I6Z00D94EA9NL@endeavor.poss.com> for avt@ietf.org; Wed,
	10 Nov 2004 15:58:57 -0500 (EST)
Date: Wed, 10 Nov 2004 15:58:57 -0500
From: "Kevin A. Noll" <kevin.noll@perfectorder.com>
Subject: RE: [AVT] Splitting of RFC 2833bis
In-reply-to: <419269D9.9090800@nortelnetworks.com>
To: "'Tom Taylor'" <taylor@nortelnetworks.com>, avt@ietf.org
Message-id: <009001c4c768$18d624b0$6c0315ac@KNOLLXPLT>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook, Build 10.0.6626
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: 7BIT
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: 7BIT



Not sure if this is proper, but would it make sense to have the codepoints
be 
handled as registered numbers with the structures of IANA? 

Either way, I don't see much sense in having separate documents for
different 
classes. It just seems like too much extra work unless there's some
precedent
for it.

--kan--
--
Kevin A. Noll, KD4WOZ
CCIE, CCDP
Perfect Order, Inc.		
Kevin.Noll@perfectorder.com
717-796-1936


-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Tom
Taylor
Sent: Wednesday, November 10, 2004 2:20 PM
To: avt@ietf.org
Subject: [AVT] Splitting of RFC 2833bis


At the AVT meeting today, it was agreed that it would be a good idea to
split the 
current draft-ietf-avt-rfc2833bis-05.txt.  The idea would be to remove and
put 
into a separate draft the codepoints for the less-implemented event types.
This 
proposal was inspired partly by the magnitude of the changes to the trunk 
signalling related events, which raised the suspicion these events have
never been 
implemented.

It was generally agreed that the DTMF codepoints should stay with the core 
specification.  Are there any other candidates for this honour, or should
all the 
rest go to the new document(s)?

Going further: should there be one new document, or one per class of events
(i.e., 
lines, data and FAX, trunks)?

-- 
Tom Taylor
Carrier VoIP Standards Development
Nortel Networks
Phone +1 613 763 1496  (ESN 393-1496)
E-mail: taylor@nortelnetworks.com

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 10 16:53:05 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08873
	for <avt-archive@ietf.org>; Wed, 10 Nov 2004 16:53:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CS0Ps-0008VK-19
	for avt-archive@ietf.org; Wed, 10 Nov 2004 16:54:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CS0DZ-0006Av-AC; Wed, 10 Nov 2004 16:41:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CS081-0003X8-Ik
	for avt@megatron.ietf.org; Wed, 10 Nov 2004 16:35:45 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07353
	for <avt@ietf.org>; Wed, 10 Nov 2004 16:35:43 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CS092-00088A-Lj
	for avt@ietf.org; Wed, 10 Nov 2004 16:36:50 -0500
Received: from zcard303.ca.nortel.com (zcard303.ca.nortel.com [47.129.242.59])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iAALZBi24308
	for <avt@ietf.org>; Wed, 10 Nov 2004 16:35:11 -0500 (EST)
Received: from [47.102.179.50] (archt184.us.nortel.com [47.102.179.50]) by
	zcard303.ca.nortel.com with SMTP (Microsoft Exchange Internet
	Mail Service Version 5.5.2653.13)
	id W14FPL45; Wed, 10 Nov 2004 16:35:12 -0500
Message-ID: <4192898C.8040900@nortelnetworks.com>
Date: Wed, 10 Nov 2004 16:35:08 -0500
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: avt@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit
Subject: [AVT] Handling lost marker packet in 2833bis
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit

Kevin Noll had asked for advice in 2833bis on what to do if the initial packet of 
an event report (with the 'M' bit set) got lost but subsequent packets were 
received.  I did incorporate some advice in rfc2833bis-05, but it's probably a 
good idea to put it out to the list for consideration.  Here's what was added to 
rfc2833bis-05:

    2.5.2.2  Playout of Tone Events
....
       If a receiver receives an event packet for an event which it is not
       currently playing out and the packet does not have the "M" bit set,
       earlier packets for that event have evidently been lost.  The
       receiver MAY determine on the basis of retained history and the
       timestamp and event code of the current packet that it corresponds to
       an event already played out and lapsed.  In that case further reports
       for the event MUST be ignored, as indicated in the previous
       paragraph.  If this is not so, the receiver MAY attempt to play the
       event out to the complete duration indicated in the event report.
       The appropriate behaviour will depend on the event type concerned,
       and requires consideration of the relationship of the event to audio
       media flows and whether correct event duration is essential to the
       correct operation of the media session.

-- 
Tom Taylor
Carrier VoIP Standards Development
Nortel Networks
Phone +1 613 763 1496  (ESN 393-1496)
E-mail: taylor@nortelnetworks.com

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 10 16:57:05 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09196
	for <avt-archive@ietf.org>; Wed, 10 Nov 2004 16:57:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CS0Ti-00009J-VS
	for avt-archive@ietf.org; Wed, 10 Nov 2004 16:58:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CS0O8-0002di-47; Wed, 10 Nov 2004 16:52:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CS0C3-0005fv-Gv
	for avt@megatron.ietf.org; Wed, 10 Nov 2004 16:39:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07897
	for <avt@ietf.org>; Wed, 10 Nov 2004 16:39:53 -0500 (EST)
Received: from zcars04e.nortelnetworks.com ([47.129.242.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CS0D5-0008Dt-KJ
	for avt@ietf.org; Wed, 10 Nov 2004 16:40:59 -0500
Received: from zcard303.ca.nortel.com (zcard303.ca.nortel.com [47.129.242.59])
	by zcars04e.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iAALdHD27010; Wed, 10 Nov 2004 16:39:18 -0500 (EST)
Received: from [47.102.179.50] (archt184.us.nortel.com [47.102.179.50]) by
	zcard303.ca.nortel.com with SMTP (Microsoft Exchange Internet
	Mail Service Version 5.5.2653.13)
	id W14FPLVN; Wed, 10 Nov 2004 16:39:18 -0500
Message-ID: <41928A84.4050100@nortelnetworks.com>
Date: Wed, 10 Nov 2004 16:39:16 -0500
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Kevin A. Noll" <kevin.noll@perfectorder.com>
Subject: Re: [AVT] Splitting of RFC 2833bis
References: <009001c4c768$18d624b0$6c0315ac@KNOLLXPLT>
In-Reply-To: <009001c4c768$18d624b0$6c0315ac@KNOLLXPLT>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7bit
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: 7bit

We do intend to set up an IANA registry.  Taking your advice, the initial
population of that registry would include the DTMF events and probably some data
events to which current ITU-T documents refer.  The other events would be added
when the second document is approved.

I suspect what you have in mind is a registry anyone can add to.  This probably
won't work because the code space is so small: just 256 events, thanks to the
payload format.  If we find we need more down the road (hope not!), I suppose we
could define an extension to that format.  We could use the "R" bit to double the
code space, for instance.

Barring that, the criterion for adding codepoints should probably be a published
standards-track RFC.

Kevin A. Noll wrote:
> 
> Not sure if this is proper, but would it make sense to have the codepoints
> be 
> handled as registered numbers with the structures of IANA? 
> 
> Either way, I don't see much sense in having separate documents for
> different 
> classes. It just seems like too much extra work unless there's some
> precedent
> for it.
> 
> --kan--
> --
> Kevin A. Noll, KD4WOZ
> CCIE, CCDP
> Perfect Order, Inc.		
> Kevin.Noll@perfectorder.com
> 717-796-1936
> 
> 
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Tom
> Taylor
> Sent: Wednesday, November 10, 2004 2:20 PM
> To: avt@ietf.org
> Subject: [AVT] Splitting of RFC 2833bis
> 
> 
> At the AVT meeting today, it was agreed that it would be a good idea to
> split the 
> current draft-ietf-avt-rfc2833bis-05.txt.  The idea would be to remove and
> put 
> into a separate draft the codepoints for the less-implemented event types.
> This 
> proposal was inspired partly by the magnitude of the changes to the trunk 
> signalling related events, which raised the suspicion these events have
> never been 
> implemented.
> 
> It was generally agreed that the DTMF codepoints should stay with the core 
> specification.  Are there any other candidates for this honour, or should
> all the 
> rest go to the new document(s)?
> 
> Going further: should there be one new document, or one per class of events
> (i.e., 
> lines, data and FAX, trunks)?
> 

-- 
Tom Taylor
Carrier VoIP Standards Development
Nortel Networks
Phone +1 613 763 1496  (ESN 393-1496)
E-mail: taylor@nortelnetworks.com


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 10 17:38:11 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12895
	for <avt-archive@ietf.org>; Wed, 10 Nov 2004 17:38:10 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CS17W-00015f-Fr
	for avt-archive@ietf.org; Wed, 10 Nov 2004 17:39:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CS0zT-0003GK-Or; Wed, 10 Nov 2004 17:30:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CS0qK-0001T3-H9
	for avt@megatron.ietf.org; Wed, 10 Nov 2004 17:21:32 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11563
	for <avt@ietf.org>; Wed, 10 Nov 2004 17:21:29 -0500 (EST)
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254] helo=mail.tvol.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CS0rI-0000l2-WC
	for avt@ietf.org; Wed, 10 Nov 2004 17:22:37 -0500
Received: from jesup.eng.tvol.net ([10.32.2.26]) by mail.tvol.net with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id WQKMY9JJ; Wed, 10 Nov 2004 17:20:31 -0500
To: "Dan Wing" <dwing@cisco.com>
Subject: Re: [AVT] RE: [Ietf-behave] RTP in draft-ietf-behave-nat-00
References: <LIECKHBKICJFBLOMPHNMOEENNLAA.dwing@cisco.com>
From: Randell Jesup <rjesup@wgate.com>
Date: 10 Nov 2004 17:26:12 -0500
In-Reply-To: <LIECKHBKICJFBLOMPHNMOEENNLAA.dwing@cisco.com>
Message-ID: <ybu654ds5mj.fsf@jesup.eng.tvol.net.jesup.eng.tvol.net>
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: fluffy@cisco.com, ietf-behave@list.sipfoundry.org,
        Stephen Casner <casner@acm.org>, AVT WG <avt@ietf.org>,
        audet@nortelnetworks.com
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15

"Dan Wing" <dwing@cisco.com> writes:
>To your first point, I believe we resolved this, in a positive way, on the
>list; -00 doesn't yet reflect those changes.  We decided to require NATs
>to preserve even and odd port numbers when they create their UDP bindings,
>as this provides the best interoperability for RTP applications that
>don't/can't provide explicit signaling of their RTCP port.

        Ummm...

        And how will you "require" NATs to do this?  This would mean that
all NATs would need to map all UDP traffic to the same oddness (even->even,
odd->odd).  While sure, the NAT vendors _could_ write code this way (though
it may well break some current NAT-traversal code that tries to do
predictive mapping), there are millions of NATs out there that will never
implement this, and nothing to force new releases to do so.

        The even/odd port thing was (IMHO) a Bad Idea (in hindsight), I
assume meant to avoid having to figure out how to signal the number for the
second port - and even for that even/odd wasn't really needed, all you
needed was contiguous.  Other TCP/UDP protocols don't do these sorts of
things with port numbers (even/odd, or implied relationships between port
numbers) - it's much better to actually signal the ports to be used.

        We shouldn't compound it by "requiring" NATs maintain oddness
(after the horse is not only out of the barn, but 12 miles down the road).
We're apparently trying to avoid breaking "RTP applications that
don't/can't provide explicit signaling of their RTCP port" by putting a
requirement on NATs that will at best be phased in over years, and at worst
totally ignored, instead of requiring RTP applications to specify both RTP
and RTCP ports.  The effect will be that RTP applications that attempt to
rely on this NAT requirement will end up breaking in many situations, and
quite probably in unpredictable ways.  (For example, many NATs try to
maintain port numbers inside->outside, but if the port is in use will then
allocate other non-contiguous port numbers of different oddness.)

        The original idea (even/odd pairs) wasn't a good one, and was
somewhat at odds with normal techniques in TCP/UDP, and certainly at odds
with any sort of NAT concept.  (Note: just my opinion, of course)

        Of course, having a NAT preserve oddness (and contiguity!) will
improve the odds of an older RTP application working from behind it, so it
might be a *nice* thing to do in the NAT - but no one should be counting on
it, and it's yet another complication in NAT design and limitation that
could cause it to run out of ports (in a large corporate-style NAT).

>To your second, a reference to RFC3605 will be added to the 'application
>behavior' document, which will describe how applications should behave.
>The current BEHAVE document just describes how NATs should behave.

        If BEHAVE is how they "should" behave, then my objections are
lessened - though we need to make sure that people don't use this document
as an excuse not to specify the RTCP port.

-- 
Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team
rjesup@wgate.com


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 10 17:47:02 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13570
	for <avt-archive@ietf.org>; Wed, 10 Nov 2004 17:47:02 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CS1G5-0001H1-0D
	for avt-archive@ietf.org; Wed, 10 Nov 2004 17:48:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CS17r-0004v4-Kj; Wed, 10 Nov 2004 17:39:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CS11V-0003cz-Rz
	for avt@megatron.ietf.org; Wed, 10 Nov 2004 17:33:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12514
	for <avt@ietf.org>; Wed, 10 Nov 2004 17:33:02 -0500 (EST)
Received: from m6f195e42.tmodns.net ([66.94.25.111]
	helo=mailrelay.t-mobile.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CS12Y-0000xK-DP
	for avt@ietf.org; Wed, 10 Nov 2004 17:34:10 -0500
Received: from localhost (localhost [127.0.0.1])
	by mailrelay.t-mobile.com (Postfix) with ESMTP id 3180F99B0
	for <avt@ietf.org>; Wed, 10 Nov 2004 16:28:56 -0600 (CST)
Received: from mailrelay.t-mobile.com ([127.0.0.1])
	by localhost (mailrelay.t-mobile.com [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 23505-04 for <avt@ietf.org>;
	Wed, 10 Nov 2004 16:28:55 -0600 (CST)
Received: from telws116 (unknown [10.255.98.246])
	by mailrelay.t-mobile.com (Postfix) with ESMTP
	for <avt@ietf.org>; Wed, 10 Nov 2004 16:28:55 -0600 (CST)
From: "Alan Clark" <alan.d.clark@telchemy.com>
To: <avt@ietf.org>
Date: Wed, 10 Nov 2004 17:32:29 -0500
Message-ID: <BGEKJNNFCPJKLLMMDMELMEBPFJAA.alan.d.clark@telchemy.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit
Subject: [AVT] RTP MIB update - comments/ requirements?
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit


Following today's AVT meeting - we are planning to update the RTP MIB to
accomodate any changes needed that result from RFC3550, and would like to
ensure that we also address any other known issues/ shortcomings.  Please
send any comments, requirements or suggestions to the AVT list by December
1st in order that we can rough out what needs to be done

Thanks

Alan Clark


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Thu Nov 11 09:01:52 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11746
	for <avt-archive@ietf.org>; Thu, 11 Nov 2004 09:01:52 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSFXW-0002f3-9c
	for avt-archive@ietf.org; Thu, 11 Nov 2004 09:03:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSFPt-0007HT-RO; Thu, 11 Nov 2004 08:55:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRzID-0005uS-RJ
	for avt@megatron.ietf.org; Wed, 10 Nov 2004 15:42:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26782
	for <avt@ietf.org>; Wed, 10 Nov 2004 15:42:11 -0500 (EST)
Received: from ihemail1.lucent.com ([192.11.222.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRzJF-0005F3-F7
	for avt@ietf.org; Wed, 10 Nov 2004 15:43:17 -0500
Received: from il0015exch001h.wins.lucent.com (h135-1-23-83.lucent.com
	[135.1.23.83])
	by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id iAAKff8M002473
	for <avt@ietf.org>; Wed, 10 Nov 2004 14:41:41 -0600 (CST)
Received: by il0015exch001h.ih.lucent.com with Internet Mail Service
	(5.5.2657.72) id <4M3GAVTF>; Wed, 10 Nov 2004 14:41:40 -0600
Message-ID: <17D8724A2A8D9542B2B8AE546B9E5BBC031F8C8A@AZ4315EXCH001U>
From: "COLDREN, REX A (REX)" <coldrenr@lucent.com>
To: taylor@nortelnoetworks.com.cnri.reston.va.us
Subject: [AVT] Exceptional treatment of E bit for state events in 2833bis
Date: Wed, 10 Nov 2004 14:41:39 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
X-Mailman-Approved-At: Thu, 11 Nov 2004 08:55:12 -0500
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793

This one comes from the trunk events, where one state is necessarily 
exclusive of all others.  For them, the 'E' bit is not useful and is 
deemed to be, in fact, problematic.  For example, while reporting a
stable off-hook state in real time with RFC 2833 packets every 50ms,
there is an inherent 50ms delay (perhaps more with de-bouncing code)
in reporting the end of event (e.g. on-hook event occurred but one
additional off-hook needs to be sent with the 'E' bit set).

This is but an example.  I don't know how many of the other state
related events would be affected by changing this requirement.

Rex

-----Original Message-----
From: Tom Taylor [mailto:taylor@nortelnetworks.com]
Sent: Wednesday, November 10, 2004 12:52 PM
To: avt@ietf.org
Subject: [AVT] Exceptional treatment of E bit for state events in
2833bis


draft-ietf-avt-rfc2833bis-05.txt section 2.5.1.2 contains the following text 
regarding the setting of 'E' (end) bits for events that are states:

       Sending of a packet with the "E" bit set is OPTIONAL if the packet
       reports two events which are defined as mutually exclusive states, or
       if the final packet for one state is immediately followed by a packet
       reporting a mutually exclusive state.  (For events defined as states,
       the appearance of a mutually exclusive state implies the end of the
       previous state.)

This is a small optimization at the potential expense of a bunch of extra code.  I 
really don't see it as worth the effort.  I propose to delete it unless someone 
makes a good case otherwise.

Comments?

-- 
Tom Taylor
Carrier VoIP Standards Development
Nortel Networks
Phone +1 613 763 1496  (ESN 393-1496)
E-mail: taylor@nortelnetworks.com

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Thu Nov 11 10:40:33 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23884
	for <avt-archive@ietf.org>; Thu, 11 Nov 2004 10:40:33 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSH52-00055x-Nq
	for avt-archive@ietf.org; Thu, 11 Nov 2004 10:41:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSH2C-0001GU-7Q; Thu, 11 Nov 2004 10:38:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSGvk-0008Bg-TR
	for avt@megatron.ietf.org; Thu, 11 Nov 2004 10:32:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22822
	for <avt@ietf.org>; Thu, 11 Nov 2004 10:32:11 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSGwu-0004rc-H1 for avt@ietf.org; Thu, 11 Nov 2004 10:33:26 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 11 Nov 2004 07:43:40 -0800
Received: from edison.cisco.com (edison.cisco.com [171.71.180.109])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iABFVaom027157;
	Thu, 11 Nov 2004 07:31:36 -0800 (PST)
Received: from DWINGW2K4 (sjc-vpn1-807.cisco.com [10.21.99.39]) by
	edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with
	SMTP id HAA11306; Thu, 11 Nov 2004 07:31:35 -0800 (PST)
From: "Dan Wing" <dwing@cisco.com>
To: "Randell Jesup" <rjesup@wgate.com>
Subject: RE: [AVT] RE: [Ietf-behave] RTP in draft-ietf-behave-nat-00
Date: Thu, 11 Nov 2004 07:31:34 -0800
Keywords: dwing_to_me
Message-ID: <LIECKHBKICJFBLOMPHNMEEOFNLAA.dwing@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <ybu654ds5mj.fsf@jesup.eng.tvol.net.jesup.eng.tvol.net>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: 7bit
Cc: fluffy@cisco.com, ietf-behave@list.sipfoundry.org,
        Stephen Casner <casner@acm.org>, AVT WG <avt@ietf.org>,
        Francois Audet <audet@nortelnetworks.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Content-Transfer-Encoding: 7bit

Randell Jesup:

> "Dan Wing" <dwing@cisco.com> writes:
> >To your first point, I believe we resolved this, in a positive
> way, on the
> >list; -00 doesn't yet reflect those changes.  We decided to require NATs
> >to preserve even and odd port numbers when they create their UDP
> bindings,
> >as this provides the best interoperability for RTP applications that
> >don't/can't provide explicit signaling of their RTCP port.
>
>         Ummm...
>
>         And how will you "require" NATs to do this?  This would mean that
> all NATs would need to map all UDP traffic to the same oddness
> (even->even,
> odd->odd).  While sure, the NAT vendors _could_ write code this
> way (though
> it may well break some current NAT-traversal code that tries to do
> predictive mapping), there are millions of NATs out there that will never
> implement this, and nothing to force new releases to do so.
>
>         The even/odd port thing was (IMHO) a Bad Idea (in hindsight), I
> assume meant to avoid having to figure out how to signal the
> number for the
> second port - and even for that even/odd wasn't really needed, all you
> needed was contiguous.  Other TCP/UDP protocols don't do these sorts of
> things with port numbers (even/odd, or implied relationships between port
> numbers) - it's much better to actually signal the ports to be used.
>
>         We shouldn't compound it by "requiring" NATs maintain oddness
> (after the horse is not only out of the barn, but 12 miles down the road).
> We're apparently trying to avoid breaking "RTP applications that
> don't/can't provide explicit signaling of their RTCP port" by putting a
> requirement on NATs that will at best be phased in over years,
> and at worst
> totally ignored, instead of requiring RTP applications to specify both RTP
> and RTCP ports.  The effect will be that RTP applications that attempt to
> rely on this NAT requirement will end up breaking in many situations, and
> quite probably in unpredictable ways.  (For example, many NATs try to
> maintain port numbers inside->outside, but if the port is in use will then
> allocate other non-contiguous port numbers of different oddness.)
>
>         The original idea (even/odd pairs) wasn't a good one, and was
> somewhat at odds with normal techniques in TCP/UDP, and certainly at odds
> with any sort of NAT concept.  (Note: just my opinion, of course)
>
>         Of course, having a NAT preserve oddness (and contiguity!) will
> improve the odds of an older RTP application working from behind it, so it
> might be a *nice* thing to do in the NAT - but no one should be
> counting on
> it, and it's yet another complication in NAT design and limitation that
> could cause it to run out of ports (in a large corporate-style NAT).

I'll leave the draft-ietf-behave-nat authors to comment on the specific
text they're considering; it's my understanding they are adding text which
hits on your points above.

> >To your second, a reference to RFC3605 will be added to the 'application
> >behavior' document, which will describe how applications should behave.
> >The current BEHAVE document just describes how NATs should behave.
>
>         If BEHAVE is how they "should" behave, then my objections are
> lessened - though we need to make sure that people don't use this document
> as an excuse not to specify the RTCP port.

Application behavior will be in the application document (not in
draft-ietf-behave-nat); Francois and I are going to take a first cut at
the application document in the next month or two.  The application
document is described as "Produce a BCP that discusses protocol design
techniques for using the existing set of NAT traversal approaches" in
the BEHAVE charter
<http://www.ietf.org/html.charters/behave-charter.html>.

-d


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Thu Nov 11 12:34:49 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05699
	for <avt-archive@ietf.org>; Thu, 11 Nov 2004 12:34:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSIrd-00085j-Vi
	for avt-archive@ietf.org; Thu, 11 Nov 2004 12:36:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSIi9-0001aF-Nn; Thu, 11 Nov 2004 12:26:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSIXT-0006K3-4T
	for avt@megatron.ietf.org; Thu, 11 Nov 2004 12:15:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03948
	for <avt@ietf.org>; Thu, 11 Nov 2004 12:15:12 -0500 (EST)
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSIYW-0007bw-Bd
	for avt@ietf.org; Thu, 11 Nov 2004 12:16:30 -0500
Received: from mailgate2.apple.com (a17-128-100-204.apple.com [17.128.100.204])
	by mail-out3.apple.com (8.12.11/8.12.11) with ESMTP id iABHKJKv025069
	for <avt@ietf.org>; Thu, 11 Nov 2004 09:20:19 -0800 (PST)
Received: from relay1.apple.com (relay1.apple.com) by mailgate2.apple.com
	(Content Technologies SMTPRS 4.3.14) with ESMTP id
	<T6d3352691d118064cc618@mailgate2.apple.com> for <avt@ietf.org>;
	Thu, 11 Nov 2004 09:14:34 -0800
Received: from [17.212.34.157] (to0203a-dhcp29.apple.com [17.212.34.157])
	by relay1.apple.com (8.12.11/8.12.11) with ESMTP id iABHEWKQ016691
	for <avt@ietf.org>; Thu, 11 Nov 2004 09:14:32 -0800 (PST)
User-Agent: Microsoft-Entourage/11.0.0.040405
Date: Thu, 11 Nov 2004 09:16:05 -0800
From: Kevin Lane <klane@apple.com>
To: <avt@ietf.org>
Message-ID: <BDB8DE55.13D1%klane@apple.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Subject: [AVT] Job at Apple Computer
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit

Hello,

I am a new member.

Can I post 1-2 site specific jobs we have available?

Thank you for your help.


-- 
Kevin Lane
Staffing Specialist
Apple Computer, Inc.
408-974-1502
klane@apple.com
http://jobs.apple.com




_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Thu Nov 11 13:14:53 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09047
	for <avt-archive@ietf.org>; Thu, 11 Nov 2004 13:14:53 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSJUQ-0000XS-6Z
	for avt-archive@ietf.org; Thu, 11 Nov 2004 13:16:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSJMs-0001Ve-29; Thu, 11 Nov 2004 13:08:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSJHC-0000Hs-RJ
	for avt@megatron.ietf.org; Thu, 11 Nov 2004 13:02:30 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08155
	for <avt@ietf.org>; Thu, 11 Nov 2004 13:02:27 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSJIN-0000GV-Nt
	for avt@ietf.org; Thu, 11 Nov 2004 13:03:45 -0500
Received: from [130.129.135.72] (port=52404 helo=[130.129.135.72])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1CSJGb-0001DE-5i; Thu, 11 Nov 2004 18:01:53 +0000
In-Reply-To: <BDB8DE55.13D1%klane@apple.com>
References: <BDB8DE55.13D1%klane@apple.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <C24D44E3-340B-11D9-8623-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Job at Apple Computer
Date: Thu, 11 Nov 2004 13:01:49 -0500
To: Kevin Lane <klane@apple.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Content-Transfer-Encoding: 7bit
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit

On 11 Nov 2004, at 12:16, Kevin Lane wrote:
> Can I post 1-2 site specific jobs we have available?

No. Jobs advertisements are not appropriate to this list.

Colin


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Thu Nov 11 13:15:18 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09074
	for <avt-archive@ietf.org>; Thu, 11 Nov 2004 13:15:18 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSJUq-0000Xp-28
	for avt-archive@ietf.org; Thu, 11 Nov 2004 13:16:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSJMv-0001bJ-23; Thu, 11 Nov 2004 13:08:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSJI9-0000Qp-Qs
	for avt@megatron.ietf.org; Thu, 11 Nov 2004 13:03:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08242
	for <avt@ietf.org>; Thu, 11 Nov 2004 13:03:27 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSJJL-0000Ib-ES
	for avt@ietf.org; Thu, 11 Nov 2004 13:04:44 -0500
Received: from [130.129.135.72] (port=52413 helo=[130.129.135.72])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1CSJHd-0001gx-0j for avt@ietf.org; Thu, 11 Nov 2004 18:02:57 +0000
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <EC70F7CE-333C-11D9-AA76-000A957FC5F2@csperkins.org>
References: <EC70F7CE-333C-11D9-AA76-000A957FC5F2@csperkins.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <E89E2108-340B-11D9-8623-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Slides for AVT on Wednesday
Date: Thu, 11 Nov 2004 13:02:53 -0500
To: avt@ietf.org
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: 7bit
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit

On 10 Nov 2004, at 12:21, Colin Perkins wrote:
> Copies of the presentation materials that will be used in AVT this 
> afternoon can be found at 
> http://csperkins.org/misc/ietf61-avt-day1.zip

Slides for Thursday are also available at the obvious location:
	http://csperkins.org/misc/ietf61-avt-day2.zip

Colin


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Thu Nov 11 13:24:39 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09965
	for <avt-archive@ietf.org>; Thu, 11 Nov 2004 13:24:39 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSJdt-0000kS-LL
	for avt-archive@ietf.org; Thu, 11 Nov 2004 13:25:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSJUs-0003Bo-9x; Thu, 11 Nov 2004 13:16:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSJSD-0002UT-82
	for avt@megatron.ietf.org; Thu, 11 Nov 2004 13:13:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08885
	for <avt@ietf.org>; Thu, 11 Nov 2004 13:13:50 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSJTQ-0000VS-9E
	for avt@ietf.org; Thu, 11 Nov 2004 13:15:08 -0500
Received: from zcard303.ca.nortel.com (zcard303.ca.nortel.com [47.129.242.59])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iABIDEP20082; Thu, 11 Nov 2004 13:13:14 -0500 (EST)
Received: from [47.140.54.97] (artpt64s.us.nortel.com [47.140.54.97]) by
	zcard303.ca.nortel.com with SMTP (Microsoft Exchange Internet
	Mail Service Version 5.5.2653.13)
	id W14FPPYP; Thu, 11 Nov 2004 13:13:14 -0500
Message-ID: <4193ABB5.4030102@nortelnetworks.com>
Date: Thu, 11 Nov 2004 13:13:09 -0500
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "COLDREN, REX A (REX)" <coldrenr@lucent.com>
Subject: Re: [AVT] Exceptional treatment of E bit for state events in 2833bis
References: <17D8724A2A8D9542B2B8AE546B9E5BBC031F8C8A@AZ4315EXCH001U>
In-Reply-To: <17D8724A2A8D9542B2B8AE546B9E5BBC031F8C8A@AZ4315EXCH001U>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7bit

Well, you certainly know where all the skeletons are buried.  I'd better leave it 
alone.  I'd also better track down that NAR trunk gateway specification you 
mentioned privately to see what 2833bis breaks.

COLDREN, REX A (REX) wrote:
> This one comes from the trunk events, where one state is necessarily 
> exclusive of all others.  For them, the 'E' bit is not useful and is 
> deemed to be, in fact, problematic.  For example, while reporting a
> stable off-hook state in real time with RFC 2833 packets every 50ms,
> there is an inherent 50ms delay (perhaps more with de-bouncing code)
> in reporting the end of event (e.g. on-hook event occurred but one
> additional off-hook needs to be sent with the 'E' bit set).
> 
> This is but an example.  I don't know how many of the other state
> related events would be affected by changing this requirement.
> 
> Rex
> 
> -----Original Message-----
> From: Tom Taylor [mailto:taylor@nortelnetworks.com]
> Sent: Wednesday, November 10, 2004 12:52 PM
> To: avt@ietf.org
> Subject: [AVT] Exceptional treatment of E bit for state events in
> 2833bis
> 
> 
> draft-ietf-avt-rfc2833bis-05.txt section 2.5.1.2 contains the following text 
> regarding the setting of 'E' (end) bits for events that are states:
> 
>        Sending of a packet with the "E" bit set is OPTIONAL if the packet
>        reports two events which are defined as mutually exclusive states, or
>        if the final packet for one state is immediately followed by a packet
>        reporting a mutually exclusive state.  (For events defined as states,
>        the appearance of a mutually exclusive state implies the end of the
>        previous state.)
> 
> This is a small optimization at the potential expense of a bunch of extra code.  I 
> really don't see it as worth the effort.  I propose to delete it unless someone 
> makes a good case otherwise.
> 
> Comments?
> 

-- 
Tom Taylor
Carrier VoIP Standards Development
Nortel Networks
Phone +1 613 763 1496  (ESN 393-1496)
E-mail: taylor@nortelnetworks.com

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Thu Nov 11 16:43:00 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01822
	for <avt-archive@ietf.org>; Thu, 11 Nov 2004 16:43:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSMjr-00066g-B7
	for avt-archive@ietf.org; Thu, 11 Nov 2004 16:44:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSMUV-000443-7K; Thu, 11 Nov 2004 16:28:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSMM4-0007UR-Mg
	for avt@megatron.ietf.org; Thu, 11 Nov 2004 16:19:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29285
	for <avt@ietf.org>; Thu, 11 Nov 2004 16:19:42 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSMNJ-0005Qi-3V
	for avt@ietf.org; Thu, 11 Nov 2004 16:21:01 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iABLJ5W12209; Thu, 11 Nov 2004 16:19:05 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WVCTCQ28>; Thu, 11 Nov 2004 16:19:05 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCFFBD076@zrc2hxm0.corp.nortel.com>
From: "Francois Audet" <audet@nortelnetworks.com>
To: "'Dan Wing'" <dwing@cisco.com>, "'Randell Jesup'" <rjesup@wgate.com>
Subject: RE: [AVT] RE: [Ietf-behave] RTP in draft-ietf-behave-nat-00
Date: Thu, 11 Nov 2004 16:18:51 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: fac892abe0c719c7bb99f6e7c710cdae
Cc: "'fluffy@cisco.com'" <fluffy@cisco.com>,
        "'Stephen Casner'" <casner@acm.org>,
        "'ietf-behave@list.sipfoundry.org'" <ietf-behave@list.sipfoundry.org>,
        "'AVT WG'" <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1133563604=="
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: a630332fa112280ecc4c4186b5c9ea83

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============1133563604==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C834.0C01F178"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C4C834.0C01F178
Content-Type: text/plain

Dan is correct.

The intent is definitively NOT that application can rely on ports being odd
or even.

We will address your points in an upcoming version of the document and in
the application
draft.

> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com] 
> Sent: Thursday, November 11, 2004 07:32
> To: Randell Jesup
> Cc: Stephen Casner; Audet, Francois [SC100:9T51:EXCH]; 
> fluffy@cisco.com; AVT WG; ietf-behave@list.sipfoundry.org
> Subject: RE: [AVT] RE: [Ietf-behave] RTP in draft-ietf-behave-nat-00
> 
> 
> Randell Jesup:
> 
> > "Dan Wing" <dwing@cisco.com> writes:
> > >To your first point, I believe we resolved this, in a positive
> > way, on the
> > >list; -00 doesn't yet reflect those changes.  We decided 
> to require 
> > >NATs to preserve even and odd port numbers when they 
> create their UDP
> > bindings,
> > >as this provides the best interoperability for RTP 
> applications that 
> > >don't/can't provide explicit signaling of their RTCP port.
> >
> >         Ummm...
> >
> >         And how will you "require" NATs to do this?  This 
> would mean 
> > that all NATs would need to map all UDP traffic to the same oddness 
> > (even->even,
> > odd->odd).  While sure, the NAT vendors _could_ write code this
> > way (though
> > it may well break some current NAT-traversal code that tries to do 
> > predictive mapping), there are millions of NATs out there that will 
> > never implement this, and nothing to force new releases to do so.
> >
> >         The even/odd port thing was (IMHO) a Bad Idea (in 
> hindsight), 
> > I assume meant to avoid having to figure out how to signal 
> the number 
> > for the second port - and even for that even/odd wasn't 
> really needed, 
> > all you needed was contiguous.  Other TCP/UDP protocols 
> don't do these 
> > sorts of things with port numbers (even/odd, or implied 
> relationships 
> > between port
> > numbers) - it's much better to actually signal the ports to be used.
> >
> >         We shouldn't compound it by "requiring" NATs 
> maintain oddness 
> > (after the horse is not only out of the barn, but 12 miles down the 
> > road). We're apparently trying to avoid breaking "RTP applications 
> > that don't/can't provide explicit signaling of their RTCP port" by 
> > putting a requirement on NATs that will at best be phased in over 
> > years, and at worst totally ignored, instead of requiring RTP 
> > applications to specify both RTP and RTCP ports.  The 
> effect will be 
> > that RTP applications that attempt to rely on this NAT requirement 
> > will end up breaking in many situations, and quite probably in 
> > unpredictable ways.  (For example, many NATs try to maintain port 
> > numbers inside->outside, but if the port is in use will 
> then allocate 
> > other non-contiguous port numbers of different oddness.)
> >
> >         The original idea (even/odd pairs) wasn't a good 
> one, and was 
> > somewhat at odds with normal techniques in TCP/UDP, and 
> certainly at 
> > odds with any sort of NAT concept.  (Note: just my opinion, 
> of course)
> >
> >         Of course, having a NAT preserve oddness (and contiguity!) 
> > will improve the odds of an older RTP application working 
> from behind 
> > it, so it might be a *nice* thing to do in the NAT - but no 
> one should 
> > be counting on it, and it's yet another complication in NAT 
> design and 
> > limitation that could cause it to run out of ports (in a large 
> > corporate-style NAT).
> 
> I'll leave the draft-ietf-behave-nat authors to comment on 
> the specific text they're considering; it's my understanding 
> they are adding text which hits on your points above.
> 
> > >To your second, a reference to RFC3605 will be added to the 
> > >'application behavior' document, which will describe how 
> applications 
> > >should behave. The current BEHAVE document just describes how NATs 
> > >should behave.
> >
> >         If BEHAVE is how they "should" behave, then my 
> objections are 
> > lessened - though we need to make sure that people don't use this 
> > document as an excuse not to specify the RTCP port.
> 
> Application behavior will be in the application document (not 
> in draft-ietf-behave-nat); Francois and I are going to take a 
> first cut at the application document in the next month or 
> two.  The application document is described as "Produce a BCP 
> that discusses protocol design techniques for using the 
> existing set of NAT traversal approaches" in the BEHAVE 
> charter <http://www.ietf.org/html.charters/behave-charter.html>.
> 
> -d
> 
> 
> 

------_=_NextPart_001_01C4C834.0C01F178
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>RE: [AVT] RE: [Ietf-behave] RTP in =
draft-ietf-behave-nat-00</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Dan is correct.</FONT>
</P>

<P><FONT SIZE=3D2>The intent is definitively NOT that application can =
rely on ports being odd or even.</FONT>
</P>

<P><FONT SIZE=3D2>We will address your points in an upcoming version of =
the document and in the application</FONT>
<BR><FONT SIZE=3D2>draft.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Dan Wing [<A =
HREF=3D"mailto:dwing@cisco.com">mailto:dwing@cisco.com</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Thursday, November 11, 2004 07:32</FONT>
<BR><FONT SIZE=3D2>&gt; To: Randell Jesup</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: Stephen Casner; Audet, Francois =
[SC100:9T51:EXCH]; </FONT>
<BR><FONT SIZE=3D2>&gt; fluffy@cisco.com; AVT WG; =
ietf-behave@list.sipfoundry.org</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [AVT] RE: [Ietf-behave] RTP in =
draft-ietf-behave-nat-00</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Randell Jesup:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &quot;Dan Wing&quot; =
&lt;dwing@cisco.com&gt; writes:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;To your first point, I believe we =
resolved this, in a positive</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; way, on the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;list; -00 doesn't yet reflect those =
changes.&nbsp; We decided </FONT>
<BR><FONT SIZE=3D2>&gt; to require </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;NATs to preserve even and odd port =
numbers when they </FONT>
<BR><FONT SIZE=3D2>&gt; create their UDP</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; bindings,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;as this provides the best =
interoperability for RTP </FONT>
<BR><FONT SIZE=3D2>&gt; applications that </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;don't/can't provide explicit signaling =
of their RTCP port.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ummm...</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; And how will you =
&quot;require&quot; NATs to do this?&nbsp; This </FONT>
<BR><FONT SIZE=3D2>&gt; would mean </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; that all NATs would need to map all UDP =
traffic to the same oddness </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; (even-&gt;even,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; odd-&gt;odd).&nbsp; While sure, the NAT =
vendors _could_ write code this</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; way (though</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; it may well break some current =
NAT-traversal code that tries to do </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; predictive mapping), there are millions of =
NATs out there that will </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; never implement this, and nothing to force =
new releases to do so.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The even/odd port =
thing was (IMHO) a Bad Idea (in </FONT>
<BR><FONT SIZE=3D2>&gt; hindsight), </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I assume meant to avoid having to figure =
out how to signal </FONT>
<BR><FONT SIZE=3D2>&gt; the number </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; for the second port - and even for that =
even/odd wasn't </FONT>
<BR><FONT SIZE=3D2>&gt; really needed, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; all you needed was contiguous.&nbsp; Other =
TCP/UDP protocols </FONT>
<BR><FONT SIZE=3D2>&gt; don't do these </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; sorts of things with port numbers =
(even/odd, or implied </FONT>
<BR><FONT SIZE=3D2>&gt; relationships </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; between port</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; numbers) - it's much better to actually =
signal the ports to be used.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; We shouldn't =
compound it by &quot;requiring&quot; NATs </FONT>
<BR><FONT SIZE=3D2>&gt; maintain oddness </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; (after the horse is not only out of the =
barn, but 12 miles down the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; road). We're apparently trying to avoid =
breaking &quot;RTP applications </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; that don't/can't provide explicit =
signaling of their RTCP port&quot; by </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; putting a requirement on NATs that will at =
best be phased in over </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; years, and at worst totally ignored, =
instead of requiring RTP </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; applications to specify both RTP and RTCP =
ports.&nbsp; The </FONT>
<BR><FONT SIZE=3D2>&gt; effect will be </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; that RTP applications that attempt to rely =
on this NAT requirement </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; will end up breaking in many situations, =
and quite probably in </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; unpredictable ways.&nbsp; (For example, =
many NATs try to maintain port </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; numbers inside-&gt;outside, but if the =
port is in use will </FONT>
<BR><FONT SIZE=3D2>&gt; then allocate </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; other non-contiguous port numbers of =
different oddness.)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The original idea =
(even/odd pairs) wasn't a good </FONT>
<BR><FONT SIZE=3D2>&gt; one, and was </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; somewhat at odds with normal techniques in =
TCP/UDP, and </FONT>
<BR><FONT SIZE=3D2>&gt; certainly at </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; odds with any sort of NAT concept.&nbsp; =
(Note: just my opinion, </FONT>
<BR><FONT SIZE=3D2>&gt; of course)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Of course, having =
a NAT preserve oddness (and contiguity!) </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; will improve the odds of an older RTP =
application working </FONT>
<BR><FONT SIZE=3D2>&gt; from behind </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; it, so it might be a *nice* thing to do in =
the NAT - but no </FONT>
<BR><FONT SIZE=3D2>&gt; one should </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; be counting on it, and it's yet another =
complication in NAT </FONT>
<BR><FONT SIZE=3D2>&gt; design and </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; limitation that could cause it to run out =
of ports (in a large </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; corporate-style NAT).</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I'll leave the draft-ietf-behave-nat authors to =
comment on </FONT>
<BR><FONT SIZE=3D2>&gt; the specific text they're considering; it's my =
understanding </FONT>
<BR><FONT SIZE=3D2>&gt; they are adding text which hits on your points =
above.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;To your second, a reference to RFC3605 =
will be added to the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;'application behavior' document, which =
will describe how </FONT>
<BR><FONT SIZE=3D2>&gt; applications </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;should behave. The current BEHAVE =
document just describes how NATs </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;should behave.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If BEHAVE is how =
they &quot;should&quot; behave, then my </FONT>
<BR><FONT SIZE=3D2>&gt; objections are </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; lessened - though we need to make sure =
that people don't use this </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; document as an excuse not to specify the =
RTCP port.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Application behavior will be in the application =
document (not </FONT>
<BR><FONT SIZE=3D2>&gt; in draft-ietf-behave-nat); Francois and I are =
going to take a </FONT>
<BR><FONT SIZE=3D2>&gt; first cut at the application document in the =
next month or </FONT>
<BR><FONT SIZE=3D2>&gt; two.&nbsp; The application document is =
described as &quot;Produce a BCP </FONT>
<BR><FONT SIZE=3D2>&gt; that discusses protocol design techniques for =
using the </FONT>
<BR><FONT SIZE=3D2>&gt; existing set of NAT traversal approaches&quot; =
in the BEHAVE </FONT>
<BR><FONT SIZE=3D2>&gt; charter &lt;<A =
HREF=3D"http://www.ietf.org/html.charters/behave-charter.html" =
TARGET=3D"_blank">http://www.ietf.org/html.charters/behave-charter.html<=
/A>&gt;.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -d</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C4C834.0C01F178--


--===============1133563604==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

--===============1133563604==--



From avt-bounces@ietf.org  Thu Nov 11 16:44:19 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01966
	for <avt-archive@ietf.org>; Thu, 11 Nov 2004 16:44:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSMl7-00069B-Iv
	for avt-archive@ietf.org; Thu, 11 Nov 2004 16:45:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSMXu-00055E-Ms; Thu, 11 Nov 2004 16:31:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSMQq-0001sT-H5
	for avt@megatron.ietf.org; Thu, 11 Nov 2004 16:24:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29886
	for <avt@ietf.org>; Thu, 11 Nov 2004 16:24:38 -0500 (EST)
Received: from ondar.cablelabs.com ([192.160.73.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSMS1-0005bL-Vt
	for avt@ietf.org; Thu, 11 Nov 2004 16:25:57 -0500
Received: from srvxchg.cablelabs.com (srvxchg.cablelabs.com [10.5.0.20])
	by ondar.cablelabs.com (8.12.10/8.12.10) with ESMTP id iABLNx1e004928; 
	Thu, 11 Nov 2004 14:23:59 -0700 (MST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: [AVT] comments on draft-ietf-avt-rtcp-xr-mib-00.txt
Date: Thu, 11 Nov 2004 14:23:59 -0700
Message-ID: <CD6CE349CFD30D40BF5E13B3E0D8480406A418@srvxchg.cablelabs.com>
Thread-Topic: [AVT] comments on draft-ietf-avt-rtcp-xr-mib-00.txt
Thread-Index: AcTCUuSiOrF8FfRITiypLoiXuSVLQwF3XMEg
From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
To: <aspen@nortelnetworks.com>, <alan@telchemy.com>, <avt@ietf.org>
X-Approved: ondar
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: quoted-printable
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: quoted-printable

Hi,

   Here is a follow-up to the comments I made at the mike during the avt
meeting.

--- Add object to indicate what computational model is used to calculate
the call quality metrics
This comment pertains to the call quality metrics (R factors and
potentially mean opinion scores). I believe it would be valuable to
indicate in the MIB module what particular model or algorithm was used
so that the mgmt application can understand the reference points for the
values being polled.

As Alan stated, the models are constantly evolving and it is likely that
vendors will be creative in fine tuning how those metrics are calculated
in impaired networks. While g.107 is currently named as one option, it
won't be the only one.
Hope this clarifies the request, otherwise let me know.


--- re: discussion at the mike about VoIP metric block extension
We had a subsequent discussion at the mike with Michael R. on extending
the VoIP Metrics Report Block to indicate the algorithm to the remote
peer inside RTCP XR. I just wanted to clarify my statement. I believe
this is a separate question and that the MIB objects can be added today
without waiting for the rfc update or the extension.=20


Jean-Francois=20
PS: re: Dan's comment 21, here is the section you may want to add based
on what we use in ipcdn.
x. IANA Considerations

   The MIB module defined in this document uses the following IANA-
   assigned OBJECT IDENTIFIER value recorded in the SMI Numbers
   registry:

   Descriptor    OBJECT IDENTIFIER value
   ----------    -----------------------
   rtcpXrMIB     { mib-2 XX }

       -- ***********************************************************
       -- * Note to RFC Editor (to be removed)
       -- *  The IANA is requested to assign a value for XX under the
       -- *  mib-2 subtree and to record the assignment in the SMI
       -- *  Numbers registry. When the assignment has been made, the
       -- *  RFC Editor is asked to replace xx (here and in the MIB
       -- *  module) with the assigned value and to remove this note.
       -- ***********************************************************

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Thu Nov 11 18:17:15 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12181
	for <avt-archive@ietf.org>; Thu, 11 Nov 2004 18:17:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSOD5-0000Fl-OW
	for avt-archive@ietf.org; Thu, 11 Nov 2004 18:18:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSO5i-0007xx-8Y; Thu, 11 Nov 2004 18:10:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSNx9-0002e3-HV
	for avt@megatron.ietf.org; Thu, 11 Nov 2004 18:02:07 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09808
	for <avt@ietf.org>; Thu, 11 Nov 2004 18:02:05 -0500 (EST)
Received: from dns.packetdesign.com ([65.192.41.10]
	helo=mailman.packetdesign.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSNyO-0008Gw-Tb
	for avt@ietf.org; Thu, 11 Nov 2004 18:03:25 -0500
Received: from packetdesign.com (main-fw-eth1.packetdesign.com [192.168.0.254])
	by mailman.packetdesign.com (8.12.8/8.12.8) with ESMTP id
	iABN1RCJ082550; Thu, 11 Nov 2004 15:01:27 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Thu, 11 Nov 2004 15:02:34 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: Tom Taylor <taylor@nortelnetworks.com>
Subject: Re: [AVT] Handling lost marker packet in 2833bis
In-Reply-To: <4192898C.8040900@nortelnetworks.com>
Message-ID: <20041111150044.J57058@oak.packetdesign.com>
References: <4192898C.8040900@nortelnetworks.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081

Tom,

The way that packet loss is detected is through the sequence number.
The missing M bit is another indication, but the primary indication is
the sequence number gap.

                                                        -- Steve

On Wed, 10 Nov 2004, Tom Taylor wrote:

> Kevin Noll had asked for advice in 2833bis on what to do if the initial packet of
> an event report (with the 'M' bit set) got lost but subsequent packets were
> received.  I did incorporate some advice in rfc2833bis-05, but it's probably a
> good idea to put it out to the list for consideration.  Here's what was added to
> rfc2833bis-05:
>
>     2.5.2.2  Playout of Tone Events
> ....
>        If a receiver receives an event packet for an event which it is not
>        currently playing out and the packet does not have the "M" bit set,
>        earlier packets for that event have evidently been lost.  The
>        receiver MAY determine on the basis of retained history and the
>        timestamp and event code of the current packet that it corresponds to
>        an event already played out and lapsed.  In that case further reports
>        for the event MUST be ignored, as indicated in the previous
>        paragraph.  If this is not so, the receiver MAY attempt to play the
>        event out to the complete duration indicated in the event report.
>        The appropriate behaviour will depend on the event type concerned,
>        and requires consideration of the relationship of the event to audio
>        media flows and whether correct event duration is essential to the
>        correct operation of the media session.
>
> --
> Tom Taylor
> Carrier VoIP Standards Development
> Nortel Networks
> Phone +1 613 763 1496  (ESN 393-1496)
> E-mail: taylor@nortelnetworks.com
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Thu Nov 18 18:38:20 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04041
	for <avt-archive@ietf.org>; Thu, 18 Nov 2004 18:38:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CUvto-0002bo-1c
	for avt-archive@ietf.org; Thu, 18 Nov 2004 18:41:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUvoB-0007l4-CX; Thu, 18 Nov 2004 18:35:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUvl3-0006vH-TR; Thu, 18 Nov 2004 18:32:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03541;
	Thu, 18 Nov 2004 18:32:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CUvnm-0002U7-ED; Thu, 18 Nov 2004 18:34:58 -0500
Received: from apache by megatron.ietf.org with local (Exim 4.32)
	id 1CUvbv-0003jv-An; Thu, 18 Nov 2004 18:22:43 -0500
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1CUvbv-0003jv-An@megatron.ietf.org>
Date: Thu, 18 Nov 2004 18:22:43 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: avt@ietf.org
Subject: [AVT] Last Call: 'RTP Payload for Text Conversation' to Proposed
	Standard 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@ietf.org
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f

The IESG has received a request from the Audio/Video Transport WG to consider 
the following document:

- 'RTP Payload for Text Conversation '
   <draft-ietf-avt-rfc2793bis-09.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2004-12-02.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc2793bis-09.txt


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Fri Nov 19 10:57:09 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14713
	for <avt-archive@ietf.org>; Fri, 19 Nov 2004 10:57:09 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVBAz-0007lh-7s
	for avt-archive@ietf.org; Fri, 19 Nov 2004 11:00:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVAwz-0005XY-42; Fri, 19 Nov 2004 10:45:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CVArU-0004Af-81
	for avt@megatron.ietf.org; Fri, 19 Nov 2004 10:39:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13068
	for <avt@ietf.org>; Fri, 19 Nov 2004 10:39:46 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVAu9-0007LI-C3
	for avt@ietf.org; Fri, 19 Nov 2004 10:42:45 -0500
Received: from esealmw129.eemea.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iAJFdNR2025694; Fri, 19 Nov 2004 16:39:26 +0100
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 19 Nov 2004 16:39:23 +0100
Received: from esealmw104.eemea.ericsson.se ([153.88.200.67]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 19 Nov 2004 16:39:23 +0100
Content-class: urn:content-classes:message
Subject: RE: [AVT] RFC3711: Srtp Parameters for Rx/Tx ?
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 19 Nov 2004 16:39:22 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Message-ID: <3AD208E1F0D5EB47AC3C5617420BCB0210622A@esealmw104.eemea.ericsson.se>
Thread-Topic: [AVT] RFC3711: Srtp Parameters for Rx/Tx ?
Thread-Index: AcTOSf2a1sypKxwbSFeSSkGrUB1BvgAA5Yqw
From: "Karl Norrman \(KI/EAB\)" <karl.norrman@ericsson.com>
To: "milo diurn" <srtpdev@hotmail.com>
X-OriginalArrivalTime: 19 Nov 2004 15:39:23.0429 (UTC)
	FILETIME=[F197FD50:01C4CE4D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: quoted-printable
Cc: "Elisabetta Carrara \(KI/EAB\)" <elisabetta.carrara@ericsson.com>,
        mcgrew@cisco.com, avt@ietf.org, mbaugher@cisco.com
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: quoted-printable

Hello!

SRTP does not provide the functionality to exchange the parameters =
needed,
but relies on a key management protocol (e.g., RFC 3830, MIKEY) to do =
that.

Regards,
Karl

> -----Original Message-----
> From: milo diurn [mailto:srtpdev@hotmail.com]
> Sent: den 19 november 2004 16:11
> To: Karl Norrman (KI/EAB)
> Cc: avt@ietf.org; mbaugher@cisco.com; Elisabetta Carrara (KI/EAB);
> mcgrew@cisco.com
> Subject: [AVT] RFC3711: Srtp Parameters for Rx/Tx ?
>=20
>=20
> Karl, and Srtp community,
>=20
> In RFC3711, I do not see any clear way of setting the Srtp=20
> parameters (chap=20
> 8.2)
> for both ways of the session:
> - Transmit : need the Srtp parameters for Encryption (to be=20
> sent to the=20
> network)
> - Receive: need the Srtp parameters for Decryption (to be=20
> received from the=20
> network).
>=20
> Could you, please, clarify this point ?
>=20
> Thanks
>=20
> Regards
>=20
> _________________________________________________________________
> FREE pop-up blocking with the new MSN Toolbar - get it now!=20
> http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
>=20

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Fri Nov 19 11:16:02 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16786
	for <avt-archive@ietf.org>; Fri, 19 Nov 2004 11:16:01 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVBTR-0008FK-FD
	for avt-archive@ietf.org; Fri, 19 Nov 2004 11:19:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVBO1-0004DO-FB; Fri, 19 Nov 2004 11:13:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CVBKI-00034g-Jb
	for avt@megatron.ietf.org; Fri, 19 Nov 2004 11:09:34 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16072
	for <avt@ietf.org>; Fri, 19 Nov 2004 11:09:32 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVBMz-00085e-9S
	for avt@ietf.org; Fri, 19 Nov 2004 11:12:32 -0500
Received: from esealmw129.eemea.ericsson.se ([153.88.254.120])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iAJG8Eh5017561; Fri, 19 Nov 2004 17:08:14 +0100 (MET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 19 Nov 2004 17:08:13 +0100
Received: from esealmw104.eemea.ericsson.se ([153.88.200.67]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 19 Nov 2004 17:08:13 +0100
Content-class: urn:content-classes:message
Subject: RE: [AVT] RFC3711: Srtp key_id ?
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 19 Nov 2004 17:08:12 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Message-ID: <3AD208E1F0D5EB47AC3C5617420BCB0210622C@esealmw104.eemea.ericsson.se>
Thread-Topic: [AVT] RFC3711: Srtp key_id ?
Thread-Index: AcTOUWXGKzZ/48BDQjKU6RWvA6QxOAAAD7sw
From: "Karl Norrman \(KI/EAB\)" <karl.norrman@ericsson.com>
To: "milo diurn" <srtpdev@hotmail.com>
X-OriginalArrivalTime: 19 Nov 2004 16:08:13.0297 (UTC)
	FILETIME=[F8ACE610:01C4CE51]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: quoted-printable
Cc: "Elisabetta Carrara \(KI/EAB\)" <elisabetta.carrara@ericsson.com>,
        "David A. McGrew" <mcgrew@cisco.com>, mbaugher@cisco.com, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: quoted-printable

Hello!

I think there is a slight misunderstanding here.
I suppose Milo is referring to "key_id" on Page 27.
It is there used as variable (place holder) to easy
up the notation.

Regards,
Karl

> -----Original Message-----
> From: David A. McGrew [mailto:mcgrew@cisco.com]
> Sent: den 19 november 2004 17:04
> To: milo diurn
> Cc: mbaugher@cisco.com; Karl Norrman (KI/EAB); avt@ietf.org;=20
> Elisabetta
> Carrara (KI/EAB)
> Subject: Re: [AVT] RFC3711: Srtp key_id ?
>=20
>=20
> Milo,
>=20
> On Nov 19, 2004, at 7:12 AM, milo diurn wrote:
>=20
> > Karl, and Srtp community,
> >
> > In RFC3711,
> > how is key_id defined and by which part (external/internal) ?
>=20
> it is defined externally.  From Section 3.1:
>=20
>     MKI (Master Key Identifier): configurable length, OPTIONAL.  The
>                MKI is defined, signaled, and used by key management.
>=20
>=20
> >
> > If key_id belongs to the Srtp parameters, why do not=20
> referring to it in
> > the parameters list (chap 8.2) ?
>=20
> It is there, but you might have missed it because it is only referred=20
> to by the acronym "MKI"
>=20
> Hope this helps!
>=20
> David
>=20
> >
> > Could you, please, clarify this point ?
> >
> > Thanks
> >
> > Regards
> >
> > _________________________________________________________________
> > FREE pop-up blocking with the new MSN Toolbar - get it now!=20
> > http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
> >
>=20

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Fri Nov 19 11:31:37 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18231
	for <avt-archive@ietf.org>; Fri, 19 Nov 2004 11:31:36 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVBiV-000090-PB
	for avt-archive@ietf.org; Fri, 19 Nov 2004 11:34:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVBaM-0007RO-Go; Fri, 19 Nov 2004 11:26:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CVAQC-0003vx-Dw
	for avt@megatron.ietf.org; Fri, 19 Nov 2004 10:11:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09600
	for <avt@ietf.org>; Fri, 19 Nov 2004 10:11:34 -0500 (EST)
Received: from bay2-f4.bay2.hotmail.com ([65.54.247.4] helo=hotmail.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVAT2-0006fe-0t
	for avt@ietf.org; Fri, 19 Nov 2004 10:14:33 -0500
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Fri, 19 Nov 2004 07:11:02 -0800
Message-ID: <BAY2-F4E529CB87AB6ED9E66E42BDC30@phx.gbl>
Received: from 199.33.79.4 by by2fd.bay2.hotmail.msn.com with HTTP;
	Fri, 19 Nov 2004 15:10:43 GMT
X-Originating-IP: [199.33.79.4]
X-Originating-Email: [srtpdev@hotmail.com]
X-Sender: srtpdev@hotmail.com
From: "milo diurn" <srtpdev@hotmail.com>
To: karl.norrman@ericsson.com
Subject: [AVT] RFC3711: Srtp Parameters for Rx/Tx ?
Date: Fri, 19 Nov 2004 15:10:43 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
X-OriginalArrivalTime: 19 Nov 2004 15:11:02.0901 (UTC)
	FILETIME=[FC000250:01C4CE49]
X-Spam-Score: 3.7 (+++)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
X-Mailman-Approved-At: Fri, 19 Nov 2004 11:26:08 -0500
Cc: elisabetta.carrara@ericsson.com, mcgrew@cisco.com, avt@ietf.org,
        mbaugher@cisco.com
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 3.7 (+++)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32

Karl, and Srtp community,

In RFC3711, I do not see any clear way of setting the Srtp parameters (chap 
8.2)
for both ways of the session:
- Transmit : need the Srtp parameters for Encryption (to be sent to the 
network)
- Receive: need the Srtp parameters for Decryption (to be received from the 
network).

Could you, please, clarify this point ?

Thanks

Regards

_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar - get it now! 
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Fri Nov 19 11:32:17 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18274
	for <avt-archive@ietf.org>; Fri, 19 Nov 2004 11:32:17 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVBjA-0000AO-GF
	for avt-archive@ietf.org; Fri, 19 Nov 2004 11:35:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVBaN-0007RT-2L; Fri, 19 Nov 2004 11:26:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CVASA-0004xX-KV
	for avt@megatron.ietf.org; Fri, 19 Nov 2004 10:13:38 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09923
	for <avt@ietf.org>; Fri, 19 Nov 2004 10:13:36 -0500 (EST)
Received: from bay2-f10.bay2.hotmail.com ([65.54.247.10] helo=hotmail.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVAV0-0006iU-Cw
	for avt@ietf.org; Fri, 19 Nov 2004 10:16:35 -0500
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Fri, 19 Nov 2004 07:13:04 -0800
Message-ID: <BAY2-F10605E9897A60510000F1CBDC30@phx.gbl>
Received: from 199.33.79.4 by by2fd.bay2.hotmail.msn.com with HTTP;
	Fri, 19 Nov 2004 15:12:03 GMT
X-Originating-IP: [199.33.79.4]
X-Originating-Email: [srtpdev@hotmail.com]
X-Sender: srtpdev@hotmail.com
From: "milo diurn" <srtpdev@hotmail.com>
To: karl.norrman@ericsson.com
Subject: [AVT] RFC3711: Srtp key_id ?
Date: Fri, 19 Nov 2004 15:12:03 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
X-OriginalArrivalTime: 19 Nov 2004 15:13:04.0260 (UTC)
	FILETIME=[4455EC40:01C4CE4A]
X-Spam-Score: 3.7 (+++)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
X-Mailman-Approved-At: Fri, 19 Nov 2004 11:26:08 -0500
Cc: elisabetta.carrara@ericsson.com, mcgrew@cisco.com, avt@ietf.org,
        mbaugher@cisco.com
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 3.7 (+++)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906

Karl, and Srtp community,

In RFC3711,
how is key_id defined and by which part (external/internal) ?

If key_id belongs to the Srtp parameters, why do not referring to it in
the parameters list (chap 8.2) ?

Could you, please, clarify this point ?

Thanks

Regards

_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar - get it now! 
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Fri Nov 19 11:33:17 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18531
	for <avt-archive@ietf.org>; Fri, 19 Nov 2004 11:33:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVBk7-0000DC-Qy
	for avt-archive@ietf.org; Fri, 19 Nov 2004 11:36:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVBaN-0007Rk-Ma; Fri, 19 Nov 2004 11:26:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CVATE-0005Rc-Az
	for avt@megatron.ietf.org; Fri, 19 Nov 2004 10:14:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10135
	for <avt@ietf.org>; Fri, 19 Nov 2004 10:14:42 -0500 (EST)
Received: from bay2-f2.bay2.hotmail.com ([65.54.247.2] helo=hotmail.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVAW3-0006kQ-PS
	for avt@ietf.org; Fri, 19 Nov 2004 10:17:41 -0500
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Fri, 19 Nov 2004 07:14:04 -0800
Message-ID: <BAY2-F2DDC3FB0EDD1DC7D6CD03BDC30@phx.gbl>
Received: from 199.33.79.4 by by2fd.bay2.hotmail.msn.com with HTTP;
	Fri, 19 Nov 2004 15:13:20 GMT
X-Originating-IP: [199.33.79.4]
X-Originating-Email: [srtpdev@hotmail.com]
X-Sender: srtpdev@hotmail.com
From: "milo diurn" <srtpdev@hotmail.com>
To: karl.norrman@ericsson.com
Subject: [AVT] RFC3711: Srtp salt_key
Date: Fri, 19 Nov 2004 15:13:20 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
X-OriginalArrivalTime: 19 Nov 2004 15:14:04.0775 (UTC)
	FILETIME=[6867C770:01C4CE4A]
X-Spam-Score: 3.7 (+++)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
X-Mailman-Approved-At: Fri, 19 Nov 2004 11:26:08 -0500
Cc: elisabetta.carrara@ericsson.com, mcgrew@cisco.com, avt@ietf.org,
        mbaugher@cisco.com
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 3.7 (+++)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906

Karl, and Srtp community,

In RFC3711, Chap 11.1 shows how the generated keys order is :
SRTP_encr_key, SRTP_auth_key, SRTCP_encr_key, and SRTCP_auth key.

How about the generated SRTP_salt_key, SRTCP_salt_key ?
Where are they located in the list ?

Could you, please, clarify this point ?

Thanks

Regards

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Fri Nov 19 11:34:21 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18604
	for <avt-archive@ietf.org>; Fri, 19 Nov 2004 11:34:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVBl9-0000Et-Th
	for avt-archive@ietf.org; Fri, 19 Nov 2004 11:37:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVBaO-0007UG-O7; Fri, 19 Nov 2004 11:26:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CVBAS-0000EP-Iy
	for avt@megatron.ietf.org; Fri, 19 Nov 2004 10:59:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14864
	for <avt@ietf.org>; Fri, 19 Nov 2004 10:59:22 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVBDI-0007pg-OJ for avt@ietf.org; Fri, 19 Nov 2004 11:02:22 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 19 Nov 2004 09:03:47 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iAJFwf3O029910;
	Fri, 19 Nov 2004 07:58:42 -0800 (PST)
Received: from [10.32.254.210] ([10.32.254.210])
	by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with SMTP id AZD50011;
	Fri, 19 Nov 2004 08:04:28 -0800 (PST)
In-Reply-To: <BAY2-F2DDC3FB0EDD1DC7D6CD03BDC30@phx.gbl>
References: <BAY2-F2DDC3FB0EDD1DC7D6CD03BDC30@phx.gbl>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <A0D55704-3A43-11D9-85C1-0003935495EC@cisco.com>
Content-Transfer-Encoding: 7bit
From: "David A. McGrew" <mcgrew@cisco.com>
Subject: Re: [AVT] RFC3711: Srtp salt_key
Date: Fri, 19 Nov 2004 07:56:51 -0800
To: "milo diurn" <srtpdev@hotmail.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 19 Nov 2004 11:26:08 -0500
Cc: karl.norrman@ericsson.com, elisabetta.carrara@ericsson.com,
        mbaugher@cisco.com, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit

Milo,

On Nov 19, 2004, at 7:13 AM, milo diurn wrote:

> Karl, and Srtp community,
>
> In RFC3711, Chap 11.1 shows how the generated keys order is :
> SRTP_encr_key, SRTP_auth_key, SRTCP_encr_key, and SRTCP_auth key.
>
> How about the generated SRTP_salt_key, SRTCP_salt_key ?
> Where are they located in the list ?

the salt is an input to the key derivation process, not an output from 
it.

David

>
> Could you, please, clarify this point ?
>
> Thanks
>
> Regards
>
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today it's 
> FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Fri Nov 19 11:35:40 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18736
	for <avt-archive@ietf.org>; Fri, 19 Nov 2004 11:35:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVBmR-0000Gv-HB
	for avt-archive@ietf.org; Fri, 19 Nov 2004 11:38:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVBaP-0007UP-Eo; Fri, 19 Nov 2004 11:26:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CVBAV-0000EW-Cy
	for avt@megatron.ietf.org; Fri, 19 Nov 2004 10:59:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14867
	for <avt@ietf.org>; Fri, 19 Nov 2004 10:59:25 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVBDL-0007pn-HE for avt@ietf.org; Fri, 19 Nov 2004 11:02:24 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 19 Nov 2004 08:03:02 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iAJFwIw0016178;
	Fri, 19 Nov 2004 07:58:18 -0800 (PST)
Received: from [10.32.254.210] ([10.32.254.210])
	by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with SMTP id AZD49916;
	Fri, 19 Nov 2004 08:02:54 -0800 (PST)
In-Reply-To: <BAY2-F4E529CB87AB6ED9E66E42BDC30@phx.gbl>
References: <BAY2-F4E529CB87AB6ED9E66E42BDC30@phx.gbl>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <56E6F546-3A43-11D9-85C1-0003935495EC@cisco.com>
Content-Transfer-Encoding: 7bit
From: "David A. McGrew" <mcgrew@cisco.com>
Subject: Re: [AVT] RFC3711: Srtp Parameters for Rx/Tx ?
Date: Fri, 19 Nov 2004 07:54:47 -0800
To: "milo diurn" <srtpdev@hotmail.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 19 Nov 2004 11:26:08 -0500
Cc: karl.norrman@ericsson.com, elisabetta.carrara@ericsson.com,
        mbaugher@cisco.com, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit

Hi Milo,

On Nov 19, 2004, at 7:10 AM, milo diurn wrote:

> Karl, and Srtp community,
>
> In RFC3711, I do not see any clear way of setting the Srtp parameters 
> (chap 8.2)
> for both ways of the session:
> - Transmit : need the Srtp parameters for Encryption (to be sent to 
> the network)
> - Receive: need the Srtp parameters for Decryption (to be received 
> from the network).

essentially, the parameters are established out-of-band for SRTP.  The 
transmit/receive issue doesn't affect this point; either SRTP endpoint, 
or a third-party device (e.g. a call controller) could set the 
parameters.  In this respect, SRTP is like RTP: it relies on another 
protocol to signal the context information needed to get it going.  
MIKEY and the SDP Security Descriptions are two standards-track ways of 
signaling SRTP.

David

>
> Could you, please, clarify this point ?
>
> Thanks
>
> Regards
>
> _________________________________________________________________
> FREE pop-up blocking with the new MSN Toolbar - get it now! 
> http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
>


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Fri Nov 19 11:37:23 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18857
	for <avt-archive@ietf.org>; Fri, 19 Nov 2004 11:37:23 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVBo6-0000Ja-4C
	for avt-archive@ietf.org; Fri, 19 Nov 2004 11:40:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVBaQ-0007UU-1m; Fri, 19 Nov 2004 11:26:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CVBFU-0001SM-H6
	for avt@megatron.ietf.org; Fri, 19 Nov 2004 11:04:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15512
	for <avt@ietf.org>; Fri, 19 Nov 2004 11:04:34 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVBIK-0007y4-OE
	for avt@ietf.org; Fri, 19 Nov 2004 11:07:34 -0500
Received: from sj-core-3.cisco.com (171.68.223.137)
	by sj-iport-5.cisco.com with ESMTP; 19 Nov 2004 08:04:27 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id iAJG41Yr026082;
	Fri, 19 Nov 2004 08:04:02 -0800 (PST)
Received: from [10.32.254.210] ([10.32.254.210])
	by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with SMTP id AZD50468;
	Fri, 19 Nov 2004 08:09:39 -0800 (PST)
In-Reply-To: <BAY2-F10605E9897A60510000F1CBDC30@phx.gbl>
References: <BAY2-F10605E9897A60510000F1CBDC30@phx.gbl>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <98DD3E1C-3A44-11D9-85C1-0003935495EC@cisco.com>
Content-Transfer-Encoding: 7bit
From: "David A. McGrew" <mcgrew@cisco.com>
Subject: Re: [AVT] RFC3711: Srtp key_id ?
Date: Fri, 19 Nov 2004 08:03:48 -0800
To: "milo diurn" <srtpdev@hotmail.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 19 Nov 2004 11:26:08 -0500
Cc: karl.norrman@ericsson.com, elisabetta.carrara@ericsson.com,
        mbaugher@cisco.com, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit

Milo,

On Nov 19, 2004, at 7:12 AM, milo diurn wrote:

> Karl, and Srtp community,
>
> In RFC3711,
> how is key_id defined and by which part (external/internal) ?

it is defined externally.  From Section 3.1:

    MKI (Master Key Identifier): configurable length, OPTIONAL.  The
               MKI is defined, signaled, and used by key management.


>
> If key_id belongs to the Srtp parameters, why do not referring to it in
> the parameters list (chap 8.2) ?

It is there, but you might have missed it because it is only referred 
to by the acronym "MKI"

Hope this helps!

David

>
> Could you, please, clarify this point ?
>
> Thanks
>
> Regards
>
> _________________________________________________________________
> FREE pop-up blocking with the new MSN Toolbar - get it now! 
> http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
>


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Fri Nov 19 14:04:36 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02442
	for <avt-archive@ietf.org>; Fri, 19 Nov 2004 14:04:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVE6N-0003xK-9V
	for avt-archive@ietf.org; Fri, 19 Nov 2004 14:07:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVDsj-0004sR-1y; Fri, 19 Nov 2004 13:53:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CVDrn-0004Iq-7F
	for avt@megatron.ietf.org; Fri, 19 Nov 2004 13:52:19 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01471
	for <avt@ietf.org>; Fri, 19 Nov 2004 13:52:18 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVDue-0003ee-ON
	for avt@ietf.org; Fri, 19 Nov 2004 13:55:18 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iAJIqGh5004760
	for <avt@ietf.org>; Fri, 19 Nov 2004 19:52:16 +0100 (MET)
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by
	esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 19 Nov 2004 19:52:15 +0100
Received: from ericsson.com (permit151.er.ki.sw.ericsson.se [147.214.97.151])
	by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id WB192K7V; Fri, 19 Nov 2004 19:52:15 +0100
Message-ID: <419E40E0.5040903@ericsson.com>
Date: Fri, 19 Nov 2004 19:52:16 +0100
X-Sybari-Trust: b7154f39 8cefd49f 40fe769a 00000138
From: =?ISO-8859-1?Q?Mats_N=E4slund?= <mats.naslund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "David A. McGrew" <mcgrew@cisco.com>
Subject: Re: [AVT] RFC3711: Srtp salt_key
References: <A0D55704-3A43-11D9-85C1-0003935495EC@cisco.com>
In-Reply-To: <A0D55704-3A43-11D9-85C1-0003935495EC@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Nov 2004 18:52:15.0941 (UTC)
	FILETIME=[E3592F50:01C4CE68]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit
Cc: "Karl Norrman \(KI/EAB\)" <karl.norrman@ericsson.com>,
        milo diurn <srtpdev@hotmail.com>,
        "Elisabetta Carrara \(KI/EAB\)" <elisabetta.carrara@ericsson.com>,
        avt@ietf.org, mbaugher@cisco.com
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit

Hi Milo,

I think you have received answers to all the questions,
I would just to add to David's reply on the salt:

David A. McGrew wrote:

> Milo,
> 
> On Nov 19, 2004, at 7:13 AM, milo diurn wrote:
> 
>  > Karl, and Srtp community,
>  >
>  > In RFC3711, Chap 11.1 shows how the generated keys order is :
>  > SRTP_encr_key, SRTP_auth_key, SRTCP_encr_key, and SRTCP_auth key.
>  >
>  > How about the generated SRTP_salt_key, SRTCP_salt_key ?
>  > Where are they located in the list ?
> 
> the salt is an input to the key derivation process, not an output from
> it.

To be precise, there's both "input salt" and "output salt". Please refer
to Fig 5 of rfc3711:
                          packet index ---+
                                          |
                                          v
                +-----------+ master  +--------+ session encr_key
                | ext       | key     |        |---------->
                | key mgmt  |-------->|  key   | session auth_key
                | (optional |         | deriv  |---------->
                | rekey)    |-------->|        | session salt_key
                |           | master  |        |---------->
                +-----------+ salt    +--------+

    Figure 5: SRTP key derivation.


The master salt (and master key) are among parameters signalled
out-of-band by a key management protocol. From this "session
salts" are derived (see above). I think this pictures nicely shows
how the external key mgmt comes in here ("ext" means "external").

Cheers

/Mats








_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Fri Nov 19 15:45:12 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14099
	for <avt-archive@ietf.org>; Fri, 19 Nov 2004 15:45:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVFfy-0006ro-Hc
	for avt-archive@ietf.org; Fri, 19 Nov 2004 15:48:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVFQ9-0005i4-UJ; Fri, 19 Nov 2004 15:31:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVFCG-00034B-MQ; Fri, 19 Nov 2004 15:17:32 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09398;
	Fri, 19 Nov 2004 15:17:31 -0500 (EST)
Message-Id: <200411192017.PAA09398@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 19 Nov 2004 15:17:31 -0500
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rfc2833bis-06.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2

--NextPart

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

	Title		: RTP Payload for DTMF Digits, Telephony Tones and 
                          Telephony Signals
	Author(s)	: H. Schulzrinne, et al.
	Filename	: draft-ietf-avt-rfc2833bis-06.txt
	Pages		: 49
	Date		: 2004-11-19
	
This memo describes how to carry dual-tone multifrequency (DTMF) 
   signaling, other tone signals and telephony events in RTP packets. 
   This memo captures and expands upon the basic framework defined in 
   RFC 2833, but retains only the most basic event codepoints.  Other 
   codepoints are documented separately.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc2833bis-06.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-avt-rfc2833bis-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-avt-rfc2833bis-06.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2004-11-19153048.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rfc2833bis-06.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-avt-rfc2833bis-06.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2004-11-19153048.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

--NextPart--





From avt-bounces@ietf.org  Sat Nov 20 02:42:48 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28124
	for <avt-archive@ietf.org>; Sat, 20 Nov 2004 02:42:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVPwR-0006kO-9G
	for avt-archive@ietf.org; Sat, 20 Nov 2004 02:45:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVPqy-0000bz-53; Sat, 20 Nov 2004 02:40:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CVPpc-0008Pw-N0
	for avt@megatron.ietf.org; Sat, 20 Nov 2004 02:38:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27787
	for <avt@ietf.org>; Sat, 20 Nov 2004 02:38:47 -0500 (EST)
Received: from mail8.spymac.net ([195.225.149.8] helo=mail8)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVPsY-0006fj-7v
	for avt@ietf.org; Sat, 20 Nov 2004 02:41:54 -0500
Received: from [60.25.112.249] (helo=[60.25.112.249])
	by mail8 with asmtp (Exim 4.34) id 1CVPpT-0003Zd-Dt
	for avt@ietf.org; Sat, 20 Nov 2004 00:38:44 -0700
Message-ID: <419EF46D.3020200@spymac.com>
Date: Sat, 20 Nov 2004 15:38:21 +0800
From: McArthor Lee <linux_fan@spymac.com>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: avt@ietf.org
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit
Subject: [AVT] any implementation of RFC 2733?
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit

hi all,

anybody know that there's any open-source implementation of RFC 2733?

thx in advance

========================
Thank You !!!
McArthor Lee



_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Sun Nov 21 03:24:55 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23274
	for <avt-archive@ietf.org>; Sun, 21 Nov 2004 03:24:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVn4x-000198-0p
	for avt-archive@ietf.org; Sun, 21 Nov 2004 03:28:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVn0E-00012H-9p; Sun, 21 Nov 2004 03:23:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CVmvN-0000SB-FT
	for avt@megatron.ietf.org; Sun, 21 Nov 2004 03:18:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22762
	for <avt@ietf.org>; Sun, 21 Nov 2004 03:18:20 -0500 (EST)
Received: from [212.179.22.140] (helo=imss.audiocodes.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVmyZ-00011Y-1B
	for avt@ietf.org; Sun, 21 Nov 2004 03:21:40 -0500
Received: from aclmsg.corp.audiocodes.com ([10.1.0.8]) by imss with InterScan
	Messaging Security Suite; Sun, 21 Nov 2004 11:24:24 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 21 Nov 2004 10:18:33 +0200
Message-ID: <79B4F738DDD4EF4F85A4641A0FE5EFD6096E37@aclmsg.corp.audiocodes.com>
Thread-Topic: RFC 3711 and High Availability
Thread-Index: AcTPorDB5uXTaiqtTsedyCmHdDa51g==
From: "Yuval Nissan" <YuvalN@audiocodes.com>
To: <avt@ietf.org>
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 0e9ebc0cbd700a87c0637ad0e2c91610
Subject: [AVT] RFC 3711 and High Availability
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1844645890=="
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 1.0 (+)
X-Scan-Signature: 97c820c82c68af374c4e382a80dc5017

This is a multi-part message in MIME format.

--===============1844645890==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4CFA2.B0BE9FFB"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4CFA2.B0BE9FFB
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Hello,

I have question regarding SRTP and High Availability. This issue isn't
covered by RFC 3711:

The question is if channel crashes, what are the parameters that need to
be recovered by the new channel so that the conversation will continue
(in both directions)?

Also in this case it is assumed that we can't know exactly the dynamic
parameters of the channel. For example the current s_l which is updated
every frame. This means that part of the parameters need to be
estimated.

=0D

Thanks,

=0D

Yuval=0D

AudioCodes=0D

=0D

=0D

=0D



***************************************************************************=
*********************************
This email and any files transmitted with it are confidential material.
They are intended solely for the use of the designated individual or entity=
 to whom they are addressed.
If the reader of this message is not the intended recipient,
you are hereby notified that any dissemination,use,
distribution or copying of this communication is strictly prohibited and=
 may be unlawful.

If you have received this email in error please notify=
 postmaster@audiocodes.com and permanently delete the e-mail and files.


***************************************************************************=
********************************
------_=_NextPart_001_01C4CFA2.B0BE9FFB
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>Hello,</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>I have question regarding SRTP and High Availability.=
 This
issue isn&#8217;t covered by RFC 3711:</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>The question is if channel crashes, what are the=
 parameters
that need to be recovered by the new channel so that the conversation will
continue (in both directions)?</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>Also in this case it is assumed that we can&#8217;t know
exactly the dynamic parameters of the channel. For example the current s_l
which is updated every frame. This means that part of the parameters need=
 to be
estimated.</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>Thanks,</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>Yuval </span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>AudioCodes </span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

</div>

</body>

</html>

<table><tr><td bgcolor=3D#ffffff><font color=
=3D#000000>****************************************************************=
********************************************<br>This email and any files=
 transmitted with it are confidential material.<br>They are intended solely=
 for the use of the designated individual or entity to whom they are=
 addressed.<br>If the reader of this message is not the intended=
 recipient,<br>you are hereby notified that any=
 dissemination,use,<br>distribution or copying of this communication is=
 strictly prohibited and may be unlawful.<br><br>If you have received this=
 email in error please notify postmaster@audiocodes.com and permanently=
 delete the e-mail and=
 files.<br><br><br>********************************************************=
***************************************************<br></font></td></tr></t=
able>
------_=_NextPart_001_01C4CFA2.B0BE9FFB--


--===============1844645890==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

--===============1844645890==--



From avt-bounces@ietf.org  Sun Nov 21 16:33:13 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25828
	for <avt-archive@ietf.org>; Sun, 21 Nov 2004 16:33:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVzNx-0003qR-8T
	for avt-archive@ietf.org; Sun, 21 Nov 2004 16:36:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVzIX-0004F0-4z; Sun, 21 Nov 2004 16:31:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CVzEZ-0003UP-Ie
	for avt@megatron.ietf.org; Sun, 21 Nov 2004 16:26:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25470
	for <avt@ietf.org>; Sun, 21 Nov 2004 16:26:57 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVzHs-0003jc-Eu for avt@ietf.org; Sun, 21 Nov 2004 16:30:25 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-3.cisco.com with ESMTP; 21 Nov 2004 14:31:49 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iALLQOPJ004980;
	Sun, 21 Nov 2004 13:26:25 -0800 (PST)
Received: from [192.168.0.10] (sjc-vpn4-753.cisco.com [10.21.82.241])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id iALLQSWn016138;
	Sun, 21 Nov 2004 13:26:29 -0800
In-Reply-To: <79B4F738DDD4EF4F85A4641A0FE5EFD6096E37@aclmsg.corp.audiocodes.com>
References: <79B4F738DDD4EF4F85A4641A0FE5EFD6096E37@aclmsg.corp.audiocodes.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed
Message-Id: <FD48FBCF-3C03-11D9-ADB6-000A95DC10F2@cisco.com>
Content-Transfer-Encoding: quoted-printable
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [AVT] RFC 3711 and High Availability
Date: Sun, 21 Nov 2004 13:26:21 -0800
To: "Yuval Nissan" <YuvalN@audiocodes.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1101072389.289204"; x:"432200"; a:"rsa-sha1"; b:"nofws:2496";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"C1ApRHstgSh0XZIGmj2daqX5btxPYJlPKt9wXvM9OozRyVa1pI1aTfqVUtJsK"
	"vAGYZhoc2eMrb30rPz2BTZA3a0wPZZWQl0oE+ovXWlrIkJ2FhC2T1OQRDLE+r"
	"JBCx3lRvoJYBpvuGwNSkrXcNCah7hKgTL3DWQvYFdtNlaWO7I=";
	c:"From: Mark Baugher <mbaugher@cisco.com>";
	c:"Subject: Re: [AVT] RFC 3711 and High Availability";
	c:"Date: Sun, 21 Nov 2004 13:26:21 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.2 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Content-Transfer-Encoding: quoted-printable
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Content-Transfer-Encoding: quoted-printable

Yuval
   You mention the channel crashing and there seems to be two major =20
cases, either the destination or source addresses change or they don't. =20=

  If they do change, then we effectively have a new session.  Often they =
=20
won't change in an HA system, so I can't immediately recognize any =20
affects on the state of the end-systems.  s_l should be easily =20
recovered and ROC correctly updated unless there are more than 2^15 =20
packets lost.

   In the case where a sender or a receiver fail, then I think it will =20=

be hard to seamlessly handle a transition to another sender and =20
receiver unless the addresses remain the same and most of the =20
cryptographic context is recovered.  Commercial HA systems can do this, =20=

at least in a hot-standby mode, can't they?

Mark
On Nov 21, 2004, at 12:18 AM, Yuval Nissan wrote:

> Hello,
>
> I have question regarding SRTP and High Availability. This issue isn=92t=
 =20
> covered by RFC 3711:
>
> The question is if channel crashes, what are the parameters that need =20=

> to be recovered by the new channel so that the conversation will =20
> continue (in both directions)?
>
> Also in this case it is assumed that we can=92t know exactly the =
dynamic =20
> parameters of the channel. For example the current s_l which is =20
> updated every frame. This means that part of the parameters need to be =
=20
> estimated.
>
> =A0
>
> Thanks,
>
> =A0
>
> Yuval
>
>  AudioCodes
>
>  =A0
>
> =A0
>
> =A0
>
> =
***********************************************************************=20=

> *************************************
> This email and any files transmitted with it are confidential =
material.
> They are intended solely for the use of the designated individual or =20=

> entity to whom they are addressed.
> If the reader of this message is not the intended recipient,
> you are hereby notified that any dissemination,use,
> distribution or copying of this communication is strictly prohibited =20=

> and may be unlawful.
>
> If you have received this email in error please notify =20
> postmaster@audiocodes.com and permanently delete the e-mail and files.
>
>
> =
***********************************************************************=20=

> ************************************
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov 22 03:25:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00818
	for <avt-archive@ietf.org>; Mon, 22 Nov 2004 03:25:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CW9Zg-0007oC-Qx
	for avt-archive@ietf.org; Mon, 22 Nov 2004 03:29:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CW9Q0-0002Px-LM; Mon, 22 Nov 2004 03:19:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CW9P0-0002BM-C7
	for avt@megatron.ietf.org; Mon, 22 Nov 2004 03:18:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00232
	for <avt@ietf.org>; Mon, 22 Nov 2004 03:18:24 -0500 (EST)
Received: from mail2.dslextreme.com ([66.51.199.52])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CW9SE-0007dg-FU
	for avt@ietf.org; Mon, 22 Nov 2004 03:21:57 -0500
Received: (qmail 511 invoked from network); 22 Nov 2004 08:17:40 -0000
Received: from unknown (HELO server.hyervision.com) (66.159.193.111)
	by 192.168.8.48 with (EDH-RSA-DES-CBC3-SHA encrypted) SMTP;
	Mon, 22 Nov 2004 08:17:40 +0000
Received: from peacock (adsl-66-159-193-142.dslextreme.com [66.159.193.142])
	by server.hyervision.com (8.12.11/8.12.11) with ESMTP id iAM8OU8d002633;
	Mon, 22 Nov 2004 00:24:30 -0800 (PST)
From: "Adam Li" <adamli@icsl.ucla.edu>
To: "'McArthor Lee'" <linux_fan@spymac.com>, <avt@ietf.org>
Subject: RE: [AVT] any implementation of RFC 2733?
Date: Mon, 22 Nov 2004 00:17:13 -0800
Message-ID: <00c701c4d06b$ac4752d0$658ea8c0@peacock>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.2180
Importance: Normal
In-Reply-To: <419EF46D.3020200@spymac.com>
X-AntiVirus: scanned for viruses by AMaViS 0.2.1 (http://amavis.org/)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit

Hi McArthor,

There is some pseudo code in the RFC 2733 text itself. As far as I know,
there has not been any open-source implementation. If you have found one, I
would appreciate that you could let me know also.

Adam


-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
McArthor Lee
Sent: Friday, November 19, 2004 11:38 PM
To: avt@ietf.org
Subject: [AVT] any implementation of RFC 2733?

hi all,

anybody know that there's any open-source implementation of RFC 2733?

thx in advance

========================
Thank You !!!
McArthor Lee



_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov 22 03:42:45 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02136
	for <avt-archive@ietf.org>; Mon, 22 Nov 2004 03:42:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CW9pz-0008AQ-5D
	for avt-archive@ietf.org; Mon, 22 Nov 2004 03:46:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CW9l6-0006yt-HW; Mon, 22 Nov 2004 03:41:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CW9ev-00052s-IL
	for avt@megatron.ietf.org; Mon, 22 Nov 2004 03:34:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01477
	for <avt@ietf.org>; Mon, 22 Nov 2004 03:34:52 -0500 (EST)
Received: from [212.179.22.140] (helo=imss.audiocodes.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CW9iK-0007z4-Ip
	for avt@ietf.org; Mon, 22 Nov 2004 03:38:25 -0500
Received: from aclmsg.corp.audiocodes.com ([10.1.0.8]) by imss with InterScan
	Messaging Security Suite; Mon, 22 Nov 2004 11:38:50 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] RFC 3711 and High Availability
Date: Mon, 22 Nov 2004 10:32:56 +0200
Message-ID: <79B4F738DDD4EF4F85A4641A0FE5EFD6096E3C@aclmsg.corp.audiocodes.com>
Thread-Topic: [AVT] RFC 3711 and High Availability
Thread-Index: AcTQEOCyHO3su2mxT8aj4mUdOODvAwAVjlmw
From: "Yuval Nissan" <YuvalN@audiocodes.com>
To: "Mark Baugher" <mbaugher@cisco.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Content-Transfer-Encoding: quoted-printable
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Content-Transfer-Encoding: quoted-printable


Mark,
I meant the second case you describe, with hot-standby mode.

The problem in HA systems of this kind is that you want minimum updates of=
 the dynamic parameters in order not to overload the boards.

Actually, the main issue I see is with s_l and SEQ that are updated every=
 frame. What is the minimum rate that they are needed to be updated and how=
 should they be estimated?

Thanks,
Yuval=0D

-----Original Message-----
From: Mark Baugher [mailto:mbaugher@cisco.com]=0D
Sent: Sunday, November 21, 2004 11:26 PM
To: Yuval Nissan
Cc: avt@ietf.org
Subject: Re: [AVT] RFC 3711 and High Availability

Yuval
   You mention the channel crashing and there seems to be two major =0D
cases, either the destination or source addresses change or they don't. =0D
  If they do change, then we effectively have a new session.  Often they =0D
won't change in an HA system, so I can't immediately recognize any =0D
affects on the state of the end-systems.  s_l should be easily =0D
recovered and ROC correctly updated unless there are more than 2^15 =0D
packets lost.

   In the case where a sender or a receiver fail, then I think it will =0D
be hard to seamlessly handle a transition to another sender and =0D
receiver unless the addresses remain the same and most of the =0D
cryptographic context is recovered.  Commercial HA systems can do this, =0D
at least in a hot-standby mode, can't they?

Mark
On Nov 21, 2004, at 12:18 AM, Yuval Nissan wrote:

> Hello,
>
> I have question regarding SRTP and High Availability. This issue isn=92t =
=0D
> covered by RFC 3711:
>
> The question is if channel crashes, what are the parameters that need =0D
> to be recovered by the new channel so that the conversation will =0D
> continue (in both directions)?
>
> Also in this case it is assumed that we can=92t know exactly the dynamic =
=0D
> parameters of the channel. For example the current s_l which is =0D
> updated every frame. This means that part of the parameters need to be =0D
> estimated.
>
> =A0
>
> Thanks,
>
> =A0
>
> Yuval
>
>  AudioCodes
>
>  =A0
>
> =A0
>
> =A0
>
> ***********************************************************************=0D
> *************************************
> This email and any files transmitted with it are confidential material.
> They are intended solely for the use of the designated individual or =0D
> entity to whom they are addressed.
> If the reader of this message is not the intended recipient,
> you are hereby notified that any dissemination,use,
> distribution or copying of this communication is strictly prohibited =0D
> and may be unlawful.
>
> If you have received this email in error please notify =0D
> postmaster@audiocodes.com and permanently delete the e-mail and files.
>
>
> ***********************************************************************=0D
> ************************************
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt


***************************************************************************=
*********************************
This email and any files transmitted with it are confidential material.
They are intended solely for the use of the designated individual or entity=
 to whom they are addressed.
If the reader of this message is not the intended recipient,
you are hereby notified that any dissemination,use,
distribution or copying of this communication is strictly prohibited and=
 may be unlawful.

If you have received this email in error please notify=
 postmaster@audiocodes.com and permanently delete the e-mail and files.


***************************************************************************=
********************************

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov 22 07:50:49 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25211
	for <avt-archive@ietf.org>; Mon, 22 Nov 2004 07:50:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWDi4-0001aN-Dp
	for avt-archive@ietf.org; Mon, 22 Nov 2004 07:54:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWDbC-0002rR-Al; Mon, 22 Nov 2004 07:47:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWDaY-0002lU-PE
	for avt@megatron.ietf.org; Mon, 22 Nov 2004 07:46:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25013
	for <avt@ietf.org>; Mon, 22 Nov 2004 07:46:37 -0500 (EST)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWDe0-0001L8-DA
	for avt@ietf.org; Mon, 22 Nov 2004 07:50:12 -0500
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (Motorola/Motgate8) with ESMTP id iAMCm6Ni028268
	for <avt@ietf.org>; Mon, 22 Nov 2004 05:48:06 -0700 (MST)
Received: from zin24exm01.ap.mot.com (zin24exm01.ap.mot.com [10.232.25.1])
	by il06exr03.mot.com (Motorola/il06exr03) with ESMTP id iAMCkV1L030753
	for <avt@ietf.org>; Mon, 22 Nov 2004 06:46:32 -0600
Received: by zin24exm01.ap.mot.com with Internet Mail Service (5.5.2657.72)
	id <WYWRWLZN>; Mon, 22 Nov 2004 18:15:45 +0530
Message-ID: <772BCEF88A1DD91191F80011856715F3245B35@zin24exm01.ap.mot.com>
From: Vavilapalli Srikanth-A19563 <srikanthv@motorola.com>
To: "'David A. McGrew'" <mcgrew@cisco.com>, karl.norrman@ericsson.com,
        avt@ietf.org
Date: Mon, 22 Nov 2004 18:15:44 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: milo diurn <srtpdev@hotmail.com>, elisabetta.carrara@ericsson.com,
        mbaugher@cisco.com
Subject: [AVT] RFC3711: SRTP session keys derivation with non-zero key
	derivatio n rate
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db

David, Karl and SRTP Community

RFC: 3711
Section: 4.3.1 (Key Derivation Algorithm)
Scenario: Unicast Bidirectional single stream RTP session

RFC States: that the sender and receiver of a SRTP session derive all the
SRTP/SRTCP session keys from master key using Master key, Master salt,
Packet Index and Key Derivation Rate (KDR).
Mathematically k_e = PRF_n_e (k_master, ((0x00 || (index DIV KDR)) XOR
master_salt)
And also it mentions that the derivation should happen before the first
packet sent or first packet is received. 

Description: In this scenario how can the sender of SRTP packets make sure
that the receiver uses the same packet index to derive the same session keys
at receiver's place that are used at sender side? I mean what if the packet
with packet index (which is used for key derivation at the sender side) is
not reached to the receiver's and the KDR used for this session is non-zero.
Then I guess the sender and receivers will be out of sync in terms of
session keys. Am I right in stating that?

OR

Are the applications using a non-zero value of KDR out of scope of this
document? 

There will not be any issues in this approach if the KDR is zero because
"(index DIV zero)" produces zero every where. Even in the examples, the
session keys are derived with KDR as zero.
 

Could you please clarify this point?


Thanks & Regards
Srikanth Vavilapalli



-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of David
A. McGrew
Sent: Friday, November 19, 2004 9:34 PM
To: milo diurn
Cc: karl.norrman@ericsson.com; elisabetta.carrara@ericsson.com;
mbaugher@cisco.com; avt@ietf.org
Subject: Re: [AVT] RFC3711: Srtp key_id ?

Milo,

On Nov 19, 2004, at 7:12 AM, milo diurn wrote:

> Karl, and Srtp community,
>
> In RFC3711,
> how is key_id defined and by which part (external/internal) ?

it is defined externally.  From Section 3.1:

    MKI (Master Key Identifier): configurable length, OPTIONAL.  The
               MKI is defined, signaled, and used by key management.


>
> If key_id belongs to the Srtp parameters, why do not referring to it in
> the parameters list (chap 8.2) ?

It is there, but you might have missed it because it is only referred 
to by the acronym "MKI"

Hope this helps!

David

>
> Could you, please, clarify this point ?
>
> Thanks
>
> Regards
>
> _________________________________________________________________
> FREE pop-up blocking with the new MSN Toolbar - get it now! 
> http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
>


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov 22 08:12:22 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27157
	for <avt-archive@ietf.org>; Mon, 22 Nov 2004 08:12:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWE2u-0002vI-SS
	for avt-archive@ietf.org; Mon, 22 Nov 2004 08:15:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWDwd-00063u-8O; Mon, 22 Nov 2004 08:09:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWDpa-00057b-R2
	for avt@megatron.ietf.org; Mon, 22 Nov 2004 08:02:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26059
	for <avt@ietf.org>; Mon, 22 Nov 2004 08:02:09 -0500 (EST)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWDt2-0002KH-1g
	for avt@ietf.org; Mon, 22 Nov 2004 08:05:45 -0500
Received: from il06exr06.mot.com (il06exr06.mot.com [129.188.137.136])
	by motgate8.mot.com (Motorola/Motgate8) with ESMTP id iAMD3fNi016424
	for <avt@ietf.org>; Mon, 22 Nov 2004 06:03:41 -0700 (MST)
Received: from zin24exm01.ap.mot.com (zin24exm01.ap.mot.com [10.232.25.1])
	by il06exr06.mot.com (Motorola/il06exr06) with ESMTP id iAMD26hZ006471
	for <avt@ietf.org>; Mon, 22 Nov 2004 07:02:07 -0600
Received: by zin24exm01.ap.mot.com with Internet Mail Service (5.5.2657.72)
	id <WYWRWL97>; Mon, 22 Nov 2004 18:31:20 +0530
Message-ID: <772BCEF88A1DD91191F80011856715F3245B36@zin24exm01.ap.mot.com>
From: Vavilapalli Srikanth-A19563 <srikanthv@motorola.com>
To: "'David A. McGrew'" <mcgrew@cisco.com>, milo diurn <srtpdev@hotmail.com>,
        avt@ietf.org
Date: Mon, 22 Nov 2004 18:31:19 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: karl.norrman@ericsson.com, elisabetta.carrara@ericsson.com,
        mbaugher@cisco.com
Subject: [AVT] SRTP_PREFIX_LENGTH
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248

Hi

Another question from my side:

RFC 3711: Section 4.1: Page 19: SRTP_PREFIX_LENGTH is the octet length of
the key-stream prefix, a non-negative integer, specified by the message
authentication code in use.

RFC 3711: Section 4.1: Page 20: SRTP_PREFIX_LENGTH, the key-stream prefix is
indicated by a positive, non-zero value of SRTP_PREFIX_LENGTH.

It looks like the second bullet is restricting zero value for
SRTP_PREFIX_LENGTH. In that case, how can HMAC-SHA1 use a zero length
key-stream prefix?

	RFC 3711: Section 4.2.1: Page 25: With HMAC-SHA1, the
SRTP_PREFIX_LENGTH SHALL be 0.

Am missing something here? Please clarify this point.

Thanks & Regards
Srikanth Vavilapalli


-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of David
A. McGrew
Sent: Friday, November 19, 2004 9:25 PM
To: milo diurn
Cc: karl.norrman@ericsson.com; elisabetta.carrara@ericsson.com;
mbaugher@cisco.com; avt@ietf.org
Subject: Re: [AVT] RFC3711: Srtp Parameters for Rx/Tx ?

Hi Milo,

On Nov 19, 2004, at 7:10 AM, milo diurn wrote:

> Karl, and Srtp community,
>
> In RFC3711, I do not see any clear way of setting the Srtp parameters 
> (chap 8.2)
> for both ways of the session:
> - Transmit : need the Srtp parameters for Encryption (to be sent to 
> the network)
> - Receive: need the Srtp parameters for Decryption (to be received 
> from the network).

essentially, the parameters are established out-of-band for SRTP.  The 
transmit/receive issue doesn't affect this point; either SRTP endpoint, 
or a third-party device (e.g. a call controller) could set the 
parameters.  In this respect, SRTP is like RTP: it relies on another 
protocol to signal the context information needed to get it going.  
MIKEY and the SDP Security Descriptions are two standards-track ways of 
signaling SRTP.

David

>
> Could you, please, clarify this point ?
>
> Thanks
>
> Regards
>
> _________________________________________________________________
> FREE pop-up blocking with the new MSN Toolbar - get it now! 
> http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
>


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov 22 08:51:47 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29601
	for <avt-archive@ietf.org>; Mon, 22 Nov 2004 08:51:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWEf5-0004o7-LE
	for avt-archive@ietf.org; Mon, 22 Nov 2004 08:55:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWEaH-0002rt-6W; Mon, 22 Nov 2004 08:50:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWEZP-0002hM-3d
	for avt@megatron.ietf.org; Mon, 22 Nov 2004 08:49:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29366
	for <avt@ietf.org>; Mon, 22 Nov 2004 08:49:29 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWEcr-0004el-KC for avt@ietf.org; Mon, 22 Nov 2004 08:53:06 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-3.cisco.com with ESMTP; 22 Nov 2004 06:54:29 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iAMDmsw0005268;
	Mon, 22 Nov 2004 05:48:55 -0800 (PST)
Received: from [10.32.245.156] (stealth-10-32-245-156.cisco.com
	[10.32.245.156])
	by imail.cisco.com (8.12.11/8.12.10) with SMTP id iAMDmwd9019044;
	Mon, 22 Nov 2004 05:48:58 -0800
In-Reply-To: <FD48FBCF-3C03-11D9-ADB6-000A95DC10F2@cisco.com>
References: <79B4F738DDD4EF4F85A4641A0FE5EFD6096E37@aclmsg.corp.audiocodes.com>
	<FD48FBCF-3C03-11D9-ADB6-000A95DC10F2@cisco.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed
Message-Id: <4008C1B9-3C8D-11D9-A48C-000A95C73842@cisco.com>
Content-Transfer-Encoding: quoted-printable
From: David R Oran <oran@cisco.com>
Subject: Re: [AVT] RFC 3711 and High Availability
Date: Mon, 22 Nov 2004 08:48:54 -0500
To: Mark Baugher <mbaugher@cisco.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1101131339.232734"; x:"432200"; a:"rsa-sha1"; b:"nofws:3458";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"o7mXR6LIZOAVRmmN659dWTYdegtlUhHb/Mr+fMw8Y3PJo7pM1+fZnGEJZFhRE"
	"N7jE9HHc+cbKY7Px3Qe5BFeOiRmvLAAzoi0ZSerfEGPGgfoP1E4nfuqBkEuI+"
	"sqZJGtYS2FTgFrtEwGsIMXdnZSBbBKM1Wkob6R7BOUo2iv+B8=";
	c:"From: David R Oran <oran@cisco.com>";
	c:"Subject: Re: [AVT] RFC 3711 and High Availability";
	c:"Date: Mon, 22 Nov 2004 08:48:54 -0500"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Content-Transfer-Encoding: quoted-printable
Cc: Yuval Nissan <YuvalN@audiocodes.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Content-Transfer-Encoding: quoted-printable

Assuming the control plane is still running, the simplest thing to do =20=

is initiate an offer-answer exchange in SDP through SIP or whatever =20
your signaling protocol is. That way you can rebuild all the session =20
state from scratch and avoid corner cases of stale state (e.g. codec =20
payload type maps, keys, addresses, ports, etc.)

In other words - it may be simpler, faster and work better to start a =20=

new RTP session through offer-answer rather than trying to recover the =20=

old one.

Dave.

On Nov 21, 2004, at 4:26 PM, Mark Baugher wrote:

> Yuval
>   You mention the channel crashing and there seems to be two major =20
> cases, either the destination or source addresses change or they =20
> don't.  If they do change, then we effectively have a new session.  =20=

> Often they won't change in an HA system, so I can't immediately =20
> recognize any affects on the state of the end-systems.  s_l should be =20=

> easily recovered and ROC correctly updated unless there are more than =20=

> 2^15 packets lost.
>
>   In the case where a sender or a receiver fail, then I think it will =20=

> be hard to seamlessly handle a transition to another sender and =20
> receiver unless the addresses remain the same and most of the =20
> cryptographic context is recovered.  Commercial HA systems can do =20
> this, at least in a hot-standby mode, can't they?
>
> Mark
> On Nov 21, 2004, at 12:18 AM, Yuval Nissan wrote:
>
>> Hello,
>>
>> I have question regarding SRTP and High Availability. This issue =20
>> isn=92t covered by RFC 3711:
>>
>> The question is if channel crashes, what are the parameters that need =
=20
>> to be recovered by the new channel so that the conversation will =20
>> continue (in both directions)?
>>
>> Also in this case it is assumed that we can=92t know exactly the =20
>> dynamic parameters of the channel. For example the current s_l which =20=

>> is updated every frame. This means that part of the parameters need =20=

>> to be estimated.
>>
>> =A0
>>
>> Thanks,
>>
>> =A0
>>
>> Yuval
>>
>>  AudioCodes
>>
>>  =A0
>>
>> =A0
>>
>> =A0
>>
>> =
**********************************************************************=20=

>> **************************************
>> This email and any files transmitted with it are confidential =20
>> material.
>> They are intended solely for the use of the designated individual or =20=

>> entity to whom they are addressed.
>> If the reader of this message is not the intended recipient,
>> you are hereby notified that any dissemination,use,
>> distribution or copying of this communication is strictly prohibited =20=

>> and may be unlawful.
>>
>> If you have received this email in error please notify =20
>> postmaster@audiocodes.com and permanently delete the e-mail and =20
>> files.
>>
>>
>> =
**********************************************************************=20=

>> *************************************
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www1.ietf.org/mailman/listinfo/avt
>
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>
David R. Oran
Cisco Fellow
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720 USA
Tel: +1 978 264 2048
Email: oran@cisco.com


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov 22 09:06:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00724
	for <avt-archive@ietf.org>; Mon, 22 Nov 2004 09:06:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWEtj-0005Zq-Rx
	for avt-archive@ietf.org; Mon, 22 Nov 2004 09:10:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWEkn-0004Jf-Gm; Mon, 22 Nov 2004 09:01:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWEgS-0003i3-VG
	for avt@megatron.ietf.org; Mon, 22 Nov 2004 08:56:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29962
	for <avt@ietf.org>; Mon, 22 Nov 2004 08:56:47 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWEjl-00055A-5b
	for avt@ietf.org; Mon, 22 Nov 2004 09:00:24 -0500
Received: from esealmw126.eemea.ericsson.se ([153.88.254.123])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iAMDuXh5009197; Mon, 22 Nov 2004 14:56:33 +0100 (MET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 22 Nov 2004 14:56:32 +0100
Received: from esealmw104.eemea.ericsson.se ([153.88.200.67]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 22 Nov 2004 14:56:32 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 22 Nov 2004 14:56:32 +0100
Message-ID: <3AD208E1F0D5EB47AC3C5617420BCB02106239@esealmw104.eemea.ericsson.se>
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Thread-Topic: RFC3711: SRTP session keys derivation with non-zero key
	derivatio n rate
Thread-Index: AcTQkVExOkzRvBzySGiQU0wRVyMUDQACNI/g
From: "Karl Norrman \(KI/EAB\)" <karl.norrman@ericsson.com>
To: "Vavilapalli Srikanth-A19563" <srikanthv@motorola.com>
X-OriginalArrivalTime: 22 Nov 2004 13:56:32.0497 (UTC)
	FILETIME=[12ABBE10:01C4D09B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
Content-Transfer-Encoding: quoted-printable
Cc: milo diurn <srtpdev@hotmail.com>, "David A. McGrew" <mcgrew@cisco.com>,
        "Elisabetta Carrara \(KI/EAB\)" <elisabetta.carrara@ericsson.com>,
        avt@ietf.org, mbaugher@cisco.com
Subject: [AVT] RE: RFC3711: SRTP session keys derivation with non-zero key
	derivatio n rate
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 42e3ed3f10a1d8bef690f09da16f507a
Content-Transfer-Encoding: quoted-printable

Hello!

First, please refer to our previous answer (in another thread)
where we explained that "parameters" in general need to be communicated
out-of-band by key management.

Specifically, in this case, the current ROC is communicated
to the receiver as he joins the session. Alternatively, the
session just starts and the ROC is zero. On consecutive packets,
an "estimation" of the index is done at the receiver (as also
explained in the RFC).=20

To be more specific, the packet index is the
concatenation of the roll-over counter and the sequence number.=20
The roll-over counter can be estimated from the sequence number=20
carried with each SRTP packet using, e.g., the algorithm in appendix A.
Hence, the sender and receiver would be synchronized when the next
packet arrives.

You are absolutely right that there *are* (extreme) cases when
the receiver *can* get out of synch.

Regards,
Karl & Co

> -----Original Message-----
> From: Vavilapalli Srikanth-A19563 [mailto:srikanthv@motorola.com]
> Sent: den 22 november 2004 13:46
> To: David A. McGrew; Karl Norrman (KI/EAB); avt@ietf.org
> Cc: milo diurn; Elisabetta Carrara (KI/EAB); mbaugher@cisco.com
> Subject: RFC3711: SRTP session keys derivation with non-zero key
> derivatio n rate
>=20
>=20
> David, Karl and SRTP Community
>=20
> RFC: 3711
> Section: 4.3.1 (Key Derivation Algorithm)
> Scenario: Unicast Bidirectional single stream RTP session
>=20
> RFC States: that the sender and receiver of a SRTP session=20
> derive all the
> SRTP/SRTCP session keys from master key using Master key, Master salt,
> Packet Index and Key Derivation Rate (KDR).
> Mathematically k_e =3D PRF_n_e (k_master, ((0x00 || (index DIV KDR)) =
XOR
> master_salt)
> And also it mentions that the derivation should happen before=20
> the first
> packet sent or first packet is received.=20
>=20
> Description: In this scenario how can the sender of SRTP=20
> packets make sure
> that the receiver uses the same packet index to derive the=20
> same session keys
> at receiver's place that are used at sender side? I mean what=20
> if the packet
> with packet index (which is used for key derivation at the=20
> sender side) is
> not reached to the receiver's and the KDR used for this=20
> session is non-zero.
> Then I guess the sender and receivers will be out of sync in terms of
> session keys. Am I right in stating that?
>=20
> OR
>=20
> Are the applications using a non-zero value of KDR out of=20
> scope of this
> document?=20
>=20
> There will not be any issues in this approach if the KDR is=20
> zero because
> "(index DIV zero)" produces zero every where. Even in the=20
> examples, the
> session keys are derived with KDR as zero.
> =20
>=20
> Could you please clarify this point?
>=20
>=20
> Thanks & Regards
> Srikanth Vavilapalli
>=20
>=20
>=20
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On=20
> Behalf Of David
> A. McGrew
> Sent: Friday, November 19, 2004 9:34 PM
> To: milo diurn
> Cc: karl.norrman@ericsson.com; elisabetta.carrara@ericsson.com;
> mbaugher@cisco.com; avt@ietf.org
> Subject: Re: [AVT] RFC3711: Srtp key_id ?
>=20
> Milo,
>=20
> On Nov 19, 2004, at 7:12 AM, milo diurn wrote:
>=20
> > Karl, and Srtp community,
> >
> > In RFC3711,
> > how is key_id defined and by which part (external/internal) ?
>=20
> it is defined externally.  From Section 3.1:
>=20
>     MKI (Master Key Identifier): configurable length, OPTIONAL.  The
>                MKI is defined, signaled, and used by key management.
>=20
>=20
> >
> > If key_id belongs to the Srtp parameters, why do not=20
> referring to it in
> > the parameters list (chap 8.2) ?
>=20
> It is there, but you might have missed it because it is only referred=20
> to by the acronym "MKI"
>=20
> Hope this helps!
>=20
> David
>=20
> >
> > Could you, please, clarify this point ?
> >
> > Thanks
> >
> > Regards
> >
> > _________________________________________________________________
> > FREE pop-up blocking with the new MSN Toolbar - get it now!=20
> > http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
> >
>=20
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>=20

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov 22 10:16:32 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06780
	for <avt-archive@ietf.org>; Mon, 22 Nov 2004 10:16:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWFz7-0000pc-2d
	for avt-archive@ietf.org; Mon, 22 Nov 2004 10:20:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWFrL-0004XU-7s; Mon, 22 Nov 2004 10:12:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWFl6-0001eB-7t
	for avt@megatron.ietf.org; Mon, 22 Nov 2004 10:05:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05206
	for <avt@ietf.org>; Mon, 22 Nov 2004 10:05:38 -0500 (EST)
Received: from motgate7.mot.com ([129.188.136.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWFoZ-0000KU-DC
	for avt@ietf.org; Mon, 22 Nov 2004 10:09:15 -0500
Received: from az33exr04.mot.com (pobox4.mot.com [10.64.251.243])
	by motgate7.mot.com (Motorola/Motgate7) with ESMTP id iAMEvMxY026260
	for <avt@ietf.org>; Mon, 22 Nov 2004 07:57:22 -0700 (MST)
Received: from zin24exm01.ap.mot.com (zin24exm01.ap.mot.com [10.232.25.1])
	by az33exr04.mot.com (Motorola/az33exr04) with ESMTP id iAMD4tdj001912
	for <avt@ietf.org>; Mon, 22 Nov 2004 07:04:56 -0600
Received: by zin24exm01.ap.mot.com with Internet Mail Service (5.5.2657.72)
	id <WYWRWNBA>; Mon, 22 Nov 2004 20:34:39 +0530
Message-ID: <772BCEF88A1DD91191F80011856715F3245B38@zin24exm01.ap.mot.com>
From: Vavilapalli Srikanth-A19563 <srikanthv@motorola.com>
To: "'Karl Norrman \\(KI/EAB\\)'" <karl.norrman@ericsson.com>,
        "David A. McGrew" <mcgrew@cisco.com>
Date: Mon, 22 Nov 2004 20:34:39 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93df555cbdbcdae9621e5b95d44b301e
Cc: milo diurn <srtpdev@hotmail.com>,
        "Elisabetta Carrara \\\(KI/EAB\\\)" <elisabetta.carrara@ericsson.com>,
        avt@ietf.org, mbaugher@cisco.com
Subject: [AVT] RE: RFC3711: SRTP session keys derivation with non-zero key
	deriv ation rate
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ec7c6dab5a62df223002ae71b5179d41

Karl

Thanks for your reply. I am still not fully clarified with this answer.

Lets take an example of an RTP session with two participants X and Y. Assume
X & Y have communicated their ROC of zero using some out-of-band signaling.
I don't think you are suggesting us to exchange the initial sequence numbers
of this session also here, are you? (Though RFC states that "Sending the RTP
sequence number in the key management MAY be useful e.g., when the initial
sequence number is close to wrapping (to avoid synchronization problems),
and to communicate the current sequence number to a joining endpoint (to
properly initialize its replay list).")

Assumption1: Initial sequence number is not communicated using key mgmt
protocol. Only ROC is exchanged.

"X" started the RTP TX traffic with initial sequence number say 150 and ROC
obviously zero. So PACKET_INDEX at Tx side is = ROC || SEQ = 150. Using this
index value including with some other parameters, "X" derives his session
keys (k_e, k_a, k_s) using AEC-CM PRF function. This key derivation happens
once at the initial time before transmitting first packet and after that
whenever (index mod KDR) equals zero. Now "X" encrypts the first packet
using k_e and transmits to "Y". Similarly "X" transmits packet index 151
after encrypting it with the same session key k_e derived earlier.
Tx Packet traffic = 150, 151, 152...

Assumption2: The packet with index 150 is lost in the transit.

"Y" receives his first packet and estimates the value "v" from set {ROC-1,
ROC, ROC+1} and calculates the PACKET_INDEX = v || SEQ = 151. As this is the
first packet, "Y" derives his session keys using packet index 151 and some
other params and gets a different set of session keys (k_e1, k_a1, k_s1),
which he uses to decrypt the packet. However this packet was encrypted with
a key-stream which was generated using the session key (k_e) at "X". Hence
decryption fails for all the consecutive packets. How to tackle this
scenario or synchronization issue?

Hope my question is clear.

Regards
Srikanth  


-----Original Message-----
From: Karl Norrman \(KI/EAB\) [mailto:karl.norrman@ericsson.com] 
Sent: Monday, November 22, 2004 7:27 PM
To: Vavilapalli Srikanth-A19563
Cc: milo diurn; Elisabetta Carrara \(KI/EAB\); mbaugher@cisco.com; David A.
McGrew; avt@ietf.org
Subject: RE: RFC3711: SRTP session keys derivation with non-zero key
derivatio n rate

Hello!

First, please refer to our previous answer (in another thread)
where we explained that "parameters" in general need to be communicated
out-of-band by key management.

Specifically, in this case, the current ROC is communicated
to the receiver as he joins the session. Alternatively, the
session just starts and the ROC is zero. On consecutive packets,
an "estimation" of the index is done at the receiver (as also
explained in the RFC). 

To be more specific, the packet index is the
concatenation of the roll-over counter and the sequence number. 
The roll-over counter can be estimated from the sequence number 
carried with each SRTP packet using, e.g., the algorithm in appendix A.
Hence, the sender and receiver would be synchronized when the next
packet arrives.

You are absolutely right that there *are* (extreme) cases when
the receiver *can* get out of synch.

Regards,
Karl & Co

> -----Original Message-----
> From: Vavilapalli Srikanth-A19563 [mailto:srikanthv@motorola.com]
> Sent: den 22 november 2004 13:46
> To: David A. McGrew; Karl Norrman (KI/EAB); avt@ietf.org
> Cc: milo diurn; Elisabetta Carrara (KI/EAB); mbaugher@cisco.com
> Subject: RFC3711: SRTP session keys derivation with non-zero key
> derivatio n rate
> 
> 
> David, Karl and SRTP Community
> 
> RFC: 3711
> Section: 4.3.1 (Key Derivation Algorithm)
> Scenario: Unicast Bidirectional single stream RTP session
> 
> RFC States: that the sender and receiver of a SRTP session 
> derive all the
> SRTP/SRTCP session keys from master key using Master key, Master salt,
> Packet Index and Key Derivation Rate (KDR).
> Mathematically k_e = PRF_n_e (k_master, ((0x00 || (index DIV KDR)) XOR
> master_salt)
> And also it mentions that the derivation should happen before 
> the first
> packet sent or first packet is received. 
> 
> Description: In this scenario how can the sender of SRTP 
> packets make sure
> that the receiver uses the same packet index to derive the 
> same session keys
> at receiver's place that are used at sender side? I mean what 
> if the packet
> with packet index (which is used for key derivation at the 
> sender side) is
> not reached to the receiver's and the KDR used for this 
> session is non-zero.
> Then I guess the sender and receivers will be out of sync in terms of
> session keys. Am I right in stating that?
> 
> OR
> 
> Are the applications using a non-zero value of KDR out of 
> scope of this
> document? 
> 
> There will not be any issues in this approach if the KDR is 
> zero because
> "(index DIV zero)" produces zero every where. Even in the 
> examples, the
> session keys are derived with KDR as zero.
>  
> 
> Could you please clarify this point?
> 
> 
> Thanks & Regards
> Srikanth Vavilapalli
> 
> 
> 
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On 
> Behalf Of David
> A. McGrew
> Sent: Friday, November 19, 2004 9:34 PM
> To: milo diurn
> Cc: karl.norrman@ericsson.com; elisabetta.carrara@ericsson.com;
> mbaugher@cisco.com; avt@ietf.org
> Subject: Re: [AVT] RFC3711: Srtp key_id ?
> 
> Milo,
> 
> On Nov 19, 2004, at 7:12 AM, milo diurn wrote:
> 
> > Karl, and Srtp community,
> >
> > In RFC3711,
> > how is key_id defined and by which part (external/internal) ?
> 
> it is defined externally.  From Section 3.1:
> 
>     MKI (Master Key Identifier): configurable length, OPTIONAL.  The
>                MKI is defined, signaled, and used by key management.
> 
> 
> >
> > If key_id belongs to the Srtp parameters, why do not 
> referring to it in
> > the parameters list (chap 8.2) ?
> 
> It is there, but you might have missed it because it is only referred 
> to by the acronym "MKI"
> 
> Hope this helps!
> 
> David
> 
> >
> > Could you, please, clarify this point ?
> >
> > Thanks
> >
> > Regards
> >
> > _________________________________________________________________
> > FREE pop-up blocking with the new MSN Toolbar - get it now! 
> > http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
> >
> 
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
> 

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov 22 11:41:22 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15410
	for <avt-archive@ietf.org>; Mon, 22 Nov 2004 11:41:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWHJF-0005Yc-7X
	for avt-archive@ietf.org; Mon, 22 Nov 2004 11:45:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWHAm-0006FA-Jt; Mon, 22 Nov 2004 11:36:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWH7c-0005FO-8j
	for avt@megatron.ietf.org; Mon, 22 Nov 2004 11:33:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14655
	for <avt@ietf.org>; Mon, 22 Nov 2004 11:32:57 -0500 (EST)
Received: from [212.179.22.140] (helo=imss.audiocodes.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWHB5-00054S-Iw
	for avt@ietf.org; Mon, 22 Nov 2004 11:36:36 -0500
Received: from aclmsg.corp.audiocodes.com ([10.1.0.8]) by imss with InterScan
	Messaging Security Suite; Mon, 22 Nov 2004 19:38:03 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] RFC 3711 and High Availability
Date: Mon, 22 Nov 2004 18:32:08 +0200
Message-ID: <79B4F738DDD4EF4F85A4641A0FE5EFD6096E47@aclmsg.corp.audiocodes.com>
Thread-Topic: [AVT] RFC 3711 and High Availability
Thread-Index: AcTQmiNCtMbgGICVT2SprBsc8K//xwAFqSOw
From: "Yuval Nissan" <YuvalN@audiocodes.com>
To: "David R Oran" <oran@cisco.com>, "Mark Baugher" <mbaugher@cisco.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Content-Transfer-Encoding: quoted-printable
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
Content-Transfer-Encoding: quoted-printable


David,
Assuming you need to do this process on many channels at once (when for=
 example one board crashes with hundreds of channels), I don't think this=
 solution is feasible. What do you think?

Thanks
Yuval

-----Original Message-----
From: David R Oran [mailto:oran@cisco.com]=0D
Sent: Monday, November 22, 2004 3:49 PM
To: Mark Baugher
Cc: avt@ietf.org; Yuval Nissan
Subject: Re: [AVT] RFC 3711 and High Availability

Assuming the control plane is still running, the simplest thing to do =0D
is initiate an offer-answer exchange in SDP through SIP or whatever =0D
your signaling protocol is. That way you can rebuild all the session =0D
state from scratch and avoid corner cases of stale state (e.g. codec =0D
payload type maps, keys, addresses, ports, etc.)

In other words - it may be simpler, faster and work better to start a =0D
new RTP session through offer-answer rather than trying to recover the =0D
old one.

Dave.

On Nov 21, 2004, at 4:26 PM, Mark Baugher wrote:

> Yuval
>   You mention the channel crashing and there seems to be two major =0D
> cases, either the destination or source addresses change or they =0D
> don't.  If they do change, then we effectively have a new session.  =0D
> Often they won't change in an HA system, so I can't immediately =0D
> recognize any affects on the state of the end-systems.  s_l should be =0D
> easily recovered and ROC correctly updated unless there are more than =0D
> 2^15 packets lost.
>
>   In the case where a sender or a receiver fail, then I think it will =0D
> be hard to seamlessly handle a transition to another sender and =0D
> receiver unless the addresses remain the same and most of the =0D
> cryptographic context is recovered.  Commercial HA systems can do =0D
> this, at least in a hot-standby mode, can't they?
>
> Mark
> On Nov 21, 2004, at 12:18 AM, Yuval Nissan wrote:
>
>> Hello,
>>
>> I have question regarding SRTP and High Availability. This issue =0D
>> isn=92t covered by RFC 3711:
>>
>> The question is if channel crashes, what are the parameters that need =0D
>> to be recovered by the new channel so that the conversation will =0D
>> continue (in both directions)?
>>
>> Also in this case it is assumed that we can=92t know exactly the =0D
>> dynamic parameters of the channel. For example the current s_l which =0D
>> is updated every frame. This means that part of the parameters need =0D
>> to be estimated.
>>
>> =A0
>>
>> Thanks,
>>
>> =A0
>>
>> Yuval
>>
>>  AudioCodes
>>
>>  =A0
>>
>> =A0
>>
>> =A0
>>
>> **********************************************************************=0D
>> **************************************
>> This email and any files transmitted with it are confidential =0D
>> material.
>> They are intended solely for the use of the designated individual or =0D
>> entity to whom they are addressed.
>> If the reader of this message is not the intended recipient,
>> you are hereby notified that any dissemination,use,
>> distribution or copying of this communication is strictly prohibited =0D
>> and may be unlawful.
>>
>> If you have received this email in error please notify =0D
>> postmaster@audiocodes.com and permanently delete the e-mail and =0D
>> files.
>>
>>
>> **********************************************************************=0D
>> *************************************
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www1.ietf.org/mailman/listinfo/avt
>
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>
David R. Oran
Cisco Fellow
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720 USA
Tel: +1 978 264 2048
Email: oran@cisco.com


***************************************************************************=
*********************************
This email and any files transmitted with it are confidential material.
They are intended solely for the use of the designated individual or entity=
 to whom they are addressed.
If the reader of this message is not the intended recipient,
you are hereby notified that any dissemination,use,
distribution or copying of this communication is strictly prohibited and=
 may be unlawful.

If you have received this email in error please notify=
 postmaster@audiocodes.com and permanently delete the e-mail and files.


***************************************************************************=
********************************

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov 22 13:59:01 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02533
	for <avt-archive@ietf.org>; Mon, 22 Nov 2004 13:59:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWJSR-0004Ce-76
	for avt-archive@ietf.org; Mon, 22 Nov 2004 14:02:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWJK9-0006ZK-Lr; Mon, 22 Nov 2004 13:54:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWJDe-0005IL-1p
	for avt@megatron.ietf.org; Mon, 22 Nov 2004 13:47:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01748
	for <avt@ietf.org>; Mon, 22 Nov 2004 13:47:21 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWJH9-0002Pc-5k for avt@ietf.org; Mon, 22 Nov 2004 13:50:59 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-3.cisco.com with ESMTP; 22 Nov 2004 11:52:23 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iAMIkjPJ010826;
	Mon, 22 Nov 2004 10:46:46 -0800 (PST)
Received: from [192.168.0.10] (sjc-vpn1-211.cisco.com [10.21.96.211])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id iAMIkkZv021113;
	Mon, 22 Nov 2004 10:46:46 -0800
In-Reply-To: <79B4F738DDD4EF4F85A4641A0FE5EFD6096E3C@aclmsg.corp.audiocodes.com>
References: <79B4F738DDD4EF4F85A4641A0FE5EFD6096E3C@aclmsg.corp.audiocodes.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed
Message-Id: <DA498F90-3CB6-11D9-9BBF-000A95DC10F2@cisco.com>
Content-Transfer-Encoding: quoted-printable
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [AVT] RFC 3711 and High Availability
Date: Mon, 22 Nov 2004 10:46:42 -0800
To: "Yuval Nissan" <YuvalN@audiocodes.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1101149206.879609"; x:"432200"; a:"rsa-sha1"; b:"nofws:6125";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"enEVPckGp1iUgQSI6tGYzbDXQrfq7W8Z/ew9reMQr5pWS8bbeBS+SLpZDd9yh"
	"zln8r8p0tWrkraOZ2mEBKquIJ15UhfIkvGyQJH/LeadkTlcKD14QpuW4vq6kp"
	"0KUxvwrxdZili0xpSZK1P76hl11FIb/0snqIppQ+Ja7jaErak=";
	c:"From: Mark Baugher <mbaugher@cisco.com>";
	c:"Subject: Re: [AVT] RFC 3711 and High Availability";
	c:"Date: Mon, 22 Nov 2004 10:46:42 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 4b7d60495f1a7f2e853e8cbae7e6dbfc
Content-Transfer-Encoding: quoted-printable
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: bf422c85703d3d847fb014987125ac48
Content-Transfer-Encoding: quoted-printable

Yuval,

On Nov 22, 2004, at 12:32 AM, Yuval Nissan wrote:

>
> Mark,
> I meant the second case you describe, with hot-standby mode.
>
> The problem in HA systems of this kind is that you want minimum =20
> updates of the dynamic parameters in order not to overload the boards.
>
> Actually, the main issue I see is with s_l and SEQ that are updated =20=

> every frame. What is the minimum rate that they are needed to be =20
> updated and how should they be estimated?

s_l (at the receiver), SEQ (at the sender) and potentially the ROC need =20=

to be updated on every packet to be strictly correct, and I can see why =20=

this would be impractical in hot-standby mode.  There are a few =20
tradeoffs.  If you want a nearly-seamless transition to the standby =20
machine, then s_l needs to consistent between receiving machines and =20
SEQ between sending machines.  If this is not practical and the HA =20
application requirements permit a round-trip signaling message during =20=

recovery, then Dave Oran's suggestion seems to be a straightforward and =20=

reliable solution.  I'd opt for this.

Alternatively, consider Appendix A:  Appendix A handles the case where =20=

the sequence-number wraps to zero, and I think the ROC update will be =20=

correct so long as s_l stays within 2^15 packets of SEQ.  The replay =20
window is a tighter bound.  Thinking out loud, it might be possible to =20=

update SEQ and s_l infrequently if you take account of the size of =20
replay window.  Lazy update at the sender will cause problems at the =20
receiver until the sender's SEQ reaches the receiver's s_l.  All of the =20=

senders packets with a SEQ less than s_l minus the replay-window-size =20=

(modulo 2^16) will get discarded.  The sender's packets that are within =20=

that window will get discarded if they match previously-received =20
packets or else they would be incorrectly accepted.  So it might be =20
possible to update SEQ on the hot-standby machine in increments of the =20=

replay window size.  When failover occurs, the last recorded SEQ would =20=

be incremented by the replay-window size and the hot-standby sender =20
could resume sending packets with the new SEQ, and the receiver would =20=

update it's s_l to the new, higher-value SEQ.  This might work, but I'm =20=

not entirely sure.

Mark
>
> Thanks,
> Yuval
>
> -----Original Message-----
> From: Mark Baugher [mailto:mbaugher@cisco.com]
> Sent: Sunday, November 21, 2004 11:26 PM
> To: Yuval Nissan
> Cc: avt@ietf.org
> Subject: Re: [AVT] RFC 3711 and High Availability
>
> Yuval
>    You mention the channel crashing and there seems to be two major
> cases, either the destination or source addresses change or they =
don't.
>   If they do change, then we effectively have a new session.  Often =20=

> they
> won't change in an HA system, so I can't immediately recognize any
> affects on the state of the end-systems.  s_l should be easily
> recovered and ROC correctly updated unless there are more than 2^15
> packets lost.
>
>    In the case where a sender or a receiver fail, then I think it will
> be hard to seamlessly handle a transition to another sender and
> receiver unless the addresses remain the same and most of the
> cryptographic context is recovered.  Commercial HA systems can do =
this,
> at least in a hot-standby mode, can't they?
>
> Mark
> On Nov 21, 2004, at 12:18 AM, Yuval Nissan wrote:
>
>> Hello,
>>
>> I have question regarding SRTP and High Availability. This issue =
isn=92t
>> covered by RFC 3711:
>>
>> The question is if channel crashes, what are the parameters that need
>> to be recovered by the new channel so that the conversation will
>> continue (in both directions)?
>>
>> Also in this case it is assumed that we can=92t know exactly the =
dynamic
>> parameters of the channel. For example the current s_l which is
>> updated every frame. This means that part of the parameters need to =
be
>> estimated.
>>
>> =A0
>>
>> Thanks,
>>
>> =A0
>>
>> Yuval
>>
>>  AudioCodes
>>
>>  =A0
>>
>> =A0
>>
>> =A0
>>
>> =
**********************************************************************=20=

>> *
>> *************************************
>> This email and any files transmitted with it are confidential =20
>> material.
>> They are intended solely for the use of the designated individual or
>> entity to whom they are addressed.
>> If the reader of this message is not the intended recipient,
>> you are hereby notified that any dissemination,use,
>> distribution or copying of this communication is strictly prohibited
>> and may be unlawful.
>>
>> If you have received this email in error please notify
>> postmaster@audiocodes.com and permanently delete the e-mail and =
files.
>>
>>
>> =
**********************************************************************=20=

>> *
>> ************************************
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www1.ietf.org/mailman/listinfo/avt
>
>
> =
***********************************************************************=20=

> *************************************
> This email and any files transmitted with it are confidential =
material.
> They are intended solely for the use of the designated individual or =20=

> entity to whom they are addressed.
> If the reader of this message is not the intended recipient,
> you are hereby notified that any dissemination,use,
> distribution or copying of this communication is strictly prohibited =20=

> and may be unlawful.
>
> If you have received this email in error please notify =20
> postmaster@audiocodes.com and permanently delete the e-mail and files.
>
>
> =
***********************************************************************=20=

> ************************************
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov 22 14:07:01 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03506
	for <avt-archive@ietf.org>; Mon, 22 Nov 2004 14:07:01 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWJaC-00058S-1J
	for avt-archive@ietf.org; Mon, 22 Nov 2004 14:10:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWJMB-0006ru-JP; Mon, 22 Nov 2004 13:56:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWJHu-00069P-DS
	for avt@megatron.ietf.org; Mon, 22 Nov 2004 13:51:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02022
	for <avt@ietf.org>; Mon, 22 Nov 2004 13:51:45 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWJLP-000327-H0 for avt@ietf.org; Mon, 22 Nov 2004 13:55:24 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 22 Nov 2004 10:54:17 -0800
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iAMIp6AC029927;
	Mon, 22 Nov 2004 10:51:08 -0800 (PST)
Received: from [10.32.245.156] (stealth-10-32-245-156.cisco.com
	[10.32.245.156])
	by imail.cisco.com (8.12.11/8.12.10) with SMTP id iAMIp74Z021148;
	Mon, 22 Nov 2004 10:51:08 -0800
In-Reply-To: <79B4F738DDD4EF4F85A4641A0FE5EFD6096E47@aclmsg.corp.audiocodes.com>
References: <79B4F738DDD4EF4F85A4641A0FE5EFD6096E47@aclmsg.corp.audiocodes.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed
Message-Id: <7650D648-3CB7-11D9-A48C-000A95C73842@cisco.com>
Content-Transfer-Encoding: quoted-printable
From: David R Oran <oran@cisco.com>
Subject: Re: [AVT] RFC 3711 and High Availability
Date: Mon, 22 Nov 2004 13:51:04 -0500
To: "Yuval Nissan" <YuvalN@audiocodes.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1101149469.729695"; x:"432200"; a:"rsa-sha1"; b:"nofws:5623";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"nRcX4yKxw8F9jCkSkE5VtYRpqSFGqL7NsVhGj7S6r2VI++rwWGH3U+3APnwDg"
	"LZYEfCEcwpJNpFMAFBUzg35Z1FZ9dCsN5dsp6o3wfp5rcmIhopD2B8nD6hFY7"
	"dxfvu8wp786zLj+Xuc9tt9nCXGiW0igKpKnhM0RcTvMWbwnxQ=";
	c:"From: David R Oran <oran@cisco.com>";
	c:"Subject: Re: [AVT] RFC 3711 and High Availability";
	c:"Date: Mon, 22 Nov 2004 13:51:04 -0500"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.2 (/)
X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176
Content-Transfer-Encoding: quoted-printable
Cc: avt@ietf.org, Mark Baugher <mbaugher@cisco.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 33cc095b503da4365ce57c727e553cf1
Content-Transfer-Encoding: quoted-printable

Any solution that doesn't shadow all state will require at least one =20
round trip per session. Offer-answer rebuilds the RTP state in one =20
round trip. Note that to do true hot failover without a round trip, you =20=

would have to shadow all RTP state, including ports, addresses, ROC, =20
and possibly sequence numbers as well. One way to do this is to send a =20=

copy of each packet to both machines. There are a number of ways to do =20=

this, all expensive. OTOH, that's what 1:1 redundancy is inherently: =20
expensive.

Dave.

On Nov 22, 2004, at 11:32 AM, Yuval Nissan wrote:

>
> David,
> Assuming you need to do this process on many channels at once (when =20=

> for example one board crashes with hundreds of channels), I don't =20
> think this solution is feasible. What do you think?
>
> Thanks
> Yuval
>
> -----Original Message-----
> From: David R Oran [mailto:oran@cisco.com]
> Sent: Monday, November 22, 2004 3:49 PM
> To: Mark Baugher
> Cc: avt@ietf.org; Yuval Nissan
> Subject: Re: [AVT] RFC 3711 and High Availability
>
> Assuming the control plane is still running, the simplest thing to do
> is initiate an offer-answer exchange in SDP through SIP or whatever
> your signaling protocol is. That way you can rebuild all the session
> state from scratch and avoid corner cases of stale state (e.g. codec
> payload type maps, keys, addresses, ports, etc.)
>
> In other words - it may be simpler, faster and work better to start a
> new RTP session through offer-answer rather than trying to recover the
> old one.
>
> Dave.
>
> On Nov 21, 2004, at 4:26 PM, Mark Baugher wrote:
>
>> Yuval
>>   You mention the channel crashing and there seems to be two major
>> cases, either the destination or source addresses change or they
>> don't.  If they do change, then we effectively have a new session.
>> Often they won't change in an HA system, so I can't immediately
>> recognize any affects on the state of the end-systems.  s_l should be
>> easily recovered and ROC correctly updated unless there are more than
>> 2^15 packets lost.
>>
>>   In the case where a sender or a receiver fail, then I think it will
>> be hard to seamlessly handle a transition to another sender and
>> receiver unless the addresses remain the same and most of the
>> cryptographic context is recovered.  Commercial HA systems can do
>> this, at least in a hot-standby mode, can't they?
>>
>> Mark
>> On Nov 21, 2004, at 12:18 AM, Yuval Nissan wrote:
>>
>>> Hello,
>>>
>>> I have question regarding SRTP and High Availability. This issue
>>> isn=92t covered by RFC 3711:
>>>
>>> The question is if channel crashes, what are the parameters that =
need
>>> to be recovered by the new channel so that the conversation will
>>> continue (in both directions)?
>>>
>>> Also in this case it is assumed that we can=92t know exactly the
>>> dynamic parameters of the channel. For example the current s_l which
>>> is updated every frame. This means that part of the parameters need
>>> to be estimated.
>>>
>>> =A0
>>>
>>> Thanks,
>>>
>>> =A0
>>>
>>> Yuval
>>>
>>>  AudioCodes
>>>
>>>  =A0
>>>
>>> =A0
>>>
>>> =A0
>>>
>>> =
*********************************************************************=20
>>> *
>>> **************************************
>>> This email and any files transmitted with it are confidential
>>> material.
>>> They are intended solely for the use of the designated individual or
>>> entity to whom they are addressed.
>>> If the reader of this message is not the intended recipient,
>>> you are hereby notified that any dissemination,use,
>>> distribution or copying of this communication is strictly prohibited
>>> and may be unlawful.
>>>
>>> If you have received this email in error please notify
>>> postmaster@audiocodes.com and permanently delete the e-mail and
>>> files.
>>>
>>>
>>> =
*********************************************************************=20
>>> *
>>> *************************************
>>> _______________________________________________
>>> Audio/Video Transport Working Group
>>> avt@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/avt
>>
>>
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www1.ietf.org/mailman/listinfo/avt
>>
> David R. Oran
> Cisco Fellow
> Cisco Systems
> 7 Ladyslipper Lane
> Acton, MA 01720 USA
> Tel: +1 978 264 2048
> Email: oran@cisco.com
>
>
> =
***********************************************************************=20=

> *************************************
> This email and any files transmitted with it are confidential =
material.
> They are intended solely for the use of the designated individual or =20=

> entity to whom they are addressed.
> If the reader of this message is not the intended recipient,
> you are hereby notified that any dissemination,use,
> distribution or copying of this communication is strictly prohibited =20=

> and may be unlawful.
>
> If you have received this email in error please notify =20
> postmaster@audiocodes.com and permanently delete the e-mail and files.
>
>
> =
***********************************************************************=20=

> ************************************
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>
David R. Oran
Cisco Fellow
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720 USA
Tel: +1 978 264 2048
Email: oran@cisco.com


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Tue Nov 23 03:30:42 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14441
	for <avt-archive@ietf.org>; Tue, 23 Nov 2004 03:30:42 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWW85-0002ui-0W
	for avt-archive@ietf.org; Tue, 23 Nov 2004 03:34:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWVyB-00055G-3p; Tue, 23 Nov 2004 03:24:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWVvR-0004Ds-HZ
	for avt@megatron.ietf.org; Tue, 23 Nov 2004 03:21:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13365
	for <avt@ietf.org>; Tue, 23 Nov 2004 03:21:23 -0500 (EST)
Received: from [212.179.22.140] (helo=imss.audiocodes.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWVz3-0001hd-44
	for avt@ietf.org; Tue, 23 Nov 2004 03:25:10 -0500
Received: from aclmsg.corp.audiocodes.com ([10.1.0.8]) by imss with InterScan
	Messaging Security Suite; Tue, 23 Nov 2004 11:27:31 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] RFC 3711 and High Availability
Date: Tue, 23 Nov 2004 10:21:34 +0200
Message-ID: <79B4F738DDD4EF4F85A4641A0FE5EFD6096E4A@aclmsg.corp.audiocodes.com>
Thread-Topic: [AVT] RFC 3711 and High Availability
Thread-Index: AcTQw76mp6GQn1iXRbmLjranB+oWCAAbsSHA
From: "Yuval Nissan" <YuvalN@audiocodes.com>
To: "Mark Baugher" <mbaugher@cisco.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: a92270ba83d7ead10c5001bb42ec3221
Content-Transfer-Encoding: quoted-printable
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 31b28e25e9d13a22020d8b7aedc9832c
Content-Transfer-Encoding: quoted-printable


Mark,
Consider the second solution you propose (the lazy update), there is=
 possibility to make the update much less frequent (but still must be less=
 than every 2^15 packets), and to estimate Transmit SEQ as following:
TransmitSEQ =3D=
 lastUpdateTransmitSEQ+TimeFromLastUpdate/PacketFrameSize+Delta=0D
(and also update the transmit ROC if needed).

I think this also should work if appendix A is implemented.

Yuval=0D

-----Original Message-----
From: Mark Baugher [mailto:mbaugher@cisco.com]=0D
Sent: Monday, November 22, 2004 8:47 PM
To: Yuval Nissan
Cc: avt@ietf.org
Subject: Re: [AVT] RFC 3711 and High Availability

Yuval,

On Nov 22, 2004, at 12:32 AM, Yuval Nissan wrote:

>
> Mark,
> I meant the second case you describe, with hot-standby mode.
>
> The problem in HA systems of this kind is that you want minimum =0D
> updates of the dynamic parameters in order not to overload the boards.
>
> Actually, the main issue I see is with s_l and SEQ that are updated =0D
> every frame. What is the minimum rate that they are needed to be =0D
> updated and how should they be estimated?

s_l (at the receiver), SEQ (at the sender) and potentially the ROC need =0D
to be updated on every packet to be strictly correct, and I can see why =0D
this would be impractical in hot-standby mode.  There are a few =0D
tradeoffs.  If you want a nearly-seamless transition to the standby =0D
machine, then s_l needs to consistent between receiving machines and =0D
SEQ between sending machines.  If this is not practical and the HA =0D
application requirements permit a round-trip signaling message during =0D
recovery, then Dave Oran's suggestion seems to be a straightforward and =0D
reliable solution.  I'd opt for this.

Alternatively, consider Appendix A:  Appendix A handles the case where =0D
the sequence-number wraps to zero, and I think the ROC update will be =0D
correct so long as s_l stays within 2^15 packets of SEQ.  The replay =0D
window is a tighter bound.  Thinking out loud, it might be possible to =0D
update SEQ and s_l infrequently if you take account of the size of =0D
replay window.  Lazy update at the sender will cause problems at the =0D
receiver until the sender's SEQ reaches the receiver's s_l.  All of the =0D
senders packets with a SEQ less than s_l minus the replay-window-size =0D
(modulo 2^16) will get discarded.  The sender's packets that are within =0D
that window will get discarded if they match previously-received =0D
packets or else they would be incorrectly accepted.  So it might be =0D
possible to update SEQ on the hot-standby machine in increments of the =0D
replay window size.  When failover occurs, the last recorded SEQ would =0D
be incremented by the replay-window size and the hot-standby sender =0D
could resume sending packets with the new SEQ, and the receiver would =0D
update it's s_l to the new, higher-value SEQ.  This might work, but I'm =0D
not entirely sure.

Mark
>
> Thanks,
> Yuval
>
> -----Original Message-----
> From: Mark Baugher [mailto:mbaugher@cisco.com]
> Sent: Sunday, November 21, 2004 11:26 PM
> To: Yuval Nissan
> Cc: avt@ietf.org
> Subject: Re: [AVT] RFC 3711 and High Availability
>
> Yuval
>    You mention the channel crashing and there seems to be two major
> cases, either the destination or source addresses change or they don't.
>   If they do change, then we effectively have a new session.  Often =0D
> they
> won't change in an HA system, so I can't immediately recognize any
> affects on the state of the end-systems.  s_l should be easily
> recovered and ROC correctly updated unless there are more than 2^15
> packets lost.
>
>    In the case where a sender or a receiver fail, then I think it will
> be hard to seamlessly handle a transition to another sender and
> receiver unless the addresses remain the same and most of the
> cryptographic context is recovered.  Commercial HA systems can do this,
> at least in a hot-standby mode, can't they?
>
> Mark
> On Nov 21, 2004, at 12:18 AM, Yuval Nissan wrote:
>
>> Hello,
>>
>> I have question regarding SRTP and High Availability. This issue isn=92t
>> covered by RFC 3711:
>>
>> The question is if channel crashes, what are the parameters that need
>> to be recovered by the new channel so that the conversation will
>> continue (in both directions)?
>>
>> Also in this case it is assumed that we can=92t know exactly the dynamic
>> parameters of the channel. For example the current s_l which is
>> updated every frame. This means that part of the parameters need to be
>> estimated.
>>
>> =A0
>>
>> Thanks,
>>
>> =A0
>>
>> Yuval
>>
>>  AudioCodes
>>
>>  =A0
>>
>> =A0
>>
>> =A0
>>
>> **********************************************************************=0D
>> *
>> *************************************
>> This email and any files transmitted with it are confidential =0D
>> material.
>> They are intended solely for the use of the designated individual or
>> entity to whom they are addressed.
>> If the reader of this message is not the intended recipient,
>> you are hereby notified that any dissemination,use,
>> distribution or copying of this communication is strictly prohibited
>> and may be unlawful.
>>
>> If you have received this email in error please notify
>> postmaster@audiocodes.com and permanently delete the e-mail and files.
>>
>>
>> **********************************************************************=0D
>> *
>> ************************************
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www1.ietf.org/mailman/listinfo/avt
>
>
> ***********************************************************************=0D
> *************************************
> This email and any files transmitted with it are confidential material.
> They are intended solely for the use of the designated individual or =0D
> entity to whom they are addressed.
> If the reader of this message is not the intended recipient,
> you are hereby notified that any dissemination,use,
> distribution or copying of this communication is strictly prohibited =0D
> and may be unlawful.
>
> If you have received this email in error please notify =0D
> postmaster@audiocodes.com and permanently delete the e-mail and files.
>
>
> ***********************************************************************=0D
> ************************************
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>


***************************************************************************=
*********************************
This email and any files transmitted with it are confidential material.
They are intended solely for the use of the designated individual or entity=
 to whom they are addressed.
If the reader of this message is not the intended recipient,
you are hereby notified that any dissemination,use,
distribution or copying of this communication is strictly prohibited and=
 may be unlawful.

If you have received this email in error please notify=
 postmaster@audiocodes.com and permanently delete the e-mail and files.


***************************************************************************=
********************************

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Tue Nov 23 10:25:05 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20989
	for <avt-archive@ietf.org>; Tue, 23 Nov 2004 10:25:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWcb9-0007NJ-2s
	for avt-archive@ietf.org; Tue, 23 Nov 2004 10:28:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWcRR-0007q0-J1; Tue, 23 Nov 2004 10:18:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWcIY-0003m9-RV
	for avt@megatron.ietf.org; Tue, 23 Nov 2004 10:09:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18822
	for <avt@ietf.org>; Tue, 23 Nov 2004 10:09:40 -0500 (EST)
Received: from bay2-f33.bay2.hotmail.com ([65.54.247.33] helo=hotmail.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWcME-0005JH-2a
	for avt@ietf.org; Tue, 23 Nov 2004 10:13:31 -0500
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Tue, 23 Nov 2004 07:09:09 -0800
Message-ID: <BAY2-F33625A39A29E16FAE5CAB5BDC70@phx.gbl>
Received: from 199.33.79.4 by by2fd.bay2.hotmail.msn.com with HTTP;
	Tue, 23 Nov 2004 15:08:41 GMT
X-Originating-IP: [199.33.79.4]
X-Originating-Email: [srtpdev@hotmail.com]
X-Sender: srtpdev@hotmail.com
In-Reply-To: <3AD208E1F0D5EB47AC3C5617420BCB0210622A@esealmw104.eemea.ericsson.se>
From: "milo diurn" <srtpdev@hotmail.com>
To: karl.norrman@ericsson.com
Subject: [AVT] RFC3711:  Srtp validation.
Date: Tue, 23 Nov 2004 15:08:41 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
X-OriginalArrivalTime: 23 Nov 2004 15:09:09.0501 (UTC)
	FILETIME=[620F8AD0:01C4D16E]
X-Spam-Score: 3.7 (+++)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: elisabetta.carrara@ericsson.com, mcgrew@cisco.com, avt@ietf.org,
        mbaugher@cisco.com
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 3.7 (+++)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906


Karl, Srtp Authors,

Thanks for your previous answers.

An other one about Srtp validation.

Is there any tools, or sw (free or not) allowing to validate Srtp under many 
conditions ?

A kind of Srtp Certification.

Thanks.

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Tue Nov 23 10:57:19 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24455
	for <avt-archive@ietf.org>; Tue, 23 Nov 2004 10:57:18 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWd6L-0003Ne-Cc
	for avt-archive@ietf.org; Tue, 23 Nov 2004 11:01:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWcyn-0008AS-Vs; Tue, 23 Nov 2004 10:53:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWcnZ-00053u-G0
	for avt@megatron.ietf.org; Tue, 23 Nov 2004 10:41:45 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22627
	for <avt@ietf.org>; Tue, 23 Nov 2004 10:41:42 -0500 (EST)
Received: from mx.cbeyond.net ([66.180.96.58] helo=mx.cbeyond.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWcrF-0001Hk-J5
	for avt@ietf.org; Tue, 23 Nov 2004 10:45:34 -0500
Received: from [64.238.103.215] (port=1186 helo=telws116)
	by mx.cbeyond.com with asmtp (Exim 4.34) id 1CWcnX-0007Oc-L2
	for avt@ietf.org; Tue, 23 Nov 2004 10:41:43 -0500
From: "Alan Clark" <alan.d.clark@telchemy.com>
To: <avt@ietf.org>
Subject: [AVT] RFC 3711 and RTCP
Date: Tue, 23 Nov 2004 10:41:43 -0500
Message-ID: <BGEKJNNFCPJKLLMMDMELCEGCFLAA.alan.d.clark@telchemy.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
In-Reply-To: <7650D648-3CB7-11D9-A48C-000A95C73842@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit


>From the flurry of discussion on RFC3711 it looks as if there is
considerable interest in SRTP implementation.  I'd like to add a request to
SRTP implementors with regard to manageability.

RTCP SR, RR and more particularly XR (e.g. VoIP Metrics report block)
contain useful information for network monitoring, and are often used by
probes and analyzers to support problem diagnosis.  RFC3711 allows the
selective encryption of RTCP payloads and hence I would strongly recomment
that RFC3711 implementors DO NOT encrypt RTCP SR, RR and XR payloads as this
adversely impacts manageability.

Regards

Alan Clark
Telchemy


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Tue Nov 23 12:37:22 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02270
	for <avt-archive@ietf.org>; Tue, 23 Nov 2004 12:37:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWefD-0008En-C0
	for avt-archive@ietf.org; Tue, 23 Nov 2004 12:41:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWeP6-0001F9-Cf; Tue, 23 Nov 2004 12:24:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWeAS-0004Jg-D4
	for avt@megatron.ietf.org; Tue, 23 Nov 2004 12:09:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00775
	for <avt@ietf.org>; Tue, 23 Nov 2004 12:09:25 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWeE9-0004gI-7Y for avt@ietf.org; Tue, 23 Nov 2004 12:13:17 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 23 Nov 2004 09:13:51 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iANH8mAC011082;
	Tue, 23 Nov 2004 09:08:48 -0800 (PST)
Received: from [192.168.0.10] (sjc-vpn4-1459.cisco.com [10.21.85.178])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id iANH8mPX027919;
	Tue, 23 Nov 2004 09:08:48 -0800
In-Reply-To: <79B4F738DDD4EF4F85A4641A0FE5EFD6096E4A@aclmsg.corp.audiocodes.com>
References: <79B4F738DDD4EF4F85A4641A0FE5EFD6096E4A@aclmsg.corp.audiocodes.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed
Message-Id: <5712274A-3D72-11D9-A16E-000A95DC10F2@cisco.com>
Content-Transfer-Encoding: quoted-printable
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [AVT] RFC 3711 and High Availability
Date: Tue, 23 Nov 2004 09:08:48 -0800
To: "Yuval Nissan" <YuvalN@audiocodes.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1101229728.717622"; x:"432200"; a:"rsa-sha1"; b:"nofws:9053";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"MY0RObJWSKR0kcNZVu2FyiIW6k0uTtV0mv1i7c0IPMgoZLVE5BBkbbYJ46us4"
	"WtAJwTKDxQCO2t5Qi+qadBHY6o3ltQmi1uUoUyMVzbCItDawoNWqmC88ytbSZ"
	"JdeDodUcBJhWXURdy8GTF91F6924Cgo795/0g991qC4mHubX0=";
	c:"From: Mark Baugher <mbaugher@cisco.com>";
	c:"Subject: Re: [AVT] RFC 3711 and High Availability";
	c:"Date: Tue, 23 Nov 2004 09:08:48 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 27ec2ff0f5c3b18b49c722f4f1748838
Content-Transfer-Encoding: quoted-printable
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 249cd1efd3d5e0d09114abe826a41235
Content-Transfer-Encoding: quoted-printable

Yuval,
   I have not thought of anything that would break using such a "lazy" =20=

synchronization of the SEQ on the sender on an HA system.  Perhaps =20
someone else on this list will.  There are so many RTP payload types =20
with so many distinct operational characteristics, I'd be careful and =20=

take the payload type(s) that you are using into consideration when =20
analyzing this approach.

On Nov 23, 2004, at 12:21 AM, Yuval Nissan wrote:

>
> Mark,
> Consider the second solution you propose (the lazy update), there is =20=

> possibility to make the update much less frequent (but still must be =20=

> less than every 2^15 packets),

Specifically, we are concerned with an SRTP replay-window-size number =20=

of packets; section 3.3.2 of RFC 3711 sets the default to 64, which =20
means you will synchronize the hot-standby machine about every 64 =20
packets rather than following each packet.  Failover occurs within this =20=

window of 64 packets, but the value of SEQ for the last packet sent is =20=

unknown.  Thus, it's necessary to advance the SEQ by the window size to =20=

ensure that subsequent packets don't collide with previous packets =20
sent.

> and to estimate Transmit SEQ as following:
> TransmitSEQ =3D =20
> lastUpdateTransmitSEQ+TimeFromLastUpdate/PacketFrameSize+Delta

I think it would be
TransmitSEQ =3D lastUpdateTransmitSEQ + RTPWindowSize

> (and also update the transmit ROC if needed).
>
> I think this also should work if appendix A is implemented.

I think appendix A, or something like it, always needs to be =20
implemented.

Mark
>
> Yuval
>
> -----Original Message-----
> From: Mark Baugher [mailto:mbaugher@cisco.com]
> Sent: Monday, November 22, 2004 8:47 PM
> To: Yuval Nissan
> Cc: avt@ietf.org
> Subject: Re: [AVT] RFC 3711 and High Availability
>
> Yuval,
>
> On Nov 22, 2004, at 12:32 AM, Yuval Nissan wrote:
>
>>
>> Mark,
>> I meant the second case you describe, with hot-standby mode.
>>
>> The problem in HA systems of this kind is that you want minimum
>> updates of the dynamic parameters in order not to overload the =
boards.
>>
>> Actually, the main issue I see is with s_l and SEQ that are updated
>> every frame. What is the minimum rate that they are needed to be
>> updated and how should they be estimated?
>
> s_l (at the receiver), SEQ (at the sender) and potentially the ROC =
need
> to be updated on every packet to be strictly correct, and I can see =
why
> this would be impractical in hot-standby mode.  There are a few
> tradeoffs.  If you want a nearly-seamless transition to the standby
> machine, then s_l needs to consistent between receiving machines and
> SEQ between sending machines.  If this is not practical and the HA
> application requirements permit a round-trip signaling message during
> recovery, then Dave Oran's suggestion seems to be a straightforward =
and
> reliable solution.  I'd opt for this.
>
> Alternatively, consider Appendix A:  Appendix A handles the case where
> the sequence-number wraps to zero, and I think the ROC update will be
> correct so long as s_l stays within 2^15 packets of SEQ.  The replay
> window is a tighter bound.  Thinking out loud, it might be possible to
> update SEQ and s_l infrequently if you take account of the size of
> replay window.  Lazy update at the sender will cause problems at the
> receiver until the sender's SEQ reaches the receiver's s_l.  All of =
the
> senders packets with a SEQ less than s_l minus the replay-window-size
> (modulo 2^16) will get discarded.  The sender's packets that are =
within
> that window will get discarded if they match previously-received
> packets or else they would be incorrectly accepted.  So it might be
> possible to update SEQ on the hot-standby machine in increments of the
> replay window size.  When failover occurs, the last recorded SEQ would
> be incremented by the replay-window size and the hot-standby sender
> could resume sending packets with the new SEQ, and the receiver would
> update it's s_l to the new, higher-value SEQ.  This might work, but =
I'm
> not entirely sure.
>
> Mark
>>
>> Thanks,
>> Yuval
>>
>> -----Original Message-----
>> From: Mark Baugher [mailto:mbaugher@cisco.com]
>> Sent: Sunday, November 21, 2004 11:26 PM
>> To: Yuval Nissan
>> Cc: avt@ietf.org
>> Subject: Re: [AVT] RFC 3711 and High Availability
>>
>> Yuval
>>    You mention the channel crashing and there seems to be two major
>> cases, either the destination or source addresses change or they =20
>> don't.
>>   If they do change, then we effectively have a new session.  Often
>> they
>> won't change in an HA system, so I can't immediately recognize any
>> affects on the state of the end-systems.  s_l should be easily
>> recovered and ROC correctly updated unless there are more than 2^15
>> packets lost.
>>
>>    In the case where a sender or a receiver fail, then I think it =
will
>> be hard to seamlessly handle a transition to another sender and
>> receiver unless the addresses remain the same and most of the
>> cryptographic context is recovered.  Commercial HA systems can do =20
>> this,
>> at least in a hot-standby mode, can't they?
>>
>> Mark
>> On Nov 21, 2004, at 12:18 AM, Yuval Nissan wrote:
>>
>>> Hello,
>>>
>>> I have question regarding SRTP and High Availability. This issue =20
>>> isn=92t
>>> covered by RFC 3711:
>>>
>>> The question is if channel crashes, what are the parameters that =
need
>>> to be recovered by the new channel so that the conversation will
>>> continue (in both directions)?
>>>
>>> Also in this case it is assumed that we can=92t know exactly the =20
>>> dynamic
>>> parameters of the channel. For example the current s_l which is
>>> updated every frame. This means that part of the parameters need to =20=

>>> be
>>> estimated.
>>>
>>> =A0
>>>
>>> Thanks,
>>>
>>> =A0
>>>
>>> Yuval
>>>
>>>  AudioCodes
>>>
>>>  =A0
>>>
>>> =A0
>>>
>>> =A0
>>>
>>> =
*********************************************************************=20
>>> *
>>> *
>>> *************************************
>>> This email and any files transmitted with it are confidential
>>> material.
>>> They are intended solely for the use of the designated individual or
>>> entity to whom they are addressed.
>>> If the reader of this message is not the intended recipient,
>>> you are hereby notified that any dissemination,use,
>>> distribution or copying of this communication is strictly prohibited
>>> and may be unlawful.
>>>
>>> If you have received this email in error please notify
>>> postmaster@audiocodes.com and permanently delete the e-mail and =20
>>> files.
>>>
>>>
>>> =
*********************************************************************=20
>>> *
>>> *
>>> ************************************
>>> _______________________________________________
>>> Audio/Video Transport Working Group
>>> avt@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/avt
>>
>>
>> =
**********************************************************************=20=

>> *
>> *************************************
>> This email and any files transmitted with it are confidential =20
>> material.
>> They are intended solely for the use of the designated individual or
>> entity to whom they are addressed.
>> If the reader of this message is not the intended recipient,
>> you are hereby notified that any dissemination,use,
>> distribution or copying of this communication is strictly prohibited
>> and may be unlawful.
>>
>> If you have received this email in error please notify
>> postmaster@audiocodes.com and permanently delete the e-mail and =
files.
>>
>>
>> =
**********************************************************************=20=

>> *
>> ************************************
>>
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www1.ietf.org/mailman/listinfo/avt
>>
>
>
> =
***********************************************************************=20=

> *************************************
> This email and any files transmitted with it are confidential =
material.
> They are intended solely for the use of the designated individual or =20=

> entity to whom they are addressed.
> If the reader of this message is not the intended recipient,
> you are hereby notified that any dissemination,use,
> distribution or copying of this communication is strictly prohibited =20=

> and may be unlawful.
>
> If you have received this email in error please notify =20
> postmaster@audiocodes.com and permanently delete the e-mail and files.
>
>
> =
***********************************************************************=20=

> ************************************
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 24 08:01:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20385
	for <avt-archive@ietf.org>; Wed, 24 Nov 2004 08:01:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWwph-0007xK-TI
	for avt-archive@ietf.org; Wed, 24 Nov 2004 08:05:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWwha-0000Ah-Up; Wed, 24 Nov 2004 07:56:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWwai-0006sO-Av
	for avt@megatron.ietf.org; Wed, 24 Nov 2004 07:49:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18154
	for <avt@ietf.org>; Wed, 24 Nov 2004 07:49:46 -0500 (EST)
Received: from [212.179.22.140] (helo=imss.audiocodes.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWweP-0006Up-GC
	for avt@ietf.org; Wed, 24 Nov 2004 07:53:48 -0500
Received: from aclmsg.corp.audiocodes.com ([10.1.0.8]) by imss with InterScan
	Messaging Security Suite; Wed, 24 Nov 2004 15:55:49 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] RFC 3711 and RTCP
Date: Wed, 24 Nov 2004 14:49:49 +0200
Message-ID: <EF8DFB1B64FF0A43AB00555B8E2717B19F6B3A@aclmsg.corp.audiocodes.com>
Thread-Topic: [AVT] RFC 3711 and RTCP
Thread-Index: AcTRdaq8DuSVVjfkS4qpKF8pWBJ4XQAriEsg
From: "Oren Peleg" <OrenP@audiocodes.com>
To: "Alan Clark" <alan.d.clark@telchemy.com>, <avt@ietf.org>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: quoted-printable
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: quoted-printable


Isnt encryption is to prevent monitoring from the first place?

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Alan Clark
Sent: Tuesday, November 23, 2004 5:42 PM
To: avt@ietf.org
Subject: [AVT] RFC 3711 and RTCP


>From the flurry of discussion on RFC3711 it looks as if there is
considerable interest in SRTP implementation.  I'd like to add a request
to
SRTP implementors with regard to manageability.

RTCP SR, RR and more particularly XR (e.g. VoIP Metrics report block)
contain useful information for network monitoring, and are often used by
probes and analyzers to support problem diagnosis.  RFC3711 allows the
selective encryption of RTCP payloads and hence I would strongly
recomment
that RFC3711 implementors DO NOT encrypt RTCP SR, RR and XR payloads as
this
adversely impacts manageability.

Regards

Alan Clark
Telchemy


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

***************************************************************************=
*********************************
This email and any files transmitted with it are confidential material.
They are intended solely for the use of the designated individual or entity=
 to whom they are addressed.
If the reader of this message is not the intended recipient,
you are hereby notified that any dissemination,use,
distribution or copying of this communication is strictly prohibited and=
 may be unlawful.

If you have received this email in error please notify=
 postmaster@audiocodes.com and permanently delete the e-mail and files.


***************************************************************************=
********************************

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 24 08:04:11 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20557
	for <avt-archive@ietf.org>; Wed, 24 Nov 2004 08:04:11 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWwsX-0008Gf-5J
	for avt-archive@ietf.org; Wed, 24 Nov 2004 08:08:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWwju-0000cr-OA; Wed, 24 Nov 2004 07:59:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWwes-0007us-R7
	for avt@megatron.ietf.org; Wed, 24 Nov 2004 07:54:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18744
	for <avt@ietf.org>; Wed, 24 Nov 2004 07:54:05 -0500 (EST)
Received: from mx.cbeyond.net ([66.180.96.58] helo=mx.cbeyond.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWwik-00076v-FS
	for avt@ietf.org; Wed, 24 Nov 2004 07:58:06 -0500
Received: from [67.33.162.5] (port=1323 helo=telws116)
	by mx.cbeyond.com with asmtp (Exim 4.34)
	id 1CWwer-0006xr-9D; Wed, 24 Nov 2004 07:54:05 -0500
From: "Alan Clark" <alan.d.clark@telchemy.com>
To: "Oren Peleg" <OrenP@audiocodes.com>, <avt@ietf.org>
Subject: RE: [AVT] RFC 3711 and RTCP
Date: Wed, 24 Nov 2004 07:54:06 -0500
Message-ID: <BGEKJNNFCPJKLLMMDMELIEJBFLAA.alan.d.clark@telchemy.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
In-Reply-To: <EF8DFB1B64FF0A43AB00555B8E2717B19F6B3A@aclmsg.corp.audiocodes.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: 7bit
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Content-Transfer-Encoding: 7bit

Hi Oren

Yes - encryption is intended to provide privacy however this relates
primarily to the voice payloads and to information within RTCP that may be
associated with individual users (e.g. SDES).

SR, RR and XR contain only peformance statistics and there is no privacy
consideration that I can think of related to this type of data.

The message is - encrypt RTP, optionally encrypt RTCP SDES but don't encrypt
RTCP SR/RR/XR

Regards

Alan

-----Original Message-----
From: Oren Peleg [mailto:OrenP@audiocodes.com]
Sent: Wednesday, November 24, 2004 7:50 AM
To: Alan Clark; avt@ietf.org
Subject: RE: [AVT] RFC 3711 and RTCP



Isnt encryption is to prevent monitoring from the first place?

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Alan Clark
Sent: Tuesday, November 23, 2004 5:42 PM
To: avt@ietf.org
Subject: [AVT] RFC 3711 and RTCP


>From the flurry of discussion on RFC3711 it looks as if there is
considerable interest in SRTP implementation.  I'd like to add a request
to
SRTP implementors with regard to manageability.

RTCP SR, RR and more particularly XR (e.g. VoIP Metrics report block)
contain useful information for network monitoring, and are often used by
probes and analyzers to support problem diagnosis.  RFC3711 allows the
selective encryption of RTCP payloads and hence I would strongly
recomment
that RFC3711 implementors DO NOT encrypt RTCP SR, RR and XR payloads as
this
adversely impacts manageability.

Regards

Alan Clark
Telchemy


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

****************************************************************************
********************************
This email and any files transmitted with it are confidential material.
They are intended solely for the use of the designated individual or entity
to whom they are addressed.
If the reader of this message is not the intended recipient,
you are hereby notified that any dissemination,use,
distribution or copying of this communication is strictly prohibited and may
be unlawful.

If you have received this email in error please notify
postmaster@audiocodes.com and permanently delete the e-mail and files.


****************************************************************************
*******************************


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 24 09:47:40 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29014
	for <avt-archive@ietf.org>; Wed, 24 Nov 2004 09:47:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWyUh-00023q-5P
	for avt-archive@ietf.org; Wed, 24 Nov 2004 09:51:43 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWyKa-00085a-Qu; Wed, 24 Nov 2004 09:41:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWyIg-0007ZB-0l
	for avt@megatron.ietf.org; Wed, 24 Nov 2004 09:39:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27963
	for <avt@ietf.org>; Wed, 24 Nov 2004 09:39:16 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWyMX-00014v-Om for avt@ietf.org; Wed, 24 Nov 2004 09:43:19 -0500
Received: from sj-core-4.cisco.com (171.68.223.138)
	by sj-iport-1.cisco.com with ESMTP; 24 Nov 2004 06:43:50 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mramalho-w2k.cisco.com (sjc-vpn5-651.cisco.com [10.21.90.139])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id iAOEcefu007782;
	Wed, 24 Nov 2004 06:38:41 -0800 (PST)
Message-Id: <4.3.2.7.2.20041124092246.00c97668@mira-sjc5-e.cisco.com>
X-Sender: mramalho@mira-sjc5-e.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 24 Nov 2004 09:38:40 -0500
To: "Alan Clark" <alan.d.clark@telchemy.com>
From: "Michael A. Ramalho" <mramalho@cisco.com>
Subject: RE: [AVT] RFC 3711 and RTCP
In-Reply-To: <BGEKJNNFCPJKLLMMDMELIEJBFLAA.alan.d.clark@telchemy.com>
References: <EF8DFB1B64FF0A43AB00555B8E2717B19F6B3A@aclmsg.corp.audiocodes.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Cc: Oren Peleg <OrenP@audiocodes.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433

At 07:54 AM 11/24/2004 -0500, Alan Clark wrote:
>Hi Oren
>
>Yes - encryption is intended to provide privacy however this relates
>primarily to the voice payloads and to information within RTCP that may be
>associated with individual users (e.g. SDES).
>
>SR, RR and XR contain only peformance statistics and there is no privacy
>consideration that I can think of related to this type of data.
>
>The message is - encrypt RTP, optionally encrypt RTCP SDES but don't encrypt
>RTCP SR/RR/XR

Hi Alan,

I am wondering about implementations utilizing your advise "optionally encrypt
RTCP SDES but don't encrypt RTCP SR/RR/XR".

Is there an easy way to tell SRTP to encrypt RTCP SDES, but not RTCP
SR/RR/XR? It seems that all the RTCP blocks would otherwise be highly
related to each other. For example (quote out of RFC 3611):

"XR packets supplement the existing RTCP packets, and may be stacked with
other RTCP packets to form compound RTCP packets [9, Section 6]."

Thus, RFC3611 explicitly admits the possibility of (but does not mandate)
the piggybacking all the RTCP-XR block types.

RTCP implementations would have to know the SRTP encryption rules to
make sure they don't perform piggybacking with SDES ... but could allow
(the more bandwidth efficient) piggybacking on the other RTCP-XR blocks.

This RTCP/SRTP interaction/dependency seems to add a burden to both
RTCP and SRTP implementations ... let alone the expressiveness required
to signal your advise in existing SDP/SRTP mechanisms.

Are you aware of any implementations that have actually followed your
advise above? I rather go into this one with our eyes open ... developers
highly dislike this cross-functional entity dependency (RTCP & SRTP along
with expressing it in SDP/SRTP mechanisms).

Regards,

Michael Ramalho



>Regards
>
>Alan
>
>-----Original Message-----
>From: Oren Peleg [mailto:OrenP@audiocodes.com]
>Sent: Wednesday, November 24, 2004 7:50 AM
>To: Alan Clark; avt@ietf.org
>Subject: RE: [AVT] RFC 3711 and RTCP
>
>
>
>Isnt encryption is to prevent monitoring from the first place?
>
>-----Original Message-----
>From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
>Alan Clark
>Sent: Tuesday, November 23, 2004 5:42 PM
>To: avt@ietf.org
>Subject: [AVT] RFC 3711 and RTCP
>
>
> >From the flurry of discussion on RFC3711 it looks as if there is
>considerable interest in SRTP implementation.  I'd like to add a request
>to
>SRTP implementors with regard to manageability.
>
>RTCP SR, RR and more particularly XR (e.g. VoIP Metrics report block)
>contain useful information for network monitoring, and are often used by
>probes and analyzers to support problem diagnosis.  RFC3711 allows the
>selective encryption of RTCP payloads and hence I would strongly
>recomment
>that RFC3711 implementors DO NOT encrypt RTCP SR, RR and XR payloads as
>this
>adversely impacts manageability.
>
>Regards
>
>Alan Clark
>Telchemy
>
>
>_______________________________________________
>Audio/Video Transport Working Group
>avt@ietf.org
>https://www1.ietf.org/mailman/listinfo/avt
>
>****************************************************************************
>********************************
>This email and any files transmitted with it are confidential material.
>They are intended solely for the use of the designated individual or entity
>to whom they are addressed.
>If the reader of this message is not the intended recipient,
>you are hereby notified that any dissemination,use,
>distribution or copying of this communication is strictly prohibited and may
>be unlawful.
>
>If you have received this email in error please notify
>postmaster@audiocodes.com and permanently delete the e-mail and files.
>
>
>****************************************************************************
>*******************************
>
>
>_______________________________________________
>Audio/Video Transport Working Group
>avt@ietf.org
>https://www1.ietf.org/mailman/listinfo/avt


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 24 10:08:42 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01627
	for <avt-archive@ietf.org>; Wed, 24 Nov 2004 10:08:42 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWyp4-0004GF-2b
	for avt-archive@ietf.org; Wed, 24 Nov 2004 10:12:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWye6-0005K6-Lt; Wed, 24 Nov 2004 10:01:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWycw-0004EK-FX
	for avt@megatron.ietf.org; Wed, 24 Nov 2004 10:00:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00134
	for <avt@ietf.org>; Wed, 24 Nov 2004 10:00:12 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWygo-0003KT-4J
	for avt@ietf.org; Wed, 24 Nov 2004 10:04:15 -0500
Received: from alor.dcs.gla.ac.uk ([130.209.247.84]:55870)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1CWycM-0003lT-B8; Wed, 24 Nov 2004 14:59:38 +0000
In-Reply-To: <6.1.2.0.1.20041006133327.02d75450@localhost>
References: <6.1.2.0.1.20041006133327.02d75450@localhost>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <728017F1-3E29-11D9-B0BC-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Updated Internet Drafts for "audio/mpa-robust" Draft
	Standard
Date: Wed, 24 Nov 2004 14:59:31 +0000
To: Ross Finlayson <finlayson@live.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: 7bit
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7bit

Ross,

On 6 Oct 2004, at 21:38, Ross Finlayson wrote:
> FYI, I have made available two updated Internet Drafts related to the 
> "audio/mpa-robust" RTP payload format:
> 	draft-ietf-avt-rfc3119bis-03.txt
> 	draft-finlayson-avt-mpa-robust-interoperability-01.txt
>
> These versions were updated to use the proper new IETF 'boilerplate'; 
> there were no other changes.
>
> Can this now be progressed to Draft Standard?

Apologies for the slow response. I have a few minor comments after 
reviewing the payload format draft:

  - Section 4.4 notes that static payload type 14 was defined for MPEG 
audio
    but MUST NOT be used for this new format (which uses a dynamic 
payload
    type). That's fine, but the wording is not sufficient now we have 
many
    RTP profiles. Suggest changing it to:

       Payload Type: The assignment of an RTP payload type for this
          payload format is outside the scope of this document, and will
          not be specified here. It is expected that the RTP profile for
          a particular class of applications will assign a payload type
          for this encoding, or if that is not done then a payload type
          in the dynamic range SHALL be chosen. Note that the "RTP/AVP"
          profile [6] defines static payload type 14 for MPEG audio [2];
          that payload type MUST NOT be used for the format defined in
          this memo.

    or some similar wording, making it clear that payload type 14 is 
defined
    only in the context of RTP/AVP.

  - Last paragraph of section 5, please remove the * around *only* and
    *unless*.

  - The draft is missing an IANA Considerations section. The easiest
    fix would be to rename section 8 to "IANA Considerations" and add
    the text "The media type registration for audio/mpa-robust is to
    be updated as described below." to the start of the section.

  - The references need to be updated to match RFC 3550 and 3551.

  - Please check that the draft conforms to the formatting guidelines and
    passes the idnits tool without any nits being detected:

       idnits 1.49 (16 Nov 2004)

       draft-ietf-avt-rfc3119bis-03.txt:

         The document seems to lack an IANA Considerations section
         Checking conformance with RFC 3667/3668 boilerplate...
         the boilerplate looks good.
         The document is more than 15 pages and seems to lack a Table of
         Contents
         There are 43 instances of too long lines in the document,
         -- the longest one being 1 character in excess of 72.

These should be simple to fix, and otherwise this looks to be fine.
Colin


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 24 11:03:04 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06181
	for <avt-archive@ietf.org>; Wed, 24 Nov 2004 11:03:04 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWzfW-0001G0-KT
	for avt-archive@ietf.org; Wed, 24 Nov 2004 11:07:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWzWF-0007Lh-1C; Wed, 24 Nov 2004 10:57:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWzOT-0005BT-7W; Wed, 24 Nov 2004 10:49:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05122;
	Wed, 24 Nov 2004 10:49:18 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWzSB-0008Bb-91; Wed, 24 Nov 2004 10:53:22 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iAOFn7h5005937; Wed, 24 Nov 2004 16:49:07 +0100 (MET)
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 24 Nov 2004 16:49:07 +0100
Received: from [147.214.97.153] (permit153.er.ki.sw.ericsson.se
	[147.214.97.153]) by esealnt610.al.sw.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id XRD5YW3M; Wed, 24 Nov 2004 16:48:35 +0100
Message-ID: <41A4AD4C.7060607@ericsson.com>
Date: Wed, 24 Nov 2004 16:48:28 +0100
X-Sybari-Trust: 5abed82a 8ac546dc 47ea6b95 00000979
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>, rmt@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Nov 2004 15:49:07.0413 (UTC)
	FILETIME=[21BDA050:01C4D23D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
Subject: [AVT] 3GPP includes RTP FEC framework in MBMS specificaiton 26.346
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit

Hi,

3GPP WG SA4 has this week agreed to include the specification text 
present in the contribution;
http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/TSGS4_33/Docs/S4-040698.zip
to be included in 3GPP Technical specification 26.346 in Release 6.

There is know that some small changes are necessary to certain details. 
The changes known, is to the actual reference to the FEC encoding ID 
utilized in the RTP payload, which will be harmonized with the 
declaration used for FLUTE in SDP.

Cheers

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 24 12:33:23 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13828
	for <avt-archive@ietf.org>; Wed, 24 Nov 2004 12:33:23 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CX156-0000nw-MS
	for avt-archive@ietf.org; Wed, 24 Nov 2004 12:37:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CX0tt-00026f-46; Wed, 24 Nov 2004 12:25:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CX0lM-0006y2-O9
	for avt@megatron.ietf.org; Wed, 24 Nov 2004 12:17:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12089
	for <avt@ietf.org>; Wed, 24 Nov 2004 12:17:01 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CX0p5-0000CX-Pa
	for avt@ietf.org; Wed, 24 Nov 2004 12:21:07 -0500
Received: from sj-core-4.cisco.com (171.68.223.138)
	by sj-iport-4.cisco.com with ESMTP; 24 Nov 2004 09:16:52 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id iAOHGIft019013;
	Wed, 24 Nov 2004 09:16:18 -0800 (PST)
Received: from [192.168.0.10] (sjc-vpn4-827.cisco.com [10.21.83.58])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id iAOHGA4a002362;
	Wed, 24 Nov 2004 09:16:12 -0800
In-Reply-To: <4.3.2.7.2.20041124092246.00c97668@mira-sjc5-e.cisco.com>
References: <EF8DFB1B64FF0A43AB00555B8E2717B19F6B3A@aclmsg.corp.audiocodes.com>
	<4.3.2.7.2.20041124092246.00c97668@mira-sjc5-e.cisco.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <8ADEA3FD-3E3C-11D9-A16E-000A95DC10F2@cisco.com>
Content-Transfer-Encoding: 7bit
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [AVT] RFC 3711 and RTCP
Date: Wed, 24 Nov 2004 09:16:13 -0800
To: "Michael A. Ramalho" <mramalho@cisco.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1101316572.521158"; x:"432200"; a:"rsa-sha1"; b:"nofws:4914";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"j9HgxSer+s52UxaZ1ln4kWIZ1d3G0GPmFVu8Xc/wW8FKPO/KguS/0dW16YUfD"
	"UODexrzcNkDuo44IwDnGk8KrDVoxUa+lRHjl/Ev3CH/+9m1k14JuZ1m+pZKO0"
	"xb200rA5gq8XJ7yuV1aBspnWDNONphbDHLnNb0L4VL4YbLyaY=";
	c:"From: Mark Baugher <mbaugher@cisco.com>";
	c:"Subject: Re: [AVT] RFC 3711 and RTCP";
	c:"Date: Wed, 24 Nov 2004 09:16:13 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.2 (/)
X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985
Content-Transfer-Encoding: 7bit
Cc: Oren Peleg <OrenP@audiocodes.com>, avt@ietf.org,
        Alan Clark <alan.d.clark@telchemy.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f
Content-Transfer-Encoding: 7bit

It's not possible to selectively encrypt SRTCP packets.  The default is  
to encrypt SRTCP, but it is a matter of policy.  Presumably, SRTCP will  
be authenticated and not encrypted when monitoring is desired.  I think  
Alan's plea to implementers should be to ensure that SRTCP encryption  
is strictly optional.

Mark
On Nov 24, 2004, at 6:38 AM, Michael A. Ramalho wrote:

> At 07:54 AM 11/24/2004 -0500, Alan Clark wrote:
>> Hi Oren
>>
>> Yes - encryption is intended to provide privacy however this relates
>> primarily to the voice payloads and to information within RTCP that  
>> may be
>> associated with individual users (e.g. SDES).
>>
>> SR, RR and XR contain only peformance statistics and there is no  
>> privacy
>> consideration that I can think of related to this type of data.
>>
>> The message is - encrypt RTP, optionally encrypt RTCP SDES but don't  
>> encrypt
>> RTCP SR/RR/XR
>
> Hi Alan,
>
> I am wondering about implementations utilizing your advise "optionally  
> encrypt
> RTCP SDES but don't encrypt RTCP SR/RR/XR".
>
> Is there an easy way to tell SRTP to encrypt RTCP SDES, but not RTCP
> SR/RR/XR? It seems that all the RTCP blocks would otherwise be highly
> related to each other. For example (quote out of RFC 3611):
>
> "XR packets supplement the existing RTCP packets, and may be stacked  
> with
> other RTCP packets to form compound RTCP packets [9, Section 6]."
>
> Thus, RFC3611 explicitly admits the possibility of (but does not  
> mandate)
> the piggybacking all the RTCP-XR block types.
>
> RTCP implementations would have to know the SRTP encryption rules to
> make sure they don't perform piggybacking with SDES ... but could allow
> (the more bandwidth efficient) piggybacking on the other RTCP-XR  
> blocks.
>
> This RTCP/SRTP interaction/dependency seems to add a burden to both
> RTCP and SRTP implementations ... let alone the expressiveness required
> to signal your advise in existing SDP/SRTP mechanisms.
>
> Are you aware of any implementations that have actually followed your
> advise above? I rather go into this one with our eyes open ...  
> developers
> highly dislike this cross-functional entity dependency (RTCP & SRTP  
> along
> with expressing it in SDP/SRTP mechanisms).
>
> Regards,
>
> Michael Ramalho
>
>
>
>> Regards
>>
>> Alan
>>
>> -----Original Message-----
>> From: Oren Peleg [mailto:OrenP@audiocodes.com]
>> Sent: Wednesday, November 24, 2004 7:50 AM
>> To: Alan Clark; avt@ietf.org
>> Subject: RE: [AVT] RFC 3711 and RTCP
>>
>>
>>
>> Isnt encryption is to prevent monitoring from the first place?
>>
>> -----Original Message-----
>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
>> Alan Clark
>> Sent: Tuesday, November 23, 2004 5:42 PM
>> To: avt@ietf.org
>> Subject: [AVT] RFC 3711 and RTCP
>>
>>
>> >From the flurry of discussion on RFC3711 it looks as if there is
>> considerable interest in SRTP implementation.  I'd like to add a  
>> request
>> to
>> SRTP implementors with regard to manageability.
>>
>> RTCP SR, RR and more particularly XR (e.g. VoIP Metrics report block)
>> contain useful information for network monitoring, and are often used  
>> by
>> probes and analyzers to support problem diagnosis.  RFC3711 allows the
>> selective encryption of RTCP payloads and hence I would strongly
>> recomment
>> that RFC3711 implementors DO NOT encrypt RTCP SR, RR and XR payloads  
>> as
>> this
>> adversely impacts manageability.
>>
>> Regards
>>
>> Alan Clark
>> Telchemy
>>
>>
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www1.ietf.org/mailman/listinfo/avt
>>
>> ********************************************************************** 
>> ******
>> ********************************
>> This email and any files transmitted with it are confidential  
>> material.
>> They are intended solely for the use of the designated individual or  
>> entity
>> to whom they are addressed.
>> If the reader of this message is not the intended recipient,
>> you are hereby notified that any dissemination,use,
>> distribution or copying of this communication is strictly prohibited  
>> and may
>> be unlawful.
>>
>> If you have received this email in error please notify
>> postmaster@audiocodes.com and permanently delete the e-mail and files.
>>
>>
>> ********************************************************************** 
>> ******
>> *******************************
>>
>>
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www1.ietf.org/mailman/listinfo/avt
>
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 24 12:40:32 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14846
	for <avt-archive@ietf.org>; Wed, 24 Nov 2004 12:40:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CX1C1-00012D-Pl
	for avt-archive@ietf.org; Wed, 24 Nov 2004 12:44:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CX0zp-0003Zm-91; Wed, 24 Nov 2004 12:32:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CX0s3-0001F2-BT
	for avt@megatron.ietf.org; Wed, 24 Nov 2004 12:23:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12706
	for <avt@ietf.org>; Wed, 24 Nov 2004 12:23:56 -0500 (EST)
Received: from mx.cbeyond.net ([66.180.96.58] helo=mx.cbeyond.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CX0vx-0000Qd-8z
	for avt@ietf.org; Wed, 24 Nov 2004 12:28:01 -0500
Received: from [64.238.103.215] (port=1306 helo=telws116)
	by mx.cbeyond.com with asmtp (Exim 4.34)
	id 1CX0s1-0005N0-JT; Wed, 24 Nov 2004 12:23:57 -0500
From: "Alan Clark" <alan.d.clark@telchemy.com>
To: "Michael A. Ramalho" <mramalho@cisco.com>
Subject: RE: [AVT] RFC 3711 and RTCP
Date: Wed, 24 Nov 2004 12:23:56 -0500
Message-ID: <BGEKJNNFCPJKLLMMDMELEEJPFLAA.alan.d.clark@telchemy.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
In-Reply-To: <4.3.2.7.2.20041124092246.00c97668@mira-sjc5-e.cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78
Content-Transfer-Encoding: 7bit
Cc: Cullen Jennings <fluffy@cisco.com>, Oren Peleg <OrenP@audiocodes.com>,
        avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407
Content-Transfer-Encoding: 7bit


Michael

I don't see why this would be a problem unless you included SDES and (SR or
RR or XR) in the same RTCP packet.  SRTP (at least the protocol) is
apparently able to decided on a packet by packet basis whether to encrypt
RTCP - hopefully SRTP implementations also permit this.

Logically I'd send SDES on its own at the start of a call to provide some
user info, but would not send SR/RR/XR until at least 8-10 seconds into the
call as I need some time to gather statistics to report.  After the
start-of-call exchange there would appear to be minimal need to include
SDES. I'm sure we could construct some scenarios in which you "may" need to
include SDES with SR/RR/XR however the vast majority of cases would either
need only a single initial exchange or may not need SDES at all.

Regards

Alan



-----Original Message-----
From: Michael A. Ramalho [mailto:mramalho@cisco.com]
Sent: Wednesday, November 24, 2004 9:39 AM
To: Alan Clark
Cc: Oren Peleg; avt@ietf.org
Subject: RE: [AVT] RFC 3711 and RTCP


At 07:54 AM 11/24/2004 -0500, Alan Clark wrote:
>Hi Oren
>
>Yes - encryption is intended to provide privacy however this relates
>primarily to the voice payloads and to information within RTCP that may be
>associated with individual users (e.g. SDES).
>
>SR, RR and XR contain only peformance statistics and there is no privacy
>consideration that I can think of related to this type of data.
>
>The message is - encrypt RTP, optionally encrypt RTCP SDES but don't
encrypt
>RTCP SR/RR/XR

Hi Alan,

I am wondering about implementations utilizing your advise "optionally
encrypt
RTCP SDES but don't encrypt RTCP SR/RR/XR".

Is there an easy way to tell SRTP to encrypt RTCP SDES, but not RTCP
SR/RR/XR? It seems that all the RTCP blocks would otherwise be highly
related to each other. For example (quote out of RFC 3611):

"XR packets supplement the existing RTCP packets, and may be stacked with
other RTCP packets to form compound RTCP packets [9, Section 6]."

Thus, RFC3611 explicitly admits the possibility of (but does not mandate)
the piggybacking all the RTCP-XR block types.

RTCP implementations would have to know the SRTP encryption rules to
make sure they don't perform piggybacking with SDES ... but could allow
(the more bandwidth efficient) piggybacking on the other RTCP-XR blocks.

This RTCP/SRTP interaction/dependency seems to add a burden to both
RTCP and SRTP implementations ... let alone the expressiveness required
to signal your advise in existing SDP/SRTP mechanisms.

Are you aware of any implementations that have actually followed your
advise above? I rather go into this one with our eyes open ... developers
highly dislike this cross-functional entity dependency (RTCP & SRTP along
with expressing it in SDP/SRTP mechanisms).

Regards,

Michael Ramalho



>Regards
>
>Alan
>
>-----Original Message-----
>From: Oren Peleg [mailto:OrenP@audiocodes.com]
>Sent: Wednesday, November 24, 2004 7:50 AM
>To: Alan Clark; avt@ietf.org
>Subject: RE: [AVT] RFC 3711 and RTCP
>
>
>
>Isnt encryption is to prevent monitoring from the first place?
>
>-----Original Message-----
>From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
>Alan Clark
>Sent: Tuesday, November 23, 2004 5:42 PM
>To: avt@ietf.org
>Subject: [AVT] RFC 3711 and RTCP
>
>
> >From the flurry of discussion on RFC3711 it looks as if there is
>considerable interest in SRTP implementation.  I'd like to add a request
>to
>SRTP implementors with regard to manageability.
>
>RTCP SR, RR and more particularly XR (e.g. VoIP Metrics report block)
>contain useful information for network monitoring, and are often used by
>probes and analyzers to support problem diagnosis.  RFC3711 allows the
>selective encryption of RTCP payloads and hence I would strongly
>recomment
>that RFC3711 implementors DO NOT encrypt RTCP SR, RR and XR payloads as
>this
>adversely impacts manageability.
>
>Regards
>
>Alan Clark
>Telchemy
>
>
>_______________________________________________
>Audio/Video Transport Working Group
>avt@ietf.org
>https://www1.ietf.org/mailman/listinfo/avt
>
>***************************************************************************
*
>********************************
>This email and any files transmitted with it are confidential material.
>They are intended solely for the use of the designated individual or entity
>to whom they are addressed.
>If the reader of this message is not the intended recipient,
>you are hereby notified that any dissemination,use,
>distribution or copying of this communication is strictly prohibited and
may
>be unlawful.
>
>If you have received this email in error please notify
>postmaster@audiocodes.com and permanently delete the e-mail and files.
>
>
>***************************************************************************
*
>*******************************
>
>
>_______________________________________________
>Audio/Video Transport Working Group
>avt@ietf.org
>https://www1.ietf.org/mailman/listinfo/avt


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 24 13:21:37 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17953
	for <avt-archive@ietf.org>; Wed, 24 Nov 2004 13:21:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CX1pl-0002R3-Si
	for avt-archive@ietf.org; Wed, 24 Nov 2004 13:25:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CX1h6-0007Ow-80; Wed, 24 Nov 2004 13:16:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CX1Wl-00049H-KC
	for avt@megatron.ietf.org; Wed, 24 Nov 2004 13:06:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16620
	for <avt@ietf.org>; Wed, 24 Nov 2004 13:06:00 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CX1af-0001rf-Vt for avt@ietf.org; Wed, 24 Nov 2004 13:10:06 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-3.cisco.com with ESMTP; 24 Nov 2004 11:11:28 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iAOI5OAC028266;
	Wed, 24 Nov 2004 10:05:24 -0800 (PST)
Received: from [10.32.245.156] (stealth-10-32-245-156.cisco.com
	[10.32.245.156])
	by imail.cisco.com (8.12.11/8.12.10) with SMTP id iAOI5DkC002772;
	Wed, 24 Nov 2004 10:05:17 -0800
In-Reply-To: <BGEKJNNFCPJKLLMMDMELEEJPFLAA.alan.d.clark@telchemy.com>
References: <BGEKJNNFCPJKLLMMDMELEEJPFLAA.alan.d.clark@telchemy.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <62B7EEEA-3E43-11D9-8CD3-000A95C73842@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Subject: Re: [AVT] RFC 3711 and RTCP
Date: Wed, 24 Nov 2004 13:05:12 -0500
To: "Alan Clark" <alan.d.clark@telchemy.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1101319523.320987"; x:"432200"; a:"rsa-sha1"; b:"nofws:6821";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"X6/jkERqaUqQcaqlB5UEgfFxDQ3u7YnUVwM2P5865T3lUrcqbA4bfbfL319tQ"
	"6DiHNEShhA+FI8nsp/g+oXplzxzipRGj4S1CHB/g2OKYFGGe095sQDQdD+ND8"
	"1WOOBgfiT5CBoo2SgEe6CHE1Kjx8mrvDKo67oq1u7KHarBY64=";
	c:"From: David R Oran <oran@cisco.com>";
	c:"Subject: Re: [AVT] RFC 3711 and RTCP";
	c:"Date: Wed, 24 Nov 2004 13:05:12 -0500"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.2 (/)
X-Scan-Signature: a743e34ab8eb08259de9a7307caed594
Content-Transfer-Encoding: 7bit
Cc: Cullen Jennings <fluffy@cisco.com>, Oren Peleg <OrenP@audiocodes.com>,
        "Michael A. Ramalho" <mramalho@cisco.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: ff0adf256e4dd459cc25215cfa732ac1
Content-Transfer-Encoding: 7bit


On Nov 24, 2004, at 12:23 PM, Alan Clark wrote:

>
> Michael
>
> I don't see why this would be a problem unless you included SDES and  
> (SR or
> RR or XR) in the same RTCP packet.  SRTP (at least the protocol) is
> apparently able to decided on a packet by packet basis whether to  
> encrypt
> RTCP - hopefully SRTP implementations also permit this.
>
Sure, they can do this. But remember offer-answer. How does a receiver  
communicate such a granular policy to the transmitter? Right now if can  
say whether to auth or auth+encrypt RTP, and auth or auth+encrypt RTCP.  
There's no way to say auth+encrypt SDES but only auth SR/XR etc.


> Logically I'd send SDES on its own at the start of a call to provide  
> some
> user info, but would not send SR/RR/XR until at least 8-10 seconds  
> into the
> call as I need some time to gather statistics to report.
That's not exactly what the RTP specs say. RTCP timers don't have this  
kind of policy today. In fact, there are porposals on the table to use  
RTCP for early feedback to assess reception quality on some initial  
packets - e.g. the RTP-noop proposal. In any event that has no bearing  
on the present discussion.

> After the
> start-of-call exchange there would appear to be minimal need to include
> SDES. I'm sure we could construct some scenarios in which you "may"  
> need to
> include SDES with SR/RR/XR however the vast majority of cases would  
> either
> need only a single initial exchange or may not need SDES at all.
>
Any time you change SSRC you potentially need to send SDES.
That said, I still don't see what bearing this has on the discussion  
about whether we need the complexity of encrypting some RTCP packets  
and not others for a single session.

It's a tradeoff between extra complexity+less privacy versus allowing  
snoopers to gather RTCP stats.

Dave.

> Regards
>
> Alan
>
>
>
> -----Original Message-----
> From: Michael A. Ramalho [mailto:mramalho@cisco.com]
> Sent: Wednesday, November 24, 2004 9:39 AM
> To: Alan Clark
> Cc: Oren Peleg; avt@ietf.org
> Subject: RE: [AVT] RFC 3711 and RTCP
>
>
> At 07:54 AM 11/24/2004 -0500, Alan Clark wrote:
>> Hi Oren
>>
>> Yes - encryption is intended to provide privacy however this relates
>> primarily to the voice payloads and to information within RTCP that  
>> may be
>> associated with individual users (e.g. SDES).
>>
>> SR, RR and XR contain only peformance statistics and there is no  
>> privacy
>> consideration that I can think of related to this type of data.
>>
>> The message is - encrypt RTP, optionally encrypt RTCP SDES but don't
> encrypt
>> RTCP SR/RR/XR
>
> Hi Alan,
>
> I am wondering about implementations utilizing your advise "optionally
> encrypt
> RTCP SDES but don't encrypt RTCP SR/RR/XR".
>
> Is there an easy way to tell SRTP to encrypt RTCP SDES, but not RTCP
> SR/RR/XR? It seems that all the RTCP blocks would otherwise be highly
> related to each other. For example (quote out of RFC 3611):
>
> "XR packets supplement the existing RTCP packets, and may be stacked  
> with
> other RTCP packets to form compound RTCP packets [9, Section 6]."
>
> Thus, RFC3611 explicitly admits the possibility of (but does not  
> mandate)
> the piggybacking all the RTCP-XR block types.
>
> RTCP implementations would have to know the SRTP encryption rules to
> make sure they don't perform piggybacking with SDES ... but could allow
> (the more bandwidth efficient) piggybacking on the other RTCP-XR  
> blocks.
>
> This RTCP/SRTP interaction/dependency seems to add a burden to both
> RTCP and SRTP implementations ... let alone the expressiveness required
> to signal your advise in existing SDP/SRTP mechanisms.
>
> Are you aware of any implementations that have actually followed your
> advise above? I rather go into this one with our eyes open ...  
> developers
> highly dislike this cross-functional entity dependency (RTCP & SRTP  
> along
> with expressing it in SDP/SRTP mechanisms).
>
> Regards,
>
> Michael Ramalho
>
>
>
>> Regards
>>
>> Alan
>>
>> -----Original Message-----
>> From: Oren Peleg [mailto:OrenP@audiocodes.com]
>> Sent: Wednesday, November 24, 2004 7:50 AM
>> To: Alan Clark; avt@ietf.org
>> Subject: RE: [AVT] RFC 3711 and RTCP
>>
>>
>>
>> Isnt encryption is to prevent monitoring from the first place?
>>
>> -----Original Message-----
>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
>> Alan Clark
>> Sent: Tuesday, November 23, 2004 5:42 PM
>> To: avt@ietf.org
>> Subject: [AVT] RFC 3711 and RTCP
>>
>>
>>> From the flurry of discussion on RFC3711 it looks as if there is
>> considerable interest in SRTP implementation.  I'd like to add a  
>> request
>> to
>> SRTP implementors with regard to manageability.
>>
>> RTCP SR, RR and more particularly XR (e.g. VoIP Metrics report block)
>> contain useful information for network monitoring, and are often used  
>> by
>> probes and analyzers to support problem diagnosis.  RFC3711 allows the
>> selective encryption of RTCP payloads and hence I would strongly
>> recomment
>> that RFC3711 implementors DO NOT encrypt RTCP SR, RR and XR payloads  
>> as
>> this
>> adversely impacts manageability.
>>
>> Regards
>>
>> Alan Clark
>> Telchemy
>>
>>
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www1.ietf.org/mailman/listinfo/avt
>>
>> ********************************************************************** 
>> *****
> *
>> ********************************
>> This email and any files transmitted with it are confidential  
>> material.
>> They are intended solely for the use of the designated individual or  
>> entity
>> to whom they are addressed.
>> If the reader of this message is not the intended recipient,
>> you are hereby notified that any dissemination,use,
>> distribution or copying of this communication is strictly prohibited  
>> and
> may
>> be unlawful.
>>
>> If you have received this email in error please notify
>> postmaster@audiocodes.com and permanently delete the e-mail and files.
>>
>>
>> ********************************************************************** 
>> *****
> *
>> *******************************
>>
>>
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www1.ietf.org/mailman/listinfo/avt
>
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>
David R. Oran
Cisco Fellow
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720 USA
Tel: +1 978 264 2048
Email: oran@cisco.com


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 24 13:32:31 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18698
	for <avt-archive@ietf.org>; Wed, 24 Nov 2004 13:32:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CX20L-0002iX-Ql
	for avt-archive@ietf.org; Wed, 24 Nov 2004 13:36:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CX1u4-0002iw-AR; Wed, 24 Nov 2004 13:30:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CX1oY-0001XK-VA
	for avt@megatron.ietf.org; Wed, 24 Nov 2004 13:24:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18165
	for <avt@ietf.org>; Wed, 24 Nov 2004 13:24:23 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CX1sT-0002VT-KS for avt@ietf.org; Wed, 24 Nov 2004 13:28:30 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 24 Nov 2004 10:27:21 -0800
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iAOINjAC015973;
	Wed, 24 Nov 2004 10:23:46 -0800 (PST)
Received: from [192.168.0.10] (sjc-vpn4-827.cisco.com [10.21.83.58])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id iAOINict002886;
	Wed, 24 Nov 2004 10:23:44 -0800
In-Reply-To: <8ADEA3FD-3E3C-11D9-A16E-000A95DC10F2@cisco.com>
References: <EF8DFB1B64FF0A43AB00555B8E2717B19F6B3A@aclmsg.corp.audiocodes.com>
	<4.3.2.7.2.20041124092246.00c97668@mira-sjc5-e.cisco.com>
	<8ADEA3FD-3E3C-11D9-A16E-000A95DC10F2@cisco.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <FB0924C4-3E45-11D9-A16E-000A95DC10F2@cisco.com>
Content-Transfer-Encoding: 7bit
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [AVT] RFC 3711 and RTCP
Date: Wed, 24 Nov 2004 10:23:46 -0800
To: Mark Baugher <mbaugher@cisco.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1101320624.711464"; x:"432200"; a:"rsa-sha1"; b:"nofws:5315";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"Lu2AMSZfkd+GZU30wQJL07oEXp8JICntxrsfCZ9urxj5l+s4tav+y7TbTfqKD"
	"HhuhP9E7ihBvcaLaa61LL4tZxXriiF/bguruoD/sbFPIIheR9M1FSqHD01K0f"
	"UBHvmskhyZpgBcS8zlGQPA0UqUmjgHWUh1/RbsgJruTFfJRqc=";
	c:"From: Mark Baugher <mbaugher@cisco.com>";
	c:"Subject: Re: [AVT] RFC 3711 and RTCP";
	c:"Date: Wed, 24 Nov 2004 10:23:46 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7e439b86d3292ef5adf93b694a43a576
Content-Transfer-Encoding: 7bit
Cc: Oren Peleg <OrenP@audiocodes.com>,
        "Michael A. Ramalho" <mramalho@cisco.com>,
        Alan Clark <alan.d.clark@telchemy.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 25eb6223a37c19d53ede858176b14339
Content-Transfer-Encoding: 7bit


On Nov 24, 2004, at 9:16 AM, Mark Baugher wrote:

> It's not possible to selectively encrypt SRTCP packets.

I was wrong about this:  Section 3.4 of  
http://www.ietf.org/rfc/rfc3711.txt describes the E bit, which allows  
selective encryption of SRTP packets.

Mark
> The default is to encrypt SRTCP, but it is a matter of policy.   
> Presumably, SRTCP will be authenticated and not encrypted when  
> monitoring is desired.  I think Alan's plea to implementers should be  
> to ensure that SRTCP encryption is strictly optional.
>
> Mark
> On Nov 24, 2004, at 6:38 AM, Michael A. Ramalho wrote:
>
>> At 07:54 AM 11/24/2004 -0500, Alan Clark wrote:
>>> Hi Oren
>>>
>>> Yes - encryption is intended to provide privacy however this relates
>>> primarily to the voice payloads and to information within RTCP that  
>>> may be
>>> associated with individual users (e.g. SDES).
>>>
>>> SR, RR and XR contain only peformance statistics and there is no  
>>> privacy
>>> consideration that I can think of related to this type of data.
>>>
>>> The message is - encrypt RTP, optionally encrypt RTCP SDES but don't  
>>> encrypt
>>> RTCP SR/RR/XR
>>
>> Hi Alan,
>>
>> I am wondering about implementations utilizing your advise  
>> "optionally encrypt
>> RTCP SDES but don't encrypt RTCP SR/RR/XR".
>>
>> Is there an easy way to tell SRTP to encrypt RTCP SDES, but not RTCP
>> SR/RR/XR? It seems that all the RTCP blocks would otherwise be highly
>> related to each other. For example (quote out of RFC 3611):
>>
>> "XR packets supplement the existing RTCP packets, and may be stacked  
>> with
>> other RTCP packets to form compound RTCP packets [9, Section 6]."
>>
>> Thus, RFC3611 explicitly admits the possibility of (but does not  
>> mandate)
>> the piggybacking all the RTCP-XR block types.
>>
>> RTCP implementations would have to know the SRTP encryption rules to
>> make sure they don't perform piggybacking with SDES ... but could  
>> allow
>> (the more bandwidth efficient) piggybacking on the other RTCP-XR  
>> blocks.
>>
>> This RTCP/SRTP interaction/dependency seems to add a burden to both
>> RTCP and SRTP implementations ... let alone the expressiveness  
>> required
>> to signal your advise in existing SDP/SRTP mechanisms.
>>
>> Are you aware of any implementations that have actually followed your
>> advise above? I rather go into this one with our eyes open ...  
>> developers
>> highly dislike this cross-functional entity dependency (RTCP & SRTP  
>> along
>> with expressing it in SDP/SRTP mechanisms).
>>
>> Regards,
>>
>> Michael Ramalho
>>
>>
>>
>>> Regards
>>>
>>> Alan
>>>
>>> -----Original Message-----
>>> From: Oren Peleg [mailto:OrenP@audiocodes.com]
>>> Sent: Wednesday, November 24, 2004 7:50 AM
>>> To: Alan Clark; avt@ietf.org
>>> Subject: RE: [AVT] RFC 3711 and RTCP
>>>
>>>
>>>
>>> Isnt encryption is to prevent monitoring from the first place?
>>>
>>> -----Original Message-----
>>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
>>> Alan Clark
>>> Sent: Tuesday, November 23, 2004 5:42 PM
>>> To: avt@ietf.org
>>> Subject: [AVT] RFC 3711 and RTCP
>>>
>>>
>>> >From the flurry of discussion on RFC3711 it looks as if there is
>>> considerable interest in SRTP implementation.  I'd like to add a  
>>> request
>>> to
>>> SRTP implementors with regard to manageability.
>>>
>>> RTCP SR, RR and more particularly XR (e.g. VoIP Metrics report block)
>>> contain useful information for network monitoring, and are often  
>>> used by
>>> probes and analyzers to support problem diagnosis.  RFC3711 allows  
>>> the
>>> selective encryption of RTCP payloads and hence I would strongly
>>> recomment
>>> that RFC3711 implementors DO NOT encrypt RTCP SR, RR and XR payloads  
>>> as
>>> this
>>> adversely impacts manageability.
>>>
>>> Regards
>>>
>>> Alan Clark
>>> Telchemy
>>>
>>>
>>> _______________________________________________
>>> Audio/Video Transport Working Group
>>> avt@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/avt
>>>
>>> ********************************************************************* 
>>> *******
>>> ********************************
>>> This email and any files transmitted with it are confidential  
>>> material.
>>> They are intended solely for the use of the designated individual or  
>>> entity
>>> to whom they are addressed.
>>> If the reader of this message is not the intended recipient,
>>> you are hereby notified that any dissemination,use,
>>> distribution or copying of this communication is strictly prohibited  
>>> and may
>>> be unlawful.
>>>
>>> If you have received this email in error please notify
>>> postmaster@audiocodes.com and permanently delete the e-mail and  
>>> files.
>>>
>>>
>>> ********************************************************************* 
>>> *******
>>> *******************************
>>>
>>>
>>> _______________________________________________
>>> Audio/Video Transport Working Group
>>> avt@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/avt
>>
>>
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www1.ietf.org/mailman/listinfo/avt
>>
>


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 24 13:45:06 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19342
	for <avt-archive@ietf.org>; Wed, 24 Nov 2004 13:45:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CX2CV-000312-48
	for avt-archive@ietf.org; Wed, 24 Nov 2004 13:49:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CX24w-0005pz-7n; Wed, 24 Nov 2004 13:41:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CX1xg-0004JE-1Q
	for avt@megatron.ietf.org; Wed, 24 Nov 2004 13:33:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18764
	for <avt@ietf.org>; Wed, 24 Nov 2004 13:33:48 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CX21a-0002jU-NX for avt@ietf.org; Wed, 24 Nov 2004 13:37:55 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 24 Nov 2004 10:36:46 -0800
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iAOIXHAC026012;
	Wed, 24 Nov 2004 10:33:18 -0800 (PST)
Received: from [192.168.0.10] (sjc-vpn4-827.cisco.com [10.21.83.58])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id iAOIXBif002966;
	Wed, 24 Nov 2004 10:33:11 -0800
In-Reply-To: <62B7EEEA-3E43-11D9-8CD3-000A95C73842@cisco.com>
References: <BGEKJNNFCPJKLLMMDMELEEJPFLAA.alan.d.clark@telchemy.com>
	<62B7EEEA-3E43-11D9-8CD3-000A95C73842@cisco.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <4D5C4E83-3E47-11D9-A16E-000A95DC10F2@cisco.com>
Content-Transfer-Encoding: 7bit
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [AVT] RFC 3711 and RTCP
Date: Wed, 24 Nov 2004 10:33:14 -0800
To: David R Oran <oran@cisco.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1101321191.830589"; x:"432200"; a:"rsa-sha1"; b:"nofws:7670";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"V21xKvHfVuITwl2UqGsZaeDDV2Ow0gb4NA8SIvnXV2ZPyHCk2DZK7NNzszEJR"
	"/zKg7Gp/16eHc3m24fzV/uu2qFZ8mrh0DVVin/Usk1mSlC3b3ceExLrQfJwDH"
	"SeRu08vqGpKZws1DLjiBxJMEo8Xc43eMkOxot8esPfpCNSf8k=";
	c:"From: Mark Baugher <mbaugher@cisco.com>";
	c:"Subject: Re: [AVT] RFC 3711 and RTCP";
	c:"Date: Wed, 24 Nov 2004 10:33:14 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7698d1420ecbbce1995432e99bb6d1a1
Content-Transfer-Encoding: 7bit
Cc: Cullen Jennings <fluffy@cisco.com>, Oren Peleg <OrenP@audiocodes.com>,
        "Michael A. Ramalho" <mramalho@cisco.com>,
        Alan Clark <alan.d.clark@telchemy.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 17bdfcaea25d1444baef0e24abc38874
Content-Transfer-Encoding: 7bit


On Nov 24, 2004, at 10:05 AM, David R Oran wrote:

>
> On Nov 24, 2004, at 12:23 PM, Alan Clark wrote:
>
>>
>> Michael
>>
>> I don't see why this would be a problem unless you included SDES and  
>> (SR or
>> RR or XR) in the same RTCP packet.  SRTP (at least the protocol) is
>> apparently able to decided on a packet by packet basis whether to  
>> encrypt
>> RTCP - hopefully SRTP implementations also permit this.
>>
> Sure, they can do this. But remember offer-answer. How does a receiver  
> communicate such a granular policy to the transmitter? Right now if  
> can say whether to auth or auth+encrypt RTP, and auth or auth+encrypt  
> RTCP. There's no way to say auth+encrypt SDES but only auth SR/XR etc.

Seems to me that this is a problem with SDP security descriptions.   
That problem might be there because we forgot about the E bit.  This  
seems very messy for the reason you mention above - granularity.  I  
don't think that we want to negotiate the encryption policy for each  
type SDP message, which is a problem with something like the E bit.

Mark
>
>
>> Logically I'd send SDES on its own at the start of a call to provide  
>> some
>> user info, but would not send SR/RR/XR until at least 8-10 seconds  
>> into the
>> call as I need some time to gather statistics to report.
> That's not exactly what the RTP specs say. RTCP timers don't have this  
> kind of policy today. In fact, there are porposals on the table to use  
> RTCP for early feedback to assess reception quality on some initial  
> packets - e.g. the RTP-noop proposal. In any event that has no bearing  
> on the present discussion.
>
>> After the
>> start-of-call exchange there would appear to be minimal need to  
>> include
>> SDES. I'm sure we could construct some scenarios in which you "may"  
>> need to
>> include SDES with SR/RR/XR however the vast majority of cases would  
>> either
>> need only a single initial exchange or may not need SDES at all.
>>
> Any time you change SSRC you potentially need to send SDES.
> That said, I still don't see what bearing this has on the discussion  
> about whether we need the complexity of encrypting some RTCP packets  
> and not others for a single session.
>
> It's a tradeoff between extra complexity+less privacy versus allowing  
> snoopers to gather RTCP stats.
>
> Dave.
>
>> Regards
>>
>> Alan
>>
>>
>>
>> -----Original Message-----
>> From: Michael A. Ramalho [mailto:mramalho@cisco.com]
>> Sent: Wednesday, November 24, 2004 9:39 AM
>> To: Alan Clark
>> Cc: Oren Peleg; avt@ietf.org
>> Subject: RE: [AVT] RFC 3711 and RTCP
>>
>>
>> At 07:54 AM 11/24/2004 -0500, Alan Clark wrote:
>>> Hi Oren
>>>
>>> Yes - encryption is intended to provide privacy however this relates
>>> primarily to the voice payloads and to information within RTCP that  
>>> may be
>>> associated with individual users (e.g. SDES).
>>>
>>> SR, RR and XR contain only peformance statistics and there is no  
>>> privacy
>>> consideration that I can think of related to this type of data.
>>>
>>> The message is - encrypt RTP, optionally encrypt RTCP SDES but don't
>> encrypt
>>> RTCP SR/RR/XR
>>
>> Hi Alan,
>>
>> I am wondering about implementations utilizing your advise "optionally
>> encrypt
>> RTCP SDES but don't encrypt RTCP SR/RR/XR".
>>
>> Is there an easy way to tell SRTP to encrypt RTCP SDES, but not RTCP
>> SR/RR/XR? It seems that all the RTCP blocks would otherwise be highly
>> related to each other. For example (quote out of RFC 3611):
>>
>> "XR packets supplement the existing RTCP packets, and may be stacked  
>> with
>> other RTCP packets to form compound RTCP packets [9, Section 6]."
>>
>> Thus, RFC3611 explicitly admits the possibility of (but does not  
>> mandate)
>> the piggybacking all the RTCP-XR block types.
>>
>> RTCP implementations would have to know the SRTP encryption rules to
>> make sure they don't perform piggybacking with SDES ... but could  
>> allow
>> (the more bandwidth efficient) piggybacking on the other RTCP-XR  
>> blocks.
>>
>> This RTCP/SRTP interaction/dependency seems to add a burden to both
>> RTCP and SRTP implementations ... let alone the expressiveness  
>> required
>> to signal your advise in existing SDP/SRTP mechanisms.
>>
>> Are you aware of any implementations that have actually followed your
>> advise above? I rather go into this one with our eyes open ...  
>> developers
>> highly dislike this cross-functional entity dependency (RTCP & SRTP  
>> along
>> with expressing it in SDP/SRTP mechanisms).
>>
>> Regards,
>>
>> Michael Ramalho
>>
>>
>>
>>> Regards
>>>
>>> Alan
>>>
>>> -----Original Message-----
>>> From: Oren Peleg [mailto:OrenP@audiocodes.com]
>>> Sent: Wednesday, November 24, 2004 7:50 AM
>>> To: Alan Clark; avt@ietf.org
>>> Subject: RE: [AVT] RFC 3711 and RTCP
>>>
>>>
>>>
>>> Isnt encryption is to prevent monitoring from the first place?
>>>
>>> -----Original Message-----
>>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
>>> Alan Clark
>>> Sent: Tuesday, November 23, 2004 5:42 PM
>>> To: avt@ietf.org
>>> Subject: [AVT] RFC 3711 and RTCP
>>>
>>>
>>>> From the flurry of discussion on RFC3711 it looks as if there is
>>> considerable interest in SRTP implementation.  I'd like to add a  
>>> request
>>> to
>>> SRTP implementors with regard to manageability.
>>>
>>> RTCP SR, RR and more particularly XR (e.g. VoIP Metrics report block)
>>> contain useful information for network monitoring, and are often  
>>> used by
>>> probes and analyzers to support problem diagnosis.  RFC3711 allows  
>>> the
>>> selective encryption of RTCP payloads and hence I would strongly
>>> recomment
>>> that RFC3711 implementors DO NOT encrypt RTCP SR, RR and XR payloads  
>>> as
>>> this
>>> adversely impacts manageability.
>>>
>>> Regards
>>>
>>> Alan Clark
>>> Telchemy
>>>
>>>
>>> _______________________________________________
>>> Audio/Video Transport Working Group
>>> avt@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/avt
>>>
>>> ********************************************************************* 
>>> ******
>> *
>>> ********************************
>>> This email and any files transmitted with it are confidential  
>>> material.
>>> They are intended solely for the use of the designated individual or  
>>> entity
>>> to whom they are addressed.
>>> If the reader of this message is not the intended recipient,
>>> you are hereby notified that any dissemination,use,
>>> distribution or copying of this communication is strictly prohibited  
>>> and
>> may
>>> be unlawful.
>>>
>>> If you have received this email in error please notify
>>> postmaster@audiocodes.com and permanently delete the e-mail and  
>>> files.
>>>
>>>
>>> ********************************************************************* 
>>> ******
>> *
>>> *******************************
>>>
>>>
>>> _______________________________________________
>>> Audio/Video Transport Working Group
>>> avt@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/avt
>>
>>
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www1.ietf.org/mailman/listinfo/avt
>>
> David R. Oran
> Cisco Fellow
> Cisco Systems
> 7 Ladyslipper Lane
> Acton, MA 01720 USA
> Tel: +1 978 264 2048
> Email: oran@cisco.com
>
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 24 14:04:36 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20465
	for <avt-archive@ietf.org>; Wed, 24 Nov 2004 14:04:36 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CX2VN-0003To-FW
	for avt-archive@ietf.org; Wed, 24 Nov 2004 14:08:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CX2QD-0000iV-AG; Wed, 24 Nov 2004 14:03:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CX2LO-0008Fj-3D
	for avt@megatron.ietf.org; Wed, 24 Nov 2004 13:58:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20143
	for <avt@ietf.org>; Wed, 24 Nov 2004 13:58:20 -0500 (EST)
Received: from mx.cbeyond.net ([66.180.96.58] helo=mx.cbeyond.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CX2PI-0003LM-GB
	for avt@ietf.org; Wed, 24 Nov 2004 14:02:25 -0500
Received: from [64.238.103.215] (port=1412 helo=telws116)
	by mx.cbeyond.com with asmtp (Exim 4.34)
	id 1CX2LK-0002R9-UB; Wed, 24 Nov 2004 13:58:19 -0500
From: "Alan Clark" <alan.d.clark@telchemy.com>
To: "Mark Baugher" <mbaugher@cisco.com>, "David R Oran" <oran@cisco.com>
Subject: RE: [AVT] RFC 3711 and RTCP
Date: Wed, 24 Nov 2004 13:58:18 -0500
Message-ID: <BGEKJNNFCPJKLLMMDMELOEKEFLAA.alan.d.clark@telchemy.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
In-Reply-To: <4D5C4E83-3E47-11D9-A16E-000A95DC10F2@cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
X-Spam-Score: 0.2 (/)
X-Scan-Signature: e5bfa71b340354e384155def5e70b13b
Content-Transfer-Encoding: 7bit
Cc: Cullen Jennings <fluffy@cisco.com>, Oren Peleg <OrenP@audiocodes.com>,
        "Michael A. Ramalho" <mramalho@cisco.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: ba0d4c5f57f7c289496fce758bbf4798
Content-Transfer-Encoding: 7bit


If the use of encryption in SRTCP is signalled by an explicit (E) bit in the
SRTCP header then perhaps the sender could autonomously decide whether it
wants to encrypt?  Presumably since the sender is in the best position to
decide if the data is sensitive then this would be ok - and the receiver is
able to just look at the E bit and hence recognize that decryption is
needed.

Alan

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]On Behalf Of
Mark Baugher
Sent: Wednesday, November 24, 2004 1:33 PM
To: David R Oran
Cc: Cullen Jennings; Oren Peleg; Michael A. Ramalho; Alan Clark;
avt@ietf.org
Subject: Re: [AVT] RFC 3711 and RTCP



On Nov 24, 2004, at 10:05 AM, David R Oran wrote:

>
> On Nov 24, 2004, at 12:23 PM, Alan Clark wrote:
>
>>
>> Michael
>>
>> I don't see why this would be a problem unless you included SDES and
>> (SR or
>> RR or XR) in the same RTCP packet.  SRTP (at least the protocol) is
>> apparently able to decided on a packet by packet basis whether to
>> encrypt
>> RTCP - hopefully SRTP implementations also permit this.
>>
> Sure, they can do this. But remember offer-answer. How does a receiver
> communicate such a granular policy to the transmitter? Right now if
> can say whether to auth or auth+encrypt RTP, and auth or auth+encrypt
> RTCP. There's no way to say auth+encrypt SDES but only auth SR/XR etc.

Seems to me that this is a problem with SDP security descriptions.
That problem might be there because we forgot about the E bit.  This
seems very messy for the reason you mention above - granularity.  I
don't think that we want to negotiate the encryption policy for each
type SDP message, which is a problem with something like the E bit.

Mark
>
>
>> Logically I'd send SDES on its own at the start of a call to provide
>> some
>> user info, but would not send SR/RR/XR until at least 8-10 seconds
>> into the
>> call as I need some time to gather statistics to report.
> That's not exactly what the RTP specs say. RTCP timers don't have this
> kind of policy today. In fact, there are porposals on the table to use
> RTCP for early feedback to assess reception quality on some initial
> packets - e.g. the RTP-noop proposal. In any event that has no bearing
> on the present discussion.
>
>> After the
>> start-of-call exchange there would appear to be minimal need to
>> include
>> SDES. I'm sure we could construct some scenarios in which you "may"
>> need to
>> include SDES with SR/RR/XR however the vast majority of cases would
>> either
>> need only a single initial exchange or may not need SDES at all.
>>
> Any time you change SSRC you potentially need to send SDES.
> That said, I still don't see what bearing this has on the discussion
> about whether we need the complexity of encrypting some RTCP packets
> and not others for a single session.
>
> It's a tradeoff between extra complexity+less privacy versus allowing
> snoopers to gather RTCP stats.
>
> Dave.
>
>> Regards
>>
>> Alan
>>
>>
>>
>> -----Original Message-----
>> From: Michael A. Ramalho [mailto:mramalho@cisco.com]
>> Sent: Wednesday, November 24, 2004 9:39 AM
>> To: Alan Clark
>> Cc: Oren Peleg; avt@ietf.org
>> Subject: RE: [AVT] RFC 3711 and RTCP
>>
>>
>> At 07:54 AM 11/24/2004 -0500, Alan Clark wrote:
>>> Hi Oren
>>>
>>> Yes - encryption is intended to provide privacy however this relates
>>> primarily to the voice payloads and to information within RTCP that
>>> may be
>>> associated with individual users (e.g. SDES).
>>>
>>> SR, RR and XR contain only peformance statistics and there is no
>>> privacy
>>> consideration that I can think of related to this type of data.
>>>
>>> The message is - encrypt RTP, optionally encrypt RTCP SDES but don't
>> encrypt
>>> RTCP SR/RR/XR
>>
>> Hi Alan,
>>
>> I am wondering about implementations utilizing your advise "optionally
>> encrypt
>> RTCP SDES but don't encrypt RTCP SR/RR/XR".
>>
>> Is there an easy way to tell SRTP to encrypt RTCP SDES, but not RTCP
>> SR/RR/XR? It seems that all the RTCP blocks would otherwise be highly
>> related to each other. For example (quote out of RFC 3611):
>>
>> "XR packets supplement the existing RTCP packets, and may be stacked
>> with
>> other RTCP packets to form compound RTCP packets [9, Section 6]."
>>
>> Thus, RFC3611 explicitly admits the possibility of (but does not
>> mandate)
>> the piggybacking all the RTCP-XR block types.
>>
>> RTCP implementations would have to know the SRTP encryption rules to
>> make sure they don't perform piggybacking with SDES ... but could
>> allow
>> (the more bandwidth efficient) piggybacking on the other RTCP-XR
>> blocks.
>>
>> This RTCP/SRTP interaction/dependency seems to add a burden to both
>> RTCP and SRTP implementations ... let alone the expressiveness
>> required
>> to signal your advise in existing SDP/SRTP mechanisms.
>>
>> Are you aware of any implementations that have actually followed your
>> advise above? I rather go into this one with our eyes open ...
>> developers
>> highly dislike this cross-functional entity dependency (RTCP & SRTP
>> along
>> with expressing it in SDP/SRTP mechanisms).
>>
>> Regards,
>>
>> Michael Ramalho
>>
>>
>>
>>> Regards
>>>
>>> Alan
>>>
>>> -----Original Message-----
>>> From: Oren Peleg [mailto:OrenP@audiocodes.com]
>>> Sent: Wednesday, November 24, 2004 7:50 AM
>>> To: Alan Clark; avt@ietf.org
>>> Subject: RE: [AVT] RFC 3711 and RTCP
>>>
>>>
>>>
>>> Isnt encryption is to prevent monitoring from the first place?
>>>
>>> -----Original Message-----
>>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
>>> Alan Clark
>>> Sent: Tuesday, November 23, 2004 5:42 PM
>>> To: avt@ietf.org
>>> Subject: [AVT] RFC 3711 and RTCP
>>>
>>>
>>>> From the flurry of discussion on RFC3711 it looks as if there is
>>> considerable interest in SRTP implementation.  I'd like to add a
>>> request
>>> to
>>> SRTP implementors with regard to manageability.
>>>
>>> RTCP SR, RR and more particularly XR (e.g. VoIP Metrics report block)
>>> contain useful information for network monitoring, and are often
>>> used by
>>> probes and analyzers to support problem diagnosis.  RFC3711 allows
>>> the
>>> selective encryption of RTCP payloads and hence I would strongly
>>> recomment
>>> that RFC3711 implementors DO NOT encrypt RTCP SR, RR and XR payloads
>>> as
>>> this
>>> adversely impacts manageability.
>>>
>>> Regards
>>>
>>> Alan Clark
>>> Telchemy
>>>
>>>
>>> _______________________________________________
>>> Audio/Video Transport Working Group
>>> avt@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/avt
>>>
>>> *********************************************************************
>>> ******
>> *
>>> ********************************
>>> This email and any files transmitted with it are confidential
>>> material.
>>> They are intended solely for the use of the designated individual or
>>> entity
>>> to whom they are addressed.
>>> If the reader of this message is not the intended recipient,
>>> you are hereby notified that any dissemination,use,
>>> distribution or copying of this communication is strictly prohibited
>>> and
>> may
>>> be unlawful.
>>>
>>> If you have received this email in error please notify
>>> postmaster@audiocodes.com and permanently delete the e-mail and
>>> files.
>>>
>>>
>>> *********************************************************************
>>> ******
>> *
>>> *******************************
>>>
>>>
>>> _______________________________________________
>>> Audio/Video Transport Working Group
>>> avt@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/avt
>>
>>
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www1.ietf.org/mailman/listinfo/avt
>>
> David R. Oran
> Cisco Fellow
> Cisco Systems
> 7 Ladyslipper Lane
> Acton, MA 01720 USA
> Tel: +1 978 264 2048
> Email: oran@cisco.com
>
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 24 14:50:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23275
	for <avt-archive@ietf.org>; Wed, 24 Nov 2004 14:50:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CX3DZ-0004UL-N2
	for avt-archive@ietf.org; Wed, 24 Nov 2004 14:54:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CX38G-0002WA-Ht; Wed, 24 Nov 2004 14:48:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CX32N-0000tc-1x
	for avt@megatron.ietf.org; Wed, 24 Nov 2004 14:42:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22801
	for <avt@ietf.org>; Wed, 24 Nov 2004 14:42:45 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CX36I-0004JE-6A for avt@ietf.org; Wed, 24 Nov 2004 14:46:50 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 24 Nov 2004 11:47:22 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iAOJgBUk006291;
	Wed, 24 Nov 2004 11:42:11 -0800 (PST)
Received: from [192.168.0.10] (sjc-vpn4-827.cisco.com [10.21.83.58])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id iAOJg5Os003612;
	Wed, 24 Nov 2004 11:42:05 -0800
In-Reply-To: <BGEKJNNFCPJKLLMMDMELOEKEFLAA.alan.d.clark@telchemy.com>
References: <BGEKJNNFCPJKLLMMDMELOEKEFLAA.alan.d.clark@telchemy.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <ED8165A4-3E50-11D9-A16E-000A95DC10F2@cisco.com>
Content-Transfer-Encoding: 7bit
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [AVT] RFC 3711 and RTCP
Date: Wed, 24 Nov 2004 11:42:08 -0800
To: "Alan Clark" <alan.d.clark@telchemy.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1101325325.875438"; x:"432200"; a:"rsa-sha1"; b:"nofws:10257";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"bqStNfzMRhdxm9oTD1lIzvHduj3hJyZMa1CXHHgufk6S84Y7Gh6KD7lBFXbBi"
	"aPZqGpt2e9+MemEfiUPYrYo2Eq1eeTWrTGHa5pOfCsoDGhj6NF8YdPDsen41y"
	"95I+lX4w8mmp8tqlH7wgkuHUMBexILIUG9Aw7uH88z8p4zWKQ=";
	c:"From: Mark Baugher <mbaugher@cisco.com>";
	c:"Subject: Re: [AVT] RFC 3711 and RTCP";
	c:"Date: Wed, 24 Nov 2004 11:42:08 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 52f402fbded34a6df606921f56b8bdd8
Content-Transfer-Encoding: 7bit
Cc: Cullen Jennings <fluffy@cisco.com>, Oren Peleg <OrenP@audiocodes.com>,
        David R Oran <oran@cisco.com>, avt@ietf.org,
        "Michael A. Ramalho" <mramalho@cisco.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: abda3837e791065a13ac6f11cf8e625a
Content-Transfer-Encoding: 7bit

So, when the sender and receiver agree to encrypt SRTCP, this would mean
only that some SRTCP messages would be encrypted and the sender would
decide which ones to encrypt?  My personal opinion is that this is not
secure because it is unpredictable to the receiver, which may have a
policy that all messages related to its session be encrypted.

I can think of a few potential approaches to this problem.

1. Let individual SRTCP messages or a bundle of SRTCP messages
be signaled to be unencrypted when SRTCP encryption is used.

2. Make a blanket policy that the sender determine what
to selectively encrypt, as you suggest.

3. Define the policy of what to selectively encrypt in
the particular specification.  In other words, a document could
re-define the signaling of SRTCP encryption according to its
needs.  The specification of foo, therefore, could define a new
parameter such as foo_ENCRYPTED_SRTCP to be used in place of
ENCRYPTED_SRTCP.  The foo document would define what gets
encrypted and what does not get encrypted as per its needs.

I commented on #2 already.  I don't like #1 because of its signaling
complexity.  I like #3 because it limits the complexity to the
specific needs of an application.  #1 would be more efficient than
#3 if lots of applications had their own specific needs for
selective encryption of SRTCP message.  But I don't think this is
the case.

Mark

On Nov 24, 2004, at 10:58 AM, Alan Clark wrote:

>
> If the use of encryption in SRTCP is signalled by an explicit (E) bit  
> in the
> SRTCP header then perhaps the sender could autonomously decide whether  
> it
> wants to encrypt?  Presumably since the sender is in the best position  
> to
> decide if the data is sensitive then this would be ok - and the  
> receiver is
> able to just look at the E bit and hence recognize that decryption is
> needed.
>
> Alan
>
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]On Behalf Of
> Mark Baugher
> Sent: Wednesday, November 24, 2004 1:33 PM
> To: David R Oran
> Cc: Cullen Jennings; Oren Peleg; Michael A. Ramalho; Alan Clark;
> avt@ietf.org
> Subject: Re: [AVT] RFC 3711 and RTCP
>
>
>
> On Nov 24, 2004, at 10:05 AM, David R Oran wrote:
>
>>
>> On Nov 24, 2004, at 12:23 PM, Alan Clark wrote:
>>
>>>
>>> Michael
>>>
>>> I don't see why this would be a problem unless you included SDES and
>>> (SR or
>>> RR or XR) in the same RTCP packet.  SRTP (at least the protocol) is
>>> apparently able to decided on a packet by packet basis whether to
>>> encrypt
>>> RTCP - hopefully SRTP implementations also permit this.
>>>
>> Sure, they can do this. But remember offer-answer. How does a receiver
>> communicate such a granular policy to the transmitter? Right now if
>> can say whether to auth or auth+encrypt RTP, and auth or auth+encrypt
>> RTCP. There's no way to say auth+encrypt SDES but only auth SR/XR etc.
>
> Seems to me that this is a problem with SDP security descriptions.
> That problem might be there because we forgot about the E bit.  This
> seems very messy for the reason you mention above - granularity.  I
> don't think that we want to negotiate the encryption policy for each
> type SDP message, which is a problem with something like the E bit.
>
> Mark
>>
>>
>>> Logically I'd send SDES on its own at the start of a call to provide
>>> some
>>> user info, but would not send SR/RR/XR until at least 8-10 seconds
>>> into the
>>> call as I need some time to gather statistics to report.
>> That's not exactly what the RTP specs say. RTCP timers don't have this
>> kind of policy today. In fact, there are porposals on the table to use
>> RTCP for early feedback to assess reception quality on some initial
>> packets - e.g. the RTP-noop proposal. In any event that has no bearing
>> on the present discussion.
>>
>>> After the
>>> start-of-call exchange there would appear to be minimal need to
>>> include
>>> SDES. I'm sure we could construct some scenarios in which you "may"
>>> need to
>>> include SDES with SR/RR/XR however the vast majority of cases would
>>> either
>>> need only a single initial exchange or may not need SDES at all.
>>>
>> Any time you change SSRC you potentially need to send SDES.
>> That said, I still don't see what bearing this has on the discussion
>> about whether we need the complexity of encrypting some RTCP packets
>> and not others for a single session.
>>
>> It's a tradeoff between extra complexity+less privacy versus allowing
>> snoopers to gather RTCP stats.
>>
>> Dave.
>>
>>> Regards
>>>
>>> Alan
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: Michael A. Ramalho [mailto:mramalho@cisco.com]
>>> Sent: Wednesday, November 24, 2004 9:39 AM
>>> To: Alan Clark
>>> Cc: Oren Peleg; avt@ietf.org
>>> Subject: RE: [AVT] RFC 3711 and RTCP
>>>
>>>
>>> At 07:54 AM 11/24/2004 -0500, Alan Clark wrote:
>>>> Hi Oren
>>>>
>>>> Yes - encryption is intended to provide privacy however this relates
>>>> primarily to the voice payloads and to information within RTCP that
>>>> may be
>>>> associated with individual users (e.g. SDES).
>>>>
>>>> SR, RR and XR contain only peformance statistics and there is no
>>>> privacy
>>>> consideration that I can think of related to this type of data.
>>>>
>>>> The message is - encrypt RTP, optionally encrypt RTCP SDES but don't
>>> encrypt
>>>> RTCP SR/RR/XR
>>>
>>> Hi Alan,
>>>
>>> I am wondering about implementations utilizing your advise  
>>> "optionally
>>> encrypt
>>> RTCP SDES but don't encrypt RTCP SR/RR/XR".
>>>
>>> Is there an easy way to tell SRTP to encrypt RTCP SDES, but not RTCP
>>> SR/RR/XR? It seems that all the RTCP blocks would otherwise be highly
>>> related to each other. For example (quote out of RFC 3611):
>>>
>>> "XR packets supplement the existing RTCP packets, and may be stacked
>>> with
>>> other RTCP packets to form compound RTCP packets [9, Section 6]."
>>>
>>> Thus, RFC3611 explicitly admits the possibility of (but does not
>>> mandate)
>>> the piggybacking all the RTCP-XR block types.
>>>
>>> RTCP implementations would have to know the SRTP encryption rules to
>>> make sure they don't perform piggybacking with SDES ... but could
>>> allow
>>> (the more bandwidth efficient) piggybacking on the other RTCP-XR
>>> blocks.
>>>
>>> This RTCP/SRTP interaction/dependency seems to add a burden to both
>>> RTCP and SRTP implementations ... let alone the expressiveness
>>> required
>>> to signal your advise in existing SDP/SRTP mechanisms.
>>>
>>> Are you aware of any implementations that have actually followed your
>>> advise above? I rather go into this one with our eyes open ...
>>> developers
>>> highly dislike this cross-functional entity dependency (RTCP & SRTP
>>> along
>>> with expressing it in SDP/SRTP mechanisms).
>>>
>>> Regards,
>>>
>>> Michael Ramalho
>>>
>>>
>>>
>>>> Regards
>>>>
>>>> Alan
>>>>
>>>> -----Original Message-----
>>>> From: Oren Peleg [mailto:OrenP@audiocodes.com]
>>>> Sent: Wednesday, November 24, 2004 7:50 AM
>>>> To: Alan Clark; avt@ietf.org
>>>> Subject: RE: [AVT] RFC 3711 and RTCP
>>>>
>>>>
>>>>
>>>> Isnt encryption is to prevent monitoring from the first place?
>>>>
>>>> -----Original Message-----
>>>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf  
>>>> Of
>>>> Alan Clark
>>>> Sent: Tuesday, November 23, 2004 5:42 PM
>>>> To: avt@ietf.org
>>>> Subject: [AVT] RFC 3711 and RTCP
>>>>
>>>>
>>>>> From the flurry of discussion on RFC3711 it looks as if there is
>>>> considerable interest in SRTP implementation.  I'd like to add a
>>>> request
>>>> to
>>>> SRTP implementors with regard to manageability.
>>>>
>>>> RTCP SR, RR and more particularly XR (e.g. VoIP Metrics report  
>>>> block)
>>>> contain useful information for network monitoring, and are often
>>>> used by
>>>> probes and analyzers to support problem diagnosis.  RFC3711 allows
>>>> the
>>>> selective encryption of RTCP payloads and hence I would strongly
>>>> recomment
>>>> that RFC3711 implementors DO NOT encrypt RTCP SR, RR and XR payloads
>>>> as
>>>> this
>>>> adversely impacts manageability.
>>>>
>>>> Regards
>>>>
>>>> Alan Clark
>>>> Telchemy
>>>>
>>>>
>>>> _______________________________________________
>>>> Audio/Video Transport Working Group
>>>> avt@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/avt
>>>>
>>>> ******************************************************************** 
>>>> *
>>>> ******
>>> *
>>>> ********************************
>>>> This email and any files transmitted with it are confidential
>>>> material.
>>>> They are intended solely for the use of the designated individual or
>>>> entity
>>>> to whom they are addressed.
>>>> If the reader of this message is not the intended recipient,
>>>> you are hereby notified that any dissemination,use,
>>>> distribution or copying of this communication is strictly prohibited
>>>> and
>>> may
>>>> be unlawful.
>>>>
>>>> If you have received this email in error please notify
>>>> postmaster@audiocodes.com and permanently delete the e-mail and
>>>> files.
>>>>
>>>>
>>>> ******************************************************************** 
>>>> *
>>>> ******
>>> *
>>>> *******************************
>>>>
>>>>
>>>> _______________________________________________
>>>> Audio/Video Transport Working Group
>>>> avt@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/avt
>>>
>>>
>>> _______________________________________________
>>> Audio/Video Transport Working Group
>>> avt@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/avt
>>>
>> David R. Oran
>> Cisco Fellow
>> Cisco Systems
>> 7 Ladyslipper Lane
>> Acton, MA 01720 USA
>> Tel: +1 978 264 2048
>> Email: oran@cisco.com
>>
>>
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www1.ietf.org/mailman/listinfo/avt
>>
>
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 24 15:31:51 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28825
	for <avt-archive@ietf.org>; Wed, 24 Nov 2004 15:31:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CX3rp-0005cR-OE
	for avt-archive@ietf.org; Wed, 24 Nov 2004 15:35:57 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CX3kO-0002L7-VJ; Wed, 24 Nov 2004 15:28:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CX3iZ-00019k-OG
	for avt@megatron.ietf.org; Wed, 24 Nov 2004 15:26:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28085
	for <avt@ietf.org>; Wed, 24 Nov 2004 15:26:21 -0500 (EST)
Received: from tiere.net.avaya.com ([198.152.12.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CX3mV-0005U9-Ko
	for avt@ietf.org; Wed, 24 Nov 2004 15:30:28 -0500
Received: from tiere.net.avaya.com (localhost [127.0.0.1])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	iAOKOQZ4016164
	for <avt@ietf.org>; Wed, 24 Nov 2004 15:24:27 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	iAOKMaZ4014183
	for <avt@ietf.org>; Wed, 24 Nov 2004 15:23:12 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] RFC 3711 and RTCP
Date: Wed, 24 Nov 2004 22:22:35 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F038A9F56@is0004avexu1.global.avaya.com>
Thread-Topic: [AVT] RFC 3711 and RTCP
Thread-Index: AcTRddZ8r8Lp+QiSRNibQJ7fv7/dcAA6wQQg
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "Alan Clark" <alan.d.clark@telchemy.com>, <avt@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: quoted-printable
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: quoted-printable

Alan,

I anticipated this problem in some on my previous comments about placing =
monitoring probes on the RTCP XR path as a media monitoring strategy. =
The current discussion is useful, and may lead to some solutions like =
selective signaling encryption. It still may be the case that running =
non-encrypted signaling of any type may be un-acceptable in some =
environments. The need for manageability and specifically media =
monitoring is still here, even in such security sensitive deployments. I =
would like to point to the fact that there are other options to for =
media monitoring even if all RTCP traffic must be encrypted end-to-end:

1. Implement the RTCP XR MIB in the endpoints and collect the media =
monitoring information using SNMP. Certainly this type of solution may =
have scalability problems in larger installations
2. Define a set of RTCP XR extensions to RAQMON, and have the IP phones =
report the RTCP XR information using RAQMON PDUs to collectors. This =
solution seems to be scalable and avoid the privacy problems of =
non-encrypted RTCP XR traffic=20

Regards,

Dan



> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]On=20
> Behalf Of Alan Clark
> Sent: 23 November, 2004 5:42 PM
> To: avt@ietf.org
> Subject: [AVT] RFC 3711 and RTCP
>=20
>=20
>=20
> >From the flurry of discussion on RFC3711 it looks as if there is
> considerable interest in SRTP implementation.  I'd like to=20
> add a request to
> SRTP implementors with regard to manageability.
>=20
> RTCP SR, RR and more particularly XR (e.g. VoIP Metrics report block)
> contain useful information for network monitoring, and are=20
> often used by
> probes and analyzers to support problem diagnosis.  RFC3711 allows the
> selective encryption of RTCP payloads and hence I would=20
> strongly recomment
> that RFC3711 implementors DO NOT encrypt RTCP SR, RR and XR=20
> payloads as this
> adversely impacts manageability.
>=20
> Regards
>=20
> Alan Clark
> Telchemy
>=20
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>=20

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 24 17:39:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11149
	for <avt-archive@ietf.org>; Wed, 24 Nov 2004 17:39:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CX5rA-0000C1-DL
	for avt-archive@ietf.org; Wed, 24 Nov 2004 17:43:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CX5lL-0006dm-0s; Wed, 24 Nov 2004 17:37:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CX5hp-0005rJ-Vf
	for avt@megatron.ietf.org; Wed, 24 Nov 2004 17:33:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10847
	for <avt@ietf.org>; Wed, 24 Nov 2004 17:33:43 -0500 (EST)
Received: from mx.cbeyond.net ([66.180.96.58] helo=mx.cbeyond.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CX5lm-00005u-Ke
	for avt@ietf.org; Wed, 24 Nov 2004 17:37:51 -0500
Received: from [64.238.103.215] (port=1732 helo=telws116)
	by mx.cbeyond.com with asmtp (Exim 4.34)
	id 1CX5ho-00026X-41; Wed, 24 Nov 2004 17:33:44 -0500
From: "Alan Clark" <alan.d.clark@telchemy.com>
To: "Mark Baugher" <mbaugher@cisco.com>
Subject: RE: [AVT] RFC 3711 and RTCP
Date: Wed, 24 Nov 2004 17:33:42 -0500
Message-ID: <BGEKJNNFCPJKLLMMDMELIEKNFLAA.alan.d.clark@telchemy.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
In-Reply-To: <ED8165A4-3E50-11D9-A16E-000A95DC10F2@cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 32a65c0bf5eb4ec26489239c7cdd0636
Content-Transfer-Encoding: 7bit
Cc: Cullen Jennings <fluffy@cisco.com>, Oren Peleg <OrenP@audiocodes.com>,
        David R Oran <oran@cisco.com>, avt@ietf.org,
        "Michael A. Ramalho" <mramalho@cisco.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: e654cfa5e44bd623be3eb2c720858b05
Content-Transfer-Encoding: 7bit



Mark

We tried to flag this in RFC3611 with the following text in the "security
considerations" section

   Any encryption or filtering of XR report blocks entails a loss of
   monitoring information to third parties.  For example, a network that
   establishes a tunnel to encrypt VoIP Report Blocks denies that
   information to the service providers traversed by the tunnel.  The
   service providers cannot then monitor or respond to the quality of
   the VoIP calls that they carry, potentially creating problems for the
   network's users.  As a default, XR packets should not be encrypted or
   filtered.

Could we potentially interpret this as being the definition of what to
selectively encrypt in the case of the RFC3611 specification?

Regards

Alan


-----Original Message-----
From: Mark Baugher [mailto:mbaugher@cisco.com]
Sent: Wednesday, November 24, 2004 2:42 PM
To: Alan Clark
Cc: Oren Peleg; Cullen Jennings; avt@ietf.org; David R Oran; Michael A.
Ramalho
Subject: Re: [AVT] RFC 3711 and RTCP


So, when the sender and receiver agree to encrypt SRTCP, this would mean
only that some SRTCP messages would be encrypted and the sender would
decide which ones to encrypt?  My personal opinion is that this is not
secure because it is unpredictable to the receiver, which may have a
policy that all messages related to its session be encrypted.

I can think of a few potential approaches to this problem.

1. Let individual SRTCP messages or a bundle of SRTCP messages
be signaled to be unencrypted when SRTCP encryption is used.

2. Make a blanket policy that the sender determine what
to selectively encrypt, as you suggest.

3. Define the policy of what to selectively encrypt in
the particular specification.  In other words, a document could
re-define the signaling of SRTCP encryption according to its
needs.  The specification of foo, therefore, could define a new
parameter such as foo_ENCRYPTED_SRTCP to be used in place of
ENCRYPTED_SRTCP.  The foo document would define what gets
encrypted and what does not get encrypted as per its needs.

I commented on #2 already.  I don't like #1 because of its signaling
complexity.  I like #3 because it limits the complexity to the
specific needs of an application.  #1 would be more efficient than
#3 if lots of applications had their own specific needs for
selective encryption of SRTCP message.  But I don't think this is
the case.

Mark

On Nov 24, 2004, at 10:58 AM, Alan Clark wrote:

>
> If the use of encryption in SRTCP is signalled by an explicit (E) bit
> in the
> SRTCP header then perhaps the sender could autonomously decide whether
> it
> wants to encrypt?  Presumably since the sender is in the best position
> to
> decide if the data is sensitive then this would be ok - and the
> receiver is
> able to just look at the E bit and hence recognize that decryption is
> needed.
>
> Alan
>
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]On Behalf Of
> Mark Baugher
> Sent: Wednesday, November 24, 2004 1:33 PM
> To: David R Oran
> Cc: Cullen Jennings; Oren Peleg; Michael A. Ramalho; Alan Clark;
> avt@ietf.org
> Subject: Re: [AVT] RFC 3711 and RTCP
>
>
>
> On Nov 24, 2004, at 10:05 AM, David R Oran wrote:
>
>>
>> On Nov 24, 2004, at 12:23 PM, Alan Clark wrote:
>>
>>>
>>> Michael
>>>
>>> I don't see why this would be a problem unless you included SDES and
>>> (SR or
>>> RR or XR) in the same RTCP packet.  SRTP (at least the protocol) is
>>> apparently able to decided on a packet by packet basis whether to
>>> encrypt
>>> RTCP - hopefully SRTP implementations also permit this.
>>>
>> Sure, they can do this. But remember offer-answer. How does a receiver
>> communicate such a granular policy to the transmitter? Right now if
>> can say whether to auth or auth+encrypt RTP, and auth or auth+encrypt
>> RTCP. There's no way to say auth+encrypt SDES but only auth SR/XR etc.
>
> Seems to me that this is a problem with SDP security descriptions.
> That problem might be there because we forgot about the E bit.  This
> seems very messy for the reason you mention above - granularity.  I
> don't think that we want to negotiate the encryption policy for each
> type SDP message, which is a problem with something like the E bit.
>
> Mark
>>
>>
>>> Logically I'd send SDES on its own at the start of a call to provide
>>> some
>>> user info, but would not send SR/RR/XR until at least 8-10 seconds
>>> into the
>>> call as I need some time to gather statistics to report.
>> That's not exactly what the RTP specs say. RTCP timers don't have this
>> kind of policy today. In fact, there are porposals on the table to use
>> RTCP for early feedback to assess reception quality on some initial
>> packets - e.g. the RTP-noop proposal. In any event that has no bearing
>> on the present discussion.
>>
>>> After the
>>> start-of-call exchange there would appear to be minimal need to
>>> include
>>> SDES. I'm sure we could construct some scenarios in which you "may"
>>> need to
>>> include SDES with SR/RR/XR however the vast majority of cases would
>>> either
>>> need only a single initial exchange or may not need SDES at all.
>>>
>> Any time you change SSRC you potentially need to send SDES.
>> That said, I still don't see what bearing this has on the discussion
>> about whether we need the complexity of encrypting some RTCP packets
>> and not others for a single session.
>>
>> It's a tradeoff between extra complexity+less privacy versus allowing
>> snoopers to gather RTCP stats.
>>
>> Dave.
>>
>>> Regards
>>>
>>> Alan
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: Michael A. Ramalho [mailto:mramalho@cisco.com]
>>> Sent: Wednesday, November 24, 2004 9:39 AM
>>> To: Alan Clark
>>> Cc: Oren Peleg; avt@ietf.org
>>> Subject: RE: [AVT] RFC 3711 and RTCP
>>>
>>>
>>> At 07:54 AM 11/24/2004 -0500, Alan Clark wrote:
>>>> Hi Oren
>>>>
>>>> Yes - encryption is intended to provide privacy however this relates
>>>> primarily to the voice payloads and to information within RTCP that
>>>> may be
>>>> associated with individual users (e.g. SDES).
>>>>
>>>> SR, RR and XR contain only peformance statistics and there is no
>>>> privacy
>>>> consideration that I can think of related to this type of data.
>>>>
>>>> The message is - encrypt RTP, optionally encrypt RTCP SDES but don't
>>> encrypt
>>>> RTCP SR/RR/XR
>>>
>>> Hi Alan,
>>>
>>> I am wondering about implementations utilizing your advise
>>> "optionally
>>> encrypt
>>> RTCP SDES but don't encrypt RTCP SR/RR/XR".
>>>
>>> Is there an easy way to tell SRTP to encrypt RTCP SDES, but not RTCP
>>> SR/RR/XR? It seems that all the RTCP blocks would otherwise be highly
>>> related to each other. For example (quote out of RFC 3611):
>>>
>>> "XR packets supplement the existing RTCP packets, and may be stacked
>>> with
>>> other RTCP packets to form compound RTCP packets [9, Section 6]."
>>>
>>> Thus, RFC3611 explicitly admits the possibility of (but does not
>>> mandate)
>>> the piggybacking all the RTCP-XR block types.
>>>
>>> RTCP implementations would have to know the SRTP encryption rules to
>>> make sure they don't perform piggybacking with SDES ... but could
>>> allow
>>> (the more bandwidth efficient) piggybacking on the other RTCP-XR
>>> blocks.
>>>
>>> This RTCP/SRTP interaction/dependency seems to add a burden to both
>>> RTCP and SRTP implementations ... let alone the expressiveness
>>> required
>>> to signal your advise in existing SDP/SRTP mechanisms.
>>>
>>> Are you aware of any implementations that have actually followed your
>>> advise above? I rather go into this one with our eyes open ...
>>> developers
>>> highly dislike this cross-functional entity dependency (RTCP & SRTP
>>> along
>>> with expressing it in SDP/SRTP mechanisms).
>>>
>>> Regards,
>>>
>>> Michael Ramalho
>>>
>>>
>>>
>>>> Regards
>>>>
>>>> Alan
>>>>
>>>> -----Original Message-----
>>>> From: Oren Peleg [mailto:OrenP@audiocodes.com]
>>>> Sent: Wednesday, November 24, 2004 7:50 AM
>>>> To: Alan Clark; avt@ietf.org
>>>> Subject: RE: [AVT] RFC 3711 and RTCP
>>>>
>>>>
>>>>
>>>> Isnt encryption is to prevent monitoring from the first place?
>>>>
>>>> -----Original Message-----
>>>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf
>>>> Of
>>>> Alan Clark
>>>> Sent: Tuesday, November 23, 2004 5:42 PM
>>>> To: avt@ietf.org
>>>> Subject: [AVT] RFC 3711 and RTCP
>>>>
>>>>
>>>>> From the flurry of discussion on RFC3711 it looks as if there is
>>>> considerable interest in SRTP implementation.  I'd like to add a
>>>> request
>>>> to
>>>> SRTP implementors with regard to manageability.
>>>>
>>>> RTCP SR, RR and more particularly XR (e.g. VoIP Metrics report
>>>> block)
>>>> contain useful information for network monitoring, and are often
>>>> used by
>>>> probes and analyzers to support problem diagnosis.  RFC3711 allows
>>>> the
>>>> selective encryption of RTCP payloads and hence I would strongly
>>>> recomment
>>>> that RFC3711 implementors DO NOT encrypt RTCP SR, RR and XR payloads
>>>> as
>>>> this
>>>> adversely impacts manageability.
>>>>
>>>> Regards
>>>>
>>>> Alan Clark
>>>> Telchemy
>>>>
>>>>
>>>> _______________________________________________
>>>> Audio/Video Transport Working Group
>>>> avt@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/avt
>>>>
>>>> ********************************************************************
>>>> *
>>>> ******
>>> *
>>>> ********************************
>>>> This email and any files transmitted with it are confidential
>>>> material.
>>>> They are intended solely for the use of the designated individual or
>>>> entity
>>>> to whom they are addressed.
>>>> If the reader of this message is not the intended recipient,
>>>> you are hereby notified that any dissemination,use,
>>>> distribution or copying of this communication is strictly prohibited
>>>> and
>>> may
>>>> be unlawful.
>>>>
>>>> If you have received this email in error please notify
>>>> postmaster@audiocodes.com and permanently delete the e-mail and
>>>> files.
>>>>
>>>>
>>>> ********************************************************************
>>>> *
>>>> ******
>>> *
>>>> *******************************
>>>>
>>>>
>>>> _______________________________________________
>>>> Audio/Video Transport Working Group
>>>> avt@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/avt
>>>
>>>
>>> _______________________________________________
>>> Audio/Video Transport Working Group
>>> avt@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/avt
>>>
>> David R. Oran
>> Cisco Fellow
>> Cisco Systems
>> 7 Ladyslipper Lane
>> Acton, MA 01720 USA
>> Tel: +1 978 264 2048
>> Email: oran@cisco.com
>>
>>
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www1.ietf.org/mailman/listinfo/avt
>>
>
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Wed Nov 24 19:30:43 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20674
	for <avt-archive@ietf.org>; Wed, 24 Nov 2004 19:30:43 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CX7b1-0002ZV-Vs
	for avt-archive@ietf.org; Wed, 24 Nov 2004 19:34:53 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CX7Sx-0001Qx-Jp; Wed, 24 Nov 2004 19:26:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CX7MP-0008M1-LW
	for avt@megatron.ietf.org; Wed, 24 Nov 2004 19:19:45 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19756
	for <avt@ietf.org>; Wed, 24 Nov 2004 19:19:42 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CX7QN-0002JW-8K for avt@ietf.org; Wed, 24 Nov 2004 19:23:51 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 24 Nov 2004 16:22:42 -0800
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iAP0It9N014106;
	Wed, 24 Nov 2004 16:18:56 -0800 (PST)
Received: from [192.168.0.10] (sjc-vpn4-24.cisco.com [10.21.80.24])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id iAP0J30J005141;
	Wed, 24 Nov 2004 16:19:03 -0800
In-Reply-To: <BGEKJNNFCPJKLLMMDMELIEKNFLAA.alan.d.clark@telchemy.com>
References: <BGEKJNNFCPJKLLMMDMELIEKNFLAA.alan.d.clark@telchemy.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <7D052489-3E77-11D9-A16E-000A95DC10F2@cisco.com>
Content-Transfer-Encoding: 7bit
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [AVT] RFC 3711 and RTCP
Date: Wed, 24 Nov 2004 16:18:10 -0800
To: "Alan Clark" <alan.d.clark@telchemy.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1101341944.197133"; x:"432200"; a:"rsa-sha1"; b:"nofws:13179";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"AGpjmXJOgkwHCTyrxLneLyeQtsr4EFwzqVTXZDx7JTZ7TIt2s77mToo7BzZQE"
	"DQQ/m5bsdhTeoRkLN5AzMLm5Om70WHskjh5kEH0HnHOs5mfxKOlD0HuvRshE4"
	"LoVT6j83s5rhVJ2W2zzv0I1nSAsGZ1/Rnd6ZA8OZxiQO5DDVY=";
	c:"From: Mark Baugher <mbaugher@cisco.com>";
	c:"Subject: Re: [AVT] RFC 3711 and RTCP";
	c:"Date: Wed, 24 Nov 2004 16:18:10 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 3a331e4a192f4d33f18e6f8376287cf6
Content-Transfer-Encoding: 7bit
Cc: Colin Perkins <csp@csperkins.org>, Joerg Ott <jo@tzi.uni-bremen.de>,
        IETF AVT WG <avt@ietf.org>, Jon Peterson <jon.peterson@neustar.biz>,
        "'mankin@psg.com'" <mankin@psg.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 4cbeb0f20efb229aa93fae1468d20275
Content-Transfer-Encoding: 7bit

Alan
   As Dave Oran has pointed out, the definition that you want is not  
supported in the signaling, at present.  The current definition of  
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions 
-07.txt treats SRTCP encryption as either on or off and does not  
address the problem of setting the E bit in SRTCP packets.  This is a  
bug that we need to fix.

   MMUSIC has finished last call on  
draft-ietf-mmusic-sdescriptions-07.txt, and the transport ADs have  
reviewed it.  We'll be making some changes at Jon Peterson's request  
and post another version in about a week.  This is an opportunity to  
address the E bit, but the MMUSIC chairs or transport ADs may want  
another WG last call.  Off the top of my head, I would offer something  
like the following.

"As the default behavior when UNENCRYPTED_SRTCP is signaled, all SRTCP  
packets MUST have the E bit set to zero and MUST NOT be encrypted.   
Otherwise, all SRTP packets MUST have the E bit set to one and MUST be  
encrypted by default.  Individual applications MAY override these  
default behaviors in their specifications.  In a session where SRTCP  
packets are encrypted, therefore, applications that use RFC 3611 MAY  
set the E bit to 0 for XR packets as recommended by RFC 3611."

Mark

On Nov 24, 2004, at 2:33 PM, Alan Clark wrote:

>
>
> Mark
>
> We tried to flag this in RFC3611 with the following text in the  
> "security
> considerations" section
>
>    Any encryption or filtering of XR report blocks entails a loss of
>    monitoring information to third parties.  For example, a network  
> that
>    establishes a tunnel to encrypt VoIP Report Blocks denies that
>    information to the service providers traversed by the tunnel.  The
>    service providers cannot then monitor or respond to the quality of
>    the VoIP calls that they carry, potentially creating problems for  
> the
>    network's users.  As a default, XR packets should not be encrypted  
> or
>    filtered.
>
> Could we potentially interpret this as being the definition of what to
> selectively encrypt in the case of the RFC3611 specification?
>
> Regards
>
> Alan
>
>
> -----Original Message-----
> From: Mark Baugher [mailto:mbaugher@cisco.com]
> Sent: Wednesday, November 24, 2004 2:42 PM
> To: Alan Clark
> Cc: Oren Peleg; Cullen Jennings; avt@ietf.org; David R Oran; Michael A.
> Ramalho
> Subject: Re: [AVT] RFC 3711 and RTCP
>
>
> So, when the sender and receiver agree to encrypt SRTCP, this would  
> mean
> only that some SRTCP messages would be encrypted and the sender would
> decide which ones to encrypt?  My personal opinion is that this is not
> secure because it is unpredictable to the receiver, which may have a
> policy that all messages related to its session be encrypted.
>
> I can think of a few potential approaches to this problem.
>
> 1. Let individual SRTCP messages or a bundle of SRTCP messages
> be signaled to be unencrypted when SRTCP encryption is used.
>
> 2. Make a blanket policy that the sender determine what
> to selectively encrypt, as you suggest.
>
> 3. Define the policy of what to selectively encrypt in
> the particular specification.  In other words, a document could
> re-define the signaling of SRTCP encryption according to its
> needs.  The specification of foo, therefore, could define a new
> parameter such as foo_ENCRYPTED_SRTCP to be used in place of
> ENCRYPTED_SRTCP.  The foo document would define what gets
> encrypted and what does not get encrypted as per its needs.
>
> I commented on #2 already.  I don't like #1 because of its signaling
> complexity.  I like #3 because it limits the complexity to the
> specific needs of an application.  #1 would be more efficient than
> #3 if lots of applications had their own specific needs for
> selective encryption of SRTCP message.  But I don't think this is
> the case.
>
> Mark
>
> On Nov 24, 2004, at 10:58 AM, Alan Clark wrote:
>
>>
>> If the use of encryption in SRTCP is signalled by an explicit (E) bit
>> in the
>> SRTCP header then perhaps the sender could autonomously decide whether
>> it
>> wants to encrypt?  Presumably since the sender is in the best position
>> to
>> decide if the data is sensitive then this would be ok - and the
>> receiver is
>> able to just look at the E bit and hence recognize that decryption is
>> needed.
>>
>> Alan
>>
>> -----Original Message-----
>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]On Behalf Of
>> Mark Baugher
>> Sent: Wednesday, November 24, 2004 1:33 PM
>> To: David R Oran
>> Cc: Cullen Jennings; Oren Peleg; Michael A. Ramalho; Alan Clark;
>> avt@ietf.org
>> Subject: Re: [AVT] RFC 3711 and RTCP
>>
>>
>>
>> On Nov 24, 2004, at 10:05 AM, David R Oran wrote:
>>
>>>
>>> On Nov 24, 2004, at 12:23 PM, Alan Clark wrote:
>>>
>>>>
>>>> Michael
>>>>
>>>> I don't see why this would be a problem unless you included SDES and
>>>> (SR or
>>>> RR or XR) in the same RTCP packet.  SRTP (at least the protocol) is
>>>> apparently able to decided on a packet by packet basis whether to
>>>> encrypt
>>>> RTCP - hopefully SRTP implementations also permit this.
>>>>
>>> Sure, they can do this. But remember offer-answer. How does a  
>>> receiver
>>> communicate such a granular policy to the transmitter? Right now if
>>> can say whether to auth or auth+encrypt RTP, and auth or auth+encrypt
>>> RTCP. There's no way to say auth+encrypt SDES but only auth SR/XR  
>>> etc.
>>
>> Seems to me that this is a problem with SDP security descriptions.
>> That problem might be there because we forgot about the E bit.  This
>> seems very messy for the reason you mention above - granularity.  I
>> don't think that we want to negotiate the encryption policy for each
>> type SDP message, which is a problem with something like the E bit.
>>
>> Mark
>>>
>>>
>>>> Logically I'd send SDES on its own at the start of a call to provide
>>>> some
>>>> user info, but would not send SR/RR/XR until at least 8-10 seconds
>>>> into the
>>>> call as I need some time to gather statistics to report.
>>> That's not exactly what the RTP specs say. RTCP timers don't have  
>>> this
>>> kind of policy today. In fact, there are porposals on the table to  
>>> use
>>> RTCP for early feedback to assess reception quality on some initial
>>> packets - e.g. the RTP-noop proposal. In any event that has no  
>>> bearing
>>> on the present discussion.
>>>
>>>> After the
>>>> start-of-call exchange there would appear to be minimal need to
>>>> include
>>>> SDES. I'm sure we could construct some scenarios in which you "may"
>>>> need to
>>>> include SDES with SR/RR/XR however the vast majority of cases would
>>>> either
>>>> need only a single initial exchange or may not need SDES at all.
>>>>
>>> Any time you change SSRC you potentially need to send SDES.
>>> That said, I still don't see what bearing this has on the discussion
>>> about whether we need the complexity of encrypting some RTCP packets
>>> and not others for a single session.
>>>
>>> It's a tradeoff between extra complexity+less privacy versus allowing
>>> snoopers to gather RTCP stats.
>>>
>>> Dave.
>>>
>>>> Regards
>>>>
>>>> Alan
>>>>
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Michael A. Ramalho [mailto:mramalho@cisco.com]
>>>> Sent: Wednesday, November 24, 2004 9:39 AM
>>>> To: Alan Clark
>>>> Cc: Oren Peleg; avt@ietf.org
>>>> Subject: RE: [AVT] RFC 3711 and RTCP
>>>>
>>>>
>>>> At 07:54 AM 11/24/2004 -0500, Alan Clark wrote:
>>>>> Hi Oren
>>>>>
>>>>> Yes - encryption is intended to provide privacy however this  
>>>>> relates
>>>>> primarily to the voice payloads and to information within RTCP that
>>>>> may be
>>>>> associated with individual users (e.g. SDES).
>>>>>
>>>>> SR, RR and XR contain only peformance statistics and there is no
>>>>> privacy
>>>>> consideration that I can think of related to this type of data.
>>>>>
>>>>> The message is - encrypt RTP, optionally encrypt RTCP SDES but  
>>>>> don't
>>>> encrypt
>>>>> RTCP SR/RR/XR
>>>>
>>>> Hi Alan,
>>>>
>>>> I am wondering about implementations utilizing your advise
>>>> "optionally
>>>> encrypt
>>>> RTCP SDES but don't encrypt RTCP SR/RR/XR".
>>>>
>>>> Is there an easy way to tell SRTP to encrypt RTCP SDES, but not RTCP
>>>> SR/RR/XR? It seems that all the RTCP blocks would otherwise be  
>>>> highly
>>>> related to each other. For example (quote out of RFC 3611):
>>>>
>>>> "XR packets supplement the existing RTCP packets, and may be stacked
>>>> with
>>>> other RTCP packets to form compound RTCP packets [9, Section 6]."
>>>>
>>>> Thus, RFC3611 explicitly admits the possibility of (but does not
>>>> mandate)
>>>> the piggybacking all the RTCP-XR block types.
>>>>
>>>> RTCP implementations would have to know the SRTP encryption rules to
>>>> make sure they don't perform piggybacking with SDES ... but could
>>>> allow
>>>> (the more bandwidth efficient) piggybacking on the other RTCP-XR
>>>> blocks.
>>>>
>>>> This RTCP/SRTP interaction/dependency seems to add a burden to both
>>>> RTCP and SRTP implementations ... let alone the expressiveness
>>>> required
>>>> to signal your advise in existing SDP/SRTP mechanisms.
>>>>
>>>> Are you aware of any implementations that have actually followed  
>>>> your
>>>> advise above? I rather go into this one with our eyes open ...
>>>> developers
>>>> highly dislike this cross-functional entity dependency (RTCP & SRTP
>>>> along
>>>> with expressing it in SDP/SRTP mechanisms).
>>>>
>>>> Regards,
>>>>
>>>> Michael Ramalho
>>>>
>>>>
>>>>
>>>>> Regards
>>>>>
>>>>> Alan
>>>>>
>>>>> -----Original Message-----
>>>>> From: Oren Peleg [mailto:OrenP@audiocodes.com]
>>>>> Sent: Wednesday, November 24, 2004 7:50 AM
>>>>> To: Alan Clark; avt@ietf.org
>>>>> Subject: RE: [AVT] RFC 3711 and RTCP
>>>>>
>>>>>
>>>>>
>>>>> Isnt encryption is to prevent monitoring from the first place?
>>>>>
>>>>> -----Original Message-----
>>>>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf
>>>>> Of
>>>>> Alan Clark
>>>>> Sent: Tuesday, November 23, 2004 5:42 PM
>>>>> To: avt@ietf.org
>>>>> Subject: [AVT] RFC 3711 and RTCP
>>>>>
>>>>>
>>>>>> From the flurry of discussion on RFC3711 it looks as if there is
>>>>> considerable interest in SRTP implementation.  I'd like to add a
>>>>> request
>>>>> to
>>>>> SRTP implementors with regard to manageability.
>>>>>
>>>>> RTCP SR, RR and more particularly XR (e.g. VoIP Metrics report
>>>>> block)
>>>>> contain useful information for network monitoring, and are often
>>>>> used by
>>>>> probes and analyzers to support problem diagnosis.  RFC3711 allows
>>>>> the
>>>>> selective encryption of RTCP payloads and hence I would strongly
>>>>> recomment
>>>>> that RFC3711 implementors DO NOT encrypt RTCP SR, RR and XR  
>>>>> payloads
>>>>> as
>>>>> this
>>>>> adversely impacts manageability.
>>>>>
>>>>> Regards
>>>>>
>>>>> Alan Clark
>>>>> Telchemy
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Audio/Video Transport Working Group
>>>>> avt@ietf.org
>>>>> https://www1.ietf.org/mailman/listinfo/avt
>>>>>
>>>>> ******************************************************************* 
>>>>> *
>>>>> *
>>>>> ******
>>>> *
>>>>> ********************************
>>>>> This email and any files transmitted with it are confidential
>>>>> material.
>>>>> They are intended solely for the use of the designated individual  
>>>>> or
>>>>> entity
>>>>> to whom they are addressed.
>>>>> If the reader of this message is not the intended recipient,
>>>>> you are hereby notified that any dissemination,use,
>>>>> distribution or copying of this communication is strictly  
>>>>> prohibited
>>>>> and
>>>> may
>>>>> be unlawful.
>>>>>
>>>>> If you have received this email in error please notify
>>>>> postmaster@audiocodes.com and permanently delete the e-mail and
>>>>> files.
>>>>>
>>>>>
>>>>> ******************************************************************* 
>>>>> *
>>>>> *
>>>>> ******
>>>> *
>>>>> *******************************
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Audio/Video Transport Working Group
>>>>> avt@ietf.org
>>>>> https://www1.ietf.org/mailman/listinfo/avt
>>>>
>>>>
>>>> _______________________________________________
>>>> Audio/Video Transport Working Group
>>>> avt@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/avt
>>>>
>>> David R. Oran
>>> Cisco Fellow
>>> Cisco Systems
>>> 7 Ladyslipper Lane
>>> Acton, MA 01720 USA
>>> Tel: +1 978 264 2048
>>> Email: oran@cisco.com
>>>
>>>
>>> _______________________________________________
>>> Audio/Video Transport Working Group
>>> avt@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/avt
>>>
>>
>>
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www1.ietf.org/mailman/listinfo/avt
>>
>


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Fri Nov 26 13:52:54 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09056
	for <avt-archive@ietf.org>; Fri, 26 Nov 2004 13:52:53 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CXlHX-0001Ru-E1
	for avt-archive@ietf.org; Fri, 26 Nov 2004 13:57:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CXl8D-0003Yb-LJ; Fri, 26 Nov 2004 13:47:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CXkyv-00022o-66
	for avt@megatron.ietf.org; Fri, 26 Nov 2004 13:38:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07689
	for <avt@ietf.org>; Fri, 26 Nov 2004 13:38:05 -0500 (EST)
Received: from mx.cbeyond.net ([66.180.96.58] helo=mx.cbeyond.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXl3E-0000su-HV
	for avt@ietf.org; Fri, 26 Nov 2004 13:42:37 -0500
Received: from [67.33.162.5] (port=1368 helo=telws116)
	by mx.cbeyond.com with asmtp (Exim 4.34)
	id 1CXkys-0005WP-Be; Fri, 26 Nov 2004 13:38:06 -0500
From: "Alan Clark" <alan.d.clark@telchemy.com>
To: "Mark Baugher" <mbaugher@cisco.com>
Subject: RE: [AVT] RFC 3711 and RTCP
Date: Fri, 26 Nov 2004 13:38:08 -0500
Message-ID: <BGEKJNNFCPJKLLMMDMELAEOJFLAA.alan.d.clark@telchemy.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
In-Reply-To: <7D052489-3E77-11D9-A16E-000A95DC10F2@cisco.com>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 958aa603499a3de6b2b87d68741ed60e
Content-Transfer-Encoding: 7bit
Cc: mankin@psg.com, Joerg Ott <jo@tzi.uni-bremen.de>,
        Colin Perkins <csp@csperkins.org>,
        Jon Peterson <jon.peterson@neustar.biz>, IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: bfef20db74c24e87b6dbcd42ea7ba67c
Content-Transfer-Encoding: 7bit

Mark

The language you suggest would address the issue.  It would be great if you
could incorporate this

Regards

Alan

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]On Behalf Of
Mark Baugher
Sent: Wednesday, November 24, 2004 7:18 PM
To: Alan Clark
Cc: Colin Perkins; Joerg Ott; IETF AVT WG; Jon Peterson;
'mankin@psg.com'
Subject: Re: [AVT] RFC 3711 and RTCP


Alan
   As Dave Oran has pointed out, the definition that you want is not
supported in the signaling, at present.  The current definition of
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions
-07.txt treats SRTCP encryption as either on or off and does not
address the problem of setting the E bit in SRTCP packets.  This is a
bug that we need to fix.

   MMUSIC has finished last call on
draft-ietf-mmusic-sdescriptions-07.txt, and the transport ADs have
reviewed it.  We'll be making some changes at Jon Peterson's request
and post another version in about a week.  This is an opportunity to
address the E bit, but the MMUSIC chairs or transport ADs may want
another WG last call.  Off the top of my head, I would offer something
like the following.

"As the default behavior when UNENCRYPTED_SRTCP is signaled, all SRTCP
packets MUST have the E bit set to zero and MUST NOT be encrypted.
Otherwise, all SRTP packets MUST have the E bit set to one and MUST be
encrypted by default.  Individual applications MAY override these
default behaviors in their specifications.  In a session where SRTCP
packets are encrypted, therefore, applications that use RFC 3611 MAY
set the E bit to 0 for XR packets as recommended by RFC 3611."

Mark

On Nov 24, 2004, at 2:33 PM, Alan Clark wrote:

>
>
> Mark
>
> We tried to flag this in RFC3611 with the following text in the
> "security
> considerations" section
>
>    Any encryption or filtering of XR report blocks entails a loss of
>    monitoring information to third parties.  For example, a network
> that
>    establishes a tunnel to encrypt VoIP Report Blocks denies that
>    information to the service providers traversed by the tunnel.  The
>    service providers cannot then monitor or respond to the quality of
>    the VoIP calls that they carry, potentially creating problems for
> the
>    network's users.  As a default, XR packets should not be encrypted
> or
>    filtered.
>
> Could we potentially interpret this as being the definition of what to
> selectively encrypt in the case of the RFC3611 specification?
>
> Regards
>
> Alan
>
>
> -----Original Message-----
> From: Mark Baugher [mailto:mbaugher@cisco.com]
> Sent: Wednesday, November 24, 2004 2:42 PM
> To: Alan Clark
> Cc: Oren Peleg; Cullen Jennings; avt@ietf.org; David R Oran; Michael A.
> Ramalho
> Subject: Re: [AVT] RFC 3711 and RTCP
>
>
> So, when the sender and receiver agree to encrypt SRTCP, this would
> mean
> only that some SRTCP messages would be encrypted and the sender would
> decide which ones to encrypt?  My personal opinion is that this is not
> secure because it is unpredictable to the receiver, which may have a
> policy that all messages related to its session be encrypted.
>
> I can think of a few potential approaches to this problem.
>
> 1. Let individual SRTCP messages or a bundle of SRTCP messages
> be signaled to be unencrypted when SRTCP encryption is used.
>
> 2. Make a blanket policy that the sender determine what
> to selectively encrypt, as you suggest.
>
> 3. Define the policy of what to selectively encrypt in
> the particular specification.  In other words, a document could
> re-define the signaling of SRTCP encryption according to its
> needs.  The specification of foo, therefore, could define a new
> parameter such as foo_ENCRYPTED_SRTCP to be used in place of
> ENCRYPTED_SRTCP.  The foo document would define what gets
> encrypted and what does not get encrypted as per its needs.
>
> I commented on #2 already.  I don't like #1 because of its signaling
> complexity.  I like #3 because it limits the complexity to the
> specific needs of an application.  #1 would be more efficient than
> #3 if lots of applications had their own specific needs for
> selective encryption of SRTCP message.  But I don't think this is
> the case.
>
> Mark
>
> On Nov 24, 2004, at 10:58 AM, Alan Clark wrote:
>
>>
>> If the use of encryption in SRTCP is signalled by an explicit (E) bit
>> in the
>> SRTCP header then perhaps the sender could autonomously decide whether
>> it
>> wants to encrypt?  Presumably since the sender is in the best position
>> to
>> decide if the data is sensitive then this would be ok - and the
>> receiver is
>> able to just look at the E bit and hence recognize that decryption is
>> needed.
>>
>> Alan
>>
>> -----Original Message-----
>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]On Behalf Of
>> Mark Baugher
>> Sent: Wednesday, November 24, 2004 1:33 PM
>> To: David R Oran
>> Cc: Cullen Jennings; Oren Peleg; Michael A. Ramalho; Alan Clark;
>> avt@ietf.org
>> Subject: Re: [AVT] RFC 3711 and RTCP
>>
>>
>>
>> On Nov 24, 2004, at 10:05 AM, David R Oran wrote:
>>
>>>
>>> On Nov 24, 2004, at 12:23 PM, Alan Clark wrote:
>>>
>>>>
>>>> Michael
>>>>
>>>> I don't see why this would be a problem unless you included SDES and
>>>> (SR or
>>>> RR or XR) in the same RTCP packet.  SRTP (at least the protocol) is
>>>> apparently able to decided on a packet by packet basis whether to
>>>> encrypt
>>>> RTCP - hopefully SRTP implementations also permit this.
>>>>
>>> Sure, they can do this. But remember offer-answer. How does a
>>> receiver
>>> communicate such a granular policy to the transmitter? Right now if
>>> can say whether to auth or auth+encrypt RTP, and auth or auth+encrypt
>>> RTCP. There's no way to say auth+encrypt SDES but only auth SR/XR
>>> etc.
>>
>> Seems to me that this is a problem with SDP security descriptions.
>> That problem might be there because we forgot about the E bit.  This
>> seems very messy for the reason you mention above - granularity.  I
>> don't think that we want to negotiate the encryption policy for each
>> type SDP message, which is a problem with something like the E bit.
>>
>> Mark
>>>
>>>
>>>> Logically I'd send SDES on its own at the start of a call to provide
>>>> some
>>>> user info, but would not send SR/RR/XR until at least 8-10 seconds
>>>> into the
>>>> call as I need some time to gather statistics to report.
>>> That's not exactly what the RTP specs say. RTCP timers don't have
>>> this
>>> kind of policy today. In fact, there are porposals on the table to
>>> use
>>> RTCP for early feedback to assess reception quality on some initial
>>> packets - e.g. the RTP-noop proposal. In any event that has no
>>> bearing
>>> on the present discussion.
>>>
>>>> After the
>>>> start-of-call exchange there would appear to be minimal need to
>>>> include
>>>> SDES. I'm sure we could construct some scenarios in which you "may"
>>>> need to
>>>> include SDES with SR/RR/XR however the vast majority of cases would
>>>> either
>>>> need only a single initial exchange or may not need SDES at all.
>>>>
>>> Any time you change SSRC you potentially need to send SDES.
>>> That said, I still don't see what bearing this has on the discussion
>>> about whether we need the complexity of encrypting some RTCP packets
>>> and not others for a single session.
>>>
>>> It's a tradeoff between extra complexity+less privacy versus allowing
>>> snoopers to gather RTCP stats.
>>>
>>> Dave.
>>>
>>>> Regards
>>>>
>>>> Alan
>>>>
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Michael A. Ramalho [mailto:mramalho@cisco.com]
>>>> Sent: Wednesday, November 24, 2004 9:39 AM
>>>> To: Alan Clark
>>>> Cc: Oren Peleg; avt@ietf.org
>>>> Subject: RE: [AVT] RFC 3711 and RTCP
>>>>
>>>>
>>>> At 07:54 AM 11/24/2004 -0500, Alan Clark wrote:
>>>>> Hi Oren
>>>>>
>>>>> Yes - encryption is intended to provide privacy however this
>>>>> relates
>>>>> primarily to the voice payloads and to information within RTCP that
>>>>> may be
>>>>> associated with individual users (e.g. SDES).
>>>>>
>>>>> SR, RR and XR contain only peformance statistics and there is no
>>>>> privacy
>>>>> consideration that I can think of related to this type of data.
>>>>>
>>>>> The message is - encrypt RTP, optionally encrypt RTCP SDES but
>>>>> don't
>>>> encrypt
>>>>> RTCP SR/RR/XR
>>>>
>>>> Hi Alan,
>>>>
>>>> I am wondering about implementations utilizing your advise
>>>> "optionally
>>>> encrypt
>>>> RTCP SDES but don't encrypt RTCP SR/RR/XR".
>>>>
>>>> Is there an easy way to tell SRTP to encrypt RTCP SDES, but not RTCP
>>>> SR/RR/XR? It seems that all the RTCP blocks would otherwise be
>>>> highly
>>>> related to each other. For example (quote out of RFC 3611):
>>>>
>>>> "XR packets supplement the existing RTCP packets, and may be stacked
>>>> with
>>>> other RTCP packets to form compound RTCP packets [9, Section 6]."
>>>>
>>>> Thus, RFC3611 explicitly admits the possibility of (but does not
>>>> mandate)
>>>> the piggybacking all the RTCP-XR block types.
>>>>
>>>> RTCP implementations would have to know the SRTP encryption rules to
>>>> make sure they don't perform piggybacking with SDES ... but could
>>>> allow
>>>> (the more bandwidth efficient) piggybacking on the other RTCP-XR
>>>> blocks.
>>>>
>>>> This RTCP/SRTP interaction/dependency seems to add a burden to both
>>>> RTCP and SRTP implementations ... let alone the expressiveness
>>>> required
>>>> to signal your advise in existing SDP/SRTP mechanisms.
>>>>
>>>> Are you aware of any implementations that have actually followed
>>>> your
>>>> advise above? I rather go into this one with our eyes open ...
>>>> developers
>>>> highly dislike this cross-functional entity dependency (RTCP & SRTP
>>>> along
>>>> with expressing it in SDP/SRTP mechanisms).
>>>>
>>>> Regards,
>>>>
>>>> Michael Ramalho
>>>>
>>>>
>>>>
>>>>> Regards
>>>>>
>>>>> Alan
>>>>>
>>>>> -----Original Message-----
>>>>> From: Oren Peleg [mailto:OrenP@audiocodes.com]
>>>>> Sent: Wednesday, November 24, 2004 7:50 AM
>>>>> To: Alan Clark; avt@ietf.org
>>>>> Subject: RE: [AVT] RFC 3711 and RTCP
>>>>>
>>>>>
>>>>>
>>>>> Isnt encryption is to prevent monitoring from the first place?
>>>>>
>>>>> -----Original Message-----
>>>>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf
>>>>> Of
>>>>> Alan Clark
>>>>> Sent: Tuesday, November 23, 2004 5:42 PM
>>>>> To: avt@ietf.org
>>>>> Subject: [AVT] RFC 3711 and RTCP
>>>>>
>>>>>
>>>>>> From the flurry of discussion on RFC3711 it looks as if there is
>>>>> considerable interest in SRTP implementation.  I'd like to add a
>>>>> request
>>>>> to
>>>>> SRTP implementors with regard to manageability.
>>>>>
>>>>> RTCP SR, RR and more particularly XR (e.g. VoIP Metrics report
>>>>> block)
>>>>> contain useful information for network monitoring, and are often
>>>>> used by
>>>>> probes and analyzers to support problem diagnosis.  RFC3711 allows
>>>>> the
>>>>> selective encryption of RTCP payloads and hence I would strongly
>>>>> recomment
>>>>> that RFC3711 implementors DO NOT encrypt RTCP SR, RR and XR
>>>>> payloads
>>>>> as
>>>>> this
>>>>> adversely impacts manageability.
>>>>>
>>>>> Regards
>>>>>
>>>>> Alan Clark
>>>>> Telchemy
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Audio/Video Transport Working Group
>>>>> avt@ietf.org
>>>>> https://www1.ietf.org/mailman/listinfo/avt
>>>>>
>>>>> *******************************************************************
>>>>> *
>>>>> *
>>>>> ******
>>>> *
>>>>> ********************************
>>>>> This email and any files transmitted with it are confidential
>>>>> material.
>>>>> They are intended solely for the use of the designated individual
>>>>> or
>>>>> entity
>>>>> to whom they are addressed.
>>>>> If the reader of this message is not the intended recipient,
>>>>> you are hereby notified that any dissemination,use,
>>>>> distribution or copying of this communication is strictly
>>>>> prohibited
>>>>> and
>>>> may
>>>>> be unlawful.
>>>>>
>>>>> If you have received this email in error please notify
>>>>> postmaster@audiocodes.com and permanently delete the e-mail and
>>>>> files.
>>>>>
>>>>>
>>>>> *******************************************************************
>>>>> *
>>>>> *
>>>>> ******
>>>> *
>>>>> *******************************
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Audio/Video Transport Working Group
>>>>> avt@ietf.org
>>>>> https://www1.ietf.org/mailman/listinfo/avt
>>>>
>>>>
>>>> _______________________________________________
>>>> Audio/Video Transport Working Group
>>>> avt@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/avt
>>>>
>>> David R. Oran
>>> Cisco Fellow
>>> Cisco Systems
>>> 7 Ladyslipper Lane
>>> Acton, MA 01720 USA
>>> Tel: +1 978 264 2048
>>> Email: oran@cisco.com
>>>
>>>
>>> _______________________________________________
>>> Audio/Video Transport Working Group
>>> avt@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/avt
>>>
>>
>>
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www1.ietf.org/mailman/listinfo/avt
>>
>


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Fri Nov 26 16:47:27 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26496
	for <avt-archive@ietf.org>; Fri, 26 Nov 2004 16:47:27 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CXo0V-0008W1-Ld
	for avt-archive@ietf.org; Fri, 26 Nov 2004 16:51:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CXnqk-0003z7-V1; Fri, 26 Nov 2004 16:41:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CXnqI-0003sE-L4
	for avt@megatron.ietf.org; Fri, 26 Nov 2004 16:41:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26104
	for <avt@ietf.org>; Fri, 26 Nov 2004 16:41:24 -0500 (EST)
Received: from ns.live.com ([66.80.62.34])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXnue-0008Gq-CN
	for avt@ietf.org; Fri, 26 Nov 2004 16:45:56 -0500
Received: from ns.live.com (localhost.live.com [127.0.0.1])
	by ns.live.com (8.13.1/8.12.11) with ESMTP id iAQLfIiq046782
	for <avt@ietf.org>; Fri, 26 Nov 2004 13:41:19 -0800 (PST)
	(envelope-from rsf@ns.live.com)
Received: (from rsf@localhost)
	by ns.live.com (8.13.1/8.12.9/Submit) id iAQLfIxh046781;
	Fri, 26 Nov 2004 13:41:18 -0800 (PST) (envelope-from rsf)
Message-Id: <6.2.0.14.1.20041126132615.02962e40@localhost>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14
Date: Fri, 26 Nov 2004 13:40:52 -0800
To: avt@ietf.org
From: Ross Finlayson <finlayson@live.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: [AVT] The use of RFC 2190 vs. RFC 2429 for transporting H.263 video?
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab

The first paragraph of RFC 2429 notes that it is preferred over the older 
RFC 2190 payload format - even for transporting the 1996 version of H.263.

However, today I read a claim that several legacy H.323 videoconferencing 
systems (the names Polycom and Tandberg were mentioned) still use the older 
RFC 2190 payload format when sending H.263, and that some (perhaps 
different) videoconferencing systems will receive only the RFC 2190 payload 
format, and do not understand the RFC 2429 payload format 
("video/H263-1998") at all.

Can anyone confirm (or deny) this claim?  Basically, I'd like to know 
whether RFC 2190 is something that I (as an implementor of RTP-based 
software) should still be concerned with, or whether I can get away with 
supporting only RFC 2429?

	Ross.


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Sun Nov 28 03:40:55 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21372
	for <avt-archive@ietf.org>; Sun, 28 Nov 2004 03:40:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYKgJ-00019I-TD
	for avt-archive@ietf.org; Sun, 28 Nov 2004 03:45:45 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYKXF-0004py-QL; Sun, 28 Nov 2004 03:35:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYKVQ-0004bJ-Lp
	for avt@megatron.ietf.org; Sun, 28 Nov 2004 03:34:04 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20824
	for <avt@ietf.org>; Sun, 28 Nov 2004 03:33:58 -0500 (EST)
Received: from [212.179.22.140] (helo=imss.audiocodes.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYKZb-0000q1-0Z
	for avt@ietf.org; Sun, 28 Nov 2004 03:38:48 -0500
Received: from aclmsg.corp.audiocodes.com ([10.1.0.8]) by imss with InterScan
	Messaging Security Suite; Sun, 28 Nov 2004 11:39:54 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 28 Nov 2004 10:33:44 +0200
Message-ID: <79B4F738DDD4EF4F85A4641A0FE5EFD606CB89@aclmsg.corp.audiocodes.com>
Thread-Topic: RFC 3711 Key Derivation
Thread-Index: AcTVJPkR3j4RH2s3TD+/9uPRiVV8UA==
From: "Ofer Idan" <ofer.idan@audiocodes.com>
To: <avt@ietf.org>
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 453b1bfcf0292bffe4cab90ba115f503
Cc: Yuval Nissan <YuvalN@audiocodes.com>
Subject: [AVT] RFC 3711 Key Derivation
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2002528349=="
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: a0ecb232550b38fd41a3cf6a312fbabc

This is a multi-part message in MIME format.

--===============2002528349==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4D524.F8FC511B"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4D524.F8FC511B
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Hi,

=0D

I have a question regarding RFC 3711 Key derivation rate.

=0D

In section 3.3 the decrypt process is described:

=0D

Bullet (4) says to determine the session keys using the maser key,
master salt, key derivation rate.

Bullet (5) says to check for anti reply, verify authentication.

=0D

I think that there might be a problem here.=0D

=0D

Consider a scenario where Key derivation rate is supported (different
than zero).

=0D

An attacker can send a packet with a higher sequence number that will
cause the receiver to change his session keys (according to key
derivation rate).

>From this moment on, the two sides will be unsynchronized and the
conversation will end.

=0D

Therefore I think that before updating the session keys the receiver
must first verify the message (and the sequence number) and only if
verified he should update all the keys.

=0D

Further more;

I think that when supporting key derivation rate, authentication must be
applied. (otherwise the receiver is vulnerable to such attack)

=0D

What do you think ?

------------------

Regards,

Ofer Idan

Audio Codes

=0D



***************************************************************************=
*********************************
This email and any files transmitted with it are confidential material.
They are intended solely for the use of the designated individual or entity=
 to whom they are addressed.
If the reader of this message is not the intended recipient,
you are hereby notified that any dissemination,use,
distribution or copying of this communication is strictly prohibited and=
 may be unlawful.

If you have received this email in error please notify=
 postmaster@audiocodes.com and permanently delete the e-mail and files.


***************************************************************************=
********************************
------_=_NextPart_001_01C4D524.F8FC511B
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>Hi,</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>I have a question regarding RFC 3711 Key derivation=
 rate.</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>In section 3.3 the decrypt process is=
 described:</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>Bullet (4) says to determine the session keys using the
maser key, master salt, key derivation rate.</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>Bullet (5) says to check for anti reply, verify
authentication.</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>I think that there might be a problem here.=
 </span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>Consider a scenario where Key derivation rate is=
 supported (different
than zero).</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>An attacker can send a packet with a higher sequence=
 number
that will cause the receiver to change his session keys (according to key
derivation rate).</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>From this moment on, the two sides will be=
 unsynchronized and
the conversation will end.</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>Therefore I think that before updating the session keys=
 the receiver
must first verify the message (and the sequence number) and only if=
 verified he
should update all the keys.</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>Further more;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>I think that when supporting key derivation rate,
authentication must be applied. (otherwise the receiver is vulnerable to=
 such
attack)</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>What do you think ?</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>------------------</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>Regards,</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>Ofer Idan</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>Audio Codes</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=
=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

</div>

</body>

</html>

<table><tr><td bgcolor=3D#ffffff><font color=
=3D#000000>****************************************************************=
********************************************<br>This email and any files=
 transmitted with it are confidential material.<br>They are intended solely=
 for the use of the designated individual or entity to whom they are=
 addressed.<br>If the reader of this message is not the intended=
 recipient,<br>you are hereby notified that any=
 dissemination,use,<br>distribution or copying of this communication is=
 strictly prohibited and may be unlawful.<br><br>If you have received this=
 email in error please notify postmaster@audiocodes.com and permanently=
 delete the e-mail and=
 files.<br><br><br>********************************************************=
***************************************************<br></font></td></tr></t=
able>
------_=_NextPart_001_01C4D524.F8FC511B--


--===============2002528349==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

--===============2002528349==--



From avt-bounces@ietf.org  Sun Nov 28 17:43:26 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22448
	for <avt-archive@ietf.org>; Sun, 28 Nov 2004 17:43:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYXqD-0007TK-Lo
	for avt-archive@ietf.org; Sun, 28 Nov 2004 17:48:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYXkF-00005p-Ki; Sun, 28 Nov 2004 17:42:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYXgJ-00082Z-2q
	for avt@megatron.ietf.org; Sun, 28 Nov 2004 17:38:11 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22028
	for <avt@ietf.org>; Sun, 28 Nov 2004 17:38:08 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYXl4-0007NL-Ky for avt@ietf.org; Sun, 28 Nov 2004 17:43:07 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 28 Nov 2004 14:43:30 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iASMbaf3008413;
	Sun, 28 Nov 2004 14:37:36 -0800 (PST)
Received: from [192.168.0.13] (sjc-vpn1-1092.cisco.com [10.21.100.68])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id iASMbEfd021549;
	Sun, 28 Nov 2004 14:37:14 -0800
In-Reply-To: <79B4F738DDD4EF4F85A4641A0FE5EFD606CB89@aclmsg.corp.audiocodes.com>
References: <79B4F738DDD4EF4F85A4641A0FE5EFD606CB89@aclmsg.corp.audiocodes.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <1971A2FC-418E-11D9-8EAB-000A95DC10F2@cisco.com>
Content-Transfer-Encoding: quoted-printable
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [AVT] RFC 3711 Key Derivation
Date: Sun, 28 Nov 2004 14:37:35 -0800
To: "Ofer Idan" <ofer.idan@audiocodes.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1101681435.238860"; x:"432200"; a:"rsa-sha1"; b:"nofws:2518";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"k7UXtVmXz5q0yhFYdsP8pfQeIOHjdC/TolWuOEOZVoHYcdGLIZHjkiV3l+0SS"
	"12afhsZ1L2M7jJ1mlNoGo71/4ZgLWMOEVSpZ0R0aPC8+SgSdOD9QrC0nqvhZK"
	"jB5rV36Fkp95n8qT9LTpDc2rym9DHuCKjeUCbHoaohiQYWT6c=";
	c:"From: Mark Baugher <mbaugher@cisco.com>";
	c:"Subject: Re: [AVT] RFC 3711 Key Derivation";
	c:"Date: Sun, 28 Nov 2004 14:37:35 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Content-Transfer-Encoding: quoted-printable
Cc: Yuval Nissan <YuvalN@audiocodes.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Content-Transfer-Encoding: quoted-printable

hi
On Nov 28, 2004, at 12:33 AM, Ofer Idan wrote:

> Hi,
>
> =A0
>
> I have a question regarding RFC 3711 Key derivation rate.
>
> =A0
>
> In section 3.3 the decrypt process is described:
>
> =A0
>
> Bullet (4) says to determine the session keys using the maser key, =20
> master salt, key derivation rate.
>
> Bullet (5) says to check for anti reply, verify authentication.
>
> =A0
>
> I think that there might be a problem here.
>
>  =A0
>
> Consider a scenario where Key derivation rate is supported (different =20=

> than zero).
>
> =A0
>
> An attacker can send a packet with a higher sequence number that will =20=

> cause the receiver to change his session keys (according to key =20
> derivation rate).

The attacker's packet won't verify upon receipt when the session is =20
integrity protected and will be rejected.  (Hence the importance of =20
integrity protection).

Mark
>
> =46rom this moment on, the two sides will be unsynchronized and the =20=

> conversation will end.
>
> =A0
>
> Therefore I think that before updating the session keys the receiver =20=

> must first verify the message (and the sequence number) and only if =20=

> verified he should update all the keys.
>
> =A0
>
> Further more;
>
> I think that when supporting key derivation rate, authentication must =20=

> be applied. (otherwise the receiver is vulnerable to such attack)
>
> =A0
>
> What do you think ?
>
> ------------------
>
> Regards,
>
> Ofer Idan
>
> Audio Codes
>
> =A0
>
> =
***********************************************************************=20=

> *************************************
> This email and any files transmitted with it are confidential =
material.
> They are intended solely for the use of the designated individual or =20=

> entity to whom they are addressed.
> If the reader of this message is not the intended recipient,
> you are hereby notified that any dissemination,use,
> distribution or copying of this communication is strictly prohibited =20=

> and may be unlawful.
>
> If you have received this email in error please notify =20
> postmaster@audiocodes.com and permanently delete the e-mail and files.
>
>
> =
***********************************************************************=20=

> ************************************
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov 29 00:03:31 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25582
	for <avt-archive@ietf.org>; Mon, 29 Nov 2004 00:03:30 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYdm5-0007E8-5T
	for avt-archive@ietf.org; Mon, 29 Nov 2004 00:08:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYdcX-0005R4-74; Sun, 28 Nov 2004 23:58:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYdZf-0004NA-Hs
	for avt@megatron.ietf.org; Sun, 28 Nov 2004 23:55:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24881
	for <avt@ietf.org>; Sun, 28 Nov 2004 23:55:41 -0500 (EST)
Received: from mail3.microsoft.com ([131.107.3.123])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYdeV-0006t7-AQ
	for avt@ietf.org; Mon, 29 Nov 2004 00:00:43 -0500
Received: from mailout2.microsoft.com ([157.54.1.120]) by mail3.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Sun, 28 Nov 2004 20:55:11 -0800
Received: from red-hub-04.redmond.corp.microsoft.com ([157.54.3.6]) by
	mailout2.microsoft.com with Microsoft SMTPSVC(6.0.3790.211); 
	Sun, 28 Nov 2004 20:55:12 -0800
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com
	([157.54.0.39]) by red-hub-04.redmond.corp.microsoft.com with
	Microsoft SMTPSVC(6.0.3790.211); Sun, 28 Nov 2004 20:55:10 -0800
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com
	([157.54.12.81]) by
	win-imc-01.wingroup.windeploy.ntdev.microsoft.com with
	Microsoft SMTPSVC(6.0.3790.1277); Sun, 28 Nov 2004 20:55:10 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] The use of RFC 2190 vs. RFC 2429 for transporting H.263
	video?
Date: Sun, 28 Nov 2004 20:55:10 -0800
Message-ID: <91D7F2CEE3425A4A9D11311D09FCE2460C0EDADF@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: [AVT] The use of RFC 2190 vs. RFC 2429 for transporting H.263
	video?
thread-index: AcTUAaPhqzez1b08SCiySbJhiww9cABCYqKA
From: "Gary Sullivan" <garysull@windows.microsoft.com>
To: "Ross Finlayson" <finlayson@live.com>, <avt@ietf.org>
X-OriginalArrivalTime: 29 Nov 2004 04:55:10.0509 (UTC)
	FILETIME=[9AC9F5D0:01C4D5CF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: quoted-printable
Cc: Arild Fuldseth <arild.fuldseth@tandberg.net>,
        =?iso-8859-1?Q?Gisle_Bj=F8nteg=E5rd?= <gisle.bjontegaard@tandberg.net>,
        Dave Lindbergh <lindbergh@92F1.com>,
        John Sievers <John.Sievers@polycom.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: quoted-printable

Polycom & Tandberg -- you probably know how to answer your =
company-specific part of this.

It is probably true that there are still some systems that use the =
legacy format, so it may still be useful to support RFC 2190 in a system =
(in fact it might even be mandatory in ITU-T systems, I'm not sure).  =
However, it is also clear that RFC 2429 is preferred.

Best Regards,

Gary Sullivan

+> -----Original Message-----
+> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On=20
+> Behalf Of Ross Finlayson
+> Sent: Friday, November 26, 2004 1:41 PM
+> To: avt@ietf.org
+> Subject: [AVT] The use of RFC 2190 vs. RFC 2429 for=20
+> transporting H.263 video?
+>=20
+> The first paragraph of RFC 2429 notes that it is preferred=20
+> over the older=20
+> RFC 2190 payload format - even for transporting the 1996=20
+> version of H.263.
+>=20
+> However, today I read a claim that several legacy H.323=20
+> videoconferencing=20
+> systems (the names Polycom and Tandberg were mentioned)=20
+> still use the older=20
+> RFC 2190 payload format when sending H.263, and that some (perhaps=20
+> different) videoconferencing systems will receive only the=20
+> RFC 2190 payload=20
+> format, and do not understand the RFC 2429 payload format=20
+> ("video/H263-1998") at all.
+>=20
+> Can anyone confirm (or deny) this claim?  Basically, I'd=20
+> like to know=20
+> whether RFC 2190 is something that I (as an implementor of RTP-based=20
+> software) should still be concerned with, or whether I can=20
+> get away with=20
+> supporting only RFC 2429?
+>=20
+> 	Ross.
+>=20
+>=20
+> _______________________________________________
+> Audio/Video Transport Working Group
+> avt@ietf.org
+> https://www1.ietf.org/mailman/listinfo/avt
+>=20

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov 29 01:34:39 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04742
	for <avt-archive@ietf.org>; Mon, 29 Nov 2004 01:34:39 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYfCH-0000ox-Bp
	for avt-archive@ietf.org; Mon, 29 Nov 2004 01:39:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYf60-0000TQ-JZ; Mon, 29 Nov 2004 01:33:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYf1r-0007oC-IX
	for avt@megatron.ietf.org; Mon, 29 Nov 2004 01:28:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04367
	for <avt@ietf.org>; Mon, 29 Nov 2004 01:28:55 -0500 (EST)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYf6i-0000ij-AQ
	for avt@ietf.org; Mon, 29 Nov 2004 01:33:56 -0500
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate8.mot.com (Motorola/Motgate8) with ESMTP id iAT6USNi028322
	for <avt@ietf.org>; Sun, 28 Nov 2004 23:30:28 -0700 (MST)
Received: from zin24exm01.ap.mot.com (zin24exm01.ap.mot.com [10.232.25.1])
	by az33exr02.mot.com (Motorola/az33exr02) with ESMTP id iAT6Q8nh014657
	for <avt@ietf.org>; Mon, 29 Nov 2004 00:26:09 -0600
Received: by zin24exm01.ap.mot.com with Internet Mail Service (5.5.2657.72)
	id <WYWRYF4H>; Mon, 29 Nov 2004 11:58:02 +0530
Message-ID: <772BCEF88A1DD91191F80011856715F3245B4A@zin24exm01.ap.mot.com>
From: Vavilapalli Srikanth-A19563 <srikanthv@motorola.com>
To: "'Mark Baugher'" <mbaugher@cisco.com>,
        Ofer Idan <ofer.idan@audiocodes.com>
Subject: RE: [AVT] RFC 3711 Key Derivation
Date: Mon, 29 Nov 2004 11:58:01 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
Content-Transfer-Encoding: quoted-printable
Cc: Yuval Nissan <YuvalN@audiocodes.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
Content-Transfer-Encoding: quoted-printable

Idan

I think the initial sequence number (SEQ) and ROC of the session must =
be
communicated to the other participants in the case non-zero key =
derivation
rate using some out-of-band signaling.=20

If not (i.e. if SEQ number is not communicated), even the integrity
protection also can not avoid the out of sync issues. The integrity
protection helps the receiver to drop the attacker's packet, but also =
makes
receiver to drop the actual sender's packets, because receiver uses
different session key than the sender's.=20

Regards
Srikanth


-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of =
Mark
Baugher
Sent: Monday, November 29, 2004 4:08 AM
To: Ofer Idan
Cc: Yuval Nissan; avt@ietf.org
Subject: Re: [AVT] RFC 3711 Key Derivation

hi
On Nov 28, 2004, at 12:33 AM, Ofer Idan wrote:

> Hi,
>
> =A0
>
> I have a question regarding RFC 3711 Key derivation rate.
>
> =A0
>
> In section 3.3 the decrypt process is described:
>
> =A0
>
> Bullet (4) says to determine the session keys using the maser key, =20
> master salt, key derivation rate.
>
> Bullet (5) says to check for anti reply, verify authentication.
>
> =A0
>
> I think that there might be a problem here.
>
>  =A0
>
> Consider a scenario where Key derivation rate is supported (different =
=20
> than zero).
>
> =A0
>
> An attacker can send a packet with a higher sequence number that will =
=20
> cause the receiver to change his session keys (according to key =20
> derivation rate).

The attacker's packet won't verify upon receipt when the session is =20
integrity protected and will be rejected.  (Hence the importance of =20
integrity protection).

Mark
>
> From this moment on, the two sides will be unsynchronized and the =20
> conversation will end.
>
> =A0
>
> Therefore I think that before updating the session keys the receiver  =

> must first verify the message (and the sequence number) and only if =20
> verified he should update all the keys.
>
> =A0
>
> Further more;
>
> I think that when supporting key derivation rate, authentication must =
=20
> be applied. (otherwise the receiver is vulnerable to such attack)
>
> =A0
>
> What do you think ?
>
> ------------------
>
> Regards,
>
> Ofer Idan
>
> Audio Codes
>
> =A0
>
> =
*********************************************************************** =

> *************************************
> This email and any files transmitted with it are confidential =
material.
> They are intended solely for the use of the designated individual or  =

> entity to whom they are addressed.
> If the reader of this message is not the intended recipient,
> you are hereby notified that any dissemination,use,
> distribution or copying of this communication is strictly prohibited  =

> and may be unlawful.
>
> If you have received this email in error please notify =20
> postmaster@audiocodes.com and permanently delete the e-mail and =
files.
>
>
> =
*********************************************************************** =

> ************************************
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov 29 07:40:36 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13635
	for <avt-archive@ietf.org>; Mon, 29 Nov 2004 07:40:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYkuS-0007tj-Pa
	for avt-archive@ietf.org; Mon, 29 Nov 2004 07:45:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYkfe-0000nI-4n; Mon, 29 Nov 2004 07:30:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYkcK-0008Sg-OX
	for avt@megatron.ietf.org; Mon, 29 Nov 2004 07:26:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06974
	for <avt@ietf.org>; Mon, 29 Nov 2004 06:16:30 -0500 (EST)
Received: from prix.tandberg.no ([194.196.35.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYjaq-00069F-F7
	for avt@ietf.org; Mon, 29 Nov 2004 06:21:36 -0500
Received: from tvpc.lysaker.tandberg.net (tvpc.lysaker.tandberg.net
	[10.47.12.255])
	by prix.tandberg.no (8.12.10/8.12.10) with ESMTP id iATBFgqS020851;
	Mon, 29 Nov 2004 12:15:42 +0100
Received: by tvpc.lysaker.tandberg.net (Postfix, from userid 502)
	id B4F357C200; Mon, 29 Nov 2004 12:16:18 +0100 (CET)
To: Ross Finlayson <finlayson@live.com>
Subject: Re: [AVT] The use of RFC 2190 vs. RFC 2429 for transporting H.263
	video?
References: <6.2.0.14.1.20041126132615.02962e40@localhost>
From: Terje Vernly <terje.vernly@tandberg.net>
Date: 29 Nov 2004 12:16:18 +0100
In-Reply-To: <6.2.0.14.1.20041126132615.02962e40@localhost>
Message-ID: <m1pt1wrjlp.fsf@tvpc.lysaker.tandberg.net>
Lines: 30
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Scanned-By: MIMEDefang 2.45
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17

Ross Finlayson <finlayson@live.com> writes:

> The first paragraph of RFC 2429 notes that it is preferred over the
> older RFC 2190 payload format - even for transporting the 1996 version
> of H.263.
> 
> However, today I read a claim that several legacy H.323
> videoconferencing systems (the names Polycom and Tandberg were
> mentioned) still use the older RFC 2190 payload format when sending
> H.263, and that some (perhaps different) videoconferencing systems
> will receive only the RFC 2190 payload format, and do not understand
> the RFC 2429 payload format ("video/H263-1998") at all.
 
> Can anyone confirm (or deny) this claim?  Basically, I'd like to know
> whether RFC 2190 is something that I (as an implementor of RTP-based
> software) should still be concerned with, or whether I can get away
> with supporting only RFC 2429?

Support for RFC2190 is mandatory for systems conforming to ITU-T
H.323.  Support for other packetization methods has to be signalled
explicitly within the capability exchange procedure and within logical
channel messaging.

In real life, H.323-systems that don't utilize the features of
H.263+(+) will most likely not support reception of RFC2429 packetized
H.263.

-- 
Terje Vernly
TANDBERG

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov 29 07:48:24 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14499
	for <avt-archive@ietf.org>; Mon, 29 Nov 2004 07:48:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYl1p-00086b-UT
	for avt-archive@ietf.org; Mon, 29 Nov 2004 07:53:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYkgI-0001Aa-0P; Mon, 29 Nov 2004 07:31:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYke5-0000SF-Ms
	for avt@megatron.ietf.org; Mon, 29 Nov 2004 07:28:45 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00582
	for <avt@ietf.org>; Mon, 29 Nov 2004 04:36:56 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYi2S-00049o-4j
	for avt@ietf.org; Mon, 29 Nov 2004 04:42:00 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iAT9abR2003345 for <avt@ietf.org>; Mon, 29 Nov 2004 10:36:37 +0100
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 29 Nov 2004 10:36:37 +0100
Received: from ericsson.com (research-64de67.ki.sw.ericsson.se
	[147.214.118.190]) by esealnt611.al.sw.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id WHLTP4AY; Mon, 29 Nov 2004 10:36:37 +0100
Message-ID: <41AAEDA5.2070107@ericsson.com>
Date: Mon, 29 Nov 2004 10:36:37 +0100
X-Sybari-Trust: b9ae3ce8 a5e9b67f 2b3f5727 00000139
From: =?ISO-8859-1?Q?Mats_N=E4slund?= <mats.naslund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ofer Idan <ofer.idan@audiocodes.com>
Subject: Re: [AVT] RFC 3711 Key Derivation
References: <79B4F738DDD4EF4F85A4641A0FE5EFD606CB89@aclmsg.corp.audiocodes.com>
In-Reply-To: <79B4F738DDD4EF4F85A4641A0FE5EFD606CB89@aclmsg.corp.audiocodes.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Nov 2004 09:36:37.0631 (UTC)
	FILETIME=[EC4C48F0:01C4D5F6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit
Cc: Yuval Nissan <YuvalN@audiocodes.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: 7bit

Hi Ofer,

Ofer Idan wrote:

> I have a question regarding RFC 3711 Key derivation rate.
> 
> In section 3.3 the decrypt process is described:
> 
> Bullet (4) says to determine the session keys using the maser key, 
> master salt, key derivation rate.
> 
> Bullet (5) says to check for anti reply, verify authentication.
> 
> I think that there might be a problem here.
> 
> Consider a scenario where Key derivation rate is supported (different 
> than zero).
> 
> An attacker can send a packet with a higher sequence number that will 
> cause the receiver to change his session keys (according to key 
> derivation rate).

Yes, they will be changed when processing *this* packet.

> 
>  From this moment on, the two sides will be unsynchronized and the 
> conversation will end.

This is not entirely true. As soon as a "correct" packet arrives,
the receiver will update his keys back to the correct value again.

> 
> Therefore I think that before updating the session keys the receiver 
> must first verify the message (and the sequence number) and only if 
> verified he should update all the keys.
> 

I would put it differently: for each packet received, the receiver
needs to determine whether key update is needed ot not. This holds
also when no attacker is present: re-ordering of packets could
occur anyway.

> Further more;
> 
> I think that when supporting key derivation rate, authentication must be 
> applied. (otherwise the receiver is vulnerable to such attack)
> 
>  
> 
> What do you think ?

Authentication should always be used.

Best,

/Mats


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov 29 09:03:06 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22069
	for <avt-archive@ietf.org>; Mon, 29 Nov 2004 09:03:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYmCK-0001u5-7Y
	for avt-archive@ietf.org; Mon, 29 Nov 2004 09:08:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYm2U-0001zy-N9; Mon, 29 Nov 2004 08:58:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYlsV-0000PH-CM
	for avt@megatron.ietf.org; Mon, 29 Nov 2004 08:47:45 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20691
	for <avt@ietf.org>; Mon, 29 Nov 2004 08:47:41 -0500 (EST)
Received: from [212.179.22.140] (helo=imss.audiocodes.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYlxP-0001UB-4l
	for avt@ietf.org; Mon, 29 Nov 2004 08:52:48 -0500
Received: from aclmsg.corp.audiocodes.com ([10.1.0.8]) by imss with InterScan
	Messaging Security Suite; Mon, 29 Nov 2004 16:54:04 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] RFC 3711 Key Derivation
Date: Mon, 29 Nov 2004 15:47:52 +0200
Message-ID: <79B4F738DDD4EF4F85A4641A0FE5EFD6096E5E@aclmsg.corp.audiocodes.com>
Thread-Topic: [AVT] RFC 3711 Key Derivation
Thread-Index: AcTWEbzjMlKQ4SlKTee6f/rdKWYNZQABhzIg
From: "Yuval Nissan" <YuvalN@audiocodes.com>
To: "Mats N?slund" <mats.naslund@ericsson.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Content-Transfer-Encoding: quoted-printable
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Content-Transfer-Encoding: quoted-printable


Hi,
Is there any recommendation for the key derivation rate in voice Unicast
session?

As understood form the previous mail the issue of key derivation isn't
that simple as to check whether index mod r equal zero (as written in
section 4.3.1). When we take into consideration possibility of
packet-loss and re-ordering we have to check wrap around of index mod r.

Do you agree?=0D

Thanks,
Yuval =0D

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
mats.naslund@ericsson.com
Sent: Monday, November 29, 2004 11:37 AM
To: Ofer Idan
Cc: Yuval Nissan; avt@ietf.org
Subject: Re: [AVT] RFC 3711 Key Derivation

Hi Ofer,

Ofer Idan wrote:

> I have a question regarding RFC 3711 Key derivation rate.
>=0D
> In section 3.3 the decrypt process is described:
>=0D
> Bullet (4) says to determine the session keys using the maser key,=0D
> master salt, key derivation rate.
>=0D
> Bullet (5) says to check for anti reply, verify authentication.
>=0D
> I think that there might be a problem here.
>=0D
> Consider a scenario where Key derivation rate is supported (different=0D
> than zero).
>=0D
> An attacker can send a packet with a higher sequence number that will=0D
> cause the receiver to change his session keys (according to key=0D
> derivation rate).

Yes, they will be changed when processing *this* packet.

>=0D
>  From this moment on, the two sides will be unsynchronized and the=0D
> conversation will end.

This is not entirely true. As soon as a "correct" packet arrives,
the receiver will update his keys back to the correct value again.

>=0D
> Therefore I think that before updating the session keys the receiver=0D
> must first verify the message (and the sequence number) and only if=0D
> verified he should update all the keys.
>=0D

I would put it differently: for each packet received, the receiver
needs to determine whether key update is needed ot not. This holds
also when no attacker is present: re-ordering of packets could
occur anyway.

> Further more;
>=0D
> I think that when supporting key derivation rate, authentication must
be=0D
> applied. (otherwise the receiver is vulnerable to such attack)
>=0D
> =0D
>=0D
> What do you think ?

Authentication should always be used.

Best,

/Mats


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

***************************************************************************=
*********************************
This email and any files transmitted with it are confidential material.
They are intended solely for the use of the designated individual or entity=
 to whom they are addressed.
If the reader of this message is not the intended recipient,
you are hereby notified that any dissemination,use,
distribution or copying of this communication is strictly prohibited and=
 may be unlawful.

If you have received this email in error please notify=
 postmaster@audiocodes.com and permanently delete the e-mail and files.


***************************************************************************=
********************************

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov 29 09:07:48 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22658
	for <avt-archive@ietf.org>; Mon, 29 Nov 2004 09:07:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYmGr-000228-RQ
	for avt-archive@ietf.org; Mon, 29 Nov 2004 09:12:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYm5q-0002sK-Kk; Mon, 29 Nov 2004 09:01:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYm0e-0001pf-9X
	for avt@megatron.ietf.org; Mon, 29 Nov 2004 08:56:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21426
	for <avt@ietf.org>; Mon, 29 Nov 2004 08:56:07 -0500 (EST)
Received: from [140.242.250.10] (helo=mojave)
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CYm5Y-0001hX-Us
	for avt@ietf.org; Mon, 29 Nov 2004 09:01:13 -0500
Message-Id: <6.1.2.0.2.20041129085359.02e4d640@pop.directnic.com>
X-Sender: lindbergh@92F1.com@pop.directnic.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Mon, 29 Nov 2004 08:55:32 -0500
To: "Gary Sullivan" <garysull@windows.microsoft.com>
From: Dave Lindbergh <lindbergh@92F1.com>
Subject: RE: [AVT] The use of RFC 2190 vs. RFC 2429 for transporting
	H.263 video?
In-Reply-To: <91D7F2CEE3425A4A9D11311D09FCE2460C0EDADF@WIN-MSG-10.wingro
	up.windeploy.ntdev.microsoft.com>
References: <91D7F2CEE3425A4A9D11311D09FCE2460C0EDADF@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: Arild Fuldseth <arild.fuldseth@tandberg.net>, Gisle,
        John Sievers <John.Sievers@polycom.com>,
        =?iso-8859-1?Q?Bj=F8nteg=E5rd?= <gisle.bjontegaard@tandberg.net>,
        Dave Lindbergh <lindbergh@92F1.com>, avt@ietf.org,
        Ross Finlayson <finlayson@live.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36

Hi all,

Speaking for Polycom, our equipment does both RFC 2190 and RFC 
2429.  Mostly RFC 2190 is used when transporting baseline H.263.

The main reason we continue to do this is to support older gear that did 
RFC 2190 only.

--Dave

At 11:55 PM 11/28/2004, Gary Sullivan wrote:
>Polycom & Tandberg -- you probably know how to answer your 
>company-specific part of this.
>
>It is probably true that there are still some systems that use the legacy 
>format, so it may still be useful to support RFC 2190 in a system (in fact 
>it might even be mandatory in ITU-T systems, I'm not sure).  However, it 
>is also clear that RFC 2429 is preferred.
>
>Best Regards,
>
>Gary Sullivan
>
>+> -----Original Message-----
>+> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
>+> Behalf Of Ross Finlayson
>+> Sent: Friday, November 26, 2004 1:41 PM
>+> To: avt@ietf.org
>+> Subject: [AVT] The use of RFC 2190 vs. RFC 2429 for
>+> transporting H.263 video?
>+>
>+> The first paragraph of RFC 2429 notes that it is preferred
>+> over the older
>+> RFC 2190 payload format - even for transporting the 1996
>+> version of H.263.
>+>
>+> However, today I read a claim that several legacy H.323
>+> videoconferencing
>+> systems (the names Polycom and Tandberg were mentioned)
>+> still use the older
>+> RFC 2190 payload format when sending H.263, and that some (perhaps
>+> different) videoconferencing systems will receive only the
>+> RFC 2190 payload
>+> format, and do not understand the RFC 2429 payload format
>+> ("video/H263-1998") at all.
>+>
>+> Can anyone confirm (or deny) this claim?  Basically, I'd
>+> like to know
>+> whether RFC 2190 is something that I (as an implementor of RTP-based
>+> software) should still be concerned with, or whether I can
>+> get away with
>+> supporting only RFC 2429?
>+>
>+>      Ross.
>+>
>+>
>+> _______________________________________________
>+> Audio/Video Transport Working Group
>+> avt@ietf.org
>+> https://www1.ietf.org/mailman/listinfo/avt
>+>

----------
Dave Lindbergh
Polycom, Inc.
100 Minuteman Road
Andover MA 01810  USA
Voice: +1 978 292 5366
Email: lindbergh@92F1.com
H.320, H.323 video by arrangement


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov 29 09:23:13 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23880
	for <avt-archive@ietf.org>; Mon, 29 Nov 2004 09:23:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYmVd-0002Px-6R
	for avt-archive@ietf.org; Mon, 29 Nov 2004 09:28:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYmBl-00047Y-GT; Mon, 29 Nov 2004 09:07:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYm5M-0002jV-6R
	for avt@megatron.ietf.org; Mon, 29 Nov 2004 09:01:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21893
	for <avt@ietf.org>; Mon, 29 Nov 2004 09:00:59 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYmA5-0001qr-VC
	for avt@ietf.org; Mon, 29 Nov 2004 09:06:05 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iATE0lh5003943
	for <avt@ietf.org>; Mon, 29 Nov 2004 15:00:47 +0100 (MET)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 29 Nov 2004 15:00:47 +0100
Received: from ericsson.com (research-64de67.ki.sw.ericsson.se
	[147.214.118.190]) by esealnt612.al.sw.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id XVC4LM2K; Mon, 29 Nov 2004 15:00:47 +0100
Message-ID: <41AB2B8F.1000701@ericsson.com>
Date: Mon, 29 Nov 2004 15:00:47 +0100
X-Sybari-Trust: ebefceb9 a5e9b67f 2b3f5727 00000139
From: =?ISO-8859-1?Q?Mats_N=E4slund?= <mats.naslund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Yuval Nissan <YuvalN@audiocodes.com>
Subject: Re: [AVT] RFC 3711 Key Derivation
References: <79B4F738DDD4EF4F85A4641A0FE5EFD6096E5E@aclmsg.corp.audiocodes.com>
In-Reply-To: <79B4F738DDD4EF4F85A4641A0FE5EFD6096E5E@aclmsg.corp.audiocodes.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Nov 2004 14:00:47.0507 (UTC)
	FILETIME=[D38F6E30:01C4D61B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit

Hi Yuval,

I can agree that the text

"The key derivation function [...] is performed whenever
index mod r equals zero."

is perhaps not the best choice of language. However, in the
more normative text that follows,

"key [...] for this packet SHALL then be derived [...] as follows:",

hopefully the use of "key for THIS packet" should make it
clear that there may be a need for a per-packet derivation.

I do not believe there's a general recommendation, the higher the
rate, the less "wear" on the key, but OTOH the more administration
and overhead.

Best,

/Mats

Yuval Nissan wrote:

> 
> Hi,
> Is there any recommendation for the key derivation rate in voice Unicast
> session?
> 
> As understood form the previous mail the issue of key derivation isn't
> that simple as to check whether index mod r equal zero (as written in
> section 4.3.1). When we take into consideration possibility of
> packet-loss and re-ordering we have to check wrap around of index mod r.
> 
> Do you agree?
> 
> 
> Thanks,
> Yuval
> 
> 


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov 29 09:31:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24822
	for <avt-archive@ietf.org>; Mon, 29 Nov 2004 09:31:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYmdt-0002gT-DL
	for avt-archive@ietf.org; Mon, 29 Nov 2004 09:36:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYmQV-0006o7-7W; Mon, 29 Nov 2004 09:22:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYmBc-00046i-4q
	for avt@megatron.ietf.org; Mon, 29 Nov 2004 09:07:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22618
	for <avt@ietf.org>; Mon, 29 Nov 2004 09:07:26 -0500 (EST)
Received: from fep2.012.net.il ([212.117.129.202])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYmGW-00020K-JM
	for avt@ietf.org; Mon, 29 Nov 2004 09:12:33 -0500
Received: from isrexch01.israel.polycom.com ([212.199.61.2])
	by fep2.012.net.il with ESMTP
	id <20041129140654.CBNH9868.fep2@isrexch01.israel.polycom.com>;
	Mon, 29 Nov 2004 16:06:54 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
Subject: RE: [AVT] The use of RFC 2190 vs. RFC 2429 for transporting
	H.263video?
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 29 Nov 2004 16:06:51 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C5C6ACB@IsrExch01.israel.polycom.com>
Thread-Topic: [AVT] The use of RFC 2190 vs. RFC 2429 for transporting
	H.263video?
Thread-Index: AcTWEXgwHvdFh/btQISUGacZVDtJaAACSJXQ
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Terje Vernly" <terje.vernly@tandberg.net>,
        "Ross Finlayson" <finlayson@live.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Content-Transfer-Encoding: quoted-printable
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Content-Transfer-Encoding: quoted-printable

Hi,
This is the text from H.225 version 5

Annex E
E.1	H.263
An RTP payload format for H.263 video is specified in IETF RFC 2190 for
H.263 video bitstreams that do not contain the new features adopted in
version 2 (the 1998 version) of ITU-T H.263 (the features using
PLUSPTYPE or annexes subsequent to Annex H/H.263). An additional payload
format which supports the enhanced features of H.263 version 2
bitstreams will be specified at a later date. A legacy packetization
format widely used in industry (not as specified in IETF RFC 2190) may
only be used if the peer indicated support for this format in the
capability exchange.



ANNEX I
H.263+ video packetization
IETF RFC 2429 specifies the RTP payload format for H.263 video
bitstreams that contain the new "H.263+" features adopted in version 2
(dated 1998) of ITU-T H.263 (includes the features using PLUSTYPE or
Annex I/H.263 through Annex T/H.263).
The ability to support the H.263 payload format of RFC 2190 as specified
in Annex E is required for H.263 bitstreams which do not use the new
version 2 features of ITU-T H.263, because this support is needed for
compatibility with prior implementations. However, the new payload
format specified in RFC 2429 should be used even for bitstreams which do
not contain the new version 2 features, provided the newer payload
format is within the capabilities of the receiving terminals.


As can be seen from both annexes RFC2190 is not mandated here and on the
other hand annex I has the same recommendation as RFC2429. Annexes in
ITU document are normative!!!.

As for what is happening in the SIP world. There are not many shipping
products. Microsoft window messenger supports video/H263 using RFC2190
and will not support H263-1998 using RFC2429. That is why we had to send
in our SDP both media type parameters.
The IETF would like to move RFC2190 to historic state. This will mean
that legacy systems may use it but the expectation is that the new
products will use RFC2429-bis (H263-1998) and thus may be able to use
the optional parameters specified in the bis drafts enabling specifying
of annexes as well as frame rate per specific resolution.

An example is shown, this works even though the H263 line is not correct
but is there due to some implementations that we encountered and it does
not break for endpoint who do not understand the second line for BW my
suggestion is to use the new TIAS to specify the exact BW

a=3Drtpmap:96 H263-1998/90000
a=3Dfmtp:96 CIF=3D1;QCIF=3D1;CIF4=3D2;SQCIF=3D1

a=3Drtpmap:34 H263/90000
a=3Dfmtp:34 CIF=3D1;QCIF=3D1;CIF4=3D2;SQCIF=3D1

b=3DTIAS=3D320000

Roni Even




-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Terje Vernly
Sent: Monday, November 29, 2004 1:16 PM
To: Ross Finlayson
Cc: avt@ietf.org
Subject: Re: [AVT] The use of RFC 2190 vs. RFC 2429 for transporting
H.263video?

Ross Finlayson <finlayson@live.com> writes:

> The first paragraph of RFC 2429 notes that it is preferred over the
> older RFC 2190 payload format - even for transporting the 1996 version
> of H.263.
>=20
> However, today I read a claim that several legacy H.323
> videoconferencing systems (the names Polycom and Tandberg were
> mentioned) still use the older RFC 2190 payload format when sending
> H.263, and that some (perhaps different) videoconferencing systems
> will receive only the RFC 2190 payload format, and do not understand
> the RFC 2429 payload format ("video/H263-1998") at all.
=20
> Can anyone confirm (or deny) this claim?  Basically, I'd like to know
> whether RFC 2190 is something that I (as an implementor of RTP-based
> software) should still be concerned with, or whether I can get away
> with supporting only RFC 2429?

Support for RFC2190 is mandatory for systems conforming to ITU-T
H.323.  Support for other packetization methods has to be signalled
explicitly within the capability exchange procedure and within logical
channel messaging.

In real life, H.323-systems that don't utilize the features of
H.263+(+) will most likely not support reception of RFC2429 packetized
H.263.

--=20
Terje Vernly
TANDBERG

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov 29 12:54:13 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14179
	for <avt-archive@ietf.org>; Mon, 29 Nov 2004 12:54:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYpo3-0007SY-77
	for avt-archive@ietf.org; Mon, 29 Nov 2004 12:59:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYpfo-0006M7-OL; Mon, 29 Nov 2004 12:50:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYpXd-0005MU-2t
	for avt@megatron.ietf.org; Mon, 29 Nov 2004 12:42:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13340
	for <avt@ietf.org>; Mon, 29 Nov 2004 12:42:22 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYpcY-0007DG-7l for avt@ietf.org; Mon, 29 Nov 2004 12:47:32 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 29 Nov 2004 10:48:47 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iATHfl9N002653;
	Mon, 29 Nov 2004 09:41:47 -0800 (PST)
Received: from [192.168.0.13] (sjc-vpn4-376.cisco.com [10.21.81.120])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id iATHfM6F025765;
	Mon, 29 Nov 2004 09:41:22 -0800
In-Reply-To: <772BCEF88A1DD91191F80011856715F3245B4A@zin24exm01.ap.mot.com>
References: <772BCEF88A1DD91191F80011856715F3245B4A@zin24exm01.ap.mot.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <F0EB9823-422D-11D9-868E-000A95DC10F2@cisco.com>
Content-Transfer-Encoding: quoted-printable
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [AVT] RFC 3711 Key Derivation
Date: Mon, 29 Nov 2004 09:41:46 -0800
To: Vavilapalli Srikanth-A19563 <srikanthv@motorola.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1101750082.910185"; x:"432200"; a:"rsa-sha1"; b:"nofws:4314";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"GuoTFkBYBVXcw2H2a7Ai2nhLqfVOo8+yKfb26jEi5LKbsV0oicHY9wx6hmEGo"
	"OG3YuPOcBcttGxjqsM74EYjYLtC4+IpEaB/VEfg8n1SCXfvSzE2vF2aAw3edz"
	"oQvVxl5YRHlsavwAXIcPfB9NWM+0p6xlMHbNB1chbgWle6rgg=";
	c:"From: Mark Baugher <mbaugher@cisco.com>";
	c:"Subject: Re: [AVT] RFC 3711 Key Derivation";
	c:"Date: Mon, 29 Nov 2004 09:41:46 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.2 (/)
X-Scan-Signature: cd3fc8e909678b38737fc606dec187f0
Content-Transfer-Encoding: quoted-printable
Cc: Yuval Nissan <YuvalN@audiocodes.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 21be852dc93f0971708678c18d38c096
Content-Transfer-Encoding: quoted-printable

hi

On Nov 28, 2004, at 10:28 PM, Vavilapalli Srikanth-A19563 wrote:

> Idan
>
> I think the initial sequence number (SEQ) and ROC of the session must =20=

> be
> communicated to the other participants in the case non-zero key =20
> derivation
> rate using some out-of-band signaling.

I hope it's not necessary to communicate the SEQ, which is a
very difficult thing to signal OOB.  Signaling the ROC for ongoing
sessions is bad enough.  The signaling layer typically does not have
access to this sort of state information.
>
> If not (i.e. if SEQ number is not communicated), even the integrity
> protection also can not avoid the out of sync issues. The integrity
> protection helps the receiver to drop the attacker's packet, but also =20=

> makes
> receiver to drop the actual sender's packets, because receiver uses
> different session key than the sender's.

The value of the SEQ in the validated packet with the ROC are enough =20
information
to identify and calculate the correct key (the SEQ is not encrypted so =20=

the
receiver can determine the key to use).  What am I missing?

Mark
>
>
> Regards
> Srikanth
>
>
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of =20=

> Mark
> Baugher
> Sent: Monday, November 29, 2004 4:08 AM
> To: Ofer Idan
> Cc: Yuval Nissan; avt@ietf.org
> Subject: Re: [AVT] RFC 3711 Key Derivation
>
> hi
> On Nov 28, 2004, at 12:33 AM, Ofer Idan wrote:
>
>> Hi,
>>
>> =A0
>>
>> I have a question regarding RFC 3711 Key derivation rate.
>>
>> =A0
>>
>> In section 3.3 the decrypt process is described:
>>
>> =A0
>>
>> Bullet (4) says to determine the session keys using the maser key,
>> master salt, key derivation rate.
>>
>> Bullet (5) says to check for anti reply, verify authentication.
>>
>> =A0
>>
>> I think that there might be a problem here.
>>
>>  =A0
>>
>> Consider a scenario where Key derivation rate is supported (different
>> than zero).
>>
>> =A0
>>
>> An attacker can send a packet with a higher sequence number that will
>> cause the receiver to change his session keys (according to key
>> derivation rate).
>
> The attacker's packet won't verify upon receipt when the session is
> integrity protected and will be rejected.  (Hence the importance of
> integrity protection).
>
> Mark
>>
>> =46rom this moment on, the two sides will be unsynchronized and the
>> conversation will end.
>>
>> =A0
>>
>> Therefore I think that before updating the session keys the receiver
>> must first verify the message (and the sequence number) and only if
>> verified he should update all the keys.
>>
>> =A0
>>
>> Further more;
>>
>> I think that when supporting key derivation rate, authentication must
>> be applied. (otherwise the receiver is vulnerable to such attack)
>>
>> =A0
>>
>> What do you think ?
>>
>> ------------------
>>
>> Regards,
>>
>> Ofer Idan
>>
>> Audio Codes
>>
>> =A0
>>
>> =
**********************************************************************=20=

>> *
>> *************************************
>> This email and any files transmitted with it are confidential =20
>> material.
>> They are intended solely for the use of the designated individual or
>> entity to whom they are addressed.
>> If the reader of this message is not the intended recipient,
>> you are hereby notified that any dissemination,use,
>> distribution or copying of this communication is strictly prohibited
>> and may be unlawful.
>>
>> If you have received this email in error please notify
>> postmaster@audiocodes.com and permanently delete the e-mail and =
files.
>>
>>
>> =
**********************************************************************=20=

>> *
>> ************************************
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www1.ietf.org/mailman/listinfo/avt
>
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov 29 12:56:10 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14258
	for <avt-archive@ietf.org>; Mon, 29 Nov 2004 12:56:09 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYppv-0007Vg-GY
	for avt-archive@ietf.org; Mon, 29 Nov 2004 13:01:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYpfs-0006Nu-Gy; Mon, 29 Nov 2004 12:50:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYpZN-0005Te-GM
	for avt@megatron.ietf.org; Mon, 29 Nov 2004 12:44:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13497
	for <avt@ietf.org>; Mon, 29 Nov 2004 12:44:10 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYpeK-0007Ez-2D for avt@ietf.org; Mon, 29 Nov 2004 12:49:20 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 29 Nov 2004 10:50:37 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iATHhc9N003889;
	Mon, 29 Nov 2004 09:43:39 -0800 (PST)
Received: from [192.168.0.13] (sjc-vpn4-376.cisco.com [10.21.81.120])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id iATHhEmV025775;
	Mon, 29 Nov 2004 09:43:14 -0800
In-Reply-To: <79B4F738DDD4EF4F85A4641A0FE5EFD6096E5E@aclmsg.corp.audiocodes.com>
References: <79B4F738DDD4EF4F85A4641A0FE5EFD6096E5E@aclmsg.corp.audiocodes.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <34326728-422E-11D9-868E-000A95DC10F2@cisco.com>
Content-Transfer-Encoding: 7bit
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [AVT] RFC 3711 Key Derivation
Date: Mon, 29 Nov 2004 09:43:39 -0800
To: "Yuval Nissan" <YuvalN@audiocodes.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1101750194.533454"; x:"432200"; a:"rsa-sha1"; b:"nofws:3619";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"TEltAH9g8qBj+LkpyVGdeDunOV7Z0nigJ5CxGhOxn+IbNCpk5C/ANNc/1l8rF"
	"Tmo0bKCtRx+X0a1EJM3u/ryXQtVHULDc60viNhPi4KOOJ3cGKiPrJNWGXAW2R"
	"aVsN/y1IRp4GfCucM1N9PhjnszOkTQcM/pcLnW+QXMXgNUIeA=";
	c:"From: Mark Baugher <mbaugher@cisco.com>";
	c:"Subject: Re: [AVT] RFC 3711 Key Derivation";
	c:"Date: Mon, 29 Nov 2004 09:43:39 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Content-Transfer-Encoding: 7bit
Cc: avt@ietf.org, Mats N?slund <mats.naslund@ericsson.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003
Content-Transfer-Encoding: 7bit


On Nov 29, 2004, at 5:47 AM, Yuval Nissan wrote:

>
> Hi,
> Is there any recommendation for the key derivation rate in voice  
> Unicast
> session?

The default is zero.  I would take that as a recommendation.

Mark

>
> As understood form the previous mail the issue of key derivation isn't
> that simple as to check whether index mod r equal zero (as written in
> section 4.3.1). When we take into consideration possibility of
> packet-loss and re-ordering we have to check wrap around of index mod  
> r.
>
> Do you agree?
>
> Thanks,
> Yuval
>
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> mats.naslund@ericsson.com
> Sent: Monday, November 29, 2004 11:37 AM
> To: Ofer Idan
> Cc: Yuval Nissan; avt@ietf.org
> Subject: Re: [AVT] RFC 3711 Key Derivation
>
> Hi Ofer,
>
> Ofer Idan wrote:
>
>> I have a question regarding RFC 3711 Key derivation rate.
>>
>> In section 3.3 the decrypt process is described:
>>
>> Bullet (4) says to determine the session keys using the maser key,
>> master salt, key derivation rate.
>>
>> Bullet (5) says to check for anti reply, verify authentication.
>>
>> I think that there might be a problem here.
>>
>> Consider a scenario where Key derivation rate is supported (different
>> than zero).
>>
>> An attacker can send a packet with a higher sequence number that will
>> cause the receiver to change his session keys (according to key
>> derivation rate).
>
> Yes, they will be changed when processing *this* packet.
>
>>
>>  From this moment on, the two sides will be unsynchronized and the
>> conversation will end.
>
> This is not entirely true. As soon as a "correct" packet arrives,
> the receiver will update his keys back to the correct value again.
>
>>
>> Therefore I think that before updating the session keys the receiver
>> must first verify the message (and the sequence number) and only if
>> verified he should update all the keys.
>>
>
> I would put it differently: for each packet received, the receiver
> needs to determine whether key update is needed ot not. This holds
> also when no attacker is present: re-ordering of packets could
> occur anyway.
>
>> Further more;
>>
>> I think that when supporting key derivation rate, authentication must
> be
>> applied. (otherwise the receiver is vulnerable to such attack)
>>
>>
>>
>> What do you think ?
>
> Authentication should always be used.
>
> Best,
>
> /Mats
>
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>
> *********************************************************************** 
> *************************************
> This email and any files transmitted with it are confidential material.
> They are intended solely for the use of the designated individual or  
> entity to whom they are addressed.
> If the reader of this message is not the intended recipient,
> you are hereby notified that any dissemination,use,
> distribution or copying of this communication is strictly prohibited  
> and may be unlawful.
>
> If you have received this email in error please notify  
> postmaster@audiocodes.com and permanently delete the e-mail and files.
>
>
> *********************************************************************** 
> ************************************
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Mon Nov 29 23:56:32 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21140
	for <avt-archive@ietf.org>; Mon, 29 Nov 2004 23:56:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZ095-0000z6-DA
	for avt-archive@ietf.org; Tue, 30 Nov 2004 00:01:47 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYzyS-0005dT-0K; Mon, 29 Nov 2004 23:50:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYzug-0004VU-5e
	for avt@megatron.ietf.org; Mon, 29 Nov 2004 23:46:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20416
	for <avt@ietf.org>; Mon, 29 Nov 2004 23:46:51 -0500 (EST)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYzzi-0000eT-OW
	for avt@ietf.org; Mon, 29 Nov 2004 23:52:07 -0500
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (Motorola/Motgate8) with ESMTP id iAU4mSNi004005
	for <avt@ietf.org>; Mon, 29 Nov 2004 21:48:28 -0700 (MST)
Received: from zin24exm01.ap.mot.com (zin24exm01.ap.mot.com [10.232.25.1])
	by il06exr03.mot.com (Motorola/il06exr03) with ESMTP id iAU4kn97011206
	for <avt@ietf.org>; Mon, 29 Nov 2004 22:46:50 -0600
Received: by zin24exm01.ap.mot.com with Internet Mail Service (5.5.2657.72)
	id <WYWRYPHH>; Tue, 30 Nov 2004 10:16:01 +0530
Message-ID: <772BCEF88A1DD91191F80011856715F3245B4E@zin24exm01.ap.mot.com>
From: Vavilapalli Srikanth-A19563 <srikanthv@motorola.com>
To: "'Mark Baugher'" <mbaugher@cisco.com>
Subject: RE: [AVT] RFC 3711 Key Derivation
Date: Tue, 30 Nov 2004 10:16:01 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.2 (/)
X-Scan-Signature: ff0adf256e4dd459cc25215cfa732ac1
Content-Transfer-Encoding: quoted-printable
Cc: Yuval Nissan <YuvalN@audiocodes.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: e367d58950869b6582535ddf5a673488
Content-Transfer-Encoding: quoted-printable

Mark

Please correct me if my understanding from the RFC3711 standard is =
wrong.=20

RFC3711 specifies a key derivation mechanism to be run for deriving the
session keys (k_e, k_a, k_s) which are used in encryption and =
authentication
process and must be executed once before media flow commencement and =
can be
refreshed depending on the Key derivation rate. This key derivation
mechanism uses the packet index as an input to the PRF algorithm.

First understanding from the above text is if Key derivation rate is =
"N"
(where N is a non-zero positive integer) means, the SRTP sender should
refresh/regenerate the session keys (k_e, k_s, k_a) for every "N" =
packets
sent. Am I right here? However, I am not clear on the receiver =
refreshing
its session keys. Will it also depend on the number of packets =
received? If
so how are the packet losses accounted in this calculation?

Second, the SRTP sender uses the packet index (ROC || SEQ) of the first
packet to derive the session keys (k_e, k_s, k_a), where ROC will be =
zero
and SEQ is a random number (not necessarily zero) used as initial =
sequence
number. This packet index will have impact on the key derivation only =
when
the derivation rate is non-zero positive integer. In the similar =
fashion, to
derive the same session keys at the receiving end, the receiver also =
should
use the same packet index to derive the session keys. With this
understanding I strongly believe that the receiver might get =
out-of-sync if
the initial packets of the session are lost, because the packet index
estimated at the receiver end might not be the same that is used at the
sender side to derive the session keys. How do we re-sync both parties =
in
this scenario?=20


-Srikanth



-----Original Message-----
From: Mark Baugher [mailto:mbaugher@cisco.com]=20
Sent: Monday, November 29, 2004 11:12 PM
To: Vavilapalli Srikanth-A19563
Cc: Ofer Idan; avt@ietf.org; Yuval Nissan
Subject: Re: [AVT] RFC 3711 Key Derivation

hi

On Nov 28, 2004, at 10:28 PM, Vavilapalli Srikanth-A19563 wrote:

> Idan
>
> I think the initial sequence number (SEQ) and ROC of the session must =
=20
> be
> communicated to the other participants in the case non-zero key =20
> derivation
> rate using some out-of-band signaling.

I hope it's not necessary to communicate the SEQ, which is a
very difficult thing to signal OOB.  Signaling the ROC for ongoing
sessions is bad enough.  The signaling layer typically does not have
access to this sort of state information.
>
> If not (i.e. if SEQ number is not communicated), even the integrity
> protection also can not avoid the out of sync issues. The integrity
> protection helps the receiver to drop the attacker's packet, but also =
=20
> makes
> receiver to drop the actual sender's packets, because receiver uses
> different session key than the sender's.

The value of the SEQ in the validated packet with the ROC are enough =20
information
to identify and calculate the correct key (the SEQ is not encrypted so  =

the
receiver can determine the key to use).  What am I missing?

Mark
>
>
> Regards
> Srikanth
>
>
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of =
=20
> Mark
> Baugher
> Sent: Monday, November 29, 2004 4:08 AM
> To: Ofer Idan
> Cc: Yuval Nissan; avt@ietf.org
> Subject: Re: [AVT] RFC 3711 Key Derivation
>
> hi
> On Nov 28, 2004, at 12:33 AM, Ofer Idan wrote:
>
>> Hi,
>>
>> =A0
>>
>> I have a question regarding RFC 3711 Key derivation rate.
>>
>> =A0
>>
>> In section 3.3 the decrypt process is described:
>>
>> =A0
>>
>> Bullet (4) says to determine the session keys using the maser key,
>> master salt, key derivation rate.
>>
>> Bullet (5) says to check for anti reply, verify authentication.
>>
>> =A0
>>
>> I think that there might be a problem here.
>>
>>  =A0
>>
>> Consider a scenario where Key derivation rate is supported =
(different
>> than zero).
>>
>> =A0
>>
>> An attacker can send a packet with a higher sequence number that =
will
>> cause the receiver to change his session keys (according to key
>> derivation rate).
>
> The attacker's packet won't verify upon receipt when the session is
> integrity protected and will be rejected.  (Hence the importance of
> integrity protection).
>
> Mark
>>
>> From this moment on, the two sides will be unsynchronized and the
>> conversation will end.
>>
>> =A0
>>
>> Therefore I think that before updating the session keys the receiver
>> must first verify the message (and the sequence number) and only if
>> verified he should update all the keys.
>>
>> =A0
>>
>> Further more;
>>
>> I think that when supporting key derivation rate, authentication =
must
>> be applied. (otherwise the receiver is vulnerable to such attack)
>>
>> =A0
>>
>> What do you think ?
>>
>> ------------------
>>
>> Regards,
>>
>> Ofer Idan
>>
>> Audio Codes
>>
>> =A0
>>
>> =
**********************************************************************=20
>> *
>> *************************************
>> This email and any files transmitted with it are confidential =20
>> material.
>> They are intended solely for the use of the designated individual or
>> entity to whom they are addressed.
>> If the reader of this message is not the intended recipient,
>> you are hereby notified that any dissemination,use,
>> distribution or copying of this communication is strictly prohibited
>> and may be unlawful.
>>
>> If you have received this email in error please notify
>> postmaster@audiocodes.com and permanently delete the e-mail and =
files.
>>
>>
>> =
**********************************************************************=20
>> *
>> ************************************
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www1.ietf.org/mailman/listinfo/avt
>
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Tue Nov 30 04:23:48 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24714
	for <avt-archive@ietf.org>; Tue, 30 Nov 2004 04:23:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZ4Jj-0006A7-KA
	for avt-archive@ietf.org; Tue, 30 Nov 2004 04:29:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZ409-0002Y3-1U; Tue, 30 Nov 2004 04:08:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZ3tk-0001Vj-Tc
	for avt@megatron.ietf.org; Tue, 30 Nov 2004 04:02:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22884
	for <avt@ietf.org>; Tue, 30 Nov 2004 04:02:10 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZ3yf-0005lJ-H8
	for avt@ietf.org; Tue, 30 Nov 2004 04:07:28 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iAU921R2015016 for <avt@ietf.org>; Tue, 30 Nov 2004 10:02:01 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 30 Nov 2004 10:02:01 +0100
Received: from ericsson.com (research-64de67.ki.sw.ericsson.se
	[147.214.118.190]) by esealnt612.al.sw.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id XVC4RN6W; Tue, 30 Nov 2004 10:02:00 +0100
Message-ID: <41AC3708.8030709@ericsson.com>
Date: Tue, 30 Nov 2004 10:02:00 +0100
X-Sybari-Trust: 5255e3ea a5e9b67f 50bbdbd0 00000139
From: =?ISO-8859-1?Q?Mats_N=E4slund?= <mats.naslund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Vavilapalli Srikanth-A19563 <srikanthv@motorola.com>
Subject: Re: [AVT] RFC 3711 Key Derivation
References: <772BCEF88A1DD91191F80011856715F3245B4E@zin24exm01.ap.mot.com>
In-Reply-To: <772BCEF88A1DD91191F80011856715F3245B4E@zin24exm01.ap.mot.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 30 Nov 2004 09:02:01.0013 (UTC)
	FILETIME=[40F34650:01C4D6BB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cdb443e3957ca9b4c5b55e78cfcf4b26
Content-Transfer-Encoding: 7bit
Cc: Yuval Nissan <YuvalN@audiocodes.com>, Mark Baugher <mbaugher@cisco.com>,
        avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 926f893f9bbbfa169f045f85f0cdb955
Content-Transfer-Encoding: 7bit

Hi,

I hope Mark excuses me for jumping in, but I can't resist
to give my explanation for why specific synch problem cannot occur
due to the key derivation. Please take a look at the RFC
on page 26. Here, you will see that for a given (just received)
packet, the keys (and salt etc) are given by:

	key = PRF_n(k_master, x),

(where key is k_s, k_a or k_e), and where in turn, x is of the form,

	x = salt XOR (<label> || index DIV key_derivation_rate).

If we "expand" this, you will get (unimportant stuff left out):

key = PRF_n(k_master, ... index DIV key_derivation_rate).

Note that index is determined by SEQ and ROC.  SEQ is carried
along with the packet and does not create problems. The only thing
that can go wrong is if the wrong ROC is used. This can happen
only if packet loss or reordering on the order of 2^15 packets
occurs. However, *if* ROC wrong, notice that ROC is also
part of the IV for the decryption, and it is also part of the
authenticated data, etc. Hence, even if the right keys were used,
decryption and/or authentication will fail anyway. When authentication 
fails, possible ROC update will be discarded. Therefore, the
problem with loosing synch on ROC is general, and the key derivation
does not make it worse, it shows precisely the same problem
as the rest of the protocol does in case of EXTREME loss or
re-order.

You could argue that authentication helps since it will assist
in avoiding false ROC updates. However, as long as we keep
using the wrong ROC on the receiver side, it does not help much
since decryption will just produce garbage anyway, and it is still
not until we somehow re-gain synch on the ROC value that the
protocol starts to work properly again.

Best,

/Mats

Vavilapalli Srikanth-A19563 wrote:

> Mark
> 
> Please correct me if my understanding from the RFC3711 standard is wrong.
> 
> RFC3711 specifies a key derivation mechanism to be run for deriving the
> session keys (k_e, k_a, k_s) which are used in encryption and 
> authentication
> process and must be executed once before media flow commencement and can be
> refreshed depending on the Key derivation rate. This key derivation
> mechanism uses the packet index as an input to the PRF algorithm.
> 
> First understanding from the above text is if Key derivation rate is "N"
> (where N is a non-zero positive integer) means, the SRTP sender should
> refresh/regenerate the session keys (k_e, k_s, k_a) for every "N" packets
> sent. Am I right here? However, I am not clear on the receiver refreshing
> its session keys. Will it also depend on the number of packets received? If
> so how are the packet losses accounted in this calculation?
> 
> Second, the SRTP sender uses the packet index (ROC || SEQ) of the first
> packet to derive the session keys (k_e, k_s, k_a), where ROC will be zero
> and SEQ is a random number (not necessarily zero) used as initial sequence
> number. This packet index will have impact on the key derivation only when
> the derivation rate is non-zero positive integer. In the similar 
> fashion, to
> derive the same session keys at the receiving end, the receiver also should
> use the same packet index to derive the session keys. With this
> understanding I strongly believe that the receiver might get out-of-sync if
> the initial packets of the session are lost, because the packet index
> estimated at the receiver end might not be the same that is used at the
> sender side to derive the session keys. How do we re-sync both parties in
> this scenario?
> 
> 
> -Srikanth
> 
> 
> 
> -----Original Message-----
> From: Mark Baugher [mailto:mbaugher@cisco.com]
> Sent: Monday, November 29, 2004 11:12 PM
> To: Vavilapalli Srikanth-A19563
> Cc: Ofer Idan; avt@ietf.org; Yuval Nissan
> Subject: Re: [AVT] RFC 3711 Key Derivation
> 
> hi
> 
> On Nov 28, 2004, at 10:28 PM, Vavilapalli Srikanth-A19563 wrote:
> 
>  > Idan
>  >
>  > I think the initial sequence number (SEQ) and ROC of the session must 
>  > be
>  > communicated to the other participants in the case non-zero key 
>  > derivation
>  > rate using some out-of-band signaling.
> 
> I hope it's not necessary to communicate the SEQ, which is a
> very difficult thing to signal OOB.  Signaling the ROC for ongoing
> sessions is bad enough.  The signaling layer typically does not have
> access to this sort of state information.
>  >
>  > If not (i.e. if SEQ number is not communicated), even the integrity
>  > protection also can not avoid the out of sync issues. The integrity
>  > protection helps the receiver to drop the attacker's packet, but also 
>  > makes
>  > receiver to drop the actual sender's packets, because receiver uses
>  > different session key than the sender's.
> 
> The value of the SEQ in the validated packet with the ROC are enough 
> information
> to identify and calculate the correct key (the SEQ is not encrypted so 
> the
> receiver can determine the key to use).  What am I missing?
> 
> Mark
>  >
>  >
>  > Regards
>  > Srikanth
>  >
>  >
>  > -----Original Message-----
>  > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of 
>  > Mark
>  > Baugher
>  > Sent: Monday, November 29, 2004 4:08 AM
>  > To: Ofer Idan
>  > Cc: Yuval Nissan; avt@ietf.org
>  > Subject: Re: [AVT] RFC 3711 Key Derivation
>  >
>  > hi
>  > On Nov 28, 2004, at 12:33 AM, Ofer Idan wrote:
>  >
>  >> Hi,
>  >>
>  >>  
>  >>
>  >> I have a question regarding RFC 3711 Key derivation rate.
>  >>
>  >>  
>  >>
>  >> In section 3.3 the decrypt process is described:
>  >>
>  >>  
>  >>
>  >> Bullet (4) says to determine the session keys using the maser key,
>  >> master salt, key derivation rate.
>  >>
>  >> Bullet (5) says to check for anti reply, verify authentication.
>  >>
>  >>  
>  >>
>  >> I think that there might be a problem here.
>  >>
>  >>   
>  >>
>  >> Consider a scenario where Key derivation rate is supported (different
>  >> than zero).
>  >>
>  >>  
>  >>
>  >> An attacker can send a packet with a higher sequence number that will
>  >> cause the receiver to change his session keys (according to key
>  >> derivation rate).
>  >
>  > The attacker's packet won't verify upon receipt when the session is
>  > integrity protected and will be rejected.  (Hence the importance of
>  > integrity protection).
>  >
>  > Mark
>  >>
>  >> From this moment on, the two sides will be unsynchronized and the
>  >> conversation will end.
>  >>
>  >>  
>  >>
>  >> Therefore I think that before updating the session keys the receiver
>  >> must first verify the message (and the sequence number) and only if
>  >> verified he should update all the keys.
>  >>
>  >>  
>  >>
>  >> Further more;
>  >>
>  >> I think that when supporting key derivation rate, authentication must
>  >> be applied. (otherwise the receiver is vulnerable to such attack)
>  >>
>  >>  
>  >>
>  >> What do you think ?
>  >>
>  >> ------------------
>  >>
>  >> Regards,
>  >>
>  >> Ofer Idan
>  >>
>  >> Audio Codes



_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Tue Nov 30 05:15:13 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00763
	for <avt-archive@ietf.org>; Tue, 30 Nov 2004 05:15:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZ57W-0007Ca-7u
	for avt-archive@ietf.org; Tue, 30 Nov 2004 05:20:31 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZ4q6-0004bY-3W; Tue, 30 Nov 2004 05:02:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZ4By-0003zQ-F9
	for avt@megatron.ietf.org; Tue, 30 Nov 2004 04:21:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24192
	for <avt@ietf.org>; Tue, 30 Nov 2004 04:21:00 -0500 (EST)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZ4H3-00066X-F0
	for avt@ietf.org; Tue, 30 Nov 2004 04:26:17 -0500
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate8.mot.com (Motorola/Motgate8) with ESMTP id iAU9MXNi003428
	for <avt@ietf.org>; Tue, 30 Nov 2004 02:22:33 -0700 (MST)
Received: from zin24exm01.ap.mot.com (zin24exm01.ap.mot.com [10.232.25.1])
	by az33exr02.mot.com (Motorola/az33exr02) with ESMTP id iAU9IDnh014264
	for <avt@ietf.org>; Tue, 30 Nov 2004 03:18:14 -0600
Received: by zin24exm01.ap.mot.com with Internet Mail Service (5.5.2657.72)
	id <WYWRYSHM>; Tue, 30 Nov 2004 14:50:07 +0530
Message-ID: <772BCEF88A1DD91191F80011856715F3245B50@zin24exm01.ap.mot.com>
From: Vavilapalli Srikanth-A19563 <srikanthv@motorola.com>
To: =?iso-8859-1?Q?=27Mats_N=E4slund=27?= <mats.naslund@ericsson.com>,
        Vavilapalli Srikanth-A19563 <srikanthv@motorola.com>
Subject: RE: [AVT] RFC 3711 Key Derivation
Date: Tue, 30 Nov 2004 14:50:06 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 155726d2f5fe5eb5c40a9f079fd9e841
Content-Transfer-Encoding: quoted-printable
Cc: Yuval Nissan <YuvalN@audiocodes.com>, Mark Baugher <mbaugher@cisco.com>,
        avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8cb9b411340046bf4080a729180a0672
Content-Transfer-Encoding: quoted-printable

Thanks a lot Mats.

Effectively you are saying that the RTP senders and receivers have to =
derive
the session keys (k_e, k_s, k_a) for "every packet" sent or received
respectively, not just once before session start. Am I right?

If that is the case, then I agree there will not be any out-of-sync =
issues
at-least in the session key derivation because of initial loss of =
packets.=20

NOTE: However, no where in the RFC (at-least from my understanding) =
says to
derive the session keys for every packet sent and received. It was =
saying to
derive the session once before session commencement and refresh the =
keys
whenever (index mod 2^key-derivation-rate) is zero. Isn't my =
understanding
right here?


Regards
Srikanth

-----Original Message-----
From: Mats N=E4slund [mailto:mats.naslund@ericsson.com]=20
Sent: Tuesday, November 30, 2004 2:32 PM
To: Vavilapalli Srikanth-A19563
Cc: Mark Baugher; Yuval Nissan; avt@ietf.org
Subject: Re: [AVT] RFC 3711 Key Derivation

Hi,

I hope Mark excuses me for jumping in, but I can't resist
to give my explanation for why specific synch problem cannot occur
due to the key derivation. Please take a look at the RFC
on page 26. Here, you will see that for a given (just received)
packet, the keys (and salt etc) are given by:

	key =3D PRF_n(k_master, x),

(where key is k_s, k_a or k_e), and where in turn, x is of the form,

	x =3D salt XOR (<label> || index DIV key_derivation_rate).

If we "expand" this, you will get (unimportant stuff left out):

key =3D PRF_n(k_master, ... index DIV key_derivation_rate).

Note that index is determined by SEQ and ROC.  SEQ is carried
along with the packet and does not create problems. The only thing
that can go wrong is if the wrong ROC is used. This can happen
only if packet loss or reordering on the order of 2^15 packets
occurs. However, *if* ROC wrong, notice that ROC is also
part of the IV for the decryption, and it is also part of the
authenticated data, etc. Hence, even if the right keys were used,
decryption and/or authentication will fail anyway. When authentication=20
fails, possible ROC update will be discarded. Therefore, the
problem with loosing synch on ROC is general, and the key derivation
does not make it worse, it shows precisely the same problem
as the rest of the protocol does in case of EXTREME loss or
re-order.

You could argue that authentication helps since it will assist
in avoiding false ROC updates. However, as long as we keep
using the wrong ROC on the receiver side, it does not help much
since decryption will just produce garbage anyway, and it is still
not until we somehow re-gain synch on the ROC value that the
protocol starts to work properly again.

Best,

/Mats

Vavilapalli Srikanth-A19563 wrote:

> Mark
>=20
> Please correct me if my understanding from the RFC3711 standard is =
wrong.
>=20
> RFC3711 specifies a key derivation mechanism to be run for deriving =
the
> session keys (k_e, k_a, k_s) which are used in encryption and=20
> authentication
> process and must be executed once before media flow commencement and =
can
be
> refreshed depending on the Key derivation rate. This key derivation
> mechanism uses the packet index as an input to the PRF algorithm.
>=20
> First understanding from the above text is if Key derivation rate is =
"N"
> (where N is a non-zero positive integer) means, the SRTP sender =
should
> refresh/regenerate the session keys (k_e, k_s, k_a) for every "N" =
packets
> sent. Am I right here? However, I am not clear on the receiver =
refreshing
> its session keys. Will it also depend on the number of packets =
received?
If
> so how are the packet losses accounted in this calculation?
>=20
> Second, the SRTP sender uses the packet index (ROC || SEQ) of the =
first
> packet to derive the session keys (k_e, k_s, k_a), where ROC will be =
zero
> and SEQ is a random number (not necessarily zero) used as initial =
sequence
> number. This packet index will have impact on the key derivation only =
when
> the derivation rate is non-zero positive integer. In the similar=20
> fashion, to
> derive the same session keys at the receiving end, the receiver also
should
> use the same packet index to derive the session keys. With this
> understanding I strongly believe that the receiver might get =
out-of-sync
if
> the initial packets of the session are lost, because the packet index
> estimated at the receiver end might not be the same that is used at =
the
> sender side to derive the session keys. How do we re-sync both =
parties in
> this scenario?
>=20
>=20
> -Srikanth
>=20
>=20
>=20
> -----Original Message-----
> From: Mark Baugher [mailto:mbaugher@cisco.com]
> Sent: Monday, November 29, 2004 11:12 PM
> To: Vavilapalli Srikanth-A19563
> Cc: Ofer Idan; avt@ietf.org; Yuval Nissan
> Subject: Re: [AVT] RFC 3711 Key Derivation
>=20
> hi
>=20
> On Nov 28, 2004, at 10:28 PM, Vavilapalli Srikanth-A19563 wrote:
>=20
>  > Idan
>  >
>  > I think the initial sequence number (SEQ) and ROC of the session =
must=20
>  > be
>  > communicated to the other participants in the case non-zero key=20
>  > derivation
>  > rate using some out-of-band signaling.
>=20
> I hope it's not necessary to communicate the SEQ, which is a
> very difficult thing to signal OOB.  Signaling the ROC for ongoing
> sessions is bad enough.  The signaling layer typically does not have
> access to this sort of state information.
>  >
>  > If not (i.e. if SEQ number is not communicated), even the =
integrity
>  > protection also can not avoid the out of sync issues. The =
integrity
>  > protection helps the receiver to drop the attacker's packet, but =
also=20
>  > makes
>  > receiver to drop the actual sender's packets, because receiver =
uses
>  > different session key than the sender's.
>=20
> The value of the SEQ in the validated packet with the ROC are enough=20
> information
> to identify and calculate the correct key (the SEQ is not encrypted =
so=20
> the
> receiver can determine the key to use).  What am I missing?
>=20
> Mark
>  >
>  >
>  > Regards
>  > Srikanth
>  >
>  >
>  > -----Original Message-----
>  > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf =
Of=20
>  > Mark
>  > Baugher
>  > Sent: Monday, November 29, 2004 4:08 AM
>  > To: Ofer Idan
>  > Cc: Yuval Nissan; avt@ietf.org
>  > Subject: Re: [AVT] RFC 3711 Key Derivation
>  >
>  > hi
>  > On Nov 28, 2004, at 12:33 AM, Ofer Idan wrote:
>  >
>  >> Hi,
>  >>
>  >> =20
>  >>
>  >> I have a question regarding RFC 3711 Key derivation rate.
>  >>
>  >> =20
>  >>
>  >> In section 3.3 the decrypt process is described:
>  >>
>  >> =20
>  >>
>  >> Bullet (4) says to determine the session keys using the maser =
key,
>  >> master salt, key derivation rate.
>  >>
>  >> Bullet (5) says to check for anti reply, verify authentication.
>  >>
>  >> =20
>  >>
>  >> I think that there might be a problem here.
>  >>
>  >>  =20
>  >>
>  >> Consider a scenario where Key derivation rate is supported =
(different
>  >> than zero).
>  >>
>  >> =20
>  >>
>  >> An attacker can send a packet with a higher sequence number that =
will
>  >> cause the receiver to change his session keys (according to key
>  >> derivation rate).
>  >
>  > The attacker's packet won't verify upon receipt when the session =
is
>  > integrity protected and will be rejected.  (Hence the importance =
of
>  > integrity protection).
>  >
>  > Mark
>  >>
>  >> From this moment on, the two sides will be unsynchronized and the
>  >> conversation will end.
>  >>
>  >> =20
>  >>
>  >> Therefore I think that before updating the session keys the =
receiver
>  >> must first verify the message (and the sequence number) and only =
if
>  >> verified he should update all the keys.
>  >>
>  >> =20
>  >>
>  >> Further more;
>  >>
>  >> I think that when supporting key derivation rate, authentication =
must
>  >> be applied. (otherwise the receiver is vulnerable to such attack)
>  >>
>  >> =20
>  >>
>  >> What do you think ?
>  >>
>  >> ------------------
>  >>
>  >> Regards,
>  >>
>  >> Ofer Idan
>  >>
>  >> Audio Codes


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Tue Nov 30 05:15:24 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00783
	for <avt-archive@ietf.org>; Tue, 30 Nov 2004 05:15:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZ57f-0007D0-Sj
	for avt-archive@ietf.org; Tue, 30 Nov 2004 05:20:43 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZ4rK-00059P-Sw; Tue, 30 Nov 2004 05:03:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZ4Ec-0004QW-Bl
	for avt@megatron.ietf.org; Tue, 30 Nov 2004 04:23:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24693
	for <avt@ietf.org>; Tue, 30 Nov 2004 04:23:44 -0500 (EST)
Received: from [212.179.22.140] (helo=imss.audiocodes.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZ4Jg-00069H-EW
	for avt@ietf.org; Tue, 30 Nov 2004 04:29:01 -0500
Received: from aclmsg.corp.audiocodes.com ([10.1.0.8]) by imss with InterScan
	Messaging Security Suite; Tue, 30 Nov 2004 12:30:02 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] RFC 3711 Key Derivation
Date: Tue, 30 Nov 2004 11:23:47 +0200
Message-ID: <79B4F738DDD4EF4F85A4641A0FE5EFD6096E5F@aclmsg.corp.audiocodes.com>
Thread-Topic: [AVT] RFC 3711 Key Derivation
Thread-Index: AcTWu12/pl1i3FkaSfaDH4rpHnLYUwAAXMHg
From: "Yuval Nissan" <YuvalN@audiocodes.com>
To: "Mats N?slund" <mats.naslund@ericsson.com>,
        "Vavilapalli Srikanth-A19563" <srikanthv@motorola.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: e5bfa71b340354e384155def5e70b13b
Content-Transfer-Encoding: quoted-printable
Cc: Mark Baugher <mbaugher@cisco.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: ba0d4c5f57f7c289496fce758bbf4798
Content-Transfer-Encoding: quoted-printable


Hi,
Also to avoid the ROC sync problem in the beginning of session, I saw in
the "Session Description Protocol Security Descriptions for Media
Streams" recommendation to limit the Tx Sequence Number to maximum
2^15-1. So this I think also needed to complete the picture...

Yuval

-----Original Message-----
From: mats.naslund@ericsson.com [mailto:mats.naslund@ericsson.com]=0D
Sent: Tuesday, November 30, 2004 11:02 AM
To: Vavilapalli Srikanth-A19563
Cc: Mark Baugher; Yuval Nissan; avt@ietf.org
Subject: Re: [AVT] RFC 3711 Key Derivation

Hi,

I hope Mark excuses me for jumping in, but I can't resist
to give my explanation for why specific synch problem cannot occur
due to the key derivation. Please take a look at the RFC
on page 26. Here, you will see that for a given (just received)
packet, the keys (and salt etc) are given by:

	key =3D PRF_n(k_master, x),

(where key is k_s, k_a or k_e), and where in turn, x is of the form,

	x =3D salt XOR (<label> || index DIV key_derivation_rate).

If we "expand" this, you will get (unimportant stuff left out):

key =3D PRF_n(k_master, ... index DIV key_derivation_rate).

Note that index is determined by SEQ and ROC.  SEQ is carried
along with the packet and does not create problems. The only thing
that can go wrong is if the wrong ROC is used. This can happen
only if packet loss or reordering on the order of 2^15 packets
occurs. However, *if* ROC wrong, notice that ROC is also
part of the IV for the decryption, and it is also part of the
authenticated data, etc. Hence, even if the right keys were used,
decryption and/or authentication will fail anyway. When authentication=0D
fails, possible ROC update will be discarded. Therefore, the
problem with loosing synch on ROC is general, and the key derivation
does not make it worse, it shows precisely the same problem
as the rest of the protocol does in case of EXTREME loss or
re-order.

You could argue that authentication helps since it will assist
in avoiding false ROC updates. However, as long as we keep
using the wrong ROC on the receiver side, it does not help much
since decryption will just produce garbage anyway, and it is still
not until we somehow re-gain synch on the ROC value that the
protocol starts to work properly again.

Best,

/Mats

Vavilapalli Srikanth-A19563 wrote:

> Mark
>=0D
> Please correct me if my understanding from the RFC3711 standard is
wrong.
>=0D
> RFC3711 specifies a key derivation mechanism to be run for deriving
the
> session keys (k_e, k_a, k_s) which are used in encryption and=0D
> authentication
> process and must be executed once before media flow commencement and
can be
> refreshed depending on the Key derivation rate. This key derivation
> mechanism uses the packet index as an input to the PRF algorithm.
>=0D
> First understanding from the above text is if Key derivation rate is
"N"
> (where N is a non-zero positive integer) means, the SRTP sender should
> refresh/regenerate the session keys (k_e, k_s, k_a) for every "N"
packets
> sent. Am I right here? However, I am not clear on the receiver
refreshing
> its session keys. Will it also depend on the number of packets
received? If
> so how are the packet losses accounted in this calculation?
>=0D
> Second, the SRTP sender uses the packet index (ROC || SEQ) of the
first
> packet to derive the session keys (k_e, k_s, k_a), where ROC will be
zero
> and SEQ is a random number (not necessarily zero) used as initial
sequence
> number. This packet index will have impact on the key derivation only
when
> the derivation rate is non-zero positive integer. In the similar=0D
> fashion, to
> derive the same session keys at the receiving end, the receiver also
should
> use the same packet index to derive the session keys. With this
> understanding I strongly believe that the receiver might get
out-of-sync if
> the initial packets of the session are lost, because the packet index
> estimated at the receiver end might not be the same that is used at
the
> sender side to derive the session keys. How do we re-sync both parties
in
> this scenario?
>=0D
>=0D
> -Srikanth
>=0D
>=0D
>=0D
> -----Original Message-----
> From: Mark Baugher [mailto:mbaugher@cisco.com]
> Sent: Monday, November 29, 2004 11:12 PM
> To: Vavilapalli Srikanth-A19563
> Cc: Ofer Idan; avt@ietf.org; Yuval Nissan
> Subject: Re: [AVT] RFC 3711 Key Derivation
>=0D
> hi
>=0D
> On Nov 28, 2004, at 10:28 PM, Vavilapalli Srikanth-A19563 wrote:
>=0D
>  > Idan
>  >
>  > I think the initial sequence number (SEQ) and ROC of the session
must=0D
>  > be
>  > communicated to the other participants in the case non-zero key=0D
>  > derivation
>  > rate using some out-of-band signaling.
>=0D
> I hope it's not necessary to communicate the SEQ, which is a
> very difficult thing to signal OOB.  Signaling the ROC for ongoing
> sessions is bad enough.  The signaling layer typically does not have
> access to this sort of state information.
>  >
>  > If not (i.e. if SEQ number is not communicated), even the integrity
>  > protection also can not avoid the out of sync issues. The integrity
>  > protection helps the receiver to drop the attacker's packet, but
also=0D
>  > makes
>  > receiver to drop the actual sender's packets, because receiver uses
>  > different session key than the sender's.
>=0D
> The value of the SEQ in the validated packet with the ROC are enough=0D
> information
> to identify and calculate the correct key (the SEQ is not encrypted so

> the
> receiver can determine the key to use).  What am I missing?
>=0D
> Mark
>  >
>  >
>  > Regards
>  > Srikanth
>  >
>  >
>  > -----Original Message-----
>  > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf
Of=0D
>  > Mark
>  > Baugher
>  > Sent: Monday, November 29, 2004 4:08 AM
>  > To: Ofer Idan
>  > Cc: Yuval Nissan; avt@ietf.org
>  > Subject: Re: [AVT] RFC 3711 Key Derivation
>  >
>  > hi
>  > On Nov 28, 2004, at 12:33 AM, Ofer Idan wrote:
>  >
>  >> Hi,
>  >>
>  >> =0D
>  >>
>  >> I have a question regarding RFC 3711 Key derivation rate.
>  >>
>  >> =0D
>  >>
>  >> In section 3.3 the decrypt process is described:
>  >>
>  >> =0D
>  >>
>  >> Bullet (4) says to determine the session keys using the maser key,
>  >> master salt, key derivation rate.
>  >>
>  >> Bullet (5) says to check for anti reply, verify authentication.
>  >>
>  >> =0D
>  >>
>  >> I think that there might be a problem here.
>  >>
>  >>  =0D
>  >>
>  >> Consider a scenario where Key derivation rate is supported
(different
>  >> than zero).
>  >>
>  >> =0D
>  >>
>  >> An attacker can send a packet with a higher sequence number that
will
>  >> cause the receiver to change his session keys (according to key
>  >> derivation rate).
>  >
>  > The attacker's packet won't verify upon receipt when the session is
>  > integrity protected and will be rejected.  (Hence the importance of
>  > integrity protection).
>  >
>  > Mark
>  >>
>  >> From this moment on, the two sides will be unsynchronized and the
>  >> conversation will end.
>  >>
>  >> =0D
>  >>
>  >> Therefore I think that before updating the session keys the
receiver
>  >> must first verify the message (and the sequence number) and only
if
>  >> verified he should update all the keys.
>  >>
>  >> =0D
>  >>
>  >> Further more;
>  >>
>  >> I think that when supporting key derivation rate, authentication
must
>  >> be applied. (otherwise the receiver is vulnerable to such attack)
>  >>
>  >> =0D
>  >>
>  >> What do you think ?
>  >>
>  >> ------------------
>  >>
>  >> Regards,
>  >>
>  >> Ofer Idan
>  >>
>  >> Audio Codes



***************************************************************************=
*********************************
This email and any files transmitted with it are confidential material.
They are intended solely for the use of the designated individual or entity=
 to whom they are addressed.
If the reader of this message is not the intended recipient,
you are hereby notified that any dissemination,use,
distribution or copying of this communication is strictly prohibited and=
 may be unlawful.

If you have received this email in error please notify=
 postmaster@audiocodes.com and permanently delete the e-mail and files.


***************************************************************************=
********************************

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Tue Nov 30 05:20:10 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01264
	for <avt-archive@ietf.org>; Tue, 30 Nov 2004 05:20:10 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZ5C8-0007Ka-9M
	for avt-archive@ietf.org; Tue, 30 Nov 2004 05:25:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZ4xk-0006rX-UA; Tue, 30 Nov 2004 05:10:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZ4VY-0006fK-Gv
	for avt@megatron.ietf.org; Tue, 30 Nov 2004 04:41:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26531
	for <avt@ietf.org>; Tue, 30 Nov 2004 04:41:14 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZ4aR-0006Uw-7P
	for avt@ietf.org; Tue, 30 Nov 2004 04:46:32 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iAU9f2h5018816
	for <avt@ietf.org>; Tue, 30 Nov 2004 10:41:02 +0100 (MET)
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 30 Nov 2004 10:41:01 +0100
Received: from ericsson.com (research-64de67.ki.sw.ericsson.se
	[147.214.118.190]) by esealnt613.al.sw.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id X8ANP1XN; Tue, 30 Nov 2004 10:40:56 +0100
Message-ID: <41AC4027.5030106@ericsson.com>
Date: Tue, 30 Nov 2004 10:40:55 +0100
X-Sybari-Trust: 5f7a4565 96d33411 638159be 00000138
From: =?ISO-8859-1?Q?Mats_N=E4slund?= <mats.naslund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Vavilapalli Srikanth-A19563 <srikanthv@motorola.com>
Subject: Re: [AVT] RFC 3711 Key Derivation
References: <772BCEF88A1DD91191F80011856715F3245B50@zin24exm01.ap.mot.com>
In-Reply-To: <772BCEF88A1DD91191F80011856715F3245B50@zin24exm01.ap.mot.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-OriginalArrivalTime: 30 Nov 2004 09:41:01.0558 (UTC)
	FILETIME=[B4061960:01C4D6C0]
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by penguin.ericsson.se id
	iAU9f2h5018816
X-Spam-Score: 0.0 (/)
X-Scan-Signature: abda3837e791065a13ac6f11cf8e625a
Content-Transfer-Encoding: quoted-printable
Cc: Yuval Nissan <YuvalN@audiocodes.com>, Mark Baugher <mbaugher@cisco.com>,
        avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9f79b8e383fd3af2b1b5b1d0910f6094
Content-Transfer-Encoding: quoted-printable

Hi Srikanth,

Vavilapalli Srikanth-A19563 wrote:

> Thanks a lot Mats.
>=20
> Effectively you are saying that the RTP senders and receivers have to=20
> derive
> the session keys (k_e, k_s, k_a) for "every packet" sent or received
> respectively, not just once before session start. Am I right?

Yes. At least you will need to *consider* the need to perform derivation
on every packet. Just because you updated the key on the previous
packet, you can never be sure that you won't need to go back to the
"previous" key again due to re-order. I would compare the "logic" needed
with that you need to keep ROC updated (sect 3.3.1) where you MAY need
to consider any ROC in the set { ROC-1, ROC, ROC+1 }. It's the same with
the keys.

In almost all practical cases (unless you have derivation_rate close
to "1") you will NOT need to derive a new key for the next packet,
and this can be determined by straight-forward "sequence number logic"
without actually applying the derivation function.

As Mark said, if this still worries you, just set the rate to zero.

>=20
> If that is the case, then I agree there will not be any out-of-sync iss=
ues
> at-least in the session key derivation because of initial loss of packe=
ts.
>=20

Good.

> NOTE: However, no where in the RFC (at-least from my understanding) say=
s to
> derive the session keys for every packet sent and received. It was=20
> saying to
> derive the session once before session commencement and refresh the key=
s
> whenever (index mod 2^key-derivation-rate) is zero. Isn't my understand=
ing
> right here?

One can always ask if the spec. if clear enough on every single issue.
We certainly tried to be. If you look at the "formula" on p 26,
as I wrote before, the keys are computed like

	key =3D PRF( ... , ... index ...),

so since index can vary both up and down, I hope it is clear that the
order in which the keys are to be used may not always be "monotonic".

Best,

/Mats
> -----Original Message-----
> From: Mats N=E4slund [mailto:mats.naslund@ericsson.com]
> Sent: Tuesday, November 30, 2004 2:32 PM
> To: Vavilapalli Srikanth-A19563
> Cc: Mark Baugher; Yuval Nissan; avt@ietf.org
> Subject: Re: [AVT] RFC 3711 Key Derivation
>=20
> Hi,
>=20
> I hope Mark excuses me for jumping in, but I can't resist
> to give my explanation for why specific synch problem cannot occur
> due to the key derivation. Please take a look at the RFC
> on page 26. Here, you will see that for a given (just received)
> packet, the keys (and salt etc) are given by:
>=20
>         key =3D PRF_n(k_master, x),
>=20
> (where key is k_s, k_a or k_e), and where in turn, x is of the form,
>=20
>         x =3D salt XOR (<label> || index DIV key_derivation_rate).
>=20
> If we "expand" this, you will get (unimportant stuff left out):
>=20
> key =3D PRF_n(k_master, ... index DIV key_derivation_rate).
>=20
> Note that index is determined by SEQ and ROC.  SEQ is carried
> along with the packet and does not create problems. The only thing
> that can go wrong is if the wrong ROC is used. This can happen
> only if packet loss or reordering on the order of 2^15 packets
> occurs. However, *if* ROC wrong, notice that ROC is also
> part of the IV for the decryption, and it is also part of the
> authenticated data, etc. Hence, even if the right keys were used,
> decryption and/or authentication will fail anyway. When authentication
> fails, possible ROC update will be discarded. Therefore, the
> problem with loosing synch on ROC is general, and the key derivation
> does not make it worse, it shows precisely the same problem
> as the rest of the protocol does in case of EXTREME loss or
> re-order.
>=20
> You could argue that authentication helps since it will assist
> in avoiding false ROC updates. However, as long as we keep
> using the wrong ROC on the receiver side, it does not help much
> since decryption will just produce garbage anyway, and it is still
> not until we somehow re-gain synch on the ROC value that the
> protocol starts to work properly again.
>=20
> Best,
>=20
> /Mats
>=20
> Vavilapalli Srikanth-A19563 wrote:
>=20
>  > Mark
>  >
>  > Please correct me if my understanding from the RFC3711 standard is=20
> wrong.
>  >
>  > RFC3711 specifies a key derivation mechanism to be run for deriving =
the
>  > session keys (k_e, k_a, k_s) which are used in encryption and
>  > authentication
>  > process and must be executed once before media flow commencement and=
 can
> be
>  > refreshed depending on the Key derivation rate. This key derivation
>  > mechanism uses the packet index as an input to the PRF algorithm.
>  >
>  > First understanding from the above text is if Key derivation rate is=
 "N"
>  > (where N is a non-zero positive integer) means, the SRTP sender shou=
ld
>  > refresh/regenerate the session keys (k_e, k_s, k_a) for every "N"=20
> packets
>  > sent. Am I right here? However, I am not clear on the receiver=20
> refreshing
>  > its session keys. Will it also depend on the number of packets recei=
ved?
> If
>  > so how are the packet losses accounted in this calculation?
>  >
>  > Second, the SRTP sender uses the packet index (ROC || SEQ) of the fi=
rst
>  > packet to derive the session keys (k_e, k_s, k_a), where ROC will be=
=20
> zero
>  > and SEQ is a random number (not necessarily zero) used as initial=20
> sequence
>  > number. This packet index will have impact on the key derivation onl=
y=20
> when
>  > the derivation rate is non-zero positive integer. In the similar
>  > fashion, to
>  > derive the same session keys at the receiving end, the receiver also
> should
>  > use the same packet index to derive the session keys. With this
>  > understanding I strongly believe that the receiver might get out-of-=
sync
> if
>  > the initial packets of the session are lost, because the packet inde=
x
>  > estimated at the receiver end might not be the same that is used at =
the
>  > sender side to derive the session keys. How do we re-sync both=20
> parties in
>  > this scenario?
>  >
>  >
>  > -Srikanth
>  >
>  >
>  >
>  > -----Original Message-----
>  > From: Mark Baugher [mailto:mbaugher@cisco.com]
>  > Sent: Monday, November 29, 2004 11:12 PM
>  > To: Vavilapalli Srikanth-A19563
>  > Cc: Ofer Idan; avt@ietf.org; Yuval Nissan
>  > Subject: Re: [AVT] RFC 3711 Key Derivation
>  >
>  > hi
>  >
>  > On Nov 28, 2004, at 10:28 PM, Vavilapalli Srikanth-A19563 wrote:
>  >
>  >  > Idan
>  >  >
>  >  > I think the initial sequence number (SEQ) and ROC of the session =
must
>  >  > be
>  >  > communicated to the other participants in the case non-zero key
>  >  > derivation
>  >  > rate using some out-of-band signaling.
>  >
>  > I hope it's not necessary to communicate the SEQ, which is a
>  > very difficult thing to signal OOB.  Signaling the ROC for ongoing
>  > sessions is bad enough.  The signaling layer typically does not have
>  > access to this sort of state information.
>  >  >
>  >  > If not (i.e. if SEQ number is not communicated), even the integri=
ty
>  >  > protection also can not avoid the out of sync issues. The integri=
ty
>  >  > protection helps the receiver to drop the attacker's packet, but =
also
>  >  > makes
>  >  > receiver to drop the actual sender's packets, because receiver us=
es
>  >  > different session key than the sender's.
>  >
>  > The value of the SEQ in the validated packet with the ROC are enough
>  > information
>  > to identify and calculate the correct key (the SEQ is not encrypted =
so
>  > the
>  > receiver can determine the key to use).  What am I missing?
>  >
>  > Mark
>  >  >
>  >  >
>  >  > Regards
>  >  > Srikanth
>  >  >
>  >  >
>  >  > -----Original Message-----
>  >  > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behal=
f Of
>  >  > Mark
>  >  > Baugher
>  >  > Sent: Monday, November 29, 2004 4:08 AM
>  >  > To: Ofer Idan
>  >  > Cc: Yuval Nissan; avt@ietf.org
>  >  > Subject: Re: [AVT] RFC 3711 Key Derivation
>  >  >
>  >  > hi
>  >  > On Nov 28, 2004, at 12:33 AM, Ofer Idan wrote:
>  >  >
>  >  >> Hi,
>  >  >>
>  >  >>=20
>  >  >>
>  >  >> I have a question regarding RFC 3711 Key derivation rate.
>  >  >>
>  >  >>=20
>  >  >>
>  >  >> In section 3.3 the decrypt process is described:
>  >  >>
>  >  >>=20
>  >  >>
>  >  >> Bullet (4) says to determine the session keys using the maser ke=
y,
>  >  >> master salt, key derivation rate.
>  >  >>
>  >  >> Bullet (5) says to check for anti reply, verify authentication.
>  >  >>
>  >  >>=20
>  >  >>
>  >  >> I think that there might be a problem here.
>  >  >>
>  >  >> =20
>  >  >>
>  >  >> Consider a scenario where Key derivation rate is supported=20
> (different
>  >  >> than zero).
>  >  >>
>  >  >>=20
>  >  >>
>  >  >> An attacker can send a packet with a higher sequence number that=
=20
> will
>  >  >> cause the receiver to change his session keys (according to key
>  >  >> derivation rate).
>  >  >
>  >  > The attacker's packet won't verify upon receipt when the session =
is
>  >  > integrity protected and will be rejected.  (Hence the importance =
of
>  >  > integrity protection).
>  >  >
>  >  > Mark
>  >  >>
>  >  >> From this moment on, the two sides will be unsynchronized and th=
e
>  >  >> conversation will end.
>  >  >>
>  >  >>=20
>  >  >>
>  >  >> Therefore I think that before updating the session keys the rece=
iver
>  >  >> must first verify the message (and the sequence number) and only=
 if
>  >  >> verified he should update all the keys.
>  >  >>
>  >  >>=20
>  >  >>
>  >  >> Further more;
>  >  >>
>  >  >> I think that when supporting key derivation rate, authentication=
=20
> must
>  >  >> be applied. (otherwise the receiver is vulnerable to such attack=
)
>  >  >>
>  >  >>=20
>  >  >>
>  >  >> What do you think ?
>  >  >>
>  >  >> ------------------
>  >  >>
>  >  >> Regards,
>  >  >>
>  >  >> Ofer Idan
>  >  >>
>  >  >> Audio Codes
>=20


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Tue Nov 30 10:13:52 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26569
	for <avt-archive@ietf.org>; Tue, 30 Nov 2004 10:13:52 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZ9ma-00063A-HN
	for avt-archive@ietf.org; Tue, 30 Nov 2004 10:19:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZ9e7-0007Tm-21; Tue, 30 Nov 2004 10:10:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZ9aF-0005by-7O
	for avt@megatron.ietf.org; Tue, 30 Nov 2004 10:06:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25523
	for <avt@ietf.org>; Tue, 30 Nov 2004 10:06:24 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZ9fM-0005sP-U6
	for avt@ietf.org; Tue, 30 Nov 2004 10:11:45 -0500
Received: from sj-core-4.cisco.com (171.68.223.138)
	by sj-iport-5.cisco.com with ESMTP; 30 Nov 2004 07:06:08 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id iAUF5ptR029171;
	Tue, 30 Nov 2004 07:05:51 -0800 (PST)
Received: from [192.168.0.11] (sjc-vpn4-864.cisco.com [10.21.83.95])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id iAUF5Ngt000470;
	Tue, 30 Nov 2004 07:05:23 -0800
In-Reply-To: <41AC4027.5030106@ericsson.com>
References: <772BCEF88A1DD91191F80011856715F3245B50@zin24exm01.ap.mot.com>
	<41AC4027.5030106@ericsson.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <50B77EDE-42E1-11D9-B875-000A95DC10F2@cisco.com>
Content-Transfer-Encoding: quoted-printable
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [AVT] RFC 3711 Key Derivation
Date: Tue, 30 Nov 2004 07:05:47 -0800
To: =?ISO-8859-1?Q?Mats_N=E4slund?= <mats.naslund@ericsson.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1101827124.201157"; x:"432200"; a:"rsa-sha1"; b:"nofws:10983";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"p1D3QoBKvVEqQjDhfPmXI1GBB534RAA/8KLQAQVO48OhHZ8IYwjRrQ21g1hFd"
	"AKoeY0Sza5hQtQmbGNjvZps5Xufc7tfc/ocMicwo0vAeoGmtgLjZfwSmOEQHT"
	"AvZtlF7DAu1njUYYc3rA/I+gaUvtAgdncTg4wyQ4Hp35gW2rM=";
	c:"From: Mark Baugher <mbaugher@cisco.com>";
	c:"Subject: Re: [AVT] RFC 3711 Key Derivation";
	c:"Date: Tue, 30 Nov 2004 07:05:47 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bd8a74b81c71f965ca7918b90d1c49c0
Content-Transfer-Encoding: quoted-printable
Cc: Yuval Nissan <YuvalN@audiocodes.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4bb0e9e1ca9d18125bc841b2d8d77e24
Content-Transfer-Encoding: quoted-printable

Thanks for the explanations Mats.  Over the past year or so, several=20
people have misread how the key derivation algorithm works in about the=20=

same way: People expect to perform key derivation after 2^Nth packet=20
has been sent rather than when the extended sequence number reaches=20
2^N.  We might want to update the specification or even put the=20
clarification in the form of an errata write-up on the RFC page.

Mark
On Nov 30, 2004, at 1:40 AM, Mats N=E4slund wrote:

> Hi Srikanth,
>
> Vavilapalli Srikanth-A19563 wrote:
>
>> Thanks a lot Mats.
>> Effectively you are saying that the RTP senders and receivers have to=20=

>> derive
>> the session keys (k_e, k_s, k_a) for "every packet" sent or received
>> respectively, not just once before session start. Am I right?
>
> Yes. At least you will need to *consider* the need to perform=20
> derivation
> on every packet. Just because you updated the key on the previous
> packet, you can never be sure that you won't need to go back to the
> "previous" key again due to re-order. I would compare the "logic"=20
> needed
> with that you need to keep ROC updated (sect 3.3.1) where you MAY need
> to consider any ROC in the set { ROC-1, ROC, ROC+1 }. It's the same=20
> with
> the keys.
>
> In almost all practical cases (unless you have derivation_rate close
> to "1") you will NOT need to derive a new key for the next packet,
> and this can be determined by straight-forward "sequence number logic"
> without actually applying the derivation function.
>
> As Mark said, if this still worries you, just set the rate to zero.
>
>> If that is the case, then I agree there will not be any out-of-sync=20=

>> issues
>> at-least in the session key derivation because of initial loss of=20
>> packets.
>
> Good.
>
>> NOTE: However, no where in the RFC (at-least from my understanding)=20=

>> says to
>> derive the session keys for every packet sent and received. It was=20
>> saying to
>> derive the session once before session commencement and refresh the=20=

>> keys
>> whenever (index mod 2^key-derivation-rate) is zero. Isn't my=20
>> understanding
>> right here?
>
> One can always ask if the spec. if clear enough on every single issue.
> We certainly tried to be. If you look at the "formula" on p 26,
> as I wrote before, the keys are computed like
>
> 	key =3D PRF( ... , ... index ...),
>
> so since index can vary both up and down, I hope it is clear that the
> order in which the keys are to be used may not always be "monotonic".
>
> Best,
>
> /Mats
>> -----Original Message-----
>> From: Mats N=E4slund [mailto:mats.naslund@ericsson.com]
>> Sent: Tuesday, November 30, 2004 2:32 PM
>> To: Vavilapalli Srikanth-A19563
>> Cc: Mark Baugher; Yuval Nissan; avt@ietf.org
>> Subject: Re: [AVT] RFC 3711 Key Derivation
>> Hi,
>> I hope Mark excuses me for jumping in, but I can't resist
>> to give my explanation for why specific synch problem cannot occur
>> due to the key derivation. Please take a look at the RFC
>> on page 26. Here, you will see that for a given (just received)
>> packet, the keys (and salt etc) are given by:
>>         key =3D PRF_n(k_master, x),
>> (where key is k_s, k_a or k_e), and where in turn, x is of the form,
>>         x =3D salt XOR (<label> || index DIV key_derivation_rate).
>> If we "expand" this, you will get (unimportant stuff left out):
>> key =3D PRF_n(k_master, ... index DIV key_derivation_rate).
>> Note that index is determined by SEQ and ROC.  SEQ is carried
>> along with the packet and does not create problems. The only thing
>> that can go wrong is if the wrong ROC is used. This can happen
>> only if packet loss or reordering on the order of 2^15 packets
>> occurs. However, *if* ROC wrong, notice that ROC is also
>> part of the IV for the decryption, and it is also part of the
>> authenticated data, etc. Hence, even if the right keys were used,
>> decryption and/or authentication will fail anyway. When =
authentication
>> fails, possible ROC update will be discarded. Therefore, the
>> problem with loosing synch on ROC is general, and the key derivation
>> does not make it worse, it shows precisely the same problem
>> as the rest of the protocol does in case of EXTREME loss or
>> re-order.
>> You could argue that authentication helps since it will assist
>> in avoiding false ROC updates. However, as long as we keep
>> using the wrong ROC on the receiver side, it does not help much
>> since decryption will just produce garbage anyway, and it is still
>> not until we somehow re-gain synch on the ROC value that the
>> protocol starts to work properly again.
>> Best,
>> /Mats
>> Vavilapalli Srikanth-A19563 wrote:
>>  > Mark
>>  >
>>  > Please correct me if my understanding from the RFC3711 standard is=20=

>> wrong.
>>  >
>>  > RFC3711 specifies a key derivation mechanism to be run for=20
>> deriving the
>>  > session keys (k_e, k_a, k_s) which are used in encryption and
>>  > authentication
>>  > process and must be executed once before media flow commencement=20=

>> and can
>> be
>>  > refreshed depending on the Key derivation rate. This key =
derivation
>>  > mechanism uses the packet index as an input to the PRF algorithm.
>>  >
>>  > First understanding from the above text is if Key derivation rate=20=

>> is "N"
>>  > (where N is a non-zero positive integer) means, the SRTP sender=20
>> should
>>  > refresh/regenerate the session keys (k_e, k_s, k_a) for every "N"=20=

>> packets
>>  > sent. Am I right here? However, I am not clear on the receiver=20
>> refreshing
>>  > its session keys. Will it also depend on the number of packets=20
>> received?
>> If
>>  > so how are the packet losses accounted in this calculation?
>>  >
>>  > Second, the SRTP sender uses the packet index (ROC || SEQ) of the=20=

>> first
>>  > packet to derive the session keys (k_e, k_s, k_a), where ROC will=20=

>> be zero
>>  > and SEQ is a random number (not necessarily zero) used as initial=20=

>> sequence
>>  > number. This packet index will have impact on the key derivation=20=

>> only when
>>  > the derivation rate is non-zero positive integer. In the similar
>>  > fashion, to
>>  > derive the same session keys at the receiving end, the receiver=20
>> also
>> should
>>  > use the same packet index to derive the session keys. With this
>>  > understanding I strongly believe that the receiver might get=20
>> out-of-sync
>> if
>>  > the initial packets of the session are lost, because the packet=20
>> index
>>  > estimated at the receiver end might not be the same that is used=20=

>> at the
>>  > sender side to derive the session keys. How do we re-sync both=20
>> parties in
>>  > this scenario?
>>  >
>>  >
>>  > -Srikanth
>>  >
>>  >
>>  >
>>  > -----Original Message-----
>>  > From: Mark Baugher [mailto:mbaugher@cisco.com]
>>  > Sent: Monday, November 29, 2004 11:12 PM
>>  > To: Vavilapalli Srikanth-A19563
>>  > Cc: Ofer Idan; avt@ietf.org; Yuval Nissan
>>  > Subject: Re: [AVT] RFC 3711 Key Derivation
>>  >
>>  > hi
>>  >
>>  > On Nov 28, 2004, at 10:28 PM, Vavilapalli Srikanth-A19563 wrote:
>>  >
>>  >  > Idan
>>  >  >
>>  >  > I think the initial sequence number (SEQ) and ROC of the=20
>> session must
>>  >  > be
>>  >  > communicated to the other participants in the case non-zero key
>>  >  > derivation
>>  >  > rate using some out-of-band signaling.
>>  >
>>  > I hope it's not necessary to communicate the SEQ, which is a
>>  > very difficult thing to signal OOB.  Signaling the ROC for ongoing
>>  > sessions is bad enough.  The signaling layer typically does not=20
>> have
>>  > access to this sort of state information.
>>  >  >
>>  >  > If not (i.e. if SEQ number is not communicated), even the=20
>> integrity
>>  >  > protection also can not avoid the out of sync issues. The=20
>> integrity
>>  >  > protection helps the receiver to drop the attacker's packet,=20
>> but also
>>  >  > makes
>>  >  > receiver to drop the actual sender's packets, because receiver=20=

>> uses
>>  >  > different session key than the sender's.
>>  >
>>  > The value of the SEQ in the validated packet with the ROC are=20
>> enough
>>  > information
>>  > to identify and calculate the correct key (the SEQ is not=20
>> encrypted so
>>  > the
>>  > receiver can determine the key to use).  What am I missing?
>>  >
>>  > Mark
>>  >  >
>>  >  >
>>  >  > Regards
>>  >  > Srikanth
>>  >  >
>>  >  >
>>  >  > -----Original Message-----
>>  >  > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On=20
>> Behalf Of
>>  >  > Mark
>>  >  > Baugher
>>  >  > Sent: Monday, November 29, 2004 4:08 AM
>>  >  > To: Ofer Idan
>>  >  > Cc: Yuval Nissan; avt@ietf.org
>>  >  > Subject: Re: [AVT] RFC 3711 Key Derivation
>>  >  >
>>  >  > hi
>>  >  > On Nov 28, 2004, at 12:33 AM, Ofer Idan wrote:
>>  >  >
>>  >  >> Hi,
>>  >  >>
>>  >  >>  >  >>
>>  >  >> I have a question regarding RFC 3711 Key derivation rate.
>>  >  >>
>>  >  >>  >  >>
>>  >  >> In section 3.3 the decrypt process is described:
>>  >  >>
>>  >  >>  >  >>
>>  >  >> Bullet (4) says to determine the session keys using the maser=20=

>> key,
>>  >  >> master salt, key derivation rate.
>>  >  >>
>>  >  >> Bullet (5) says to check for anti reply, verify =
authentication.
>>  >  >>
>>  >  >>  >  >>
>>  >  >> I think that there might be a problem here.
>>  >  >>
>>  >  >>   >  >>
>>  >  >> Consider a scenario where Key derivation rate is supported=20
>> (different
>>  >  >> than zero).
>>  >  >>
>>  >  >>  >  >>
>>  >  >> An attacker can send a packet with a higher sequence number=20
>> that will
>>  >  >> cause the receiver to change his session keys (according to =
key
>>  >  >> derivation rate).
>>  >  >
>>  >  > The attacker's packet won't verify upon receipt when the=20
>> session is
>>  >  > integrity protected and will be rejected.  (Hence the=20
>> importance of
>>  >  > integrity protection).
>>  >  >
>>  >  > Mark
>>  >  >>
>>  >  >> =46rom this moment on, the two sides will be unsynchronized =
and=20
>> the
>>  >  >> conversation will end.
>>  >  >>
>>  >  >>  >  >>
>>  >  >> Therefore I think that before updating the session keys the=20
>> receiver
>>  >  >> must first verify the message (and the sequence number) and=20
>> only if
>>  >  >> verified he should update all the keys.
>>  >  >>
>>  >  >>  >  >>
>>  >  >> Further more;
>>  >  >>
>>  >  >> I think that when supporting key derivation rate,=20
>> authentication must
>>  >  >> be applied. (otherwise the receiver is vulnerable to such=20
>> attack)
>>  >  >>
>>  >  >>  >  >>
>>  >  >> What do you think ?
>>  >  >>
>>  >  >> ------------------
>>  >  >>
>>  >  >> Regards,
>>  >  >>
>>  >  >> Ofer Idan
>>  >  >>
>>  >  >> Audio Codes
>


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Tue Nov 30 18:03:55 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27309
	for <avt-archive@ietf.org>; Tue, 30 Nov 2004 18:03:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZH7Y-0006QB-Uf
	for avt-archive@ietf.org; Tue, 30 Nov 2004 18:09:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZGyf-0001aG-Nn; Tue, 30 Nov 2004 18:00:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZGrV-0007Vp-Dr
	for avt@megatron.ietf.org; Tue, 30 Nov 2004 17:52:45 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26181
	for <avt@ietf.org>; Tue, 30 Nov 2004 17:52:40 -0500 (EST)
Received: from news.ti.com ([192.94.94.33] helo=dragon.ti.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZGwf-00065X-EQ
	for avt@ietf.org; Tue, 30 Nov 2004 17:58:05 -0500
Received: from dlep90.itg.ti.com ([157.170.152.54])
	by dragon.ti.com (8.13.1/8.13.1) with ESMTP id iAUMpb9r000626
	for <avt@ietf.org>; Tue, 30 Nov 2004 16:51:37 -0600 (CST)
Received: from dlee2k70.ent.ti.com (localhost [127.0.0.1])
	by dlep90.itg.ti.com (8.12.11/8.12.11) with ESMTP id iAUMpX3h005020
	for <avt@ietf.org>; Tue, 30 Nov 2004 16:51:37 -0600 (CST)
Received: from dlee2k03.ent.ti.com ([157.170.152.86]) by dlee2k70.ent.ti.com
	with Microsoft SMTPSVC(5.0.2195.6713); 
	Tue, 30 Nov 2004 16:50:34 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: [AVT] comments on draft-ietf-avt-rfc2833bis-06.txt
Date: Tue, 30 Nov 2004 16:50:34 -0600
Message-ID: <953541C3AD5E7F4B9A9ED03338BD50435DEB83@dlee2k03.ent.ti.com>
Thread-Topic: [AVT] comments on draft-ietf-avt-rfc2833bis-06.txt
Thread-Index: AcTXFkrVbEZVb5sgSjiQAABi1JxybAAGKPew
From: "Mundra, Satish" <smundra@ti.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 30 Nov 2004 22:50:34.0707 (UTC)
	FILETIME=[009EFA30:01C4D72F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
Content-Transfer-Encoding: quoted-printable
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede
Content-Transfer-Encoding: quoted-printable

=20
I have following comments on this draft:


1. Section 2.5.1.2 states:
   "Timing information is contained in the RTP timestamp, allowing=20
   precise recovery of inter-event times.  Thus, the sender does not=20
   need to maintain precise or consistent time intervals between event=20
   packets."=20

The section refers to "event packets" as those belonging to same event.
I=20
think a sender needs to maintain consistent interval between event
packets=20
as a receiver relies on the inter-arrival times to decide how long to
extend=20
the tone when there are no event packets received. For e.g. if the
interval is=20
changed from 10ms to 50ms then a receiver could timeout before the event
packet=20
sent at new interval arrives.=20


2. Section 2.5.1.4 states:
   "A sender MAY delay setting the "E" bit until retransmitting the last

   packet for a tone, rather than setting the bit on its first=20
   transmission. This avoids having to wait to detect whether the tone=20
   has indeed ended.  Once the sender has set the "E" bit for a packet,=20
   it MUST continue to set the "E" bit for any further retransmissions=20
   of that packet."

How is above different from a sender that does not re-transmit packets
with=20
E-bit set? Assuming that receiver is using section2.5.2.2 alogorithm-2
for=20
playout, isn't delaying the setting of E-bit going to cause tone
extension=20
by 5*inter-arrival periods if the packet with E-bit set was lost ?=20

3. Section 2.6.2 states: =20
      "This approach allows dumb gateways that do not understand this

      format to function. See also the discussion in section 1."

This statement should be removed, as gateways first need to negotiate
the=20
payloads via out-of-band means, hence the situation where dumb gateway
receives=20
payload format that it does not understand should not arise.

4. Section 2.6.2 states:
   "The audio redundancy mechanism described in RFC 2198 [N-2] MAY be=20
   used to recover from packet loss across events. For the suggested=20
   packet gap of 50 ms, the effective data rate is r times 64 bits (32=20
   bits for the redundancy header and 32 bits for the telephone-event=20
   payload) plus 8 bits for the primary encoding every 50 ms or (r times

   1280 + 160) bits/second, where r is the number of redundant events=20
   carried in each packet. The value of r is an implementation trade-
   off, with a value of 5 suggested."

I think calculations are for "effective increase in data rate" when
redundancy
is used and not effective data rate. The primary payload of 4 bytes is
not=20
included in the above data rate.

5. Section 5.1 states:
   "Gateways which send signalling events via RTP MAY send both named=20
   signals (section named) and the tone representation (section tones)=20
   as a single RTP session, using the redundancy mechanism defined in=20
   RFC 2198 [N-2] to interleave the two representations. It is generally

   a good idea to send both, since it allows the receiver to choose the=20
   appropriate rendering."=20
  =20
I think "a single RTP session" above should be changed to "in a single
RTP packet".

6. Section 5.2 states:
  "Events and Audio
      "The source sends events and encoded audio packets (e.g., PCMU or=20
      the codec used for speech signals) for the same time instant. In=20
      that mode, events are treated as redundant encodings for the=20
      encoded audio stream."

 =20
As noted in section 2.5.2.2, encoded audio packets preceding the encoded

events can cause spurious digits/events and this mode allows the encoded

audio packets after the recognition of events and is probably going to=20
increase the probability of spurious digits. Section 5.2 also recommends

using encoded tones rather than encoded audio for rendering tones.=20
Why not disallow this mode?

7. Section 2.6 states:=20
      "Section 2.6.2 describes how a summary of earlier events MAY be=20
      carried in RFC 2198 redundancy payloads.  This is particularly=20
      useful for sequences of short events, e.g., digits dialed by a=20
      modem or autodialer or in-band tone signaling sequences (section=20
      3.2 or 3.5)."

There is no section 3.5 in the new draft. What about redundancy when the

digits are not dialed by auto-dialer or modem and inter-digit interval
and=20
dialing duration are not small, for e.g., calling card calls ?=20


Regards,

Satish Mundra


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


From avt-bounces@ietf.org  Tue Nov 30 18:52:12 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01530
	for <avt-archive@ietf.org>; Tue, 30 Nov 2004 18:52:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZHsH-0007P4-Uh
	for avt-archive@ietf.org; Tue, 30 Nov 2004 18:57:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZHhU-0006tV-PW; Tue, 30 Nov 2004 18:46:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZHgo-0006am-DJ
	for avt@megatron.ietf.org; Tue, 30 Nov 2004 18:45:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01343
	for <avt@ietf.org>; Tue, 30 Nov 2004 18:45:43 -0500 (EST)
From: sassan.ahmadi@nokia.com
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZHm1-0007Jh-20
	for avt@ietf.org; Tue, 30 Nov 2004 18:51:09 -0500
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121])
	by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iAUNjgo27551; Wed, 1 Dec 2004 01:45:42 +0200 (EET)
X-Scanned: Wed, 1 Dec 2004 01:45:37 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks002.ntc.nokia.com (8.12.9/8.12.9) id iAUNjb5X020220;
	Wed, 1 Dec 2004 01:45:37 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks002.ntc.nokia.com 00zBWwba; Wed, 01 Dec 2004 01:45:35 EET
Received: from daebh002.NOE.Nokia.com (daebh002.americas.nokia.com
	[10.241.35.122])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iAUNjXa27908; Wed, 1 Dec 2004 01:45:34 +0200 (EET)
Received: from sdebe002.NOE.Nokia.com ([172.19.201.138]) by
	daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Tue, 30 Nov 2004 17:44:49 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 30 Nov 2004 15:44:44 -0800
Message-ID: <0B08EA1BF5F6304992CDC985EE02209E02A743AE@sdebe002.americas.nokia.com>
Thread-Topic: <draft-ietf-avt-rtp-vmr-wb-06.txt>
Thread-Index: AcTXNpG1abMfLJAMSa2QBhzLvnMwBg==
To: <avt@ietf.org>
X-OriginalArrivalTime: 30 Nov 2004 23:44:50.0000 (UTC)
	FILETIME=[94ED4500:01C4D736]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: quoted-printable
Cc: magnus.westerlund@ericsson.com, csp@csperkins.org, sassan.ahmadi@nokia.com
Subject: [AVT] <draft-ietf-avt-rtp-vmr-wb-06.txt>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: quoted-printable

Dear AVT Chairs,
=20
Greetings!
=20
I just posted a revised version of the VMR-WB RTP payload I-D =
<draft-ietf-avt-rtp-vmr-wb-06.txt> on the IETF server. It should be =
shortly available at =
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-vmr-wb-06.txt.
=20
This revision comprises the changes with respect to RTP clock rate and =
media sampling rate that were discussed and approved by the AVT group in =
the 61st IETF meetings in Washington, DC.
=20
I also ran the draft through "idnits-v1.51" and made sure that it is =
compliant with the IETF secretariat requirements.

I would like to ask you to accept this draft for the Working Group Last =
Call.

Regards

-Sassan Ahmadi



_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


