[rsvp-dir] Fwd: Update from RSVP directorate on RSVP Candidate items?

Bruce Davie <bdavie@cisco.com> Tue, 27 July 2010 14:40 UTC

Return-Path: <bdavie@cisco.com>
X-Original-To: rsvp-dir@core3.amsl.com
Delivered-To: rsvp-dir@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 0CACB3A69BC for <rsvp-dir@core3.amsl.com>; Tue, 27 Jul 2010 07:40:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id PSk1Od-LNN2p for <rsvp-dir@core3.amsl.com>; Tue, 27 Jul 2010 07:40:07 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com []) by core3.amsl.com (Postfix) with ESMTP id E09953A6BE0 for <rsvp-dir@ietf.org>; Tue, 27 Jul 2010 07:40:01 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAGOMTkxAZnwN/2dsb2JhbACfZnGmTZtFAoU0BIhq
X-IronPort-AV: E=Sophos; i="4.55,268,1278288000"; d="scan'208,217"; a="139751061"
Received: from rtp-core-2.cisco.com ([]) by rtp-iport-1.cisco.com with ESMTP; 27 Jul 2010 14:40:23 +0000
Received: from dhcp-161-44-173-109.cisco.com (dhcp-161-44-173-109.cisco.com []) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o6REeLUs011133 for <rsvp-dir@ietf.org>; Tue, 27 Jul 2010 14:40:21 GMT
From: Bruce Davie <bdavie@cisco.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-1--860772023"
Date: Tue, 27 Jul 2010 10:40:22 -0400
References: <4C4EE303.5080300@erg.abdn.ac.uk>
To: rsvp-dir@ietf.org
Message-Id: <C1CDBAB0-6BB1-4DB5-9250-CD0811BCC730@cisco.com>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Subject: [rsvp-dir] Fwd: Update from RSVP directorate on RSVP Candidate items?
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: Tue, 27 Jul 2010 14:40:39 -0000

 I don't feel I can speak for the directorate at this point, as I have only heard back from Bob Briscoe to date, and only with questions. For the record, I am in favor of the WG adopting the 3 drafts that I asked you to look at, but I'd like to hear from some more directorate members.

Is anyone there?


Begin forwarded message:

> From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
> Date: July 27, 2010 9:45:39 AM EDT
> To: Francois Le Faucheur <flefauch@cisco.com>
> Cc: rsvp-dir@ietf.org, "tsvwg-chairs@tools.ietf.org chair" <tsvwg-chairs@tools.ietf.org>, tsvwg WG <tsvwg@ietf.org>
> Subject: Re: [rsvp-dir] Update from RSVP directorate on RSVP Candidate items?
> Reply-To: gorry@erg.abdn.ac.uk
> It would indeed be good to get a summary of feedback from the rsvp directorate on these 2 drafts - please reply to tsv-ads and tsvwg-chairs, if it is appropriate, please also feel free to copy the tsvwg list.
> My understanding is that this consultation is to provide feedback for the ADs and Chairs. These inputs can help to determine if there is sufficient interest and a need to adopt a draft. The RSVP directorate are not enabled to make a decision on what drafts are adopted.
> If the directorate provide comments that support progression it may be helpful to also suggest some document reviewers who would commit to comment on the document both as it progresses through the WG *and* in the WGLC.
> Gorry
> On 27/07/2010 15:26, Francois Le Faucheur wrote:
>> Hello RSVP Directorate,
>> Any chance to get an update from RSVP Directorate regarding the
>> submitted RSVP candidate items before TSVWG (Thur am)?
>> I believe the submitted candidate items are:
>> * RSVP Flexible Resource Sharing
>> Also, for memory:
>> * the meaty part of "draft-narayanan-tsvwg-rsvp-resource-sharing" has
>> been merged into "draft-berger-ccamp-assoc-info"
>> * so the latest version of "draft-narayanan-tsvwg-rsvp-resource-sharing"
>> only contains a smaller optional delta on top of
>> "draft-berger-ccamp-assoc-info"
>> * the CCAMP plan is that "draft-berger-ccamp-assoc-info" be progressed
>> in CCAMP
>> * I believe CCAMP is also proposing to progress
>> "draft-narayanan-tsvwg-rsvp-resource-sharing" as a companion document
>> (this proposal does make sense to me since, again, the real meat is in
>> "draft-berger-ccamp-assoc-info").
>> It would be good to get views on this plan.
>> Thanks
>> Francois
>>> On 10 May 2010, at 15:01, 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
>>>> <mailto:rsv-dir@ietf.org>. Additional information about the
>>>> directorate is at
>>>> http://trac.tools.ietf.org/area/tsv/trac/wiki/RSVP-Directorate.
>>>> Lars
>> *
>> Francois Le Faucheur*
>> *Distinguished Engineer*
>> *Corporate Development*
>> flefauch@cisco.com <mailto:flefauch@cisco.com>
>> Phone: *+33 49 723 2619*
>> Mobile: *+33 6 19 98 50 90*
>> *Cisco Systems France*
>> Greenside
>> 400 Ave de Roumanille
>> 06410 Sophia Antipolis
>> France
>> Cisco.com <http://www.cisco.com>
>> Think before you print.
>> This email may contain confidential and privileged material for the sole
>> use of the intended recipient. Any review, use, distribution or
>> disclosure by others is strictly prohibited. If you are not the intended
>> recipient (or authorized to receive for the recipient), please contact
>> the sender by reply email and delete all copies of this message.
>> Cisco Systems France, Société à responsabiité limitée, Rue Camille
>> Desmoulins – Imm Atlantis Zac Forum Seine Ilot 7 92130 Issy les
>> Moulineaux, Au capital de 91.470 €, 349 166 561 RCS Nanterre, Directeur
>> de la publication: Jean-Luc Michel Givone.
>> For corporate legal information go to:
>> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
> _______________________________________________
> rsvp-dir mailing list
> rsvp-dir@ietf.org
> https://www.ietf.org/mailman/listinfo/rsvp-dir