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

Harald Alvestrand <harald@alvestrand.no> Sat, 27 July 2013 14:27 UTC

Return-Path: <harald@alvestrand.no>
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 7BBE321F9AA8 for <rtcweb@ietfa.amsl.com>; Sat, 27 Jul 2013 07:27:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level:
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 YtsDCT3CTbzG for <rtcweb@ietfa.amsl.com>; Sat, 27 Jul 2013 07:27:39 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 5802521F99FB for <rtcweb@ietf.org>; Sat, 27 Jul 2013 07:27:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 2658A39E17B for <rtcweb@ietf.org>; Sat, 27 Jul 2013 16:27:38 +0200 (CEST)
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 sU8vnTPNBeNM for <rtcweb@ietf.org>; Sat, 27 Jul 2013 16:27:36 +0200 (CEST)
Received: from [10.0.0.79] (unknown [91.113.173.59]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 1E98739E13F for <rtcweb@ietf.org>; Sat, 27 Jul 2013 16:27:36 +0200 (CEST)
Message-ID: <51F3D8D7.10409@alvestrand.no>
Date: Sat, 27 Jul 2013 16:27:35 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <7A95191A-6488-435E-B491-FEF3A6AC342F@iii.ca> <BLU169-W823344CCF942CC7B75815E937D0@phx.gbl>
In-Reply-To: <BLU169-W823344CCF942CC7B75815E937D0@phx.gbl>
Content-Type: multipart/alternative; boundary="------------020804010305020801010101"
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: Sat, 27 Jul 2013 14:27:44 -0000

On 07/05/2013 11:25 PM, Bernard Aboba 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.

I don't know exactly what Cullen meant by the percentages, but I don't
think he intended them to be sequential the way publication dependencies
are.

If, for instance, he was thinking about how many percent of the text
needed to change semantically before it was done, I think 80% for
"overview" may be right (unless we choose to change the approach by some
large delta).

If you want to draw up a dependency graph .... well, since -overview-
was intended to be the one that points to all the others, it's
reasonable to put it last in the graph. That's what it's for.


>
>
> > 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