Re: [rsvp-dir] Our first work items for RSVP Directorate

Bob,
 The RSVP directorate will not, of course, decide the fate of these documents. Our job is to review documents and advise the TSV ADs and TSVWG chairs. I'm just trying to jump start that process, so that when the authors show up at TSVWG, (a) the chairs will be able to say whether it's even worth the time of the WG to hear a presentation on the draft (b) there will be at least a couple of people in the audience who have read the drafts.

 For the record, all 3 of the drafts mentioned below were presented at IETF 76. The authors have asked that they be taken on as TSVWG items.

Bruce

On Jun 4, 2010, at 1:39 PM, Bob Briscoe wrote:

> Bruce,
> 
> Will take a look.
> 
> A process break point.... for a draft to be adopted by a working group, the authors have to present it (possibly a couple of times) then justify to the WG why it is ready to be adopted as a WG item. Shouldn't we raise a similar bar for these drafts, rather than pick up "a few drafts floating around"?
> 
> We have probably all seen these presented (tho I personally haven't been in CCAMP so I will have missed narayanan). But I'd now like to see the authors justify to us why they are ready to be WG items, against the criteria established recently.
> 
> Is this fair?
> 
> 
> Bob
> 
> At 17:41 04/06/2010, Bruce Davie wrote:
>> Folks,
>> There are a few drafts floating around that I think we should take a look at and make a recommendation to the ADs regarding their suitability for the TSVWG. These drafts are:
>> 
>> draft-narayanan-tsvwg-rsvp-resource-sharing-02
>> 
>> draft-lefaucheur-tsvwg-rsvp-multiple-preemption-02.txt
>> draft-polk-tsvwg-intserv-multiple-tspec-03.txt
>> 
>> The first one seems pretty non-controversial. Here are comments from the author:
>> >
>> > draft-narayanan-tsvwg-rsvp-resource-sharing-02 is now a companion draft to draft-berger-ccamp-assoc-info-01, and contains only the RSVP-CAC-specific part of the resource sharing thingy. Given that TSVWG is the place for RSVP CAC extensions, yes, I would think TSVWG is the place for it. It's a very small draft basically defining a new codepoint (Resource Sharing Remote-ID Association) with a small behavioural change (only treat this Association-ID as binding on the Resv, not on the Path), so I don't envision any significant backpressure of the form "this is not a small change to RSVP".
>> 
>> I would like to recommend that this be made a TSVWG work item. Any comments or concerns?
>> 
>> The lefaucheur and polk drafts should probably be treated as a pair. Both relate to the issue of reserving an appropriate level of resource (e.g. bandwidth) in a single round trip when it is not known in advance how much resource is available. This is quite helpful, for example, in a video conferencing application that has a choice of codecs. The polk draft in particular was (I think) a catalyst for the RSVP discussion in Anaheim because it seemed to be stretching the scope of what has normally been done in TSVWG for RSVP maintenance.
>> 
>> Given the scope of the directorate, I would like a couple of folks on the directorate to review those drafts and then we can discuss whether they should become TSVWG work items. Can I have some volunteers?
>> 
>> Thanks,
>> Bruce
>> 
>> 
>> _______________________________________________
>> rsvp-dir mailing list
>> rsvp-dir@ietf.org
>> https://www.ietf.org/mailman/listinfo/rsvp-dir
> 
> ________________________________________________________________
> Bob Briscoe,                                BT Innovate & Design 