Re: PQC and QOSPF

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Fri, 24 July 1998 18:50 UTC

Delivery-Date: Fri, 24 Jul 1998 14:51:00 -0400
Return-Path: owner-qosr@ca.newbridge.com
Received: from ns.newbridge.com (ns.newbridge.com [192.75.23.67]) by ietf.org (8.8.5/8.8.7a) with ESMTP id OAA23495 for <ietf-archive@ietf.org>; Fri, 24 Jul 1998 14:50:59 -0400 (EDT)
Received: (from smtpd@localhost) by ns.newbridge.com (8.8.8/8.6.12) id OAA14724; Fri, 24 Jul 1998 14:42:13 -0400 (EDT)
Received: from kanata-gw1.newbridge.com(192.75.23.72), claiming to be "kanata-gw1.ca.newbridge.com" via SMTP by ns.newbridge.com, id smtpdAAAa14684; Fri Jul 24 14:42:03 1998
Received: from kanmaster.ca.newbridge.com by kanata-gw1.ca.newbridge.com via smtpd (for ns.newbridge.com [192.75.23.67]) with SMTP; 24 Jul 1998 18:42:02 UT
Received: from distmaster.newbridge.com (distmaster.ca.newbridge.com [138.120.118.27]) by ca.newbridge.com. (8.8.8/8.8.6) with SMTP id OAA05581; Fri, 24 Jul 1998 14:41:59 -0400 (EDT)
Received: by distmaster.newbridge.com (SMI-8.6/SMI-SVR4) id OAA01334; Fri, 24 Jul 1998 14:25:32 -0400
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <199807241814.DAA00254@necom830.hpcl.titech.ac.jp>
Subject: Re: PQC and QOSPF
To: J.Crowcroft@cs.ucl.ac.uk
Date: Sat, 25 Jul 1998 03:14:11 -0000
Cc: ychen@fla.fujitsu.com, zzhang@argon.com, qosr@newbridge.com
In-Reply-To: <1927.901301580@cs.ucl.ac.uk>; from "Jon Crowcroft" at Jul 24, 98 6:33 pm
X-Mailer: ELM [version 2.3 PL11]
Sender: owner-qosr@ca.newbridge.com
Precedence: bulk
X-Info: [Un]Subscribe to qosr-request@newbridge.com

Jon;

> well if you do qos (load related) routing, then you HAVE to update the
> route state somehow - there's 3-ish ways

3/ is like reimplementing TCP over UDP.

And, it is always the case that the implementation is poor.

> 3/ have a third party distriburted entity that uses traffic
> measurement and is neither signaling protocol
> nor route protocol dependent

> the latter approach seems to me to be the best option sicne we can
> then evolve routing signaling and admission control (and charging) all
> seperately...

The protocol to do it distributed way is called a routing protocol.

Of course, all the distributed protocol is subject to delay.

							Masataka Ohta