Re: [rsvp-dir] RSVP Directorate Reviews

Bob Briscoe <bob.briscoe@bt.com> Thu, 31 March 2011 08:56 UTC

Return-Path: <bob.briscoe@bt.com>
X-Original-To: rsvp-dir@core3.amsl.com
Delivered-To: rsvp-dir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D21728C11B for <rsvp-dir@core3.amsl.com>; Thu, 31 Mar 2011 01:56:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.474
X-Spam-Level:
X-Spam-Status: No, score=-3.474 tagged_above=-999 required=5 tests=[AWL=0.125, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QPNQpl9I5RhE for <rsvp-dir@core3.amsl.com>; Thu, 31 Mar 2011 01:56:42 -0700 (PDT)
Received: from smtp1.smtp.bt.com (smtp1.smtp.bt.com [217.32.164.137]) by core3.amsl.com (Postfix) with ESMTP id 23DBF28C0F1 for <rsvp-dir@ietf.org>; Thu, 31 Mar 2011 01:56:41 -0700 (PDT)
Received: from i2kc08-ukbr.domain1.systemhost.net ([193.113.197.71]) by smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 31 Mar 2011 09:58:20 +0100
Received: from cbibipnt08.iuser.iroot.adidom.com ([147.149.100.81]) by i2kc08-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(6.0.3790.4675); Thu, 31 Mar 2011 09:58:20 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by cbibipnt08.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a P0803.399); id 1301561899405; Thu, 31 Mar 2011 09:58:19 +0100
Received: from MUT.jungle.bt.co.uk ([10.73.129.212]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id p2V8wH8Y023340; Thu, 31 Mar 2011 09:58:17 +0100
Message-Id: <201103310858.p2V8wH8Y023340@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 31 Mar 2011 09:58:14 +0100
To: Bruce Davie <bdavie@cisco.com>
From: Bob Briscoe <bob.briscoe@bt.com>
In-Reply-To: <0032A84F-8088-4855-BB4A-02AB9DAEE5F7@cisco.com>
References: <A9C46E7F-680F-4541-B496-5ED3FD563E6D@cisco.com> <4D93265E.2060703@labn.net> <0032A84F-8088-4855-BB4A-02AB9DAEE5F7@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 31 Mar 2011 08:58:20.0985 (UTC) FILETIME=[C8DBAA90:01CBEF81]
Cc: tsvwg-ads@tools.ietf.org, rsvp-dir@ietf.org
Subject: Re: [rsvp-dir] RSVP Directorate Reviews
X-BeenThere: rsvp-dir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: RSVP directorate <rsvp-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rsvp-dir>, <mailto:rsvp-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rsvp-dir>
List-Post: <mailto:rsvp-dir@ietf.org>
List-Help: <mailto:rsvp-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rsvp-dir>, <mailto:rsvp-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 08:56:43 -0000

Bruce,

I have detailed pen-written reviews of:
- rsvp-multiple-preemption-02 (still at 02)
- intserv-multiple-tspec-03 (now at 06)

Back in Sep'11, I should have said I have to go into background mode 
regarding IETF activities for a few months. Since, loads of stuff has 
backed up due to personal & work issues outside my control. I'm out 
of the end of the tunnel now, and eating up the front of the queue so 
that the queue length is now shrinking, but...

Typing these reviews up is now way down my priority stack. If taking 
paper copies away from Prague would be useful, I can offer that at 
least. No-one will be able to understand my scrawlings, but...


Bob

At 17:36 30/03/2011, Bruce Davie wrote:

>On Mar 30, 2011, at 8:47 AM, Lou Berger wrote:
>
> > Bruce/Dave,
> >       First let me say that review is goodness and I have no issues with
> > providing input on the suitability for *acceptance* as a WG document
> > based on technical review.  But I'm left with a couple of questions:
> >
> > 1) It sounds like you are expecting a non-technical / market review of
> > the drafts by the rsvp-dir.  Is this correct?
>
>I would tend to say that the review guidelines I wrote are trying to 
>get at 2 key issues:
>  - does this draft tackle a problem worth solving?
>  - does it do so in a technically correct way?
>
>So, no, I don't really view this as a non-technical review. But the 
>first question has some not-totally-technical aspects, I guess.
>
> >
> > 2) What work / input do you expect from the WG before a LC is issued for
> > a document that has gone through the described process?
>
>David (or Gorry) should maybe answer this, but I think they are 
>looking for adequate review from *somewhere*, either the directorate 
>(which contains a lot of RSVP experts) or other WG members (which is 
>the reason I was asking the directorate to try to recruit more reviewers).
>
>It seems to me that the ADs & Chairs are looking for a pretty large 
>number of reviews even before adopting the draft as a WG item, which 
>should mean that any adopted draft should be in fairly good shape.
>
>Bruce
>
> >
> > Much thanks,
> > Lou
> >
> > On 3/30/2011 9:57 AM, Bruce Davie wrote:
> >> I met with the TSV ADs on Monday and we talked about how we 
> might make more progress with the RSVP-related drafts that are 
> coming through TSVWG. As you know, the directorate has not to date 
> produced many reviews of the drafts, and the ADs really would like 
> to see more reviews, and promises to review mature drafts, in order 
> to feel confident that the drafts are worth the time and attention 
> of the WG. So, first of all, I'd like to respectfully ask the 
> Directorate members to step up and commit to reviewing these 
> drafts. The 2 drafts that need attention right now are:
> >>
> >> draft-polk-tsvwg-intserv-multiple-tspec-06.txt
> >> draft-polk-tsvwg-rsvp-app-id-vv-profiles-02.txt
> >>
> >> Many of you have spoken in favor of the former, but AFAIK, only 
> Lou and I have actually provided detailed reviews. Could I ask for 
> one or two more reviewers? Even a promise of a review would be nice.
> >>
> >> For the record, I will also review the second draft.
> >>
> >> To spread the load around, we should be trying to find people 
> outside the directorate who can do reviews. I have asked Ken 
> Carlberg; can any of you think of, or find, others who might do 
> reviews? If we want to keep RSVP standards in the IETF, we really 
> need a stable of reviewers.
> >>
> >> Finally, David Harrington asked me to draw up some review 
> guidelines, so here is my attempt to do that.
> >>
> >> A review should address why (or whether) the draft warrants the 
> attention of TSVWG. That justification should cover the following 
> points to the extent possible:
> >> - What problem with existing RSVP/Intserv is the draft trying to solve?
> >> - What class of application will benefit if the draft becomes a standard?
> >> - Is there another way to solve this problem (or might someone 
> think there is)? If so, explain how this solution is better.
> >> - What new capability will we have if this draft becomes a standard?
> >> - What community of users will benefit from this work?
> >>
> >> In addition, the review should sanity-check the draft for 
> technical correctness in terms of its relationship to the RSVP and 
> Intserv specifications.
> >>
> >> Thanks.
> >>
> >> Bruce Davie
> >>
> >>
> >>
> >> _______________________________________________
> >> rsvp-dir mailing list
> >> rsvp-dir@ietf.org
> >> https://www.ietf.org/mailman/listinfo/rsvp-dir
> >>
> >>
> >>
> >>
>
>_______________________________________________
>rsvp-dir mailing list
>rsvp-dir@ietf.org
>https://www.ietf.org/mailman/listinfo/rsvp-dir

________________________________________________________________
Bob Briscoe,                                BT Innovate & Design