RE: hop-by-hop and router alert options [Re: Question about use of RSVP in Production Networks]
"Ping Pan" <ppan@hammerheadsystems.com> Fri, 13 August 2004 01:43 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23079; Thu, 12 Aug 2004 21:43:45 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BvRBl-00030p-T2; Thu, 12 Aug 2004 21:49:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BvR4B-0000pl-UX; Thu, 12 Aug 2004 21:41:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BvR1N-0000MJ-Gt for ietf@megatron.ietf.org; Thu, 12 Aug 2004 21:38:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22814 for <ietf@ietf.org>; Thu, 12 Aug 2004 21:38:15 -0400 (EDT)
Received: from mail.hammerheadsystems.com ([12.108.173.98]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BvR6L-0002ts-In for ietf@ietf.org; Thu, 12 Aug 2004 21:43:32 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 12 Aug 2004 18:37:39 -0700
Message-ID: <2DAC9E7A4640234B85975565E5D83AE173056C@srvcaexg01.headquarters.hammerheadsystems.com>
Thread-Topic: hop-by-hop and router alert options [Re: Question about use of RSVP in Production Networks]
Thread-Index: AcSAtDT84nAGCdv1Q6SBKzifOrHdagAH+S1A
From: Ping Pan <ppan@hammerheadsystems.com>
To: Pekka Savola <pekkas@netcore.fi>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
Subject: RE: hop-by-hop and router alert options [Re: Question about use of RSVP in Production Networks]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: quoted-printable
Pekka, > > I really really hope that there has been a problem statement... > Here is an old draft on RSVP issues: http://www1.cs.columbia.edu/~pingpan/papers/draft-pan-nsis-rsvp-transpor t-01.txt > Further point where you can use path-coupled signalling, you mean? > Not really, as there seems to be something seriously broken > if you need set up priorization except in well-defined points > in the network. > And to achieve that, you could use a "bandwidth broker": > either it's able to set up the required bandwidth (it's in > the same site, or at a site your site has a roaming agreement > with), or it isn't and the approach is going to fail in any > case, because the sites out in the Internet don't want > outsiders to request bandwidth allocations. > If someone has a BB, would you and your boss buy and deploy it? :-) You will certainly get a lot of wasted code and effort, and make the day for many researchers. > What I can't figure why this is happening. I guess the IESG > must have been asleep, or the most people just thought, > "well.. let them waste their energy on that.. at least they > don't bother us while they are bashing the heads in the wall.." > One word of caution: never ask too much from any standard body, or any sausage-making organizaion in that matter. If you have a desire for something cool and money, either build it yourself, or ask for it from vendors directly. :-) 2 cents, - Ping _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- Re: hop-by-hop and router alert options [Re: Ques… Bob Braden
- Re: hop-by-hop and router alert options [Re: Ques… Pekka Savola
- RE: hop-by-hop and router alert options [Re: Ques… Ping Pan
- Re: hop-by-hop and router alert options [Re: Ques… John Loughney
- Re: hop-by-hop and router alert options [Re: Ques… Pekka Savola
- Re: hop-by-hop and router alert options Iljitsch van Beijnum
- Re: hop-by-hop and router alert options [Re: Ques… Bob Braden
- Re: hop-by-hop and router alert options [Re: Ques… Pekka Savola
- Re: hop-by-hop and router alert options Pekka Savola