[72attendees] FSA signalling issues

JOHN ADAMS <j.l.adams1@btinternet.com> Tue, 26 August 2008 19:53 UTC

Return-Path: <72attendees-bounces@ietf.org>
X-Original-To: 72attendees-archive@ietf.org
Delivered-To: ietfarch-72attendees-archive@core3.amsl.com
Received: from [] (localhost []) by core3.amsl.com (Postfix) with ESMTP id C9B1228C216; Tue, 26 Aug 2008 12:53:10 -0700 (PDT)
X-Original-To: 72attendees@core3.amsl.com
Delivered-To: 72attendees@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id B9F043A6A01 for <72attendees@core3.amsl.com>; Tue, 26 Aug 2008 12:53:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id oM6UoZ-VNtrf for <72attendees@core3.amsl.com>; Tue, 26 Aug 2008 12:53:07 -0700 (PDT)
Received: from web86507.mail.ukl.yahoo.com (web86507.mail.ukl.yahoo.com []) by core3.amsl.com (Postfix) with SMTP id C60E53A6817 for <72attendees@ietf.org>; Tue, 26 Aug 2008 12:53:06 -0700 (PDT)
Received: (qmail 41761 invoked by uid 60001); 26 Aug 2008 19:53:07 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=btinternet.com; h=Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Message-ID; b=aepun89BKipVHpcsQtHpO25G+cPWAzdhHBaNaX3/YtZmViSu9F1xjZSgzQguJc3V+doMc6LxYx+nKcUAcjb/IDWWcMAVtZAglbCkkd2z50g9WHHavIaMlejOCn0X3yae9gAOvvs3bw520fKKW135jDvrV8wFdcrKzwOciqA/D0s=;
Received: from [] by web86507.mail.ukl.yahoo.com via HTTP; Tue, 26 Aug 2008 19:53:07 GMT
X-Mailer: YahooMailRC/1042.40 YahooMailWebService/0.7.218
Date: Tue, 26 Aug 2008 19:53:07 +0000 (GMT)
From: JOHN ADAMS <j.l.adams1@btinternet.com>
To: 72attendees@ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-899389963-1219780387=:41468"
Message-ID: <578148.41468.qm@web86507.mail.ukl.yahoo.com>
Subject: [72attendees] FSA signalling issues
X-BeenThere: 72attendees@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: JOHN ADAMS <j.l.adams1@btinternet.com>
List-Id: "Discussion list for the attendees of IETF 72 meeting." <72attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/72attendees>, <mailto:72attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/72attendees>
List-Post: <mailto:72attendees@ietf.org>
List-Help: <mailto:72attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/72attendees>, <mailto:72attendees-request@ietf.org?subject=subscribe>
Sender: 72attendees-bounces@ietf.org
Errors-To: 72attendees-bounces@ietf.org

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
72attendees mailing list