Re: [rsvp-dir] RSVP directorate formed

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Thu, 08 July 2010 14:46 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
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 5CB3A3A6924 for <rsvp-dir@core3.amsl.com>; Thu, 8 Jul 2010 07:46:05 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DWXwf0GcmIOG for <rsvp-dir@core3.amsl.com>; Thu, 8 Jul 2010 07:46:04 -0700 (PDT)
Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by core3.amsl.com (Postfix) with ESMTP id D97963A6AD0 for <rsvp-dir@ietf.org>; Thu, 8 Jul 2010 07:46:00 -0700 (PDT)
Received: from gorry-mac.erg.abdn.ac.uk (gorry-mac.erg.abdn.ac.uk [139.133.207.5]) (authenticated bits=0) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id o68Ek2T6014157 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 8 Jul 2010 15:46:02 +0100 (BST)
Message-ID: <4C35E4AA.2050604@erg.abdn.ac.uk>
Date: Thu, 08 Jul 2010 15:46:02 +0100
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland, No SC013683.
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: rsvp-dir@ietf.org
References: <E119C8DF-64CE-46DD-976B-1C9750720F45@nokia.com> <201005101816.o4AIGdHL021437@sj-core-2.cisco.com>
In-Reply-To: <201005101816.o4AIGdHL021437@sj-core-2.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
X-Mailman-Approved-At: Thu, 08 Jul 2010 09:47:46 -0700
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Subject: Re: [rsvp-dir] RSVP directorate formed
X-BeenThere: rsvp-dir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
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, 08 Jul 2010 14:46:05 -0000

Hello RSVP directorate!

Now that a directorate exists, I'd like help in two ways to manage the 
RSVP work in TSVWG:

1) I'm assuming that you will help with selecting appropriate work for 
adoption of TSVWG (as per the top bullet below). How do you see this 
working, specifically there are a number of drafts that currently have 
not become work items - despite author pleas - while we waited for 
clarification of how to handle RSVP work. Undoubtedly I'll be asked if 
these can become work items. As usual I'll push-back on need to do the 
work, and people to review/contribute to the drafts. Are there current 
drafts know to the directorate that would seem ready and important 
enough that the WG should consider taking these on?

2) Would someone from the directorate like to say "hi we're here and 
this is our remit" - taht would be helpful in the tsvwg meeting!

Gorry

> At 08:01 AM 5/10/2010, Lars Eggert wrote:
>> Hi,
>>
>> following the discussion during the IETF-77 TSVAREA meeting on how to 
>> better review and progress extensions to (non-TE) RSVP and IntServ, 
>> the transport area directors have formed a new RSVP directorate and 
>> given it these tasks:
>>
>>   * Review of all new work related to RSVP and Integrated Services that
>>     is proposed for IETF adoption. The purpose of this review is to
>>     advise the ADs and the chairs of the Transport Area Working Group
>>     (TSVWG) on whether a particular proposal should be taken on as a
>>     work item. The directorate will continue to guide and review such
>>     new work in TSVWG until it is ready for publication as an RFC.
>>
>>   * Review of selected documents during IETF last call or under IESG
>>     review. The directorate monitors ongoing IETF work and should
>>     independently decide when a document will benefit from their review,
>>     assign a reviewer and enter into a follow-on discussion with the
>>     authors. When deemed necessary, the area directors will on occasion
>>     directly consult the directorate while forming their opinion on
>>     selected documents being under review by the IESG.
>>
>>   * Cross-working group review. RSVP documents may have relevance to
>>     several working groups, including TSVWG and MPLS-related groups
>>     such as MPLS WG and CCAMP WG. The directorate will ensure that
>>     drafts submitted to TSV WG are reviewed in the appropriate 
>> MPLS-related
>>     WGs if necessary, and will bring drafts from the MPLS-related WGs
>>     to the attention of the TSV WG as appropriate.
>>
>> The directorate can be reached at rsv-dir@ietf.org. Additional 
>> information about the directorate is at 
>> http://trac.tools.ietf.org/area/tsv/trac/wiki/RSVP-Directorate.
>>
>> Lars
> 
>