Re: [tsv-area] FSA signalling issues

Roland Bless <bless@tm.uka.de> Wed, 27 August 2008 07:17 UTC

Return-Path: <tsv-area-bounces@ietf.org>
X-Original-To: tsv-area-archive@optimus.ietf.org
Delivered-To: ietfarch-tsv-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 555BC3A6BB7; Wed, 27 Aug 2008 00:17:56 -0700 (PDT)
X-Original-To: tsv-area@core3.amsl.com
Delivered-To: tsv-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ABE663A68BD; Wed, 27 Aug 2008 00:17:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.351
X-Spam-Level:
X-Spam-Status: No, score=0.351 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_DE=0.35]
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 ZF6XgDfEN40L; Wed, 27 Aug 2008 00:17:54 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by core3.amsl.com (Postfix) with ESMTP id CBADE3A687D; Wed, 27 Aug 2008 00:17:53 -0700 (PDT)
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5]) by iramx2.ira.uni-karlsruhe.de with esmtps id 1KYFHs-000667-IL; Wed, 27 Aug 2008 09:17:54 +0200
Received: from i72ms.tm.uni-karlsruhe.de ([141.3.70.5] helo=smtp.ipv6.tm.uni-karlsruhe.de) by irams1.ira.uni-karlsruhe.de with esmtps id 1KYFHs-0001qn-Ck; Wed, 27 Aug 2008 09:17:52 +0200
Received: from vorta.tm.uka.de (vorta.ipv6.tm.uni-karlsruhe.de [IPv6:2001:638:204:6:21b:fcff:fe96:fe02]) by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id 4CAD42FC056; Wed, 27 Aug 2008 09:17:52 +0200 (CEST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by vorta.tm.uka.de (Postfix) with ESMTP id 30D0710382; Wed, 27 Aug 2008 09:17:52 +0200 (CEST)
Message-ID: <48B4FF9F.5050205@tm.uka.de>
Date: Wed, 27 Aug 2008 09:17:51 +0200
From: Roland Bless <bless@tm.uka.de>
Organization: Institute of Telematics, University of Karlsruhe
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: JOHN ADAMS <j.l.adams1@btinternet.com>
References: <772264.35065.qm@web86512.mail.ukl.yahoo.com>
In-Reply-To: <772264.35065.qm@web86512.mail.ukl.yahoo.com>
X-Enigmail-Version: 0.95.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: tsv-area@ietf.org, "nsis@ietf.org" <nsis@ietf.org>
Subject: Re: [tsv-area] FSA signalling issues
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
Sender: tsv-area-bounces@ietf.org
Errors-To: tsv-area-bounces@ietf.org

Hi John,

JOHN ADAMS wrote:
> I gave a talk at Dublin in the Transport Area Open meeting. The subject
> was developments
> at the ITU-T on Flow State Aware (FSA) standardisation.
>  
> A question raised at the IETF was (roughly) "why isn't a new extension
> of RSVP being proposed
> to accommodate the requirements of FSA signalling?"
>  
> I attach an intial response to that question in the form of an issues
> list that will also be proposed as
> a new Appendix of the draft ITU Recommendation Q.flowstatesig. The
> conclusions of this first
> analysis are that:
> - it is an aim that we try our hardest to fit within the preferred
> architectural framework of RSVP
> - however there are a number of challenging issues and, since that is
> the case, the preferred approach
>    is to keep other options open.
>  
> Please get back to me with issues that will help the continued progress
> of FSA at the next IETF

It seems that the work in the NSIS WG would be a much better fit
to FSA than RSVP. Furthermore, since it is easier to extend NSIS
than RSVP, you should definitely have a look at the work there.

http://tools.ietf.org/wg/nsis/

However, I have to look at the FSA in order to better understand
your objectives and to find a good match...

Regards,
 Roland