Re: [Diffserv-interest] Re: [Tsvwg] Re: [NSIS] PPS and MF-PHB

Roland Bless <bless@tm.uka.de> Tue, 11 November 2003 18:16 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14049 for <diffserv-interest-archive@odin.ietf.org>; Tue, 11 Nov 2003 13:16:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJd3a-0008Ks-PW for diffserv-interest-archive@odin.ietf.org; Tue, 11 Nov 2003 13:16:02 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hABIG2t6032027 for diffserv-interest-archive@odin.ietf.org; Tue, 11 Nov 2003 13:16:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJd3Z-0008KH-Fv; Tue, 11 Nov 2003 13:16:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJd2c-0008GS-Pu for diffserv-interest@optimus.ietf.org; Tue, 11 Nov 2003 13:15:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14022; Tue, 11 Nov 2003 13:14:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJd2a-0007Ob-00; Tue, 11 Nov 2003 13:15:00 -0500
Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81]) by ietf-mx with esmtp (Exim 4.12) id 1AJd2a-0007OY-00; Tue, 11 Nov 2003 13:15:00 -0500
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5] helo=irams1.ira.uka.de) by iramx2.ira.uni-karlsruhe.de with esmtp (Exim 3.30 #10 (Debian)) id 1AJd2S-0002af-00; Tue, 11 Nov 2003 19:14:52 +0100
Received: from i72ms1.tm.uni-karlsruhe.de ([141.3.70.16] helo=smtp.ipv6.tm.uni-karlsruhe.de ident=8) by irams1.ira.uka.de with esmtp (Exim 3.30 #7 (Debian)) id 1AJd2R-00009B-00; Tue, 11 Nov 2003 19:14:51 +0100
Received: from i72ms.tm.uni-karlsruhe.de ([141.3.70.5] helo=i72mn12.tm.uka.de ident=3010) by smtp.ipv6.tm.uni-karlsruhe.de with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.12) id 1AJd2Q-0000z4-00; Tue, 11 Nov 2003 19:14:50 +0100
Date: Tue, 11 Nov 2003 19:15:12 +0100
From: Roland Bless <bless@tm.uka.de>
To: "MORITA, Naotaka" <morita.naotaka@lab.ntt.co.jp>, diffserv-interest@ietf.org, "'tsvwg@ietf.org'" <tsvwg@ietf.org>
Subject: Re: [Diffserv-interest] Re: [Tsvwg] Re: [NSIS] PPS and MF-PHB
Message-Id: <20031111191512.0adcff52.bless@tm.uka.de>
In-Reply-To: <5.1.1.11.2.20031110230755.04c76b18@imj.m.ecl.ntt.co.jp>
References: <5.1.1.11.2.20031110203629.04c62f88@imj.m.ecl.ntt.co.jp> <5.1.1.11.2.20031107093524.04528c98@imj.m.ecl.ntt.co.jp> <5.1.1.11.2.20031107093524.04528c98@imj.m.ecl.ntt.co.jp> <5.1.1.11.2.20031110203629.04c62f88@imj.m.ecl.ntt.co.jp> <5.1.1.11.2.20031110230755.04c76b18@imj.m.ecl.ntt.co.jp>
Organization: Institute of Telematics, University of Karlsruhe
X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: diffserv-interest-admin@ietf.org
Errors-To: diffserv-interest-admin@ietf.org
X-BeenThere: diffserv-interest@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/diffserv-interest>, <mailto:diffserv-interest-request@ietf.org?subject=unsubscribe>
List-Id: Differentiated services general discussion <diffserv-interest.ietf.org>
List-Post: <mailto:diffserv-interest@ietf.org>
List-Help: <mailto:diffserv-interest-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/diffserv-interest>, <mailto:diffserv-interest-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

On Mon, 10 Nov 2003 23:18:37 -0600
"MORITA, Naotaka" <morita.naotaka@lab.ntt.co.jp> wrote:
 
> That is right.  I will check the meaning of PDP.

PDB=Per-Domain Behavior, see RFC 3086.

>  >What you call "sub-classes" are effectively two different PHBs: you will
>  >need two distinct DSCPs and each DSCP will be mapped to a distinct PHB
>  >that will cause a specific packet forwarding treatment. RFC 2475 defines
>  >a PHB group as "a set of one or more PHBs that can only be meaningfully
>  >specified and implemented simultaneously,....". Please, see also RFC 3260
>  >for clarification on the AF class as a PHB group. MF-H makes not much
>  >sense without MF-M and vice versa. However, I think your PPS admission control
>  >scheme can be applied to an AF class as well as to the CSC PHBs, therefore you
>  >don't need two new PHBs.
> 
> But the important factor is the bandwidth limitation is shared between two 
> sub-classes.

Sure, no problem. That's why it is a PHB group.

> Sequence integrity is another one.

You mean that micro-flows should not be reordered if their
packets are marked as MF-H and MF-M alternatingly?
This is also a requirement for the PHBs in an AF class.
However, I don't see how you achieve this with the implementation 
described in 4.1 Fig.3: as soon as you have separate queues
for MF-H and MF-M, reordering may occur.

> How do I describe such things by isolated PHBs?

Confer the AF class definition and read RFC3260 in
addition to that.

> Anyway, what is CSC?

Class Selector Compliant PHB, cf. RFC 2474, sec. 4.2.2.2

> I will soon show you the difference between srTCM and my proposed two-threshold.

No, you don't have to, I support that there are differences. I'm not referring to 
the marking scheme, I'm referring to the AF PHB definition.

> For the correctness of the feedback information is a target of media 
> monitor server.

I'm not sure whether it is reasonable that the scheme depends on
the existence of some additional server.

Regards,
 Roland

_______________________________________________
Diffserv-interest mailing list
Diffserv-interest@ietf.org
https://www1.ietf.org/mailman/listinfo/diffserv-interest