Re: [rtcweb] Call for comment on document split

Igor Faynberg <igor.faynberg@alcatel-lucent.com> Fri, 17 June 2011 17:14 UTC

Return-Path: <igor.faynberg@alcatel-lucent.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 8AB6421F84C3 for <rtcweb@ietfa.amsl.com>; Fri, 17 Jun 2011 10:14:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 9PDzsYKzD0N9 for <rtcweb@ietfa.amsl.com>; Fri, 17 Jun 2011 10:14:27 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 226E621F84C2 for <rtcweb@ietf.org>; Fri, 17 Jun 2011 10:14:27 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p5HHEMmo008101 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <rtcweb@ietf.org>; Fri, 17 Jun 2011 12:14:23 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p5HHEMpf005247 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rtcweb@ietf.org>; Fri, 17 Jun 2011 12:14:22 -0500
Received: from [135.222.134.173] (faynberg-c1.mh.lucent.com [135.222.134.173]) by umail.lucent.com (8.13.8/TPES) with ESMTP id p5HHEMSW026612; Fri, 17 Jun 2011 12:14:22 -0500 (CDT)
Message-ID: <4DFB8B6E.7010201@alcatel-lucent.com>
Date: Fri, 17 Jun 2011 13:14:22 -0400
From: Igor Faynberg <igor.faynberg@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <BANLkTinu402NoPovU6nDWAKKUBKfbJyk3Q@mail.gmail.com>
In-Reply-To: <BANLkTinu402NoPovU6nDWAKKUBKfbJyk3Q@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------080905050800000306010108"
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Subject: Re: [rtcweb] Call for comment on document split
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: igor.faynberg@alcatel-lucent.com
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, 17 Jun 2011 17:14:28 -0000

Ted,

I think the proposed split is well in line with the Internet 
Architecture principle, "Modularity is always good."

It is well thought through.

Igor

On 6/17/2011 12:30 AM, Ted Hardie wrote:
> Hi Folks,
>
> In order to allow folks time to submit draft-ietf-rtcweb versions in 
> time for the upcoming 00 deadline, the chairs would like to first 
> outline our theory of the document splits to meet our chartered 
> milestones (to refresh you self on them: 
> http://datatracker.ietf.org/wg/rtcweb/charter/) in the August time frame.
>
> We'd like to have one document which describes the use cases.
> We'd like to have one document that gives a system overview and 
> outlines the overall model.
> We'd like to have one document that describes the privacy and security 
> model.
> We'd like to have one document that  describes the connectivity model 
> (for NAT traversal etc.).
>
> Later documents will be: signaling and negotiation methods, media 
> transports, datagram transport for non-media data, and one or more 
> documents on media processing and codecs.
>
> Note that this set of "documents we'd like" is missing one that says 
> "requirements".  Discussion among the chairs has come to consensus 
> that we have at least three different kinds of requirements being 
> discussed and the the use of the term "requirement" is hindering both 
> our internal discussion and the balance of work between us and the W3C 
> at the moment.  So, we'd like to have the focus be on what the parts 
> of the system *do* within the context of a system overview, rather 
> than on a discussion of requirements or, even worse, a meta discussion 
> of what the word "requirements" means in particular contexts.
>
> If folks our okay with this document set, the chairs will then appoint 
> editors from among those who have contributed text so far.  This may 
> mean that the initial -00 versions have a strong resemblance to the 
> individual submissions they'd already presented; it also may not. 
>  We'd like to remind everyone that taking on the role of document 
> editor in an IETF context means accepting the responsibility to make 
> the document reflect the consensus of the group.  If a WG -00 is 
> missing items or needs revision to meet the needs of the group, in 
> other words, that's normal--send text.
>
> Ted, Magnus, and Cullen
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb