From mailnull@www1.ietf.org Fri Apr 4 09:36:15 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23359 for ; Fri, 4 Apr 2003 09:36:15 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h34Ed2q20830 for diffserv-interest-archive@odin.ietf.org; Fri, 4 Apr 2003 09:39:02 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h34Ed1K20825; Fri, 4 Apr 2003 09:39:01 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h34EbdK20747 for ; Fri, 4 Apr 2003 09:37:39 -0500 Received: from d12lmsgate-5.de.ibm.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23239 for ; Fri, 4 Apr 2003 09:34:20 -0500 (EST) Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23]) by d12lmsgate-5.de.ibm.com (8.12.9/8.12.8) with ESMTP id h34Eagju008826; Fri, 4 Apr 2003 16:36:42 +0200 Received: from ochsehorn.zurich.ibm.com (ochsehorn.zurich.ibm.com [9.4.16.140]) by d12relay02.de.ibm.com (8.12.8/NCO/VER6.5) with SMTP id h34EafcM285748; Fri, 4 Apr 2003 16:36:41 +0200 Received: from dhcp21-82.zurich.ibm.com by ochsehorn.zurich.ibm.com (AIX 4.3/UCB 5.64/4.03) id AA62078 from ; Fri, 4 Apr 2003 16:36:40 +0200 Message-Id: <3E8D98A6.615AA61E@hursley.ibm.com> Date: Fri, 04 Apr 2003 16:37:26 +0200 From: Brian E Carpenter Organization: IBM X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,fr,de Mime-Version: 1.0 To: diffserv-interest@ietf.org Cc: Bert Wijnen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Diffserv-interest] Fwd: Re-usability of DIFFSERV MIB 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: , List-Id: Differentiated services general discussion List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit On behalf of Bert... Subject: Re-usability of DIFFSERV MIB Date: Fri, 4 Apr 2003 15:12:15 +0200 From: "Wijnen, Bert (Bert)" To: diffserv@ietf.org FYI and possible (re-)action. Thanks, Bert -----Original Message----- From: Woundy, Richard [mailto:Richard_Woundy@cable.comcast.com] Sent: donderdag 3 april 2003 0:58 To: 'Wilson.Sawyer@arrisi.com'; Wijnen, Bert (Bert) Cc: ipcdn@ietf.org Subject: RE: [ipcdn] Re: Status - draft-ietf-ipcdn-subscriber-mib-10.txt Wilson and Bert, One immediate issue I found, in trying to re-use the DiffServ MIB for the DOCSIS Subscriber Management functionality, was in the structure of the Data Path table, which is the initial table for packet classification. The Data Path Table is the first lookup table in the DiffServ MIB, and it uses ifIndex and ifDirection as the initial parameters to match. Upon a match, the typical next table is the Classifier Table (although the entry may point to other Tables in the MIB). In the Subscriber Management MIB, the first lookup table is docsSubMgtCmFilterTable, which uses the particular cable modem, upstream or downstream direction (similar to ifDirection), and CM versus CPE (CPEs are behind the CMs on the subscriber home network) source/target to map to a filter-group. The filter-group points to a set of rows in the docsSubMgtPktFilterTable for packet classification. The four subscriber management filter-groups are configured through the DOCSIS 1.1/2.0 CM registration processes. The two gaps I see in DiffServ MIB functionality are: 1. The DiffServ MIB assumes that a uniform set of classifiers are applied to all traffic flowing over a particular interface, because in the general network case, one cannot differentiate traffic except by classification. The Subscriber Management MIB assumes that distinct sets of classifiers are applied to different groups of cable modems that co-exist on the same cable RF interface, because the DOCSIS registration process aids the CMTS in differentiating different CM/CPE traffic sources and sinks. Note that there can be thousands of CMs from different filter-groups co-existing on the same cable RF interface, so an operator would need to add thousands of Classifier Table entries to match on specific CM/CPE sources and sinks. 2. The Subscriber Management MIB differentiates between CM source/sink traffic and CPE source/sink traffic. The CMTS knows the difference between CMs and CPEs on the same cable RF IP subnet(s) via the DOCSIS registration process. Using the current DiffServ MIB, making distinctions between CM and CPE traffic would require many more entries in the Classifier Tables, in order to enumerate the CM source IP addresses. It looks like the DiffServ folks were looking to use more generic parameters than the ifIndex during the development of the MIB. From section 2.2 of RFC 3289: Another possible direction of abstraction is one using a concept of "roles" (often, but not always, applied to interfaces). In this case, it may be possible to re-use the object definitions in this MIB, especially the parameterization tables. The Data Path table will help in the reuse of the data path linkage tables by having the interface specific information centralized, allowing easier mechanical replacement of ifIndex by some sort of "roleIndex". This work is ongoing. I don't know how to apply this "ongoing work" to the immediate issues that are solved by the current Subscriber Management MIB. -- Rich _______________________________________________ Diffserv-interest mailing list Diffserv-interest@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv-interest From mailnull@www1.ietf.org Sat Apr 5 10:05:54 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07498 for ; Sat, 5 Apr 2003 10:05:54 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h35F9AJ01345 for diffserv-interest-archive@odin.ietf.org; Sat, 5 Apr 2003 10:09:10 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h35F9A801340; Sat, 5 Apr 2003 10:09:10 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h35F3l800322 for ; Sat, 5 Apr 2003 10:03:47 -0500 Received: from auemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07133 for ; Sat, 5 Apr 2003 10:00:00 -0500 (EST) Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by auemail1.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h35F2T609732 for ; Sat, 5 Apr 2003 10:02:29 -0500 (EST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Sat, 5 Apr 2003 17:02:28 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15501484215@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: diffserv-interest@ietf.org Date: Sat, 5 Apr 2003 17:02:22 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [Diffserv-interest] FW: Last Call: Textual Conventions for IPv6 Flow Label to Propos ed Standard 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: , List-Id: Differentiated services general discussion List-Post: List-Help: List-Subscribe: , FYI and possible comment. Send comments to iesg/ietf mailing lists, or for discussions join mibs@ops.ietf.org Thanks, Bert -----Original Message----- From: The IESG [mailto:iesg-secretary@ietf.org] Sent: zaterdag 5 april 2003 0:49 Subject: Last Call: Textual Conventions for IPv6 Flow Label to Proposed Standard The IESG has received a request from the Operations & Management Open Area Working Group to consider Textual Conventions for IPv6 Flow Label as a Proposed Standard. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2003-5-4. Files can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-ops-ipv6-flowlabel-00.txt _______________________________________________ Diffserv-interest mailing list Diffserv-interest@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv-interest From mailnull@www1.ietf.org Tue Apr 8 04:33:21 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02475 for ; Tue, 8 Apr 2003 04:33:21 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h388bxB03420 for diffserv-interest-archive@odin.ietf.org; Tue, 8 Apr 2003 04:37:59 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h388bv803415; Tue, 8 Apr 2003 04:37:57 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h388af802557 for ; Tue, 8 Apr 2003 04:36:41 -0400 Received: from keskus.tct.hut.fi (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02463 for ; Tue, 8 Apr 2003 04:31:33 -0400 (EDT) Received: from keskus.tct.hut.fi (localhost [127.0.0.1]) by keskus.tct.hut.fi (8.12.8/8.12.8) with ESMTP id h388Y4gf017820 for ; Tue, 8 Apr 2003 11:34:04 +0300 (EET DST) Received: from localhost (wzhou@localhost) by keskus.tct.hut.fi (8.12.8/8.12.8/Submit) with ESMTP id h388Y4Q2017817 for ; Tue, 8 Apr 2003 11:34:04 +0300 (EET DST) X-Authentication-Warning: keskus.tct.hut.fi: wzhou owned process doing -bs Date: Tue, 8 Apr 2003 11:34:04 +0300 (EET DST) From: Wenpeng Zhou X-X-Sender: To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Diffserv-interest] The effect of high prioriy class traffic 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: , List-Id: Differentiated services general discussion List-Post: List-Help: List-Subscribe: , Hi, I am a novice in this DiffServ networks field. In order to guarantee the QoS of EF class traffic and improve BE (Best Effort) throughput, do we need to consider the impact of EF class traffic on BE? if so, are there some feasible methods? Best regards, Zhou Wenpeng _______________________________________________ Diffserv-interest mailing list Diffserv-interest@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv-interest From mailnull@www1.ietf.org Tue Apr 8 06:05:05 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04295 for ; Tue, 8 Apr 2003 06:05:05 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h38A9j809560 for diffserv-interest-archive@odin.ietf.org; Tue, 8 Apr 2003 06:09:45 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h38A9j809555; Tue, 8 Apr 2003 06:09:45 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h38A8U809514 for ; Tue, 8 Apr 2003 06:08:30 -0400 Received: from ukexchsvr001.thrupoint.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04255 for ; Tue, 8 Apr 2003 06:03:19 -0400 (EDT) Received: by UKEXCHSVR001 with Internet Mail Service (5.5.2650.21) id <23PH3RC9>; Tue, 8 Apr 2003 10:59:50 +0100 Message-ID: From: "Metz, Eduard" To: "'Wenpeng Zhou '" , "'diffserv-interest@ietf.org '" Subject: RE: [Diffserv-interest] The effect of high prioriy class traffic Date: Tue, 8 Apr 2003 10:59:50 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2FDB5.98148FEC" 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: , List-Id: Differentiated services general discussion List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C2FDB5.98148FEC Content-Type: text/plain; charset="iso-8859-1" A common method is to set an upperbound to the resources (e.g. link capacity) that can be consumed by EF traffic. On one hand this protects other traffic from starvation through EF traffic, as well as assures that EF guarantees (or more precisely that of the PDB for which EF is used as a building block) can be met. Above can be implemented by policing EF traffic at the network ingress to assure users/customers stay within their profile. Additional measures may need to be taken in the core of the network (e.g. DIFFSERV aware TE) to assure EF load on specific links does not exceed its threshold. Hope this helps. cheers, Eduard -----Original Message----- From: Wenpeng Zhou To: diffserv-interest@ietf.org Sent: 8-4-03 9:34 Subject: [Diffserv-interest] The effect of high prioriy class traffic Hi, I am a novice in this DiffServ networks field. In order to guarantee the QoS of EF class traffic and improve BE (Best Effort) throughput, do we need to consider the impact of EF class traffic on BE? if so, are there some feasible methods? Best regards, Zhou Wenpeng _______________________________________________ Diffserv-interest mailing list Diffserv-interest@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv-interest ------_=_NextPart_001_01C2FDB5.98148FEC Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [Diffserv-interest] The effect of high prioriy class = traffic

 A common method is to set an upperbound to the = resources (e.g. link capacity) that can be consumed by EF traffic. On = one hand this protects other traffic from starvation through EF = traffic, as well as assures that EF guarantees (or more precisely that = of the PDB for which EF is used as a building block) can be = met.

 Above can be implemented by policing EF traffic = at the network ingress to assure users/customers stay within their = profile. Additional measures may need to be taken in the core of the = network (e.g. DIFFSERV aware TE) to assure EF load on specific links = does not exceed its threshold.

Hope this helps.

cheers,
   Eduard

-----Original Message-----
From: Wenpeng Zhou
To: diffserv-interest@ietf.org
Sent: 8-4-03 9:34
Subject: [Diffserv-interest] The effect of high = prioriy class traffic

Hi,
I am a novice in this DiffServ networks field. In = order to guarantee the
QoS of EF class traffic and improve BE (Best Effort) = throughput, do we
need to consider the impact of EF class traffic on = BE? if so, are there
some feasible methods?

Best regards,

Zhou Wenpeng

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

------_=_NextPart_001_01C2FDB5.98148FEC-- _______________________________________________ Diffserv-interest mailing list Diffserv-interest@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv-interest From mailnull@www1.ietf.org Wed Apr 9 10:31:32 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00744 for ; Wed, 9 Apr 2003 10:31:32 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h39EajZ18377 for diffserv-interest-archive@odin.ietf.org; Wed, 9 Apr 2003 10:36:45 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h39Eaj818372; Wed, 9 Apr 2003 10:36:45 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h39EXn818174 for ; Wed, 9 Apr 2003 10:33:49 -0400 Received: from d12lmsgate-3.de.ibm.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00638 for ; Wed, 9 Apr 2003 10:28:04 -0400 (EDT) Received: from d12relay01.de.ibm.com (d12relay01.de.ibm.com [9.165.215.22]) by d12lmsgate-3.de.ibm.com (8.12.9/8.12.8) with ESMTP id h39EUUCi019232; Wed, 9 Apr 2003 16:30:34 +0200 Received: from ochsehorn.zurich.ibm.com (ochsehorn.zurich.ibm.com [9.4.16.140]) by d12relay01.de.ibm.com (8.12.8/NCO/VER6.5) with SMTP id h39EUOvl114998; Wed, 9 Apr 2003 16:30:25 +0200 Received: from dhcp21-82.zurich.ibm.com by ochsehorn.zurich.ibm.com (AIX 4.3/UCB 5.64/4.03) id AA33950 from ; Wed, 9 Apr 2003 16:30:21 +0200 Message-Id: <3E942EAA.20C90134@hursley.ibm.com> Date: Wed, 09 Apr 2003 16:31:06 +0200 From: Brian E Carpenter Organization: IBM X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,fr,de Mime-Version: 1.0 To: "Metz, Eduard" Cc: "'Wenpeng Zhou '" , "'diffserv-interest@ietf.org '" Subject: Re: [Diffserv-interest] The effect of high prioriy class traffic References: 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: , List-Id: Differentiated services general discussion List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Since EF by definition has a throughput limit, its main effect on BE traffic is to reduce the available capacity for BE at times when the EF aggregate is consuming its allowed resources (and to worsen the jitter for BE when EF is scheduled preemptively). To look at it in a very elementary way, consider a 100 Mbit link on which you allocate 10 Mbits for an EF aggregate (e.g. carrying VoIP traffic). Then at busy hour, the BE traffic will see a 90 Mbit link. Brian > "Metz, Eduard" wrote: > > A common method is to set an upperbound to the resources (e.g. link capacity) that can be consumed by EF traffic. On one hand > this protects other traffic from starvation through EF traffic, as well as assures that EF guarantees (or more precisely that > of the PDB for which EF is used as a building block) can be met. > > Above can be implemented by policing EF traffic at the network ingress to assure users/customers stay within their profile. > Additional measures may need to be taken in the core of the network (e.g. DIFFSERV aware TE) to assure EF load on specific > links does not exceed its threshold. > > Hope this helps. > > cheers, > Eduard > > -----Original Message----- > From: Wenpeng Zhou > To: diffserv-interest@ietf.org > Sent: 8-4-03 9:34 > Subject: [Diffserv-interest] The effect of high prioriy class traffic > > Hi, > I am a novice in this DiffServ networks field. In order to guarantee the > QoS of EF class traffic and improve BE (Best Effort) throughput, do we > need to consider the impact of EF class traffic on BE? if so, are there > some feasible methods? > > Best regards, > > Zhou Wenpeng > _______________________________________________ Diffserv-interest mailing list Diffserv-interest@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv-interest From mailnull@www1.ietf.org Wed Apr 9 12:45:15 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05668 for ; Wed, 9 Apr 2003 12:45:15 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h39Esc420148 for diffserv-interest-archive@odin.ietf.org; Wed, 9 Apr 2003 10:54:38 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h39Es6820117; Wed, 9 Apr 2003 10:54:06 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h391PB817752 for ; Tue, 8 Apr 2003 21:25:11 -0400 Received: from gandalf.icr.a-star.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10922 for ; Tue, 8 Apr 2003 21:19:37 -0400 (EDT) Received: from mailer.icr.a-star.edu.sg (mailer.icr.a-star.edu.sg [137.132.31.243]) by gandalf.icr.a-star.edu.sg (8.12.8+Sun/8.12.2) with ESMTP id h391MiGi009161 for ; Wed, 9 Apr 2003 09:22:44 +0800 (SGT) Received: from bkdom-MTA by mailer.icr.a-star.edu.sg with Novell_GroupWise; Wed, 09 Apr 2003 09:14:36 +0800 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.3 Date: Wed, 09 Apr 2003 09:14:21 +0800 From: "Jiang Yuming" To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h391PB817753 Subject: [Diffserv-interest] An Expedited Forwarding Per-Domain Behavior (EF PDB) 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: , List-Id: Differentiated services general discussion List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Hi, For your interest, the following paper defines an EF PDB, which will be presented at IWQoS'03. Yuming Jiang, "Per-Domain Packet Scale Rate Guarantee for Expedited Forwarding", IWQoS 2003. (http://www.cwc.nus.edu.sg/~jiangym/publications/c-iwqos'03.pdf) Regards, Yuming _______________________________________________ Diffserv-interest mailing list Diffserv-interest@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv-interest From mailnull@www1.ietf.org Tue Apr 15 04:35:01 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19081 for ; Tue, 15 Apr 2003 04:35:01 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3F8h3X16525 for diffserv-interest-archive@odin.ietf.org; Tue, 15 Apr 2003 04:43:03 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3F8h1816520; Tue, 15 Apr 2003 04:43:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3F8fL816467 for ; Tue, 15 Apr 2003 04:41:21 -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 EAA19028 for ; Tue, 15 Apr 2003 04:32:49 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 195LuS-0000v1-00 for diffserv-interest@ietf.org; Tue, 15 Apr 2003 04:35:20 -0400 Received: from keskus.netlab.hut.fi ([130.233.154.176] helo=keskus.tct.hut.fi) by ietf-mx with esmtp (Exim 4.12) id 195LuR-0000us-00 for diffserv-interest@ietf.org; Tue, 15 Apr 2003 04:35:19 -0400 Received: from keskus.tct.hut.fi (localhost [127.0.0.1]) by keskus.tct.hut.fi (8.12.8/8.12.8) with ESMTP id h3F8ZPgf003331 for ; Tue, 15 Apr 2003 11:35:25 +0300 (EET DST) Received: from localhost (wzhou@localhost) by keskus.tct.hut.fi (8.12.8/8.12.8/Submit) with ESMTP id h3F8ZPdk003328 for ; Tue, 15 Apr 2003 11:35:25 +0300 (EET DST) X-Authentication-Warning: keskus.tct.hut.fi: wzhou owned process doing -bs Date: Tue, 15 Apr 2003 11:35:24 +0300 (EET DST) From: Wenpeng Zhou X-X-Sender: To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Diffserv-interest] Bandwidth broker and scalability 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: , List-Id: Differentiated services general discussion List-Post: List-Help: List-Subscribe: , Hi, In DiffServ networks, core routes are not aware of signaling. Therefore, some researchers proposed bandwidth broker. One bandwidth broker for one domain, I think there is a problem about the scalability. In general, How can we resolve this problem? Can MPLS provide some aids in this perspective? Best regards, Wenpeng _______________________________________________ Diffserv-interest mailing list Diffserv-interest@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv-interest From mailnull@www1.ietf.org Tue Apr 15 05:00:04 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA19535 for ; Tue, 15 Apr 2003 05:00:04 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3F987M18505 for diffserv-interest-archive@odin.ietf.org; Tue, 15 Apr 2003 05:08:07 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3F987818500; Tue, 15 Apr 2003 05:08:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3F97f818470 for ; Tue, 15 Apr 2003 05:07:41 -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 EAA19504 for ; Tue, 15 Apr 2003 04:59:08 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 195MJv-00011u-00 for diffserv-interest@ietf.org; Tue, 15 Apr 2003 05:01:39 -0400 Received: from tokyo.ccrle.nec.de ([195.37.70.2]) by ietf-mx with esmtp (Exim 4.12) id 195MJu-00011k-00 for diffserv-interest@ietf.org; Tue, 15 Apr 2003 05:01:39 -0400 Received: from venus.office (venus.office [10.1.1.11]) by tokyo.ccrle.nec.de (8.12.9/8.12.8) with ESMTP id h3F91EVI011955; Tue, 15 Apr 2003 11:01:14 +0200 (CEST) Received: from [10.1.1.130] (brunner.office [10.1.1.130]) by venus.office (Postfix on SuSE Linux eMail Server 3.0) with ESMTP id 2153AC078; Tue, 15 Apr 2003 10:57:13 +0200 (CEST) Date: Tue, 15 Apr 2003 11:01:15 +0200 From: Marcus Brunner Reply-To: Marcus Brunner To: Wenpeng Zhou , diffserv-interest@ietf.org Subject: Re: [Diffserv-interest] Bandwidth broker and scalability Message-ID: <7610753.1050404475@[10.1.1.130]> In-Reply-To: References: X-Mailer: Mulberry/3.0.2 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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: , List-Id: Differentiated services general discussion List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Wenpeng, you have to carefully look into the issue, before you can judge that it does not scale. Then it depends on the dimension you measure scalability. But I don't see how MPLS could with this. Marcus --On Dienstag, 15. April 2003 11:35 +0300 Wenpeng Zhou wrote: > Hi, > In DiffServ networks, core routes are not aware of signaling. Therefore, > some researchers proposed bandwidth broker. One bandwidth broker for one > domain, I think there is a problem about the scalability. In general, > How can we resolve this problem? Can MPLS provide some aids in this > perspective? > > Best regards, > > Wenpeng > > _______________________________________________ > Diffserv-interest mailing list > Diffserv-interest@ietf.org > https://www1.ietf.org/mailman/listinfo/diffserv-interest -------------------------------------- Dr. Marcus Brunner Network Laboratories NEC Europe Ltd. E-Mail: brunner@ccrle.nec.de WWW: http://www.ccrle.nec.de/ Phone: +49 (0) 6221 905 11 29 personal home page: http://www.brubers.org/marcus _______________________________________________ Diffserv-interest mailing list Diffserv-interest@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv-interest From mailnull@www1.ietf.org Wed Apr 16 02:39:19 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20079 for ; Wed, 16 Apr 2003 02:39:18 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3G6lmo22996 for diffserv-interest-archive@odin.ietf.org; Wed, 16 Apr 2003 02:47:48 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3G6ll822989; Wed, 16 Apr 2003 02:47:47 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3G6kc822911 for ; Wed, 16 Apr 2003 02:46:38 -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 CAA19936 for ; Wed, 16 Apr 2003 02:37:38 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 195gaX-00073M-00 for diffserv-interest@ietf.org; Wed, 16 Apr 2003 02:40:09 -0400 Received: from seic33.seu.edu.cn ([202.119.24.43] helo=seu.edu.cn) by ietf-mx with smtp (Exim 4.12) id 195gaW-00073J-00 for diffserv-interest@ietf.org; Wed, 16 Apr 2003 02:40:08 -0400 Received: (qmail 26195 invoked from network); 16 Apr 2003 06:39:37 -0000 Received: from ghome.seu.edu.cn (HELO gq) (211.65.59.4) by seic33.seu.edu.cn with SMTP; 16 Apr 2003 06:39:37 -0000 Date: Wed, 16 Apr 2003 14:40:49 +0800 From: cathy To: "diffserv-interest@ietf.org" X-mailer: FoxMail 4.0 beta 1 [cn] Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====002_Dragon832426226418_=====" Message-Id: Subject: [Diffserv-interest] The relationship between qos routing and diffserv 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: , List-Id: Differentiated services general discussion List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. --=====002_Dragon832426226418_===== Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: base64 SGVsbG8gYWxsLA0KICAgICAgICBJbiB0aGUgcGFwZXIgIkRpZmZlcmVudGlhdGVkIFNlcnZpY2Vz IGluIHRoZSBJbnRlcm5ldCIgb2YgRHIuIENhcnBlbnRlci4gVGhlIHJlbGF0aW9uc2hpcCBiZXR3 ZWVuIERpZmZzZXJ2IGFuZCBxb3Mgcm91dGluZyBpcyBkaXNjdXNzZWQuIEl0IGNvbmNsdWRlcyBm cm9tIHN0YXRpc3RpY3MgdGhhdCAic2VydmljZSBsZXZlbHMgYXJlIHNldCB1cCB0byBob2xkIGFj cm9zcyBhIGNsb3VkLG5vdCBhIHBhcnRpY3VsYXIgcGF0aCIuSXQgaXMgdGhlIHNwaXJpdCBvZiBE aWZmU2VydixidXQgSSB3YXMgY29uZnVzZWQgdGhhdCBob3cgdGhlIGNoYXJhY3RlcmlzdGljIG9m IHRoZSB3aG9sZSBkb21haW4gY2FuIGJlIHJlcHJlc2VudGVkIGJ5IG9ubHkgc2V2ZXJhbCBlZGdl IHJvdXRlcnM/IA0KICAgICAgIFN1cHBvc2Ugd2UgdXNlIEJCIHRvIG1hbmFnZSB0aGUgcmVzb3Vy Y2Ugb2YgdGhlIGRvbWFpbiBhbmQgZXhlY3V0ZSBhZG1pc3Npb24gY29udHJvbC4gd2hlbiBhIG5l dyBmbG93IHdhbnQgdG8gdHJhbnNtaXQgZGF0YSB0aHJvdWdoIHRoZSBEaWZmU2VydiBkb21haW4s IGhvdyBjYW4gd2UgZG8gdGhlIGFkbWlzc2lvbiBjb250cm9sIHdpdGhvdXQgY29uY2VybmluZyBp dCdzIHJvdXRlPyBTaW5jZSBtaWNyb2Zsb3dzIGluIHRoZSBzYW1lIHRyYWZmaWMgYWdncmVnYXRl IHdpbGwgZmxvdyBvdXQgdGhlIGRvbWFpbiAgZnJvbSBkaWZmZXJlbnQgZWdyZXNzIHJvdXRlciwg aG93IGNhbiB0aGUgcmVzb3VyY2UgYmUgcmVzZXJ2ZWQgaW4gdGhlIGludGVyaW9yIHJvdXRlcj8N CiAgICAgICBEb2VzIHNvbWVvbmUga25vdyB0aGlzIGtpbmQgb2Ygd29yayA/DQogICAgICAgVGhh bmtzIQ0KDQogICAgICAgQ2F0aHkNCg== --=====002_Dragon832426226418_===== Content-Type: text/html; charset="GB2312" Content-Transfer-Encoding: base64 PEhUTUw+DQo8SEVBRD4NCjxtZXRhIGh0dHAtZXF1aXZlPSJDb250ZW50LVR5cGUiIGNvbnRlbnQ9 InRleHQvaHRtbDsgY2hhcnNldD1HQjIzMTIiPg0KPE1FVEEgTkFNRT0iR0VORVJBVE9SIiBDb250 ZW50PSJNaWNyb3NvZnQgREhUTUwgRWRpdGluZyBDb250cm9sIj4NCjxUSVRMRT48L1RJVExFPg0K PC9IRUFEPg0KPEJPRFk+DQo8RElWPkhlbGxvIGFsbCw8L0RJVj4NCjxESVY+Jm5ic3A7Jm5ic3A7 Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IEluIHRoZSBwYXBlciAiRGlmZmVyZW50aWF0 ZWQgDQpTZXJ2aWNlcyBpbiB0aGUgSW50ZXJuZXQiIG9mIERyLiBDYXJwZW50ZXIuIFRoZSByZWxh dGlvbnNoaXAgYmV0d2VlbiBEaWZmc2VydiANCmFuZCBxb3Mgcm91dGluZyBpcyBkaXNjdXNzZWQu IEl0IGNvbmNsdWRlcyBmcm9tIHN0YXRpc3RpY3MgdGhhdCAic2VydmljZSBsZXZlbHMgDQphcmUg c2V0IHVwIHRvIGhvbGQgYWNyb3NzIGEgY2xvdWQsbm90IGEgcGFydGljdWxhciBwYXRoIi5JdCBp cyB0aGUgc3Bpcml0IG9mIA0KRGlmZlNlcnYsYnV0IEkgd2FzIGNvbmZ1c2VkIHRoYXQgaG93IHRo ZSBjaGFyYWN0ZXJpc3RpYyBvZiB0aGUgd2hvbGUgZG9tYWluIGNhbiANCmJlIHJlcHJlc2VudGVk IGJ5IG9ubHkgc2V2ZXJhbCBlZGdlIHJvdXRlcnM/IDwvRElWPg0KPERJVj4mbmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgU3VwcG9zZSB3ZSB1c2UgQkIgdG8gbWFuYWdlIHRoZSAN CnJlc291cmNlIG9mIHRoZSBkb21haW4gYW5kIGV4ZWN1dGUgYWRtaXNzaW9uIGNvbnRyb2wuIHdo ZW4gYSBuZXcgZmxvdyB3YW50IHRvIA0KdHJhbnNtaXQgZGF0YSB0aHJvdWdoIHRoZSBEaWZmU2Vy diBkb21haW4sIGhvdyBjYW4gd2UgZG8gdGhlIGFkbWlzc2lvbiBjb250cm9sIA0Kd2l0aG91dCBj b25jZXJuaW5nIGl0J3Mgcm91dGU/IFNpbmNlIG1pY3JvZmxvd3MgaW4gdGhlIHNhbWUgdHJhZmZp YyBhZ2dyZWdhdGUgDQp3aWxsIGZsb3cgb3V0IHRoZSBkb21haW4mbmJzcDsgZnJvbSBkaWZmZXJl bnQgZWdyZXNzIHJvdXRlciwgaG93IGNhbiB0aGUgDQpyZXNvdXJjZSBiZSByZXNlcnZlZCBpbiB0 aGUgaW50ZXJpb3Igcm91dGVyPzwvRElWPg0KPERJVj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsgRG9lcyBzb21lb25lIGtub3cgdGhpcyBraW5kIG9mIA0Kd29yayZuYnNwOz88 L0RJVj4NCjxESVY+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IFRoYW5rcyE8 L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu YnNwOyZuYnNwOyBDYXRoeTwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVY+Jm5ic3A7PC9E SVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPC9CT0RZPg0KPC9IVE1MPg0K --=====002_Dragon832426226418_=====-- _______________________________________________ Diffserv-interest mailing list Diffserv-interest@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv-interest From mailnull@www1.ietf.org Wed Apr 16 03:11:38 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20839 for ; Wed, 16 Apr 2003 03:11:38 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3G7K8225542 for diffserv-interest-archive@odin.ietf.org; Wed, 16 Apr 2003 03:20:08 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3G7K8825535; Wed, 16 Apr 2003 03:20:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3G7Ji825464 for ; Wed, 16 Apr 2003 03:19:44 -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 DAA20830 for ; Wed, 16 Apr 2003 03:10:43 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 195h6Y-0007Do-00 for diffserv-interest@ietf.org; Wed, 16 Apr 2003 03:13:14 -0400 Received: from web15206.mail.bjs.yahoo.com ([202.3.77.136]) by ietf-mx with smtp (Exim 4.12) id 195h6W-0007Df-00 for diffserv-interest@ietf.org; Wed, 16 Apr 2003 03:13:13 -0400 Message-ID: <20030416071244.67049.qmail@web15206.mail.bjs.yahoo.com> Received: from [61.174.154.4] by web15206.mail.bjs.yahoo.com via HTTP; Wed, 16 Apr 2003 15:12:44 CST Date: Wed, 16 Apr 2003 15:12:44 +0800 (CST) From: =?gb2312?q?Jing=20Shen?= Subject: Re: [Diffserv-interest] The relationship between qos routing and diffserv To: cathy , "diffserv-interest@ietf.org" In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1659805585-1050477164=:66075" Content-Transfer-Encoding: 8bit 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: , List-Id: Differentiated services general discussion List-Post: List-Help: List-Subscribe: , --0-1659805585-1050477164=:66075 Content-Type: text/plain; charset=gb2312 Content-Transfer-Encoding: 8bit Cathy, DiffServ does not try to control e2e qos by a explicit way which is adopted by InterServ. It just tries to identify several service level and relize that by orchestrating routers' behavior accross the network. The basic idea is: if every router delivers packet with the same policy the edge-to-edge QoS is predicable. > how can we do the admission control without concerning it's route? Incoming packet is classified according to SLA. >how can the resource be reserved in the interior router? it does not reserve any resource for special flow but share resource between service class. hope this helps. Does someone know this kind of work ? Thanks! Cathy Jing Shen State Key Lab of CAD&CG ZheJiang University(YuQuan) HangZhou, ZheJiang Province 310027 P.R.China --------------------------------- Do You Yahoo!? "雅虎邀你参与CCTV-2对话节目调查：移动、联通、灵通，要说爱你不容易 --0-1659805585-1050477164=:66075 Content-Type: text/html; charset=gb2312 Content-Transfer-Encoding: 8bit

Cathy,

DiffServ does not try to control e2e qos by a explicit way which is adopted by InterServ. It just tries to identify several service level and relize that by orchestrating routers' behavior accross the network. The basic idea is: if every router delivers packet with the same policy the edge-to-edge QoS is predicable.   

 > how can we do the admission control without concerning it's route?

Incoming packet is classified according to SLA.

>how can the resource be reserved in the interior router?

it does not reserve any resource for special flow but share resource between service class.

hope this helps.

 

       Does someone know this kind of work ?
       Thanks!
 
       Cathy
 
 
 


Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, ZheJiang Province 310027
P.R.China


Do You Yahoo!?
"雅虎邀你参与CCTV-2对话节目调查：移动、联通、灵通，要说爱你不容易 --0-1659805585-1050477164=:66075-- _______________________________________________ Diffserv-interest mailing list Diffserv-interest@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv-interest From mailnull@www1.ietf.org Wed Apr 16 07:02:19 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25174 for ; Wed, 16 Apr 2003 07:02:19 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3GBArP09919 for diffserv-interest-archive@odin.ietf.org; Wed, 16 Apr 2003 07:10:53 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3GBAr809914; Wed, 16 Apr 2003 07:10:53 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3GB9v809879 for ; Wed, 16 Apr 2003 07:09:57 -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 HAA25101 for ; Wed, 16 Apr 2003 07:00:52 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 195khG-0000KJ-00 for diffserv-interest@ietf.org; Wed, 16 Apr 2003 07:03:22 -0400 Received: from [193.205.242.5] (helo=nausicaa.coritel.it ident=root) by ietf-mx with esmtp (Exim 4.12) id 195khF-0000KF-00 for diffserv-interest@ietf.org; Wed, 16 Apr 2003 07:03:21 -0400 Received: from uniroma2.it ([160.80.82.21]) by nausicaa.coritel.it (8.11.2/8.11.2) with ESMTP id h3GB2Uh17162; Wed, 16 Apr 2003 13:02:30 +0200 Message-ID: <3E9D381C.2B8B671@uniroma2.it> Date: Wed, 16 Apr 2003 13:01:49 +0200 From: Stefano Salsano X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: cathy CC: "diffserv-interest@ietf.org" Subject: Re: [Diffserv-interest] The relationship between qos routing and diffserv References: 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: , List-Id: Differentiated services general discussion List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Dear Cathy, among the several research efforts that have targeted the issue you describe, you may want to have a look at the AQUILA project: http://www.ist-aquila.org/ Best regards, Stefano cathy wrote: > > Hello all, > In the paper "Differentiated Services in the Internet" of Dr. > Carpenter. The relationship between Diffserv and qos routing is > discussed. It concludes from statistics that "service levels are set > up to hold across a cloud,not a particular path".It is the spirit of > DiffServ,but I was confused that how the characteristic of the whole > domain can be represented by only several edge routers? > Suppose we use BB to manage the resource of the domain and > execute admission control. when a new flow want to transmit data > through the DiffServ domain, how can we do the admission control > without concerning it's route? Since microflows in the same traffic > aggregate will flow out the domain from different egress router, how > can the resource be reserved in the interior router? > Does someone know this kind of work ? > Thanks! > > Cathy > > > -- ******************************************************************* Stefano Salsano Dipartimento Ingegneria Elettronica Universita' di Roma "Tor Vergata" Viale Politecnico, 1 - 00133 Roma - ITALY E-mail : stefano.salsano@uniroma2.it Cell. : +39 347 3706201 (Tor Vergata) Tel. : +39 06 72597450 Fax. : +39 06 72597435 (CoRiTeL) Tel. : +39 06 72582540 Fax. : +39 06 72583002 ******************************************************************* _______________________________________________ Diffserv-interest mailing list Diffserv-interest@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv-interest From mailnull@www1.ietf.org Wed Apr 16 23:26:50 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25276 for ; Wed, 16 Apr 2003 23:26:49 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3H3Zj516333 for diffserv-interest-archive@odin.ietf.org; Wed, 16 Apr 2003 23:35:45 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3H3Zh816328; Wed, 16 Apr 2003 23:35:43 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3H3YO816273 for ; Wed, 16 Apr 2003 23:34:24 -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 XAA25223 for ; Wed, 16 Apr 2003 23:24:58 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 19603c-0004vI-00 for diffserv-interest@ietf.org; Wed, 16 Apr 2003 23:27:28 -0400 Received: from web15203.mail.bjs.yahoo.com ([202.3.77.133]) by ietf-mx with smtp (Exim 4.12) id 19603b-0004vF-00 for diffserv-interest@ietf.org; Wed, 16 Apr 2003 23:27:28 -0400 Message-ID: <20030417032705.99085.qmail@web15203.mail.bjs.yahoo.com> Received: from [61.174.154.4] by web15203.mail.bjs.yahoo.com via HTTP; Thu, 17 Apr 2003 11:27:05 CST Date: Thu, 17 Apr 2003 11:27:05 +0800 (CST) From: =?gb2312?q?Jing=20Shen?= Subject: Re: Re: [Diffserv-interest] The relationship between qos routing and diffserv To: cathy Cc: diffserv-interest@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1136020350-1050550025=:99011" Content-Transfer-Encoding: 8bit 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: , List-Id: Differentiated services general discussion List-Post: List-Help: List-Subscribe: , --0-1136020350-1050550025=:99011 Content-Type: text/plain; charset=gb2312 Content-Transfer-Encoding: 8bit Cathy, >>Incoming packet is classified according to SLA. >So, how can we determine the SLA according to the resources of the domain? If a company's network is connected to ISP, the SLA is negotiated between ISP and customer before any traffic happens. Base on SLA policy could be set up in BB and traffic classification rules could be set up in edge router. On the other hand, if dynamic negotiation is supported dynamic SLA negotiation could be done between BBs, which set up traffic classification rules in correponding edge routers. >>how can the resource be reserved in the interior router? >it does not reserve any resource for special flow but share resource between service class. >I know it does not reserve resource for microflow,but how can it reserve >the resources for the aggregate flows(the special class)? The BW is allocated between service classes, e.g. Premium, BE etc. There has been some BW allocation policies defined, as Russian Model, MAM , MAR etc. hope this helps Best Wishes! Cathy Gao cathy_nj@sina.com 2003-04-16 Jing Shen State Key Lab of CAD&CG ZheJiang University(YuQuan) HangZhou, ZheJiang Province 310027 P.R.China --------------------------------- Do You Yahoo!? "雅虎邀你参与CCTV-2对话节目调查：移动、联通、灵通，要说爱你不容易 --0-1136020350-1050550025=:99011 Content-Type: text/html; charset=gb2312 Content-Transfer-Encoding: 8bit

Cathy,

 >>Incoming packet is classified according to SLA.
>So, how can we determine the SLA according to the resources of the domain?

If a company's network is connected to ISP, the SLA is negotiated between ISP and customer before any traffic happens. Base on SLA  policy could be set up in BB and traffic classification rules could be set up in edge router.

On the other hand, if dynamic negotiation is supported dynamic SLA negotiation could be done between BBs, which set up traffic classification rules in correponding edge routers.


>>how can the resource be reserved in the interior router?
>it does not reserve any resource for special flow but share resource between service class.
>I know it does not reserve resource for microflow,but how can it reserve >the resources for the aggregate flows(the special class)?

The BW is allocated between service classes, e.g. Premium, BE etc. There has been some BW allocation policies defined, as Russian Model, MAM , MAR etc. 

hope this helps



Best Wishes!
Cathy Gao
cathy_nj@sina.com
2003-04-16



Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, ZheJiang Province 310027
P.R.China


Do You Yahoo!?
"雅虎邀你参与CCTV-2对话节目调查：移动、联通、灵通，要说爱你不容易 --0-1136020350-1050550025=:99011-- _______________________________________________ Diffserv-interest mailing list Diffserv-interest@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv-interest From mailnull@www1.ietf.org Thu Apr 17 02:42:05 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10722 for ; Thu, 17 Apr 2003 02:42:05 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3H6p3e07683 for diffserv-interest-archive@odin.ietf.org; Thu, 17 Apr 2003 02:51:03 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3H6p2807678; Thu, 17 Apr 2003 02:51:02 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3H6nJ807618 for ; Thu, 17 Apr 2003 02:49:19 -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 CAA10683 for ; Thu, 17 Apr 2003 02:39:49 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 196367-0005oX-00 for diffserv-interest@ietf.org; Thu, 17 Apr 2003 02:42:15 -0400 Received: from web15204.mail.bjs.yahoo.com ([202.3.77.134]) by ietf-mx with smtp (Exim 4.12) id 196367-0005oS-00 for diffserv-interest@ietf.org; Thu, 17 Apr 2003 02:42:15 -0400 Message-ID: <20030417064148.25548.qmail@web15204.mail.bjs.yahoo.com> Received: from [61.174.154.4] by web15204.mail.bjs.yahoo.com via HTTP; Thu, 17 Apr 2003 14:41:48 CST Date: Thu, 17 Apr 2003 14:41:48 +0800 (CST) From: =?gb2312?q?Jing=20Shen?= Subject: Re: Re: [Diffserv-interest] The relationship between qos routing and diffserv To: Jing Shen , cathy Cc: diffserv-interest@ietf.org In-Reply-To: <20030417032705.99085.qmail@web15203.mail.bjs.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1809229721-1050561708=:10097" Content-Transfer-Encoding: 8bit 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: , List-Id: Differentiated services general discussion List-Post: List-Help: List-Subscribe: , --0-1809229721-1050561708=:10097 Content-Type: text/plain; charset=gb2312 Content-Transfer-Encoding: 8bit >The BW is allocated between service classes, e.g. Premium, BE etc. >There has been some BW allocation policies defined, as Russian >Model, MAM , MAR etc. I'm sorry to make a mistake, it should be Russian Doll Model, MAM and MAR. Jing Shen State Key Lab of CAD&CG ZheJiang University(YuQuan) HangZhou, ZheJiang Province 310027 P.R.China --------------------------------- Do You Yahoo!? "雅虎邀你参与CCTV-2对话节目调查：移动、联通、灵通，要说爱你不容易 --0-1809229721-1050561708=:10097 Content-Type: text/html; charset=gb2312 Content-Transfer-Encoding: 8bit

>The BW is allocated between service classes, e.g. Premium, BE etc. >There has been some BW allocation policies defined, as Russian >Model, MAM , MAR etc. 

I'm sorry to make a mistake, it should be Russian Doll Model, MAM and MAR.



Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, ZheJiang Province 310027
P.R.China


Do You Yahoo!?
"雅虎邀你参与CCTV-2对话节目调查：移动、联通、灵通，要说爱你不容易 --0-1809229721-1050561708=:10097-- _______________________________________________ Diffserv-interest mailing list Diffserv-interest@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv-interest From mailnull@www1.ietf.org Sun Apr 20 21:52:45 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20804 for ; Sun, 20 Apr 2003 21:52:45 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3L23YP10890 for diffserv-interest-archive@odin.ietf.org; Sun, 20 Apr 2003 22:03:34 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3L23T810885; Sun, 20 Apr 2003 22:03:29 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3L1wf810740 for ; Sun, 20 Apr 2003 21:58:41 -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 VAA20767 for ; Sun, 20 Apr 2003 21:47:22 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 197QRE-0005Eb-00 for diffserv-interest@ietf.org; Sun, 20 Apr 2003 21:49:44 -0400 Received: from seic33.seu.edu.cn ([202.119.24.43] helo=seu.edu.cn) by ietf-mx with smtp (Exim 4.12) id 197QRD-0005EW-00 for diffserv-interest@ietf.org; Sun, 20 Apr 2003 21:49:43 -0400 Received: (qmail 28190 invoked from network); 21 Apr 2003 01:49:28 -0000 Received: from ghome.seu.edu.cn (HELO gq) (211.65.59.4) by seic33.seu.edu.cn with SMTP; 21 Apr 2003 01:49:28 -0000 Date: Mon, 21 Apr 2003 9:50:43 +0800 From: cathy To: Jing Shen CC: "diffserv-interest@ietf.org" Subject: Re: Re: Re: [Diffserv-interest] The relationship between qos routing and diffserv X-mailer: FoxMail 4.0 beta 1 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Message-Id: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id h3L1wg810741 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: , List-Id: Differentiated services general discussion List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Jing Shen, Thanks for your help! > >>Incoming packet is classified according to SLA. >>So, how can we determine the SLA according to the resources of the domain? > >If a company's network is connected to ISP, the SLA is negotiated between ISP and customer before any traffic happens. Base on SLA policy could be set up in BB and traffic classification rules could be set up in edge router. > >On the other hand, if dynamic negotiation is supported dynamic SLA negotiation could be done between BBs, which set up traffic classification rules in correponding edge routers. > I m still confused that how can we decide the correct SLA, then add the corresponding policy to the edge router? Can you introduce some algorithms for BB and custom to negotiation SLA, then setup policy Base on SLA and the resources of domain? >>>how can the resource be reserved in the interior router? >>it does not reserve any resource for special flow but share resource between service class. >>I know it does not reserve resource for microflow,but how can it reserve >the resources for the aggregate flows(the special class)? > >The BW is allocated between service classes, e.g. Premium, BE etc. There has been some BW allocation policies defined, as Russian Model, MAM , MAR etc. This models is used in DiffServ with MPLS,but not in DIffserv its self, is it right? Best Wishes! Cathy Gao cathy_nj@sina.com 2003-04-21 _______________________________________________ Diffserv-interest mailing list Diffserv-interest@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv-interest From mailnull@www1.ietf.org Mon Apr 21 07:39:45 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10000 for ; Mon, 21 Apr 2003 07:39:45 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3LBol322963 for diffserv-interest-archive@odin.ietf.org; Mon, 21 Apr 2003 07:50:47 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3LBok822958; Mon, 21 Apr 2003 07:50:46 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3LBNu821517 for ; Mon, 21 Apr 2003 07:23:56 -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 HAA09423 for ; Mon, 21 Apr 2003 07:12:24 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 197ZG2-0006p1-00 for diffserv-interest@ietf.org; Mon, 21 Apr 2003 07:14:46 -0400 Received: from web15213.mail.bjs.yahoo.com ([202.3.77.143]) by ietf-mx with smtp (Exim 4.12) id 197ZG1-0006oy-00 for diffserv-interest@ietf.org; Mon, 21 Apr 2003 07:14:45 -0400 Message-ID: <20030421111429.22426.qmail@web15213.mail.bjs.yahoo.com> Received: from [61.174.154.4] by web15213.mail.bjs.yahoo.com via HTTP; Mon, 21 Apr 2003 19:14:29 CST Date: Mon, 21 Apr 2003 19:14:29 +0800 (CST) From: =?gb2312?q?Jing=20Shen?= Subject: Re: Re: Re: [Diffserv-interest] The relationship between qos routing and diffserv To: cathy Cc: diffserv-interest@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1218441457-1050923669=:22321" Content-Transfer-Encoding: 8bit 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: , List-Id: Differentiated services general discussion List-Post: List-Help: List-Subscribe: , --0-1218441457-1050923669=:22321 Content-Type: text/plain; charset=gb2312 Content-Transfer-Encoding: 8bit Cathy, >Thanks for your help! You're welcome. >I m still confused that how can we decide the correct SLA, then add the >corresponding policy to the edge router? The SLA is negotiated between ISP and customers or between ISPs. If such contract is set up it is put into PDB which is used by BB. BB control edge routeror negotiate with other BB by COPS. >Can you introduce some algorithms for BB and custom to negotiation >SLA, then setup policy Base on SLA and the resources of domain? It does not need any algo. but a protocol, as COPS. To the bandwidth allocation between different service classes, RDM or MAR is proposed for DS-TE but it does not limited to that area. MPLS is a transport protocol which enables QoS differentiation and TE in packet networks. regards Jing Shen State Key Lab of CAD&CG ZheJiang University(YuQuan) HangZhou, ZheJiang Province 310027 P.R.China --------------------------------- Do You Yahoo!? "雅虎邀你参与CCTV-2对话节目调查：移动、联通、灵通，要说爱你不容易 --0-1218441457-1050923669=:22321 Content-Type: text/html; charset=gb2312 Content-Transfer-Encoding: 8bit

Cathy,

 >Thanks for your help!

You're welcome.


>I m still confused that how can we decide the correct SLA, then add the >corresponding policy to the edge router?

The SLA is negotiated between ISP and customers or between ISPs. If such contract is set up it is put into PDB which is used by BB. BB control edge routeror negotiate with other BB by COPS.


>Can you introduce some algorithms for BB and custom to negotiation >SLA, then setup policy Base on SLA and the resources of domain?

It does not need any algo. but a protocol, as COPS. 

To the bandwidth allocation between different service classes, RDM or MAR is proposed for DS-TE but it does not limited to that area. MPLS is a transport protocol which enables QoS differentiation and TE in packet networks.

regards



Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, ZheJiang Province 310027
P.R.China


Do You Yahoo!?
"雅虎邀你参与CCTV-2对话节目调查：移动、联通、灵通，要说爱你不容易 --0-1218441457-1050923669=:22321-- _______________________________________________ Diffserv-interest mailing list Diffserv-interest@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv-interest