Re: [rtcweb] Network times . was SDP Security Descriptions (RFC 4568) and RTCWeb (UNCLASSIFIED)

"Roy, Radhika R CIV USARMY (US)" <radhika.r.roy.civ@mail.mil> Wed, 01 May 2013 19:03 UTC

Return-Path: <radhika.r.roy.civ@mail.mil>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E205921F9B67 for <rtcweb@ietfa.amsl.com>; Wed, 1 May 2013 12:03:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b5-UwAL16Tij for <rtcweb@ietfa.amsl.com>; Wed, 1 May 2013 12:02:57 -0700 (PDT)
Received: from edge-cols.mail.mil (edge-cols.mail.mil [131.64.100.13]) by ietfa.amsl.com (Postfix) with ESMTP id 8FCDC21F9885 for <rtcweb@ietf.org>; Wed, 1 May 2013 12:02:31 -0700 (PDT)
Received: from UCOLHP3H.easf.csd.disa.mil (131.64.100.149) by edge-cols.mail.mil (131.64.100.13) with Microsoft SMTP Server (TLS) id 14.2.309.2; Wed, 1 May 2013 19:02:23 +0000
Received: from UCOLHP9B.easf.csd.disa.mil ([169.254.10.82]) by UCOLHP3H.easf.csd.disa.mil ([131.64.100.149]) with mapi id 14.03.0123.003; Wed, 1 May 2013 19:02:23 +0000
From: "Roy, Radhika R CIV USARMY (US)" <radhika.r.roy.civ@mail.mil>
To: Randell Jesup <randell-ietf@jesup.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Network times . was SDP Security Descriptions (RFC 4568) and RTCWeb (UNCLASSIFIED)
Thread-Index: AQHORiot3hT0toA1x0SAjJDE87njG5jv9reggAA9LSCAAHBaAIAAC5Hg
Date: Wed, 01 May 2013 19:02:22 +0000
Message-ID: <8486C8728176924BAF5BDB2F7D7EEDDF49AC5D19@ucolhp9b.easf.csd.disa.mil>
References: <3FA2E46D-C98E-4FC0-9F1D-AD595A861CE1@iii.ca> <20130425202238.74EF321F96A5@ietfa.amsl.com> <AE1A6B5FD507DC4FB3C5166F3A05A48416281FDB@tk5ex14mbxc272.redmond.corp.microsoft.com> <03FBA798AC24E3498B74F47FD082A92F3BB8FAF7@US70UWXCHMBA04.zam.alcatel-lucent.com> <9F33F40F6F2CD847824537F3C4E37DDF0E6C04AF@MCHP04MSX.global-ad.net> <CAErhfrx6xi7rNmc6CZc5iyKiYv+oZbi3sBa5QywB7dUKtms2Aw@mail.gmail.com> <C643F355C8D33C48B983F1C1EA702A450B49EA@ESESSMB301.ericsson.se> <4AA3A95D6033ED488F8AE4E45F47448742B13620@WABOTH9MSGUSR8B.ITServices.sbc.com> <CALiegfmpZZigigQtaadsXup6VfWgJAF8--TJpbUwSJMmar7fRA@mail.gmail.com> <CAD5OKxv2d2DemnjHQdB8XU8NKfK-Uu913DLPq9JUT4z9kvFfTQ@mail.gmail.com> <829F9A35-5F23-4A0F-9831-80478F70965E@phonefromhere.com> <517E2F6A.30905@alvestrand.no> <C5E08FE080ACFD4DAE31E4BDBF944EB1134B0090@xmb-aln-x02.cisco.com> <02d001ce465c$bf00f690$3d02e3b0$@stahl@intertex.se> <8486C8728176924BAF5BDB2F7D7EEDDF49AC5673@ucolhp9b.easf.csd.disa.mil> <51815C78.4010403@jesup.org>
In-Reply-To: <51815C78.4010403@jesup.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [131.64.62.4]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="SHA1"; boundary="----=_NextPart_000_0049_01CE467C.E0D57E60"
MIME-Version: 1.0
Subject: Re: [rtcweb] Network times . was SDP Security Descriptions (RFC 4568) and RTCWeb (UNCLASSIFIED)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 May 2013 19:03:04 -0000

Classification: UNCLASSIFIED
Caveats: NONE

Inline [RRR]

-----Original Message-----
From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of
Randell Jesup
Sent: Wednesday, May 01, 2013 2:19 PM
To: rtcweb@ietf.org
Subject: Re: [rtcweb] Network times . was SDP Security Descriptions (RFC
4568) and RTCWeb (UNCLASSIFIED)

On 5/1/2013 4:46 AM, Roy, Radhika R CIV USARMY (US) wrote:
> I am responding only on a part of this email about retransmissions of 
> audio or video packets.
>
> Let us not consider the retransmission of audio or video packets. Let 
> us consider audio or video packets are sent only over UDP. Let MOS/QoS 
> of audio or video are considered in a way that retransmissions do not take
place.
>
> Then the question comes only about "data" traffic retransmissions. 
> Data traffic can tolerate much higher delays than that of audio or 
> video. Data has only QoS (and no MOS).

It may not have MOS per-se, but unreliable data channels have equivalent
issues - think of a first-person realtime game - unreliable position/state
updates of the user and the world mean that what data is lost (and how much
data is delayed but received) has a very strong impact on the user's
perception of the world.

[RRR] Yes, we need to have NEW threshold of delays (RTT) for data
performance.
--
Randell Jesup
randell-ietf@jesup.org




Classification: UNCLASSIFIED
Caveats: NONE