[Tsvwg] Comments on draft-morita-tsvwg-pps

"Geib, Ruediger" <Ruediger.Geib@t-systems.com> Fri, 08 August 2003 16:05 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16158 for <tsvwg-archive@odin.ietf.org>; Fri, 8 Aug 2003 12:05:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19l9ji-0003gA-UH for tsvwg-archive@odin.ietf.org; Fri, 08 Aug 2003 12:05:04 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h78G521c014143 for tsvwg-archive@odin.ietf.org; Fri, 8 Aug 2003 12:05:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19l9jh-0003fK-5h; Fri, 08 Aug 2003 12:05:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19l3rO-0004ga-Ur for tsvwg@optimus.ietf.org; Fri, 08 Aug 2003 05:48:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05831 for <tsvwg@ietf.org>; Fri, 8 Aug 2003 05:48:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19l3rL-0007Mu-00 for tsvwg@ietf.org; Fri, 08 Aug 2003 05:48:31 -0400
Received: from mail1.telekom.de ([62.225.183.202]) by ietf-mx with esmtp (Exim 4.12) id 19l3rK-0007MX-00 for tsvwg@ietf.org; Fri, 08 Aug 2003 05:48:30 -0400
Received: from g8pbr.blf01.telekom.de by G8SBV.dmz.telekom.de with ESMTP; Fri, 8 Aug 2003 11:24:16 +0200
Received: by G8PBR.blf01.telekom.de with Internet Mail Service (5.5.2653.19) id <QHJCK1V1>; Fri, 8 Aug 2003 11:24:16 +0200
Message-Id: <9F8582E37B2EE5498E76392AEDDCD3FE03DBB58B@G8PQD.blf01.telekom.de>
From: "Geib, Ruediger" <Ruediger.Geib@t-systems.com>
To: morita.naotaka@lab.ntt.co.jp
Cc: tsvwg@ietf.org
Date: Fri, 08 Aug 2003 11:24:15 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Subject: [Tsvwg] Comments on draft-morita-tsvwg-pps
Sender: tsvwg-admin@ietf.org
Errors-To: tsvwg-admin@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Hello Naotaka,

I think that pps is a good 
idea. Having not to maintain QoS signaling 
state in a backbone router is a pretty 
good thing to do.

Some comments on contents:

Section 4 suggests two stage monitoring 
of end-system behaviour. I agree that abuse 
must be prevented at the source. You don't 
talk of signaling there, but I guess it 
could be part of a two stage monitoring 
solution (you mention however a "declared 
peak bit rate" - sounds like signaling 
to me).

Section 5 is about system behaviour in the 
case of congestion. Would something like 
an "explicit congestion notification" of 
the backbone be useful? If end systems 
could, as a reaction on such a congestion 
indication, use codecs with lower bit rate 
for their MF-H traffic, additional calls 
may be accepted. 

Section 7.1: I'm not a queuing expert, but 
why would MF-M traffic see higher jitter? 
Aren't all MF packet in the same queue and 
those tagged as MF-M are discarded earlier? 
The result is higher loss probability, 
which is intended. But it shouldn't be 
higher jitter (don't earlier losses make 
it look like a "shorter" queue?).

Section 7.4 suggests the transmitter not to 
pause at the edge. ISPs may charge on volume 
and customers won't be happy if their 
terminal creates traffic while they aren't 
active. 
I understand the issue and I should offer 
an alternative. Some form of signaling based 
admission control in combination with 
measurements?

Section 7.5: The RMONMIB WG maintains some 
drafts promoting RAQMON. I'm not familiar with 
details, but your media monitoring server might 
require similar functionality. If you are 
interested:
http://www.ietf.org/internet-drafts/draft-ietf-rmonmib-raqmon-framework-02.txt

Regards, RĂ¼diger


RĂ¼diger Geib
T-Systems
Systems Integration
Senior Expert, Technologiezentrum
Am Kavalleriesand 3, 64295 Darmstadt
Germany
Fon: +49 6151 832138
http://www.t-systems.com
 

_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg