Re: [rtcweb] On ptimes and maxptimes

Randell Jesup <randell-ietf@jesup.org> Sun, 23 March 2014 06:12 UTC

Return-Path: <randell-ietf@jesup.org>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 799301A6F2E for <rtcweb@ietfa.amsl.com>; Sat, 22 Mar 2014 23:12:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level:
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aCuMJ8Rkt_z9 for <rtcweb@ietfa.amsl.com>; Sat, 22 Mar 2014 23:12:29 -0700 (PDT)
Received: from r2-chicago.webserversystems.com (r2-chicago.webserversystems.com [173.236.101.58]) by ietfa.amsl.com (Postfix) with ESMTP id 25EBA1A6F2D for <rtcweb@ietf.org>; Sat, 22 Mar 2014 23:12:28 -0700 (PDT)
Received: from pool-71-175-4-197.phlapa.fios.verizon.net ([71.175.4.197]:1976 helo=[192.168.1.12]) by r2-chicago.webserversystems.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <randell-ietf@jesup.org>) id 1WRbe0-0001Mn-EV for rtcweb@ietf.org; Sun, 23 Mar 2014 01:12:28 -0500
Message-ID: <532E7B47.8060202@jesup.org>
Date: Sun, 23 Mar 2014 02:12:23 -0400
From: Randell Jesup <randell-ietf@jesup.org>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CAOJ7v-1e+FXQZrvh8Q549kwyhf8JX2BA_0q=+6mjha9+o-Dgpw@mail.gmail.com> <531DE104.2010908@ericsson.com> <CAOJ7v-31-xHGq1ERYYx5mvZuqTor0Seod_ChNT2AhY2BLaJi-Q@mail.gmail.com> <532AC890.7000602@ericsson.com> <CAOJ7v-2=p8LBjVK289usieiDFsmf6m3N8rYMNpBFPhDzdb_61Q@mail.gmail.com> <532BF5F4.90901@ericsson.com> <2ED6AAC7-5D6F-48C1-BCAE-EA161C6BC0CF@iii.ca>
In-Reply-To: <2ED6AAC7-5D6F-48C1-BCAE-EA161C6BC0CF@iii.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - r2-chicago.webserversystems.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jesup.org
X-Get-Message-Sender-Via: r2-chicago.webserversystems.com: authenticated_id: randell@jesup.org
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/j0JeOJ6EqpaCN_6IkKiCZqMnjwQ
Subject: Re: [rtcweb] On ptimes and maxptimes
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 23 Mar 2014 06:12:31 -0000

On 3/22/2014 2:39 PM, Cullen Jennings wrote:
> It seems like from interoperability point of view, we also need, if a 
> browser receives a maxptime or prime, it MUST be able to understand that.

maxptime - yes, MUST
ptime - since it's merely a preference, it's not a MUST understand.

-- 
Randell Jesup -- rjesup a t mozilla d o t com