References to MLPP that works Re: [Ieprep] I-D ACTION:draft-ietf-ieprep-domain-req-00.txt
Janet P Gunn <jgunn6@csc.com> Mon, 02 February 2004 22:14 UTC
Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17628 for <ieprep-archive@odin.ietf.org>; Mon, 2 Feb 2004 17:14:45 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AnmKg-0005WT-Ex for ieprep-archive@odin.ietf.org; Mon, 02 Feb 2004 17:14:18 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i12MEIoG021223 for ieprep-archive@odin.ietf.org; Mon, 2 Feb 2004 17:14:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AnmKg-0005WE-At for ieprep-web-archive@optimus.ietf.org; Mon, 02 Feb 2004 17:14:18 -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 RAA17579 for <ieprep-web-archive@ietf.org>; Mon, 2 Feb 2004 17:14:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AnmKd-0004Il-00 for ieprep-web-archive@ietf.org; Mon, 02 Feb 2004 17:14:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AnmJN-00049o-00 for ieprep-web-archive@ietf.org; Mon, 02 Feb 2004 17:12:58 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AnmIQ-0003zs-00 for ieprep-web-archive@ietf.org; Mon, 02 Feb 2004 17:11:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AnmIR-0005JI-S3; Mon, 02 Feb 2004 17:11:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AnmHr-0005HS-Eg for ieprep@optimus.ietf.org; Mon, 02 Feb 2004 17:11:23 -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 RAA17343 for <ieprep@ietf.org>; Mon, 2 Feb 2004 17:11:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AnmHp-0003se-00 for ieprep@ietf.org; Mon, 02 Feb 2004 17:11:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AnmGo-0003im-00 for ieprep@ietf.org; Mon, 02 Feb 2004 17:10:18 -0500
Received: from amer-mta02.csc.com ([20.137.2.248]) by ietf-mx with esmtp (Exim 4.12) id 1AnmFv-0003aR-00 for ieprep@ietf.org; Mon, 02 Feb 2004 17:09:23 -0500
Received: from csc.com (va-fch32.csc.com [20.6.39.233]) by amer-mta02.csc.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i12MATsQ029059 for <ieprep@ietf.org>; Mon, 2 Feb 2004 17:10:29 -0500 (EST)
Subject: References to MLPP that works Re: [Ieprep] I-D ACTION:draft-ietf-ieprep-domain-req-00.txt
To: Fred Baker <fred@cisco.com>
Cc: ieprep@ietf.org
X-Mailer: Lotus Notes Release 5.0.11 July 24, 2002
Message-ID: <OF251F8553.6764218B-ON85256E2E.00788507-85256E2E.007A05B0@csc.com>
From: Janet P Gunn <jgunn6@csc.com>
Date: Mon, 02 Feb 2004 17:12:48 -0500
X-MIMETrack: Serialize by Router on VA-FCH32/SRV/CSC(Release 6.0.3|September 26, 2003) at 02/02/2004 05:07:40 PM
MIME-Version: 1.0
Content-type: text/plain; charset="US-ASCII"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Comments in line. ---------------------------------------------------------------------------------------- This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. ---------------------------------------------------------------------------------------- Fred Baker <fred @cisco.com> To: Janet P Gunn <jgunn6@csc.com> cc: ieprep@ietf.org 01/27/2004 09:35 Subject: Re: [Ieprep] I-D ACTION:draft-ietf-ieprep-domain-req-00.txt PM At 12:32 PM 1/27/2004, Janet P Gunn wrote: >As Fred Baker says in draft-baker-tsvwg-mlpp-that-works.00.txt, if call >admission is working properly, traffic marking is not needed in normal >operations. lest I be misunderstood, let me restate that. What I wrote was: One will ask the value of the multiple DSCPs. They are, in fact, of limited to no value in normal operation, as all vice and video traffic should have been admitted, and therefore capacity will have been assigned to them. The behavior of this service will be indistinguishable from the EF PHB regardless of traffic marking. In retrospect, I wonder what the vice traffic would be :^) [jpg] Maybe all that "organ enlargement" spam? This is not to be understood as saying "no traffic marking is required"; one still needs RFC 3246. But if bandwidth admission is operating correctly, having N different marks will be operationally indistinguishable from having a single EF mark, as the total number of bytes on the wire will be the same. jpg], I did understand that. I was oversimplifying to make my point. >It is in this context that ETS calls must be given a high probability of >meeting the QoS criteria, even when network congestion and or damage are >severe. I wonder if we are communicating here. RFC 3246 is designed to operate in a congested network, and to operate in a network in which routing may change. The comment in the mlpp-that-works draft - which if it is giving cause for confusion I will happily remove - is basically me bending over backwards to be intellectually honest and see if I can find a case where CAC may be insufficient. [jpg] And I was blatantly taking advantage of your "bending over backwards" - to identify a case where CAC may not be sufficient for the ETS Voice application. Think about this for a moment: the argument being placed for MLEF is that even in the presence of some loss, voice is intelligible. If that is true, then just after a route change, during the brief interval between the data flow being switched to a new path and the CAC following that and either OKing the flow or deciding to shut down the call, when there may be some loss, voice should be equally intelligible, no? Or does the argument that voice is able to work around a modest level of loss only work when it comes from the proponents of multiple code points? [jpg] In the ETS voice scenario, I am NOT trying to say that "voice is able to work around a modest level of loss". I am taking the highly elitist position that, if there is a situation where SOME "calls" are going to have to lose packets, I want it to be the non-ETS calls (whether or not the non-ETS calls remain intelligible or not) that lose packets, and not the ETS calls. [jpg] I further agree that, in any situation where "calls" are losing packets, it is highly desirable to "do something" so that you have some calls that remain up and intelligible, and so that other calls go away, rather than using up bandwidth sending packets that are not "useful" from the end user's perspective. And whatever that "something" is, I want it to be able (assuming the appropriate business agreements are in place) to slant the odds in favor of the ETS calls being the ones that stay up and intelligible. Janet << Attachment Removed : C.DTF >> _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep
- References to MLPP that works Re: [Ieprep] I-D AC… Janet P Gunn
- RE: References to MLPP that works Re: [Ieprep] I-… steve.norreys
- RE: References to MLPP that works Re: [Ieprep] I-… Janet Gunn
- Re: References to MLPP that works Re: [Ieprep] I-… Fred Baker
- RE: References to MLPP that works Re: [Ieprep] I-… Ken Carlberg