Re: [rtcweb] Question about the status of various drafts

Cullen Jennings <fluffy@iii.ca> Fri, 26 July 2013 19:59 UTC

Return-Path: <fluffy@iii.ca>
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 09FBC11E80FB for <rtcweb@ietfa.amsl.com>; Fri, 26 Jul 2013 12:59:00 -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 lsNlBQC8AEQu for <rtcweb@ietfa.amsl.com>; Fri, 26 Jul 2013 12:58:55 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 7CD4A11E8127 for <rtcweb@ietf.org>; Fri, 26 Jul 2013 12:58:54 -0700 (PDT)
Received: from [192.168.4.100] (unknown [128.107.239.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 68C3D22E1FA; Fri, 26 Jul 2013 15:58:47 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C40AE21@ESESSMB209.ericsson.se>
Date: Fri, 26 Jul 2013 13:58:45 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <572C6849-5315-40CB-A3E2-D59AD9BDC4F7@iii.ca>
References: <7A95191A-6488-435E-B491-FEF3A6AC342F@iii.ca> <BLU169-W823344CCF942CC7B75815E937D0@phx.gbl>, <C8F0073F-9B59-4FF8-BC04-5458221634A4@iii.ca> <7594FB04B1934943A5C02806D1A2204B1C40AE21@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1508)
Cc: "rtcweb_ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Question about the status of various drafts
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, 26 Jul 2013 19:59:00 -0000

I'm in the process of updating it it all - I'll try and make reasonable estimates. Note some of the individual drafts are planned to be AD sponsored. 


On Jul 26, 2013, at 12:56 PM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:

> Hi Cullen,
>  
> I may missed something, but it seems a little strange to me when individual drafts, that haven't even been adopted yet, are indicated as 70-80% complete...
>  
> Some drafts have also expired.
>  
> Regards,
>  
> Christer
>  
> 
> 
> Sent from Windows using TouchDown (www.nitrodesk.com)
> 
> -----Original Message-----
> From: Cullen Jennings [fluffy@iii.ca]
> To: Bernard Aboba [bernard_aboba@hotmail.com]
> CC: rtcweb@ietf.org [rtcweb@ietf.org]
> Subject: Re: [rtcweb] Question about the status of various drafts
> 
> Yah, I get your point. I will try and find a way to better represent this on the slides. 
> 
> 
> On Jul 5, 2013, at 3:25 PM, Bernard Aboba <bernard_aboba@hotmail.com> wrote:
> 
> > I think you need to take dependencies into account.   There are several reasons for this: 
> > 
> >    a. Until you've gone through the dependency graph for the items, the full list of documents that need to be tracked isn't known. 
> >    b. Estimates of completion are dependent on the progress of normative dependencies (e.g. they can't be published until the dependencies are resolved). 
> > 
> > As an example,  draft-ietf-rtcweb-overview (which is listed as 80 percent complete) has normative references to the following drafts: 
> > 
> >    [I-D.ietf-mmusic-sctp-sdp] 70
> >    [I-D.ietf-rtcweb-audio] 50
> >    [I-D.ietf-rtcweb-data-channel] 70
> >    [I-D.ietf-rtcweb-jsep] 50
> >    [I-D.ietf-rtcweb-rtp-usage] 40
> >    [I-D.ietf-rtcweb-security] 80
> >    [I-D.ietf-rtcweb-security-arch] 80
> >    [I-D.nandakumar-rtcweb-stun-uri] 80
> >    [I-D.tuexen-tsvwg-sctp-dtls-encaps] 70
> >             
> > Since draft-ietf-rtcweb-overview is dependent on a document (rtp usage) which only has an estimate of 40 percent done) I'd say that the estimate is probably closer to 40 than 80. 
> > 
> > 
> > > From: fluffy@iii.ca
> > > Date: Thu, 4 Jul 2013 17:47:20 -0700
> > > To: rtcweb@ietf.org
> > > Subject: [rtcweb] Question about the status of various drafts
> > > 
> > > 
> > > As part of putting together some chair slides for Berlin, I'm trying to get a very rough idea of where things are. I'd like to get folks input on what percent done various drafts are where Done is a published RFC. 
> > > 
> > > This is nearly impossible to do at any level of accuracy but I do want to get a vague idea. I took a very rough stab below just to have a starting point to get the conversation going. I'm sure my numbers are mostly wrong but I have tried to ask a few people and sort of take the central cluster of the guess. If you think I am way out, please provide some feedback of what you think the number actually is.
> > > 
> > > I'm happy to get feedback on specific drafts or feedback of the form they are all too low or too high. I do encourage people to realistically look at the data tracker to see how long other drafts have taken for each stage to get a baseline instead of just going with their gut feel. 
> > > 
> > > Thanks, Cullen
> > > 
> > > PS - if you are an author and look at the number next to your draft and think it is way off, please please, say something. 
> > > 
> > > 
> > > 
> > > draft-ietf-rtcweb-overview   80
> > > draft-ietf-rtcweb-use-cases-and-requirements        70
> > > http://dev.w3.org/2011/webrtc/editor/getusermedia.html       70
> > > draft-burnett-rtcweb-constraints-registry    80
> > > http://dev.w3.org/2011/webrtc/editor/webrtc.html     50
> > > draft-nandakumar-rtcweb-stun-uri     80
> > > draft-petithuguenin-behave-turn-uris         80
> > > draft-ietf-rtcweb-security   80
> > > draft-ietf-rtcweb-security-arch      80
> > > draft-muthu-behave-consent-freshness-02 50
> > > draft-ietf-rtcweb-data-channel       70
> > > draft-ietf-mmusic-sctp-sdp   70
> > > draft-jesup-rtcweb-data-protocol 50
> > > draft-ietf-tsvwg-sctp-dtls-encaps    70
> > > draft-ietf-rtcweb-rtp-usage  40
> > > draft-ietf-avtcore-6222bis   80
> > > draft-ietf-avtcore-avp-codecs        80
> > > draft-ietf-avtcore-srtp-encrypted-header-ext        80
> > > draft-ietf-avtext-multiple-clock-rates       70
> > > draft-lennox-rtcweb-rtp-media-type-mux 80
> > > draft-ietf-avtcore-rtp-circuit-breakers      70
> > > draft-ietf-avtcore-multi-media-rtp-session 70
> > > draft-lennox-avtcore-rtp-multi-stream        70
> > > draft-ietf-rtcweb-jsep       50
> > > draft-ietf-mmusic-msid       70
> > > draft-rescorla-mmusic-ice-trickle    25
> > > draft-ietf-mmusic-sdp-bundle-negotiation    50
> > > draft-nandakumar-mmusic-sdp-mux-attributes  25
> > > draft-dhesikan-tsvwg-rtcweb-qos      10 or 90
> > > draft-ietf-rtcweb-audio      50
> > > draft-ietf-payload-rtp-opus  90
> > > draft-ietf-payload-vp8-08    95
> > > 
> > > 
> > > _______________________________________________
> > > rtcweb mailing list
> > > rtcweb@ietf.org
> > > https://www.ietf.org/mailman/listinfo/rtcweb
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb