Re: FW: [Diffserv] Informal WG last call for draft-ietf-diffserv-new-terms-06.txt

Dan Grossman <dan@dma.isg.mot.com> Mon, 19 November 2001 16:00 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 LAA06238 for <diffserv-archive@odin.ietf.org>; Mon, 19 Nov 2001 11:00:38 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id LAA06879 for diffserv-archive@odin.ietf.org; Mon, 19 Nov 2001 11:00:34 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA06040; Mon, 19 Nov 2001 10:48:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA05902 for <diffserv@optimus.ietf.org>; Mon, 19 Nov 2001 10:48:25 -0500 (EST)
Received: from ftpbox.mot.com (ftpbox.mot.com [129.188.136.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05496; Mon, 19 Nov 2001 10:48:23 -0500 (EST)
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by ftpbox.mot.com (ftpbox 2.1) with ESMTP id IAA29876; Mon, 19 Nov 2001 08:48:09 -0700 (MST)]
Received: [from noah.dma.isg.mot.com (noah.dma.isg.mot.com [150.21.2.29]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id IAA11253; Mon, 19 Nov 2001 08:48:09 -0700 (MST)]
Received: from dma.isg.mot.com (nrlab-08.dma.isg.mot.com [150.21.50.46]) by noah.dma.isg.mot.com (8.8.8+Sun/8.8.8) with ESMTP id KAA08931; Mon, 19 Nov 2001 10:48:06 -0500 (EST)
Message-Id: <200111191548.KAA08931@noah.dma.isg.mot.com>
X-Mailer: exmh version 1.6.7 5/3/96
To: Andrea Westerinen <andreaw@cisco.com>
cc: Brian E Carpenter <brian@hursley.ibm.com>, Scott Brim <swb@employees.org>, "Diffserv@Ietf. Org" <diffserv@ietf.org>, "Policy@Ietf. Org" <policy@ietf.org>, "Bert Wijnen (Bert)" <bwijnen@lucent.com>
Subject: Re: FW: [Diffserv] Informal WG last call for draft-ietf-diffserv-new-terms-06.txt
In-reply-to: Your message of "Mon, 19 Nov 2001 00:54:20 EST." <GGEOLLMKEOKMFKADFNHOEEODEFAA.andreaw@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 19 Nov 2001 10:48:05 -0500
From: Dan Grossman <dan@dma.isg.mot.com>
Sender: diffserv-admin@ietf.org
Errors-To: diffserv-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Diffserv Discussion List <diffserv.ietf.org>
X-BeenThere: diffserv@ietf.org

Express it will be.

> "Express" is better.  I am ok with that.
> Thanks.
> Andrea
> 
> -----Original Message-----
> From: diffserv-admin@ietf.org [mailto:diffserv-admin@ietf.org]On Behalf
> Of Brian E Carpenter
> Sent: Monday, November 19, 2001 12:45 AM
> To: Andrea Westerinen
> Cc: Scott Brim; Dan Grossman; Diffserv@Ietf. Org; Policy@Ietf. Org; Bert
> Wijnen (Bert)
> Subject: Re: FW: [Diffserv] Informal WG last call for
> draft-ietf-diffserv-new-terms-06.txt
> 
> 
> The way we have taken to using the word "policy" in our technology is
> a bit strange - in normal English, "policy" is more abstract and general
> than a specific set of rules. Hence the problem, I think.
> 
> How about "express" instead of "define"?
> 
>    Brian
> 
> Andrea Westerinen wrote:
> >
> > But, my issue is with the word, "define" or "specify".  IMHO, the SLS
> > "defines" the values or behavior, and the rules "act on" or "realize" the
> > definition.  I didn't equate "implement" with "implementation", but I can
> > see the problem with that word.
> >
> > Does "realize" make it better or worse ("... the set of rules that realize
> > the parameters and range ...")?
> >
> > Andrea
> >
> > -----Original Message-----
> > From: diffserv-admin@ietf.org [mailto:diffserv-admin@ietf.org]On Behalf
> > Of Scott Brim
> > Sent: Sunday, November 18, 2001 2:45 PM
> > To: Andrea Westerinen
> > Cc: Dan Grossman; Diffserv@Ietf. Org; Policy@Ietf. Org; Bert Wijnen
> > (Bert)
> > Subject: Re: FW: [Diffserv] Informal WG last call for
> > draft-ietf-diffserv-new-terms-06.txt
> >
> > On Sat, Nov 17, 2001 05:55:31PM -0800, Andrea Westerinen wrote:
> > > Focusing on #4.
> > >
> > > The text says ... "Therefore, the relationship between an SLS and a
> > service
> > > provisioning policy is that the latter is, in part, the set of rules
> that
> > > define the parameters and range of values that may be in the former."
> > >
> > > <Dan> My inclination at this point is to leave it as it is, unless
> Andrea
> > > can come
> > > up with a concise sentence or two that can be dropped in.  I think that
> > > policy
> > > aware readers will understand that we don't intend to be restrictive,
> and
> > > non-policy aware readers won't be confused.
> > >
> > > Can we say "the set of rules that IMPLEMENT the parameters and range of
> > > values ..."?  My problem is with the word DEFINES.
> >
> > "Implements" is worse because the rules have nothing to do with
> > implementation (a standardization absolute).  If you think "defines"
> > crosses a boundary, I suggest "specifies".
> >
> > _______________________________________________
> 
> _______________________________________________
> diffserv mailing list
> diffserv@ietf.org
> https://www1.ietf.org/mailman/listinfo/diffserv
> Archive:
> http://www2.ietf.org/mail-archive/working-groups/diffserv/current/maillist.h
> tml
> 
> 



_______________________________________________
diffserv mailing list
diffserv@ietf.org
https://www1.ietf.org/mailman/listinfo/diffserv
Archive: http://www2.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html