Re: [Diffserv-interest] Re: Diffserv-interest digest, Vol 1 #104 - 2 msgs

Jing Shen <jshen_cad@yahoo.com.cn> Fri, 31 October 2003 09:42 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 EAA19254 for <diffserv-interest-archive@odin.ietf.org>; Fri, 31 Oct 2003 04:42:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFVn9-0004CD-4W for diffserv-interest-archive@odin.ietf.org; Fri, 31 Oct 2003 04:42:03 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9V9g2Xk016103 for diffserv-interest-archive@odin.ietf.org; Fri, 31 Oct 2003 04:42:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFVn7-0004Aj-Gu; Fri, 31 Oct 2003 04:42:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFVmq-000495-FP for diffserv-interest@optimus.ietf.org; Fri, 31 Oct 2003 04:41:44 -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 EAA19251 for <diffserv-interest@ietf.org>; Fri, 31 Oct 2003 04:41:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFVmn-0004gt-00 for diffserv-interest@ietf.org; Fri, 31 Oct 2003 04:41:41 -0500
Received: from web15206.mail.cnb.yahoo.com ([202.3.77.136] helo=web15206.mail.bjs.yahoo.com) by ietf-mx with smtp (Exim 4.12) id 1AFVmm-0004gb-00 for diffserv-interest@ietf.org; Fri, 31 Oct 2003 04:41:40 -0500
Message-ID: <20031031094109.17799.qmail@web15206.mail.bjs.yahoo.com>
Received: from [202.101.172.19] by web15206.mail.bjs.yahoo.com via HTTP; Fri, 31 Oct 2003 17:41:09 CST
Date: Fri, 31 Oct 2003 17:41:09 +0800 (CST)
From: =?gb2312?q?Jing=20Shen?= <jshen_cad@yahoo.com.cn>
Subject: Re: [Diffserv-interest] Re: Diffserv-interest digest, Vol 1 #104 - 2 msgs
To: "John H. Shuler" <johnshuler@mac.com>, diffserv-interest@ietf.org
In-Reply-To: <BBC742CC.1497A%johnshuler@mac.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id EAA19252
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: quoted-printable

IMHO, diffserv is just to define some basic rules to
be followed by ISPS who will negotiate real SLA
parameters. These parameters are to be 'implemented'
in their network and supported by routers around.
So, a coarse defination like EF, AF is enough.

Anyway, as pointed out by other people here, DiffServ
just make up logical network in physical network. This
means there will be congestion in every logical
networks.

jing shen

' spamcontrol '
 


 --- "John H. Shuler" <johnshuler@mac.com>; 的正文:>
Why make a distinction between "Standard Service
> Class" and "Low Priority
> Data"?
> 
> In fact, it seems the most useful outcome of this
> paper is to help service
> providers standardize across and between their
> networks as to service class
> treatment for different service types. For this
> reason, it seems the best
> thing to do is, rather than to create these
> semi-artificial classes and
> sub-classes, to get quite specific about how to mark
> each specific service,
> e.g. IP telephony, SNA, HTTP, FTP, unidirectional
> video, interactive
> multimedia, etc. You have gone part of the way to
> this goal, but have put
> what seems to be an artificial middle step into the
> process... These service
> classes. I can see why you would do this in an
> attempt to consolidate the
> classes for ease of management, but by the time you
> are done, you have so
> many classes and variations that you have defeated
> this purpose anyway. And
> the net goal of standardizing treatment across the
> network is still not
> achieved because of the multiple options for several
> of the services.
> 
> Just some thoughts on a single, careful reading.
> 
> Also, there is some dumb editorial stuff:
> (1) Do a lookup for the word "respectfully" and make
> sure you don't really
> mean "respectively".
> (2) Look up "sufficed" and replace with
> "sufficient".
> (3) You also have a tendency to use "which" instead
> of "that"
> (4) There is an instance of using "then" instead of
> "than".
> 
> Sorry I'm too lazy to be specific about where (it's
> late).
> 
> j
> -- 
> Jay Shuler
> President
> Beyond Category Consulting
> 4020 Halkins Drive
> San Jose, CA 95124
> (408) 582-3682
> Jay@BeyondCategory.US
> www.BeyondCategory.US
> 
> 
> > From: diffserv-interest-request@ietf.org
> > Reply-To: diffserv-interest@ietf.org
> > Date: Wed, 29 Oct 2003 12:00:04 -0500
> > To: diffserv-interest@ietf.org
> > Subject: Diffserv-interest digest, Vol 1 #104 - 2
> msgs
> > 
> > Send Diffserv-interest mailing list submissions to
> > diffserv-interest@ietf.org
> > 
> > To subscribe or unsubscribe via the World Wide
> Web, visit
> >
>
https://www1.ietf.org/mailman/listinfo/diffserv-interest
> > or, via email, send a message with subject or body
> 'help' to
> > diffserv-interest-request@ietf.org
> > 
> > You can reach the person managing the list at
> > diffserv-interest-admin@ietf.org
> > 
> > When replying, please edit your Subject line so it
> is more specific
> > than "Re: Contents of Diffserv-interest digest..."
> > 
> > 
> > Today's Topics:
> > 
> >  1. Re: congestion in diffserv network (John
> Schnizlein)
> >  2. Re: congestion in diffserv network (Brian E
> Carpenter)
> > 
> > --__--__--
> > 
> > Message: 1
> > Date: Tue, 28 Oct 2003 12:30:55 -0500
> > To: "Feng Y" <feng6@uwindsor.ca>;
> > From: John Schnizlein <jschnizl@cisco.com>;
> > Subject: Re: [Diffserv-interest] congestion in
> diffserv network
> > Cc: diffserv-interest@ietf.org
> > 
> > The simple reason that congestion can occur is
> that the TCA
> > need not limit incoming traffic sufficiently to
> avoid it.
> > The TCA for expedited forwarding is the only one,
> of many=20
> > traffic classes, that seeks to eliminate potential
> congestion,=20
> > in order to minimize delay and jitter.
> > 
> > The parameters of other class definitions, assured
> forwarding
> > for example, are intended to mark traffic at
> different ingress
> > rates for different treatment when congestion
> occurs. Note
> > that this anticipates that congestion will occur.
> > 
> > Please recall that the high link utilization in an
> IP network
> > is obtained in large measure because traffic loads
> are high
> > enough to produce occasional congestion.
> Cooperative management
> > of this congestion is the responsibility of
> transport-layer
> > protocols.
> > 
> > John
> > 
> > At 10:43 AM 10/28/2003, Feng Y wrote:
> >> ... I wonder why the
> >> overloading or even congestion occurs in diffserv
> network.
> >> In diffserv architecture, the =93DS ingress node
> is
> >> responsible for ensuring that the traffic
> entering the DS
> >> domain conforms to any traffic conditioning
> agreement (TCA)
> >> between it and the other domain to which the
> ingress node
> >> is connected=94 [RFC 2475]. Moreover,  
> =93Traffic conditioning
> >> performs metering, shaping, policing and/or
> re-marking to
> >> ensure that the traffic entering the DS domain
> conforms to
> >> the rules specified in the TCA, in accordance
> with the
> >> domain's service provisioning policy=94. So what
> causes the
> >> overloading or congestion in diffserv? Does
> anyone explain
> >> it for me or give me some references. Thanks in
> advance.
> > 
> > 
> > 
> > --__--__--
> > 
> > Message: 2
> > Date: Wed, 29 Oct 2003 12:07:02 +0100
> > From: Brian E Carpenter <brc@zurich.ibm.com>;
> > Organization: IBM
> > To: John Schnizlein <jschnizl@cisco.com>;
> > CC: Feng Y <feng6@uwindsor.ca>;,
> diffserv-interest@ietf.org
> > Subject: Re: [Diffserv-interest] congestion in
> diffserv network
> > 
> > Another way to look at it is that what diffserv
> does is split the network=
> > 
> > into several separate networks, but each of them
> retains the statistical
> > properties of a single Internet.
> > 
> >  Brian
> > 
> > John Schnizlein wrote:
> >> =
> > 
> >> The simple reason that congestion can occur is
> that the TCA
> >> need not limit incoming traffic sufficiently to
> avoid it.
> >> The TCA for expedited forwarding is the only one,
> of many
> >> traffic classes, that seeks to eliminate
> potential congestion,
> >> in order to minimize delay and jitter.
> >> =
> > 
> >> The parameters of other class definitions,
> assured forwarding
> >> for example, are intended to mark traffic at
> different ingress
> >> rates for different treatment when congestion
> occurs. 
=== message truncated === 

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

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