Re: [rtcweb] I-D Action: draft-ietf-rtcweb-overview-00.txt

Dzonatas Sol <dzonatas@gmail.com> Fri, 01 July 2011 15:12 UTC

Return-Path: <dzonatas@gmail.com>
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 A0F709E800A for <rtcweb@ietfa.amsl.com>; Fri, 1 Jul 2011 08:12:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.243
X-Spam-Level:
X-Spam-Status: No, score=-4.243 tagged_above=-999 required=5 tests=[AWL=-0.644, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id im4oB-IVbFzE for <rtcweb@ietfa.amsl.com>; Fri, 1 Jul 2011 08:12:51 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 85EFF21F8527 for <rtcweb@ietf.org>; Fri, 1 Jul 2011 08:11:31 -0700 (PDT)
Received: by pzk5 with SMTP id 5so3943805pzk.31 for <rtcweb@ietf.org>; Fri, 01 Jul 2011 08:11:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=jOkzhj65CgU6IPMylGAUZy4PC2dF9mWpBXQTIwVArpg=; b=p3xIjTrvQ3xlHYnFojQ0SIn2azixbJJb/U4GYnw/B29tbDRVTZ2mBEkw3XHyhNbkom a5/PyzIQDZL8lPcz9rmwH59y+ZvTX9HR5zLwhtf+wMqb5vLXVOQgP2lRYx4nC9WK+NvN 1FHNy1IlZbuI5YxkO/myckOTgAFpCbUCfAkJk=
Received: by 10.68.8.231 with SMTP id u7mr3548976pba.401.1309533091168; Fri, 01 Jul 2011 08:11:31 -0700 (PDT)
Received: from [192.168.0.50] (adsl-70-133-70-225.dsl.scrm01.sbcglobal.net [70.133.70.225]) by mx.google.com with ESMTPS id i9sm2044098pbk.52.2011.07.01.08.11.29 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 01 Jul 2011 08:11:30 -0700 (PDT)
Message-ID: <4E0DE382.9070309@gmail.com>
Date: Fri, 01 Jul 2011 08:10:58 -0700
From: Dzonatas Sol <dzonatas@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110505 Icedove/3.0.11
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <20110701055226.2267.16505.idtracker@ietfa.amsl.com>
In-Reply-To: <20110701055226.2267.16505.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-overview-00.txt
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: Fri, 01 Jul 2011 15:12:52 -0000

Hi, I read the entire overview. Only one concern, in 2.4 Terminology:

 >  Real-time media:  Media where generation of content and display of
 >      content are intended to occur closely together in time (on the
 >     order of no more than hundreds of milliseconds).

Can that just read:

 >  Real-time media:  Media where generation of content and display of
 >      content are intended to occur closely together in a given time 
scale.

I've found early specification of date systems may affect assets in ways 
unintended (or implied). There is no simple cure, so I think this is 
clearer without the noted "hundreds of milliseconds", there.

Some have tried to build "authoritative" dates from such real-time 
mechanics. Others pass that date thinking it is part of the asset. I've 
seen it happen, so I'm just thinking it would be nice to have some way 
to say that was not intended, yet I haven't found any.

On 06/30/2011 10:52 PM, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Real-Time Communication in WEB-browsers Working Group of the IETF.
>
> 	Title           : Overview: Real Time Protocols for Brower-based Applications
> 	Author(s)       : Harald T. Alvestrand
> 	Filename        : draft-ietf-rtcweb-overview-00.txt
> 	Pages           : 13
> 	Date            : 2011-06-30
>
>     This document gives an overview and context of a protocol suite
>     intended for use with real-time applications that can be deployed in
>     browsers -&quot;real time communication on the Web&quot;.
>
>     It intends to serve as a starting and coordination point to make sure
>     all the parts that are needed to achieve this goal are findable, and
>     that the parts that belong in the Internet protocol suite are fully
>     specified and on the right publication track.
>
>     This work is an attempt to synthesize the input of many people, but
>     makes no claims to fully represent the views of any of them.  All
>     parts of the document should be regarded as open for discussion,
>     unless the RTCWEB chairs have declared consensus on an item.
>
>     This document is a candidate to become a work item of the RTCWEB
>     working group.
>
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-rtcweb-overview-00.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-rtcweb-overview-00.txt
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>    


-- 
--- http://twitter.com/Dzonatas_Sol ---
Web Development, Software Engineering
Ag-Biotech, Virtual Reality, Consultant