Re: [rtcweb] Proposal for RTCWEB Milestone Update

Harald Alvestrand <harald@alvestrand.no> Thu, 23 January 2014 10:03 UTC

Return-Path: <harald@alvestrand.no>
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 977861A03C5 for <rtcweb@ietfa.amsl.com>; Thu, 23 Jan 2014 02:03:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level:
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] 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 TsgGf0ilmFtk for <rtcweb@ietfa.amsl.com>; Thu, 23 Jan 2014 02:03:12 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [IPv6:2001:700:1:2:213:72ff:fe0b:80d8]) by ietfa.amsl.com (Postfix) with ESMTP id 467511A03CA for <rtcweb@ietf.org>; Thu, 23 Jan 2014 02:03:12 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 3A0C039E1C0 for <rtcweb@ietf.org>; Thu, 23 Jan 2014 11:03:19 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UJPlBApuBax5 for <rtcweb@ietf.org>; Thu, 23 Jan 2014 11:03:18 +0100 (CET)
Received: from hta-hippo.lul.corp.google.com (unknown [IPv6:2620:0:1043:1:7646:a0ff:fe90:e2bb]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 7842839E127 for <rtcweb@ietf.org>; Thu, 23 Jan 2014 11:03:18 +0100 (CET)
Message-ID: <52E0E8DD.6060106@alvestrand.no>
Date: Thu, 23 Jan 2014 11:03:09 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <52E0DE9A.1090405@ericsson.com>
In-Reply-To: <52E0DE9A.1090405@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] Proposal for RTCWEB Milestone Update
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: Thu, 23 Jan 2014 10:03:15 -0000

Mostly, this looks realistic.

One place where I'm more optimistic:

On 01/23/2014 10:19 AM, Magnus Westerlund wrote:
> Old: New milestone
> New: Sep 2014
> Send Specification of Transport Protocols and their NAT Traversal to
> IESG for publication as Proposed Standard
> draft-ietf-rtcweb-transports
>

Given that there has been fairly small controversies here, I feel that 
this should be doable in the same timeframe as rtp-usage - that is, April.

If the chairs' decision is that the normative parts of -firewalls- needs 
to go into -transport-, I would aim this for September.

Note: There is no mention of -firewalls- in the milestones suggested. 
What's the chairs' thinking on this?

           Harald